“Network or server error occured. Try again later.”
In the old app, it works fine.
I don’t see that. Try removing the smart app it and re-installing it.
1 Like
No. I’m not going to redo all 20 automations because Samsung has buggy software.
1 Like
any chance you have any adware/malware blockers installed on your network? adguard?
it won’t affect your automations. They’re stored in the cloud. Or just open a ticket with SmartThings because smartlighting works fine in the new app and runs local too.
4 Likes
My ghost device has thankfully been removed
Has the issue where you can’t use something as a condition and an action in Automations been fixed? Sorry, haven’t been following along too much recently.
1 Like
Not the last time I checked.
1 Like
You are right Orange. I was looking for information on moving one of my DH’s over to the new app. As it runs on HTTP, when I read that statement I gave up looking into it any further. I poked around the Developer Workspace for a bit trying to figure out but left none the wiser and rather disillusioned. I have since bought a Hubitat Hub but the jury is still out on that one.
So what is it you are having problems with? I have two DH that rely on lan HTTP to communicate. I have them “sort of” working in the new app. Here’s where I’m at.
If they are showing offline, there is some device health code that can help with that.
If you are using custom classic tiles and attributes/capabilities, you are still out of luck there. The secret sauce to make that work is still not available. If you are using only standard capabilities, you may have more luck. VID ids are supposed to help with this, maybe. One of mine uses the music player capability and I have all kinds of inconsistent results with it.
Since I do have people using my DHs, and some trying to go new app, I ended up writing a smartapp to simulate the missing tiles for one that needed these just for install and activation. Painful and clunky, but gets the job done without having to install Classic just to set up the device.
Your custom commands still work in smartapps and WebCore, but not in automations/scenes as far as I know, same as Classic. Please, somebody let me know if I’m wrong here.
I truly feel your pain. I have a second location I want to add smarts to, and can’t decide if another Smartthings hub is a good idea.
1 Like
Nope you are spot on. We are working on a way for custom commands and capabilties to work in the new app, but it is still a bit down the road.
1 Like
When you say a bit… is that roughly 3, 6 months or perhaps 1 year? I know you can’t commit to a specific date but just curious on the timeline. 
Those are all specific timelines. I can say that will happen before we start urging people who use custom capabilities to use the new app. We aren’t going to take away classic without this functionality.
14 Likes
And just like that, @jody.albritton created the single most linked post on the community site… 
4 Likes
Said pretty much the same things back in January when this thread kicked off.
6 Likes
The new Android SmartThings Connect app does not appear to be supported by Samsung’s Multi-Window view on Samsung Android tablets (Tab S6) and smartphones (S8+) like the old SmartThings Classic app is. And in Samsung Dex mode the new SmartThings Connect app warns that some functions may not be supported, and it is missing the Dex window size toggle that is available on the old SmartThings Classic app in Dex mode.
I know this is cosmetics, but it would be nice to have both the old SmartThings Classic app and the new SmartThings Connect app up in multi-window (split screen) when converting/migrating/transitioning the old app Routines and SHM to the new app Automations and STHM.
2 Likes
@blake.arnold sensors that are used by STHM and fall offline - you should consider making the alert stand out more in the STHM block - perhaps changing the color of the font to red. Currently it is gray and I didn’t notice the alert right away for one of my sensors.
2 Likes
I have a Z-Wave device that works fine in the Classic app, but is Offline in the new app. It seems the issue is also affecting the Alexa integration for that device which shows as Unresponsive in the Alexa app and I cannot control it in the app, but it responds to verbal commands while Alexa says “[Device] isn’t responding…”
I’ve run a Z-Wave repair in the Classic app.
Any suggestions?
Have you tried to reboot the hub from ide?
1 Like
I don’t know how to reboot in the IDE, but I unplugged it for 5 mins and plugged it back in. No improvement.