Device disappears after Z2M restart

[Diadlo]

What happened?

1. Device added successfully
2. Device can be controlled in UI
3. Device is present in database.db
4. After Z2M restart device disappeared from UI and from database.db

What did you expect to happen?

1. Device added successfully
2. Device can be controlled in UI before and after restart
3. Device is present in database.db before and after restart

How to reproduce it (minimal and precise)

1. Add any zigbee device. I'm using Tuya TS011F (aka Elivco LSPA9)
2. Make sure that device can be controlled in UI
3. Check that device added in database.db
4. Restart Z2M (Tools -> Restart Zigbee2MQTT)
5. Check if device exist on "Devices" tab and can be controlled

Zigbee2MQTT version

2.0.0-dev commit: 7392557

Adapter firmware version

I've tried with:

• 0.0.0.1 (downloaded from v2.6.0_ncp_zboss_max_mem_nrf52840_dongle.hex)
• 0.2.2.0 (downloaded from v2.2.0_ncp_zboss_max_mem.hex)

Adapter

zboss

I've read that it's experimental, but I think it should support device persistence among Z2M restart

Setup

Add-on on Home Assistant OS on Raspberry Pi

Debug log

Log after reboot: log.log

Coordinator address: 0xf4ce3684e3132c9a
Device address: 0xa4c1380637ba72a5

[Diadlo]

It looks like the root of the issue is that extended PAN ID from ZBOSS has reverse order and driver decides to recreate the network. Should be fixed with Koenkk/zigbee-herdsman#1293

[pxFIN]

@Diadlo I reckon your issue is very much related to this ?

#24705

[Diadlo]

@pxFIN yep. Looks related. And now my issue is solved, so closing