Yale Assure SL ZWave Lock Battery Refresh After Changing

After changing my batteries, the lock continues to report 1% battery level. I have refreshed, repaired and rebooted, but nothing changes. The lock does not respond to commands, although the attempts are logged. The lock is also connected and reachable on the Zwave network. Help please.

I assume you tried some other new batteries or checked voltage on the ones you are using to confirm they really are good batteries?

How do you know its reachable if it does not respond?

Sounds to me like you need to try some other batteries. It may not report the new battery % right away, sometimes you just have to wait for the device to report in on its own with the battery level.

Also might be worth doing a shut down on the hub and unplug for 30 seconds so the radio can reboot.

Thank you. Every command being sent is recorded in the log. The batteries are Duracell and have tested as fully charged. I’ll unplug for 30 seconds and see if that helps.

That does not really tell you much of anything in regards to connectivity. Thats just the driver debug logging saying you ran the lock or refresh command.

Most definitely looks like the lock is not talking to the hub at all in its current state.

I would pull the batteries on the lock for 30 second also, so the lock can reboot too.

I’ll give it a try, thank you.

How many line-powered z-wave devices do you have? What does your z-wave mesh look like?

I have a lot of coverage, signal isn’t an issue.

Tried pulling the batteries for 30 seconds and rebooted and unplugged the hub for 30 seconds and still no change.

Seems like it got reset somehow.

You might need to exclude and include again.

You could create a virtual lock and then use the swap device to swap your automations to the virtual lock so it doesn’t break it all if the exclude works correctly.

If the exclude does not delete the existing node you could try the “replace” on it so you are not left with a ghost node.

I assume yours is S0 security like the one I have so you won’t have to worry about DSK codes when pairing.

Thank you, it has miraculously reestablished full communication and battery status. It’s hard to tell exactly what was responsible, but thanks to all for the suggestions.

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.