Z-wave device slow or do not respond after firmware update

[murzik]

710 works well for me.

[max.leung]

Does that mean 707 wasn’t working for you?

Off-topic: At the moment, I am not able to update - my Download Progress is stalled at 0%. Similar problem I’ve had when I first got the hub and it would refuse to update, but suddenly worked again after a few hours. I’ll create a new thread for that later if it doesn’t resolve itseld.

[murzik]

707 was working for me. 709 was not.
Try to delete RM lock rule and recreate.

[danfox52]

@max.leung

I just got the Hubitat 10 days ago, and updated to 1.0.5.707 . I was wondering why my Schlage Connect (Z-Wave) locks were very slow to lock/unlock when using Rule Machine. If I use the Device command there is usually a 1-2 second delay. Under RM, it's usually 5 seconds or so. A few times it didn't work at all.

You guys still having issues after 1.0.5.710 update that just dropped? What previous update should I try if I want to remove the delay? Thanks!

I don't think RM is the problem. I was in touch with support today and they are looking into it.

[max.leung]

Ok. One thing I noticed, on version 707 and 710, that if I enable logs for the locks, and then lock/unlock through either RM or the Device page, the message is shown twice - with the 2nd lock/unlock message occuring 5 seconds after the first one. I assume this is by design, in case the first one doesn’t make it through?

[mike.maxwell]

@max.leung

I assume this is by design, in case the first one doesn’t make it through?

RM nor the driver is sending duplicate commands to the lock, the lock may be reporting twice, but nothing on Hubitat is commanding it twice.
It is possible that the command is being repeated at the zwave network layer I suppose.

[max.leung]

I’ll have to enable debug logs for both locks to make sure they didn’t get the command twice. It could be that I have a ghost RM rule in there - I’ve had an issue before where I delete a rule from RM, and create a new rule, but when I check one of the devices, it lists two RM rules - the new one I made and the one I deleted! Very strange (this was on 707).

[EdwardN]

This actually appears to be a glitch that several people are reporting. Thank you for pointing out the way to identify it as such. Can you access the rule from the link on the device page?

[max.leung]

I was able to delete the rule after clicking on it in the device page. It is possible I may have hit back button at the wrong time in the browser after the first attempt at deleting it, but I cannot be sure.

[EdwardN]

That’s good news then! It should be easy to find and remove orphaned rules by just accessing the device page.

I always prefer solutions that are self-help.

[davechudley]

Im having the same issues on the latest release. Updated hub on 25th sept, now z wave devices on responding.