Help please....I have a number of GU10 zigbee bulbs from IKEA. Most have connected fine but when I finally managed to find the devices on search they get stuck on "Initializing". Any help for a newbie would be much appreciated
Hi this doesn't really answer your question but I have plenty of tradfri bulbs running just fine - the difference is that they are all connected to my hue controller and I've never had a problem with any of them using this set up. The hue hub is connected to hubitat via the built in app which works flawlessly. This may mean buying and housing an extra controller but it is worth it (in my opinion) especially as they can usually be picked up quite cheap on ebay.
1 Like
This could be because of a bad signal when pairing (routing through another of those zigbee bulbs), try pairing them very close to the hub to be sure they have a direct route to the hub, then you can move them to there final location.
I was having problems with automations a few weeks back after adding some more Ikea Bulbs (since not many vendors have the candle light style available), so like Simon mentioned just above, I got a Hue Hub second on MarketPlace to 1/3 price of new, paired all the lights to the Hue Hub and no more problems since.
Thanks all. I rebooted the hub in the end and managed to pair them. I do have my upstairs ikea bulbs connected to my hue bridge, however I was getting close to the 50 device limit, so these ones in particular I connected directly to the Hubitat hub 
Is it worth having a second bridge? Do 2 bridges work well with Hubitat?
After what I experienced, I believe that it would be worth getting another one or if you are not at the limit, just pair them with the current one instead of HE.
No idea, only have 1, maybe but a quick search leads me to believe that it works nicely, just keep in mind that you will have to add a new instance of the app for each Hue bridge you add, you can't just add it in the existing app.
I was having this exact same problem with Sonoff Motion Sensor (Zigbee) devices. Interestingly this only started happening once I'd upgraded to 2.2.4.156 (I haven't tried 2.2.4.158 - still running 2.2.4.148). Before I rolled back I did get a temporary solution which was suggested by someone on here....
Once the device is found and is reporting the status of "Initializing" very quickly press the reset button a couple of times - not enough to completely reset, but just quickly.
I was sceptical, but on a couple of the devices it did work!
