OK, so now let's figure out "What type of Z-Wave lights or switches you are using?"
Also, when you're in the Device Details page for one of the 'problem lights', does the status change instantly when you click the ON or OFF buttons? I know the light itself changes immediately... I want to know whether the status in Hubitat changes immediately or not.
Also, what driver is being used for these z-wave devices?
Are you using the Z-Wave Poller at all?
Fair enough, that was just my experience once updating alot of my devices turned to null and my repeaters stopped working even after power cycling.
When I go into the device for one or both of the lights and click on the status does change to on when I click off status changes to off instantly.
These are GE Z-Wave paddle switches. They are not Z-Wave plus.
driver being used on all my GE paddle switches is the generic Z-Wave switch driver
Thanks for the update... That definitely seems to be the correct driver for them. These are also the Z-Wave switches that caused me to upgrade to Lutron Caseta as I grew weary of their issues.
Are you running the Z-Wave Poller App? If so, try disabling it and letting your Z-Wave Mesh settle down. My experience is that it caused more issues than it solved.
Yes I am running the Z-Wave puller. I will disable this let it come down for a little bit
to that theory - scenes weren't touched in this release either.
You can see from the attached log that the kitchen motion was triggered then the rule was parsed then before the lights even turned on the motion sensor went inactive then the lights turned on.
Something definitely seems wonky.
can you throw up your Sl rule, and also on the device page (for the light - be it the device or group if its in a group) a screenshot of the "in use by" section pls.
so looking at your log,
kitchen motion at 1014
kitchen light night on at 1014
kitchen motion inactive at 1015
kitchen light on at 1015
So the MS fires at 1014, the rule fires at 1014 and the light turns on a 1015 ?
how did the test go with motion lighting ?
@stevebott123. Yes you are correct. I'm testing the motion lighting app right now. I tried that one a while back and for some reason it wasn't working good that's why I switched to the simple lighting. Give me 5 minutes and I'll send you another log
@stevebott123. Here's the log using the motion lighting app. As you can see another delay in turning lights on after trigger.
kitchen light {digital} and kitchen light, are they the same thing ?
ones device 8 and the other 39
it is quicker though, 10.51.34 to 10.51.43 ?
cause it looks like you have
motion kitchen - dev 34
motion kitchen - dev 9
kitchen light on - dev 8
kitchen light on - dev 39
Its hard to tell using grabs from a mobile but Device 8 is living room motion sensor.
Can confirm... I had zwave and zigbee issues after the last patch.
You can read my post above but now everything seems to be settling down and working again. Thank God though cause that was frustrating
seems to be something that might of gone wrong that @bobbyD can have a look at.
lots of people all having issues with their battery powered zigbee and zwave devices after patch .130
Ok so this mornings results.
My HSM is set to disable at 5:30am. This did not happen and when I opened the mudroom door...bam alarm went off. I could NOT turn any lights off from dashboard or from within devices.
Kitchen lights saw motion triggered rule but lights did not come on again.
Rebooted
It now seems worse then last night
Chances are that your Z-Wave repair is still running. The more you reboot your hub, the longer the repair takes. And while the repair is running, you cannot really expect anything to run properly, as the repair uses 100% of your Z-Wave bandwidth. Best time to run repair, is overnight as it may take many hours to complete, depending on the state of your mesh and how large it is.
Download the Hubitat app
