August Pro Door Sensor not working

[dxdc]

I have an August Pro door lock that I've added via Z-wave It adds 2 devices:

The first device has multiple properties (lock/unlock, alarm, battery, etc.). The second device just has lock/unlock.

Both the first AND second device can be used to lock/unlock the device, so I'm not sure the purpose of the second device since it seems to replicate the first lock entirely. But, there is also supposed to be a DoorSense contact sensor (https://community.smartthings.com/t/release-august-pro-smart-lock-z-wave-devicehandler-with-doorsense-support/178305) which, at least from that post, seems like in theory it can be accessed.

Is there some way this could be integrated, even if via some custom configuration? Happy to test it here on my end as well. Thanks!

- https://github.com/rafaelborja/SmartThingsAugustPro/blob/master/devicetypes/rafaelborja/child-contact-sensor.src/child-contact-sensor.groovy
- https://github.com/rafaelborja/SmartThingsAugustPro/blob/master/devicetypes/rafaelborja/august-lock-pro-zwave-lock-with-doorsense.src/august-lock-pro-zwave-lock-with-doorsense.groovy

[gviliunas]

Just to confirm what you are seeing. I have had an August Pro for the past ~2 years. Yes, this adds to ISY with 2 nodes. I put the second node in the Unused Nodes pile.

For the first node, I only use this for door lock/unlock status. I can command a lock/unlock if I want but almost never do since auto-lock is enabled.

I do have a program that lets me know if the lock is unlocked for > 3 minutes. 

The battery level monitoring is nearly useless. You get notification as the lock is failing to operate. I just listen for the sound during locking and can determine when to replace batteries.

 

[dxdc]

Thanks for the reply @gviliunas.

Since this feature is available on other Z-wave devices (like Smartthings), it seems that it should be accessible from ISY doesn't it?

For me, the >3 min unlocked state isn't practical or realistic.. but if you're someone who is keeping your door locked 99% of the time I can see the value.

Are your notifications through ISY or are you using another technology to do it? I have used Prowl's API in the past, but haven't messed around with integrating it. I'm still working on figuring out the best way to integrate ISY with NodeRED. That would be a match made in heaven!

[dxdc]

I'm sharing the following XML data, which hopefully helps. I retrieved this data using the REST API. Notice that for the second node I've just added "2" after the name.
 

<?xml version="1.0" encoding="UTF-8"?>
<nodeInfo>
  <node flag="128" nodeDefId="UZW000F">
    <address>ZW012_1</address>
    <name>Door Lock</name>
    <family>4</family>
    <type>4.64.3.0</type>
    <enabled>true</enabled>
    <deviceClass>0</deviceClass>
    <wattage>0</wattage>
    <dcPeriod>0</dcPeriod>
    <startDelay>0</startDelay>
    <endDelay>0</endDelay>
    <pnode>ZW012_1</pnode>
    <sgid>1</sgid>
    <devtype>
      <gen>4.64.3</gen>
      <mfg>831.1.1</mfg>
      <cat>111</cat>
    </devtype>
    <ELK_ID>A14</ELK_ID>
    <property id="ST" value="100" formatted="Locked" uom="11"/>
  </node>
  <properties>
    <property id="ALARM" value="8" formatted="Remotely Locked" uom="15"/>
    <property id="BATLVL" value="100" formatted="100%" uom="51"/>
    <property id="ST" value="100" formatted="Locked" uom="11"/>
  </properties>
</nodeInfo>

 

<?xml version="1.0" encoding="UTF-8"?>
<nodeInfo>
  <node flag="0" nodeDefId="UZW0010">
    <address>ZW012_111N002</address>
    <name>Door Lock 2</name>
    <family>4</family>
    <type>4.64.3.0</type>
    <enabled>true</enabled>
    <deviceClass>0</deviceClass>
    <wattage>0</wattage>
    <dcPeriod>0</dcPeriod>
    <startDelay>0</startDelay>
    <endDelay>0</endDelay>
    <pnode>ZW012_1</pnode>
    <sgid>111</sgid>
    <devtype>
      <gen>4.64.3</gen>
      <mfg>831.1.1</mfg>
      <cat>111</cat>
    </devtype>
    <ELK_ID>A15</ELK_ID>
    <property id="ST" value="100" formatted="Locked" uom="11"/>
  </node>
  <properties>
    <property id="ALARM" value="" formatted=" " uom="0"/>
    <property id="BATLVL" value="" formatted=" " uom="0"/>
    <property id="ST" value="100" formatted="Locked" uom="11"/>
  </properties>
</nodeInfo>

 

[tmorse305]

The ISY does not install the August Lock correctly.  The 2nd node should be the contact sensor but I found it did not work correctly.  I notified UD support so they are aware of the issue.  I am using a Hubitat controller exclusively for the lock and connecting lock status to the ISY via the ISY Portal.  The Hubitat correctly installs the lock as lock device and a contact sensor

[dxdc]

@tmorse305 thanks for confirming the same behavior. Hubitat has to rely on however ISY sets up the device, so presumably it's the same issue.

[tmorse305]

On 3/31/2020 at 4:46 PM, dxdc said:

@tmorse305 thanks for confirming the same behavior. Hubitat has to rely on however ISY sets up the device, so presumably it's the same issue.

In my setup I have disabled ISY as the Z-Wave controller and am using Hubitat instead for that purpose.  Hubitat passes lock status and contact status to an ISY variable via the portal.

[dxdc]

31 minutes ago, tmorse305 said:

In my setup I have disabled ISY as the Z-Wave controller and am using Hubitat instead for that purpose.  Hubitat passes lock status and contact status to an ISY variable via the portal.

Thanks for confirming. Hope ISY can help with the firmware/software to resolve this.

[dxdc]

@Michel Kohanim Is this on your radar for a future update? It would be a huge help for me to be able to tie automation to door events.