However, in composite devices like sensors with buttons, the button UI will not display the actions. Doesn’t matter if the button is sharing the main component with the sensor or if it has its own component of category RemoteController.
@chroeth did some digging and apparently the actions will not display if the main component is notRemoteController.That would explain why the contact sensor example doesn’t display them (which still should IMO), but it does not explain why the individual components which are RemoteController do not display them.
Wondering if it’s a bug in the app or it’s by design @nayelyz .
I’ve never really understood why the preset routines for the buttons (and also the timer for switches) are on the Controls tab instead of the Routines tab where the broadly similar types of functionality were moved to for other devices. Regardless of where they are it does seem to be rather inconsistent.
If categories are the key to displaying the extra knobs and whistles then I would suggest that it would make a lot more sense to show button automations for Button and not RemoteController.
That’s a keyword for those presets or shortcuts indeed, even if they’re routines in the end they don’t behave like normal routines.
We all know that if you hide a device in SmartThings then you can’t use the presets for any other device.
And if you delete a device used in one of those quick actions, SmartThings will just delete the action/routine instead of letting you replace the device like happens with normal routines. That’s why I usually include manually run routines in the quick actions instead of the actual actions, it’s easier to replace a device like a light.
I find them useful sometimes for simple actions, although it is objectively better to create actual routines even if you have to sacrifice the quick look at what each button does when you don’t remember.
Hi, @mocelet
Sorry for the delay. I was trying to find an old conversation about this, but the information was split up. So, the feedback collected is:
This is expected behavior.
Background:
These “Routine quick control” buttons are available only when the category is “RemoteController” or “Button”. This is because they intend to show them only when the device’s primary function is acting as a button; otherwise, the detail page would be cluttered, and even more so if the button had several actions available.
Thanks @nayelyz , I understand their reasoning although it’s unfortunate.
A contact sensor with a button (Bosch) or a temperature sensor with three buttons (Aqara W100) would not clutter the UI, in fact it feels empty if there are no button actions since the main feature is just one line with a state (opened/closed) or a number (temperature) so there’s plenty of screen unused.
Anyway, I’ll mark this as solved since it’s by design.
