Sorry to write here without trying, but I’m flying today.
Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes?
That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Hi,
I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available.
None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5.
Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image?
Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way:
docker buildx build --push \
-t <localrepo>/<project>:<tag> \
--platform=linux/arm64,linux/amd64 \
--file ./apps/<project>/Dockerfile .
This produces both the AMD64 and ARM64/v8 variants automatically.
Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications.
@toggledbits - tagging you in case you missed this.
Thanks,
mgvra
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.
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1?
[latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" }
[latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } }
[latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed!
[latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload:
{"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320}
[latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data:
{"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}}
[latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" }
[latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1
[latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 }
[latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } }
[latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed!
[latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload:
{"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323}
[latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data:
{"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}}
[latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 }
[latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2
[latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Hello,
I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light?
Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ
Please help,
P.S
Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
https://github.com/dbochicchio/reactor-mqtt-contrib
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
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.
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?
Help resolve change in behaviour post update
Multi-System Reactor
12
Posts
2
Posters
188
Views
2
Watching
-
Current set up: Bare metal (virtualised) on Debian 10.2
MSR 25310Updated over the weekend and two reactions that have worked for literally years have changed. I'm pretty sure it was due to the 'nuances' in previous versions of evaluating global variables, so just looking for some help to 'fix'?
I have two reactions that are dependant in large part on the global variable GlobalAlarmTime This is set in the Alarm Clock plugin of Openluup.
One reaction turns the heating on one hour before the alarm goes off. The other turns the outside lights on one hour before the alarm goes off.
Typically I change GlobalAlarmTime depending on the day of the week and the plans of the day ahead.
GlobalAlarmTime is a string, current value(string) "05:40:00"
Local variable HeatTime is calculated:
time(GlobalAlarmTime) - 3600000
Currently that has a value of1762749600000
Which is (quite correctly) 04:40:00 GMT 10th November. It's this because I changed the value of GlobalAlarmTime checking stuff out this morning, and HeatTime was re-evaluated at 09:37:17
The challenge that I'm facing is that prior to the upgrade, HeatTime would be re-evaluated every 15 minutes (triggered by the 'Interval' function and come midnight (or at worst 00:15:00) HeatTime would re-evaluate to
time(GlobalAlarmTime) - 3600000 today (if you get my point)That update to 'today' no longer happens. So the heating never comes on.
[latest-25310]2025-11-10T00:00:00.025Z <Rule:INFO> Holiday Shutdown (rule-l8ys5tzy in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l8ys5tzy [latest-25310]2025-11-10T00:00:00.031Z <Rule:INFO> Holiday Heating (rule-ltsdvzi8 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltsdvzi8 [latest-25310]2025-11-10T00:00:00.051Z <Rule:INFO> Holiday Lights (rule-ltse0zb4 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltse0zb4 [latest-25310]2025-11-10T00:00:00.058Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioalha1 [latest-25310]2025-11-10T00:00:00.068Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) evaluated; rule state transition from SET to 'RESET' [latest-25310]2025-11-10T00:00:00.084Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-lb2h69nb [latest-25310]2025-11-10T00:00:00.086Z <Rule:INFO> Set Greeting to Afternoon (rule-lioanahk in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioanahk [latest-25310]2025-11-10T00:00:00.095Z <Rule:INFO> Evening Lights are On (rule-l5senfyv in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l5senfyv [latest-25310]2025-11-10T00:00:00.096Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu [latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable [latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency [latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable [latest-25310]2025-11-10T00:00:00.103Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) evaluated; rule state transition from RESET to 'SET' [latest-25310]2025-11-10T00:00:00.139Z <Engine:INFO> Enqueueing "Morning Lights are on<SET>" (rule-l6gxvycu:S) [latest-25310]2025-11-10T00:00:00.140Z <Engine:NOTICE> Starting reaction Set Greeting to Morning<SET> (rule-lioajm6q:S) [latest-25310]2025-11-10T00:00:00.147Z <Engine:INFO> Set Greeting to Morning<SET> all actions completed. [latest-25310]2025-11-10T00:00:00.162Z <Engine:NOTICE> Starting reaction Morning Lights are on<SET> (rule-l6gxvycu:S) [latest-25310]2025-11-10T00:00:00.163Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20170 with { } [latest-25310]2025-11-10T00:00:00.170Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20170 with { "state": true } [latest-25310]2025-11-10T00:00:00.173Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3 [latest-25310]2025-11-10T00:00:00.178Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency [latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable [latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency [latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable [latest-25310]2025-11-10T00:00:00.180Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable [latest-25310]2025-11-10T00:00:00.185Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu [latest-25310]2025-11-10T00:00:00.192Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable [latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency [latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable [latest-25310]2025-11-10T00:00:00.195Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3 [latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency [latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable [latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency [latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable [latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable [latest-25310]2025-11-10T00:00:00.233Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20170 succeeded [latest-25310]2025-11-10T00:00:00.234Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 1 [latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20090 with { } [latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20090 with { "state": true } [latest-25310]2025-11-10T00:00:00.289Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20090 succeeded [latest-25310]2025-11-10T00:00:00.289Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 2 [latest-25310]2025-11-10T00:00:00.290Z <Engine:INFO> Morning Lights are on<SET> all actions completed. [latest-25310]2025-11-10T00:00:43.383Z <Engine:INFO> Engine#1 master timer tick, local time "10/11/2025 00:00:43" (TZ offset 0 mins from UTC) [latest-25310]2025-11-10T00:00:43.452Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system [latest-25310]2025-11-10T00:00:43.463Z <httpapi:INFO> HTTPAPI(#1) API request from ::ffff:192.168.70.249: GET /api/v1/netstatus [latest-25310]2025-11-10T00:00:43.476Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system [latest-25310]2025-11-10T00:00:43.488Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system [latest-25310]2025-11-10T00:00:43.490Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system [latest-25310]2025-11-10T00:00:43.510Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system [latest-25310]2025-11-10T00:00:43.516Z <HassController:NOTICE> HassController#hass websocket closing, 1006I'm going to guess I need to use the new
alarmfunction.I'm further guessing that I'd set up a new global variable to replace
HeatTimeand have something like
GlobalHeatTime = alarm ( 900) , time(GlobalAlarmTime) - 3600000?Am I on the right lines?
TIA
C
@CatmanV2 said in Help resolve change in behaviour post update:
I'm further guessing that I'd set up a new global variable to replace HeatTime and have something like
GlobalHeatTime = alarm ( 900) , time(GlobalAlarmTime) - 3600000You're on the right track. If I understand your description, something like this should work (all globals):
gAlarmTime = getEntity( ... ) gHeatTime = time(gAlarmTime) - 3600000 gHeatOn = alarm(900), time() >= gHeatTimegAlarmTimewill be updated any time the dependent entity changes.gHeatTimewill change any timegAlarmTimechanges (reference to another variable creates a dependency on that variable).gHeatOnwill be updated by the periodicalarm()tripping. -
@CatmanV2 said in Help resolve change in behaviour post update:
Will I see it updating in the logs?
Yes, and on the Expressions page.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@CatmanV2 said in Help resolve change in behaviour post update:
Will I see it updating in the logs?
Yes, and on the Expressions page.
@toggledbits Thanks so much
I've now got this
With
GlobalHeatOnas one of my conditions in the reaction.My assumption is it will go
falseat, or immediately after midnight?I'm guessing I can lose the
Intervalstatement as well?
Cheers
C
The Ex-Vera abuser know as CatmanV2.....
-
@toggledbits Thanks so much
I've now got this
With
GlobalHeatOnas one of my conditions in the reaction.My assumption is it will go
falseat, or immediately after midnight?I'm guessing I can lose the
Intervalstatement as well?Cheers
C
@CatmanV2 said in Help resolve change in behaviour post update:
My assumption is it will go false at, or immediately after midnight?
No. If your
GlobalAlarmTimewill always show time only (no date components), then you can safely add analarm()call toGlobalHeatTimeas well.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@CatmanV2 said in Help resolve change in behaviour post update:
My assumption is it will go false at, or immediately after midnight?
No. If your
GlobalAlarmTimewill always show time only (no date components), then you can safely add analarm()call toGlobalHeatTimeas well.@toggledbits Ahh super
GlobalAlarmTimeis never date (or I guess we'd not have this issue!)
I do appreciate you thinking down to my level
C
-
I'm working for you. You also gave me an idea that I think could create a very useful alternative way to get to where you want to go. More to come...
-
-
You should be able to go back to something similar to what you were doing originally, just in Script conditions. Give it a try!
