Z-Wave Lock Events Script - Discussion Thread

[Ltek]

Al,
I think the below logs show the 2 bugs I've been seeing.


Remote shows as 'Manual' & Lock action sends an Unlock notification...

Aug-15 10:37:12 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:37:12 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 22:37:11
Manual Unlock Operation (2) 2017-08-15 22:32:02
Manual Unlock Operation (2) 2017-08-15 20:40:46
Manual Unlock Operation (2) 2017-08-15 20:40:32
Manual Unlock Operation (2) 2017-08-15 20:40:03
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Aug-15 10:37:12 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:37:12 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 10:37:12 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 10:37:12 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 10:37:12 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:37:12 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 10:37:12 PM Door Lock Log DB Insert 1082-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-22:37:11
Aug-15 10:37:11 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:37:11 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:37:11 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:37:11 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 10:37:11 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 10:37:11 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 10:37:11 PM Z-Wave Device: Door Lock Mudroom Lock Set to 255
Aug-15 10:37:10 PM Device Control Device: Door Lock Mudroom Lock to Lock (255) by/from: CAPI Control Handler

Remote lock/unlock notifications sending as 'Manual'...

Aug-15 10:32:02 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:32:02 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 22:32:02
Manual Unlock Operation (2) 2017-08-15 20:40:46
Manual Unlock Operation (2) 2017-08-15 20:40:32
Manual Unlock Operation (2) 2017-08-15 20:40:03
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Aug-15 10:32:02 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:32:02 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 10:32:02 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 10:32:02 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 10:32:02 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:32:02 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 10:32:02 PM Door Lock Log DB Insert 1081-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-22:32:02
Aug-15 10:32:02 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 10:32:02 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:32:02 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 10:32:02 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 10:32:02 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 10:32:02 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 10:32:02 PM Z-Wave Device: Door Lock Mudroom Lock Set to 0
Aug-15 10:32:00 PM Device Control Device: Door Lock Mudroom Lock to Unlock (0) by/from: CAPI Control Handler
Aug-15 10:09:03 PM Z-Wave Device: Door Lock Foyer Battery Set to 96

Lock action sends an Unlock notification...

