`Enhancement` Directory Page for direct Room navigation & Expansion to 8 Pages

[carlosnh96]

Enhancement Summary

I am requesting a "Directory/Menu" page accessible from Home to allow direct navigation to specific pages without swiping through all of them, and increasing the page limit from 4 to 8 to match the grid layout.

Detailed Description

1. The Problem:
Currently, to access specific Button Pages or Entity Pages, we have to cycle through them one by one. This becomes slow and tedious, effectively hindering quick access to controls.

2. Use Case:
In my previous setup, I organized my devices by Rooms (e.g., Living Room, Kitchen, Bedroom). The current sequential navigation makes this workflow difficult. With the proposed improvement, I could organize my home logically again, assigning one page per room and accessing them instantly.

3. Proposed Solution: Directory/Menu Page
I suggest adding a "Directory" or "Menu" page accessible directly from Home.

• Functionality: A grid of buttons where each button links directly to a specific Button Page or Entity Page.
• Action: Tapping a button jumps straight to the corresponding page (e.g., "Living Room" button -> Opens Page 1), bypassing the need to scroll.
• Customization: Ability to define text, icons, or images for these buttons.

4. Expansion to 8 Pages
Since the panel's grid accommodates 8 buttons, it would be the perfect opportunity to increase the limit from 4 to 8 pages. This would allow us to map 8 distinct rooms/areas to the 8 slots in the Directory Page.

Additional Context

No response

[stefanhintermayr]

Great Idea. 😃

[edwardtfn]

To be honest, the bottle neck of this project is on the Blueprint inputs. Currently, rendering that interface with all the inputs takes lots of resources and I can hear many users complaining of system CPU overloaded or not being able to manage settings due to that. And that is the main reason I haven't worked so much on things that requires more entries from the Blueprint.

I will try to find some time for a clean-up, or perhaps break it in more blueprints (like one specific for Utilities buttons, if some user want to use that, another to another rarely used functionality, etc.) or perhaps even removing some of the existing functionalities.

Other than that, expand the number of button or entities pages will be quite easy to implement. That Directory page wouldn't be that hard also.

[carlosnh96]

To be honest, the bottle neck of this project is on the Blueprint inputs. Currently, rendering that interface with all the inputs takes lots of resources and I can hear many users complaining of system CPU overloaded or not being able to manage settings due to that. And that is the main reason I haven't worked so much on things that requires more entries from the Blueprint.

I will try to find some time for a clean-up, or perhaps break it in more blueprints (like one specific for Utilities buttons, if some user want to use that, another to another rarely used functionality, etc.) or perhaps even removing some of the existing functionalities.

Other than that, expand the number of button or entities pages will be quite easy to implement. That Directory page wouldn't be that hard also.

Thanks for the honest explanation. I wasn't aware that the Blueprint inputs were causing such a bottleneck/resource load, but it makes total sense given the complexity of the project.
Regarding your points:

1. Splitting the Blueprint: I think breaking the project into smaller, modular Blueprints (or separating rarely used features) is a fantastic idea. It would definitely help with performance and make it easier to manage for everyone.
2. Feasibility: It is great to hear that, aside from the input limitations, the Directory Page and the 8-page expansion would be easy to implement on the code side.
   I completely understand that a clean-up/restructuring needs to happen first. Please take your time with that. I’ll be looking forward to those changes so we can eventually see this improved navigation implemented!
   Keep up the great work.