Scratching my head here. I’ve got a presence sensor that was set up with zigbee and happily working in HA. I needed to wipe it and re-pair it with a different controller to do some troubleshooting. Removed it from Zigbee2MQTT, it disappeared from HA, all is good.
I go to re-add it after a full factory reset on it. Zigbee2MQTT picks it up but I can’t get it to show up in HA. I’ve tried renaming it, looking for it in deleted devices, restarting HA, restarting Zigbee2mqtt…I cannot get this device to show up in HA.
It looks to be working properly, as events from the device are showing up in the zigbee2mqtt logs.
I have a second sensor, same make/model, that I’ve had no problems removing and re-adding, so there is something unique to this one that won’t let HA accept it.
I got some kind of similar problem today.
One of my IKEA bulbs stopped working so I decided to replace it.
It was exposed to HA via the IKEA gateway so I removed it through the IKEA app first and then rebooted HA to make sure that HA would be updated properly about the devices in the IKEA integration.
Then I added the new bulb via zigbee2mqtt with the same name as the old bulb.
No problems there, all good.
In zigbee2mqtt everything looks alright and I can control the bulb but in HA the device and it’s entities has the status “unavailable”.
I have never observed this behaviour before.
Last week I added two presencesensor without any problems at all.
OK, at least I’m not crazy! I’ve seen things orphaned in HA, but I’ve never seen something stuck in Z2MQTT. No problems pairing/deleting/repairing to Aquara hub and built-in coordinator for testing. Seems to be very specific to this device and this install.
