Lock.lock service call fails under certain conditions - (Schlage Connect Z-Wave)

@ten000days wrote:

I am having an issue where lock.lock fails sometimes. Specifically, if the lock was most recently unlocked manually (either by turning the deadbolt by hand, or punching the code in the keypad), then the service call will fail once, and then succeed if I run it a second time.

Setup details:

Home Assistant: Version 0.96.3 in a virtual environment on a Raspberry Pi 3
Z-Wave controller: Nortek HUSBZB-1 USB stick
Lock: Schlage (Allegion) BE469ZP Connect Smart Deadbolt (Z-Wave)

Some observations:

• If I alternate calling lock/unlock from HA without physically manipulating the lock, then the call doesn’t fail
• If I wait a few minutes after physically unlocking it, then sometimes lock.lock works on the first try
• The opposite is also true: if I physically lock the deadbolt, then lock.unlock fails once
• The lock’s “lock_status” attribute is often incorrect or misleading (says unlocked when it’s really locked, etc.). I can provide more detail on this if it would be helpful

My Z-Wave configuration:

zwave:
  usb_path: /dev/ttyUSB0
  network_key: !secret zwave_network_key

The API call from the Developer tab:

Service: lock.lock
Entity: lock.schlage_allegion_be469zp_connect_smart_deadbolt_locked
Service Data: { "entity_id": "lock.schlage_allegion_be469zp_connect_smart_deadbolt_locked" }

I tried setting the ZWave logger to debug but couldn’t find anything helpful in the log, though maybe someone can tell me what to look for.

Would really appreciate any advice!

Posts: 1

Participants: 1

Read full topic