core: Zha doesn't start after update to 2021.12.1

The problem

After updating to 2012.12.1 ZHA fails to start.

What version of Home Assistant Core has the issue?

core-2021.12.1

What was the last working version of Home Assistant Core?

core-2021.11.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Source: components/zha/core/gateway.py:152
First occurred: 10:47:43 (1 occurrences)
Last logged: 10:47:43

Error setting up entry Sonoff TI CC2531 for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 102, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 152, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
    await app.startup(auto_form)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 175, in startup
    return await self._startup(
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 295, in _startup
    await self.load_network_info()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 1173, in load_network_info
    await self._znp.load_network_info(load_devices=load_devices)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 146, in load_network_info
    tclk_seed = await self.nvram.osal_read(
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/nvram.py", line 207, in osal_read
    value = self.deserialize(data, item_type)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/nvram.py", line 82, in deserialize
    raise ValueError(f"Data left after deserialization: {remaining!r}")
ValueError: Data left after deserialization: b'liance09w\x01\x00\x00\x00\x00\x00\x00'

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 32 (22 by maintainers)

Most upvoted comments

You can’t run both… it’s one or the other. you either have to remove Z2M or remove ZHA

Ok, I’ve switched from the other thread to here, as you guys mentioned it.

As noticed before, I’m new with HA and Zigbee. So don’t hold it against me, if I ask newbe questions.

So here is such a question 😃: I’ve found that - today, as stuff works again - the slaesh-device isn’t configured in the Section Devices & Services: image

But I still have installed and configured the AddOns

  • Mosquitto broker
  • Zigbee2mqtt

I really wonder, if the device is still marked as un-configured, why it currently work to control my smart devices?!? Might the Issue I’ve made be that one, that I’ve double-configured the Zigbee-Stick in my HA?

Let me explain what I think:

I still have my setup for Zigbee2mqtt in HA, and there I have some config-variables in there which also point to the zigbee-device. image

I could imagine that this are 2 different ways to setup such an stick. And as I’ve used both, they are fighting to each other… which could explain the error-messages in the logs. Always one of those configurations thorw errors, while the other one beat them down.

What do you think about this?