📄️ Device Gateway in AirNgin
Device Gateway is for products that manage one or more Child Devices on a local network or bus while only the Physical Gateway connects to the AirNgin cloud.
📄️ Gateway Architecture and Identity
Identities
📄️ Gateway Provisioning and Cloud Connection
A Physical Gateway is provisioned as a real AirNgin Device. The server issues the complete credential set, which firmware persists and reuses.
📄️ Gateway MQTT Topic Reference
This is the public Gateway v1 topic reference. Direct Device topics are not used for Gateway-mediated Children.
📄️ Gateway Security and AES
Security principal
📄️ Child Onboarding
Onboarding turns a local candidate into an authorized, associated AirNgin Child.
📄️ Drivers, Protocols, and Compatibility
Keep the three layers separate
📄️ Child Discovery
Discovery is an optional Driver capability. Some Drivers scan; others support manual configuration only.
📄️ Commands and Execution ACK
Downlink path
📄️ Shadow, Telemetry, and Events
Keep these three concepts separate.
📄️ Hybrid MQTT + HTTP Sync
Gateway v1 uses a hybrid architecture:
📄️ HTML Live MQTT for Onboarding and Settings
Interactive HTML loaded inside the mobile app may receive a temporary MQTT session for live two-way communication with the Gateway.
📄️ Gateway Analyzer
Gateway Analyzer is an optional uplink-only layer.
📄️ Offline-first Runtime
A Gateway must not become unusable just because the cloud connection is temporarily unavailable.
📄️ Backend Gateway ↔ Child Association
Association authority is server-side. Firmware consumes only the effective current state through onboarding/sync.
📄️ Gateway v1 Implementation Checklist
Cloud identity
📄️ Gateway Troubleshooting
Gateway MQTT does not connect