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. Reset Rule
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

Reset Rule

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 3 Posters 2.2k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    Hi @toggledbits !!

    A query, we have the possibility in the Set Reaction to run a Run Reaction and a Stop Reaction. Is it possible some way something like the Reset Rule that you have in the rules panel?

    01177be0-a33e-434f-a061-90d3a28b3018-image.png

    Explain better, in the rule below the Motion Rule group is already armed, because the devices have already fulfilled the rule and the estimated time of 900 secs has elapsed.

    ee9f6f77-6b6d-4b7e-99bf-1aa25ab9b35f-image.png

    What I want to do with the Reset Rule, is to reset this counter.

    Thanks!

    PablaP 1 Reply Last reply
    0
    • wmarcolinW wmarcolin

      Hi @toggledbits !!

      A query, we have the possibility in the Set Reaction to run a Run Reaction and a Stop Reaction. Is it possible some way something like the Reset Rule that you have in the rules panel?

      01177be0-a33e-434f-a061-90d3a28b3018-image.png

      Explain better, in the rule below the Motion Rule group is already armed, because the devices have already fulfilled the rule and the estimated time of 900 secs has elapsed.

      ee9f6f77-6b6d-4b7e-99bf-1aa25ab9b35f-image.png

      What I want to do with the Reset Rule, is to reset this counter.

      Thanks!

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

      @wmarcolin you could set the motion sensor to ‘pulse’ for 900 seconds. That will reset every time the 900 seconds lapses, however the only caveat is that once the pulse starts and say the motion sensor detects motion again the pulse won’t reset until the 900 seconds is over.

      wmarcolinW 1 Reply Last reply
      0
      • PablaP Pabla

        @wmarcolin you could set the motion sensor to ‘pulse’ for 900 seconds. That will reset every time the 900 seconds lapses, however the only caveat is that once the pulse starts and say the motion sensor detects motion again the pulse won’t reset until the 900 seconds is over.

        wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #3

        @pabla

        Pulse doesn't solve it, the goal is to be able to reset (restart the count) on a command from another rule.

        Thanks.

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

          Why do you want to reset the counter? Under what conditions would you do that?

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

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Why do you want to reset the counter? Under what conditions would you do that?

            wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits

            Ok, use case.

            The rule above is to turn off the air conditioning when there is no motion or presence in the room or when my wife and I are not at home, it is not possible to turn on the air conditioning in our bedroom.

            The conditions:

            • Condition 1) HouseMODE must be on Day or Evening. I will add Night once the human presence sensor (FP1) works properly (another story I will tell later);
            • Condition 2) AC Master On/Off, i.e., the air must be on for 5 minutes. This is to avoid turning off the AC by mistake;
            • Condition 3) Motion Set, in my suite, I have motion sensors in the bedroom, bathroom, and closed room, besides a human presence sensor (still being activated);
            • OR Condition 4) If I or my wife are not home, it will turn off the AC, even if there are other occupants in the room generating motion.

            What is happening?

            When I turn on the air conditioner on my way home (an example) to cool the room, conditions 3 and 4 are already TRUE, i.e., I have 5 minutes to be in the range of condition 4, and already have movement in the room for condition 3, to not turn off the A/C.

            Or even if I am inside the house, conditions 3 TRUE and 4 FALSE, I turn on the air to cool the room. I have 5 minutes (condition 2) to generate movement in the room. If not by condition 3, the air is already turned off because it is TRUE.

            This last example is a real situation. I had an accident, I am using crutches and to climb the stairs takes me more than 5 minutes. I can't turn ON the A/C, if I am at the basement of the house, when I get to the room the air is already off.

            So the goal is to reset the counters when I turn on the air conditioning, to have, in my real example 15 minutes to get into the room generating a movement. Or in the first example 10 minutes to be in range of the house, and 15 to generate motion/presence.

            As I explained before, this is not the case when using pulse, because the rule works correctly when passing times, and does not have to be restarted automatically. Either it becomes false by meeting conditions 3 and 4, or in the case I am requesting a reset generated by another rule.

            So I thought, if we have conditions to trigger or stop an action, I thought about the possibility of resetting it, since the situation exists, we would have to increment the command to the Set Reaction.

            Thanks.

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

              OK, if I understand your objective correctly, I would simply include in my logic that the AC cannot be turned off it is has been on for less than 15 minutes. This would also serve to prevent short-cycling of the compressor (something near and dear to my heart; where I control AC, I also have timers to keep it from being turned on within five minutes of turning off).

              There isn't a way to reset the sustained-for or delay-reset timers other than conditions themselves. That's by design. If the above doesn't seem like a workable alternative, I suggest adding a virtual switch to the logic, and when you want to reset the timer, toggle the switch off and back on. That feels a little "crafty" to me, though. I'd focus on the former suggestion, if it was my logic, because what ever controls that virtual switch, is probably just the logic that should be within the condition group itself.

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

              wmarcolinW 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                OK, if I understand your objective correctly, I would simply include in my logic that the AC cannot be turned off it is has been on for less than 15 minutes. This would also serve to prevent short-cycling of the compressor (something near and dear to my heart; where I control AC, I also have timers to keep it from being turned on within five minutes of turning off).

                There isn't a way to reset the sustained-for or delay-reset timers other than conditions themselves. That's by design. If the above doesn't seem like a workable alternative, I suggest adding a virtual switch to the logic, and when you want to reset the timer, toggle the switch off and back on. That feels a little "crafty" to me, though. I'd focus on the former suggestion, if it was my logic, because what ever controls that virtual switch, is probably just the logic that should be within the condition group itself.

                wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by
                #7

                @toggledbits

                Master, thanks for making me think a little 🙂

                Well, I changed the logic a little. I unified the times - before, I had 3 timers, but now I will unify only one, and I think I will not damage to the goal of not keeping the air on in case of no presence in the environment. I already have in another rule the block to always have an interval of 5 minutes between turning on and off the A/C.

                9d3f45ad-4943-4d32-b3ce-25f2b69ffb96-image.png

                Well, if I may ask, one more item for that endless wish list; just like we have Run Reacton and Stop Reacton, maybe we should have Reset Reaction 🙂

                Thanks!

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

                  Well... reactions aren't stateful objects, they are just lists of actions, so you don't reset them. That wouldn't mean anything.

                  If you mean rules... no. I give you guys plenty of rope to hang yourselves with. There are ways to get done what you need to do, I think, within the current structure of features. If I'm being completely forthcoming, giving you this "grenade without a pin" feature would encourage bad logic design, creating more odd problems that you will then ask for my assistance in troubleshooting, and my efforts will be met with hours of puzzling and frustration until the inevitable "oh wait... there's this other rule I completely forgot about that comes out of left field and resets this one" disclosure.

                  Nope. It's not going to happen. That's a hill I am willing to die on. 🙂

                  P.S. I view the similar/related request to enable/disable rules by reaction/action with the same reasoning, same outcome.

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

                  wmarcolinW 1 Reply Last reply
                  1
                  • toggledbitsT toggledbits

                    Well... reactions aren't stateful objects, they are just lists of actions, so you don't reset them. That wouldn't mean anything.

                    If you mean rules... no. I give you guys plenty of rope to hang yourselves with. There are ways to get done what you need to do, I think, within the current structure of features. If I'm being completely forthcoming, giving you this "grenade without a pin" feature would encourage bad logic design, creating more odd problems that you will then ask for my assistance in troubleshooting, and my efforts will be met with hours of puzzling and frustration until the inevitable "oh wait... there's this other rule I completely forgot about that comes out of left field and resets this one" disclosure.

                    Nope. It's not going to happen. That's a hill I am willing to die on. 🙂

                    P.S. I view the similar/related request to enable/disable rules by reaction/action with the same reasoning, same outcome.

                    wmarcolinW Offline
                    wmarcolinW Offline
                    wmarcolin
                    wrote on last edited by
                    #9

                    @toggledbits

                    870ce073-27c0-42f9-996d-3bc8e7c43e29-image.png

                    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

                    • Arming Envisalink panel from MSR
                      T
                      tamorgen
                      0
                      7
                      213

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

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

                    • DynamicGroupController and attributes
                      therealdbT
                      therealdb
                      1
                      5
                      137

                    • Upgrade Issues
                      T
                      tbully
                      0
                      9
                      256

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

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

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

                    • Logon screen timeout
                      G
                      gwp1
                      0
                      5
                      203

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

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