blake.arnold:
Correct. The endpoint smartapp that replaces SHM is called SmartThings Home Monitor. The key takeaway here is the they are two different apps. You’ll only want to have one running at a time or it can get annoying, especially if you have different triggers for each (I ran into this during beta and dogfooding). The migration process will migrate your settings to the endpoint version and uninstall the groovy version automatically, but if you start playing with the new app before using the migration tool, be aware that it’s possible to have both running at the same time.
There’s a FAQ for that…
Just to make sure everybody’s talking about the same thing…This FAQ is for people using both the V2 classic app and the 2018 V3 app, or who have previously used the classic app and have now migrated to the new V3 app.
The security feature in the classic app is SHM, Smart Home Monitor.
The security feature in the new V3 app is STHM, SmartThings Home Monitor.
These are two completely separate pieces of code.
Security mode set or changed (or an alert dismissed) in an automation created in the classic app will only affect SHM. .
Security mode set or changed (or an alert dismissed) in an automation created in the new V3 app will only affect STHM.
So if you have rules you created in the classic app, you will never see those change the security state in the new V3 app. You have to recreate…
Note in particular the need to individually delete all SHM automations in the Classic app before deleting the app itself or they just keep running forever. You might want to add that to the migration instructions unless you’ve cleaned it up on the cloud side.
6 Likes
