Zigbee bulb doesn't show in the Add Device GUI

Configuration Zigbee
,
1

Hello Friends,

When trying to add a new Zigbee bulb by Innr I’m getting the following messages in the HA ZHA log, and the bulb is not showing up in the HA GUI.

Feeding watchdog
[<Task pending name='device-availability-checker_DeviceAvailabilityChecker' coro=<periodic.<locals>.scheduler.<locals>.wrapper() running at /usr/local/lib/python3.13/site-packages/zha/decorators.py:78> cb=[set.remove()]>] executing periodic task [zha.application.helpers::DeviceAvailabilityChecker.check_device_availability]
Device availability checker interval starting
Checking device availability
[0x1A12](RS 226): last_seen is 77830.23803400993 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x1A12](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x8AA5](RS 226): last_seen is 77828.35127949715 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x8AA5](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xE86E](RS 226): last_seen is 77835.66226410866 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xE86E](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x1B2F](RS 226): last_seen is 77846.18728280067 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x1B2F](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xC504](RS 226): last_seen is 77781.8755800724 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xC504](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x8083](RS 226): last_seen is 68897.96572828293 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x8083](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xD2F1](RS 226): last_seen is 68904.13870286942 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xD2F1](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x733C](RS 226): last_seen is 69202.52195191383 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x733C](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xFF10](RS 226): last_seen is 69201.86472272873 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xFF10](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x0A72](RS 226): last_seen is 69226.53100633621 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x0A72](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x383C](RS 226): last_seen is 68856.84124231339 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x383C](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x004D](RS 226): last_seen is 69229.23820447922 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x004D](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xEEA3](RS 226): last_seen is 69173.4737625122 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xEEA3](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0x7E82](RS 226): last_seen is 69223.95436048508 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0x7E82](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xE247](RS 226): last_seen is 69226.05764341354 seconds ago and ping attempts have been exhausted, marking the device unavailable
[0xE247](RS 226): Update device availability -  device available: False - new availability: False - changed: False
[0xD0E3](lumi.sensor_magnet.aq2): Device seen - marking the device available and resetting counter
[0xD0E3](lumi.sensor_magnet.aq2): Update device availability -  device available: True - new availability: True - changed: False
[0xEB70](lumi.sensor_magnet.aq2): Device seen - marking the device available and resetting counter
[0xEB70](lumi.sensor_magnet.aq2): Update device availability -  device available: True - new availability: True - changed: False
Device availability checker interval finished

Is there a way to fix this?

Any help will be greatly appreciated :pray:

2

Is the bulb getting power? It’s a common error, smart bulb in a socket but the switch on the socket is not turned on. So smart bulb isn’t so smart without power.

3

And to add to this, if this is a 3-way lamp you may find that not all “clicks” work for joining. I have no idea why, but I have two lamps that have only been able to work for joining when the bulbs are powered by the first “click” of turning the lamp switch.

4

The lightbulb is turned on.
The log only starts showing these messages after I turn the bulb ON.

5

It’s turned on, but is the bulb in pairing mode? It should be blinking if it is

6

I have the bulb connected to a simple cable switch I built for times I need to add/re-add light bulbs, without interrupting other bulbs in the process.