Samsung SmartThings Devices

Are you signing in to the SmartThings CLI on one device, but completing the authentication on another device? If so, that’s likely the problem. The SmartThings CLI assumes you’re using the same device for both steps. After you log in, it redirects to localhost. If you authenticate on a different device, the redirect goes to the wrong machine, and the login won’t complete. You have two options: 1. ⁠Use the same device for running the CLI and completing the login. (Recommended) 2. ⁠Or manually change the localhost redirect URL to the IP address of the machine running the SmartThings CLI. Tip: …

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

… with no way to audit this, would you? This is what they are claiming can happen, and more, keep reading, This only affects tokens generated that control SmartThings devices, not integrations that allow SmartThings to control other devices. The blog post clearly states that this change affects newly generated PATs moving forward and all existing integrations will remain working. They won't be invalidating old PAT's until they've created a path for developers and users to migrate to the OAuth2 method of authenticating with the platform. They claim that PATs were never intended to be used …

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.