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).
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
[SOLVED]Hass websocket falsely reporting ready on boot??
-
You must have
wait_all_controllers: truein your config orstartup_waitisn't used at all.The
controllerssection is an array. Make sure DynamicGroupController and SystemController are the last two entries in the array. Use yamllint.com or a similar tool to make sure the format of your config file is perfect. -
All right, that did the trick.
I can clearly see in the log where it is waiting for the connection to be stable and sending the request only after. This is great!
The 3 alarm are still showing when I use the "reboot reactor" from the Tools menu. It seems that it is only transitory since a screen refresh or re-starting the browser clears it. This is also fine.
Just making sure that I understand the process. Please correct me where I am wrong.
-
without adding wait_all_controllers: true to the engine subsection, there is no delay
-
with the wait_all_controllers: true the default delay is 60 second
-
If the default delay is not enough then we can use startup_wait: xxxx to change the default delay
-
In all cases the delay is only the maximum delay and the wait will be terminated when the connections is made.
-
If I have 5 controllers, are they all treated individually or the slowest one need to be up before anything happen?
@toggledbits said in Hass websocket falsely reporting ready on boot??:
The controllers section is an array. Make sure DynamicGroupController and SystemController are the last two entries in the array.
I am not sure I understand this one. I never played with the reactor.yaml file, I simply took the template and fill it up. I fail to see why these 2 controller need to be last. In my case I had 2 unused one between the two like it is in the template. I did move them but I am not sure that it really did anything.
Many thanks for your support
Using MSR 25139 on Docker, on a Raspberry Pi with Bookworm. Home Assistant 2025.07, Z-Wave JS-UI 10.6.1
-
-
All right, that did the trick.
I can clearly see in the log where it is waiting for the connection to be stable and sending the request only after. This is great!
The 3 alarm are still showing when I use the "reboot reactor" from the Tools menu. It seems that it is only transitory since a screen refresh or re-starting the browser clears it. This is also fine.
Just making sure that I understand the process. Please correct me where I am wrong.
-
without adding wait_all_controllers: true to the engine subsection, there is no delay
-
with the wait_all_controllers: true the default delay is 60 second
-
If the default delay is not enough then we can use startup_wait: xxxx to change the default delay
-
In all cases the delay is only the maximum delay and the wait will be terminated when the connections is made.
-
If I have 5 controllers, are they all treated individually or the slowest one need to be up before anything happen?
@toggledbits said in Hass websocket falsely reporting ready on boot??:
The controllers section is an array. Make sure DynamicGroupController and SystemController are the last two entries in the array.
I am not sure I understand this one. I never played with the reactor.yaml file, I simply took the template and fill it up. I fail to see why these 2 controller need to be last. In my case I had 2 unused one between the two like it is in the template. I did move them but I am not sure that it really did anything.
Many thanks for your support
@vezinpi said in Hass websocket falsely reporting ready on boot??:
Just making sure that I understand the process. Please correct me where I am wrong.
without adding wait_all_controllers: true to the engine subsection, there is no delay
with the wait_all_controllers: true the default delay is 60 second
If the default delay is not enough then we can use startup_wait: xxxx to change the default delay
In all cases the delay is only the maximum delay and the wait will be terminated when the connections is made.
This is all correct.
If I have 5 controllers, are they all treated individually or the slowest one need to be up before anything happen?
wait_all_controllersmeans it is waiting until the slowest controller signals on line.I did move them but I am not sure that it really did anything.
It affects the startup order. DynamicGroupController in particular is very sensitive to its position, since its configuration rules refer to devices owned by other controllers.
-
-
As I sometimes seen the Controller off-line message I thought to give this a try. Added wait_all_controllers and startup_wait. When I then restart Reactor in Tools, I get a controller offline in the status window for all controllers!?! All of them are up as I am only touching reactor. I took the two options out again and status messages gone. Oddly in the reactor.log no message about off-line controllers.
[latest-25016]2025-02-07T09:08:01.620Z <app:null> Reactor build latest-25016-d47fea38 starting on v22.12.0 /usr/local/bin/node [latest-25016]2025-02-07T09:08:01.620Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #72806 SMP Thu Sep 5 13:41:01 CST 2024; locale (undefined) [latest-25016]2025-02-07T09:08:01.621Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25016]2025-02-07T09:08:01.621Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25016]2025-02-07T09:08:01.644Z <app:null> Resolved timezone=Europe/Amsterdam, environment TZ=Europe/Amsterdam; offset minutes from UTC=60 [latest-25016]2025-02-07T09:08:01.647Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25016]2025-02-07T09:08:01.664Z <app:null> Loaded locale en-US for en-US [latest-25016]2025-02-07T09:08:01.665Z <app:null> Local date/time using configured timezone and locale formatting is "2/7/2025, 10:08:01 AM" [latest-25016]2025-02-07T09:08:01.714Z <Structure:null> Module Structure v24287 [latest-25016]2025-02-07T09:08:01.716Z <Capabilities:null> Module Capabilities v24312 [latest-25016]2025-02-07T09:08:01.736Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 25004 revision 1 [latest-25016]2025-02-07T09:08:01.747Z <Plugin:null> Module Plugin v22300 [latest-25016]2025-02-07T09:08:01.767Z <TimerBroker:null> Module TimerBroker v22283 [latest-25016]2025-02-07T09:08:01.770Z <Entity:null> Module Entity v25014 [latest-25016]2025-02-07T09:08:01.773Z <Controller:null> Module Controller v25014 [latest-25016]2025-02-07T09:08:01.784Z <default:null> Module Ruleset v24288 [latest-25016]2025-02-07T09:08:01.784Z <default:null> Module Rulesets v24220 [latest-25016]2025-02-07T09:08:01.789Z <GlobalExpression:null> Module GlobalExpression v24209 [latest-25016]2025-02-07T09:08:01.800Z <Predicate:null> Module Predicate v24350 [latest-25016]2025-02-07T09:08:01.806Z <AlertManager:null> Module AlertManager v24099 [latest-25016]2025-02-07T09:08:01.809Z <Rule:null> Module Rule v24329 [latest-25016]2025-02-07T09:08:01.813Z <GlobalReaction:null> Module GlobalReaction v24220 [latest-25016]2025-02-07T09:08:01.814Z <Engine:null> Module Engine v24344 [latest-25016]2025-02-07T09:08:01.819Z <httpapi:null> Module httpapi v24298 [latest-25016]2025-02-07T09:08:01.831Z <wsapi:null> Module wsapi v25016 [latest-25016]2025-02-07T09:08:01.832Z <app:NOTICE> Starting Structure... [latest-25016]2025-02-07T09:08:01.855Z <InfluxFeed:null> Module InfluxFeed v23341 [latest-25016]2025-02-07T09:08:01.857Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed) [latest-25016]2025-02-07T09:08:01.857Z <Structure:INFO> Structure#1 loading controller interface openLuup (VeraController) [latest-25016]2025-02-07T09:08:01.881Z <TaskQueue:null> Module TaskQueue 24138 [latest-25016]2025-02-07T09:08:01.924Z <VeraController:null> Module VeraController v25014 [latest-25016]2025-02-07T09:08:01.979Z <Structure:INFO> Structure#1 loading controller interface hubitat-C8 (HubitatController) [latest-25016]2025-02-07T09:08:01.995Z <HubitatController:null> Module HubitatController v24355 [latest-25016]2025-02-07T09:08:02.035Z <Structure:INFO> Structure#1 loading controller interface hubitat-C7 (HubitatController) [latest-25016]2025-02-07T09:08:02.048Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-25016]2025-02-07T09:08:02.057Z <HassController:null> Module HassController v25010 [latest-25016]2025-02-07T09:08:02.282Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-25016]2025-02-07T09:08:02.288Z <DynamicGroupController:null> Module DynamicGroupController v24279 [latest-25016]2025-02-07T09:08:02.291Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-25016]2025-02-07T09:08:02.294Z <SystemController:null> Module SystemController v24279 [latest-25016]2025-02-07T09:08:02.298Z <Structure:INFO> Starting controller VeraController#openLuup [latest-25016]2025-02-07T09:08:02.298Z <VeraController:NOTICE> VeraController#openLuup starting... [latest-25016]2025-02-07T09:08:02.298Z <Structure:INFO> Starting controller HubitatController#hubitat-C8 [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller HubitatController#hubitat-C7 [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller HassController#hass [latest-25016]2025-02-07T09:08:02.299Z <HassController:NOTICE> HassController#hass starting... [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-25016]2025-02-07T09:08:02.301Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-25016]2025-02-07T09:08:02.301Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-25016]2025-02-07T09:08:02.302Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-25016]2025-02-07T09:08:02.367Z <Engine:null> [Engine]Engine#1 config [Object]{ "enabled": true, "wait_all_controllers": true, "startup_wait": 60000, "monitored_entities": [ "vera>device_XXX" ] } [latest-25016]2025-02-07T09:08:02.371Z <VeraController:INFO> VeraController#openLuup performing one-time initialization for VeraController class [latest-25016]2025-02-07T09:08:02.378Z <Controller:INFO> VeraController#openLuup loaded vera capabilities ver 22253 rev 1 format 1 [latest-25016]2025-02-07T09:08:02.398Z <Controller:INFO> VeraController#openLuup loaded implementation data ver 25014 rev 1 format 1 [latest-25016]2025-02-07T09:08:02.398Z <HubitatController:INFO> HubitatController#hubitat-C8 performing one-time initialization for HubitatController class [latest-25016]2025-02-07T09:08:02.399Z <Controller:INFO> HubitatController#hubitat-C8 loaded hubitat capabilities ver 24279 rev 1 format 1 [latest-25016]2025-02-07T09:08:02.407Z <Controller:INFO> HubitatController#hubitat-C8 loaded implementation data ver 24345 rev 1 format 1 [latest-25016]2025-02-07T09:08:02.407Z <HassController:INFO> HassController#hass performing one-time initialization for HassController class [latest-25016]2025-02-07T09:08:02.408Z <Controller:INFO> HassController#hass loaded hass capabilities ver 25004 rev 1 format 1 [latest-25016]2025-02-07T09:08:02.414Z <Controller:INFO> HassController#hass loaded implementation data ver 25004 rev 2 format 1 [latest-25016]2025-02-07T09:08:02.417Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-25016]2025-02-07T09:08:02.421Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.178.201:8123/api/websocket [latest-25016]2025-02-07T09:08:02.424Z <app:NOTICE> Waiting for controllers to start up... [latest-25016]2025-02-07T09:08:02.429Z <HubitatController:NOTICE> HubitatController#hubitat-C8 performing initial connection and inventory [latest-25016]2025-02-07T09:08:02.430Z <HubitatController:NOTICE> HubitatController#hubitat-C7 performing initial connection and inventory [latest-25016]2025-02-07T09:08:02.444Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-25016]2025-02-07T09:08:02.445Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.178.201:8123; fetching initial data... [latest-25016]2025-02-07T09:08:02.490Z <HassController:INFO> HassController#hass Hass reports version "2025.2.0" location Home timezone Europe/Amsterdam state RUNNING safe_mode false [latest-25016]2025-02-07T09:08:02.493Z <HassController:ERR> HassController#hass reported Hass version "2025.2.0" is not supported! [latest-25016]2025-02-07T09:08:02.519Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant [latest-25016]2025-02-07T09:08:02.528Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-25016]2025-02-07T09:08:02.535Z <HassController:NOTICE> HassController#hass no signature match for tts.google_en_com [latest-25016]2025-02-07T09:08:02.536Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_4 [latest-25016]2025-02-07T09:08:02.536Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_3 [latest-25016]2025-02-07T09:08:02.537Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_1 [latest-25016]2025-02-07T09:08:02.537Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_2 [latest-25016]2025-02-07T09:08:02.561Z <HassController:NOTICE> HassController#hass no signature match for update.hacs_update [latest-25016]2025-02-07T09:08:02.562Z <HassController:NOTICE> HassController#hass no signature match for update.entso_e_transparency_platform_update [latest-25016]2025-02-07T09:08:02.563Z <HassController:NOTICE> HassController#hass no signature match for update.hubitat_update [latest-25016]2025-02-07T09:08:02.564Z <HassController:NOTICE> HassController#hass no signature match for update.power_flow_card_update [latest-25016]2025-02-07T09:08:02.564Z <HassController:NOTICE> HassController#hass no signature match for update.apexcharts_card_update [latest-25016]2025-02-07T09:08:02.574Z <HassController:NOTICE> HassController#hass no signature match for update.netdrive_dsm_update [latest-25016]2025-02-07T09:08:02.605Z <HassController:NOTICE> HassController#hass no signature match for event.sun_screens [latest-25016]2025-02-07T09:08:02.615Z <HassController:NOTICE> HassController#hass no signature match for remote.woonkamer [latest-25016]2025-02-07T09:08:02.642Z <HassController:NOTICE> HassController#hass no signature match for update.fritz_box_5590_fiber_fritz_os [latest-25016]2025-02-07T09:08:02.647Z <HassController:NOTICE> HassController#hass no signature match for event.garage_door_motor_button_1 [latest-25016]2025-02-07T09:08:02.647Z <HassController:NOTICE> HassController#hass no signature match for event.garage_door_motor_button_2 [latest-25016]2025-02-07T09:08:02.686Z <HassController:NOTICE> HassController#hass no signature match for hubitat.hub [latest-25016]2025-02-07T09:08:02.688Z <HassController:NOTICE> HassController#hass no signature match for image.fritz_box_5590_fiber_rbguestaccess [latest-25016]2025-02-07T09:08:02.764Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-25016]2025-02-07T09:08:02.770Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-25016]2025-02-07T09:08:02.779Z <HubitatController:INFO> HubitatController#hubitat-C7 Maker API responded with 21 devices [latest-25016]2025-02-07T09:08:02.814Z <HubitatController:WARN> HubitatController#hubitat-C7 native capability URL no definition data; skipped [latest-25016]2025-02-07T09:08:02.827Z <Controller:INFO> HubitatController#hubitat-C7 0 dead entities older than 86400000s purged [latest-25016]2025-02-07T09:08:02.827Z <HubitatController:NOTICE> HubitatController#hubitat-C7 A connection health probe device was not configured. A randomly-selected device will be used. [latest-25016]2025-02-07T09:08:02.827Z <HubitatController:NOTICE> Please refer to the HubitatController configuration docs for more information. [latest-25016]2025-02-07T09:08:02.829Z <HubitatController:INFO> HubitatController#hubitat-C7 connecting to hub's eventsocket WebSocket API at ws://192.168.178.107/eventsocket [latest-25016]2025-02-07T09:08:02.833Z <HubitatController:INFO> HubitatController#hubitat-C8 Maker API responded with 66 devices [latest-25016]2025-02-07T09:08:02.881Z <HubitatController:WARN> HubitatController#hubitat-C8 native capability URL no definition data; skipped [latest-25016]2025-02-07T09:08:02.899Z <Controller:INFO> HubitatController#hubitat-C8 0 dead entities older than 86400000s purged [latest-25016]2025-02-07T09:08:02.899Z <HubitatController:NOTICE> HubitatController#hubitat-C8 A connection health probe device was not configured. A randomly-selected device will be used. [latest-25016]2025-02-07T09:08:02.899Z <HubitatController:NOTICE> Please refer to the HubitatController configuration docs for more information. [latest-25016]2025-02-07T09:08:02.900Z <HubitatController:INFO> HubitatController#hubitat-C8 connecting to hub's eventsocket WebSocket API at ws://192.168.178.104/eventsocket [latest-25016]2025-02-07T09:08:02.993Z <Controller:INFO> VeraController#openLuup 0 dead entities older than 86400000s purged [latest-25016]2025-02-07T09:08:02.994Z <Controller:NOTICE> Controller VeraController#openLuup is now online. [latest-25016]2025-02-07T09:08:03.015Z <HubitatController:INFO> HubitatController#hubitat-C8 successful connection to ws://192.168.178.104/eventsocket [latest-25016]2025-02-07T09:08:03.016Z <HubitatController:INFO> HubitatController#hubitat-C7 successful connection to ws://192.168.178.107/eventsocket [latest-25016]2025-02-07T09:08:03.078Z <HubitatController:NOTICE> HubitatController#hubitat-C8 current mode is Home (65) [latest-25016]2025-02-07T09:08:03.117Z <VeraController:NOTICE> VeraController#openLuup reload detected (status query with LoadTime 1733911518 in response; expected "1469238424") [latest-25016]2025-02-07T09:08:03.164Z <HubitatController:NOTICE> HubitatController#hubitat-C7 current mode is Home (6) [latest-25016]2025-02-07T09:08:03.168Z <Controller:NOTICE> Controller HubitatController#hubitat-C8 is now online. [latest-25016]2025-02-07T09:08:03.185Z <HubitatController:WARN> HubitatController#hubitat-C7 'Allow control of HSM' appears to be disabled in your Maker API configuration [latest-25016]2025-02-07T09:08:03.186Z <Controller:NOTICE> Controller HubitatController#hubitat-C7 is now online. [latest-25016]2025-02-07T09:08:03.186Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups [latest-25016]2025-02-07T09:08:03.199Z <app:NOTICE> All 6 controllers successfully started.Cheers Rene
-
Did you refresh the page?
-
Yes, clear status messages. Click reload. Wait until I see Connected and then go to the status page to see them in alerts.
@mrFarmer said in [SOLVED]Hass websocket falsely reporting ready on boot??:
Yes, clear status messages. Click reload. Wait until I see Connected and then go to the status page to see them in alerts.
When you say reload do you mean "Restart Reactor" from the "Tool" menu? If so, the alarm will show right back until you refresh the page or restart your browser again. In my case the messages are only transitory following a "Restart Reactor" and are gone after I refresh the page.
-
@mrFarmer said in [SOLVED]Hass websocket falsely reporting ready on boot??:
Yes, clear status messages. Click reload. Wait until I see Connected and then go to the status page to see them in alerts.
When you say reload do you mean "Restart Reactor" from the "Tool" menu? If so, the alarm will show right back until you refresh the page or restart your browser again. In my case the messages are only transitory following a "Restart Reactor" and are gone after I refresh the page.
-
The alerts persisting is a sync problem with the alerts data object. I've found and (hopefully) fixed it for the next build. Both it and the Controller Status widget need special handing when the API connection is restarted.
-
T toggledbits locked this topic
