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. Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
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

Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]

Scheduled Pinned Locked Moved Multi-System Reactor
12 Posts 5 Posters 979 Views 5 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

    I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.

    For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.

    toggledbitsT 1 Reply Last reply
    0
    • 3 3rdStng

      I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.

      For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.

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

      @3rdStng said in Feature Request - Wait for an event/trigger within Reaction:

      I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on.

      A Repeat...While group will execute and prevent the remainder of the Reaction from running until it breaks (conditions are no longer met).

      e520a1f9-7084-41c4-9aef-1ec834a068ff-image.png

      The delay prevents it from becoming a huge CPU consumer.

      Yes, this is a bit of a kludge, and a dedicated action could be more useful. I'll look into it, but in the meanwhile, this workaround should play nicely.

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

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

        Hmm.... Thanks for this, I think I can make it work, but it may take two Repeat While actions. It doesn't appear that I can wait for a change. It's only waiting for a True or False and not a change from Opened to Closed.

        I believe in my rule I would need a "Repeat While the door is false" (open) to wait for someone to actually open the door. Then a "Repeat While the door is true" (closed) to wait for them to close the door and then continuing on the actions to turn off the lights.

        1 Reply Last reply
        0
        • PablaP Offline
          PablaP Offline
          Pabla
          wrote on last edited by
          #4

          You read my mind! I have been wanting a "wait for" action in MSR for a while now never got around to making a post for it. I would want it to closely match the implementation made in HA for the "wait for trigger" action

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

            Well, really if it's just as simple as turning on the lights when the door opens, and then waiting for a close to turn them off, the rule trigger conditions should handle detecting the door opening, and the first action in the Set reaction would be to turn the lights on. Then you can wait for the door to close, and turn the lights off.

            But then, if the rule triggers are only detecting if the door is open, why not have the Set reaction turn the lights on, and the Reset reaction turn the lights off? No "wait for" needed at all, because the logic is handling it.

            As you disclose details, it's beginning to look like you've imagined a solution based on some other product, and you're trying to get Reactor to work its way, instead of doing it "the Reactor way."

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

            3 PablaP 2 Replies Last reply
            0
            • toggledbitsT toggledbits

              Well, really if it's just as simple as turning on the lights when the door opens, and then waiting for a close to turn them off, the rule trigger conditions should handle detecting the door opening, and the first action in the Set reaction would be to turn the lights on. Then you can wait for the door to close, and turn the lights off.

              But then, if the rule triggers are only detecting if the door is open, why not have the Set reaction turn the lights on, and the Reset reaction turn the lights off? No "wait for" needed at all, because the logic is handling it.

              As you disclose details, it's beginning to look like you've imagined a solution based on some other product, and you're trying to get Reactor to work its way, instead of doing it "the Reactor way."

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

              @toggledbits said in Feature Request - Wait for an event/trigger within Reaction:

              As you disclose details, it's beginning to look like you've imagined a solution based on some other product, and you're trying to get Reactor to work its way, instead of doing it "the Reactor way."

              That is very possible. I'm still mentally mapping this out too. And I 100% know that an image of my rule set would really help clear things up. I'm not in a position to get a screenshot at the moment. I'll try to put my thoughts in to text. (scary)

              Rule set as of today:
              Triggers:
              After midnight AND
              Before sunrise AND
              Any Presence Sensor in the group changes from Not Present to Present

              Actions:
              Turn on the porch light
              Turn on the driveway lights
              Wait for a random period of time between 10-15 minutes
              Turn off the porch light
              Turn off the driveway lights

              What I am after is within the Actions only. The Triggers are still the same.

              Actions:
              Turn on the porch light
              Turn on the driveway lights
              Wait until the HE Hub variable "lastDoorLockEvent" reports "Manually locked"
              Wait for a random period of time between 10-15 minutes
              Turn off the porch light
              Turn off the driveway lights

              The waiting until the hub variable is what's potentially causing the issue. When I go to bed, and assuming the door was open, I'll close it and lock it. So the hub variable now reports "Manually locked". If someone arrives after midnight and before sunrise, the variable will still report "Manually locked" since the lock status hasn't changed yet. So theoretically MSR won't wait since it already sees the variable as what it is looking for.

              And as I type this out, I suppose I could insert a set variable into the actions. I honestly haven't looked yet, but can MSR set a variable that is local to the hub only? Not within MSR.

              Actions:
              Turn on the porch light
              Turn on the driveway lights
              Set HE Hub variable "lastDoorLockEvent" to "waiting entry"
              Repeat Until the HE Hub variable "lastDoorLockEvent" reports "Manually locked"
              Wait for a random period of time between 10-15 minutes
              Turn off the porch light
              Turn off the driveway lights

              The entire concept stems from Hubitat's Rule Machine's "Wait for event" that you can define in a rule. I have a couple of these at my remote HE, where I can't run MSR easily.

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

                OK. This makes it much more clear. Your solution is workable. There are a few ways to attack it, but what you've posted should work. You picked up on the state of the hub variable, which is important. You hub variable should appear as an entity with the string_sensor capability, and it should have an extended action (x_hubitat_Variable.setVariable) to let you change the value.

                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
                0
                • toggledbitsT toggledbits

                  OK. This makes it much more clear. Your solution is workable. There are a few ways to attack it, but what you've posted should work. You picked up on the state of the hub variable, which is important. You hub variable should appear as an entity with the string_sensor capability, and it should have an extended action (x_hubitat_Variable.setVariable) to let you change the value.

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

                  @toggledbits said in Feature Request - Wait for an event/trigger within Reaction:

                  hub variable should appear as an entity with the string_sensor capability, and it should have an extended action (x_hubitat_Variable.setVariable) to let you change the value.

                  Worked perfectly!

                  Thank you for the feedback and allowing me to type out my thoughts to refine this rule.

                  1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Well, really if it's just as simple as turning on the lights when the door opens, and then waiting for a close to turn them off, the rule trigger conditions should handle detecting the door opening, and the first action in the Set reaction would be to turn the lights on. Then you can wait for the door to close, and turn the lights off.

                    But then, if the rule triggers are only detecting if the door is open, why not have the Set reaction turn the lights on, and the Reset reaction turn the lights off? No "wait for" needed at all, because the logic is handling it.

                    As you disclose details, it's beginning to look like you've imagined a solution based on some other product, and you're trying to get Reactor to work its way, instead of doing it "the Reactor way."

                    PablaP Offline
                    PablaP Offline
                    Pabla
                    wrote on last edited by
                    #9

                    @toggledbits One case I can think of where this is useful is as follows. Note I try to avoid making multiple rules to achieve this since it make managing them much harder.

                    I have some triggers (not relevant in this example) for my front doorbell when a person, vehicle, animal or package is detected. Each of these have their own respective rule. In the actions I have TTS action that says "{object name} detected at the front door". I also have another action after that send a notification to my phone with a snapshot and description of the doorbell activity.

                    The problem I run into, is that on occasion the snapshot takes a few extra seconds to come through. Now in my case I want the TTS to say what's at the door right away regardless of the snapshot since its irrelevant and then wait till the snapshot updates to send the push notification.

                    To combat the delay I added a condition in my triggers that wait for the snapshot time to update before sending the TTS and notification. Using this workaround it introduces a delay in the TTS action as well. Ideally having a "wait for" action for when the snapshot updates to then send the notification will fix the problem without needing to create another rule.

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

                      Refined my actions to include a timeout, just in case someone comes home, but they leave without entering the door.

                      Actions:
                      Set variable 'lastLockEvent' to "pending entry"
                      Turn on porch light
                      Turn on driveway lights
                      Repeat While:
                      -- Triggers:
                      -- [lastLockEvent] contains "manually locked"
                      -- [OR]
                      -- [lastLockEvent] contains "pending entry" (condition sustained for 20 minutes)
                      -- Actions:
                      -- Delay 10 seconds
                      Delay random between 1 to 5 minutes
                      Turn off porch light
                      Turn off driveway lights

                      1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        @3rdStng said in Feature Request - Wait for an event/trigger within Reaction:

                        I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on.

                        A Repeat...While group will execute and prevent the remainder of the Reaction from running until it breaks (conditions are no longer met).

                        e520a1f9-7084-41c4-9aef-1ec834a068ff-image.png

                        The delay prevents it from becoming a huge CPU consumer.

                        Yes, this is a bit of a kludge, and a dedicated action could be more useful. I'll look into it, but in the meanwhile, this workaround should play nicely.

                        tunnusT Offline
                        tunnusT Offline
                        tunnus
                        wrote on last edited by tunnus
                        #11

                        @toggledbits just an idea related to this "repeat...while" group that it could benefit from similar functionality as is available for pulse to prevent it from looping indefinitely. There are sometimes devices not updating their status properly and in those cases it would be nice to ensure exit within reasonable time.

                        This functionality can be done in a following way, for example, but would be more straightforward if it was already built-in

                        Screenshot 2024-08-07 at 21.53.46.png

                        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                        1 Reply Last reply
                        1
                        • therealdbT Offline
                          therealdbT Offline
                          therealdb
                          wrote on last edited by
                          #12

                          For me a "for/foreach" could be useful as well, when dealing with multiple devices and the same actions. Now this part is all code.

                          --
                          On a mission to automate everything.

                          My MS Reactor contrib
                          My Luup Plug-ins

                          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
                            147

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

                          • Error After Upgrade
                            G
                            gwp1
                            0
                            4
                            106

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

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

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

                          • Links to MSR from HA
                            Tom_DT
                            Tom_D
                            0
                            1
                            95

                          • Set Reaction > Script Action
                            wmarcolinW
                            wmarcolin
                            0
                            11
                            443

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

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

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

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