Core: After restart of HA all Zigbee devices are "unk_manufacturer" | 0.105.2 | ZHA

Created on 7 Feb 2020  路  12Comments  路  Source: home-assistant/core

The problem

Moved from deCONZ to ZHA with my ~ 40 devices. After all devices are paired with ZHA (deconz stick), I did a restart of Home Assistant Core. Now all (until 1) Zigbee devices have a Model of: unk_manufacturer

Example of a device after HA restart:
grafik
The shown "Nicht verf眉gbar (unknown)" entities are after the restart of HA. Also a newly switch was added after HA restart.

Part of the device list:
grafik

Environment

arch | x86_64
dev | false
docker | false
hassio | false
os_name | Linux
python_version | 3.7.5
timezone | Europe/Berlin
version | 0.105.2
virtualenv | true

Problem-relevant configuration.yaml

None as I used integrations for ZHA

Traceback/Error logs/Home Assistabt logs

Part of the Home Assistant Log.

2020-02-07 13:13:19 DEBUG (MainThread) [zigpy_deconz.uart] Connection made
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Loading application state from /var/lib/hass/.homeassistant/zigbee.db
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_motion.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_wleak.aq1
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_wleak.aq1
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_motion.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_motion.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_wleak.aq1
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 29320
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_motion.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: Philips
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: LCT010
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.weather
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 5 value: lumi.sensor_magnet.aq2
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 28521
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 27005
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 15674
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 26871
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 27005
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 26871
2020-02-07 13:13:19 DEBUG (MainThread) [zigpy.appdb] Attribute id: 4 value: 24706

Additional information

zigpy log:
zha.zip

zha problem in dependency

Most helpful comment

I think i know why this is happening after a restart.
to work around:

  1. go to zha config panel
  2. pick the device one by one
  3. select basic cluster
  4. read manufacturer attribute (for battery operated devices, you may have to trigger them to wake them up
  5. read model attribute if model is also unknown

now those should persist over a restart

All 12 comments

Hey there @dmulcahey, @adminiuga, mind taking a look at this issue as its been labeled with a integration (zha) you are listed as a codeowner for? Thanks!

I think i know why this is happening after a restart.
to work around:

  1. go to zha config panel
  2. pick the device one by one
  3. select basic cluster
  4. read manufacturer attribute (for battery operated devices, you may have to trigger them to wake them up
  5. read model attribute if model is also unknown

now those should persist over a restart

Many thanks for this workaround. Yes, with your steps they persist over a restart.

I still had this issue on v0.107.7 but the workaround by @Adminiuga seemed to work.

still happens to me in the last version with aqara door sensor, read attribute doesn't get any value and doesn't work after restart the device is detected as unk again

@miguelcaravantes Are you using Xiaomi devices? this will happen to Aqara devices when they don't play nice with other Zigbee devices like Sylvania bulbs. I ended up having to separate the Xiaomi devices on their own zigbee network (i used the Xiaomi hub and blocked connections to the internet from it).

After delete zigbee.db, update via terminal the conbee ii firmware repair again all devices, and be sure there was not weird characters in the database after repair, it works for me, no need of read atributes

I think i know why this is happening after a restart.
to work around:

  1. go to zha config panel
  2. pick the device one by one
  3. select basic cluster
  4. read manufacturer attribute (for battery operated devices, you may have to trigger them to wake them up
  5. read model attribute if model is also unknown

now those should persist over a restart

Hi @Adminiuga

i tried to follow what you have advised but im kind of lost after the 3rd step. Pleae dont mind im a total newbie to this and have just started.

I have a Aqara temp/humidity/pressure sensor.

{
"node_descriptor": "",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0302",
"in_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0402",
"0x0403",
"0x0405",
"0xffff"
],
"out_clusters": [
"0x0000",
"0x0004",
"0xffff"
]
}
},
"manufacturer": "LUMI",
"model": "lumi.weather",
"class": "zhaquirks.xiaomi.aqara.weather.Weather2"
}

is the zigbee device signature for the sensor.

step 3 : i chose "Basic Cluster" under the cluster list.

and then step 4 asks for cluster attributes. where do i get these? Is it from the above signature or do i have to do something else?

Your help would be highly appreciated :)

thanks in advance

do you get these
image

do you get these
image

Yes i do get that option but no clue as to what the value and manufacturer code overide should be.

Thanks for your reply, really appreciate it 馃槵

Nah, leave the other two empty, click get attribute and may have to wake the device by triggering it

Nah, leave the other two empty, click get attribute and may have to wake the device by triggering it

Aaahhh i see. So trigger the device by pressing the button and clicking get attributes should bring the values up. I was clicking the get attributes without pressing the button to wake the device up. Is there anything else that needs to be done? I cant wait to get home now to do this 馃槀

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Ciqsky picture Ciqsky  路  129Comments

grantalewis picture grantalewis  路  145Comments

ariel-madril picture ariel-madril  路  451Comments

Gio76 picture Gio76  路  223Comments

neotrunks picture neotrunks  路  169Comments