If I recall correctly, I did browse the subject of LG Zigbee bulbs on the Hubitat forum. I believe the consensus was that they worked with the addition of a Hue Bridge. I’m imagining the same case with Smartthings. It’s just odd that they would stop working from one ST hub to another.
Again, someone may turn up with a definitive answer. If I come across one, I’ll be sure to follow up.
Thanks very much for the clues. I may be headed in the right direction here. It does not look like there is a default option for ZHA among the DTHs offered. However, the graph.api.smartthings.com site does give me the option to create my own device handler. Is that what I need to be doing? I see something about a Zigbee Dimmer, with a number of manufacturers offered as option (Leviton, etc.), but nothing for LG. Do I need to create the handler this way?
Gotta admit, I’m wading into waters I am very unfamiliar with. I kind of solved my problem already by just buying new $10 bulbs to replace these $25 ones, but I’m also feeling a little bit stubborn about the planned obsolescence of perfectly functioning devices after only 4 years of use (they stopped dimming in 2019 or so).
I don’t want to give you bad advice here, since I can’t even read the code let alone know what smartthings would require. Also I don’t know whether the DTH Has to have the correct manufacturer code in it now, or not.
What DTH are you using now? I would expect something that works for a basic cree bulb to also work because that’s also a ZHA device, unless, again, smartthings requires a manufacturer code.
the hue bridge forms its own mini Zigbee network for devices attached to it, so those devices then don’t repeat for other devices attached to the ST hub. This can be a good thing because it gets those ZLL devices off the ST network.
ZLL and Zigbee 3.0 devices will fall back to a ZHA profile when attached to a ZHA-only hub, but this can have some quirks. This was a big issue for ST customers until the V2 and V3 hubs were updated to Zigbee 3.0, so there are a lot of old forum thread discussing those issues, but they no longer apply.
some manufacturers push the edge on their Zigbee implementation, meaning their devices don’t work smoothly with those of other brands, even though they should. Xioami Is famous for this (for example, they don’t work well with all repeaters). IKEA occasionally has this issue. It’s probably not a coincidence that these are budget brands.
some Zigbee features are optional for manufacturers. For example, the ST V3 hub now supports Zigbee 3.0, but does not support touchlink commissioning or the green power clusters. So the Hue tap cannot be directly added to an ST setup, for example, nor the RunLessWire or Senic batteryfree switches.
there are some security settings which prevent devices from other profiles from joining an existing Zigbee network, but ST does not at the time of this writing use these, so it doesn’t affect an ST setup.
So…it’s generally fine to mix ZHA, Zigbee 3.0, and ZLL devices on one Zigbee network as long as the hub is Zigbee 3.0, with the understanding that some specific models may have some issues, and that most lightbulbs are not good Zigbee repeaters except for other Zigbee lightbulbs. (IKEA seems to be the positive exception here: historically their tradfri bulbs have been good repeaters in an ST setup.)
Zigbee 3.0 is intended to be forwards and backwards compatible, it just doesn’t always succeed.
I don’t think many manufacturers are making new models using ZHA (it’s almost all Zigbee 3.0 now), but there are plenty of older ZHA devices still in service, quite a few still being sold from old inventory, and even a few models still being manufactured as new stock.
Osram/Sylvania made the decision recently to shut down their cloud services rather than upgrade all their devices to 3.0, which may be where you got that impression.
Furthermore, the implemented ZigBee® standard is not state of the art anymore (ZigBee® Light Link and ZigBee® Home Automation instead of ZigBee® 3.0) which makes it more and more difficult to ensure compatibility to other smart home systems.
But “more difficult” isn’t “impossible,” and they aren’t recalling the devices, just shutting down the cloud service.
Eventually Zigbee ZHA devices which can’t be updated to matter compatibility may become obsolete, but we’re a ways off from that yet.
Speaking just for myself, if I were buying a new device, I’d be looking for Zigbee 3.0 . But I’d continue to operate any existing ZHA devices that I had that were working fine as installed.
If ZHA devices were truly obsolete, I would surely have several dozen…
Just an observation comparing the Zigbee Dimmer vs Cree Bulb DTH. The cluster mappings, if that is the right word, looked very different. I’m not sure if that has to do with the Cree being ZHA or not, but I mention this in case someone might offer some insight, which might help getting the LG bulbs working , if the Cree handler doesn’t solve the problem.
I do have a box full of window/door sensors (although not ZHA) that don’t respond to any of the available DTH. I hope to get them working as my understanding of clusters and such improves.
This is all very intriguing banter. I did not know there were so many different Zigbee standards floating around out there.
I would just add one more tidbit here about my specific situation: the V1 hub I was using (right up until Samsung finally killed it off on June 30) also had problems with the LG bulbs and dimming. Sometime in 2019 or so, the ability to dim the LG bulbs just stopped, and they became on/off bulbs only. So the problem predates my installing the new Aeotec hub. Did Samsung/SmartThings release a software or firmware update that dropped support for the older Zigbee Home Automation standards or something?
One standard, multiple “profiles.” Bluetooth also does this. Zwave does not.
Did Samsung/SmartThings release a software or firmware update that dropped support for the older Zigbee Home Automation standards or something?
Not that I know of, but I think they did update a bunch of their generic DTHs so they would be assuming the device was Zigbee 3.0 rather than assuming it was ZHA. But again, I can’t read the code, so I don’t know if that’s really an issue or not.
What DTH are the bulbs currently using? and again my first suggestion would be just to try the existing Cree DTH and see if it works.
When I first paired the LG Zigbee bulbs with my new Aeotec hub, they were recognized with a DTH of ZigBee Dimmer.
I just tried changing them to Cree Bulb and the behavior did not change: they can be turned on/off but not dimmed. When I slide the dimmer slider in the SmartThings app for the bulbs to anything above zero or below 100, it immediately snaps back to 100%.
Yes, until sometime in late 2019/early 2020, these LG bulbs were working fine with the SmartThings v1 hub. I am not 100% sure that they were using the Zigbee Dimmer DTH; since they “just worked”, I didn’t really investigate any of the underpinnings. But it was probably using that device handler, yes.
You had mentioned Sylvania/Osram in regards to ZHA, so it got me to looking…
The DTH, didn’t appear to have any fingerprints and the commands appeared different than both the Zigbee Dimmer and the Cree DTH. Not that I have a good understanding of the particulars, but thought there might be a chance.