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
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
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
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
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 1.9k 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.5.1.142
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HAOS
    Core 2026.7.4
    w/ HA Connect ZWA-2
    FW: v1.1
    SDK: v7.23.1

    *Prod MSR in docker/portainer
    MSR: latest-26193-8dd8f854
    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.5.1.142
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HAOS
      Core 2026.7.4
      w/ HA Connect ZWA-2
      FW: v1.1
      SDK: v7.23.1

      *Prod MSR in docker/portainer
      MSR: latest-26193-8dd8f854
      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.5.1.142
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HAOS
          Core 2026.7.4
          w/ HA Connect ZWA-2
          FW: v1.1
          SDK: v7.23.1

          *Prod MSR in docker/portainer
          MSR: latest-26193-8dd8f854
          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.5.1.142
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HAOS
              Core 2026.7.4
              w/ HA Connect ZWA-2
              FW: v1.1
              SDK: v7.23.1

              *Prod MSR in docker/portainer
              MSR: latest-26193-8dd8f854
              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.5.1.142
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HAOS
                  Core 2026.7.4
                  w/ HA Connect ZWA-2
                  FW: v1.1
                  SDK: v7.23.1

                  *Prod MSR in docker/portainer
                  MSR: latest-26193-8dd8f854
                  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.5.1.142
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HAOS
                      Core 2026.7.4
                      w/ HA Connect ZWA-2
                      FW: v1.1
                      SDK: v7.23.1

                      *Prod MSR in docker/portainer
                      MSR: latest-26193-8dd8f854
                      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

                      • Arming Envisalink panel from MSR
                        T
                        tamorgen
                        0
                        7
                        206

                      • [Solved] DynamicGroupController updating members issue
                        CrilleC
                        Crille
                        0
                        5
                        145

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        148
                        130.9k

                      • DynamicGroupController and attributes
                        therealdbT
                        therealdb
                        1
                        5
                        136

                      • Upgrade Issues
                        T
                        tbully
                        0
                        9
                        252

                      • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                        toggledbitsT
                        toggledbits
                        0
                        10
                        275

                      • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                        G
                        gwp1
                        0
                        5
                        152

                      • openLuup console disappeared - 500 - Internal Server Error
                        A
                        a-lurker
                        0
                        2
                        181

                      • Logon screen timeout
                        G
                        gwp1
                        0
                        5
                        200

                      • [MSR] Copy&past of actions and/or drag&drop between set/reset
                        toggledbitsT
                        toggledbits
                        0
                        9
                        391

                      • Upgrade advice - upgrade from aarch64 to ARM64 image
                        toggledbitsT
                        toggledbits
                        0
                        4
                        226
                      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