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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

First post

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 1.2k 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

                  • Copying a global reaction
                    toggledbitsT
                    toggledbits
                    0
                    3
                    78

                  • [HowTo] Using HABridge with Reactor
                    CatmanV2C
                    CatmanV2
                    0
                    9
                    375

                  • [Reactor] Bug when sending MQTT boolean payloads
                    toggledbitsT
                    toggledbits
                    0
                    4
                    128

                  • Genuinely impressed with Zigbee and HA / Reactor
                    therealdbT
                    therealdb
                    1
                    8
                    292

                  • Difficulty defining repeating annual period
                    G
                    gwp1
                    0
                    5
                    97

                  • Need help with sequence
                    therealdbT
                    therealdb
                    0
                    3
                    60

                  • Possible feature request?
                    therealdbT
                    therealdb
                    0
                    5
                    161

                  • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                    CatmanV2C
                    CatmanV2
                    0
                    11
                    337

                  • Time series documentation
                    tunnusT
                    tunnus
                    0
                    11
                    387

                  • MQTT templates for ZIgbee scene controller, or a better way?
                    CatmanV2C
                    CatmanV2
                    0
                    3
                    155

                  • Reset a delay
                    CatmanV2C
                    CatmanV2
                    0
                    8
                    215
                  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