Events that I don't understand a delayed light

Have a motion lighting app setup with basic rules

3 motion sensors to trigger
turn on 2 lights to 50% with a delayed off of 8min.

walk in... 1 of the lights (zigbee osram strip) turns on in a second. The other a Inovelli nzw31 has a long delay (17 seconds) before the lights come on. This is the only clue I could find in the logs:

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:45.225:debug'zw device: 35, command: 2603, payload: 3C 3C 00 ' parsed to [[name:switch, value:on], [name:level, value:60, unit:%]]

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:45.144:debug'zw device: 35, command: 2603, payload: 3C 3C 00 ' parsed to [[name:switch, value:on], [name:level, value:60, unit:%]]

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.898:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.848:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.697:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.630:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.330:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.299:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.213:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:44.162:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:43.901:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:43.678:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

[dev:259](http://192.168.13.46/logs#dev259)2018-10-31 20:56:41.092:debug'zw device: 35, command: 2003, payload: 3C ' parsed to null

at 27 seconds after the minute the motion sensor was tripped. at 28 seconds after the osram turned on and at 45 seconds after the Innovelli.

Normally I would easily say this is something with the zwave...BUT it's consistent. If I stand there with the device open in the browser and click On and Off it turns on and off almost immediately....however when I wait and trigger the rule...this happens? Coincidence? It seems pretty repeatable.

1 Like

I too have consistent delays when turning off multiple lights.
I have a custom Particle Photon device I've ported over from SmartThings so I've always chalked it up to that.
Interesting to see you're seeing delays with z-wave and zigbee.

I've had to split up turning off multiple devices into multiple rules triggering each other. Two different things here (delay in turning on the lights as above) and if I try to turn off 30 lights (nighttime) it almost never gets them all. So SOMETHING is going on. This used to work fine in ST.

1 Like

When we go to bed I'm seeing long delays when turning off several lights too, sometimes 20+ seconds. Sometimes I have to either re-run the trigger (minimote button) or manually turn off the lights. I have not done anything to troubleshoot yet.

2 Likes

Try instead to put them all into a Group, and turn on the Zigbee group option. See if that gets them all off as expected.

Looked at documentation and couldn't find...I'm assuming ONLY put my zigbee lights in that group and turn that group on? Or can I put zwave and zigbee in one group and turn that on?

Also, renaming Groups does not work.... Meaning I can rename it. And under the groups list it shows with the new name. But inside rules where the group name shows up it's always the original name of the group prior to changing it. Even when creating a new rule after the name change.

Don't rename Groups. A Group, or a Scene, creates a virtual device of the same name given to the Group. That device is what is used to turn on and off the Group. In the case of a Scene, it creates two devices, one with the name of the Scene and one with that name plus Capture.

Yes, you may mix Z-Wave and Zigbee devices in a Group. It knows how to tell the two apart. It will group the Zigbees together so that a single command turns all of them on or off, while for the Z-Wave, it will do them one by one.

Still not working. I left this evening and came back to 1/2 of my lights on... I'm going to need to design some kind of rule that just keeps looping through turning off lights until they are all off. My goodnight and goodbye routine leave lights on every time.

The other easier option may be to just use Otherhub to move them over to ST and let the ST routine do it.

Then possibly don't allow renaming of groups. Because...it lets you. :smile: And is super confusing later.

Please contact support@hubitat.com so we can look at your logs. There should not be any reason you can't turn off 30 lights from a Group or a rule. Would really like to get to the bottom of it.

As for renaming groups, perhaps we could rename the group dimmer when this happens.

done, thanks