It’s not the code, like I mentioned earlier it’s a platform/hub issue. If you open live logging you’ll see that it’s sending the commands to the lock (if the platform timer is working fine). After that it’s up to the hub/platform.
1 Like
For locking / unlocking procedures why don’t you use a simpler code like:
locks?.each
{
it?.lock()
log.info ("${locks} locked")
}
Also, could you please confirm that the “AUTOLOCK” option from your custom device if OFF does not interfere with “Relock after (minutes)” in your smartapp?
Thank you
Because of the infamous z-wave network. It needs time to complete each command before sending another one, when there are multiple locks the commands gets lost.
Yes, infact we’re putting a check the next version NOT to allow for Auto unlock if Auto Lock is enabled in the DH.
1 Like
I don’t see these command lines failing:
locks?.each
{
it?.lock()
log.info ("${locks} locked")
}
It will list all the devices and send individual requests to each device rather than sending one request to all the devices.
Did you try?
Also, as today, if I have “AUTOLOCK OFF” on my DH, can your smartapp lock the lock X minutes after closing the door and if the lock is unlocked and the door is closed?
Thanks!
Yes it does when you have multiple locks. We’re tried a lot of combinations here in the lab and what you’ve written doesn’t work 90% of the time with multiple locks and repeaters across a large space. Don’t under estimate the issues with a Z-Wave network and the ST hub when you’re trying send lots of commands in a short span.
Yes it can and again it’s subject to the same Z-Wave network and platform rules as unlock.
###Multi User Lock Code Management with Notifications and Actions - Version 4.6.3
- Improved reliability of auto unlock and auto relock
- Bugfix for notifying user if codes are being reused for multiple users
- Now the App checks if the device lock has the AutoLock feature enabled and if so it will not Unlock the door when open to avoid an infinite lock/unlock loop
- Clear all codes from the lock before programming when installing for the first time to avoid conflicts
Recommend the use of the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock, Schlage Lock, Yale Lock, Kwikset Lock, IDLock, DanaLock, August Pro and Samsung Lock Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features) device handler version 2.10.1 or later for full SmartApp functionality
Thanks to DnCCrew for this step:
To set the hub Location, from smartphone app:
- Clicked on the 3 lines (top right corner)
- Clicked on gear icon (top right)
- Click area that says “Tap to set where home is on the map” and zoom in to correct location on map.
EDIT: Please note this version has simplified the user interface, so please CHECK and VERIFY your notification settings. These are now on the first page under door lock/unlock actions.
Since updating to this new Smartapp I am no longer receiving notifications (push) on unlock for my different users.
Yes that’s correct, now the notifications have been enhanced to allow configuration per door if using multiple doors so you would need to verify your settings and reconfirm them. Please see the release notes, quoting:
Please note this version has simplified the user interface, so please CHECK and VERIFY your notification settings. These are now on the first page under door lock/unlock actions.
I seem to be having an issue with the one time codes. I will set a one time code and 20 minutes after its first used it still is working. Any idea on what I may be doing wrong? I have the latest app and device handler
Couple of things to check:
- Your hub is on the same time as you. You can verify this by looking at the IDE Live logs, it will publish the hub time.
- Verify the date/time (typos etc)
- If the above two are done correctly then the ST scheduler is broken in your setup. ST has been facing problems with the scheduler not firing. See your logs and you should see the scheduler run every 5 minutes for housekeeping. If you don’t see it then it’s broken and you’ll need to report it to ST support.
- If you do see it running, see what the housekeeping logs say about that one time code (it will indicate the status, expired, etc etc).
Scratch the above, sorry, I read expired code instead of one time code.
Just open Live Logging in the IDE, it should do housekeeping every 5 minutes and just check what is says about the status of the one time code. It should mark it expired as soon as it is used.
It will be deleted the next time housekeeping runs which is every 5 minutes, so if housekeeping isn’t running then you should contact ST support since the scheduler on your account is broken. We’ve tried to build in a backup for the scheduler which kicks in every 20 minutes to kickstart the housekeeping task but again if the main scheduler is broken it may not help.
EDIT: So I was able to replicate your issue once and the root cause was the ST scheduler had failed, so the housekeeping wasn’t done. This problems with ST scheduler has been happening of late. As soon the scheduler kicked on it removed the code. Please report to ST support that you’re facing scheduler timers dying. They will investigate it further. @slagle just a FYI
Ok. Thank you for your help. I checked the live logging and it is working correctly showing that the code is deleted as soon as it is used. It seems to be working now though. Not sure if I was just having a glitch or not. But thank you again. Great app btw!!!
Ok maybe I’m wrong. When I have live logging open then it deletes it immediately after the one time code is used. If I do not have live logging open then the code still works after the one time use. Not sure if it’s a problem with the hub or if I need to have the logging open all the time.
It’s an issue with your instance of the platform, it doesn’t appear to be calling the scheduled functions which actually delete the code when you Live Logging is closed. Now I’m not saying that opening/closing Live Logging is the issue, it’s just a coincidence that when live logging it open the platform scheduler works fine and when it’s closed it’s having trouble with your instance. The scheduler problem has been known to ST engineers and they appear to be “working” on it. Please report the issue to them so they can look into your account and hopefully fix your scheduler issues.
@RBoy ever since I upgraded to 4.6.3 I am having an issue with actions based on lock/unlock. I used to have the lock turn on a light when the lock was unlocked. That option does not seem to exist any longer. When I go into the menu option labeled “Click Here To Define Actions When The User Lock/Unlocks The Door Successfully” all I see on that menu is this (see screenshot).
It’s an issue with your phone connection to the ST servers. Looks like they are running slow and probably timing out while rendering. You should report it to ST support.
Here is what I’m seeing (after a loading delay):
jesus man, ST Cloud is awful. The easiest fix is to deliver what they promised - local IDE. instead we get this half ass stuff with smart lighting. There is a huge market opportunity for someone to come up with a simply hub thats ST like with local IDE and they would win hearts and minds of everyone here.
Animus on Kickstarter. Runs groovy
1 Like
Sucks that animus will not be supporting zigbee, but seems to be really cool.
@RBoy I left that page open waiting for it to load and it never did. I deleted and re-added the smart app and it still doesn’t show up. Is there anything else I can do? I need it to disable my alarm and turn on that light, but without getting to that config screen not sure hoot do it. It worked great prior to upgrading to 4.6.3 so this is definitely an issue after I upgraded.