Aug-15 10:09:03 PM Z-Wave Device: Door Lock Foyer Battery Set to 96
Aug-15 8:40:46 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:46 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 20:40:46
Manual Unlock Operation (2) 2017-08-15 20:40:32
Manual Unlock Operation (2) 2017-08-15 20:40:03
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Family (6003) 2017-08-15 15:38:27
Aug-15 8:40:46 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:46 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 8:40:46 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 8:40:46 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 8:40:46 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:46 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 8:40:46 PM Door Lock Log DB Insert 1080-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-20:40:46
Aug-15 8:40:46 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:46 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:46 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:46 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 8:40:46 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 8:40:46 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 8:40:46 PM Z-Wave Device: Door Lock Mudroom Lock Set to 255
Aug-15 8:40:43 PM Device Control Device: Door Lock Mudroom Lock to Lock (255)
Aug-15 8:40:43 PM Device Control Device: Door Lock Foyer Lock to Lock (255)
Aug-15 8:40:32 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:32 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 20:40:32
Manual Unlock Operation (2) 2017-08-15 20:40:03
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Family (6003) 2017-08-15 15:38:27
Keypad Lock Operation (5) 2017-08-15 09:42:04
Aug-15 8:40:32 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:32 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 8:40:32 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 8:40:32 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 8:40:32 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:32 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 8:40:32 PM Door Lock Log DB Insert 1079-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-20:40:32
Aug-15 8:40:32 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:32 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:32 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:32 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 8:40:32 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 8:40:32 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 8:40:32 PM Z-Wave Device: Door Lock Mudroom Lock Set to 0
Aug-15 8:40:30 PM Device Control Device: Door Lock Mudroom Lock to Unlock (0)
Aug-15 8:40:03 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:03 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 20:40:03
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Family (6003) 2017-08-15 15:38:27
Keypad Lock Operation (5) 2017-08-15 09:42:04
Family (6003) 2017-08-15 09:41:22
Aug-15 8:40:03 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:03 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 8:40:03 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 8:40:03 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 8:40:03 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:03 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 8:40:03 PM Door Lock Log DB Insert 1078-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-20:40:03
Aug-15 8:40:03 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:40:03 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:03 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:40:03 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 8:40:03 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 8:40:03 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 8:40:03 PM Z-Wave Device: Door Lock Mudroom Lock Set to 255
Aug-15 8:40:00 PM Device Control Device: Door Lock Mudroom Lock to Lock (255)
Aug-15 8:40:00 PM Device Control Device: Door Lock Foyer Lock to Lock (255)
Aug-15 8:40:00 PM Device Control Device: Door Lock Mudroom Lock to Lock (255)
Aug-15 8:40:00 PM Device Control Device: Door Lock Foyer Lock to Lock (255)
Aug-15 8:39:39 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:39:39 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 20:39:39
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Family (6003) 2017-08-15 15:38:27
Keypad Lock Operation (5) 2017-08-15 09:42:04
Family (6003) 2017-08-15 09:41:22
Keypad Lock Operation (5) 2017-08-15 09:40:43
Aug-15 8:39:39 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:39:39 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 8:39:39 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 8:39:39 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 8:39:39 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:39:39 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 8:39:39 PM Door Lock Log DB Insert 1077-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-20:39:39
Aug-15 8:39:39 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:39:39 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:39:39 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:39:39 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 8:39:39 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 8:39:39 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 8:39:39 PM Z-Wave Device: Door Lock Mudroom Lock Set to 0
Aug-15 8:39:37 PM Device Control Device: Door Lock Mudroom Lock to Unlock (0)
Aug-15 8:30:03 PM Door Lock Log DB Cleanup C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:30:03 PM Door Lock Log DB Read
Event Date Time
Manual Unlock Operation (2) 2017-08-15 20:30:03
Manual Unlock Operation (2) 2017-08-15 19:16:03
Manual Lock Operation (1) 2017-08-15 19:12:05
Family (6003) 2017-08-15 16:01:33
Family (6003) 2017-08-15 15:44:53
Family (6003) 2017-08-15 15:38:27
Keypad Lock Operation (5) 2017-08-15 09:42:04
Family (6003) 2017-08-15 09:41:22
Keypad Lock Operation (5) 2017-08-15 09:40:43
Manual Lock Operation (1) 2017-08-15 08:45:05
Aug-15 8:30:03 PM Door Lock Log DB Read C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:30:03 PM Pushover 3P Pushover Notification Sent - Message Title Mudroom Door Lock
Aug-15 8:30:03 PM Door Lock Log Pushover Mudroom Door Lock Unlocked Manually
Aug-15 8:30:03 PM Door Lock Log Pushover Mudroom Door Lock
Aug-15 8:30:03 PM Door Lock Log ActionSendMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:30:03 PM Door Lock Log ActionAnnouncement Mudroom Door Lock Unlocked Manually
Aug-15 8:30:03 PM Door Lock Log DB Insert 1076-Mudroom Door Lock-Manual Unlock Operation (2)-2017-08-15-20:30:03
Aug-15 8:30:03 PM Door Lock Log DB Insert C:\Program Files (x86)\HomeSeer HS3\Data\Locks\locks.db
Aug-15 8:30:03 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:30:03 PM Door Lock Log ActionMessage Mudroom Door Lock Unlocked Manually
Aug-15 8:30:03 PM Door Lock Log Manual Unlock Operation (2)
Aug-15 8:30:03 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/doorlock.vb
Aug-15 8:30:03 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Aug-15 8:30:03 PM Z-Wave Device: Door Lock Mudroom Lock Set to 255
Aug-15 8:30:00 PM Device Control Device: Door Lock Mudroom Lock to Lock (255)
Aug-15 8:30:00 PM Device Control Device: Door Lock Foyer Lock to Lock (255)
Aug-15 8:30:00 PM Device Control Device: Door Lock Mudroom Lock to Lock (255)
Aug-15 8:30:00 PM Device Control Device: Door Lock Foyer Lock to Lock (255)

[cbabkirk]

New To Doorlock.vb Use.

Hello Sparkman,

Thanks for the excellent script. I recently bought a Schlage BE468NX Deadbolt lock from HS and went searching for plugins or scripts to support the lock beyond the native HS offerings. I had no problem installing the script and am assuming that the zip file in the thread is the latest version?

Do you expect that your script will provide all capabilities provided by the BE468NX lock? By that I mean, will it report all means of opening and closing the lock?

I created the virtual device for use by the door lock log. I have that set for 10 entries. I see a new entry logged whenever I operate the lock manually or via the keypad. When I open/close the lock using an event, using the LOCK/UNLOCK on the Door Lock child device, or when I use HS touch to operate the lock under the LOCKS icon, it does not create a log entry. It appears that any operation provided via zwave does not create a log entry.

I am using HS 3.0.0.307 & zwave 3.0.1.136

[Ltek]

Hello Sparkman,

