core: ZHA will not start in 2023.5
The problem
After upgrading to Home Assistant 2023.5, the ZHA integration will not start. I’ve tried it on my original setup (raspberry pi + Sonoff Zigbee 3.0 USB Dongle), and tried migrating to home assistant yellow with the built in radio. In both cases I see the error below.
I see this even if I use the Migrate Radio functionality to “erase” the radio.
What version of Home Assistant Core has the issue?
System Information version | core-2023.5.0 – | – 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.21-v8 arch | aarch64 timezone | America/Toronto config_dir | /config Home Assistant Community Store
GitHub API | ok – | – GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4645 Installed Version | 1.32.1 Stage | running Available Repositories | 1283 Downloaded Repositories | 27 Home Assistant Cloud
logged_in | true – | – subscription_expiration | August 16, 2023 at 8:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | us-east-1-1.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 | 916.2 GB disk_used | 17.2 GB healthy | true supported | true board | yellow supervisor_api | ok version_api | ok installed_addons | Node-RED (14.1.5), ESPHome (2023.4.4), File editor (5.6.0), Grafana (8.2.2), Mosquitto broker (6.2.1), Log Viewer (0.15.0), Advanced SSH & Web Terminal (14.1.0), InfluxDB (4.6.0), Studio Code Server (5.5.7), RPi Temp Monitor (0.4), Matter Server (4.3.1) Dashboards
dashboards | 2 – | – resources | 20 views | 1 mode | storage Recorder
oldest_recorder_run | April 24, 2023 at 6:40 PM – | – current_recorder_run | May 4, 2023 at 9:15 AM estimated_db_size | 1390.90 MiB database_engine | sqlite database_version | 3.40.1
Home Assistant Community Store
GitHub API | ok – | – GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4645 Installed Version | 1.32.1 Stage | running Available Repositories | 1283 Downloaded Repositories | 27Home Assistant Cloud
logged_in | true – | – subscription_expiration | August 16, 2023 at 8:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | us-east-1-1.ui.nabu.casa certificate_status | ready can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome 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 | 916.2 GB disk_used | 17.2 GB healthy | true supported | true board | yellow supervisor_api | ok version_api | ok installed_addons | Node-RED (14.1.5), ESPHome (2023.4.4), File editor (5.6.0), Grafana (8.2.2), Mosquitto broker (6.2.1), Log Viewer (0.15.0), Advanced SSH & Web Terminal (14.1.0), InfluxDB (4.6.0), Studio Code Server (5.5.7), RPi Temp Monitor (0.4), Matter Server (4.3.1)Dashboards
dashboards | 2 – | – resources | 20 views | 1 mode | storageRecorder
oldest_recorder_run | April 24, 2023 at 6:40 PM – | – current_recorder_run | May 4, 2023 at 9:15 AM estimated_db_size | 1390.90 MiB database_engine | sqlite database_version | 3.40.1What was the last working version of Home Assistant Core?
2023.4.6
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zigbee Home Automation
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
home-assistant_zha_2023-05-04T13-22-01.999Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 122, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 230, in async_initialize
self.async_load_devices()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 238, in async_load_devices
zha_device = self._async_get_or_create_device(zigpy_device, restored=True)
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 570, in _async_get_or_create_device
zha_device = ZHADevice.new(self._hass, zigpy_device, self, restored)
File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 408, in new
zha_dev = cls(hass, zigpy_dev, gateway)
File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 153, in __init__
self._endpoints[ep_id] = Endpoint.new(endpoint, self)
File "/usr/src/homeassistant/homeassistant/components/zha/core/endpoint.py", line 109, in new
endpoint.add_all_cluster_handlers()
File "/usr/src/homeassistant/homeassistant/components/zha/core/endpoint.py", line 140, in add_all_cluster_handlers
cluster_handler = cluster_handler_class(cluster, self)
File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 133, in __init__
attr_def: ZCLAttributeDef = self.cluster.attributes_by_name[
KeyError: 'acceleration'
### Additional information
_No response_
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 21 (8 by maintainers)
I’ll try restoring my backup. Unfortunately it seems to take ages to restore, so it may be a few hours before I can pull the data (restore is in progress)
It shows as
Getting the device signature or diagnostics doesn’t seem possible since ZHA isn’t starting. I also removed the accelerometer entity on the device as an attempt to troubleshoot. I’ll try the quirk and let you know.