☰
+2 votes
by
Continuing to migrate over to new app - here’s more thoughts. Does anyone else notice that device names don’t always carry over to new app? There were plenty that’d been renamed many months ago and show correctly in Classic app, but not in new app. Another question - what’s the point of lighting groups? You can’t see them in Alexa and they’re not as full featured as you’d see using Trend Setter - can’t control color . Even more ambiguous are camera groups. While I like the idea of having all my camera feeds in one area I’ve yet been able to get multiple feeds to play simultaneously and why is it the clips button opens the camera app (Arlo in my case)? Another grievance I’ve got is after having created automations for each function of a new SmartThings button I was disappointed to find out none of the actions worked. Come to find out you’ve got to program it inside the devices itself. This is all in addition to the fact that tapping any of the menus oftentimes doesn’t work right away and can be quite delayed at times. Also noticed that when creating automations occasionally the control devices option isn’t always visible and have to back out then go back in again to see it.  
Continuing to migrate over to new app - here’s more thoughts.

1 Answer

0 votes
by (5k points)
When I first started using the new app, any device renamed in the last few days still showed under the previous name. As I'd been swapping the names of devices this was particularly problematic. I also had a shed load of devices that I'd deleted over the last few months - they were maintained dynamically by a parent device handler and were long gone on IDE and in Classic. I deleted them easily enough, though it was tedious. I got the feeling that syncing was mostly only reliable going one way from new to classic.  
The SmartThings Group is where you can always find questions, answers, advice, reviews & recommendations from other community members about home automation with the Samsung SmartThings hub.
...