SmartThings is 'evolving' their developer API by charging for access starting in October. smartthings-evo is a copy of the ha-core smartthings component, refactored to mirror the authentication flow of the android mobile app, requiring a browser extension to capture the sasdk:// redirect uri and finish authorization.
This login method can't subscribe to push updates, so the integration now polls the REST api every 30s.
Important
A browser extension is required to successfully authenticate with SmartThings (capture the sasdk:// URI). Do not skip this step!
SmartThings mobile uses a Samsung account login flow that blocks automated logins. Authentication requires a browser-based OAuth flow using a browser extension to capture the mobile app redirect URI.
The chrome extension is tied to the folder location on your computer and may disappear if you move the folder.
- Download the project
- Extract the zip file and locate
./chrome-extension/ - Open Google Chrome and navigate to
chrome://extensions/or Edgeedge://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select the extracted
chrome-extensionfolder - Start the automated authentication flow in HA by the integration
- If your browser still has a Samsung login cookie, the login is skipped and no redirect URI is produced to capture — open the extension pop-up, reset Samsung auth to delete existing cookies, return to HA, and click
open websiteto continue authentication
- If your browser still has a Samsung login cookie, the login is skipped and no redirect URI is produced to capture — open the extension pop-up, reset Samsung auth to delete existing cookies, return to HA, and click
- After logging in to Samsung the redirect should be captured and re-written to my-homeassistant.io
- Proceed with the
Link to Home Assistantprocess
- A tab loads a 500 internal server error but authentication proceeds in HA
Thanks to joostlek for handling the integration thus far