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”}
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
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
@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.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
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:
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?
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
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
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
52
Folks using the ZigBee device handler should update to the latest 1.3a Universal ZigBee device handler. This is to fix an issue with the lock reporting user 255 when using manual or remote locking/unlocking. Thanks for the quick turnaround @jhamstead
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
53
##user Unlock/Lock Door Notifications and Actions - Version 03.04.00
Added support for selective use notifications only when users are not present
Added ability to chime/ring a bell when the door is opened (with option to select modes)
Improve quality of notifications and simplified user interface
I just purchased and installed 5.04, do I need to reset the lock prior to going to this version or can I just upgrade and re-publish?
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
55
If you’ve already got an older version of the SmartApp then just upgrade and republish.
If you’re installing it fresh for the first time, it would be better to clear all the codes from the lock/reset once before starting to use this SmartApp.
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
56
##user Unlock/Lock Door Notifications and Actions - Version 03.04.01
Added support to report Master Code usage for supporting locks (e.g. Yale, IDLock etc)