I have a shut the house down routine that basically turns everything off when I arm the house it works most of the time but sometimes not all my lights turn off.
I have set up two light scenes one for lights in the house ( 11 zwave dimmers, 8 zigbee rgbw controllers, 2 zwave rgbw controllers and 3 nanoleafs) and one for out side lights ( 32 zigbee gu10s and 2 zwave switchs)
The problem is the lights that don't turn off are shown as off in the hub so I have to turn them on and then off, and its not always the same lights.
I have tried pretty much all the options in light scene but have the same issue.
As long as you don't have optimization enabled for scenes, the "Off" command should be sent even if the bulbs are off. (If you do have optimization enabled, Hubitat will avoid sending commands that would put the device in the desired state if that state is reported as the current state--including on/off.) If your bulbs aren't responding to this command, then there is another problem, which there could be already if they aren't reporting state back correctly. I'm particularly curious what Zigbee bulbs you have and what the rest of your Zigbee network looks like, as many of those are known to be problematic repeaters that can cause odd issues (but that wouldn't explain Z-Wave).
Another thing you can try is to enable the "metering" option in groups and scenes, which spaces out the commands a bit. Both Z-Wave and Zigbee will probably be happier if you don't flood their networks with a bunch of commands at nearly the same time. If you want to keep the delay small, maybe start closer to 100 ms and see if that helps, otherwise I'd increase it as much as you can tolerate, which for this kind of thing might be pretty long (not like you need them to all turn off at the same time, I assume?).
Finally, for the Zigbee devices, using a group instead of addressing the devices indivudually is likely to work better (enable Zigbee group messaging in that group)--one command for the whole group instead of one per bulb. Similar to the above suggestion, this will likely cut down on network traffic. Hubitat doesn't support Z-Wave multicast, so while you can group Z-Wave devices, there isn't any technical benefit at the moment, and metering in the scene should work just as well.
Completely agree with the use of "metering". Since you are leaving, it should be OK to have the lights take a while to turn off. Suggest having at least one second delay between each device.
Oooo i thought metering was todo with power so never turn that on ill give that a go.
The zigbee bulbs are ledvance rgbw gu10's they seem to work well I have them split into 4 different groups and it's rare that they don't work very occasionally one group doesn't respond.
I made a separate group with all of my Zigbee devices that I turn off at once. No metering, that’s for z-wave, but make sure Zigbee group messaging is on and optimization is off. I have many Ledvance recessed lights btw.
Slightly off topic, but doesn't z-wave do any type of checks in it's conversation? It seems like an easy fix to me, controller sends off command, switch sends back confirmation. If no confirmation, resend off command. Why doesn't this exist?
It does--that sounds a lot like Z-Wave Supervision, though not all devices support it and not all drivers use it. I'm not sure if it's tied specifically to S2, but either it is or that's the only time I've managed to be able to use it on my own drivers (and on Hubitat, that is part of the driver and not a platform feature). So, security isn't all bad like some would have you believe.
Z-Wave as a whole also should "ACK" (acknowledge) a successful command and retry or report failure after successive tries without hearing back, but that much is handled at a level below drivers and I'm not as familiar with how it works.
