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.
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.
Not the last time I checked.
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.
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.
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.
And just like that, @jody.albritton created the single most linked post on the community site⦠![]()
Said pretty much the same things back in January when this thread kicked off.
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.
@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.
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?
I donāt know how to reboot in the IDE, but I unplugged it for 5 mins and plugged it back in. No improvement.
https://account.smartthings.com/
Login with your Samsung account.
Click hamburger menu button in top right corner.
Click Hubs.
Click View Utilities.
Click Reboot Hub.
Give it a few minutes and see if this helps.
Also try a zwave repair in the utilities section and click View progress. Make sure it finishes with no errors.
OK. I rebooted, waited 5 minutes for everything to reconnect. No improvement.
I clicked Repair Z-Wave network and then Z-Wave network repair initiated - Click to view progress, but nothing ever populates in the table to show progress, etc.
In my experience, it can take a number of minutes for anything to show up on the screen - ST says āup to 10 minutesā. Sometimes, I get no reaction at all too. I wait 10 minutes. Then I start another Z-Wave Repair. Sometimes this happens 3 or more times in a row. Eventually, the process will complete (at least for me) with either some issues noted or if youāre lucky, no issues. I usually try over and over again until I get two successive āno issueā completed runs. Again, It may take quite a number of cycles to get there.
Before starting the z-wave repair, open a new tab
- go to hub
- click on āList Eventsā (not āView Utilitiesā)
- you now have a tab with Events List - keep it open
- in a different tab, start z-wave repair as you did in past - donāt bother with the " Z-Wave network repair initiated - Click to view progress" link
- go back to your Events List tab and hit refresh - you will see the z-wave repair initiated"message
- keep refreshing occasionally - if there are any issues you will see them
- eventually when the repair is done you will see a āz-wave repair completedā message. If you donāt see it, itās still repairing.
I always do this - it gives me more information on the repair and helps you understand how long it normally takes. (I only have 12 or so z-wave devices and it usually takes about 4 minutes)
Hope this helps!