[SOLVED]Hass websocket falsely reporting ready on boot??
-
You must have
wait_all_controllers: true
in your config orstartup_wait
isn't used at all.The
controllers
section 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
-
-
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_controllers
means 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.