First...thank you staff and members. Because of your hard work, I'm on my way to finding comfort in being abandoned by Lowes. I have quite a few lightify bulbs. All seem to work flawlessly with Hubitat, except the 74283. They all identify as "device" with no controls available. After alot of playing, and a few resets and reconnects, it seems they work well as "generic dimmers". If they don't, reset the bulb, delete the device, then connect and change to "generic dimmer". Alexa responds to every command with "not responding" and the dashboard has no confirmation, but, they function reliably. Dimming is even reliable. I can't see status in the dashboard, but in person, they work. I can't see the state, but they work, even with triggered rules. I'll update if issues arise, but I've tried it a ridiculous number of times tonight.
If you can, I'd start replacing the Lightify bulbs with Sengleds. You'll thank yourself later as you WILL have issues with the OSRAM/Lightify bulbs. I've got two more two go on my mesh after experiencing tons of issues with the bulbs.
This is only the case if you have a mix of lamps (bulbs are planted 
) and other ZigBee stuff. If like me you only have lightify lamps you won't have a problem (apart from their failing rate 
)
True. I should be more specific about that. Although, I think that the percentage of people running a dedicated "light" hub is probably pretty low compared to people running everything (sensors, lights, etc) on a single hub.
I know there's not a lot of love here for Lightify bulbs. There seems to be alot of people that have issues with them. Unfortunately replacing them all is not a realistic option. Since it was the IRIS preferred bulb, I have quite a few of them. I've used them for several years and they have been very reliable. After adding some repeaters, as instructed in another thread, all seem to be well supported and fully functional except the model I listed. They work fine, but I think since I'm using it as a generic dimmer, there's no feedback. The hub and Alexa cannot see the bulb state. I wonder if adding a lightify hub may improve the compatibility. I've read that these bulbs may not get proper updates, unless connected to their hub.
Why you don't try the generic zigbee bulb driver?
This is not compatible with HE
I also have a bunch of Sylvania products: plugs and light strips. I also have one cree bulb. Rarely do I have anything disconnect.
However in my zigbee mesh I notice that nothing tries to repeat through the bulbs.
I do not have any Xioami products either.
I tried, it didn't work.
Even the one with CT name?
the correct driver for this should be generic zigbee bulb, be sure to click configure in the driver details after changing to this driver.
lightify bulbs can be reset, paired to their native hub so they can receive any available firmware updates, then reset again and re-paired to HE. I have no idea whether that would help in this particular case, though.
Totally agree. I had some Cree on my mesh...total mess. Swapped to Sengled and problems disappeared.
After a couple of deletes and pairings, the generic zigbee bulb profile seems to work, with one issue. These bulbs turn on and are reported on in the dashboard. When turning off, the dashboard icon switches to an hourglass for a second, the lamp turns off, then the dashboard shows the light still on. The bulb has turned off, but doesn't show off in the dashboard. Clicking the tile again, switches the icon to off. These 74283 bulbs are the only lightify bulbs that do this. My others do not. The only other thing I have noticed, is that all of my other bulbs switch off instantly, while these dim to off.
Thanks to all who posted here about the 74283 bulbs. I have two of them and confirm that they behave exactly as dmdauto reports. They apparently fail to confirm the off state back to the hub.
I had a similar problem with Osram non-tuneable white (not sure of the model number, but I believe that Osram branding was changed to Lightify a while ago). The hub never seemed to detect the off state properly with the 'correct' driver, though it otherwise functioned properly. I was able to work around this issue by setting them to use the Generic Zigbee RGB Light driver; the bulb now reports on/off/dim status normally.
Aside from the useless RGB settings on the device settings page, this driver properly reports the on/off state of the bulb to the automations I have that depend on it. I haven't noticed any side effects and don't do a lot of dimming (since the couple of these that I have aren't frequently used) but level setting also seemed to work OK. My bulbs were a purchased about 3 years ago; maybe not applicable to yours but might be worth trying.
Tony,
Thank you for the suggestion. Unfortunately, neither the Generic Zigbee RGB Light nor the Generic Zigbee RGBW Light worked. The latter did initially work - until I powered the bulb off and on once. Then it acted as before, failing to report back the state following a command.
Since I only have two of these, and since they seem to interfere with the reliability of my other Zigbee devices, I think I'll just replace them. Thanks again for the help.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
