August Pro now supported

Posted on
Fri Dec 07, 2018 11:01 am
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

@rapamatic - I finally installed my DoorSense and configured it. I now have a beta of the plugin with a new device to indicate the state of the door. Reach out if you want early access. I need to test it and improve the state on startup before I publish.

Posted on
Fri Dec 07, 2018 11:14 am
rapamatic offline
Posts: 270
Joined: Aug 03, 2015
Location: Glencoe, IL

Re: August Pro now supported

vtmikel wrote:
@rapamatic - I finally installed my DoorSense and configured it. I now have a beta of the plugin with a new device to indicate the state of the door. Reach out if you want early access. I need to test it and improve the state on startup before I publish.


I'd be happy to check out and test the beta - I know a lot of people probably have other z-wave sensors on their doors, but I don't, so it would be useful to track the door status and have my sonos speakers yell at the kids when they leave the front door open. I think it would also be useful to add a bit more logic to the auto-lock feature on the August lock, to, for example, temporarily bypass the auto lock....

I haven't seen the out of sync problem lately - I suspect it had more to do with my weak z-wave network (I've since added several repeaters), since I have very few z-wave devices in my house.


Sent from my iPad using Tapatalk

Posted on
Fri Dec 07, 2018 11:55 am
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

Yes I have a z-wave sensor on my door which is why I wasn't first to jump on the DoorSense.

If you mean that you wish August would allow to bypass the auto-lock, I agree. I would not be able to implement that in the plugin. My own use has found that I prefer to disable August's auto lock and I've implemented my own through Indigo. I personally have a simple python script that determines when to lock the door, taking into account the time of day, activity (motion and opening/closing of the door) in the front of the house, the season of the year, and amount of time that the door has been unlocked. I use a Indigo variable to control the lock time and change it based on the time of the day.

I've also seen less problems with my lock having errors in the event log. I still do a regular status update to ensure that the state is correct in Indigo.

I'll get in touch about the beta soon.

Posted on
Fri Dec 07, 2018 12:11 pm
rapamatic offline
Posts: 270
Joined: Aug 03, 2015
Location: Glencoe, IL

Re: August Pro now supported

vtmikel wrote:
If you mean that you wish August would allow to bypass the auto-lock, I agree. I would not be able to implement that in the plugin. My own use has found that I prefer to disable August's auto lock and I've implemented my own through Indigo. I personally have a simple python script that determines when to lock the door, taking into account the time of day, activity (motion and opening/closing of the door) in the front of the house, the season of the year, and amount of time that the door has been unlocked. I use a Indigo variable to control the lock time and change it based on the time of the day.


That sounds like exactly what I'd like to do. Plus maybe a keypad button or something to also enable/disable the auto lock... I understand that it can't be in the plugin - way too many options, variables, and different ways to control the logic. I just needed some way to be able to confirm the door was closed before sending the lock command, and sounds like that's exactly what you're working on.

By the way, would you mind sharing the script you use to determine when to lock the door - I'm always curious how people do things in Indigo and looking for ideas/inspiration.

Thanks
-Ray


Sent from my iPad using Tapatalk

Posted on
Fri Dec 07, 2018 12:43 pm
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

Sure, like you said, it's pretty house specific and I didn't do a great job commenting it, but you should be able to get the gist of it.

I extensively use the Timed Devices and Group Change Listener, which are implied in this script.

Code: Select all
auto_lock_debug = indigo.variables[1756882648].getValue(bool) # "auto_lock_debug"
auto_lock_lastchanged_status_action = indigo.variables[1143764889].value # "auto_lock_lastchanged_status_action"

auto_lock_minutes = indigo.variables[961001126].getValue(int) # "auto_lock_minutes"
auto_lock_enabled = indigo.variables[559454321].getValue(bool) # "auto_lock_enabled"
auto_lock_use_extended_presence_threshhold = indigo.variables[564324677].getValue(bool) # "auto_lock_use_extended_presence_threshhold"

extended_presence = bool(indigo.devices[1828588738].states["onOffState"]) # State "onOffState" of "Front Door and Porch Presence"

front_door_lock_id = 1545960088
front_door_lock_locked = indigo.devices[front_door_lock_id].onState # "Front Door Lock"

try:
   unlocked_minutes = indigo.variables[554776568].getValue(int) # "Front_Door_Lock_via_Cloud_locked_minutes"
except:
   unlocked_minutes = 100

garage_door_closed = indigo.devices[1969968999].onState # "Garage Door"

front_door_open = indigo.devices[502552913].onState # "Front Door Sensor"

