Airzone Cloud Integration: Zone states disappear after initial load and only update on state change

poliolet commented 3 hours ago

The problem

I am experiencing an issue with the Airzone Cloud integration in Home Assistant. Initially, the zone states (e.g., “working”, “stopped”, etc.) appear correctly after restarting Home Assistant. However, after a short period of time, the states disappear and only return when there is an explicit state change (e.g., switching on or off). This issue affects all zones in the Airzone system and happens consistently.

Steps to reproduce

Configure the Airzone Cloud integration in Home Assistant.
Observe that zone states are displayed correctly upon starting Home Assistant.
Wait for some time (or leave the system idle).
Notice that the states for all zones disappear and are no longer updated unless there is a state change (e.g., turning on/off or changing mode).

Expected Behavior:

The zone states should update consistently and remain visible in Home Assistant, regardless of changes or inactivity. (It used to work well before summer)

Additional Information:

This issue happens for all zones, not just specific ones.
The Airzone system is fully operational and works correctly from the Airzone app.
Attempts to resolve the issue included restarting Home Assistant, the Airzone webserver, and ensuring both Home Assistant and the webserver firmware are updated.
The issue persists across updates to Home Assistant.

What version of Home Assistant Core has the issue?

core-2024.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

airzone

Link to integration documentation on our website

https://www.home-assistant.io/integrations/airzone_cloud

Diagnostics information

config_entry-airzone_cloud-d11a1510055cbed35e5bf005e114b9f5.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

The only thing I found when filtering by "airzone" is this little piece:

Diari de registre: aioairzone_cloud.websockets
Font: components/airzone_cloud/coordinator.py:42
Produït per primer cop: 18 de novembre del 2024, a les 14:29:37 (1 ocurrències)
Últim registre: 18 de novembre del 2024, a les 14:29:37

WS[6540e9e78728873c089e6675]: reconnecting...

Additional information

No response

home-assistant[bot] commented 3 hours ago

Hey there @noltari, mind taking a look at this issue as it has been labeled with an integration (airzone_cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `airzone_cloud` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign airzone_cloud` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

airzone_cloud documentation airzone_cloud source _{^{(message by IssueLinks)}}

Noltari commented 2 hours ago

Hi @poliolet,

This isn't an issue on our side since the Airzone Cloud API sends the execution status as Null instead of False when a zone hasn't been on for a short period of time.

Noltari commented 2 hours ago

@home-assistant close

home-assistant / core