[RELEASE] Lock User Unlock/Lock Door Notifications and Actions

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.2

• Fixed a bug which caused disable all push notifications to also disable text notifications

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung - #383 by RBoy) device handler version 3.0.1 or later for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.3

• Added the ability to select operating modes for auto relock

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung - #383 by RBoy) device handler version 3.0.1 or later for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.4

• Added functionality to check for configured auto re-locks and open door notifications on mode changes

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.5

• Minor bug fix, when controlling multiple doors and one or more doors doesn’t have an assigned sensor, when the mode changes the door may not relock itself if configured to do so

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.6

• Workaround for bug in ST app v2.2.0 causing unlock based actions page to break for iOS/Android users

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.7

• Patch for actions page not showing up if there are no routines on the hub

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.8

• Fix for unable to change notify option
• Improved layout and explanations

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.1.9

• Patch for ST’s “ghost” routines causing some users to get an error while trying to configure actions

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.0.1 or newer for full SmartApp functionality

[cscheiene]

Cant get notification to work, this is from the logs:

45fbc4a5-0f1c-4bfd-bd7f-fa66b830e00f 15.09.44 CEST: error java.lang.NullPointerException: Cannot get property ‘eaf3c861-343a-44e3-81a6-8e94cafd2442’ on null object @ line 714
45fbc4a5-0f1c-4bfd-bd7f-fa66b830e00f 15.09.44 CEST: info Running unlock Phrase I’m Back!
45fbc4a5-0f1c-4bfd-bd7f-fa66b830e00f 15.09.44 CEST: debug Found per user unlock actions
45fbc4a5-0f1c-4bfd-bd7f-fa66b830e00f 15.09.44 CEST: debug Lock Dør Hovedinngang Lås unlocked by Hovedbruker, notify true, notify modes null, via keypad
45fbc4a5-0f1c-4bfd-bd7f-fa66b830e00f 15.09.44 CEST: trace Event name lock, value unlocked, device Dør Hovedinngang Lås

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Your state variable is corrupted. Delete your app and start over. @slagle FYI

[cscheiene]

Did not help. I have started using my contacts, could that have anything to do with it? Notifications seems to work with other apps

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Could be, contacts is still not officially released by ST and is buggy, if you contact ST support they will ask you to disable the feature.

[cscheiene]

ST has removed the my contacts function for me. I have deleted the app, and deleted the code from IDE.
Started all over with new code and new install. But I’m stilling not getting notification.

This is in the logs:

6eece88b-1c8c-44c0-86da-4efb985ae460 12.12.45 CEST: error java.lang.NullPointerException: Cannot get property ‘eaf3c861-343a-44e3-81a6-8e94cafd2442’ on null object @ line 714
6eece88b-1c8c-44c0-86da-4efb985ae460 12.12.45 CEST: debug Lock Dør Hovedinngang Lås unlocked by Hovedbruker, notify true, notify modes null, via keypad
6eece88b-1c8c-44c0-86da-4efb985ae460 12.12.45 CEST: trace Event name lock, value unlocked, device Dør Hovedinngang Lås
6eece88b-1c8c-44c0-86da-4efb985ae460 12.12.45 CEST: debug Lock event name lock, value unlocked, device Dør Hovedinngang Lås, description Dør Hovedinngang Lås was unlocked with code 1, data {“usedCode”:1,“type”:“keypad”}

And when updating settings:

