Sensor values become Unavailable frequently

[ReplicaObscura]

System Health details

System Information

version	core-2023.5.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.10.11
os_name	Linux
os_version	6.1.25
arch	x86_64
timezone	America/New_York
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4985
Installed Version	1.32.1
Stage	running
Available Repositories	1362
Downloaded Repositories	152
HACS Data	ok

Home Assistant Cloud

logged_in	true
subscription_expiration	June 15, 2023 at 8:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	us-east-1-0.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.1
update_channel	stable
supervisor_version	supervisor-2023.04.1
agent_version	1.5.1
docker_version	23.0.3
disk_total	76.2 GB
disk_used	55.1 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Samba share (10.0.1), Log Viewer (0.15.0), chrony (2.5.0), AppDaemon (0.12.2), Mosquitto broker (6.2.1), Home Assistant Google Drive Backup (0.110.4), Terminal & SSH (9.7.0), InfluxDB (4.6.0), Studio Code Server (5.5.7), Git pull (7.13.1), MariaDB (2.6.1), Node-RED (14.1.5), Network UPS Tools (0.11.2), phpMyAdmin (0.8.5), Z-Wave JS UI (1.12.0), phpVirtualBox (dev), Uptime Kuma (0.7.3), ESPHome (2023.5.0), Music Assistant BETA (2.0.0b30), Speedtest (1.5.0), EMHASS (0.3.7), Whisper (0.2.0), Piper (0.1.2), Matter Server (4.3.1), OpenThread Border Router (1.2.0)

Dashboards

dashboards	8
resources	82
views	50
mode	storage

Recorder

oldest_recorder_run	May 8, 2023 at 1:57 PM
current_recorder_run	May 16, 2023 at 9:54 AM
estimated_db_size	2542.31 MiB
database_engine	mysql
database_version	10.6.12

Checklist

• I have enabled debug logging for my installation.
• 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

1. Set up at least one Aquanta device in Home Assistant
2. Let the statistics collect for a day or so, and then check the graph

Debug logs

n/a

Diagnostics dump

No response

[ReplicaObscura]

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.

[capritzl]

I receive the following log multiple times during the day. I don't know if this is anything I should be concerned about.

This error originated from a custom integration.

Logger: custom_components.aquanta
Source: helpers/update_coordinator.py:432
integration: Aquanta (documentation, issues)
First occurred: 7:41:24 AM (1 occurrence)
Last logged: 7:41:24 AM

Timeout fetching aquanta data