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
{{ message }}
This repository has been archived by the owner on Jun 20, 2022. It is now read-only.
For those who use lovelace yaml and hide all views tabs using only navigation_path (like me) to access views, here is a parameter suggestion:
navigation_tabs: "config;home;scenes|lighting;rooms|config;config-network;config-system;config-lighting"
This parameter if used, would override skip_tabs!
In this way, using the view path, it facilitates the organization of dashboards with multiple views(the path is better than number in large ammount of views!!). The | (pipe) would be responsible for the segmentation of blocks..... the swipe would only work between config, home and scenes....and at another point between lighting and rooms and so on.
Thanks !!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For those who use lovelace yaml and hide all views tabs using only navigation_path (like me) to access views, here is a parameter suggestion:
navigation_tabs: "config;home;scenes|lighting;rooms|config;config-network;config-system;config-lighting"
This parameter if used, would override skip_tabs!
In this way, using the view path, it facilitates the organization of dashboards with multiple views(the path is better than number in large ammount of views!!). The | (pipe) would be responsible for the segmentation of blocks..... the swipe would only work between config, home and scenes....and at another point between lighting and rooms and so on.
Thanks !!
The text was updated successfully, but these errors were encountered: