Replies: 3 comments 3 replies
-
That is a climate entity not a sensor entity. You can create a template sensor out of the climate attributes to achieve this. |
Beta Was this translation helpful? Give feedback.
-
In general, it's a good practices for integration to provide two entities : one climate for control et one temperature sensor for history. The Netatmo integration should be updated to provide a sensor by default. Matter and HomeKit provide an additional temperature sensor that purpose. |
Beta Was this translation helpful? Give feedback.
-
It should absolutely be introdused support for climate entities, as we then could/should see actual AND target temperatures on the area card. that would be great.. just like we've had on Dwains Dashboard all along. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The problem
I want to set my temperature sensor for area. I go to the areas, select one and see that i have no compatible entities:
But i do have a netatmo thermostat in that area:
Is that a bug or maybe that expected and i need to create a derivative to support that?
What version of Home Assistant Core has the issue?
core-2025.4.0
What type of installation are you running?
Home Assistant OS
I created a bug ticket for that in core repository, but they redirected me here: home-assistant/core#142177
Beta Was this translation helpful? Give feedback.
All reactions