[FR] Long press action for quick settings tiles

[Jatoxo]

Is your feature request related to a problem? Please describe.
The quick settings tiles only support toggling entities. When you long press them, they just open the app info screen

Describe the solution you'd like
Long pressing the quick settings tiles should be a configurable action, ideally similar to the way actionable notifications can be configured.

One example use case would be a tile for a light. You could press it to toggle the light, or long press to open the light brightness and color controls.

Describe alternatives you've considered, if any
N/A

Additional context
N/A

[dshokouhi]

The only use case I see here is to open the entity more info panel. No need for configuration on that. Keep it simple.

[Jatoxo]

I was wrong in saying that long pressing a quick tile opens the home assistant app, it actually opens the home assistant app info screen

The only use case I see here is to open the entity more info panel. No need for configuration on that. Keep it simple.

That would certainly be better than the current capability, but I can definitely think of use cases where you do not want want to open the entities "more info" screen

If it is just a boolean toggle, then the quick settings tile already covers all of its functionality, you could use the long press to instead open a screen with additional controls or settings pertaining to the same device / category

A use case for configurability outside of opening the home assistant app on a certain screen could be a toggle for a device that is associated with another app or website, where a long press opens those

[dshokouhi]

I was wrong in saying that long pressing a quick tile opens the home assistant app, it actually opens the home assistant app info screen

that matches what Google says: https://developer.android.com/develop/ui/views/quicksettings-tiles#launch_an_activity

Long-tapping a tile prompts the App Info screen for the user.

However the intention is that overriding still takes user to a setting screen so the entity more info popup makes the most sense given that

https://developer.android.com/reference/android/service/quicksettings/TileService.html?utm_campaign=adp_series_quicksettingstiles_092916&utm_source=medium&utm_medium=blog#ACTION_QS_TILE_PREFERENCES

An activity that provides a user interface for adjusting TileService preferences.

Long press historically always went to settings, i am not sure we should do anything outside of that personally speaking. The long press action should behave just like long press does in device controls.

[Jatoxo]

The issue I have with opening the "more info" panel is that it can only be helpful if there is additional functionility on the same entity that you are toggling

If I look at the quick settings provided by Android, long pressing them brings up many other related settings. For example if you long press on the WiFi toggle, it opens the WiFi overview where you can manage multiple other related WiFi and network settings. Same with the bluetooth, Location or mobile data, the settings page they open includes many other related settings

For homeassistant to be able to function in the same way, it kind of needs to have the functionility for the user to say what "related settings" are (like a dashboard destination for example), because the app can't know what the semantics of the entity are (outside of maybe opening the associated device overview?).

From this perspective I think it makes the most sense that it should be the user's choice which "preferences" the long press should open, allowing the quick settings to function as if they were truly a "native" tile from some integrated smart home ecosystem (as opposed to explicitly being brought to an uncustomizable home assistant UI

[curz46]

Hi, I just started using Quick Tiles with Home Assistant Companion App and I'm also interested in this feature. In particular, being able to change a light entity's colour and brightness from a Quick Tile via long-press.

The long press action should behave just like long press does in device controls.

Agreed, this should be the default. I don't mind whether it can be configured to do something else.

As an aside, having just tried the device controls feature with the companion app, it seems to take a long time to bring up the corresponding menu after a long-press. I presume the companion app's view initialization is taking a while.

[dshokouhi]

As an aside, having just tried the device controls feature with the companion app, it seems to take a long time to bring up the corresponding menu after a long-press. I presume the companion app's view initialization is taking a while.

There is a 2 second delay to ensure the frontend loaded completely before the pop-up shows otherwise it wont work. You should see it load as fast as the app does when you open it from your launcher on a cold start. On my phone it loads up in 3 seconds.

if you force stop the app and open again do you see the delay gone?

[curz46]

Sorry, I should quantify a "long time". It takes roughly three seconds on my phone, too, whether I force stop beforehand or not. It's slightly longer if I force stop the app. Of course, it is not a deal breaker for daily usage, just a slight defect.

edit: I suppose I have been spoilt by how fast the companion app's Quick Tiles work. I was pleasantly surprised to see toggling my light is instantaneous.

[dshokouhi]

just a slight defect.

For us not a defect but a feature 😅 we have to wait 2 seconds for the frontend to load or the popup will open and close immediately. The only real fix is for the frontend to allow the pop-up to trigger faster with a URL. Still waiting on my original request too: home-assistant/frontend#7428

Teh app uses this feature in other places like shortcuts and notifications so the delay is the same everywhere.

in the past we found custom cards like card-mod to also impact this feature. We use javascript to trigger it so a bit of a hack but its also all we have.

[curz46]

Agreed! It would be great if the popup menu here ("more info dialog"?) could be opened in its own activity, or just in a more lightweight fashion than what is being done here. Clearly that architectural work is not trivial though.