NWK Conflict Is Reported?

Configuration Zigbee
1

I’m researching a problem that happened this morning where our Zigbee relay switched on when it was not actually triggered by any automated or user event. In this case I found this entry in the System Log:

Logger: bellows.zigbee.application
Source: runner.py:154
First occurred: February 22, 2025 at 12:59:26 PM (4 occurrences)
Last logged: 7:06:40 AM

NWK conflict is reported for 0x6223
Found f0:d1:b8:00:00:07:32:4e device for 0x6223 NWK conflict: LEDVANCE FLEX RGBW
NWK conflict is reported for 0x1634
Found 00:12:4b:00:24:5a:03:56 device for 0x1634 NWK conflict: eWeLink ZB-SW02

The symptom (in the log) is that the device “eWeLink ZB-SW02” went offline for a moment and when it came back online it tripped one of the relay unexpectedly.

I searched the forums and couldn’t quite find anything that helped me understand how to fix this. Can anyone help me understand what this means and how or if I need to fix it?

Thank you!
David

2

Most devices have a default power on behaviour set to on when power is restored.

This setting is adjustable in Z2M (on, off or last state), but I’m not entirely sure if this is exposed in ZHA. If you can’t see this setting on your device page then there might be a ZigBee cluster command you can send to set it.