Updates to the SmartThings Platform

[jkp]

FAQ: SHM and STHM are different

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…

Confusion about local processing

In the article https://support.smartthings.com/hc/en-us/articles/209979766-Local-processing you can find the following statement: If your devices and Automations meet all the above criteria, they will be able to run locally when an internet and/or power outage occurs. For example: […] ** In the event of an internet and/or power outage, a SmartThings Home Monitor automation that tells your Aeon Labs Siren to sound when motion is detected by a Samsung SmartThings Motion Sensor will locally execute.* This is exactly what I’m running: A SmartThings Motion Sensor and a Aeon Labs Siren (which both lists as local processing on the IDE page) and SHM alarm. Still, when I pull the plug to my router the alarm will not get triggered. I am running the 2018 hub. On the IDE page -> Installed Smart …