I also am facing issues with the verification code. I had been using chrome. I just tried it out on MS Edge and still cannot get past the last step with the “code”
So I tried Chrome, edge, FF on windows and Android. The only thing that worked was Safari on my Mac book. Using Safari caused the redirect to happen and I was able to get the code. Thanks for the help!
I see…if you go into Developer Tools in the browser (in the Console tab), I see some messages about “Failed to launch”…with the URL and the code at the end. You will want to use that code and put it in HA
Great info, thank you! I’ll submit a docs PR with this info.
Using the error from Developer Tools worked for me as well!
This worked for me as well, tested in Edge. I didn’t need to reference any verification emails. I also have 2FA set up on my account. Hopefully these steps help.
- Opened authorization link in browser from integration Reconfigure popup
- Entered SS credentials & submitted
- Entered 2FA code & submitted
- Opened Dev Tools > Console
- Copied value of the
code
query string parameter in theFailed to launch
URL - Pasted into the integration prompt
- Success
The developer console doesn’t show the code in ChromeOS. Have to use a Linux or Windows desktop.
Can anyone give me screenshots or something? I have tried chrome, firefox,edge, but I don’t see a code of any kind in either the window in the dev console.
Edit/Update
Ignore me, I was able to see the error by turning on 2FA in my account which then produced the error and code I needed which worked.
Another solution:
Using Firefox on Ubuntu
- Opened authorization link in browser from integration Reconfigure popup
- Entered SS credentials & submitted
- Entered 2FA code & submitted
- FF prompted me to open the link with an external application. Luckily I was able to transcribe the “code=” section of the URL it was trying to open, and that was the value Home Assistant needed.
Not working here. After entering the 2FA code, nothing happens. None of the buttons get me anywhere, no login.
I never get past logging into the WebApp for simplisafe never get the second tab opening
I do. Managed to get it working by finding the code= part in the browser console - network.
But: This is not an easy setup and most users will not go that way. Needs improvement… Thanks!
I cannot improve the overall experience, unfortunately. This is 100% due to SimpliSafe. What I can do is update the docs with as much knowledge as we have and continue to revise it over time.
My MFA has been turned the whole time I have used SimpliSafe
@kendadk, you shouldn’t necessarily have a second tab be opened up. After 2FA verification, you should still be “stuck” at the SS login page. From there, open Developer Tools (usually the F12
hotkey in most Windows PC browsers, not sure about Apple machines). Then go to the “Console” tab/area and look for a URL that begins with com.simplisafe.mobile
. Near the end of the URL, find the value listed after the code
variable:
code=<CODE>
The <CODE>
value is what you need to copy and paste in the integration’s “Authorization Code” prompt.
When I go to the console the url is
Prevented navigation to “https:// auth.SimpliSafe.com/u/mfa-sms-challenge?state=xxxxxxxxxxxxxxxlongphrase xxxxxxxxxxx”
“Then due to an unknown protocol. There is not a code there .”
But you are able to get through Steps 1-3 here?
What browser are you using? I’d suggest trying another. If a browser switch doesn’t work, you could try @iway’s method of opening the Dev Tools > Network tab and trying to find a request to that URL with the code in it instead of checking the Console.
If you go the Network tab route, you’ll probably need the tab open before you submit your 2FA code in order to capture the request URL.
Yes I am Stuck after I submit the Code from the sms i recieve fron SimpliSafe. then in the Console there is no code in the Url I have tried every Known Browser for Windows and also deleted mt App on my phone and used safari no luck with any of them.
That’s super frustrating. I wish SimpliSafe would invest the resources in shoring up their API access, but unfortunately we have to all stumble through this as best we can until they do.
Maybe you can attempt the Network tab route. Just make sure the Network tab is open before you complete Step 3. Hopefully that URL is in the network activity list.