-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Ignore unavailable #2
Comments
Does the sensor write anything to the logs when one of the sources is unavailable? I would like to see the logs. This will greatly accelerate the work. |
this would be great, like in the min_max platform, if the state of sensors are unknown pls ignore them. Now: if one sensors state is unknown the average value is also unknown. |
|
Please test this version of sensor: |
…ache-v2.1.4 Bump actions/cache from v2 to v2.1.4
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
Yes, if one of the entities goes unavailable, the sensor output is 'unknown'
Describe the solution you'd like
If I have 5 sensors and one goes offline, ignore the offline one and give me the average reading of the remaining 4.
Describe alternatives you've considered
Using a template sensor ignores the unavailable entity, but of course treats it as zero, which skews the average for the remaining sensors.
The text was updated successfully, but these errors were encountered: