I have a System Start piston that used to work about 20 beta's ago, so 3 months?
Part of the start is to reset all ZB bulbs to off as sometimes they are on from a power restoral or a hub restart. We have many on beta.
I have been chasing the failure of the lights to reset with delays and such but to no avail.
I was worried I might be overwhelming the ZB radio.
What I am finding is that after a reboot a lot of my ZB bulbs refuse to work from the Devices page or WebCore pistons; the System Start piston fails to turn the bulb on and off most of the time now. I have tried many drivers (Adv ZigBee, Sengled Classic and Legacy) no change.
I found that if I send the Devices a Set Level first then all the bulbs/groups respond right away.
Any ZB insight here? I have a gut feeling it's an HE change for the radio software; initialization for the ZB devices on reboot perhaps? @gopher.ny
Is "rebuild network on reboot" setting in Zigbee details on, by any chance?
To clarify, the commands appear in respective devices' Events, but they fail to act on it.
Also, please PM me the hub id
Rebuild on Reboot is not on.
Last reboot some light got the On command, some got On and Off.
The Groups, from the build in app, sometimes get On and SetLevel commands but no Off command.
A real mix. I have tried a full minute delay before any actions to allow the hub to settle in but it made no difference.
Here's the piston just for reference.
Hi @dnickel, did you ever get this figured out? I'm trying to do something similar and came across this post during my search. Mine is for three troublesome Zigbee light bulbs that stay on after a power failure. Just wondering if it was resolved or if any lessons learned came out of it.
I was on Groups and Scenes but moved back to Room Lighting; not sure if I mentioned that.
I solved my issue with the Setlevel but then, after some screwing around, found that I was not consistent with these 2 settings:
After I fixed those for the ZB light groups things started acting much nicer.
I was also trying different drivers in the mix and HE got really confused not having one common driver and these 2 settings.
I am a beta tester so everything has been ok until a week ago when I noticed the whole group wasn't coming on in the bedroom; about the time I went to a new beta release.
I put back SetLevel on my groups upon reboot as a test to see if that cures the issue.
