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.
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.
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others).
After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems.
For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon.
But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU.
For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system.
To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image.
pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH
armhf
pi@rpi4-1:~ $ uname -m
aarch64
pi@rpi4-1:~ $
In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image.
Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image.
Remember to always back up your system before making any changes.
For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
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
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.
@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).
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
Multi-System Reactor
17
Posts
5
Posters
763
Views
5
Watching
-
I'm running into this as well. It appears that using haas>whatever-switch and power_switch.on or power_switch.off isn't working since the 25310 update and Haas 2025.11.0. I had a few stragglers in my rule sets that stopped working. I switched to using zwavejs>whatever-switch, and it works fine.
I also tried from Entities --> whatever-switch --> Perform --> power_switch.on and there is no action performed
-
Again, haven't had time to parse the logs (silly day job) but posting these for @Pmccraw to compare/contrast as they build their case notes:
This is the rule that was working:
My other LIFX outdoor floods still work fine! I also noted that @Pmccraw is having this with another brand. My guess is that HA changed something because it started immediately after deployment of 11.0 (and I seem to recall some notes around dimming or some such but I just haven't been able to track it back).
Here's a quick grab from the log file, best I can do atm.
[latest-25308]2025-11-06T19:25:34.668Z <Engine:NOTICE> Starting reaction MBR Lamp ON (Mornings - fade-in) (re-mc83qh6e) [latest-25308]2025-11-06T19:25:34.669Z <Engine:CRIT> Engine#1 reaction re-mc83qh6e handling while Repeat Conditions (re-mc83qh6e-1vwdp9fw) constraints result state true [latest-25308]2025-11-06T19:25:34.680Z <Engine:NOTICE> Starting reaction MBR Lamp ON (Mornings - fade-in)/Repeat Conditions (re-mc83qh6e-1vwdp9fw) [latest-25308]2025-11-06T19:25:34.681Z <HassController:INFO> HassController#hass perform dimming.up on Light#hass>light_master_br_lamp_lamp_2 with { } [latest-25308]2025-11-06T19:25:34.681Z <HassController:INFO> HassController#hass perform dimming.set on Light#hass>light_master_br_lamp_lamp_2 with { "level": 0.03 } [latest-25308]2025-11-06T19:25:34.682Z <HassController:INFO> HassController#hass no entity/target for homeassistant.turn_on in { "fields": { }, "target": { } } [latest-25308]2025-11-06T19:25:34.682Z <HassController:INFO> HassController#hass: sending payload for dimming.set on Light#hass>light_master_br_lamp_lamp_2 action: { "type": "call_service", "service_data": { "brightness": 8 }, "domain": "homeassistant", "service": "turn_on" } [latest-25308]2025-11-06T19:25:34.685Z <HassController:INFO> HassController#hass action dimming.set({ "level": 0.03 }) on Light#hass>light_master_br_lamp_lamp_2 succeeded [latest-25308]2025-11-06T19:25:34.686Z <Engine:INFO> Resuming reaction MBR Lamp ON (Mornings - fade-in)/Repeat Conditions (re-mc83qh6e-1vwdp9fw) from step 1 [latest-25308]2025-11-06T19:25:34.686Z <Engine:NOTICE> MBR Lamp ON (Mornings - fade-in)/Repeat Conditions delaying until 1762457254686<11/6/2025, 2:27:34 PM> [latest-25308]2025-11-06T19:25:35.221Z <Rule:INFO> It's Too Windy (Ambient Cloud API) (rule-m34m60yh in Shared Rules) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_st_00136549_wind_speed [latest-25308]2025-11-06T19:25:35.222Z <Rule:INFO> It's Too Windy (Fan use only) TEMPEST (rule-m77rbco8 in Shared Rules) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_st_00136549_wind_speed [latest-25308]2025-11-06T19:25:35.222Z <Rule:INFO> It's Too Windy (Local APIs) (rule-m34nlj3i in Shared Rules) starting rule state evaluation; because entity-changed ValueSensor#hass>sensor_st_00136549_wind_speed -
I need to see device attributes for those devices (from the Entities list -- use Copy Attributes and paste as fenced code block, no screenshots please). Also would be helpful to see the
hass_states.jsonandhass_services.jsonfrom thelogsdirectory, but these are larger. If any of you are willing to upload them, let me know and I will provide you a link.Edit: it looks like HA 2025.11.0 breaks the
homeassistantdomain commands (turn_on,turn_off). I'm digging more into that, to see if it's a change to their required parameter structure, or just brokeness, but HA does not reply with an error when those services are attempted, and that's usually what happens when parameters/service definition changes.Edit 2: ...and a little more info. The service data published by the API in 2025.11.0 now omits the target data detail. That's odd. Maybe they are assuming that when target data is empty, just supply an entity? I need to dig through the release notes. But, easy to work around.
-
I need to see device attributes for those devices (from the Entities list -- use Copy Attributes and paste as fenced code block, no screenshots please). Also would be helpful to see the
hass_states.jsonandhass_services.jsonfrom thelogsdirectory, but these are larger. If any of you are willing to upload them, let me know and I will provide you a link.Edit: it looks like HA 2025.11.0 breaks the
homeassistantdomain commands (turn_on,turn_off). I'm digging more into that, to see if it's a change to their required parameter structure, or just brokeness, but HA does not reply with an error when those services are attempted, and that's usually what happens when parameters/service definition changes.Edit 2: ...and a little more info. The service data published by the API in 2025.11.0 now omits the target data detail. That's odd. Maybe they are assuming that when target data is empty, just supply an entity? I need to dig through the release notes. But, easy to work around.
@toggledbits I was able to grab this between meetings lol
dimming.maximum=1 dimming.minimum=0 dimming.step=0.03 light_effect.current=null light_effect.speed=null power_switch.state=false x_hass.domain="light" x_hass.entity_id="light.master_br_lamp_lamp_2" x_hass.services=["light","lifx"] x_hass.source="lifx" x_hass.state="off" x_hass_attr.brightness=null x_hass_attr.color_mode=null x_hass_attr.effect=null x_hass_attr.effect_list=["effect_pulse","effect_stop"] x_hass_attr.friendly_name="Master BR Lamp" x_hass_attr.supported_color_modes=["brightness"] x_hass_attr.supported_features=36 -
OK. I'm on this. See my previous post above yours. HA changes the way the definition of some services is published -- there's now no data/detail where there used to be data/detail. I'm not sure if that's an error they'll correct later, or if that's a new way of saying "just use the default behavior" (which in this case is pretty easy to guess). I will have a workaround update published shortly.
FWIW, specifically, from 2025.10.4:
"homeassistant": { "save_persistent_states": { "name": "Save persistent states", "description": "Saves the persistent states immediately. Maintains the normal periodic saving interval.", "fields": {} }, "turn_off": { "name": "Generic turn off", "description": "Generic action to turn devices off under any domain.", "fields": {}, "target": { "entity": [ {} ] } }, "turn_on": { "name": "Generic turn on", "description": "Generic action to turn devices on under any domain.", "fields": {}, "target": { "entity": [ {} ] } }, "toggle": { "name": "Generic toggle", "description": "Generic action to toggle devices on/off under any domain.", "fields": {}, "target": { "entity": [ {} ] } },Compare this to 2025.11.0:
"homeassistant": { "save_persistent_states": { "fields": {} }, "turn_off": { "fields": {}, "target": {} # <--- where did the detail go??? }, "turn_on": { "fields": {}, "target": {} # <--- where did the detail go??? }, "toggle": { "fields": {}, "target": {} # <--- where did the detail go??? }, -
@toggledbits I was able to grab this between meetings lol
dimming.maximum=1 dimming.minimum=0 dimming.step=0.03 light_effect.current=null light_effect.speed=null power_switch.state=false x_hass.domain="light" x_hass.entity_id="light.master_br_lamp_lamp_2" x_hass.services=["light","lifx"] x_hass.source="lifx" x_hass.state="off" x_hass_attr.brightness=null x_hass_attr.color_mode=null x_hass_attr.effect=null x_hass_attr.effect_list=["effect_pulse","effect_stop"] x_hass_attr.friendly_name="Master BR Lamp" x_hass_attr.supported_color_modes=["brightness"] x_hass_attr.supported_features=36@toggledbits I've uploaded the two log files to folder
HASS 11.0for you. -
OK... I found the PR in HA's code and the reasoning behind it. They are trying to make their data/responses more compact (performance reasons). I will have an updated build shortly for this change.
-
OK. Please pull 25310 (aka latest) again. I've patched HassController for this change.
-
OK. Please pull 25310 (aka latest) again. I've patched HassController for this change.
@toggledbits would this be latest-25310-dc2bb580?
*Hubitat C-7 2.4.3.158
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HASS 2025.11.1
w/ HA Connect ZWA-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-25323-d340b7d9
MQTTController: 25139
ZWave Controller: 25139 -
@toggledbits would this be latest-25310-dc2bb580?
@gwp1 yes!
-
T toggledbits forked this topic