Blue (replacement) switch not interviewing/unsupported in Z2M / Home Assistant

Switches General Discussion
1

Getting this error every time:

Info <small>2023-07-31 16:09:54</small>`Device '0x6c5cb1fffe5e53c0' joined`

Info <small>2023-07-31 16:09:56</small>`MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x6c5cb1fffe5e53c0","ieee_address":"0x6c5cb1fffe5e53c0"},"type":"device_joined"}'`

Info <small>2023-07-31 16:09:56</small>`MQTT publish: topic 'zigbee2mqtt/0x6c5cb1fffe5e53c0', payload '{"last_seen":"2023-07-31T16:09:56-04:00"}'`

Info <small>2023-07-31 16:09:56</small>`Starting interview of '0x6c5cb1fffe5e53c0'`

Info <small>2023-07-31 16:09:57</small>`MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x6c5cb1fffe5e53c0","ieee_address":"0x6c5cb1fffe5e53c0","status":"started"},"type":"device_interview"}'`

Error <small>2023-07-31 16:12:15</small>`Failed to interview '0x6c5cb1fffe5e53c0', device has not successfully been paired`

Info <small>2023-07-31 16:12:16</small>`MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x6c5cb1fffe5e53c0","ieee_address":"0x6c5cb1fffe5e53c0","status":"failed"},"type":"device_interview"}'`

I’ve tried:

  • Removing switch from the Z2M config and restarted pairing by pulling out the power toggle and putting back - then it’ll slow blink blue
  • Resetting switch by holding up and config for 20 seconds (several times)
  • Turning off all other switches, then try resetting the switch/pairing

I have 20 switches installed so far, and this is the first one that refuses to pair. Any ideas?

2

Anyone? I’ve tried a couple more times with resetting/repairing with the same result.

3

Have you tried a different (known good) switch in the same spot just for comparison? And any other zigbee devices in that area?

4

I haven’t swapped the switch yet, no. There are 2 switches about 10 feet away, so I don’t think it’s a reception issue.

5

I would probably try swapping it with a known good switch if you’re able. If that works fine, I’d recommend opening a support ticket.