6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.53 CEST: trace Found attribute ‘invalidCode’ on lock Dør Hovedinngang Lås, enabled support for invalid code detection
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.53 CEST: debug Update Settings: [userNotify1:true, userNotify4:true, userNotify3:true, userNames3:Gerd/Jan, userNames1:Hovedbruker, userNames2:Gjest, disableAllNotify:false, locks:[Dør Hovedinngang Lås], maxUserNames:4, userNotify2:true, userNames4:Karianne/Tor Jan]
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.50 CEST: debug Initial 4 Name: Karianne/Tor Jan, Notify: true, NotifyModes: null
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.50 CEST: debug Initial 3 Name: Gerd/Jan, Notify: true, NotifyModes: null
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.50 CEST: debug Initial 2 Name: Gjest, Notify: true, NotifyModes: null
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.50 CEST: debug Initial 1 Name: Hovedbruker, Notify: true, NotifyModes: null
6eece88b-1c8c-44c0-86da-4efb985ae460 12.26.31 CEST: trace [userNotify1:true, userNotify4:true, userNotify3:true, userNames3:Gerd/Jan, userNames1:Hovedbruker, userNames2:Gjest, disableAllNotify:false, locks:[Dør Hovedinngang Lås], maxUserNames:4, userNotify2:true, userNames4:Karianne/Tor Jan]

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Ah I think I know what may be happening. Try this please. Delete the smartapp. I see your lock is using some non English characters in its name. Please change to to only English characters and then try it out. I suspect that will fix the issue.

[cscheiene]

Thanks for the support, but it did not help. Changed the name, uninstalled and reinstalled but still the same. Very strange, don’t seem to have any issue with other notifications

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

PM me your complete logs please.

EDIT: Found the issue, will push a patch in the next update along with some cool stuff coming.

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

##user Unlock/Lock Door Notifications and Actions - Version 3.2.0

• Fixed an issue with notification not working for some users
• Added ability to check for smart app and device handler updates and notify the user

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 3.1.1 or newer for full SmartApp and automatic update notification functionality

After installing this code update, please (in this order):
1. Update the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler to version 3.1.1 (required for automatic update notifications)
2. Open the lock device page on the ST phone app and click on Refresh
3. Open the SmartApp and click Next and then Done for the changes to take effect

[einars]

Hello.
I installed this smart app two days ago, together with the device handler for id-lock.
Did a test to disarm lock when the lock was unlocked.
Worked like a charm two days ago.
Got back home today, and it is not disarming the alarm.
Made a core piston that sends me an sms if unlocked to check if it works.
And i get SMS about door being unlocked.
Tested disarming alarm with a z-wave button to rule out faults in hub, this works fine, and alarm disarms.
Settings set i app, you find in the picture.

PS brand new lock, so its a clean install, both device handler and smart app.

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

If was working a few days ago but not now then it’s likely the platform timing out. You can verify by looking at the live logging and seeing the commands are being executed or if your are seeing any errors. It should start working once the platform resumes normal operation

[einars]

Thx for quick answer.

Added turn on a light as well as disarm to have a couple off commands running.
The Core pistons sends SMS, but the smart app does not do anything.
Cant say I find the command or error in the log? PS i just tested once before i left the house for a couple of days.

ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.11: debug IDLock 101 Z-Wave/RFID Lock was locked with description: IDLock 101 Z-Wave/RFID Lock was manually locked
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.11: debug Lock event name lock, value locked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock was manually locked, data {“type”:“manual”}
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.02: debug Found per user unlock actions
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.02: debug Lock IDLock 101 Z-Wave/RFID Lock unlocked by Test, notify false, notify modes null, via keypad
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.02: trace Event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.50.02: debug Lock event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock was unlocked with code 1, data {“usedCode”:1,“type”:“keypad”}
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.51: debug IDLock 101 Z-Wave/RFID Lock was locked with description: IDLock 101 Z-Wave/RFID Lock was manually locked
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.51: debug Lock event name lock, value locked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock was manually locked, data {“type”:“manual”}
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.40: debug IDLock 101 Z-Wave/RFID Lock was unlocked manual
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.40: trace Event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.40: debug Lock event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock was manually unlocked, data {“type”:“manual”}
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.33: debug IDLock 101 Z-Wave/RFID Lock was locked with description: IDLock 101 Z-Wave/RFID Lock was manually locked
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.33: debug Lock event name lock, value locked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock was manually locked, data {“type”:“manual”}
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.26: debug IDLock 101 Z-Wave/RFID Lock was unlocked remote
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.26: trace Event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock
ba4abf36-b6da-4332-8923-5a1afc0bebbf 16.49.26: debug Lock event name lock, value unlocked, device IDLock 101 Z-Wave/RFID Lock, description IDLock 101 Z-Wave/RFID Lock lock is unlocked, data {“type”:“remote”}