Just to say, this is the incorrect procedure. It needs to be
after changing the driver to Advanced Zigbee Bulb, click Save Device > fill in and Save Preferences > then hit configure and watch the logs> once completed Refresh the driver page.
1 Like
I don't think Sengled bulbs update over SmartThings. You can only get them updated from the Sengled hub. AFAIK they all ship with the original firmware.
1 Like
Yes they do update via. SmartThings...I posted this earlier in this thread.
2 Likes
Yes. They most definitely do update FW in SmartThings, @ronv42 is correct.
Whether the FW repository that SmartThings uses is the same as the Sengled one is an interesting question for me.
i detailed out my device types and FW versions, if (anyone with a sengled hub) has got one of the same bulbs as me, can you confirm the ST FW version are the same as the Sengled hub versions?
either way, ST did not upgrade FW on any of the bulbs i have had working perfectly for quite some time pre-2.2.5. so i am going with Ockham's razor and suggest that its an introduced bug in 2.2.5. I say that because i have issues with both the Sengled drivers and the new one.
Thinking out loud I guess its possible that the original dev/test process for the original platform/Sengled drivers 'wrote around' any strange/lax protocol implementation in bulb FW, and perhaps with 2.2.5 and the new adv.zigbee bulb driver were built without as much allowance for protocol adherence (i.e. Sengled bulbs) specifically in mind, effectively breaking Sengled on HE. However if that simplistic explanation may be at least partly true, then why are some users reporting good operation of these bulbs, even as are a lot of users such as myself experiencing problems?
@mike.maxwell, thanks for your response on the other thread, however these bulbs don't seem to be working properly in 2.2.5 regardless of whether we use the new Adv.ZigbeeDriver or the original SengledClassic drivers. I'm happy to provide whatever information you need to figure this out?
I can publish the pre 2.2.5 sengled drivers which you can switch to, we are trying to close 2.2.5, so these may not be out until 2.2.6.
So for now you're going to have to stay on 2.2.4.
I can't revert the current drivers as they were specifically tested and tweaked for a large commercial installation.
hi @BorrisTheCat i was deliberately doing that so i used the default preferences, just in case there was weirdness with particular settings. for example, some users are reporting that certain bulbs work OK with the new driver only when they have certain pref values set.
i think (but didn't thoroughly document) i subsequently change some prefs (such as logging) after a while so i didn't add too much logging load to my hub.
are you saying that by accepting the default preferences (by not explicitly clicking Save Preferences after the Save Device before clicking Configure) this is a problem that will cause a device to never work? (i hope not 'cause all this reset troubleshooting is soooo tedious and time-consuming, ladders to remove bulbs, blah blah)
I'm saying certain things don't become active in the driver until you click save. Alot can be set up and called when you call the update. It depends on how the driver is written and what it's doing but this driver uses alot of state variables so that usually only gets fully populated after you click save. So it's always best to run though the full process to ensure all is completed.
thanks Mike. So the Sengled drivers were tweaked beyond the setLevel bugfix from 2.2.4 to 2.2.5? that explains a lot.
regarding roll back, the reason i went for 2.2.5 so quickly was RM4.1.
Since I went with 2.2.5, i have updated a handful of RM rules to improve some existing behaviour, and also take advantage of multiple wait conditions (love that feature) so have a few 4.1 rules now.
I've never had to roll back before.
If I roll back to 2.2.4 without a separate config restore from a relevant timeframe (assuming i can find one), what would happen as 2.2.4 reads an RM4.1 rule? or is config roll-back a mandatory pre-requisite? (sorry, I searched the community just now but didn't find a restore guide)
If you revert your 4.1 rm rules will break and not be accessable.
I've run into problems with my sengled element color plus install after changing them over to the advanced zigbee RGBW driver. Some of the bulbs became unresponsive after changing the driver and configuring. I attempted to reset these bulbs but they will no longer join. I was able to pair them with my sengled hub and update them to the latest firmware. After excluding the bulbs from the sengled hub, some of them could could not be paired with my hubitat hub, even after reset and with the hub near the bulb. I was not successful in pairing them, even after deleting the "ghost" bulb placeholder in hubitat. Are there any tips for how to proceed? I hope I'm missing something simple.
If a driver doesn’t work, just change the driver and click Configure. No need to pair the bulbs again.
If a Zigbee device loses connection, just pair it again. No need to delete the driver.
To reset Sengled bulbs, power cycle them 15 times and they’ll go through a flashing sequence indicating they’re reset and ready to pair. You should have the hub ready to pair, as the bulbs don’t stay in a ready to pair state for very long in my experience with them.
1 Like
It seems like it must be repeater related. I have not had any issues with mine and I also updated them to the latest firmware. I’ve also experienced how it doesn’t necessarily matter that the hub is close unless there are no other repeaters on the network.
1 Like
Thanks. It's strange because things were humming along with the Sengled bulbs until I started changing the drivers and upgrading the firmware on the hub. I've had a lot of experience with the bulbs and am familiar with the pairing process for the Sengleds.
It's possible that the update did something to the repeaters I have on my network (most are Peanuts) I'll check that next.
UPDATE 4/1/2021: I purged the Peanuts from the network and am now exclusively running GE/Jasco repeaters. Things are infinitely more stable
In retrospect, the mesh was struggling for a while, but I didn't notice until I tried pairing the Sengleds after updating them on another hub. I had >30 bulbs burning at a time and the mesh was "maxed out" which prevented me from adding the bulbs.
Not directly no, however restarting the hub can cause devices to try rediscovering routes while the hub is rebooting, usually things repair themselves within 24 hours. Stubborn non responsive zigbee devices can usually be kickstarted by a power cycle/battery pull
1 Like
Don't want to stir up a nest of conflicting opinions, but there are folks around here who swear Peanuts can be a pox on a Zigbee mesh. Others say they work fine. I've had a few (never more than three, currently one) on my network w/out any noticable issues. But maybe the Peanuts don't play well w/the updated drivers?
3 Likes
It’s the Peanut Pox that’s causing this. I had great difficulty getting some devices to join way back when Peanuts were cool. I also had frequent lockups before I removed them from my mesh. They would crash the Zigbee network.
2 Likes
Your input and my zigbee post-mortem analysis have led me to conclude that it's a repeater issue and not related to the new RGBW bulb drivers. I have a zigbee network with around >65 sengled bulb endpoints and I was probably having issues pairing bulbs because the repeaters in my network (6 Peanuts and 2 GE/Jasco devices) were misbehaving.
I still haven't figured out why I didn't see issues until the most recent updates. I'm actively looking for a replacement for the Peanuts, although there does not seem to be consensus on the best outlets. Please let me know if you're aware of a UL listed 1500w-capable repeater outlet preferably with power monitoring. I think the GE ZB4101 are the only ones out there, but they're not Zigbee 3.0.
1 Like
so thanks to @mike.maxwell for 2.2.5.131 publishing the legacy drivers, as always you guys have been proactive on the support front. if anyone doubts this, buy a Plex account and log a support case that can't be answered with 'Refresh your browser'. (great product, love it, but cripes support ain't their strong point)
i tested my bulbs on them, and reverting to the legacy driver fixed 6 of them, and the other 3 still would not go back to pre-2.2.5 stability.
in the end i had to replace all the sengleds to restore household sanity, as i was stuck with the RM4.1 rollback issue. very expensive fix for what in the end was an 'introduced' problem to a previously stable environment... 
1 Like
I agree with the Peanut thing. I was having stability issues with only a couple on my network. I noticed the routing table constantly changing. Once I got rid of these, the routing is very steady.
I wouldn't be too concerned about that. Just having a good Zigbee repeater is more important than if it is 3.0 or not. I have a couple of those GE, and they seem to have decent signal, and things route through them. Others seem to like the Ikea repeaters.
2 Likes
+1 on the ikea repeaters, they work well, are affordable, and i like how you can plug them into an available USB port (like on the back of a TV) 
