Can't communicate with lock

[larrywal32]

One of my locks says unknown status and hs3 is saying it can't communicate with the lock. It was fine yesterday.

I tried going to the device z wave tab and pressing rescan and I also tried running optimize. It says it can't reach it.

But on node config it says it's recognize about 50 neighbors.

It's a schlage connect.

What should I try next? It's a little disconcerting my door lock just started doing this...

[NetworkGuy]

I'd try a battery change. Did you wake it first before your rescan?

[larrywal32]

No....how do I do a wake? Can I do that remotely?

The lock is only a week old and was reporting 100% battery yesterday...

[NetworkGuy]

May not be a battery then, but battery devices are asleep most of the time. You cannot reach them without first waking them up. On their own, they wake up only periodically to report status (e.g. lock, battery, etc.).

You will need to refer to the manual to find out how to wake it up.

No....how do I do a wake? Can I do that remotely?

The lock is only a week old and was reporting 100% battery yesterday...

[larrywal32]

I guess what doesn't make sense is that sending lock and unlock commands aren't being respected either. And those should always work.

The node information is also saying no known route. Very weird.

[NetworkGuy]

That is weird. I don't have any locks, but have a number of battery devices. Maybe locks operate differently because of what you indicate - they should be operable remotely.

Sorry, you may need someone else with lock experience to help.

I guess what doesn't make sense is that sending lock and unlock commands aren't being respected either. And those should always work.

The node information is also saying no known route. Very weird.