Do not take this plugin as a security measure. Anything on client side is insecure by default and anyone with the minimum knowldge and with access to the device can inspect the code, the network tab and check your secrets. This is more intended to avoid kids/spouse/friends to interact with certain elements/entities of Home Assistant.

In Home Assistant, it is very common to hide or restrict elements from non-admins users. There are multiple HACS plugins that are used to restrict critical sections, dasboards, UI elements, cards, etc. from unauthorized users (kiosk-mode, custom-sidebar, lovelace-state-switch, are some of them). This is a recurrent task in kiosk devices that are intended to be used by the whole family or by a large group of users. The issue comes when the owner or admin wants to interact with those elements on the device because these elements are hidden also for them.

Even if those elements could be shown switching some entity, the admin needs to go to a device in which that entity is visible to be able to interact with it. It is something no so straightforward to do on the same restricted device.

But what about showing the desired element, navigating to the desired dashboard, or switching the desired entity not with an UI element but with something hidden and only known by the admin/owner?

This is when Home Assistant Secret Taps comes to scene, you can configure "secrets" based on sequences of taps on the screen and perform certain actions when these secret taps are executed. Call a service, open the more-info dialog of an entity or navigating to a dashboard are the main actions that could be performed only touching in any part of the screen using the correct sequence.

Do you have the header hidden and to show it you need to change an input_boolean?

You can configure a sequence of taps that will call the toggle service on that entity to show the header, then you can perform the changes that you want, and turn it off again using the same tap sequence.

Do you have the sidebar menu-button hidden to avoid someone else being able to open it and navigate to other dashboards?

You can configure a secret sequence of taps that opens and closes the sidebar without interacting with any visible element.

Do you have a hidden subview that is not linked from any other view and which is full of entities to administrate your Home Assistant instance?

You could navigate to that subview without clicking on a link, just executing the correct tap sequence that you configured for that.

These are just common hypotehtical use cases but I am sure that you will ideate your own. Just configure and perform your secrets taps and execute your actions without any visible interactive element and without letting any trace 🥷

You can install the plugin manually or through HACS, not both. If you install the plugin using the two installations methods you could have issues or errors.

1. Go to HACS dashboard
2. Go to Frontend
3. Click on the three-dots icon in the top-right corner
4. Select Custom repositories
5. In the repository field insert https://github.com/elchininet/home-assistant-secret-taps and in the category select Lovelace
6. Click on Add
7. Click on Explore and download repositories button in the bottom-right of the screen
8. Search for home-assistant-secret-taps and install it
9. Add the url of the plugin as an extra_module_url in your configuration.yaml:

frontend:
  extra_module_url:
    - /hacsfiles/home-assistant-secret-taps/home-assistant-secret-taps-plugin.js?v1.0.0

10. Make sure you add home-assistant-secret-taps-plugin.js and not home-assistant-secret-taps.js and make sure you add the correct version at the end of the URL (e.g. ?v=1.0.0) because in this way you make Home Assistant to load the new version instead of a version stored in cache
11. Restart Home Assistant

1. Download the latest home-assistant-secret-taps release
2. Copy home-assistant-secret-taps-plugin.js into <config directory>/www/
3. Add the url of the plugin as an extra_module_url in your configuration.yaml:

frontend:
  extra_module_url:
    - /local/home-assistant-secret-taps-plugin.js?v1.0.0

4. Make sure you add home-assistant-secret-taps-plugin.js and not home-assistant-secret-taps.js and make sure you add the correct version at the end of the URL (e.g. ?v=1.0.0) because in this way you make Home Assistant to load the new version instead of a version stored in cache
5. Restart Home Assistant

The configuration must be stored in a yaml file that needs be placed inside the <config directory>/www/ directory. The name of the configuration file should be secret-taps.yaml. It could be easier if you copy the example secret-taps.yaml file, and edit it to match your needs.

Note: the threshold among taps is by default 1000 milliseconds (1 second) and you can increase it. Just take into account that this number is also the delay between the last tap and when the action is executed, because during this time the plugin is still expecting that another tap could be executed.

Notes:

1. If you don't set at least one property from user, admin or owner, the profile will match with any user
2. Multiple profiles could match with an user. For example, if you have a profile for admins and another profile for the user John, if the user John is admin the two profiles will available to him

All secrets should have these properties:

Note: you should always configure the taps property using multiple taps and not a very common taps pattern. If you set up an action to be performed with a single tap, it will be executed every time that you tap on the screen, always.

• tap: single tap on the screen
• double-tap: two consecutive taps on the screen
• triple-tap: three consecutive taps on the screen

Sequence of taps example

taps:
  - tap
  - triple-tap
  - double-tap

• call-service: action to call a service
• more-info: action to open a more-info dialog
• navigate: action to navigate to a certain path
• toggle-menu: action to open or close the sidebar

Each secret can be any of the next ones:

Call-service secret example

action: call-service
service: light.toggle
data:
  entity_id: light.woonkamer

More-info secret example

action: more-info
entity_id: sun.sun

Navigate secret example

action: navigate
navigation_path: /config/dashboard
## Optional parameter. It is false by default
## Whether to replace the current page in the history 
navigation_replace: true 

Toggle menu secret example

action: toggle-menu

## enable the plugin
enabled: true

## list of profiles
profiles:
  ## This profile will match only with these users
  - user:
    - Jim Hawkins
    - Long John Silver
    secrets:
      - taps:
        - double-tap
        - tap
        - triple-tap
        action: call-service
        service: input_boolean.toggle
        data:
          entity_id: input_boolean.kiosk_header
      - taps:
        - tap
        - double-tap
        - tap
        action: more-info
        entity_id: sun.sun
      - taps:
        - double-tap
        - double-tap
        - tap
        action: navigate
        navigation_path: /config/dashboard
  ## This profile will match only with non-admin users
  - admin: false
    secrets:
      - taps:
        - double-tap
        - tap
        - triple-tap
        action: toggle-menu