Thanks for the excellent script. I recently bought a Schlage BE468NX Deadbolt lock from HS and went searching for plugins or scripts to support the lock beyond the native HS offerings. I had no problem installing the script and am assuming that the zip file in the thread is the latest version?

Do you expect that your script will provide all capabilities provided by the BE468NX lock? By that I mean, will it report all means of opening and closing the lock?

I created the virtual device for use by the door lock log. I have that set for 10 entries. I see a new entry logged whenever I operate the lock manually or via the keypad. When I open/close the lock using an event, using the LOCK/UNLOCK on the Door Lock child device, or when I use HS touch to operate the lock under the LOCKS icon, it does not create a log entry. It appears that any operation provided via zwave does not create a log entry.

I am using HS 3.0.0.307 & zwave 3.0.1.136

I have 2 of these locks (both Version: 3.42 (ZDK 4.54.1) Firmware: 88.21) and have had issues with this script working properly with it... see my posts in the past 2 or so pages of this thread.

I do see the script logging all lock/unlock activities BUT it logs them incorrectly. 2 different problems...

1. It logs ALL lock/unlock activities as "Manual"
2. For one lock it only ever logs 'lock', never unlock. and the Status Gfx screens are identical.

[cbabkirk]

Hello Ltek,

I get the operations logged in HS log but not in the Door Lock Log virtual child device. I will check to see if the operations are not logging correctly on the HS log.

[Ltek]

Hello Ltek,

I get the operations logged in HS log but not in the Door Lock Log virtual child device. I will check to see if the operations are not logging correctly on the HS log.

What did you find?

I have to stop using the script and set alerts manually - the script has show-stopper bugs for these locks. I'd rather spend the time setting up the events than trying to learn and debug the script.

I've kept debug logging on for a week and still found the same result...

script always records 'Mudroom Door Lock Locked Manually'
while the HS3 log correctly states the action:

Sep-05 8:52:41 PM Door Lock Log ActionMessage Mudroom Door Lock Locked Manually
Sep-05 8:52:41 PM Door Lock Log ActionMessage Mudroom Door Lock Locked Manually
Sep-05 8:52:41 PM Event Event Trigger "Door Lock Mudroom Door Lock - Script Trigger"
Sep-05 8:52:41 PM Z-Wave Device: Door Lock Mudroom Lock Set to 0
Sep-05 8:52:40 PM Device Control Device: Door Lock Mudroom Lock to Unlock (0)

and...
1. script only ever shows 'Manually' as teeh action. never RF, remote, etc
2. script never records what code is being used on the keypad so the proper alert can never be sent

[cbabkirk]

First thing I want to ask is did you create the virtual child device that will log entries directly on child new child device under "Status"? The title will be "Event". Mine looks like this..In setup or ini file I selected up to twelve entries. The date unfortunately gets chopped.

Event Date Time
Manual Unlock Operation (2) 2017-09-07 12:02:23
Manual Lock Operation (1) 2017-09-07 12:02:21
Manual Unlock Operation (2) 2017-09-07 12:02:07
Manual Lock Operation (1) 2017-09-07 12:02:05
Manual Unlock Operation (2) 2017-09-07 12:01:54
User Code 5 Keypad Lock Operation (5005) 2017-09-07 12:01:22
User Code 6 Keypad Lock Operation (5006) 2017-09-07 11:23:00
User Code 5 Keypad Unlock Operation (6005) 2017-09-07 11:21:17
User Code 4 Keypad Lock Operation (5004) 2017-09-07 11:21:06
User Code 3 Keypad Unlock Operation (6003) 2017-09-07 11:20:49
Schlage Button Pressed (5) 2017-09-07 11:19:43
User Code 4 Keypad Unlock Operation (6004)

At first I was having a problem getting log entries for anything except manual operations using knob or key. I found that when I pressed the Schlage button on the lock it would record "(5)". So I added a entry for "Status Text for device Access Control Notification" and called it "Schlage Button Pressed". For some reason once I added that. It started to record keypad operations(see above) indicating "User Code (X)". I have 3-6 codes assigned. So far in this inline log, I am getting "Lock" when it locks and "Unlock" when it unlocks.

My problem is I get no entries for any Zwave operations or even for using "off/on" on the Door Lock child device. I am not sure how big azn issue this is as if I use the On/Off on the child device or from HS Touch, I know the user is me.

I have not checked the HS log yet or turned on debugging logging so that will be next.

Yesterday I did tun on notification in the setup screen (aspx file) and I can see these new entries being populated in the doorlock.ini file. I am getting email notifications from these when it is a manual or keypad operation but do not believe I am getting anything from a zwave operation. I'll check that again.

[Ltek]