front_porch_active = indigo.devices[1864611295].onState # "Front Porch Motion Sensor"

foyer_active = indigo.devices[1059102247].onState # "Foyer Motion Sensor"

if auto_lock_debug:
   indigo.server.log("auto lock event: " + auto_lock_lastchanged_status_action)

if auto_lock_enabled and not front_door_lock_locked:
   if unlocked_minutes > auto_lock_minutes:
      if (auto_lock_use_extended_presence_threshhold and not extended_presence and garage_door_closed) or (not auto_lock_use_extended_presence_threshhold and not foyer_active and not front_porch_active and garage_door_closed and not front_door_open):
         indigo.server.log("auto locking the front door; it has been unlocked for " + str(unlocked_minutes) + " minute(s)")

         indigo.device.lock(front_door_lock_id)
      elif auto_lock_debug:
         indigo.server.log("the front door has been unlocked for " + str(unlocked_minutes) + " minute(s), and will lock once the foyer, front porch, garage are inactive and the front door is closed.")

         indigo.server.log("Foyer Active: " + str(foyer_active))
         indigo.server.log("Front Porch Active: " + str(front_porch_active))
         indigo.server.log("Garage Door Closed: " + str(garage_door_closed))
         indigo.server.log("Front Door Open: " + str(front_door_open))

   elif auto_lock_debug:
      indigo.server.log("the front door has been unlocked for " + str(unlocked_minutes) + " minute(s), which is less than the auto lock setting of " + str(auto_lock_minutes) + " minutes")      
elif auto_lock_debug:
   indigo.server.log("auto lock disabled or the door is already locked")

if auto_lock_debug:
   indigo.server.log("auto_lock_enabled: " + str(auto_lock_enabled))
   indigo.server.log("unlocked_minutes: " + str(unlocked_minutes))
   indigo.server.log("auto_lock_minutes: " + str(auto_lock_minutes))
   indigo.server.log("auto_lock_use_extended_presence_threshhold: " + str(auto_lock_use_extended_presence_threshhold))
   indigo.server.log("extended_presence: " + str(extended_presence))
   indigo.server.log("foyer_active: " + str(foyer_active))
   indigo.server.log("front_porch_active: " + str(front_porch_active))
   indigo.server.log("garage_door_closed: " + str(garage_door_closed))
   indigo.server.log("front_door_open: " + str(front_door_open))
Attachments
Screen Shot 2018-12-07 at 1.41.45 PM.png
Screen Shot 2018-12-07 at 1.41.45 PM.png (1.33 MiB) Viewed 825 times

Posted on
Sat Dec 08, 2018 12:28 pm
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

