Here’s what my integration does:
- When SimpliSafe state changes (home/away/off), STM and Mode change to match, any ST actions can be triggered as a result
- When SHM state changes, SimpliSafe gets armed/disarmed to match SHM state
- SimpliSafe state (Off/Home/Away) can be controlled from ST, each state is mapped to a virtual momentary button and works as expected
- IFTTT can control SimpliSafe as a result, since it’s just a virtual device in ST now
If there’s interest in how I achieved this, I’ll see to spend a bit of time and document, however, this integration is both hardware and software and not for the faint of heart.
In a nutshell, I hacked a SS keyfob remote, and used MIMO (2+ and Lite), by soldering wires onto the remote circuit board to simulate physical pushes on the Off/Home/Away buttons, this works great but again, not for the beginners.
Next, I used a combination of Virtual Devices, Routines, SmartApps, IFTTT and a WebCore piston to manage all that. Finally, I use FastMail’s ability to execute scripts when receiving status emails from SS to handle the SS alert logic and call IFTTT when SS state changes.
It’s a bit of a pandora’s box, but it all works. I can now run scripts like automatically setting SS to Home after a certain time, or when I lock my door at night, etc.
This shouldn’t be so hard, but it was nagging me so much I ended up building this solution over time and through trial and errors. It’s possible SS will one day open up their platform with IFTTT capabilities or directly with ST and make my solution obsolete, but for now, it works great.
And BTW, I’m using the latest SS hardware, and ST Hub 2nd Gen.