With the classic app, if my water sensor tripped, it would shut off the valve EVEN if the INTERNET was down.
They SAID that the V3 app would have local control… IT DOES NOT.
If I disconnect the router from my cable modem (shutting off the internet), nothing happens.
Can someone else confirm the same behavior ?
This will be the last straw to switch to Hubitat if they force us to go to an app that doesn’t support local control for home monitoring.
Support was horrible…they didn’t know what local control was…I asked to speak to someone else and they put me on hold for 20 mins. I hung up and they called back, put me on hold for another 5, then told me they would call back. They called back and hung up on me. If only the first support person I talked to knew understood her product.
I agree it’s a huge change if it’s true, and should have been called out.
I don’t know if it meets your requirements, but the new V3 app does have local control for the official smartlighting feature. Not as part of the security features, though. Valves typically show up as switches, so you might be able to set up a local automation that way. But it won’t have the same mode filters so I don’t know if it will work for you.
I just discovered that “automations” in the new app are all cloud executed too (unless someone can prove otherwise). I had assumed that the same rule applied as does for “smart lighting” where if all devices involved were local then execution would be as well, but that does not seem to be the case.
Do we know of anything “new app exclusive” that IS locally executed?
Some SmartLighting automations can run locally, and that’s it, unless there is some part of STHM that runs locally the way SHM did. Still waiting on official confirmation one way or the other on that one.
Automations created any other way do not run locally at this time.
They keep saying they are going to add more local processing, but it hasn’t happened yet.
Oh, I see …
I knew the Smartthings Home Monitor was NOT local control BEFORE which is why I used the Classic App. …but I I guess I never thought they would make us move to the new app without solving that issue.
Especially because the Classic App can do it This is unacceptable.
Tim
Well after days of back and forth with Samsung support …where they tell me it works correctly in the new app and had to clear cache, and uninstall,reinstall…, upload logs,etc… they come back yesterday and say "oh smartthings home monitor will NOT work if internet is down and that I should use Smart Lighting to do the Home Monitor function… How &^(&^&)() ridiculous is this. I actually tried to use the Smart Lighting but when you go to pick what device to control…you can’t pick the valve is for leak detection. My FIRST question to support was whether it worked locally like the Classic App and they said yes…and led me down a huge waste of time.
I will be getting a Hubitat hub, Samsung is incompetent.
Samsung support was kind enough to get back to me with the following (below)… I just really cant understand their treatment of loyal customers…
Thank you for your patience.
From the Team:
This is to inform you that local processing is not supported in the new app. Please apologize for the inconvenience.
We regret the inconvenience.
Thank you for your kind understanding,
True, but it never did run most of the security features locally. For example, there was never a way to arm or disarm the system locally (which led to a lot of hair pulling if the internet went out when the system was armed and the siren kept going off. )
And there was never a way to send a notification without the internet.
(The only exception to these was the dual logo ADT/SmartThings panel, which did have local operation.)
Anyway, what’s been lost are some of the local automations like “if a sensor is triggered, turn on the lights” but you should be able to recreate those In the SmartLighting feature. The problem is smartlighting doesn’t have a sensor group like the security features do so setup can be very tedious. But doable.
What I don’t like is that this change (from local to cloud) was made without notifying customers at the time of the migration. So they don’t know their formerly local rules now require internet. Even if this isn’t being used as a primary security system (which it shouldn’t be), that’s a big change.