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. Timers in my log
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

Timers in my log

Scheduled Pinned Locked Moved Multi-System Reactor
26 Posts 3 Posters 3.0k 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.
  • MatohlM Offline
    MatohlM Offline
    Matohl
    wrote on last edited by
    #4

    ... but I will check my logs again

    1 Reply Last reply
    0
    • MatohlM Offline
      MatohlM Offline
      Matohl
      wrote on last edited by
      #5

      Yes, still there

      1 Reply Last reply
      0
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #6

        OK. If it is 21058, please open a PR. Then stop Reactor, clear the log files (delete), and then start Reactor. Let it run for 15-20 seconds, and then stop it again. Gather the log file, compress, and email as attachment to the address in the Support section of the About tab.

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

        1 Reply Last reply
        0
        • MatohlM Offline
          MatohlM Offline
          Matohl
          wrote on last edited by
          #7

          Will do 🙂

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #8

            Oh, and can you screen shot a couple of those rules as well? If you click on the rule name in the Rule Sets tab, it will open rule status and show you the ID for the rule. Just match that up to two or three of logged rules.

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

            1 Reply Last reply
            0
            • MatohlM Offline
              MatohlM Offline
              Matohl
              wrote on last edited by Matohl
              #9

              Ok, I have reported it. Sent you an e-mail with the logs and left some screen shots in MBT. But every rule works fine but my logs ar flooded 🙂 You said that you left some "hooks" in the earlier problem with rules spanning over mid-night. Could it be related?

              toggledbitsT 1 Reply Last reply
              0
              • K Offline
                K Offline
                kfxo
                wrote on last edited by
                #10

                Im seeing the same as @Matohl . Let me know if you want me to supply some logs too.

                1 Reply Last reply
                0
                • MatohlM Matohl

                  Ok, I have reported it. Sent you an e-mail with the logs and left some screen shots in MBT. But every rule works fine but my logs ar flooded 🙂 You said that you left some "hooks" in the earlier problem with rules spanning over mid-night. Could it be related?

                  toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #11

                  @matohl No, I don't think it's related. There are some tricky side-effects with doing math with JavaScript dates, and I imagine something is running into a condition where it's hitting that. Everything the log says is correct, it's just not doing what it says it's going to do. It says it's going to sleep until a certain time, and then sleeps for no time at all, so I'm 99% its to do with the delay calculation in the timer object, which is as straight stupid simple as you can imagine it to be, and yet, not working, apparently, at least in some cases. And of course, I don't see it on mine. 😕

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

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

                    Can you also look and see if there's a console.log file in your logs directory, and if it has any messages, and especially, rolling error messages at the same pace as the timer messages?

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

                    1 Reply Last reply
                    0
                    • MatohlM Offline
                      MatohlM Offline
                      Matohl
                      wrote on last edited by
                      #13

                      On it ...

                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by toggledbits
                        #14

                        OK... in taking a second look at the logs, no two condition IDs are the same. You seem to use date/time conditions a lot?

                        So is this happening only when the Engine starts, or is it continuous in the logs?

                        Edit: FYI, these messages are at log level "always" from previous debugging, so I would expect a lot of them at engine startup, but once the engine starts, then really, it should quiet down to only when a timer expires and is rescheduled. And these may be the only messages you have. I guess I assumed they were rolling, but the log snippet you posted doesn't show that, so I need a better picture of when this is happening, and what's actually going on. I don't see email yet with the log file.

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

                        MatohlM 1 Reply Last reply
                        0
                        • MatohlM Offline
                          MatohlM Offline
                          Matohl
                          wrote on last edited by
                          #15

                          A really long file. Nope, no rolling error messages related to the timer messages. Should I send it?

                          1 Reply Last reply
                          0
                          • MatohlM Offline
                            MatohlM Offline
                            Matohl
                            wrote on last edited by
                            #16

                            To answer your question, it is continuous

                            1 Reply Last reply
                            0
                            • toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #17

                              OK I need that log file, then.

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

                              1 Reply Last reply
                              0
                              • MatohlM Offline
                                MatohlM Offline
                                Matohl
                                wrote on last edited by
                                #18

                                Ok. sent

                                1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  OK... in taking a second look at the logs, no two condition IDs are the same. You seem to use date/time conditions a lot?

                                  So is this happening only when the Engine starts, or is it continuous in the logs?

                                  Edit: FYI, these messages are at log level "always" from previous debugging, so I would expect a lot of them at engine startup, but once the engine starts, then really, it should quiet down to only when a timer expires and is rescheduled. And these may be the only messages you have. I guess I assumed they were rolling, but the log snippet you posted doesn't show that, so I need a better picture of when this is happening, and what's actually going on. I don't see email yet with the log file.

                                  MatohlM Offline
                                  MatohlM Offline
                                  Matohl
                                  wrote on last edited by
                                  #19

                                  @toggledbits said in Timers in my log:

                                  ... You seem to use date/time conditions a lot? ...
                                  I change it every room individually. With lights sensors, time and sunrise/sunset conditions.

                                  ... "or is it continuous in the logs?" ...
                                  Yes, it is continuous

                                  ... "it should quiet down to only when a timer expires and is rescheduled" ...
                                  I don't see that in the logs

                                  1 Reply Last reply
                                  0
                                  • MatohlM Offline
                                    MatohlM Offline
                                    Matohl
                                    wrote on last edited by Matohl
                                    #20

                                    "You seem to use date/time conditions a lot"
                                    I live in Sweden were light changes dramatically over the year and we have sun from the east and darkness in the west in the morning and the opposite in the evening. After a few seasons I realize I had to change it individually for each room. Works perfectly in MSR, I use a SSD to my Pi so if the log is large it could probably handle it 🙂 Due to this perhaps it is normal and I could move on but @kfxo signaled something similar.

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT Offline
                                      toggledbitsT Offline
                                      toggledbits
                                      wrote on last edited by toggledbits
                                      #21

                                      OK. Non-problem. Everything is fine. These are just debug messages from my previous investigation into scheduling of re-evaluations on time-based rules (PR #34 and 44 specifically). For that, I used the "always" log level (hence the "null" reported where the level goes in the logged messages). This is just normal start-up. When you start Reactor and it brings up the Engine, it reads all the rules, does an initial scan for dependencies, then evaluates all the conditions, which sets the timers for the next event based on current (post-startup) conditions. All is well.

                                      The logs do not show they are rolling. If you had a continuous stream of timer messages, that would be noteworthy, but getting a timer messages for every time condition in any rule is expected at start-up. If there were further timer messages at unexpected time, the logs provided don't show that.

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

                                      1 Reply Last reply
                                      0
                                      • MatohlM Offline
                                        MatohlM Offline
                                        Matohl
                                        wrote on last edited by
                                        #22

                                        No problems, everything is working well. I will check my logs in the coming days.

                                        1 Reply Last reply
                                        0
                                        • K Offline
                                          K Offline
                                          kfxo
                                          wrote on last edited by
                                          #23

                                          That actually makes perfect sense and upon further inspection I see that the timers I was noticing in the logs are with respect to one rule that I had recently turned on that resets often.

                                          1 Reply Last reply
                                          1
                                          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
                                            139

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            105

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            91

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            437

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

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

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

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            262
                                          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