Claim and onboard issues
Problems claiming a gateway after browser flash or SoftAP setup.
Claim returns “Invalid device credentials”
Usually the gateway has not registered with the cloud yet (Wi‑Fi just joined). The browser flasher normally handles this race automatically.
- Keep the gateway powered and on the target Wi‑Fi.
- Retry claim — the onboard form polls for about 90 seconds.
- If it still fails, open a serial monitor at 115200 and confirm the gateway ID / claim code match the form.
- Confirm production firmware is
0.1.4or newer (claim-code path).
Wrong claim code or typo returns a 400 error — double-check the code from the label or serial log when using the manual fallback.
Claim blocked: verify your email
If production has email verification enabled, claim returns 403 until the address is verified.
- Open the verification link from the registration email.
- Sign in again (prefer the same browser that started onboard).
- Return to
/onboard?device=…&code=…or Gateways → Claim.
Gateway already claimed (409)
The gateway is bound to another account. Use factory reset on the gateway (long BOOT hold) only if you own the hardware, then claim again from the intended account.
Automatic setup cannot add the gateway
The recommended flasher requires login before it starts and adds the gateway automatically after Wi‑Fi succeeds.
If automatic binding times out:
- Keep the gateway powered and restart it so cloud registration retries immediately.
- Select Try adding again in the flasher.
- As a fallback, enter the gateway ID + claim code manually at jkbmsr.com/devices/claim.
SoftAP works but claim fails
Captive portal only configures Wi‑Fi. The gateway must still reach api.jkbmsr.com on the customer network (outbound HTTPS). Captive portals that block unknown hosts will prevent register/claim.