Try disabling 5GHz temporarily in your router settings to force a 2.4GHz connection.
💡 If you see this error immediately after a power outage, your router likely assigned a new IP address that the device doesn't recognize yet. Re-syncing the device through its official app usually solves this instantly.
🟡 Moderate User Impact: Session-blocking but recoverable via re-authentication. Permanent Fix: Requires alignment of token lifecycle management (server-side) and proper client-side token refresh logic. eror code 20000107
Check your mobile app store for any pending updates for the control app.
Ensure your phone is on the same network as the device during the setup process. Advanced Fixes Try disabling 5GHz temporarily in your router settings
| Cause | Description | |-------|-------------| | | The security token embedded in a form or request header has timed out, but the session cookie remains alive. | | Session fixation or mismatch | A user ID or role claim in the token does not match the current session’s principal. | | Token replay detected | The same nonce or token was used more than once (strict idempotency enforcement). | | Clock skew | Server and client system times differ by more than the allowed tolerance (common in containerized or VM environments). | | Corrupted middleware cache | In clustered deployments, the token validation cache (e.g., Redis, Memcached) lost the reference to the original token. |
: Ensure you are using a high-quality USB 2.0 cable. Avoid using long USB extensions or front-panel USB hubs, which can cause signal degradation. Ensure your phone is on the same network
: Using a non-standard or damaged USB cable can drop the connection mid-process. How to Fix Error 20000107