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
Feature: Custom ratio for the remote and then lock the ratio, so scaling remote still fit the device's ratio.
I think App launcher 1 & 2 would be most suitable for this feature. The reason for this feature is to make it easier to make clean cards that eliminate scrolling.
Now it is trial and error to make it fit well. As I use both Mobile, Ipad and computer and make separate dashboards for each device it take some time to fix after doing some changes.
Maybe it is something I have misses but I have looked around.
Additional Comments (optional)
No response
The text was updated successfully, but these errors were encountered:
I don't have any immediate ideas for this yet. I know that arranging dashboards with cards of varying sizes can get tricky, and I admit that the Firemote card can make things somewhat difficult too.
Have you had a chance to look at the latest Home Assistant versions, especially the latest release 2024.9? They have been making some great changes to the dashboards with the new experimental sections layout option. You should give that a try once, and see if it helps.
Let me know, I'm interested to hear if it works well for you or not.
Is your feature request related to a problem?
No response
Feature Request
Feature: Custom ratio for the remote and then lock the ratio, so scaling remote still fit the device's ratio.
I think App launcher 1 & 2 would be most suitable for this feature. The reason for this feature is to make it easier to make clean cards that eliminate scrolling.
Now it is trial and error to make it fit well. As I use both Mobile, Ipad and computer and make separate dashboards for each device it take some time to fix after doing some changes.
Maybe it is something I have misses but I have looked around.
Additional Comments (optional)
No response
The text was updated successfully, but these errors were encountered: