@JTRTech wrote:
I know this has come up a few times but wanted to bring it up in a fresh topic after seeing another reason a login user would be useful - auto login for kitchen screen.
I know there are 3rd party solutions to that one.My reason for wanting something was a previously discussed idea for switch user without logout first - using RFID fobs.
although a login user action alone would not solve my request...I would look to expand the hold ticket/switch user combo into a rule along these lines;
Rule for NUMBERPAD value entered with a constraint (would need new tag of something like {VAIDUSERPIN} which would check the number pad value is a valid user pin.
The rule would execute an automation command for hold ticket/switch user rule then a 'fastswitch command' carrying a command value of the NUMBERPAD (pin) number.
That automation command triggers a rule which logs user in using the command value of the pin.
The action would need to support PIN as a field.
If an action like this were continplated I would imagine fields of 'User' and 'Pin' or a User/Pin field and an option field to specify if the value is a PIN or a User name.
Am expecting this to be a controversial request with the sugestion of entity based users (kendash :-p) understandably coming up again but as I said I like to use the users setup already in place for reasons previously discussed.
However this action could solve additional requests including a native auto login possibility triggered by application start.
Posts: 12
Participants: 3