Description
What happened?
Hello
I am using zigbee2mqtt on a proxmox LXC, v2.2.1.
Version Zigbee2MQTT
[2.1.0](https://github.com/Koenkk/zigbee2mqtt/releases/tag/2.1.0) commit: [83ff4a76](https://github.com/Koenkk/zigbee2mqtt/commit/83ff4a76)
Type de coordinateur
zStack3x0
Révision du coordinateur
20221226
Coordinator IEEE Address
0x00124b00258d7e3c
Frontend version
0.9.4
Version de zigbee-herdsman-converters
21.27.1
Version de zigbee-herdsman
3.2.5
I added to my network two Nodon SIN-4-2-20 from the same order (so I expect that they are similar), I added already a third one in my zigbee2mqtt, also from the same order, in December 2024, without issues.
One of the two new nodon is somehow buggy with zigbee2mqtt V2.2.1:
- reported as unsupported though the one already in is ok. Reinterview didn't help.
- 2nd nodon was difficult to add but it was ok after some trials.
- I tried to delete the buggy nodon but it didn't work, with forced delete
- I restart zigbee2mqtt but I have an issue similar to No devices showing in Web UI after Z2M update #26576
I switched back to an old instance of zigbee2mqtt, V2.1.0, and did my pairing with V2.1.0. It worked fine for the pairing and both are regonized in zigbee2mqtt.
I was able to update the firmware of the good nodon, the buggy one is giving me some error messages:
image CRC-32 is invalid
I updated it by using the Nodon App and it looks to be ok now.
If I try to switch again to V2.2.1, the device list is again empty.
What did you expect to happen?
No issue to add new Nodon SIN-4-2-20 since it worked on elder version.
How to reproduce it (minimal and precise)
I expect with some Nodon SIN-4-2-20 pairing with V2.2.1
Zigbee2MQTT version
2.2.1
Adapter firmware version
20221226
Adapter
Sonoff CC2652
Setup
LXC on Proxmox 8.3
Debug log
No response