Beating a dead horse over Schlage connect door lock

Configuration Z-Wave
1

I successfully excluded the lock from Smartthings (which wouldn’t control it through HA even though it was seen) I expect I successfully added a secure node to my Aotec Zstick because the lock is visible in my entities now, though none of the sensors that I’ve seen listed elsewhere. It always shows as unlocked. I cannot control it through HA. Here is the log output when trying to call the lock.unlock service:

2019-06-13 20:11:27.454 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2019-06-13 20:11:27.455 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2019-06-13 20:11:27.455 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x1d, 0xbd
2019-06-13 20:11:27.455 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x1e, 0xbf
2019-06-13 20:11:27.455 Detail,
2019-06-13 20:11:27.455 Info, Node003, Sending (Send) message (Callback ID=0x1d, Expected Reply=0x04) - DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x1d, 0xbd
2019-06-13 20:11:27.464 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-06-13 20:11:27.464 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-06-13 20:11:28.682 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0x1d, 0x00, 0x00, 0x7b, 0x8d
2019-06-13 20:11:28.682 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x1d received (expected 0x1d)
2019-06-13 20:11:28.682 Info, Node003, Request RTT 1226 Average Request RTT 1141
2019-06-13 20:11:28.682 Detail, Expected callbackId was received
2019-06-13 20:11:37.456 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-06-13 20:11:37.457 Detail, Node003, Removing current message
2019-06-13 20:11:37.457 Detail, Node003, Notification: Notification - TimeOut
2019-06-13 20:11:37.460 Detail,
2019-06-13 20:11:37.461 Info, Node003, Sending (Send) message (Callback ID=0x1e, Expected Reply=0x04) - DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x1e, 0xbf
2019-06-13 20:11:37.469 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-06-13 20:11:37.469 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-06-13 20:11:38.746 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0x1e, 0x00, 0x00, 0x80, 0x75
2019-06-13 20:11:38.746 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x1e received (expected 0x1e)
2019-06-13 20:11:38.746 Info, Node003, Request RTT 1285 Average Request RTT 1213
2019-06-13 20:11:38.746 Detail, Expected callbackId was received

Any thoughts as to why this isn’t working and how to make it?

2

It doesn’t look like it’s been included Securely. You should see some messages about encrypting the packet in OZW log if it was.

3

So after excluding and adding about 3 times it just finally decided to work. Unfortunately I lose my Alexa control of it when I set it up as z-wave. I can run it through emulated Hue but Alexa doesn’t know how to lock or unlock it when she sees it as a light. I put it back on Smartthings and out of Home Assistant until I figure out how to get DuckDNS working properly so I can connect Smartthings without MQTT.

4

You can still lock/unlock with z-wave using scripts. Expose the scripts to emulated hue. You will also need to setup alias with Alexa for commands such Lock/Unlock so you don’t have to say Turn Off/On.

lock_door:
    sequence:
      - service: lock.lock
        data:
          entity_id: lock.door
  unlock_door:
    sequence:
      - service: lock.unlock
        data:
          entity_id: lock.door