Netatmo Thermostat - Select-entity is "unavailable" (all others are there)

mischung commented 1 year ago

The problem

Hi!

After restarting HA (after an update etc.) the Select-entity of my Netatmo-Thermostat is often "unavailable".

I can only "fix" this problem with several restarts or even re-booting the system.

All other Netatmo-entities are available, so I don't know exactly what's going on here. Maybe a timing issue or so? (I have a Netatmo central smart thermostat controlling our heating boiler and a weather-station)

Unfortunately I don't know, when this was failing, but at some point I realized I selected a specific schedule and my thermostat did not follow...then I realized that this entity was not available.

I also enabled the "debug logging" and pasted the data down below.

Thanks for your help.

Marc

What version of Home Assistant Core has the issue?

2023.2.0

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

Netatmo

Link to integration documentation on our website

https://www.home-assistant.io/integrations/netatmo/#climate

Diagnostics information

config_entry-netatmo-422b349dde0990688bc68099551bbd77.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-02-02 07:43:04.022 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher account added
2023-02-02 07:43:04.128 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather added
2023-02-02 07:43:04.201 DEBUG (MainThread) [pyatmo.helpers] Server response: {'body': {'devices': [], 'user': {'mail': '...@....de', 'administrative': {'lang': 'de', 'reg_locale': 'de-DE', 'country': 'DE_DE', 'unit': 0, 'windunit': 0, 'pressureunit': 0, 'feel_like_algo': 0}}}, 'status': 'ok', 'time_exec': 0.023328781127929688, 'time_server': 1675320184}
2023-02-02 07:43:04.202 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] No device data available
2023-02-02 07:43:04.202 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care added
2023-02-02 07:43:04.334 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher home-... added
2023-02-02 07:43:04.336 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather removed
2023-02-02 07:43:04.336 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care removed
2023-02-02 07:43:04.431 DEBUG (MainThread) [pyatmo.auth] addwebhook: <ClientResponse(https://api.netatmo.com/api/addwebhook) [200 OK]>
<CIMultiDictProxy('Server': 'nginx', 'Date': 'Thu, 02 Feb 2023 06:43:04 GMT', 'Content-Type': 'application/json; charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache, must-revalidate', 'Expires': '0', 'X-XSS-Protection': '1; mode=block', 'Access-Control-Allow-Origin': '*', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Powered-By': 'Netatmo')>
2023-02-02 07:43:04.434 INFO (MainThread) [homeassistant.components.netatmo] Register Netatmo webhook: https://hooks....
2023-02-02 07:43:04.530 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather added

Additional information

No response

home-assistant[bot] commented 1 year ago

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

Code owner commands

Code owners of `netatmo` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign netatmo` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core