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 have filled out the issue template to the best of my ability.
This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
This issue is not a duplicate issue of currently previous issues..
Describe the issue
Sensor values such as temperature go unavailable when the API can't be reached, which seems to happen quite often (usually many times per day).
During those times, you see "unavailable" instead of it maintaining the previous value, which is what causes gaps in the history.
Figuring out why it goes unavailable so often is probably the first thing we need to do. If there's no way to avoid that happening, then it needs to be decided whether we should maintain the previous values (potentially being incorrect, but still more useful than seeing Unavailable regularly) in that scenario.
Reproduction steps
Set up at least one Aquanta device in Home Assistant
Let the statistics collect for a day or so, and then check the graph
Debug logs
n/a
Diagnostics dump
No response
The text was updated successfully, but these errors were encountered:
This is following up on the issue mentioned in #28, which has a bit of additional information and a screenshot of the history graph containing lots of gaps.
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Checklist
Describe the issue
Sensor values such as temperature go unavailable when the API can't be reached, which seems to happen quite often (usually many times per day).
During those times, you see "unavailable" instead of it maintaining the previous value, which is what causes gaps in the history.
Figuring out why it goes unavailable so often is probably the first thing we need to do. If there's no way to avoid that happening, then it needs to be decided whether we should maintain the previous values (potentially being incorrect, but still more useful than seeing Unavailable regularly) in that scenario.
Reproduction steps
Debug logs
Diagnostics dump
No response
The text was updated successfully, but these errors were encountered: