[RELEASE] User Unlock/Lock Door Notifications and Actions

user
notify
smartapp_alerts
smartapp_locks
smartapp_security

(www.rboyapps.com - Make your home your butler!) #32

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.


#33

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]


(www.rboyapps.com - Make your home your butler!) #34

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.


#35

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


(www.rboyapps.com - Make your home your butler!) #36

PM me your complete logs please.

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


(www.rboyapps.com - Make your home your butler!) #37

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 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 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) #38

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.


(www.rboyapps.com - Make your home your butler!) #39

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) #40

Thx for quick answer. :slight_smile:

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"}


(www.rboyapps.com - Make your home your butler!) #41

If there is an error it will show up in red. Otherwise the platform is timing out. If it doesn't start working by tomorrow I would report it to Dev avocate Tim or Aaron to see why your instance is timing out


(EinarS) #42

@slagle and or @Aaron could you have a look at this?
Like stated in the four last post.
It seems I get no execution from this smart app when i unlock my door lock.
It have worked 3 times in total, but for most times it does not work.
I have a core piston sending med an sms bound to events from the lock, and this works.
@rboy suspects its a timeout in the plattform, but there is no mentions of problems on the status.smartthings.com
Could you have a look into this?
This is my last step in automating locks and alarms. :slight_smile:


(www.rboyapps.com - Make your home your butler!) #43

So to confirm, we're also seeing the same issue here starting this afternoon. The routines being executed from the SmartApp are timing out @slagle @Aaron and the routines don't finish their configured actions

@einars since this is a "common" issue with ST from time to time, we've written a SmartApp that essentially acts like a backup routines. Thus is a routine fails this SmartApp kicks in and finishes up for it. So far I've found it 100% reliable, check it out:


(EinarS) #44

This one seemes to work @RBoy
Think it could be "weight" of whats beeing executed? Would love to use your app as one stop solution.


(www.rboyapps.com - Make your home your butler!) #45

User Unlock/Lock Door Notifications and Actions - Version 3.2.1

  • For multiple SMS/Text notifications now separate the numbers with a ; (the + can be used to send messages to international numbers)
  • Improved reliability to check for smart app and device handler updates and notify the user

Recommend use the Universal Enhanced Z-Wave Lock 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 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

Don't forget step 3 or the update notifications will not work


#46

You're website is down. And I just paid you the $35 lifetime subscription too!


(www.rboyapps.com - Make your home your butler!) #47

Yes we are having an ISP issue. Sorry for the inconvenience. It will be
back up in a few hours.


(www.rboyapps.com - Make your home your butler!) #48

The website is back up now. Thanks for your patience.


#49

Thanks. The "I just paid you $35!!!!" bit was supposed to mostly be a joke. Glad you're back up.


(EinarS) #50

Feature request.
Is it possible for you to to implement user notification when updated versions is available on your DH´s and SA´s?
Like SMS to me, og Push to me and not the whole family?


(www.rboyapps.com - Make your home your butler!) #51

User Unlock/Lock Door Notifications and Actions - Version 03.03.00

  • Added support for reporting unknown users and running actions for master codes/users
  • Added ability to NOT run door lock/unlock action when specified users are present or when in certain modes
  • Reduce notifications verbosity for lock/unlock actions, enable detailed notifications to restore verbosity

Recommend use the Universal Enhanced Z-Wave Lock device handler version 3.2.0 or newer for full SmartApp and automatic update notification functionality