Intrégration worked momentarily, then failed just prior to reduction phase

[Fphaneuf]

Describe the bug

Integration worked momentarily, then failed just prior to reduction phase; integrations entities depopulated. Rebooting did not
fix its entity's status. This resulted in Défi Hilo reduction phase was not activated, so my central heating ran for 2 hours 30 minutes at the beginning of the 4 hours Défi windows, meaning cost 5 time the regular Tariff D price !!! very costly.

-->

Version of the custom_component

I have the latest version 2026.3 Beta (read Beta too late tabar..)
-->

Configuration

Found no YAML related to Hilo worth mentioning. Please be clearer on this requirement.

Add your logs here.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-02-01 09:16:59.303 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.304 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.304 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration rd200_ble which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.304 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.305 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration neviweb130 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.305 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hilo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration rd200_ble which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.307 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.307 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration neviweb130 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.307 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hilo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.307 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:16:59.307 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-02-01 09:17:02.486 WARNING (zeroconf-ServiceBrowser-_googlecast._tcp-145) [pychromecast.dial] Failed to determine cast type for host (<urlopen error [Errno 101] Network unreachable>) (services:{MDNSServiceInfo(name='BRAVIA-4K-VH22-e1d919c819348425fe951271a2ce2467._googlecast._tcp.local.')})
2026-02-01 09:17:04.145 WARNING (MainThread) [py.warnings] /usr/local/lib/python3.13/site-packages/gql/transport/aiohttp.py:92: UserWarning: WARNING: By default, AIOHTTPTransport does not verify ssl certificates. This will be fixed in the next major version. You can set ssl=True to force the ssl certificate verification or ssl=False to disable this warning
warnings.warn(

2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading <Reading last_status_time 2026-01-29T07:15:10.280Z>
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading <Reading version 9.5.0>
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading <Reading zigbee_channel 15>
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.508 WARNING (MainThread) [pyhilo] Unable to find device 0 for reading
2026-02-01 09:17:04.577 WARNING (MainThread) [pyhilo] Delaying invoke SubscribeToLocation 0 [95736]: Websocket not ready.
2026-02-01 09:17:04.580 WARNING (MainThread) [pyhilo] Delaying invoke SubscribeToLocation 0 [95736]: Websocket not ready.
2026-02-01 09:17:04.595 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:04.596 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:04.644 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:04.645 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:14.940 WARNING (MainThread) [homeassistant.components.sensor.helpers] sensor.prochaine_preheat rendered invalid timestamp:
2026-02-01 09:17:14.940 WARNING (MainThread) [homeassistant.components.sensor.helpers] sensor.prochaine_reduction rendered invalid timestamp:
2026-02-01 09:17:14.941 WARNING (MainThread) [homeassistant.components.sensor.helpers] sensor.prochaine_recuperation rendered invalid timestamp:
2026-02-01 09:17:35.018 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.018 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.019 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.019 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.019 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.019 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.020 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:35.020 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 09:17:40.871 WARNING (MainThread) [aioecowitt.server] Unhandled sensor type gain10_piezo value 1.00
2026-02-01 09:17:40.871 WARNING (MainThread) [aioecowitt.server] Unhandled sensor type gain20_piezo value 1.00
2026-02-01 09:17:40.871 WARNING (MainThread) [aioecowitt.server] Unhandled sensor type gain30_piezo value 1.00
2026-02-01 09:17:40.871 WARNING (MainThread) [aioecowitt.server] Unhandled sensor type gain40_piezo value 1.00
2026-02-01 09:17:40.871 WARNING (MainThread) [aioecowitt.server] Unhandled sensor type gain50_piezo value 1.00
2026-02-01 10:00:00.770 ERROR (MainThread) [custom_components.hilo] Error in websocket handler handle_challenge_details_update: 'list' object has no attribute 'get'
2026-02-01 10:00:00.812 ERROR (MainThread) [custom_components.hilo] Traceback (most recent call last):
File "/config/custom_components/hilo/init.py", line 380, in _handle_websocket_message
await handler(arguments[0])
File "/config/custom_components/hilo/sensor.py", line 719, in handle_challenge_details_update
if challenge.get("id") is None or challenge.get("phases") is None:
^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'get'

2026-02-01 10:00:03.097 ERROR (MainThread) [custom_components.hilo] Error in websocket handler handle_challenge_details_update: 'list' object has no attribute 'get'
2026-02-01 10:00:03.097 ERROR (MainThread) [custom_components.hilo] Traceback (most recent call last):
File "/config/custom_components/hilo/init.py", line 380, in _handle_websocket_message
await handler(arguments[0])
File "/config/custom_components/hilo/sensor.py", line 719, in handle_challenge_details_update
if challenge.get("id") is None or challenge.get("phases") is None:
^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'get'

2026-02-01 10:45:48.409 ERROR (Thread-5) [pychromecast.socket_client] [SONY XR-55A80L(fd25:99fe:700b:ecad:2164:e9a2:41f7:3247):8009] Failed to connect to service HostServiceInfo(host='fd25:99fe:700b:ecad:2164:e9a2:41f7:3247', port=8009), retrying in 5.0s
2026-02-01 11:00:01.099 ERROR (MainThread) [custom_components.hilo] Error in websocket handler handle_challenge_details_update: 'list' object has no attribute 'get'
2026-02-01 11:00:01.100 ERROR (MainThread) [custom_components.hilo] Traceback (most recent call last):
File "/config/custom_components/hilo/init.py", line 380, in _handle_websocket_message
await handler(arguments[0])
File "/config/custom_components/hilo/sensor.py", line 719, in handle_challenge_details_update
if challenge.get("id") is None or challenge.get("phases") is None:
^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'get'

2026-02-01 11:00:03.399 ERROR (MainThread) [custom_components.hilo] Error in websocket handler handle_challenge_details_update: 'list' object has no attribute 'get'
2026-02-01 11:00:03.399 ERROR (MainThread) [custom_components.hilo] Traceback (most recent call last):
File "/config/custom_components/hilo/init.py", line 380, in _handle_websocket_message
await handler(arguments[0])
File "/config/custom_components/hilo/sensor.py", line 719, in handle_challenge_details_update
if challenge.get("id") is None or challenge.get("phases") is None:
^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'get'

2026-02-01 11:17:35.294 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.294 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.294 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.294 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.295 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.295 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.295 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.295 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:17:35.295 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated
2026-02-01 11:27:08.750 ERROR (Thread-5) [pychromecast.socket_client] [SONY XR-55A80L(fd25:99fe:700b:ecad:2164:e9a2:41f7:3247):8009] Failed to connect to service HostServiceInfo(host='fd25:99fe:700b:ecad:2164:e9a2:41f7:3247', port=8009), retrying in 5.0s
2026-02-01 12:04:19.029 ERROR (Thread-5) [pychromecast.socket_client] [SONY XR-55A80L(fd25:99fe:700b:ecad:2164:e9a2:41f7:3247):8009] Failed to connect to service HostServiceInfo(host='fd25:99fe:700b:ecad:2164:e9a2:41f7:3247', port=8009), retrying in 5.0s
2026-02-01 12:24:15.068 ERROR (Thread-5) [pychromecast.socket_client] [SONY XR-55A80L(fd25:99fe:700b:ecad:2164:e9a2:41f7:3247):8009] Failed to connect to service HostServiceInfo(host='fd25:99fe:700b:ecad:2164:e9a2:41f7:3247', port=8009), retrying in 5.0s
2026-02-01 12:30:59.681 ERROR (MainThread) [pyhilo] Received close event from SignalR: Error: CLOSE Target: Args: Error: Connection closed with an error. OperationCanceledException: Client hasn't sent a message/ping within the configured ClientTimeoutInterval.
2026-02-01 12:30:59.681 ERROR (MainThread) [pyhilo] Received close event from SignalR: Error: CLOSE Target: Args: Error: Application server closed the connection.
2026-02-01 12:30:59.681 ERROR (MainThread) [pyhilo] Websocket: Received event to close connection: 8
2026-02-01 12:30:59.681 ERROR (MainThread) [pyhilo] Websocket: Closed while listening: Connection was closed.
2026-02-01 12:30:59.681 ERROR (MainThread) [pyhilo] Connection was closed.
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/pyhilo/websocket.py", line 348, in async_listen
messages = await self._async_receive_json()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pyhilo/websocket.py", line 176, in _async_receive_json
raise ConnectionClosedError("Connection was closed.")
pyhilo.exceptions.ConnectionClosedError: Connection was closed.
2026-02-01 12:30:59.683 WARNING (MainThread) [custom_components.hilo] Unhandled websocket event: WebsocketEvent(event_type_id=7, target='', arguments='', invocation=None, error="Connection closed with an error. OperationCanceledException: Client hasn't sent a message/ping within the configured ClientTimeoutInterval.", timestamp=datetime.datetime(2026, 2, 1, 9, 17, 2, 255290), event_type='CLOSE')
2026-02-01 12:30:59.683 WARNING (MainThread) [custom_components.hilo] Unhandled websocket event: WebsocketEvent(event_type_id=7, target='', arguments='', invocation=None, error='Application server closed the connection.', timestamp=datetime.datetime(2026, 2, 1, 9, 17, 2, 255290), event_type='CLOSE')
2026-02-01 12:31:04.774 ERROR (MainThread) [pyhilo] Unable to connect to WS server 401, message='Invalid response REDACTED
2026-02-01 12:31:04.774 WARNING (MainThread) [custom_components.hilo] Invalid credentials? Refreshing websocket infos
2026-02-01 12:31:10.102 WARNING (MainThread) [pyhilo] Delaying invoke SubscribeToLocation 0 [95736]: Websocket not ready.
2026-02-01 12:31:10.121 WARNING (MainThread) [custom_components.hilo] Starting legacy connection to ChallengeHub. Your tarif is rate d, and will also attempt connection. This can be safely ignored. This will be deprecated

[ic-dev21]

I removed your websocket URL as the token is easily decoded and contains personally identifiable info.

Reduction phase starts at 6AM, your logs do not, so I'd be hard pressed to give any reasonable answer to your issue.

If you restarted in the meantime there should be a log.1 file in /config that may have more info.

[ic-dev21]

Integration worked momentarily, then failed just prior to reduction phase; integrations entities depopulated. Rebooting did not fix its entity's status. This resulted in Défi Hilo reduction phase was not activated, so my central heating ran for 2 hours 30 minutes at the beginning of the 4 hours Défi windows, meaning cost 5 time the regular Tariff D price !!! very costly.

Your logs say you're configured as rate D, not flex D, so which is it?

[Fphaneuf]

We are at Flex D since this winter

[Fphaneuf]

I removed your websocket URL as the token is easily decoded and contains personally identifiable info.

Reduction phase starts at 6AM, your logs do not, so I'd be hard pressed to give any reasonable answer to your issue.

If you restarted in the meantime there should be a log.1 file in /config that may have more info.

There is no log.1 file in there

[ic-dev21]

We are at Flex D since this winter

Please configure your component accordingly as HQ has split websocket messages between the rates, so a person on flex D is not receiving messages for Winter credits and the reverse is also true. I cannot debug flex D as I don't have a flex D account, I relied on some jsons I was able to get from other users. It should work fine in theory.

[Fphaneuf]

This has been working fine since the beginning in December. If what you mean is to re-read the integration's instructions for Flex D to be applied, will do.
I understand that there may be changes in all the resources involved in this mechanism.
Thanks for your quick reaction Ian.
Francois.

[Fphaneuf]

I confirm that the latest upgrade changed the configuration to Tarif D, so returned-it to Flex D

[ic-dev21]

I confirm that the latest upgrade changed the configuration to Tarif D, so returned-it to Flex D

Not saying this is the root cause but it could be a factor.

[Fphaneuf]

Again , I did not mean to point directly to it as the roor cause Ian. I meant that the upgrade "tickled" the sensitivity of the workflow .. I tend to be good at being where unseen stuff is hidden, and I swear that I don't do this on purpose ! ;)

[ic-dev21]

Again , I did not mean to point directly to it as the roor cause Ian. I meant that the upgrade "tickled" the sensitivity of the workflow .. I tend to be good at being where unseen stuff is hidden, and I swear that I don't do this on purpose ! ;)

What bothers me is how it changed on you. There is a default value but HA should be the one to remember what you chose in your config...