Firmware should treat Realer as a cloud control plane that can be temporarily unavailable, reject invalid data, or stop accepting cloud operations when the subscription or credentials are no longer active.
- For rejected HTTPS results, use response codes and field semantics to decide whether to retry, ignore, reconcile, or enter local safe behavior.
- For authentication and MQTT runtime failures, renew OAuth tokens and short-lived MQTT credentials through the flows documented in authentication and MQTT flow.
- For subscription or entitlement loss, expect cloud API access to stop and follow the subscription ending guide.
The API failure handling guide covers firmware behavior. Use API Docs for exact request, payload, and response contracts.