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. system capability zwave_scene_controller
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

system capability zwave_scene_controller

Scheduled Pinned Locked Moved Multi-System Reactor
46 Posts 5 Posters 18.0k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #33

    Yeah I hear what you are saying. I'll do that last test anyway a some point, be interesting to see actually what does happen with that sl_SceneActivated variable in Vera.

    Might be a few days, gonna take things easy for a while.

    1 Reply Last reply
    0
    • cw-kidC Offline
      cw-kidC Offline
      cw-kid
      wrote on last edited by
      #34

      That sl_SceneActivated variable does change OK for the Fibaro Dimmer 2 modules, as I said I have all those scene activations working and setup now in MSR.

      But for the Fibaro Roller Shutter 2 modules it only correctly changes that sl_SceneActivated variable for double clicks UP (S1).

      For double click down (S2) and triple click down (S2) it doesn't appear to be changing at all. Which is weird.

      I wonder what the Fibaro Relay Switch modules do also? I do have some of those, but I am not using them with scene activation. I saw in the vera devices .json you also had a mapping for the Fibaro Relay Switch modules.

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

        @cw-kid said in system capability zwave_scene_controller:

        I saw in the vera devices .json you also had a mapping for the Fibaro Relay Switch modules.

        Yes, but no mapping yet, so when you get around to it....

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

        1 Reply Last reply
        0
        • cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by cw-kid
          #36

          I've done the last test on these Fibaro Roller Shutter 2 modules.

          Its as I have said before. The sl_SceneActivated does not change value for S2 Double click or S2 Triple Click it remains as 0 in the Vera web GUI.

          f1982563-3711-469c-b112-0359bc204539-image.png

          This is S1 Double click this does change to 4.

          de568314-5166-4f41-b96d-5c5c9817fd01-image.png

          So there's no way this would of worked fully with MSR without also being able to see the Last_Scene_ID numbers.

          1 Reply Last reply
          0
          • cw-kidC Offline
            cw-kidC Offline
            cw-kid
            wrote on last edited by cw-kid
            #37

            In the new version of MSR this is what I see now:

            07d9c6b0-ed34-4f01-8a0f-98111f5ecd1a-image.png

            I think I am going to switch all my rules to use the last_scene_id instead as its these numbers that are in the fibaro user manuals for scene activation.

            b730373f-6e03-491f-a046-987dc2759df9-image.png

            aa62343b-938b-497b-82f5-e4bfa52310de-image.png

            I guess to reset the rule so I can repeat a double click I will have to reset the last_scene_id if possible ?

            Changing this:

            0de0166b-4b34-4ebd-b108-c6eb5a67e6bd-image.png

            To this:

            492e5df6-a535-4651-9393-46ba9394b7c4-image.png

            I will test it and see if it works.

            EDIT:

            Initial tests say everything is working as expected now using the lastsceneID numbers instead of sl_sceneactivated.

            Thank you very much for enabling this functionality in MSR.

            1 Reply Last reply
            1
            • LibraSunL Offline
              LibraSunL Offline
              LibraSun
              wrote on last edited by
              #38

              I can't wait to map all my Nodon battery-powered remote buttons to MSR routines once able. Mine can do single-, double- and long-press as well as the "release" action, netting me 16 possible actions. It even has an LED with programmable behavior (which I've never succeeded in altering; it just remains off).

              Have you noticed that controlling scenes with MSR is far faster than MFL on Vera?

              toggledbitsT 1 Reply Last reply
              0
              • LibraSunL LibraSun

                I can't wait to map all my Nodon battery-powered remote buttons to MSR routines once able. Mine can do single-, double- and long-press as well as the "release" action, netting me 16 possible actions. It even has an LED with programmable behavior (which I've never succeeded in altering; it just remains off).

                Have you noticed that controlling scenes with MSR is far faster than MFL on Vera?

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

                @librasun said in system capability zwave_scene_controller:

                Have you noticed that controlling scenes with MSR is far faster than MFL on Vera?

                I've noticed that everything is faster. They appear to have considerable overhead in setting up and calling plugin code when it needs to happen. Their job scheduling can also delay the plugin's response when the system is busy doing other things. Luup is trying to be very defensive around plugins, but that comes at a performance cost. They made similar decisions (not surprisingly) in the new firmware that I warned them about early on, in some ways worse. We'll see how that turns out. I've heard they've reversed themselves, but since I'm not playing with that stuff any more, I haven't confirmed it myself.

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

                1 Reply Last reply
                1
                • cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by
                  #40

                  I think these scene activations with my Fibaro modules are slower on MSR running on the Pi, than they were with PLEG running on Vera.

                  But that is to be expected I guess. I have about a 2 or 3 second delay after doing the clicks on the switch to when the action is run. Sometimes longer delays.

                  But its working which is the main thing.

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

                    Can you send me a log? I'd like to see if there's some obvious delay going on in MSR. And just to make sure, you're not using any condition options on the scene variable test, right?

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

                    1 Reply Last reply
                    0
                    • cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #42

                      I am not using any Constraints if that is what you mean.

                      Yes I can do some logs at some point.

                      There was one particular Fibaro Roller Shutter 2 module in the Kitchen, that was being very slow with the action running after the clicks.

                      I'll test that module again and look at logs.

                      As for all the others, 2 seconds seemed to be about the time it takes after clicking, for the action to run. Some of my actions are calling existing Vera scene I had in place, I can probably tidy that up a bit and control devices directly via MSR in the action maybe that may help.

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

                        OK. In case you want to poke at it yourself, and for the benefit of other readers... if you modify the level in logging.yaml for Rule to 6 (that is, find the line in the file that reads Rule: and change the level on the line below that one to 6), you'll get some deeper debug from all rules. Then restart MSR and activate your Fibaro device in whatever way you want to test.

                        At that level, you should be able to find a logged entry in reactor.log with the string "launching evaluation for" that references your Fibaro device. This is the detection of the change on the Fibaro. That causes the rule to be evaluated, and you'll see that happening shortly after. Follow that along, and you'll see "Enqueueing" followed by the name of the set or reset reaction that is to run based on the rule's result state. That will be followed by the execution of the reaction, which comes mostly from the Engine, so you'll see it report "Starting reaction" (followed by the reaction name), and then the steps. The reaction is finished executing when it logs "all actions completed". If you note the timestamps on all these, you'll get a feel for how fast its responding in the three major phases: detection -> evaluation -> execution.

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

                        1 Reply Last reply
                        0
                        • E Offline
                          E Offline
                          Edwin1972
                          wrote on last edited by Edwin1972
                          #44

                          I want to start moving ReactorOpenLuup to MSR and have the following problem. In Reactor OpenLuup I have set up below. Update does not show in de list in MRS. @cw-kid @ cw-kid What kind of setting do you use to use double click in MRS with roller shutter 2?

                          b181ac4b-2c8f-4d5d-b71a-e627924e2cb4-image.png

                          cw-kidC 1 Reply Last reply
                          0
                          • E Edwin1972

                            I want to start moving ReactorOpenLuup to MSR and have the following problem. In Reactor OpenLuup I have set up below. Update does not show in de list in MRS. @cw-kid @ cw-kid What kind of setting do you use to use double click in MRS with roller shutter 2?

                            b181ac4b-2c8f-4d5d-b71a-e627924e2cb4-image.png

                            cw-kidC Offline
                            cw-kidC Offline
                            cw-kid
                            wrote on last edited by cw-kid
                            #45

                            @edwin1972

                            I am just using the LastSceneID

                            Here is an example for S2 Double Click which has a number of "24"

                            You also need to reset the LastSceneID back to 0 in the "Set Reaction".

                            1b96d0da-3482-42b4-a4c6-efd740e6e0ee-image.png

                            The different SceneActivation numbers can be seen from the Fibaro Roller Shutter 2 user manual:

                            6cc75c9c-3649-4a75-a4c4-6529d83f2d2e-image.png

                            1 Reply Last reply
                            1
                            • E Offline
                              E Offline
                              Edwin1972
                              wrote on last edited by
                              #46

                              Thanks for the quick response. It works!

                              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
                                176

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

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

                              • DynamicGroupController and attributes
                                therealdbT
                                therealdb
                                1
                                5
                                121

                              • Upgrade Issues
                                T
                                tbully
                                0
                                9
                                242

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

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

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

                              • Logon screen timeout
                                G
                                gwp1
                                0
                                5
                                198

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

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