Please go ahead and try out the pre-release of v1.0.15, available on github (https://github.com/mlamoure/Indigo-August-Home/releases).

You should be able to create a second August device for the Door Sense, and link it to your lock (required to work). Do me a favor and test 1.0.15 for a few minutes before adding the new device to ensure I haven't broken anything for those without the DoorSense device added. Since it's the second device type, I had to add some conditions throughout the plugin for this change to work.

Mike

Posted on
Sun Dec 09, 2018 9:40 pm
rapamatic offline
Posts: 270
Joined: Aug 03, 2015
Location: Glencoe, IL

Re: August Pro now supported

Ok, got it working no problem, and no issues with prior functionality.

The Door Sense device is correctly reflecting the open/closed status.

However, I got this error message when I hit the update status button on the Door Sense Device:
Code: Select all
Dec 9, 2018 at 9:37:01 PM
   August Home                     sent "August Door Sense" status request
   August Home Error               Response HTTP Status Code: 400
   August Home Error               Response HTTP Response Body: {"code":"BadRequest","message":"1755508267 is not a valid lockid"}
   August Home Error               Error in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 377, in actionControlUniversal
KeyError: ('LockStatus',)



Also, it looks like the Door Sense device is acting like a basic switch - with options to turn it on or off in the interface... I wonder if it would be better to use the built in motion sensor device as the base device class? I don't know how this is done for other door/window sensors in indigo, since I don't have any...

Posted on
Mon Dec 10, 2018 8:43 am
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

Thanks, I noticed that too but missed the Status Request bug.

I've fixed that bug and converted the DoorSense to a sensor to remove the "On and Off" buttons in the Indigo client. You'll have to re-create your DoorSense device. v1.0.16 is posted to github.

Posted on
Mon Dec 10, 2018 9:04 am
rapamatic offline
Posts: 270
Joined: Aug 03, 2015
Location: Glencoe, IL

Re: August Pro now supported

So far so good. Thanks!


Sent from my iPad using Tapatalk

Posted on
Sat Dec 29, 2018 1:01 pm
bighop offline
Posts: 313
Joined: Feb 21, 2011

Re: August Pro now supported

I’m looking at the August lock pro. Will I still need a WiFi bridge if indigo is comparable with the product?

Posted on
Sat Dec 29, 2018 5:40 pm
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

August Pro now supported

bighop wrote:
I’m looking at the August lock pro. Will I still need a WiFi bridge if indigo is comparable with the product?


You’ll be missing the remote management features like adding users. You’ll be able to operate the lock remotely through HomeKit or indigo, assuming you have a HomeKit hub or access to indigo remotely. I think the August app will only work when you are near the lock without the bridge and may have less features like the “activity log”, but I’ve never tested. My plugin won’t provide any added value without the connect or a doorbell for a bridge. You can read the plugin description about those features and let me know if you have questions.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon May 20, 2019 3:07 pm
emergent offline
Posts: 49
Joined: Aug 30, 2013

Re: August Pro now supported

I've been trying to get my August Pro connected with Zwave. It connects to my Zstick fine, but then it won't sync. I've tried anything I can think of to get it to work. Any ideas?

May 20, 2019 at 5:02:46 PM
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 21 0E 32 02 21 64 00 00 00 01 00 3C 00 00 00 01 89
Z-Wave Debug . . requestMeterLevel: node 033, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 0.001 kWh (float: 0.001000)
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 21 0E 32 02 21 74 00 00 00 00 00 00 00 00 00 00 A5
Z-Wave Debug . . requestMeterLevel: node 033, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 0.000 W (float: 0.000000)
Z-Wave Syncing - started for "042 - Keypad Door Lock"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 2A 01 01 53
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 80 00 80 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5F
Z-Wave Debug . . getNodeNeighbors: nodeId 042, neighbors: 24, 40, 41
Z-Wave Syncing - retrieved module neighbors list: 24, 40, 41
Z-Wave Syncing - assigning return route to "042 - Keypad Door Lock"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 2A 01 97
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 042, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 2A 24 0E 99
Z-Wave Debug RCVD nodeInfoFrame: 01 0D 00 49 84 2A 07 04 40 03 5E 55 98 9F 59
Z-Wave Debug . . nodeInfoFrame: node 042, combined class list: 20v1 62v1 63v1 55v1 86v1 98v1 72v1 5Ev1 9Fv1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 2A 02 72 04 25 0F 91
Z-Wave Debug timeout waiting for reply from module (non-fatal, skipping request)
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 2A 02 86 11 25 10 6F
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 2A 02 86 11 25 11 6E
Z-Wave Debug RCVD sensorSetLevel: 01 09 00 04 00 12 03 20 01 00 C2
Z-Wave Debug . . sensorSetLevel: node 018, endpoint None, cmdClass 20, value 0
Z-Wave received "Entry Hall Stairs - Motion Sensor" status update is off
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 12 0A 71 05 00 00 00 FF 07 00 00 00 7F
Z-Wave Debug . . requestAlarmSensorStatus: node 018, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 2A 02 86 11 25 12 6D
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug maximum retry count exceeded waiting reply from module
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "042 - Keypad Door Lock". Module might be asleep, or is unreachable.

Posted on
Mon May 20, 2019 3:36 pm
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

Using encryption, correct?


Sent from my iPhone using Tapatalk Pro

Posted on
Mon May 20, 2019 5:55 pm
emergent offline
Posts: 49
Joined: Aug 30, 2013

Re: August Pro now supported

I was. I got it to work finally by taking the lock off and bringing it to the zstick plugged in to the computer. Indigo should put a note somewhere that the zstick has to be plugged in to the computer and the lock needs to be right next to the zstick for it to work for encrypted devices.

Posted on
Tue Jul 02, 2019 7:04 am
vtmikel offline
Posts: 511
Joined: Aug 31, 2012
Location: Boston, MA

Re: August Pro now supported

I'm curious if anyone with the August Pro has had any problems using their lock with Indigo recently. As I recall, my problems trace back to a firmware update that August pushed to my lock about a week ago. I have a thread with their technical support to look into it.

My symptoms are that the August is controllable by Indigo via Z-Wave after removing the battery and re-inserting, but only for a period of time. After a small amount of time (few hours), the lock stops responding to Z-wave lock and unlock commands, but is responding to status requests. HomeKit and Bluetooth commands to lock and unlock work fine.

Who is online

Users browsing this forum: No registered users and 1 guest

cron