I would like to use the native button integration, but on Android, when I have Minimote buttons assigned natively to various devices, all devices type pages for that type of device will really LAG (5 - 10 seconds) when I open them in the SmartThings app. Example, if I have a Smart Bulb assigned to a button, then all of my Smart Bulb device pages really LAG when I open them even though they are not assigned to any buttons. I don’t think the device page LAG happens in the iOS app though, just the Android app like @Andremain expanded above due to Quick Control settings which setting the buttons up nativity apparently uses.
Funny thing is, I’ve searched for a SmartApp and found a Button Controller SmartApp template from SmartThings, but it doesn’t work in the new SmartThings app. I then found one on Gethub by bravenel which does work in the new SmartThings app.
I sure hope that SmartThings fixes this Quick Control issue with the Android app so that I can just use the native Minimote integration.
UPDATE:
Well, nothing worked for local execution because I finally noticed why. The Aeon Minimote’s ‘Child Button’ execution apparently doesn’t run as local execution on the new SmartThings app like they did in the old SmartThings app as they used to work when offline. Even though the Aeon Minimote device handler shows local execution, the ‘Child Buttons’ that are created show ‘Cloud’. That’s just dumb!
I bought the Minimotes to handle things when the internet is down since SmartThings listed the Minimotes as local execution a few years ago when I bought them. Say it’s morning and the system is in Armed Stay and the internet is down or their SmartThings Cloud system is offline (which has been happening a lot recently), there’s no way to disarm/rearm the system unless these button controllers work local. So I would have to unplug the sirens and take the batteries out, but if I’m going somewhere, that sure defeats the purpose of having a SmartThings Home Security system.
I even changed the Child Buttons handler to use the SmartSense Button handler which shows local execution, and even though the button still worked, it didn’t do anything after I unplugged the ethernet from the SmartThings hub. So even when the Minimote and Child Button using the SmartSense Button device handler both showed ‘local’, it still didn’t work when the Hub was not connected to the internet.
So now I apparently need to find something else that WILL work when the internet or the SmartThings Cloud is offline if this is going to be the way that this new SmartThings ecosystem is going to be moving forward.
Another UPDATE:
I found a combination of settings that allow the Aeon Minimote buttons to work locally offline when the SmartThings Hub is not connected to the internet.
With the Aeon Minimote’s using the Aeon Minimote device handler, and the child buttons set to the SmartSense Button device handler, and then using the Smart Lighting SmartApp Automations with a button as the trigger to trigger devices that run local, it works when the SmartThings Hub is not connected to the internet. However, I read in another thread that the new STHM doesn’t execute locally, and I just confirmed that which REALLY STINKS!