Ok, I see where this is getting us there: “device.deviceTypeName Prompts for all devices of the specified type.”
But how do you explicitly know what “deviceTypeName” is? I’m questioning the thoroughness of the documentation in this specific area (not you, and not in general BTW, it’s pretty good documentation compared to what I have worked with at times).
I suggest you guys take the capabilities discussion to the developers category on writing device types. Lots of people there have experience with these issues and may be able to help you further and at this level it’s getting kind of off topic for this thread.
yea, input of deviceTypeName used to work, about three or four weeks ago, it doesn’t now, on android at least.
Just another platform update bonus “feature”…
I’m feeling like anything to do with custom device(s) types, and specifically child devices is pretty much fubard at the moment.
there’s so many things in my environment that worked just fine 2-3 weeks ago, and don’t work now that I seriously can’t keep track of them, and none of them show any indication of error other than not working or crashing the app…
I just finished messing around with the new code. It’s working flawlessly! I’ve created a modified version of @ethayer’s User Lock Manager which adds keypad support and an Arm delay (in seconds). As of right now there is no way to add a disarm delay…
That lock manager code is beautiful. I’d like to contribute to that at some point as you have, I wonder if @ethayer is taking enhancements?
Keypad may need to take multiple keypads. Not too hard.
Routine may need to take other routines, or restrictions. I’m not sure how to handle this, but the number of modes I have make it hard to just use a couple of routines to arm/disarm. Have to think on this generically.
Keypad may need some null safe operators put in there for users that don’t use keypads.
Thanks to everyone… specifically Brian and our OP… this is now working for me.
Having this working device type and smart app we can really have some awesome functionality.
I love where we are going with the Lock Code Manager. I use a lock code manager for my smart locks in fact, so it makes sense here.
Some quick ideas:
Ability to toggle a function that disables any sirens / alerts from triggered alarms via the disarm code or secondary code. This gives non-privileged users or children the ability to execute specific commands without having the app or other access - authenticated by something they know.
Ability to choose a routine to execute when you ‘Arm’ or ‘Disarm’ - giving us options to tie to these buttons in addition to arming away/arming stay/disarm. Example - when I leave I normally execute a routine which does many things including arm the system.
Lock code management - already in the works.
EDIT: Okay setup the Lock Code Management app on my second keypad and it’s provide much of this functionality already. This is superb.
I just added Code Usage Count (increments the existing count for door unlocks) and added notifications. I also allowed you to select multiple keypads but I’m not sure if it will work properly or not. I’m not at home to test it out so let me know if you have any issues.
It will use all of the codes that are currently enabled in the User Lock Manager SmartApp. If you want to have it only for specific codes then I would create a separate instance of the SmartApp only for those codes.