I tried searching this but it gets so many extraneous hits that I gave up and started a new topic so forgive me if this is a rehash.

I've got a page in my ud mobile app where I can arm/disarm my Elk system. I've never cared about that because I've always run it solely on my phone so authentication is pretty much a given. But now I've set up an android tablet as a home controller. It's mounted on the wall in my kitchen and obviously it's not a good idea for the disarm function to be just plain accessible to anyone.

Is there a straightforward way to require a password to get to the security system disarm folder?

On another note... would it be possible to get an 'armed stay' and 'armed away' icon added to the built in icons?

Thanks in advance

19 minutes ago, MarkJames said:

On another note... would it be possible to get an 'armed stay' and 'armed away' icon added to the built in icons?

For that, I'd either create an icon that runs a program, or create a switch with the Virtual plugin, which then runs a program that then sends the desired commands to the alarm system.

2 hours ago, Guy Lavoie said:

For that, I'd either create an icon that runs a program, or create a switch with the Virtual plugin, which then runs a program that then sends the desired commands to the alarm system.

That doesn't really address my issue. I want to require a user to enter a password before they can run a program within UD mobile. For example let's say I have a program called 'disarm house'. I create a command type icon within UD mobile that has as it's command 'run disarm house <then>'.

That's a great idea when the only one with access to the tablet is me. But I can't very well leave it like that where if someone breaks into the house they could just walk up to the tablet and disarm the alarm.

So what I need to do is if a person wants to access the disarm house icon they are required to enter a pin or password first.

I can think of a way of doing it by creating a keypad of numbers that execute programs building a pin within ISY step by step until the pin is confirmed or a wrong number is entered but it's a clunky way of doing it,

Is there a more graceful way?

Yes, that clunkly way is the workaround that comes to mind.

I just added a feature suggestion:

https://forum.universal-devices.com/topic/46913-suggested-ud-mobile-feature-numeric-keypad/

4 hours ago, Guy Lavoie said:

I just added a feature suggestion:

https://forum.universal-devices.com/topic/46913-suggested-ud-mobile-feature-numeric-keypad/

Thank you!

I used to use HSTouch with HomeSeer many moons ago. A numeric keypad password page was a built in function in that ecosystem. Very handy.\

If you're up to adding yet another suggestion it would be great to have a palette that you could define so that you didn't have to write down the hex codes for the colors you use and enter them all the time

Edited 11 hours ago11 hr by MarkJames

While having a tablet unlocked would allow a user eventual access, you could make it difficult.

Create your keypad.

Map numbers to variables/programs. E.g have a var for key entered and a var for keys entered (requires some math). Then a program to do math and update keys entered var. Another program which does alarm functions when keys matches.

Hide the alarm nodes, keypad programs and keypad vars in UDM.

That's along the lines of what I was describing earlier. Map each of those buttons to a program which dynamically builds the PIN. So the keypress would add a number according to its keypress value which would be added to the dynamically built pin multiplying its previous value by 10 each time before adding the new keypress. At whatever length is needed for the PIN it would either kick you out with an error message or run the program.

This would work for running programs, setting device status, etc but it would not work (AFAIK) to allow you through to an entire page of password protected features. eg - my house has six Elk areas - All the arm/disarm programs are on one page so it would be great to just password protect that page (folder) in UDM. The same can be said for having multiple Schlage/Yale/etc locks on one page that could be locked/unlocked from one place or any other sensitive data.

I agree that the implementation you describe is do-able and not particularly complicated but it seems like something that is so totally reuse-able and practical for such a wide variety of purposes that it makes sense for it to be a built-in function. It's just 2 more properties for a folder. Whether it's password protected and if so what the password is. When a user hits the button for a folder it could check if the folder is password protected and if so pop a dialog asking for the password.

Edited 46 minutes ago46 min by MarkJames