mhilbush
(Mark)
October 16, 2018, 12:31pm
1
My August lock reports not only the condition of the lock, but it also reports whether the door is opened or closed based on a sensor that’s integrated into the lock. This negates the need for a separate open/close sensor. Other locks may have this functionality, but I don’t specifically know of any at this time.
The door open/close indicator is included in the doorcondition
byte in position bit 0 (Table 36 in the Z-Wave Command Class spec).
Currently, it looks like the binding doesn’t do anything with the doorcondition
field. This field could be used to populate a sensor_door
or sensor_binary
channel.
@chris WDYT?
chris
(Chris Jackson)
October 16, 2018, 12:56pm
2
This should be possible. I suspect many locks don’t provide this, but we can probably have the option to add this channel into the database, and then populate it if it exists.
Let me have a look at it over the next couple of days.
mhilbush
(Mark)
October 16, 2018, 12:58pm
3
Thanks. Makes sense.
Want me to add an issue so that it can be tracked? Or, hold off on that until you look at it more closely?
mhilbush
(Mark)
October 16, 2018, 1:03pm
4
For others who want to see if their door lock reports open/close status, there’s a debug statement that starts with Door-Lock state report
that shows the value of the doorCondition
byte. Bit 0 would change based on the door being opened or closed.
chris
(Chris Jackson)
October 16, 2018, 1:13pm
5
Yes please.
Please link to the database for your lock so I can add the channel without having to work out exactly which database entry it is .
chris
(Chris Jackson)
October 16, 2018, 5:42pm
6
@mhilbush note that the channels will change as the current door channel uses the sensor_door
channel. I will change this to what it should be which is lock_door
and then use the sensor_door
for the door state.
Sorry for changing the channels - I know you’re not so happy with such change, but I think it’s the best approach.
mhilbush
(Mark)
October 16, 2018, 6:36pm
7
chris:
change this to what it should be which is lock_door
and then use the sensor_door
for the door state
I agree it’s the best approach. My main objection concerned the deletion of channels for no obvious reason (at least it wasn’t obvious to me).
Thanks!
mhilbush
(Mark)
October 16, 2018, 7:26pm
8
chris:
the current door channel uses the sensor_door
channel. I will change this to what it should be which is lock_door
and then use the sensor_door
for the door state
I’m officially confused.
My current item definition is this, which already uses lock_door
.
Switch BasementDoorLock "Basement Door Lock [%s]" { channel="zwave:device:zstick:node94:lock_door"}
And the thing definition in the current binding also shows lock_door
.
<channels>
<channel id="lock_door" typeId="lock_door">
<label>Door Lock</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_DOOR_LOCK</property>
</properties>
</channel>
...
</channels>
chris
(Chris Jackson)
October 16, 2018, 7:33pm
9
Then I’m confused as well, as the database doesn’t show this -:
This shows that the sensor_door
channel already exists, and the lock_door
has been added.
However, in the documentation (which also comes from the database, but a slightly older version), it does confirm what you see -:
So, I guess that someone has updated the channels in recent times . Anyway, this will move it back again.
1 Like
chris
(Chris Jackson)
October 20, 2018, 9:52am
10
FTR -:
@mhilbush there is a link on GH to a precompiled version - it would be great if you can test this.
mhilbush
(Mark)
October 20, 2018, 10:26am
11
chris:
it would be great if you can test this.
Working on it now. Thanks!
mhilbush
(Mark)
October 20, 2018, 10:46am
12
@chris When I deleted and rediscovered the lock, I’m not seeing the door_sensor channel.
While the database entry looks right, I don’t think the August ASL-03 thing definition got updated to include the new channel.
chris
(Chris Jackson)
October 20, 2018, 10:48am
13
Hmmm - I did a complete database update, so I assumed it should have been included…
mhilbush
(Mark)
October 20, 2018, 10:50am
14
chris:
I did a complete database update
Just looked at that PR. There’s a wording change to the asl-03, but the new channel’s not there.
chris
(Chris Jackson)
October 20, 2018, 10:51am
15
Strangely it doesnt seem to be there…
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0
http://eclipse.org/smarthome/schemas/thing-description/v1.0.0">
<thing-type id="august_asl03_00_000" listed="false">
<label>ASL-03 August Smart Lock Pro 3rd Gen</label>
<description><![CDATA[
August Smart Lock Pro 3rd Gen<br /><h1>Overview</h1><p>Give your customer total control over their front door, from anywhere. The August Smart Lock Pro is the leading Z-Wave Plus retrofit smart lock. You can lock and unlock your door, create virtual keys for guests, and keep track of who comes and goes with a 24/7 activity log, all from your iOS or Android smartphone.</p> <p>The August Smart Lock Pro features Z-Wave Plus and BLE and it is the only lock to support the three leading voice-assistants, Siri, Google Assistant, and Amazon Alexa. The lock quickly installs on the inside of your door with just a screwdriver. Keep your exterior door hardware exactly as it is and use your traditional key any time.</p> <br /><h2>Inclusion Information</h2><p>In order to include the August Smart Lock on to a Z-Wave network the user will have to do the following:</p> <ol><li>Open the August app</li> <li>Go to the Lock Settings screen</li> <li>Select Z-Wave Settings</li> <li>Select Add To A Z-Wave Network</li> <li>Put the controller into inclusion mode and select My Hub is in Inclusion Mode on the August app</li> </ol><br /><h2>Exclusion Information</h2><p>In order to exclude the August Smart Lock from a Z-Wave network the user will have to do the following:</p> <ol><li>Open the August app</li> <li>Go to the Lock Settings screen</li> <li>Select Z-Wave Settings</li> <li>Select Remove Z-Wave Device</li> <li>Put the controller into exclusion mode and select My Hub is in Exlusion Mode on the August app</li> </ol><br /><h2>Wakeup Information</h2><p>Any operation (manual, RF, etc.) will wake up the lock.</p>
]]></description>
<category>Lock</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="lock_door" typeId="lock_door">
<label>Door State Sensor</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_DOOR_LOCK</property>
This file has been truncated. show original
chris
(Chris Jackson)
October 20, 2018, 10:52am
16
Ok, I think the issue is the exporter isn’t expecting multiple channels for this command class, so it’s just exporting the first one it finds…
I’ll update this…
mhilbush
(Mark)
October 20, 2018, 10:54am
17
chris:
the exporter isn’t expecting multiple channels
Ah, that would explain why the channel wasn’t there when I did an export…
chris
(Chris Jackson)
October 20, 2018, 10:57am
18
Yep - I think so
The exporter is updated - I’ll do a build in a few minutes…
chris
(Chris Jackson)
October 20, 2018, 11:05am
19
Ok, the JAR is updated. I kept the link the same, so the JAR has the same filename as before - slightly confusing with the time, but the link remains the same…
mhilbush
(Mark)
October 20, 2018, 11:15am
20
One thing I want to mention unrelated to this change…
After installing the new binding (this latest one and the previous one), all my nodes are showing Request NIF
in HABmin, although in the log I clearly can see the nodes completing initialization. Did something change that would cause this?