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. First post
DynamicGroupController updating members issue
CrilleC
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
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
Arming Envisalink panel from MSR
T
Topic thumbnail image
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
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
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

First post

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 2.0k 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.
  • T Offline
    T Offline
    tamorgen
    wrote on last edited by
    #1

    Good morning all,
    First, I just wanted to say hi and introduce myself. I've been using a Vera Plus for about 8 years now, and the luup based Reactor for two or three. Before that I used PLEG for my home logic on Vera.

    I've been monitoring the evolution of Ezlo, and I'm starting to consider making the jump to it. After discussing with others over on the Vera/Ezlo community, it seems that it's not an all or nothing switch, particularly with the Patrick's MSR, so I'm joining here today to start taking a look at it.

    Anyway, that's my basic post. Look forward to playing with MSR in the near future.

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

      Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

      Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

      Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

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

      T 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

        Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

        Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

        T Offline
        T Offline
        tamorgen
        wrote on last edited by
        #3

        @toggledbits said in First post:

        Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

        Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

        Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

        Hi Patrick,
        Thanks for the warm welcome!

        I've actually just installed Reactor on my home server. I have essentially a file server that I also use for various other tasks, such as Pihole, dhcp managment, PlexMediaSever, running Fedora Server 36. I installed using the bare metal method

        From what I've read, MSR will give me an easier upgrade to Ezlo path than anything else. Ezlo is still missing too many things that I'm dependent on Vera to make a complete switch. I have a working Vera, so MSR should allow me to slowly transition at my own pace, until Ezlo can do it all, and eventually retire Vera.

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tamorgen
          wrote on last edited by tamorgen
          #4

          @toggledbits
          Well, like I said, I got it installed, but it would appear there is an environmental variable that isn't correct.

          reactor.service: Failed at step EXEC spawning /usr/local/lib/nodejs/bin/node: No such file or directory

          It worked when I ran NODE_PATH=$(pwd) node app.js, but after I installed it as a service, it did not.

          Any advice on how I can find the correct path?

          Note: I used the following command to install:

          sudo dnf install nodejs-1:16:140.-2.fc36

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

            The pwd command returns the path of the current directory, which in that command is the directory where app.js lives and you have Reactor installed. Just make sure your Environment line in your service file contains that fully-qualified path.

            Here's the sample service file that you can modify. I'm not sure how you generated yours. You can also find this file in the tools directory in your Reactor install.

            # THIS IS A SAMPLE SYSTEMD SERVICE CONFIGURATION FILE FOR REACTOR.
            # Modify the WorkingDirectory, Environment, and User values below
            # to suit your system configuration. Also modify ExecStart with
            # the correct path to the "node" executable, if it has not been
            # installed in the system binary directories.
            # Then place the file in /etc/systemd/system or whatever other 
            # directory is normal for your system (remove the -example) from
            # the end of the name. You will need root privilegess to do this.
            # Then run:
            #     sudo systemctl daemon-reload
            #     sudo systemctl start reactor
            #
            [Unit]
            Description=Multi System Reactor
            After=network.target
            
            [Service]
            Type=simple
            User=myuser
            WorkingDirectory=/home/myuser/reactor
            Environment=NODE_PATH=/home/myuser/reactor
            ExecStart=/usr/local/lib/nodejs/bin/node app -p
            Restart=on-failure
            RestartSec=5s
            
            [Install]
            WantedBy=multi-user.target
            

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

            T 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              The pwd command returns the path of the current directory, which in that command is the directory where app.js lives and you have Reactor installed. Just make sure your Environment line in your service file contains that fully-qualified path.

              Here's the sample service file that you can modify. I'm not sure how you generated yours. You can also find this file in the tools directory in your Reactor install.

              # THIS IS A SAMPLE SYSTEMD SERVICE CONFIGURATION FILE FOR REACTOR.
              # Modify the WorkingDirectory, Environment, and User values below
              # to suit your system configuration. Also modify ExecStart with
              # the correct path to the "node" executable, if it has not been
              # installed in the system binary directories.
              # Then place the file in /etc/systemd/system or whatever other 
              # directory is normal for your system (remove the -example) from
              # the end of the name. You will need root privilegess to do this.
              # Then run:
              #     sudo systemctl daemon-reload
              #     sudo systemctl start reactor
              #
              [Unit]
              Description=Multi System Reactor
              After=network.target
              
              [Service]
              Type=simple
              User=myuser
              WorkingDirectory=/home/myuser/reactor
              Environment=NODE_PATH=/home/myuser/reactor
              ExecStart=/usr/local/lib/nodejs/bin/node app -p
              Restart=on-failure
              RestartSec=5s
              
              [Install]
              WantedBy=multi-user.target
              
              T Offline
              T Offline
              tamorgen
              wrote on last edited by
              #6

              @toggledbits

              Patrick,
              I had already updated the reactor.service file that you are referring to, but it seems to be that the path to nodejs is incorrect. What I'm trying to figure out is where Fedora would have installed that, so I can update the correct path.

              [Service]
              Type=simple
              User=tmorgenthaler
              WorkingDirectory=/home/tmorgenthaler/reactor
              Environment=NODE_PATH=/tmorgenthaler/myuser/reactor
              ExecStart=/usr/local/lib/nodejs/bin/node app -p
              Restart=on-failure
              RestartSec=5s

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

                Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

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

                T 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

                  T Offline
                  T Offline
                  tamorgen
                  wrote on last edited by
                  #8

                  @toggledbits said in First post:

                  Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

                  That did it. I always forget that command!

                  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

                  • DynamicGroupController updating members issue
                    toggledbitsT
                    toggledbits
                    0
                    4
                    7

                  • DynamicGroupController and attributes
                    therealdbT
                    therealdb
                    1
                    5
                    49

                  • Arming Envisalink panel from MSR
                    toggledbitsT
                    toggledbits
                    0
                    5
                    71

                  • Upgrade Issues
                    T
                    tbully
                    0
                    9
                    187

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

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

                  • Reactor (Multi-System/Multi-Hub) Announcements
                    toggledbitsT
                    toggledbits
                    5
                    147
                    128.2k

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

                  • Logon screen timeout
                    G
                    gwp1
                    0
                    5
                    181

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

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