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. [SOLVED] Sprinkler control: one or both of two conditions to prevent watering
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
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
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
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
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 customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
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

[SOLVED] Sprinkler control: one or both of two conditions to prevent watering

Scheduled Pinned Locked Moved Multi-System Reactor
solved
10 Posts 2 Posters 840 Views 2 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    I think I'm just staring at this too hard so I'm opening up to the collective.

    Scenario: water the gardens at XX time unless one or both of the following are TRUE:

    • More than .25" of rain has fallen yesterday (I have an entity for this)
    • It is currently raining (I have an entity for this)

    I had it set to OR and that (obviously) doesn't work because, whilst first bullet was TRUE second bullet was FALSE and so the water flowed.

    I'm thinking, atm, of something using Reaction>Group and building out something that isolates the conditions vs making them an OR.

    Am I on the right path here?

    *Hubitat C-7 2.4.3.123
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.9.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25264-2fbe9217
    MQTTController: 25139
    ZWave Controller: 25139

    1 Reply Last reply
    0
    • G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      In staring even harder I came up with this:

      Since image functionality is STILL BROKEN on this forum (but, oh, it LOOKS pretty)...

      Triggers not or
      Comment: This is a NOT rule. If either of these conditions are NOT true then this rule is FALSE. (If the rainfall total either yesterday or today is more than 1/4" then FALSE).


      Entity Attribute: Weatherflow Precipitation Yesterday (hass>sensor_weatherflow_precipitation_yesterday) value_sensor.value <= 0.25


      OR Entity Attribute: Weatherflow Precipitation Today (hass>sensor_weatherflow_precipitation_today) value_sensor.value <= 0.25

      Currently, there was 1.61" of rain yesterday so the outcome is false and there has been no rain today so that outcome is true - as such the ruleset is rendered false.

      Is my thinking sound here?

      *Hubitat C-7 2.4.3.123
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.9.4
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25264-2fbe9217
      MQTTController: 25139
      ZWave Controller: 25139

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

        So basically the way you have your rule structured right now is that the group will go true either when it rains more than 0.25" or its currently raining. Which is the opposite of what you'd want. As you mentioned in your recent post switching this to a not or operator should fix it. Meaning the group will be true if it hasn't rained more than 0.25" yesterday or is currently raining.

        G 1 Reply Last reply
        1
        • PablaP Pabla

          So basically the way you have your rule structured right now is that the group will go true either when it rains more than 0.25" or its currently raining. Which is the opposite of what you'd want. As you mentioned in your recent post switching this to a not or operator should fix it. Meaning the group will be true if it hasn't rained more than 0.25" yesterday or is currently raining.

          G Offline
          G Offline
          gwp1
          wrote on last edited by
          #4

          @Pabla Thanks!

          I altered the premise very slightly to be rain amounts on both days because, hey, it might be actually raining right then but it might be a very slight passing shower which doesn't end up providing the needed water amount.

          The updated version looks at amounts on both days, instead.

          *Hubitat C-7 2.4.3.123
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.9.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25264-2fbe9217
          MQTTController: 25139
          ZWave Controller: 25139

          PablaP 1 Reply Last reply
          0
          • G gwp1

            @Pabla Thanks!

            I altered the premise very slightly to be rain amounts on both days because, hey, it might be actually raining right then but it might be a very slight passing shower which doesn't end up providing the needed water amount.

            The updated version looks at amounts on both days, instead.

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

            @gwp1 Excellent! Regardless of condition the not operator should do the trick

            G 1 Reply Last reply
            0
            • PablaP Pabla

              @gwp1 Excellent! Regardless of condition the not operator should do the trick

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #6

              @Pabla Hmmm. We've had a sudden storm that has dropped 2" of rain today. As such both Conditions are now false and then ruleset has gone SET.

              SO... testing, when I flip the criteria of the Conditions to >= .25 both go true and the ruleset goes false.

              I did a quick test and, yes, it appears by bumping one of the two Conditions to be silly high like 5" (so today's actual is less than that) it makes one Condition true and one false and the ruleset remains as unset. Bumping both to be silly high (so both actuals are less than that) makes the ruleset toggle to SET which is the desired outcome. Any or both of the Conditions being TRUE toggles the ruleset unset. Both conditions being false toggles the ruleset TRUE.

              The expectation is that tomorrow morning there will be no flow of water as at least today's Condition is true so no matter what tomorrow's is (between midnight and 0600 ET) this ruleset will not SET.

              *Hubitat C-7 2.4.3.123
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.9.4
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25264-2fbe9217
              MQTTController: 25139
              ZWave Controller: 25139

              PablaP 1 Reply Last reply
              0
              • G gwp1

                @Pabla Hmmm. We've had a sudden storm that has dropped 2" of rain today. As such both Conditions are now false and then ruleset has gone SET.

                SO... testing, when I flip the criteria of the Conditions to >= .25 both go true and the ruleset goes false.

                I did a quick test and, yes, it appears by bumping one of the two Conditions to be silly high like 5" (so today's actual is less than that) it makes one Condition true and one false and the ruleset remains as unset. Bumping both to be silly high (so both actuals are less than that) makes the ruleset toggle to SET which is the desired outcome. Any or both of the Conditions being TRUE toggles the ruleset unset. Both conditions being false toggles the ruleset TRUE.

                The expectation is that tomorrow morning there will be no flow of water as at least today's Condition is true so no matter what tomorrow's is (between midnight and 0600 ET) this ruleset will not SET.

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

                @gwp1 I am not sure I am quite following. Are you saying that when both conditions: Rain amount yesterday and Rain amount today are true (meaning a certain amount of rain has fallen either yesterday or today) that the ruleset still goes true and waters the garden?

                G 1 Reply Last reply
                0
                • PablaP Pabla

                  @gwp1 I am not sure I am quite following. Are you saying that when both conditions: Rain amount yesterday and Rain amount today are true (meaning a certain amount of rain has fallen either yesterday or today) that the ruleset still goes true and waters the garden?

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by
                  #8

                  @Pabla

                  @gwp1 said in [SOLVED] Sprinkler control: one or both of two conditions to prevent watering:

                  Any or both of the Conditions being TRUE toggles the ruleset unset. Both conditions being false toggles the ruleset TRUE.

                  So the settings are as such now:


                  Triggers [not or]


                  Entity Attribute: Weatherflow Precipitation Yesterday (hass>sensor_weatherflow_precipitation_yesterday) value_sensor.value >= 0.25


                  OR Entity Attribute: Weatherflow Precipitation Today (hass>sensor_weatherflow_precipitation_today) value_sensor.value >= 0.25


                  Right now the first one is true and the second is false. As such, the rule is RESET. Unless we get rain between now and tomorrow morning, the "yesterday" will roll off and "today" will become "yesterday" and both Conditions will be be false and the rule will change to SET and the water will flow.

                  *Hubitat C-7 2.4.3.123
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.9.4
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25264-2fbe9217
                  MQTTController: 25139
                  ZWave Controller: 25139

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

                    Ah I see but isn't that what you'd expect? Say yesterday you got over 0.25 (inches?) of rain and today you got 0.23. This would mean your garden will not be watered.

                    Lets say no rain falls between today and tomorrow. That means when tomorrow rolls over yesterdays rain total now becomes 0.23 and todays is 0. Based on that info you'd want your garden to be watered.

                    To me the ruleset is working as intended, if you still wouldn't want it to water I would set your "todays" threshold a little lower.

                    G 1 Reply Last reply
                    0
                    • PablaP Pabla

                      Ah I see but isn't that what you'd expect? Say yesterday you got over 0.25 (inches?) of rain and today you got 0.23. This would mean your garden will not be watered.

                      Lets say no rain falls between today and tomorrow. That means when tomorrow rolls over yesterdays rain total now becomes 0.23 and todays is 0. Based on that info you'd want your garden to be watered.

                      To me the ruleset is working as intended, if you still wouldn't want it to water I would set your "todays" threshold a little lower.

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #10

                      @Pabla The original Conditions were <= .25 whereas the working version had to be flipped to >= .25. That's what ultimately made it work.

                      *Hubitat C-7 2.4.3.123
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.9.4
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25264-2fbe9217
                      MQTTController: 25139
                      ZWave Controller: 25139

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


                      Recent Topics

                      • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                        CrilleC
                        Crille
                        0
                        67
                        4.7k

                      • Shelly Wall Display XL
                        therealdbT
                        therealdb
                        2
                        6
                        72

                      • Handling Dead Entities and Renamed Entities
                        PablaP
                        Pabla
                        0
                        5
                        60

                      • Strange behavior for MQTT templates using payload and attributes
                        toggledbitsT
                        toggledbits
                        0
                        6
                        120

                      • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                        therealdbT
                        therealdb
                        1
                        46
                        8.1k

                      • HA 2025.9.4 Supported Yet?
                        toggledbitsT
                        toggledbits
                        0
                        2
                        82

                      • The reaction stopped working (Google Nest max playing a video)
                        toggledbitsT
                        toggledbits
                        0
                        7
                        346

                      • Rule Set UI bug - RESOLVED
                        toggledbitsT
                        toggledbits
                        1
                        2
                        226

                      • [Reactor] Copy&Paste of Rules
                        therealdbT
                        therealdb
                        0
                        1
                        299

                      • [Reactor] Help with screne controller cycling logic
                        toggledbitsT
                        toggledbits
                        0
                        5
                        400

                      • Stop the MSR by an external switch on Hubitat.
                        Tom_DT
                        Tom_D
                        0
                        6
                        715

                      • Expose MSR entities
                        CatmanV2C
                        CatmanV2
                        0
                        11
                        860
                      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