Since a recent update to 2023.5.2 my HA instance is now far less stable, and by that I mean the front end (at least) becomes unavailable every day or 2, requiring a host reboot as I cannot determine why it’s crashed and how to restart it without rebooting the host.
Host is Debian 11, up to date, RPi4, 4GB, USB3 SSD boot device, wired ethernet, BT dongle, onboard wifi/bt disabled, genuine power supply.
HA is running in docker, supervised, but unsupported/unhealthy as I run some other containers
Once I SSH the host I can run commands against ha (HA supervisor restart/reload) etc but it does not complete, the Core tells me it’s waiting for the supervisor to finish a task.
journalctl -e show errors about the SD card and sometimes JSION issues (SD no longer in use, but system was SD based previously)
============================================
May 11 09:30:01 HomeAssistant kernel: mmc1: Timeout waiting for hardware cmd interrupt.
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x00000001
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Cmd: 0x00000502 | Max curr: 0x00080008
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: Host ctl2: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
May 11 09:30:01 HomeAssistant kernel: mmc1: sdhci: ============================================
May 11 23:04:56 HomeAssistant c42ba2724294[727]: 2023-05-12 09:04:56.960 WARNING (MainThread) [homeassistant.components.mqtt.mixins] JSON result was not a dictionary>
Supervisor logs show various issues but I will need to wait for a fresh crash for a copy/paste for the latest, here’s smoe examples. It awlays seem to be a bit flakey talking to my offgrid battery BMS (via BT) which is much more stable with the dongle now.
I get an error 500 when the crash occurs and complaints that it cannot restart while waiting for a process to finish - also it sends an exit command to docker but does not receive a reply (I’ll try and capture that on next crash)
This has only been since the latest update (I also have a new HDD caddy on the way from the supported list to be sure as I was having the occassional host hang).
Is there other info I can provide to help?
Thanks in advance.
23-05-12 08:10:20 ERROR (MainThread) [supervisor.resolution.evaluations.container] Found image in unhealthy image list ‘portainer’ on the host
Logger: homeassistant.util.logging
Source: util/logging.py:156
First occurred: May 9, 2023 at 10:28:11 PM (726 occurrences)
Last logged: 12:20:32 PM
Exception in async_discover when dispatching ‘mqtt_discovery_new_binary_sensor_mqtt’: ({‘unique_id’: ‘14kWh_Lifpo4__switch_charge’, ‘name’: ‘14kWh_Lifpo4 charge switch’, ‘device_class’: ‘outlet’, ‘json_attributes_topic’: ‘14kWh_Lifpo4/charge’, ‘expire_after’: 20, ‘device’: {‘identifiers’: [‘2012282166’], ‘name’: ‘JK BMS 150A’, ‘model’: ‘JK-B2A24S15P’, ‘sw_version’: ‘6.1.0S’, ‘hw_version’: ‘6.X’}, ‘state_topic’: ‘14kWh_Lifpo4/switch/charge’, ‘command_topic’: ‘homeassistant/switch/14kWh_Lifpo4/charge/set’, ‘platform’: ‘mqtt’},) Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py”, line 316, in async_discover config: DiscoveryInfoType = discovery_schema(discovery_payload) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 272, in call return self._compiled([], data) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 595, in validate_dict return base_validate(path, iteritems(data), out) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 433, in validate_mapping raise er.MultipleInvalid(errors) voluptuous.error.MultipleInvalid: expected BinarySensorDeviceClass or one of ‘battery’, ‘battery_charging’, ‘carbon_monoxide’, ‘cold’, ‘connectivity’, ‘door’, ‘garage_door’, ‘gas’, ‘heat’, ‘light’, ‘lock’, ‘moisture’, ‘motion’, ‘moving’, ‘occupancy’, ‘opening’, ‘plug’, ‘power’, ‘presence’, ‘problem’, ‘running’, ‘safety’, ‘smoke’, ‘sound’, ‘tamper’, ‘update’, ‘vibration’, ‘window’ for dictionary value @ data[‘device_class’]
Exception in async_discover when dispatching ‘mqtt_discovery_new_binary_sensor_mqtt’: ({‘unique_id’: ‘14kWh_Lifpo4__switch_discharge’, ‘name’: ‘14kWh_Lifpo4 discharge switch’, ‘device_class’: ‘outlet’, ‘json_attributes_topic’: ‘14kWh_Lifpo4/discharge’, ‘expire_after’: 20, ‘device’: {‘identifiers’: [‘2012282166’], ‘name’: ‘JK BMS 150A’, ‘model’: ‘JK-B2A24S15P’, ‘sw_version’: ‘6.1.0S’, ‘hw_version’: ‘6.X’}, ‘state_topic’: ‘14kWh_Lifpo4/switch/discharge’, ‘command_topic’: ‘homeassistant/switch/14kWh_Lifpo4/discharge/set’, ‘platform’: ‘mqtt’},) Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py”, line 316, in async_discover config: DiscoveryInfoType = discovery_schema(discovery_payload) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 272, in call return self._compiled([], data) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 595, in validate_dict return base_validate(path, iteritems(data), out) File “/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py”, line 433, in validate_mapping raise er.MultipleInvalid(errors) voluptuous.error.MultipleInvalid: expected BinarySensorDeviceClass or one of ‘battery’, ‘battery_charging’, ‘carbon_monoxide’, ‘cold’, ‘connectivity’, ‘door’, ‘garage_door’, ‘gas’, ‘heat’, ‘light’, ‘lock’, ‘moisture’, ‘motion’, ‘moving’, ‘occupancy’, ‘opening’, ‘plug’, ‘power’, ‘presence’, ‘problem’, ‘running’, ‘safety’, ‘smoke’, ‘sound’, ‘tamper’, ‘update’, ‘vibration’, ‘window’ for dictionary value @ data[‘device_class’]
Logger: aiohttp.server
Source: components/websocket_api/http.py:213
First occurred: 11:42:20 AM (1 occurrences)
Last logged: 11:42:20 AM
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py”, line 433, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 85, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 80, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 235, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 146, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/websocket_api/http.py”, line 53, in get
return await WebSocketHandler(request.app[“hass”], request).async_handle()
File “/usr/src/homeassistant/homeassistant/components/websocket_api/http.py”, line 213, in async_handle
await wsock.prepare(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_ws.py”, line 138, in prepare
payload_writer = await super().prepare(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 421, in prepare
return await self._start(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 429, in _start
await self._write_headers()
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 502, in _write_headers
await writer.write_headers(status_line, self._headers)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 130, in write_headers
self._write(buf)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 75, in _write
raise ConnectionResetError(“Cannot write to closing transport”)
ConnectionResetError: Cannot write to closing transport