Author
Topic: Pincode before executing device/event (Read 1880 times)

It would be great to have the option to ask for a pincode before a scene/device executes. Especially useful when used in Dashboard mode; e.g. cleaning lady comes in and executes 'Cleaning lady entering' and before executing scene Imperihome asks for pincode. Pincode preferably changeable per device/scene.

Alternatively: have a pin code widget which can be assigned to a scene/device based on a pincode (so if 1234 is entered it will execute scene X and when pincode 4321 is entered it will execute scene Y)

We have pincode features in our backlog, but still thinking about how to implement them.

Seems like being able to set pincode on device/scene would be the most flexible way of doing it, but not very secured after all : someone could get out of the app, install/launch another Vera control app and execute the action withou pincode (or simply do it with browser and UI5).

For me the pincode feature is not so much a security feature but more for identification. So it's not to replace a commercial alarm system.

Personally I would love to see it as a widget on the panel view; similar to how you have got a clock , webpage, http request etc but then show a 10 digit control panel. Then you should be able to link different scenes/actions/devices to specific pins;

example: Homepage: Pincode widget>cleaning lady comes in>types her personal pincode>scenes get activated (eg heating on for 3 hours, motion sensors of for three hours, auto away after three hours)

Funny enough you can do this (NFC) in the list view but not in the dashboard view. Furthermore, if you have added this in list view but use it in dashboard view, swiping the tag will cause imperihome to switch back to the list view..

Now with the API live there is -in theory- a way around this; NFC tag fires a scene and imperihome switches to list view; you can now include the Imperihome plugin in the scene which in turn fires the dashboard to go to page X. Have not tested this but could work.

UPDATE: now tested above (using tag and use plugin to go back to page x) and this indeed works.