Integration still works on my phone with the new app. I had to create a virtual switch for it, though.
Is there an updated device handler that Iâm not aware of? In the new ST app, there is no âarmâ âdisarmâ button. Plus the Smartapp does not allow me to login even with the right password.
What follows is 100% my understanding and opinion. I accept being proven wrong.
The key here is a change to the API by SimpliSafe, however the change to the new ST platform exposed the SS change. For whatever reason SS does not want to really support a fully functional API - even though they already require you to pay the additional $15 per month ($10 for basic and $25 for advanced *numbers could be off, Iâve been advanced from day one - years ago.). Complain to SS by threatening your dollars. There is no reason a modern company canât make a reasonably working API in 2020.
My proof of API change - try logging into SS via a browser (not the app). Notice the newer MFA email challenge. This Device Handler does not trigger this MFA. It is my belief that anyone that has been using this DH and has not required initiating any change (switch from SSv2 to v3 for example) has been able to continue to use the previous system.
NOW: ST change to the new app constitutes enough of a change however , that SS needs to refresh your log in and pass their new MFA challenge. However, as noted this DH will never do that. For now, this DH is dead. (For those that it still works, I suspect you switched to ST new app before the SS API change and thus you are also still stable - for the rest of us = dead).
I have strung together a path through HomeBridge and HomeKit as they have had developers write their own connections.
Set a dimmer: 1% = Disarmed, 50% = Home, 100% = Away. Pass that through to HomeBridge (note iâm actually on Hubitat not ST anymore) and have HB / HK arm SS. Reverse works too if you arm w/ keypad to set up SHM or HSM. Not for the faint of heart however. If you regularly set up rPiâs you can do this.
Solution: get SS to change API, or get an API developer to write a new DH to SS API (buy that person a beer or 50).
Best of luck!
OK, sorry, but weâre doing different things. Iâve never used the ST app directly to arm SimpliSafe. If I have to manually arm/disarm, I usually use the SimpliSafe app. However, I have automations and scenes in the ST app that will arm/disarm SS using the current DTH. I also use SharpTools Rules (which are better than STâs automations). I created a virtual switch in the ST app to turn SS on/off (so I guess I could do it manually if I wanted to and avoid the SS app). When the switch is on, SharpTools runs a rule and turns on SS. When the switch is off, SharpTools runs a rule and turns it off. It checks to see if itâs already off first so that I donât get multiple announcements from SS that the alarm is off (which sometimes happened until I fixed my rule). So, in a way, you can arm/disarm SS manually in the ST app if you use a virtual switch and SharpTools rules. The basic SharpTools app is free and so are the basic rules. I cannot figure out a way to directly turn the alarm on in the ST app because as you figured out you only have those four options (i.e., off, strobe, siren & strobe, siren) (so I guess I could turn it off, but I could never figure out a way to turn it on without the virtual switch and SharpTools) (check out SharptTools at Sharptools.io). The Android app integrates with Tasker as well (if you have an Android phone). I use the Android app with Tasker and AutoLocation to open my garage door when I enter a geofence (among other things).
2 Likes
Iâve made some changes to the Device Handler to try and support the MFA authentication changes. Itâs still very rough and could use some better error handling / cleanup, but itâs here if anyone would like to test it:
Donations for beer gladly accepted: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=5C9KVK6LLLZRC
@tobycth3, the edits DO trigger the MFA! So promising!
However, with the new Smartthings app, as others note, the device only has the options as pictured (shown) by @ThePennster 8 days ago.
I tried clicking âOffâ on my side, all I get is âA network or server error occurredâ in the app (on the device) and nothing in any logging - anywhere.
Basics, Iâve been away from ST for a while (2 yrs), over with Hubitat, but my ST hub is still operational. I went to the Device Handlers and pasted your updated code over it and ensured my email and password are good on the device preferences - anything else I need to do? Iâve forgotten so much! 
There are a few code differences between SmartThings and Hubitat. Iâve uploaded a file to the same repo for Hubitat
Do you have the original code available? Mine was working fine until I updated the DTH with the latest code. I couldnât control SS directly with the ST app, but I was able to turn it on/off with a virtual switch and SharpTools. Now the virtual switch doesnât seem to control it. I also got a ton of email notices from SS asking about logins from a new device. And Iâm getting authentication errors in ST app. As Iâm trying this though, Iâm wondering where I would have entered my login info in the new DTH? Or would that be somewhere else? Itâs been a long time since I installed this originally. Thanks.
All copies of the DTH are on GitHub. You can click history to see the previous versions. SimpliSafe recently added the MFA emails you received. Youâll need to click accept/approve in the email notification before the DTH can login to your account.
I wasnât getting the MFA emails until I change my DTH. Maybe SS hadnât implemented it for me yet? ST is no longer controlling SS using my virtual switch. However, Iâm not so sure itâs the DTH. On my phone, I had to turn off WiFi to get the ST app to let me turn the virtual switch on or off. When I turn it on/off, itâs supposed to trigger rules in SharpTools. I just set up text messages in the SharpTools rules to let me know if they trigger. I am not getting any texts. Maybe SharpTools is not getting any indication from ST that Iâve changed the status of my SS switch?
I got about 30 emails last night from SS. My fear is that one of them was asking me to confirm the SharpTools IPâs attempt to change status and I missed clicking Verify. I wasnât paying attention to email because I didnât know SS had turned on MFA. It was only when I realized that SS wasnât turning off that I saw the emails. Iâm trying to trigger the SharpTools rule with my virtual switch to see if I can generate another MFA email, but nothingâs happening. Iâm beginning to think this is mostly an ST issue with communicating between ST and SharpToolsâŠ
By the way, the DTH I found, which I think is the latest, indicates that you last made changes 3/1/2019. Is that correct? Is that the latest? Thanks!
OK, things seem to be working now, so ignore my last two posts. I rebooted my Hub. That seemed to fix the issue with it not communicating with SharpTools. After I rebooted, and tried my SimpliSafe virtual switch, I started getting the text messages from SharptTools that my rules were being activated. Then I checked your GitHub and saw that there is a Nov 10 version of the DTH (which wasnât there when I checked yesterday, which prompted my question about the March 2019 version in another post). I updated the DTH in the IDE. Rebooted the Hub again. Logged in and out of the ST app and voila itâs working again! Yay! Thanks. And I sent you some beer money through PayPal.
LATER: Well, contrary to my last post, the saga continues. I thought it was working. I heard SS go âoffâ when I turned my virtual switch off. However, when I try to turn it on with my virtual switch, the SharpTools rule runs (I know because I get a text), but it doesnât turn on. Iâll keep experimenting later today. Maybe itâll just work itself out somehowâŠ
FURTHER UPDATE: I am now able to turn SS on and Off. It seems that my SharpTools Rules are not working properly. Nothing wrong with SharpTools, but I used some If statements in the Rules, such as if the alarm is already off, donât do anything, but if itâs not off, turn it off. For some reason, the Rule statement checking the current status of SS (i.e., on or off) doesnât seem to work. Well, at least I got ST to turn the alarm on or off using my virtual switch and rules! Iâll just have to play further with checking on the If statements and status checking.
2 Likes
On the positive sideâŠ
After being broken for months, the updated device handler works for me now. Thank you @tobycth3 ! The MFA email was triggered and I was able to enable access. I can see the accurate temp of my freeze sensor and I am able to turn off the alarm directly from the device handler.
One the negative sideâŠ
I am seeing the same strange device options as @ThePennster and the smartapp SimpliSafe Monitor is not syncing in either direction.
I have done some further experimenting. As I commented in another post, my IF statements in my SharpTools Rules are not triggering properly. When I set up a Rule, I can test the Alarm and Status attributes. I usually test Alarm. If it is âoffâ or not âoffâ, my Rule does something. For example, if the alarm is already off, my rule will cancel and not turn the alarm off again (because if it did, it would announce every time it got turned off even though itâs off (and it was doing this until I reconfigured my rules, and it got annoying 
)). However, SharpTools is no longer getting a correct reading from the Alarm. I tested this in Tasker by flashing the value of the Alarm attributes. Regardless of whether SS is Off or set to Home, the attribute returned is OFF. Did you change something with the reading/reporting of attributes in the new DTH? I might try testing with the older DTH to see if it works again (although I guess there might be issues with MFA). At least for the moment, I can modify the rules so that they do turn SS on or off, but I do get extra announcements. Iâll keep experimenting. Thanks.
LATER: I tried the old DTH. It wouldnât work at all with SharpTools and Tasker. I had to reinstall the new one to be able to read the attributes of the alarm at all. One thing I discovered is that it seems to take almost a minute or more before the SS alarm attributes changes from HOME to OFF or back again. That might be one reason my IF rules are failing. I might be testing them too quickly, one after the other. Have to do real work now, so maybe more testing later.
I will be happy to try it and report back. Later today. 
LATER: Hereâs an update. Nothing seems to have changed.
In my âturn on SSâ Rule in SharpTools, I check to see if the alarm is already âoffâ. If it is off, the Rule should turn on the alarm. It should stop if the alarm is already on. However, the Rule stops at this step. If I remove the âoffâ check from the Rule, the Rule will turn SS on to either Home or Away based upon the current SmartThings mode. For some reason, the Rule is not able to check whether SS is already âoffâ. This worked until I started changing the DTH.
My âturn SS offâ SharptTools Rule checks to see if the alarm is already off. If it is, the Rule should stop. However, regardless of whether the alarm is off or on, the Rule turns it off (so that there are multiple off announcements depending upon arrivals and current states).
So, Iâm not sure whatâs changed, but SharpTools canât seem to read the current alarm state, whether itâs off or whatever. I might try playing with the Status attribute, to see if that works at all. But so far it isnât working like it used to. Thanks.
LATER AGAIN: I think I have a way to solve this for now. I can check the status of my virtual switch. That should work. Iâm gonna play with that a bit to see how it goes.
By the way, I see itâs labeled to âfix buttonsâ. Does that mean I should be seeing options in SmartThings to turn the alarm on/off? If so, I havenât seen that yet. Iâve installed latest DTH and will test with my SharpTools rules. Thanks.
Not until SmartThings allows the creation of custom buttons again 
New version published to GitHub
- Improvements to MFA login and Polling