You are so right… wow, I’m dumb. I feel like there was something that was in Notify Me When, that wasn’t (yet) in Automations… so I guess I was still just looking for it. However, I was just able to reproduce all my Notify Me When notifications into Automations, so I’m good to go! Perhaps the sweet December update added what I thought I was missing. Thanks!
3 Likes
The list of issues preventing me from solely using the new app has reduced greatly with the last few updates and i appreciate the hard work that has gone into it. The issues that still remain for me that require the classic app are:
- I rely heavily on Iris Keypads to arm and disarm SHM.
- Samsung WAM1500 and WAM3500 speakers are discovered and added in the new app but cant actually be controlled or have notifications played through them. Example: dogs barking on intrusion works in classic SHM but no sound when setup in the new STHM. Support had no resolution.
- Notifications working for echospeaks devices would be nice.
- Things that maybe should work but are just broken: Galaxy watch can no longer be used in automations in new app, broken a couple updates ago and support told me they have no resolution.
Skybell can be added in classic app but no button or motion events actually come through to smartthings. Support also had no resolution but i see that the new app has no option to add it, would be nice to just get a clear “support for skybell has been removed from both apps” or “we know its broken and we are trying to fix it” - A weird quirk that bugs me, if smartthings home monitor doesnt disarm for some reason (location issues) and i trigger it, if i hit disarm in the 30 second delay i have set before the alarm goes off, the alarm should be cancelled and not go off. Currently if i dont dismiss the trigger in addition to choosing disarm, the alarm still goes off even though its been disarmed at that point before the 30sec trigger. Am i thinking about that wrong or is that how normal security systems operate as well?
Also related to how the new STHM works, if i have the alarm turn on 15 lights when an intrusion is detected, after i dismiss that intrusion, all 15 lights stay on and i have to individually turn them all off, in the classic SHM they would all be turned off with the siren after being dismissed. Much prefer the Classic SHM way.
@blake.arnold
Happened to me as well, just disappeared while in the armed away state so my alarm KEPT going off constantly even after i added it back. Figured out it was still listed under smartapps as Smart Home Monitor and the one i setup today is renamed to Smartthings Home Monitor. Had to manually delete the Smart Home Monitor that wasnt showing from the smartapps.
What kind of virtual switch are you using here? 3 separate virtual switches mirror SHM modes or a single 3-state like switch? I’m struggling to figure out how best to recreate my SHM WebCore piston for STHM 
I haven’t noticed this however I did notice that while previously created simulated switches were showing up as local any new simulated switches I create are now showing up as cloud devices.
@blake.arnold Not sure how these speakers could of been omitted from your original year old internal list of devices to integrate to make the new app a SmartThings app, like the Classic is. Maybe someone forgot? Please put them on the current list.
Samsung Speakers
WAM 350
WAM 550
WAM 750
WAM 1500
and WAM 3500
1 Like
I setup three switches in the new app, disarm/arm(away)/arm(stay), and have created automatons that turn off the other two switches if the any of the switches is turned on:
There may be a more elegant means to do it but I consider a switch to be something that is on or off and this way I can link the STHM setting to a switch of the same/similar name.
Endpoint means a non-Groovy based, webhook SmartApp. They don’t run locally on the hub.
2 Likes
Well the problem is SmartThings isn’t addressing third party or “community” developers directly anywhere that I can see on their new SmartThings Developers website. The encourage developers to join the new Developer’s Workspace, but to enroll in SmartThings Developers, you can’t be a third party:
If you look at SmartThings Developers documentation page on Hub-Connected devices, it explains that being enrolled as an organization member in Developer Workspace is a requirement:
So, as I’m seeing it, this documentation isn’t written for me! If Samsung / SmartThings intends to address “community” developers in the official documentation, I’m not seeing it. I only see interfacing with the community in a rather haphazard way here on the forums.
Yes, and what about users? They have had access to the new mobile app for months and months asking how to get X or Y device with a custom device handler working in it, and the documentation has remained unavailable to community (aka third party) developers. Personally, I’m not going to spend a waste time trying to guess how to get the custom DTHs I’ve helped develop working in the new mobile app, but this has resulted in a lot of frustration on users’ part.
Fair enough on giving people time before the classic app has been fully sunset, but in the meanwhile I have read plenty of accounts of user confusion over which mobile app they should be using, and quite a few unhappy campers that discover they need to keep one foot in each mobile app (classic and new) to continue using all of their connected devices, since those with custom device handlers are still in various states of (un)usefulness in the new mobile app.
I understand there’s not much reason to provide any support or documentation to someone whose developing / maintaining device handlers for devices never intended to work with a SmartThings hub, but I see plenty of example of devices that should work but just aren’t due to custom device handlers that are waiting to be updated when documentation on the new DTH components are made available to explain how to get it all working again.
1 Like
Good thinking, but appears iOS widgets are only supported on iPhone, iPad, and iPod touch: https://support.apple.com/en-us/HT207122
Thats what i thought as well, but today when it disappeared from the new app and i created a new instance of it, on the smartapps listed in the new app, the old one was definitely named “Smart Home Monitor” and the new instance “Smartthings Home Monitor”. The one named just “Smart Home Monitor” that disappeared was definitely for the new app because once i found it and clicked on it, the interface opened to let me disarm it. I wish i had screenshot it, i know im not crazy.
1 Like
They were both called “smart home monitor“ for over a year, so there may be some places where the old name is still being used for the new V3 app. 
1 Like
BS. Time to switch. None of my custom device handlers and smart apps work in the new SmartThings App. Way to ruin a good thing Samsung!
Are they ones you’ve written or ones from others? Apps should actually be working for the most part, but custom DTH’s will have only the basics until ST enables custom capabilities/attributes (hopefully soon).
1 Like
I had to delete my custom DTH devices and install them again to see the “tiles” using the attributes I updated/implemented.
I hope you do not have any older GE switches.
Me too! Those old GE Switches are aweful! 
At the moment, for hub connected devices, the only thing an organization member developer can do that a community developer can’t is submit a DTH for publication.
The documentation for the new mobile app and hub connected devices isn’t available to members of organizations either…
2 Likes
I love my switches. I have about 50 installed and have no problem with then on ST.
2 Likes