2 Alarm Panel Entities: one that always shows a keypad, and another that follows the existing rules

[davesmeghead]

Just a thought process....

The user security in Home Assistant is rubbish.
What I've wanted to do for years is to set which users have to use the keypad and which users do not. The obvious use case is:

• You show a tablet/display near your front door --> always show keypad
• You want it on your mobile phone --> No keypad

Instead of one alarm panel entity, what if I create 2:

• The existing one: alarm_control_panel.visonic_alarm
• A new one that always shows the keypad: alarm_control_panel.visonic_alarm_keypad

The obvious questions

• How would this work with partitions? Do I double up them as well
• Would this actually be of benefit?

[davesmeghead]

OK so I've added this to 0.13.0.39, there will be _keypad added to the entity name(s)
I have left 0.13.0.38 on HACS so users can go back to this release if required, or you can restore from a backup.
I doubled up the main alarm panel entity and doubled up the partitions, so if you use 3 partitions you'll get 8 alarm panel entities 😄

[davesmeghead]

I've just created 0.13.0.41 with the finalised capability for Direct comms setups (but not Cloud yet).

Comments and questions here please