Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
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.
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
Vera - Attempt to set primary to power_switch.state invalid
-
In the
configsection of the controller configuration (inreactor.yaml) for this controller (vera, apparently, notvera-edge), please add the following, indented the same assource:in that section:dump_entity: ['device_75','device_139']This will create two files in
logscalledvera-device_75.jsonandvera-device_139.json. Please post them here or in a PR.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
In the
configsection of the controller configuration (inreactor.yaml) for this controller (vera, apparently, notvera-edge), please add the following, indented the same assource:in that section:dump_entity: ['device_75','device_139']This will create two files in
logscalledvera-device_75.jsonandvera-device_139.json. Please post them here or in a PR. -
OK. I think I've got it sorted. Build later today.
-
OK. Build 21203 is available.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
OK. Build 21203 is available.
@toggledbits said in Vera - Attempt to set primary to power_switch.state invalid:
Build 21203 is available.
Just updated to this build and now my Ezlo Plus controller is missing in MSR and I have error alerts about missing devices.
I can see this in the log:
2021-07-23T08:44:19.384Z <Structure:WARN> Structure#1 findEntity ezlo-plus>device_60e4a54a120bab11f9d77f67 controller undefined not found 2021-07-23T08:44:19.384Z <Structure:WARN> Structure#1 promiseEntity(ezlo-plus>device_60e4a54a120bab11f9d77f67,30000) timeout! 2021-07-23T08:44:19.384Z <Rule:CRIT> Rule#rule-kr7n2q7p failed subscription to ezlo-plus>device_60e4a54a120bab11f9d77f67 2021-07-23T08:44:19.385Z <Rule:CRIT> !timeout 2021-07-23T08:44:19.385Z <Rule:5:Rule.js:703> Rule#rule-kr7n2q7p start() dependencies resolved, performing initial evaluation 2021-07-23T08:44:19.386Z <Rule:5:Rule.js:962> Rule#rule-kr7n2q7p (Stairs Cupboard Door Closed) evaluate() acquiring mutex 2021-07-23T08:44:19.387Z <Rule:5:Rule.js:966> Rule#rule-kr7n2q7p._evaluate() mutex acquired, evaluating 2021-07-23T08:44:19.388Z <Rule:5:Rule.js:970> Rule#rule-kr7n2q7p update rate is 0/min limit 60/min 2021-07-23T08:44:19.388Z <Rule:5:Rule.js:892> Rule#rule-kr7n2q7p evaluateExpressions() with 0 expressions 2021-07-23T08:44:19.389Z <Structure:WARN> Structure#1 findEntity ezlo-plus>device_60e4a54a120bab11f9d77f67 controller undefined not found 2021-07-23T08:44:19.392Z <Rule:CRIT> ReferenceError: Can't find entity ezlo-plus>device_60e4a54a120bab11f9d77f67 ReferenceError: Can't find entity ezlo-plus>device_60e4a54a120bab11f9d77f67I tried rebooting the Ezlo Plus controller but its still the same.
-
That's too late in the log, so it's a downstream effect of whatever else happened. Look up higher, near the startup of Reactor. Look for the string "starting controller interface" and then follow down from there.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
That's too late in the log, so it's a downstream effect of whatever else happened. Look up higher, near the startup of Reactor. Look for the string "starting controller interface" and then follow down from there.
@toggledbits said in Vera - Attempt to set primary to power_switch.state invalid:
starting controller interface
Patrick
<Structure:ERR> [Structure:start] failed to start controller ezlo-plus: Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js 2021-07-23T15:30:55.837Z <Structure:CRIT> Error: Cannot find module 'server/lib/Configuration'2021-07-23T15:30:55.261Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-07-23T15:30:55.272Z <Structure:INFO> Structure#1 starting controller interface vera-edge (VeraController) 2021-07-23T15:30:55.274Z <Structure:INFO> Structure#1 starting controller interface ezlo-plus (EzloController) 2021-07-23T15:30:55.276Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController) 2021-07-23T15:30:55.279Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-07-23T15:30:55.412Z <default:null> Module VeraController v21202 2021-07-23T15:30:55.436Z <default:null> Module OWMWeatherController v21140 2021-07-23T15:30:55.441Z <default:null> Module SystemController v21102 2021-07-23T15:30:55.452Z <VeraController:NOTICE> VeraController#vera starting 2021-07-23T15:30:55.596Z <VeraController:INFO> VeraController#vera loaded mapping ver 21202 rev 1 format 1 notice 2021-07-23T15:30:55.629Z <VeraController:NOTICE> VeraController#vera-edge starting 2021-07-23T15:30:55.641Z <Controller:CRIT> Controller: failed to load ezlo-plus implementation file:///home/stuart/reactor/server/lib/EzloController.js: Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js 2021-07-23T15:30:55.644Z <Controller:CRIT> Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15) at Function.Module._load (internal/modules/cjs/loader.js:730:27) at Module.require (internal/modules/cjs/loader.js:957:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/stuart/reactor/server/lib/EzloController.js:527:157) at Module._compile (internal/modules/cjs/loader.js:1068:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10) at Module.load (internal/modules/cjs/loader.js:933:32) at Function.Module._load (internal/modules/cjs/loader.js:774:14) at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29) 2021-07-23T15:30:55.704Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-07-23T15:30:55.836Z <Structure:ERR> [Structure:start] failed to start controller ezlo-plus: Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js 2021-07-23T15:30:55.837Z <Structure:CRIT> Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js Error: Cannot find module 'server/lib/Configuration' Require stack: - /home/stuart/reactor/server/lib/EzloController.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15) at Function.Module._load (internal/modules/cjs/loader.js:730:27) at Module.require (internal/modules/cjs/loader.js:957:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/stuart/reactor/server/lib/EzloController.js:527:157) at Module._compile (internal/modules/cjs/loader.js:1068:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10) at Module.load (internal/modules/cjs/loader.js:933:32) at Function.Module._load (internal/modules/cjs/loader.js:774:14) at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29) 2021-07-23T15:30:55.839Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-07-23T15:30:56.081Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. 2021-07-23T15:30:57.165Z <VeraController:NOTICE> Controller VeraController#vera-edge is now online. 2021-07-23T15:31:04.144Z <VeraController:NOTICE> Controller VeraController#vera is now online.I don't know what happened? It was working fine for the Ezlo Plus yesterday on the prior MSR build.
This is what I see in that folder:
Thanks
-
What install method are you using, and how are you starting MSR?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
What install method are you using, and how are you starting MSR?
I downloaded the reactor-latest-21203-9503e5d.tar.gz file from this page: https://reactor.toggledbits.com/download/latest/
I copied it to my Linux machine in this folder: /home/stuart
I then SSH in to the box with Putty and run these commands one by one, as root user:
cd /home/stuart pkill -QUIT node tar xzvf /home/stuart/reactor-latest-21203-9503e5d.tar.gz sudo systemctl start reactorThis is the way I've always updated MSR. Except you now have a new download page.
Only slightly different thing about when I did it this morning, was that the downloaded file was called:
reactor-latest-21203-9503e5d.tar.gz
All the other ones prior had "generic" in their names, but I figured it likely didn't matter and maybe you'd just omitted that from the file name etc.
Regarding starting MSR nothing has change there either.
In this directory: /etc/systemd/system
There is a file called: reactor.service
# This file allows you to run your Reactor installation under systemd, # so it can be started at boot. Copy this file (as root or under sudo) # to /etc/systemd/system, and then run "systemctl daemon-reload". You # can then able Reactor to start at boot "systemctl enable reactor". # The usual systemctl subcommands can also be used to start, stop, and # restart reactor at will (e.g. "systemctl restart reactor"). [Unit] Description=Multi System Reactor After=network.target [Service] Type=simple User=stuart WorkingDirectory=/home/stuart/reactor ExecStart=/usr/bin/node app -p Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target -
Add above
WorkingDirectory:Environment=NODE_PATH=/home/stuart/reactorand then:
sudo systemctl daemon-reload sudo systemctl restart reactorAuthor of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Add above
WorkingDirectory:Environment=NODE_PATH=/home/stuart/reactorand then:
sudo systemctl daemon-reload sudo systemctl restart reactorAppears to have done the trick the Ezlo-Plus controller is back again in Entities.
Thanks
-
T toggledbits locked this topic on
