Hi,
I am almost ready to toss home assistant out the door…incredibly frustrated at the inability to upgrade hassio (or any add ons for that matter) without my system rebooting half way through.
Running on a Rasberry Pi with Samsung 250Gb SSD, plenty of power and unplugged everying else as well as stopped all add ons before upgrading.
Any suggestions before I stamp on it!
Invest your time in learning or you will be stamping this and everything else for that matter.
Have spent plenty of time on the learning, but it really has me beat this time!
Well then… have a few bears and sleep over it.
A suggestion would be to try to get logged what the errors are. Connect a screen and take a picture with your phone in worst case.
Here is the latest error log…
Cannot connect to InfluxDB due to 'HTTPConnectionPool(host='a0d7b954-influxdb', port=8086): Max retries exceeded with url: /write?db=homeassistant (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f813d3250>: Failed to establish a new connection: [Errno -5] Name has no usable address'))'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible. Retrying in 60 seconds.
8:36:18 AM – (ERROR) InfluxDB - message first occurred at 12:06:27 AM and shows up 481 times
Could not fetch stats for a0d7b954_nodered: 404 Client Error for http+docker://localhost/v1.43/containers/addon_a0d7b954_nodered/json: Not Found ("No such container: addon_a0d7b954_nodered")
8:35:41 AM – (WARNING) Home Assistant Supervisor - message first occurred at 12:05:37 AM and shows up 505 times
Unexpected ConnectionFailure trying to get remote for 192.168.2.73, please report this issue: ConnectionFailure({'event': 'ms.channel.timeOut'})
8:34:55 AM – (WARNING) Samsung Smart TV - message first occurred at 12:27:01 AM and shows up 21 times
[Zachs HomeHub(192.168.2.51):8009] Heartbeat timeout, resetting connection
8:34:34 AM – (WARNING) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py
Host 192.168.1.44:443: unknown exception "API error during login of host 192.168.1.44:443: API returned HTTP status ERROR code 502/Bad Gateway" occurred, traceback: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 800, in login json_data = await self.send(body, param, expected_response_type="json") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3603, in send return await self.send_chunk(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3816, in send_chunk raise err File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3748, in send_chunk return await self.send(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3603, in send return await self.send_chunk(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3816, in send_chunk raise err File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3748, in send_chunk return await self.send(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3603, in send return await self.send_chunk(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3816, in send_chunk raise err File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3752, in send_chunk raise ApiError(f"API returned HTTP status ERROR code {response.status}/{response.reason}") reolink_aio.exceptions.ApiError: API returned HTTP status ERROR code 502/Bad Gateway The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3748, in send_chunk return await self.send(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3603, in send return await self.send_chunk(body, param, expected_response_type, retry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 3671, in send_chunk await self.login() File "/usr/local/lib/python3.11/site-packages/reolink_aio/api.py", line 802, in login raise LoginError(f"API error during login of host {self._host}:{self._port}: {str(err)}") from err reolink_aio.exceptions.LoginError: API error during login of host 192.168.1.44:443: API returned HTTP status ERROR code 502/Bad Gateway
6:38:52 AM – (ERROR) components/reolink/host.py - message first occurred at 2:00:08 AM and shows up 16 times
Error fetching reolink.GardenCam data: API error during login of host 192.168.1.44:443: API returned HTTP status ERROR code 502/Bad Gateway
6:37:43 AM – (ERROR) Reolink IP NVR/camera - message first occurred at 2:00:10 AM and shows up 4 times
Error fetching shellydimmer-D0EBA3 data: Error fetching data: DeviceConnectionError()
5:04:07 AM – (ERROR) Shelly
[Zachs HomeHub(192.168.2.51):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.2.51', 8009)), retrying in 5.0s
2:27:23 AM – (ERROR) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py
[Zachs HomeHub(192.168.2.51):8009] Error communicating with socket, resetting connection
2:27:22 AM – (WARNING) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py
[Zachs HomeHub(192.168.2.51):8009] Error reading from socket.
2:27:22 AM – (ERROR) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py
Error fetching WiZ Dimmable White 231444 data: Failed to update device at 192.168.1.58:
1:08:36 AM – (ERROR) WiZ
Entity sensor.ebusd_bai_prenergysumhc2 (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'kWh', 'MWh', 'Wh', 'GJ']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
12:34:41 AM – (WARNING) Sensor - message first occurred at 12:06:17 AM and shows up 55 times
The unit of sensor.ble_rssi_a4c138ee0ed7 (None) cannot be converted to the unit of previously compiled statistics (dBm). Generation of long term statistics will be suppressed unless the unit changes back to dBm or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
12:13:27 AM – (WARNING) Sensor - message first occurred at 12:07:53 AM and shows up 13 times
The unit of sensor.ble_voltage_a4c138881fa6 (None) cannot be converted to the unit of previously compiled statistics (V). Generation of long term statistics will be suppressed unless the unit changes back to V or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
12:07:53 AM – (WARNING) Sensor - message first occurred at 12:07:53 AM and shows up 9 times
MQTT entity name starts with the device name in your config {'unique_id': 'ebusd_bai_TemplimiterWithNTC_0', 'name': 'ebusd bai TemplimiterWithNTC ', 'device': {'identifiers': ['ebusd_bai'], 'manufacturer': 'ebusd.eu', 'name': 'ebusd bai', 'via_device': 'ebusd', 'sw_version': '23.2', 'suggested_area': 'Heating', 'connections': []}, 'value_template': Template<template=({{value_json["0"].value}}) renders=0>, 'state_topic': 'ebusd/bai/TemplimiterWithNTC', 'device_class': <SensorDeviceClass.ENUM: 'enum'>, 'force_update': False, 'qos': 0, 'payload_available': 'online', 'encoding': 'utf-8', 'availability_mode': 'latest', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'TemplimiterWithNTC '
12:07:26 AM – (WARNING) MQTT - message first occurred at 12:06:32 AM and shows up 86 times
You have 'maykar/kiosk-mode' installed with HACS this repository has been removed from HACS, please consider removing it. Removal reason (Repository is archived)
12:07:14 AM – (WARNING) HACS (custom integration)
HomeKit Sir Terence III door lock cannot startup: entity not available: {'include_domains': [], 'exclude_domains': [], 'include_entities': ['lock.sir_terence_iii_door_lock'], 'exclude_entities': [], 'include_entity_globs': [], 'exclude_entity_globs': []}
12:07:14 AM – (ERROR) HomeKit Bridge - message first occurred at 12:07:14 AM and shows up 4 times
Waiting on integrations to complete setup: reolink
12:06:38 AM – (WARNING) bootstrap.py
Config entry 'Shapes 2129' for nanoleaf integration not ready yet; Retrying in background
12:06:37 AM – (WARNING) config_entries.py - message first occurred at 12:05:35 AM and shows up 8 times
Can't connect to ESPHome API for new-irrigation @ 192.168.3.155: Error connecting to ('192.168.3.155', 6053): [Errno 113] Connect call failed ('192.168.3.155', 6053) (SocketAPIError)
12:06:35 AM – (WARNING) runner.py - message first occurred at 12:06:35 AM and shows up 4 times
Config entry 'Gavin' for withings integration could not authenticate: Error code 401
12:06:35 AM – (WARNING) config_entries.py
Platform esphome does not generate unique IDs. ID new-irrigationswitchsonoff_basic_relay already exists - ignoring switch.sonoff_basic_relay
12:06:31 AM – (ERROR) Switch
Error setting up entry Default for unifi
12:06:29 AM – (ERROR) config_entries.py
Dashboard unavailable; skipping reauth: Cannot connect to host 127.0.0.1:63230 ssl:default [Connect call failed ('127.0.0.1', 63230)]
12:06:29 AM – (ERROR) ESPHome
Error requesting ESPHome Dashboard data: Cannot connect to host 127.0.0.1:63230 ssl:default [Connect call failed ('127.0.0.1', 63230)]
12:06:29 AM – (ERROR) ESPHome
Error setting up entry Meater for meater
12:06:26 AM – (ERROR) config_entries.py
Authentication required for Account. (421)
12:06:18 AM – (ERROR) components/icloud/account.py
Fetched https://alexa-api.nabucasa.com/access_token (400)
12:05:36 AM – (WARNING) components/cloud/alexa_config.py
Ended unfinished session (id=5946 from 2023-12-02 18:47:04.991576)
12:05:29 AM – (WARNING) Recorder
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
12:05:29 AM – (WARNING) Recorder
Looks like your database might be corrupt.
Any suggestions for a fix? Dont particularly want to lose about 4 years worth of data
You have some kind of network problem, if I understand correctly your logs.
You can’t connect to various services, why I don’t know. As database goes this error will pop up if you done hard reboot or didn’t do clean reboot or shutdown. Happened to me numerous times but I never lost data because of it.
Try to check you boot logs to see what is going on. Probably some service or few of them failed to start, but this is just my guess.
Where would I find the boot logs?
Logs on Linux are usually in /var/log directory.
You can check it with dmesg or sudo dmesg from cli using comp running ha.
Also check running services with systemctl.
Well you could test my theory by stopping HA, renaming /config/home-assistant.log to something else like config/home-assistant.log.bkup then starting HA. It will make a new log file.
Yes, but on HAOS they are journal, so
journalctl
on the OS (not the ssh container) is the command you seek.
again, on the OS.