You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know when it started to happened but, using a Netatmo thermostat and the Netatmo integration to get the climate I realized about a weird behaviour.
Home Assistant Netatmo integration exposes a select entity to choose a Netatmo plan/scheduler. These plans are already set up in Netatmo app.
I was trying to use this select entity to trigger an automation on a value change but this is not yet possible. The select is not updated. If you change the value in Lovelace the change is set up in Netatmo, but not updated in the HA entity. Furthermore, if I change the value in Netatmo app, the change is not propagate to HA.
It is a pitty, but this behaviour is not reflected in the registry, in fact there is nothing in the logs when I change the value of the select
Thank you
What version of Home Assistant Core has the issue?
24.4.3
What was the last working version of Home Assistant Core?
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 Renames 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.
@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.
The problem
Hi there!
I don't know when it started to happened but, using a Netatmo thermostat and the Netatmo integration to get the climate I realized about a weird behaviour.
Home Assistant Netatmo integration exposes a select entity to choose a Netatmo plan/scheduler. These plans are already set up in Netatmo app.
I was trying to use this select entity to trigger an automation on a value change but this is not yet possible. The select is not updated. If you change the value in Lovelace the change is set up in Netatmo, but not updated in the HA entity. Furthermore, if I change the value in Netatmo app, the change is not propagate to HA.
It is a pitty, but this behaviour is not reflected in the registry, in fact there is nothing in the logs when I change the value of the select
Thank you
What version of Home Assistant Core has the issue?
24.4.3
What was the last working version of Home Assistant Core?
IDK
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: