Hi everyone...I recently added 5 Sengled Smart LED Zigbee bulbs to my system. Model # E21-N1EA. I have defined 2 groups for them (3 in 1 group, 2 in the other). The group devices are on dashboards. Otherwise, I only have one other Zigbee device and a couple repeaters (rest of system is ZWave).
I keep noticing at random, that the group device displays as on, when none of the light bulbs in that group are physically appearing as on. In looking at the devices events, I see one of the bulbs shows being turned on, the group device showing a groupState of "someOn", the group switches to on, then two seconds later another bulb in that group has an event turned on, then the group shows a groupState of "allOn".
The whole time this occurs, the bulbs physically appear as off. The hub is on version: 2.3.0.124. Has anyone else had this problem and figured out the solution? I see it appears @razorwing had this problem back in 2019, but didn't really see a solved solution in that thread.
I tried moving my house Wifi(s) to be fixed on channel 6 and moved the hubs Zigbee to channel 25. Didn't seem to have any affect.
I am at a loss and tired of just turning the group device back off. Thanks in advance.
The problem isn't apparent from your screenshot. At 4:54:13-ish, all the bulbs report as off, and so does your group device. So, I assume this is really related to the fact that your bulbs might not be reporting back their state to the hub correctly? Everything looks fine if you trust the device events, and the hub can't know any better if those are wrong. (By the way, if you don't care for the groupState attribute, you can turn off the "Show group state in group device" option--adding this custom attribute is all it does; it doesn't affect the reporting of the standard switch attribute like your "Use group device to indicate if any members are on?" option does, which on the group device should show "switch: on" if any bulbs are on and "switch: off" when all bulbs are off.)
So I guess the question is what you can do to fix that. Hitting "Configure" on the device page is normally a good first step (especially if you switched drivers, but it can't hurt regardless). I'd also check that you're using the recommended drivers (see if you can find yours in this list: List of Compatible Devices - Hubitat Documentation), but you probably are--the Sengled drivers are reported to work best for most/all Sengled bulbs, though some people happen to prefer others (with or without various quirks).
The 4:54:13-ish events are just me manually turning off the group device.
The main problem is that throughout all these on events, no one turned any bulbs on and the bulbs remained physically off. I just keep noticing at random that the group device is back on and I keep having to turn it back off.
@troywehrle Did you ever find out any more about this? I just noticed the same thing happening because I had set up a rule to have a light strip turn on and match the color of one of my Sengled Element Plus bulbs when it was turned on. The light strip turned on when the bulb appeared to be off.
Looking at the hub, the bulb was reporting as 'on'. When I clicked the Refresh button on the device page it would momentarily show 'off' and then go right back to showing 'on'. When I clicked the 'Off' button, the bulb flashed on for a moment and then turned off, and it then reported as off.
I don't think it's a factor, but both of these bulbs are members of a Room Lighting group.
I had text logging turned on for both devices. I annotated the logs below inline... need to read from the bottom up. I'm going to turn on debug logging to see if that reveals anything more.
dev:332022-11-11 02:37:07.299 PMinfoBistro Bulb 1 was turned off
dev:332022-11-11 02:37:06.676 PMinfoBistro Bulb 1 is on
^^^ clicked "Off" for bulb 1 - this did flash the bulb on for a moment
dev:332022-11-11 02:36:56.921 PMinfoBistro Bulb 1 was turned on
dev:332022-11-11 02:36:56.721 PMinfoBistro Bulb 1 was turned off
dev:332022-11-11 02:36:56.659 PMtracerefresh() called...
^^^ clicked "Refresh" for bulb 1 again
dev:34 2022-11-11 02:36:44.249 PM info Bistro Bulb 2 is off
dev:34 2022-11-11 02:36:44.188 PM trace refresh() called...
^^^ clicked "Refresh" for bulb 2 again
dev:34 2022-11-11 02:36:39.056 PM info Bistro Bulb 2 was turned off
dev:34 2022-11-11 02:36:38.450 PM info Bistro Bulb 2 is on
^^^ clicked "Off" for bulb 2. This did flash the bulb on for a moment
dev:34 2022-11-11 02:35:50.953 PM info Bistro Bulb 2 was turned on
dev:34 2022-11-11 02:35:50.745 PM info Bistro Bulb 2 was turned off
dev:34 2022-11-11 02:35:50.669 PM trace refresh() called...
^^^ clicked refresh on bulb 2
dev:33 2022-11-11 02:35:39.582 PM info Bistro Bulb 1 was turned on
dev:33 2022-11-11 02:35:39.372 PM info Bistro Bulb 1 was turned off
dev:33 2022-11-11 02:35:39.312 PM trace refresh() called...
^^^ clicked refresh on bulb 1 - the lights were not physically on at any point here
dev:34 2022-11-11 01:59:27.036 PM info Bistro Bulb 2 was turned on
dev:33 2022-11-11 11:27:06.053 AM info Bistro Bulb 1 was turned on
^^^ these two events did not physically turn the lights on. Neither should have been initiated by any user/rule/event.
