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.
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.
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
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
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.
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
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.
Up and running
Multi-System Reactor
9
Posts
3
Posters
1.0k
Views
3
Watching
-
Ummm, ok this is embarrassing....
I'm actually stuck on creating the simplest rule set / reaction. I can't see anything in the manual that indicates my stupidity, and it's surely not a bug so here goes.
Bare metal install on Debian 10
Simple 'AND' test rule which I can see setting and resetting as the conditions change.I have tried putting a reaction in that rule set to turn on a light. So literally
Entity action > Table Lamp > power_switch.onIf I press the 'Try this action' button from within the reaction, the light goes on.
If I press the 'Run Now' button from the Global reactions list:1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:INFO> Test motion lights<SET> all actions completed. [1.0.2-21350]2022-05-26T16:20:59.510Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.70.64 [1.0.2-21350]2022-05-26T16:21:13.051Z <wsapi:INFO> client "192.168.70.64#4" closed, code=1001, reason= [1.0.2-21350]2022-05-26T16:21:15.726Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET! [1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543 [1.0.2-21350]2022-05-26T16:26:17.531Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:17.536Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:17.537Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:26:45.444Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn :upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:26:49.094Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:03.286Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:03.287Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:23.575Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:23.576Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:47.538Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:47.542Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:47.543Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:14.393Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:24.225Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:24.228Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:24.229Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:35.395Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:29:12.974Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:29:25.885Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:29:50.139Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:33:05.815Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:33:05.825Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:33:05.826Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:35:15.688Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:37:17.185Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:37:44.912Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:37:44.916Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:37:44.917Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:38:39.696Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) SET! [1.0.2-21350]2022-05-26T16:38:39.703Z <Engine:INFO> Enqueueing "Test motion lights<SET>" (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:INFO> Test motion lights<SET> all actions completed. [1.0.2-21350]2022-05-26T16:39:10.418Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET! [1.0.2-21350]2022-05-26T16:41:56.241Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938494294&Timeout=15&MinimumDelay=50&output_format=json&_r=1653583298238But the light never comes on
Similarly although the test Rule set is supposed to trigger 'Simple Test Reaction', the light never turns on.
The reaction is enabled. The rule set is enabled.
Time zone is BST (trying to conform to the log requests in the manual!)
I'm sorry! It's going to be something really dumb but I've spent about an hour so far
C
-
Screenshot of the ruleset?
*Hubitat C-7 2.4.3.173
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HASS 2025.12.4, Core 2025.12.3
w/ HA Connect ZWA-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-25328-b2ed1365
MQTTController: 25139
ZWave Controller: 25139 -
@gwp1 said in Up and running:
Screenshot of the ruleset?
Of course, but given the Reaction doesn't do anything...
It's crazy simple. Obviously the rule won't trigger under these circumstances as the motion sensor is not tripped, but even when it does....no reaction
Cheers
C
-
Well, first, you're on an ancient build. I would start by getting on
latest.After that, the log messages are telling you it can't talk to the Vera. Do you see those?
[1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Well, first, you're on an ancient build. I would start by getting on
latest.After that, the log messages are telling you it can't talk to the Vera. Do you see those?
[1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543@toggledbits Ahh, OK. I didn't check the version. I'll upgrade.
Yes I did see it can't talk to Vera but given that I can run the action directly I figured that was looking at something else it was trying to do.....
Clearly all the entities are in place, and updating in real time, as is the rule set so my takeaway was that it can talk to Vera (at least for these functions.
Cheers
C
-
OK, updated and working.
Told you it would be something stupid, although it was only 2 months old
Thanks, as ever
C
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
@toggledbits said in Up and running:
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
Ahh I was looking at the date stamp on the download. Thanks, as ever
C