RBoy
(www.rboyapps.com - Making SmartThings Easy!)
December 3, 2015, 7:12pm
246
@SetGoose
This thread is related to the door user management app, please post comments related to the Schlage lock smartdevice here:
A “future proof” Universal Enhanced Z-Wave Lock driver
This driver is enhanced to fix bugs in the stock ST ZWave Lock driver, include patches for bugs in lock firmwares and bring out additional features for Schalge, Yale, Kwikset, IDLock, Popp, Samsung, Delaney, August Pro, Danalock, KeyWe, Philia, Vivint, Locstar etc zwave locks (see below for a full list of models and features). This works with all ZWave locks and newer ZWave Plus locks (see below for a list of locks tested).
It discovers/learns the lock features and automatically configures them. If a feature is not supported by the lock it will not show up or say Unsupported.
You need SmartThings Smart Lock Guest Access (SLGA), Advanced Web UI or a SmartApp like Lock User Management (LUM) , Rental Lock Automater (RLA) to program user …
As for the door mgmt app quitting after a day or so as I had explained it’s related to the ST platform timers dying. While there’s a temporary patch I’ve put in the latest code that reboots the timers each time the mode changes please report the issue here to the ST devs so they can monitor/fix the issue:
I have a SmartApp that brightens lights in a zone when there is motion or a door opens. It dims the lights after a given timeout period.
I have 6 instances of the app on one hub, (6 different lighting zones), and 8 on another hub, in another building.
When the app initializes, it starts the scheduler to run a scheduleCheck() function every minute, to turn off lights, when appropriate.
It was working for months. Then it stopped dimming reliably.
I have determined that the scheduleCheck() function stops running as scheduled.
I have also noticed that it now usually schedules at the top of the minute, i.e., the seconds are zero. This did not used to be the case. And the time between scheduled calls can be 1, 2, or 3 minutes.
I have just installed a workaround, in which I re-initializ…