Are you using the RefID for the lock's child device named "Access Control Notification" -- adding into the 'NotificationDev' field in the Script? This is what I'm using... the documentation is not clear so it looked like thats what I should be using?

At first I was having a problem getting log entries for anything except manual operations using knob or key. I found that when I pressed the Schlage button on the lock it would record "(5)". So I added a entry for "Status Text for device Access Control Notification" and called it "Schlage Button Pressed". For some reason once I added that. It started to record keypad operations(see above) indicating "User Code (X)". I have 3-6 codes assigned. So far in this inline log, I am getting "Lock" when it locks and "Unlock" when it unlocks.

My 5 under Status-Value is... "Keypad Lock Operation"

My problem is I get no entries for any Zwave operations or even for using "off/on" on the Door Lock child device. I am not sure how big azn issue this is as if I use the On/Off on the child device or from HS Touch, I know the user is me.

Same with me.

You can see my Log Device screenshot...

[jms72499]

New to HS and just getting this setup. I have Schlage BE 468 locks. How does this handle battery events when that is registered on a separate device?

[Tyborg]

This is the discussion thread for the Z-Wave lock events script located here:

http://board.homeseer.com/showpost.p...47&postcount=1

Cheers
Al

Thanks for making my transition to Homeseer a little bit smoother. Got this script working today and will be adding a couple more locks to it this evening. Seems to be working a treat on my Yale locks.

[_ThaNerd_]

I'm a newbie and can't freakin get this going. Got the event setup, got the files to their locations but I can't see the aspx file configuration (am I suppose to open it by clicking on it? what app should I use to view it?).

Also my log is as follows:

[cfrudolphy]

Settings.ini file must get overwritten.

I am having same issue as _ThaNerd_ regarding his log. See the following:

Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteDataReader' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteCommand' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteDataReader' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteCommand' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteCommand' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteCommand' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLite.SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteCommand' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Type 'SQLiteConnection' is not defined.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Namespace or type specified in the Imports 'System.Data.SQLite' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.
Nov-25 5:11:52 PM Error Compiling script C:\Program Files (x86)\HomeSeer HS3\scripts\doorlock.vb: Namespace or type specified in the Imports 'System.Core' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.

My original settings.ini file did not have the "Scripting Reference" in it. I copied and pasted into file saved and re-started Homeseer with BLShutdown. I tested script and this error. I looked at settings.ini again and it didn't have the "Scripting Reference" in it. I copied, pasted, and saved. Then I copied settings.ini over settings.ini.bak. I checked both files and the reference was there. I restarted Homeseer again with BLShutdown, tested the script and the same error. I looked at settings.ini and settings.ini.bak and the "Scripting Reference" is missing.

Something is writing over these files on startup. Any ideas? Would appreciate some help.

Thanks in advance

Chuck

Current Date/Time: 11/25/2017 5:24:03 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.368
Operating System: Microsoft Windows 7 Home Premium - Work Station
System Uptime: 0 Days 0 Hours 14 Minutes 43 Seconds
IP Address: 192.168.0.5
Number of Devices: 142
Number of Events: 23
Available Threads: 400

Enabled Plug-Ins
2.0.74.0: BLLock
1.0.3.0: BLShutdown
3.0.1.109: PHLocation
3.0.6440.19101: UltraMon3
3.0.6496.15709: UltraTivo3
3.0.1.130: Z-Wave

[cfrudolphy]

Settings.ini file must get overwritten. - SOLVED -

Got the "Scripting References" to stick in the settings.ini file by shutting down Homeseer, editing and saving the file, and then restarting Homeseer.

I suspect Homeseer re-writes the setting.ini file on shutdown. If you edit before shutting down your changes get overwritten during the shutdown process.

When you edit prior to start up then it loads the edited file so the next time Homeseer shuts down it re-writes the file with your edits.

I think it does this because some of the settings are user changeable in the web admin pages, i.e. binding the http server to a specific ip address and port. If it didn't rewrite the file with its current settings you would have to change such things every time after start up.

Chuck

[bsobel]

Pushover broken

The Pushover Plugin changed the API (ARGH, who does that?) so now an additional path parameter (or a nothing) is required for the call to the plugin to work. I noticed this as this script stopped sending pushover notifications. FYI the new changed API version is live in the updater.

[tyke]

Just started playing with your script, is there a fix for Pushover?

[tyke]

I figured it out based on your comments in the Pushover 3p thread.

opened up doorlock.vb and went to "sub pushover"

Changed this line
Dim CO(7) As Object
to
Dim CO(8) As Object

then added a
CO(8) = Nothing

After
CO(7) = Nothing