Must be the Devices host (devices.geekforcedeveloper.com), not this customer portal. Only HTTP 200 = success.
Provisioning returns the real host (10002.geekforcedeveloper.com). Leave override blank on live so the board reports to that host. For local testing only, put e.g. http://127.0.0.1:8002.
Provisioning status
1
Announce to devices.POST /provision with MAC + customer #
2
Receive confighost, key, timezone, schedule
3
Store & switch to customer serverreport to the learned host
Learned config (stored in "NVS")
host
—
key
—
timezone
—
schedule
—
Station board—
CORS: this page calls your servers from a browser. Both the provisioning server AND the customer
server must send CORS headers or requests fail. Real boards don't need this — only this browser page does.
2 · Runtime (after provisioning) idle
These fire automatically like the real device (heartbeat + temp every cycle), and you can trigger them manually. Buttons on the board send alerts.
Auto-run (like a real device's 15-min cycle, sped up)
Node-RED command simulation (cloud → device)
Real lamps follow GET /{MAC}-andonstatus from the customer portal (Ack/Clear on the ANDON dashboard). Local Ack buttons still work for offline testing.