The Ecobee thermostat appears to have custom modes which isn’t part of the most thermostat standards (auto/cool/heat etc).
I would recommend setting up a simple CoRE rule that runs an action when it detects a lock or unlock event (with the Universal Enhanced Z-Wave lock device handler you can also identify the source, keypad etc) and then send a custom command to the thermostat to change it’s mode.
Door Lock Code Multi User Management with Notifications and Actions - Version 05.10.00
Added support for arming Smart Home Monitor (SHM) as part of the Lock actions
Added support for Delay Actions, when locked via the Keypad, you can now have the system wait before running actions (allows for folks to exit the house before arming the security system or turning off lights, etc)
Lock User Management is the most reliable and comprehensive commercial grade User Management SmartApp with many (unique) features:
Unlimited users and locks
Works with the built in SmartThings device handler
Easy and intuitive setup
Sure-Programming engine: verifies that programming was successful
Support for different types of locks (keypad, bluetooth, RFID, etc)
Define custom individual Unlock AND Lock actions for users such as:
Exit delay actions (wait for X minutes before running actions)
Turning on lights if it’s dark outside
Turning on/off switches
Define rules when to run and not run actions
Notifications on type of lock/unlock (manual, code, keypad, bluetooth, rfid etc)
Define Door Open/Close actions such as
Automatically relocking the door when it’s closed
Automatically unlocking the deadbolt if it’s extended, while door is open
Ringing chimes when door is opened
Notifications if door is left open
Define actions for each door separately
Multiple types of users such as permanent, one time, expiration (start and end date/time), scheduled (daily/weekly etc) with multiple schedules per user, presence based, mode based and many more
Lots of built in safety mechanisms to ensure users have a reliable experience
This app just chugs along and I don’t need to get involved. A credit to it’s quality.
That is until I need to update it. I decided to update the custom device handler (3.5.1) and the latest Smartapp (5.10). I followed the directions but when opening the Smartapp on my phone and then saving I get the error “Error saving page”. No details so I don’t know how to fix. This has happened to me before but it somehow fixed it self.
I do see this in the log in the IDE:
java.lang.IllegalArgumentException: Command ‘setCode’ is not supported by device ac7bb006-70f5-4d0c-b1b6-697ebf26d9ca of type ‘Door lock code user management with notifications and automatic relock’. Supported commands:
Edit - FWIW, my two locks have also disappeared from my ST app, they still exist in the IDE.
(www.rboyapps.com - Making SmartThings Easy!)
What this message is saying is that your locks either don’t exist or they are using the wrong device handlers. Check your lock setup, it isn’t using either the stock st zwave lock device handler or the universal zwave lock device handler.
Speaking of versions and updating of Device Handlers and SmartApps. Obviously the way it’s done now and being able to keep the code as locked up as possible and only available to those that have paid their subscription/donation is fine, but have you ever thought about doing something where all of this could be made available via GitHub and your SmartApps require some sort of authentication code when they are installed in SmartThings that has to be entered and maybe associated to a code stored in each person’s account on RBoy apps? This would definitely make life so much easier to be able to update via the repository and also would address the question I replied to earlier. Just a thought in moving forward.
A second question. Does your website allow for us to change our password on our own? If so, I couldn’t find it. I have the original user/pwd that was given to me and from a security standpoint, I would think everyone would be able to change their passwords. Maybe I just missed it navigating through the site.
@RBoy I installed tonight with a Schlage Connect. Also using the Enhanced Z-Wave DH, however, on the device detail screen, I just see a bunch of blank tiles, with the exception of “Lock”, “Unlock” and “Battery”. Is this correct? Device has the proper type and MSR is also populated. What am I missing here?
I’ve just installed a door sensor to allow safe auto-locking of my Schlage BE469, and set a 1 min delay to the auto-lock.
All appears to be working fine EXCEPT the one button activation of the deadlock (the Schlage button) no longer works. Also, when the door is manually locked from the inside, the auto-lock still activates after the 1 min !
I’m using the latest ST app and DH.
Anyone else having this issue or have I just set it up wrong ?