No, I migrated to new and it stopped working. Went back to classic to setup once again and that’s when i get the authentication error. Tried removing from Smartthings completely and start from scratch but still get the error.
1 Like
You need to send SimpliSafe a request to integrate with Smartthings.
I have not migrated to the new app and mine is still functional. I suspect migrating to the new app will break this integration as it uses the old groovy framework that is being phased out.
My SimpliSafe integration works fine in the new app. I recreated my routines as automations and scenes manually. I then “migrated”. I no longer have the classic app. All works well for now. I have contacted SimpliSafe in the past asking for them to integrate with SmartThings and didn’t get a hopeful reply.
I tried contacting SimpliSafe before about integration, but didn’t get very far.
When I try to authneticate via the SimpleSafe Control SmartApp, I’m getting an authentication error. IDE logs shows the following:
6:28:42 PM: error apiLogin() - General Exception: groovyx.net.http.HttpResponseException: Forbidden
6:28:42 PM: info getAPIUrl() entered with urlType: null
6:28:42 PM: info apiLogin() entered
6:28:42 PM: error checkApiAuth() - General Exception on authCheck: java.lang.NullPointerException: Cannot get property 'respAuthHeader' on null object
6:28:42 PM: info getAPIUrl() entered with urlType: null
6:28:42 PM: error apiLogin() - General Exception: groovyx.net.http.HttpResponseException: Forbidden
6:28:42 PM: info getAPIUrl() entered with urlType: null
6:28:42 PM: info apiLogin() entered
6:28:42 PM: warn checkApiAuth() Token Time has Expired, executing login
6:28:42 PM: info checkApiAuth() entered
Any suggestions for how to resolve this?
I think that’s exactly right. Mine has been working flawlessly until I migrated to the new app last week, and ever since, it hasn’t worked.
damn, I migrated as soon as I setup smartthings so I guess that is why I can’t get it to work. For now I’m just using the integration in Home-Assistant and then setting up a trigger to activate SHM using virtual switch from the HA / Smartthings Integration.
I’ll open with the fact that I acknowledge that I could be way way off here…however, I think that this can be resolved with some changes in the API call. What I need is an API specialist. My logic?
Try logging into Simplisafe from a new device, and not from within the app - but from a browser. SS added (I believe this is newer) a one time validation challenge for new devices logging into your account. Upon that log in, you will get an email sent to your registered email approving the log in. Then once logged in if you navigate to Account and then Manage Log ins (App and browsers have different names/navigation, look around), you will find a page where they save device ids for approved devices.
I also believe that they might be in the process of slowly moving their API portal which eventually if they close the current one this DH uses, will force new connections and thus the new Device ID requirement.
The changes for passing a Device ID and likely a better API portal, need to be added to the API - or so I believe.
In the meantime, I believe that migrating to the new app, moving from SS2 -> SS3 or switching from Smartthings <-> Hubitat <-> Homeseer - or whatever, will make the system see a new device and fail authentication.
Anybody know an API specialist willing to try to make it work, with a vendor (SS) that does not really want a lot of API access? 
Makes sense since the Home Assistant integration uses the simplipy SimpliSafe integration that does the email verification the first time for your smart home so it can pass the MA and stay logged in.
Interesting. I have never looked at Home Assistant. Are their apps and device coding open and readable like the groovy code ST uses or is it closed? I’d look at it if open to see if we can borrow some of their approach.
It is all open source and readable.
I looked, but sadly it is far over my head. I’m going to try to load up a simple rPI and see if Home Assistant will load and try the integration there. Hate to have to have more hubs, but if it is dedicated only to SS integration…maybe. Too bad.
I can respond regarding Home-Assistant. I dropped SmartThings a while back in favor of Home-Assistant. The Simplisafe plugin in Home-Assistant works great, and is very consistent. It doesn’t require polling, it instead uses pushes from Simplisafe on Alarm changes. Just a little detail on how the Simplisafe plugin works.
There is a home-assistant plugin called Simplisafe that basically interfaces the low level python Simplisafe Library to the Home-assistant architecture. It is purely used for the interaction between the Simplisafe python code and the front end user. Here is the Home-assistant plugin:
The low level library that is used as part of this component that does all of the Simplisafe communication can be found here:
This last link is probably the most interesting in terms of how to talk with the Simplisafe API.
@ssilence, I JUST got my rPI up with HA and connected to SS! It works!
Quick question, and apologies for not yet reading all there is too read! The set up recognized and created a device for the SS Pin Pad (or hub - not sure which) and my SS Smart Lock.
Can it create devices for each window/door sensor?
The HS SS plugin (also dead due to the MFA change) could actually create separate devices for each sensor (including all their others such as smoke and water etc).
WAF factor would go way up if I can track open/closed on windows with just the SS sensors - actually my acceptance factor would go way up too. Always chasing dead batteries on regular xwave/zigbee contacts - the SS sensors last for ever!
There has been talk in the forums with the Home-assistant Simplisafe developer about adding other sensors. He is considering that, but the issue is those would have to be polled. Right now very little is being done with polling, and he didn’t want to create a ton of requests to Simplisafe. I think it is reasonable to maybe poll them at regular intervals (user defined like 1 min, 5 min, etc…) and maybe on status change (alarm armed, disarmed, triggered, etc…).
Thanks for the quick reply. If there a correct forum for me to add a vote, point me and I can add a vote. I agree with you on the approach. The HS Plug In did create all the devices, and was coded for once an hour, but he was contemplating shortening it to 1 minute. He bailed on the Plug In when the API changed. It remains hourly, though not connecting anyway.
I just migrated into the new app, and have the same problem. Did you ever find a solution?
@ThePennster
Do you get an javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure error message as well?
Looks like the integration is dead given the move to new smarthing app.
Folks any other ways we can achieve geofencing arm / disarm for Simplisafe?