Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. [RESOLVED] How quickly should logs rotate?
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

[RESOLVED] How quickly should logs rotate?

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 3 Posters 641 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • 3 Offline
    3 Offline
    3rdStng
    wrote on last edited by 3rdStng
    #1

    MSR: latest-23078-d592d400
    --Docker image on unRAID
    Hubitat: 2.3.5.121

    I was having an issue this morning where MSR wasn't seeing any hub updates from my Hubitat. In looking at the logs I was seeing pages of "reactor.log size hit rotation limit, rotating" messages. I purged these logs and restarted MSR thinking the logs were the cause of being stuck or something. I also changed the default from 2 MB and 5 logs to 3 MB and 9 logs. Long story short, that wasn't the issue and my HE needed a reboot. I had just rebooted a couple of days ago, so I didn't think that was the problem.

    Back on topic here. Everything seems to be communicating and MSR is seeing the updates now, however I feel that my logs filled up way too fast. Granted 3 MB isn't very large these days. Is it normal to take about 45 minutes to fill up nine 3 MB log files? Or does this seem excessive? I only changed the size and qty in my logging.yaml file.

    cedba928-6adc-4f24-be57-4fa4184e9128-image.png aa2c5edf-629f-45a3-8083-6f3dece48e05-image.png

    1 Reply Last reply
    0
    • CrilleC Offline
      CrilleC Offline
      Crille
      wrote on last edited by
      #2

      What does the rest of the config look like in logging.yaml. Any level above 4?

      3 1 Reply Last reply
      0
      • 3 Offline
        3 Offline
        3rdStng
        wrote on last edited by 3rdStng
        #3

        My Rule and Engine levels are at 5. But I've never touched them personally. Maybe these are inherited from a build long ago? Should these be a 4?

        ---
        logging:
          default:
            level: 4
            streams:
              - type: console
                level: 0
              - type: file
                name: "reactor.log"
                maxsize: 3  # megabytes max size
                keep: 9     # copies of old logs
                #
                # capture_console: if true, (most) console output will be captured to
                #                  this stream (if you have multiple streams, this
                #                  feature can only be used by ONE of them). If you
                #                  turn this on (true), set the "console" type stream
                #                  (above) log level to 0 to avoid duplicate logging
                #                  entries. The default is false, console not captured.
                #capture_console: true
          app:
            level: 4
          httpapi:
            level: 4
          httpproxy:
            level: 4
          wsapi:
            level: 4
          Structure:
            level: 4
          Controller:
            level: 4
          OWMWeatherController:
            level: 4
          VeraController:
            level: 4
          HubitatController:
            level: 4
          HassController:
            level: 4
          Rule:
            level: 5
          Engine:
            level: 5
        
        1 Reply Last reply
        0
        • 3 Offline
          3 Offline
          3rdStng
          wrote on last edited by
          #4

          Lowering these two down to a 4 do not appear to have any change on the speed of the log rotation

          1 Reply Last reply
          0
          • CrilleC Offline
            CrilleC Offline
            Crille
            wrote on last edited by
            #5

            Did you restart Reactor after changing the levels?

            1 Reply Last reply
            0
            • CrilleC Crille

              What does the rest of the config look like in logging.yaml. Any level above 4?

              3 Offline
              3 Offline
              3rdStng
              wrote on last edited by
              #6

              @Crille Yes

              1 Reply Last reply
              0
              • CrilleC Offline
                CrilleC Offline
                Crille
                wrote on last edited by Crille
                #7

                OK, any hints in the log? Anything other than Rule:INFO? If not, do you have a lot of rules triggered by frequent entity updates? I've moved my most frequent entities triggering rules to global expressions resulting in true/false, and used the expression as trigger instead to lower log entries of rule evaluation every 5-10 seconds so my 5, 2MB kept logs, span from late morning to early evening. 9, 3MB in 45 minutes doesn't seem normal to me.
                I have all my loglevels at 4.

                Edit: "doesn't seem normal to me."
                If the devices triggering the rules are extremely chatty, the amount of logging is of course "normal".

                1 Reply Last reply
                0
                • 3 Offline
                  3 Offline
                  3rdStng
                  wrote on last edited by 3rdStng
                  #8

                  It does appear to mostly be related to rules that have to do with my Life360 presence sensors.

                  Correction to my log level comment above. Changing the rules and engine to 4 did slow things down a bit. I saved that changed and restarted my docker at 7:43 AM. I'm just shy of 2 hours now to fill/rotate all 9 logs.

                  8dc3f4f2-fed1-4190-8ca0-621319c679e2-image.png

                  3 1 Reply Last reply
                  0
                  • 3 3rdStng

                    It does appear to mostly be related to rules that have to do with my Life360 presence sensors.

                    Correction to my log level comment above. Changing the rules and engine to 4 did slow things down a bit. I saved that changed and restarted my docker at 7:43 AM. I'm just shy of 2 hours now to fill/rotate all 9 logs.

                    8dc3f4f2-fed1-4190-8ca0-621319c679e2-image.png

                    3 Offline
                    3 Offline
                    3rdStng
                    wrote on last edited by 3rdStng
                    #9

                    If I am understanding your global expressions correctly. Are you saying you moved your rule triggers to an expression and then changed the trigger to be the value of the expression?

                    Original rule checking presence:
                    34669be2-3f5d-427c-bb86-3c0d038ebd78-image.png

                    Now as a global expression:
                    1a1cad53-bbf2-4226-8482-4d71f7c5b155-image.png

                    With an updated trigger:
                    cedde33e-4ce2-4139-8a24-24b3a42d7046-image.png

                    When Life360 updates, won't it force the expression to revalidate its value? Are these not logged?

                    1 Reply Last reply
                    0
                    • CrilleC Offline
                      CrilleC Offline
                      Crille
                      wrote on last edited by
                      #10

                      Yes, that's how I do it. The expressions are evaluated every time the Life360 updates but if the result of the expression doesn't change, the rule will not trigger an evaluation. Evaluation of global expressions is not logged, at least not at level 4.

                      1 Reply Last reply
                      1
                      • 3 Offline
                        3 Offline
                        3rdStng
                        wrote on last edited by
                        #11

                        Thank you. I changed all my rules that had a presence sensor written in them. As well as a few other rules that have an app that phones home every minute. Just restarted MSR for good measure and can see a different. I'm over 30 minutes right now between .log and .log.1.

                        1 Reply Last reply
                        1
                        • toggledbitsT Away
                          toggledbitsT Away
                          toggledbits
                          wrote on last edited by toggledbits
                          #12

                          Note that you can also set the logging level for rules to level 3, and it would eliminate all of the log entries for when evaluations are being triggered and what is triggering them.

                          Another option is to set the log level for specific rules to a lower (quieter) value. You need to know the rule ID, which is displayed when you open the rule detail panel on the Rule Sets page (click the right-pointing arrow next to the rule name to open the panel; the ID is at the bottom of the panel).

                            Rule:  # log level for all rules
                              level: 4
                            # Override default Rule log level for a specific rule
                            "Rule#rule-la04ghp7":  # note quotes must be used here
                              level: 3
                          

                          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                          3 1 Reply Last reply
                          1
                          • toggledbitsT toggledbits

                            Note that you can also set the logging level for rules to level 3, and it would eliminate all of the log entries for when evaluations are being triggered and what is triggering them.

                            Another option is to set the log level for specific rules to a lower (quieter) value. You need to know the rule ID, which is displayed when you open the rule detail panel on the Rule Sets page (click the right-pointing arrow next to the rule name to open the panel; the ID is at the bottom of the panel).

                              Rule:  # log level for all rules
                                level: 4
                              # Override default Rule log level for a specific rule
                              "Rule#rule-la04ghp7":  # note quotes must be used here
                                level: 3
                            
                            3 Offline
                            3 Offline
                            3rdStng
                            wrote on last edited by
                            #13

                            @toggledbits Awesome. Thank you.

                            I know you know, but for others, the rule ID is also noted in the logs. Makes it easier to copy and paste without having to look up the ID within the GUI.
                            f5fc7a07-2b33-4574-b3ec-d2dca45c70f6-image.png

                            1 Reply Last reply
                            0
                            • toggledbitsT toggledbits locked this topic on
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            Recent Topics

                            • Gradually turn on lights.
                              G
                              gwp1
                              0
                              4
                              144

                            • Stop the MSR by an external switch on Hubitat.
                              wmarcolinW
                              wmarcolin
                              0
                              1
                              38

                            • Error After Upgrade
                              G
                              gwp1
                              0
                              4
                              106

                            • Reset attribute value of entity in event handler
                              R
                              RHCPNG
                              0
                              5
                              209

                            • Need help figuring out how to delay a reset on reaction
                              G
                              gwp1
                              0
                              22
                              931

                            • Way to search for rules (rule state) in other rules
                              T
                              tamorgen
                              0
                              3
                              104

                            • Links to MSR from HA
                              Tom_DT
                              Tom_D
                              0
                              1
                              93

                            • Set Reaction > Script Action
                              wmarcolinW
                              wmarcolin
                              0
                              11
                              439

                            • Wiring Samotech SM308-S into light fitting
                              akbooerA
                              akbooer
                              0
                              2
                              152

                            • Errors after updating to MQTTController build 25139
                              toggledbitsT
                              toggledbits
                              0
                              6
                              242

                            • 🎉 My very first MSR controller: OpenSprinkler
                              therealdbT
                              therealdb
                              5
                              13
                              920

                            • Advice reqeusted to migrate MSR from Bare Metal to Container
                              T
                              tamorgen
                              0
                              5
                              264
                            Powered by NodeBB | Contributors
                            Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • Unsolved