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.
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 !!