-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group sensor warnings: Unable to use state. Only numerical states are supported, entity sensor.xxx with value unavailable excluded from calculation #87924
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) group documentation |
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. |
That was not solved with the latest version. |
same warning for me; |
Same problem in version 2023.7 |
What i did as fix. Is create in a template, and give the sensor a default value:
|
Version | core-2023.10.5 |
I've got a PR lined up to fix this issue #102828 |
I have this issue as well. Thanks @mill1000 for creating a PR. Sadly no one has reviewed it yet, hope this will happen soon. |
Same here; it would be great if someone from HA Team could review the PR. |
The problem
The new sensor group is awesome, so I migrated a bunch of my template sensors (usually just sum up values of multiple power sensors, or taking the average temperature at home, etc.) to groups and have used the option to ignore non numeric, as a sensor might go out for some reason and I still want to calculate the results taking in account only the other sensors.
However with this option a warning is registered in the log every time one of the sensors inside a group is not numeric (unavailable), which means lots of new warnings during the startup.
If I already selected to ignore non numeric values that means I know that situation will happen and don't need a warning for that.
What version of Home Assistant Core has the issue?
2023.2.3
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
Group
Link to integration documentation on our website
https://www.home-assistant.io/integrations/group/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: