You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Not related to a problem, just that at the moment we can only specify one unique pin code per card
Describe the solution you'd like
Change the code section to make it a list of strings instead of just a string
Describe alternatives you've considered
N.A.
Additional context
When multiple users are using the wall tablet, it's nice that that everyone can have his own PIN code (ie. to disable the alarm system).
Thank you very much for considering the feature request :-)
The text was updated successfully, but these errors were encountered:
A workaround is to create conditional entities based on the logged user.
Let's say you have three users. Create a card with three alarm entities (the same one three times). Then, using the YAML code editor, conditionally show only the one for the logged user. Do that for all three. Done that, I think you can just assign a pin to each one and done.
As a "bonus" you'll see that just the right pin for the right user works, as with an array all codes would be valid for all users (which increases the "risk*").
* Protecting something in the frontend isn't really a protection anyways. Someone with a little experience with JS can click right through, regardless of which pin you set.
Is your feature request related to a problem? Please describe.
Not related to a problem, just that at the moment we can only specify one unique pin code per card
Describe the solution you'd like
Change the code section to make it a list of strings instead of just a string
Describe alternatives you've considered
N.A.
Additional context
When multiple users are using the wall tablet, it's nice that that everyone can have his own PIN code (ie. to disable the alarm system).
Thank you very much for considering the feature request :-)
The text was updated successfully, but these errors were encountered: