Troubleshooting
The usual causes when a device, a dashboard or an automation does not do what you expect.
A device never reports
| What you see | Likely cause | Fix |
|---|---|---|
Serial log shows rc=5 | Wrong Device ID or access token | Copy both again from the device's Settings tab, with no extra spaces. |
Serial log shows rc=-2 | No internet, or the secure connection failed | Check the network. On cellular, check the APN, the signal and that the SIM has data. |
| Never joins WiFi | 5 GHz network, or a typo | ESP boards join 2.4 GHz networks only. Names and passwords are case-sensitive. |
A web request answers 401 | Wrong Device ID in the address, or wrong token | Check both; the answer is the same for either on purpose. |
It reports, but nothing shows
- The key has no datastream on the device's template. Add one with that exact key.
- The key differs from the datastream's key, for example
Temperatureinstead oftemperature. Keys match exactly and are lower case. - The widget is bound to a different datastream. Open the widget's settings.
Commands do not reach the device
run()is not called often enough. Call it on every pass ofloop()and replace longdelay()calls withmillis()timers.- No
onWritehandler covers that key. - The device is not reporting. Commands are delivered only while it is connected.
An update does not install
- The device was offline. It receives the newest update when it reconnects, within 24 hours.
- The board updates over USB only. Use Build firmware file and flash it.
- The new code removed
begin()orrun(). Restore them and flash over USB once.
An automation did not run
- The flow is switched off. Switch it on from the device's Automations tab or the Automations page.
- The trigger watches a datastream the device does not have. The editor marks that step; pick a real one.
- A step stopped it. Open Runs: the stopped step says why.
- Your credit reached zero. See Billing.
Still stuck?
MaxwellTrack AI can check a device's recent state for you: ask "why is the boiler sensor not reporting?". Or write to MaxwellTrack support with the device's ID and what you see.
Something unclear or out of date on this page? Tell support.
