I also have this problem.
blake.arnold
He is in the classic app using the custom configure in the Smart Home MonitorâŚThis is one major function users want. We want to use a SmartThings device (motion/presence/lock) to force cameras (Arlo/Ring) to record for a certain period of time. Right now the only function is on/off. I personally want my cameras on at all times and will record motion and sounds from the camera itself (never know what it may see that doesnât necessarily happen at my front door). However, forcing a recording from a ST device is a handy function.
In the new STHM you can set the Arlo camera to record in the event of an intrusion. You just canât set the duration, which I think is 1 min.
I suspect this has been asked before: In the new app, why canât you control STHM in a Scene?
This thread âGet ready to make the switchâ is now over 5 years old. So surely someone from the Smartthings team can say whether or not HTTP will ever be supported on the new platform. If so, then when?
With 50% of my devices relying on HTTP and Classic I donât see a way forward with Smartthings as things currently stand.
Although it may feel like itâs that old, it actually started in January:
![]()
Do you mean http on the local lan?
Yes, to the local LAN using HTTP.
Something like this:
def hubAction = new physicalgraph.device.HubAction(
method: âGETâ,
path: path,
headers: [HOST: â{settings.destIp}:{settings.destPort}â]
)
Groovy DTHs will continue to work the way they currently do until we have a replacement.
You can make your standard capability device work in the new app today. We will have a way to make custom capbilties work in the future. The use of hubAction in groovy is not linked explicitly with the classic app.
Thatâs funny. I assumed Jan 15 meant January of 2015. I figured since the new Smartthings App has been around since 2017 this thread must pre-date that.
Jody, thanks for the quick response and the clarification. I read somewhere that it was Zigbee and ZWave only but that must have been in reference to something else. My devices do have custom capabilities so itâs a shame to dumb them down but at least you have given me some hope, although Iâm always afraid when I see the word âfutureâ as relates to capabilities.
2 posts were merged into an existing topic: Updates to SmartThings Community
You may have found yourself in the Developer Workspace. If you use that as a starting point you will get the impression that Hub Connected devices can only be Zigbee or Z-Wave.
The Developer Workspace seems to be a strange alternate reality where the âpublish for meâ concept doesnât exist and a lot of terminology is either stuck in the past or just different. It is perhaps the most âWTF?â thing about SmartThings, now that the ânewâ app is actually usable.
No, still working on it. This was their reply to me today:
âWe will work on this and get back to you with a prominent solution. Kindly allow us some time.â
Wow Iâm just seeing this and Iâm very surprised. Basically every older device I have is not new app compatible and frankly it never will be if the new app doesnât become more backward compatible. These cheap chinese device manufacturers are never going to update their UIs. You canât turn that off without a working transition plan, Samsung, or you will be forcing a lot of us to buy new devices for no reason at all other than we canât click on a button in the UI or something equally dumb.
LOL and I see Smart Lighting SmartApp STILL doesnât work in the new app. Itâs been, what, three years now?
You guys are nuts if you think this app is ready.
It works just fine. What are you trying to accomplish that itâs not working?
â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.
No. Iâm not going to redo all 20 automations because Samsung has buggy software.