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. sunset/sunrise question in 22251
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
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
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
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
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
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
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

sunset/sunrise question in 22251

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 2 Posters 1.5k 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #2

    In your Day rule, you have "before sunset" as a condition. That means the test will be true from midnight to sunset, false from sunset to midnight, and then go back to true at midnight, every day. Is that consistent with your intentions? IMO, Day isn't day until after sunrise (i.e. the period between midnight and sunrise isn't Day, it's part of Night to my thinking).

    Oh, and in Evening, your two conditions "after sunset" OR "before sunrise" can be written as a single condition "between sunset and sunrise".

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

    G 1 Reply Last reply
    0
    • toggledbitsT toggledbits

      In your Day rule, you have "before sunset" as a condition. That means the test will be true from midnight to sunset, false from sunset to midnight, and then go back to true at midnight, every day. Is that consistent with your intentions? IMO, Day isn't day until after sunrise (i.e. the period between midnight and sunrise isn't Day, it's part of Night to my thinking).

      Oh, and in Evening, your two conditions "after sunset" OR "before sunrise" can be written as a single condition "between sunset and sunrise".

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

      @toggledbits For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

      Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

      *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

      toggledbitsT 1 Reply Last reply
      0
      • G gwp1

        @toggledbits For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

        Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

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

        @gwp1 said in sunset/sunrise question in 22251:

        For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

        I can't really answer this, not knowing enough about your rules and how Alarm Times works. I'll leave it to your experimentation, I just wanted to point out that there's a significant number of hours that may not comport with your intentions.

        @gwp1 said in sunset/sunrise question in 22251:

        Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

        Very important feature that it handles midnight crossing correctly on all time conditions.

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

        G 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @gwp1 said in sunset/sunrise question in 22251:

          For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

          I can't really answer this, not knowing enough about your rules and how Alarm Times works. I'll leave it to your experimentation, I just wanted to point out that there's a significant number of hours that may not comport with your intentions.

          @gwp1 said in sunset/sunrise question in 22251:

          Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

          Very important feature that it handles midnight crossing correctly on all time conditions.

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

          @toggledbits Ok, this has surfaced the potential bug I referenced in my OP.

          I'm attempting to edit the Evening ruleset to change to "between sunset and sunrise". I add the trigger:

          f76a4cf3-e4f6-44e5-a789-ae1bbc8af895-image.png

          I click save and exit

          989272a0-82d7-4649-b2d2-0b6cd0020371-image.png

          Rule shows as SET

          747c65be-40ba-4841-89cc-fb5f640e6b4f-image.png

          The trigger has changed to "from sunrise to sunset"

          c84953eb-6df0-41d2-9413-973c372d75f7-image.png

          And now my system is fighting over Day vs Evening.

          EDIT:
          Further, editing the trigger does not prompt for save - it's as though the change in the trigger isn't seen.

          c1f417a4-5caa-44be-9ffa-1573d7d09a81-image.png

          12afa669-34ed-4f82-b76f-837f18966755-image.png

          Further testing... adding a new trigger of "after sunset" and clicking save switches to "after sunrise".

          *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

          G 1 Reply Last reply
          0
          • G gwp1

            @toggledbits Ok, this has surfaced the potential bug I referenced in my OP.

            I'm attempting to edit the Evening ruleset to change to "between sunset and sunrise". I add the trigger:

            f76a4cf3-e4f6-44e5-a789-ae1bbc8af895-image.png

            I click save and exit

            989272a0-82d7-4649-b2d2-0b6cd0020371-image.png

            Rule shows as SET

            747c65be-40ba-4841-89cc-fb5f640e6b4f-image.png

            The trigger has changed to "from sunrise to sunset"

            c84953eb-6df0-41d2-9413-973c372d75f7-image.png

            And now my system is fighting over Day vs Evening.

            EDIT:
            Further, editing the trigger does not prompt for save - it's as though the change in the trigger isn't seen.

            c1f417a4-5caa-44be-9ffa-1573d7d09a81-image.png

            12afa669-34ed-4f82-b76f-837f18966755-image.png

            Further testing... adding a new trigger of "after sunset" and clicking save switches to "after sunrise".

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

            Opened a bug on this issue.

            *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
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #7

              OK. I would have liked to see a bit more concise description in that OP (e.g. "sunrise/sunset selections not saving when edited"), but found and fixed. Another thing you might have observed is when you changed those menus to sunset first and sunrise second, you didn't get the green bar on the left of the condition, indicating that it had been changed.

              I'll do a build later today with the fix. In the meanwhile, you can work around it by changing the sunrise/sunset start and end to what you want, then edit the offset to something and then re-edit and put it back to 0 (or whatever you want). You should get a green bar on the left side of the condition when you do that.

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

              G 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                OK. I would have liked to see a bit more concise description in that OP (e.g. "sunrise/sunset selections not saving when edited"), but found and fixed. Another thing you might have observed is when you changed those menus to sunset first and sunrise second, you didn't get the green bar on the left of the condition, indicating that it had been changed.

                I'll do a build later today with the fix. In the meanwhile, you can work around it by changing the sunrise/sunset start and end to what you want, then edit the offset to something and then re-edit and put it back to 0 (or whatever you want). You should get a green bar on the left side of the condition when you do that.

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

                @toggledbits My screenshots were a step-by-step thru the issue. "I click save and exit "does show that there is no green bar next to the edited trigger.

                *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

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

                  Yes, I could see that. I was referring to the OP, which you also made reference to. Fixed now. Build coming later.

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

                  G 1 Reply Last reply
                  1
                  • G gwp1

                    @toggledbits My screenshots were a step-by-step thru the issue. "I click save and exit "does show that there is no green bar next to the edited trigger.

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

                    Can confirm that adding a new trigger and changing to 1 minute after for each end of it is a successful workaround.

                    b951322c-265b-47d6-8a61-fa59dced6a89-image.png

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

                      Yes, I could see that. I was referring to the OP, which you also made reference to. Fixed now. Build coming later.

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

                      @toggledbits I wasn't sure at the time of the OP post that it was a legit bug and not just... me.

                      🙂

                      *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
                      • toggledbitsT toggledbits locked this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
                        N
                        noelab
                        0
                        8
                        76

                      • DynamicGroupController and attributes
                        toggledbitsT
                        toggledbits
                        1
                        9
                        247

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        149
                        135.6k

                      • Unofficial thread for compatibility
                        tunnusT
                        tunnus
                        2
                        2
                        714

                      • Ooops - Deleted Reactor Ex Machina II
                        toggledbitsT
                        toggledbits
                        0
                        2
                        64

                      • Bail out of failed reaction?
                        T
                        tamorgen
                        0
                        3
                        108

                      • Arming Envisalink panel from MSR
                        T
                        tamorgen
                        0
                        7
                        329

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

                      • Upgrade Issues
                        T
                        tbully
                        0
                        9
                        354

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

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

                      • openLuup console disappeared - 500 - Internal Server Error
                        A
                        a-lurker
                        0
                        2
                        252
                      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