Integration regularly becomes unavailable

Krispkiwi commented 5 months ago

System Health details

System Information

version	core-2024.2.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.1
os_name	Linux
os_version	6.1.63-haos-raspi
arch	aarch64
timezone	Pacific/Auckland
config_dir	/config

Home Assistant Community Store

Home Assistant Cloud

Home Assistant Supervisor

host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.02.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 109.3 GB disk_used | 12.5 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.1.1), Studio Code Server (5.15.0), Samba share (12.3.0), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.4.0), RPC Shutdown (2.4), ESPHome (2024.2.0), Cloudflared (5.1.4), Zigbee2MQTT (1.35.3-1), ADB - Android Debug Bridge (0.7.0), MQTT Explorer (browser-1.0.3), Node-RED (17.0.7), Vaultwarden (Bitwarden) (0.21.1), Uptime Kuma (0.12.0)

Dashboards

Recorder

Spotify

api_endpoint_reachable | ok -- | --

Checklist

[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue

It looks like every so often the integration needs to be refreshed as it loses its connection and goes into an unavailable state but reloading any sensor kicks the entire thing back into gear.

Reproduction steps

Install the integration
Wait for it disconnect
Press reload

Debug logs

No response

Diagnostics dump

No response

ciejer commented 5 months ago

Hi @Krispkiwi - could you please add a bit more detail? What exactly goes into "unavailable" state? How are you "refreshing a sensor"?

My home instance is currently sitting at 9 days without dropping (since I reconfigured for the latest version) - any logs would be useful?

Thanks - Chris

Krispkiwi commented 5 months ago

Hi @Krispkiwi - could you please add a bit more detail? What exactly goes into "unavailable" state? How are you "refreshing a sensor"?

My home instance is currently sitting at 9 days without dropping (since I reconfigured for the latest version) - any logs would be useful?

Thanks - Chris

Hey mate, I've enabled debugging on the integration, not sure where to grab the logs from though.

Basically all the sensors in the integration that I have enabled fall into an unavailable state and i get the "This entity is no longer being provided by the metservice_weather integration. If the entity is no longer in use, delete it in settings" message however if I go into the integration and press reload, all sensors I am using from the integration come back online. I probably could automate this to refresh every time they go unavailable but figured its best to report it to you.

kotuku73 commented 5 months ago

Tēnā kōrua, I've had the same experience as @Krispkiwi.

Here's a likely looking snippet from my logs this morning

2024-02-25 20:19:29.581 ERROR (MainThread) [custom_components.metservice_weather.coordinator] Error fetching MetService data: TimeoutError()
2024-02-25 20:19:35.408 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up metservice_weather platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/metservice_weather/sensor.py", line 59, in async_setup_entry
    WeatherSensor(coordinator, description)
  File "/config/custom_components/metservice_weather/sensor.py", line 98, in __init__
    self._sensor_data = _get_sensor_data_public(
                        ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/metservice_weather/sensor.py", line 210, in _get_sensor_data_public
    result = get_from_dict(sensors[RESULTS_CURRENT], keys)
                           ~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Krispkiwi commented 5 months ago

Tēnā kōrua, I've had the same experience as @Krispkiwi.

Here's a likely looking snippet from my logs this morning

2024-02-25 20:19:29.581 ERROR (MainThread) [custom_components.metservice_weather.coordinator] Error fetching MetService data: TimeoutError()
2024-02-25 20:19:35.408 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up metservice_weather platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/metservice_weather/sensor.py", line 59, in async_setup_entry
    WeatherSensor(coordinator, description)
  File "/config/custom_components/metservice_weather/sensor.py", line 98, in __init__
    self._sensor_data = _get_sensor_data_public(
                        ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/metservice_weather/sensor.py", line 210, in _get_sensor_data_public
    result = get_from_dict(sensors[RESULTS_CURRENT], keys)
                           ~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

I can confirm that setting up the entities to reload when they become unavailable seems to solve it from a practical standpoint with a quick automation, it's a workaround for now.

ciejer / metservice-weather