Smart Home Monitoring / Scout Integration Bug:
Confirmed issue with SmartThings support (Dominic R) - Related to the April 7 firmware release, some users of the Scout paid SHM integration (such as myself) started receiving calls from Scout for sensor trips against sensors explicitly not-mapped in the SHM UI. In other words, SHM is sending alerts to Scout for sensors not set as active in the SHM UI.
This is an active bug, and in forcing me to no longer turn on SHM at night.
I’ve been told that as this is a “3rd party issue”, it will not be listed on the Platform Status Page
I’ve also been told to contact Scout for service fee refunds.
What I can’t determine is which 3rd party is at fault here (this appears to be a SHM issue), estimated timelines (internal support ticket # is 341001), priority within SmartThings to fix, and who will be refunding my service fees.
So, FYI - If you have or are planning to set up a Scout integration with SHM, and do not wish to use all security sensors, you may encounter this issue as well.
I’ll update this thread with any/all information received