📄️ What is MQTT?
MQTT is a lightweight publish/subscribe messaging protocol widely used in IoT systems. Devices connect to an MQTT broker and exchange messages through named topics instead of opening a dedicated connection to every other component.
📄️ DeviceSerial and ClientId
Why DeviceSerial matters
📄️ Register a Device definition
Registering the product/device definition is the first step before connecting physical device instances to AirNgin.
📄️ File manager
AirNgin provides file management for assets that belong to your product documentation and HTML experiences.
📄️ Device Help HTML
Before creating a Help HTML page, you should be familiar with basic HTML and CSS.
📄️ Device control methods
AirNgin supports different control paths depending on the hardware capabilities of your product.
📄️ Complete the device definition
After creating a Device definition, complete its user-facing structure by defining Operation Groups, Operations, and Commands.
📄️ What is an Analyzer?
An Analyzer is the translation layer used by the Direct Device architecture when device-native data does not already match the AirNgin logical model.
📄️ Write a Direct Device Analyzer
Read the MQTT and device-connection sections before implementing an Analyzer. AirNgin also provides Lab tools that can help you test Analyzer behavior before final approval.
📄️ Provisioning a device for MQTT
A device must receive its AirNgin MQTT credentials before it can connect to the broker. The legacy SoftAP flow described here is one supported Direct Device provisioning method.
📄️ Publish data from a device to the AirNgin MQTT server
Read the provisioning/login guide before publishing.
📄️ Subscribe to AirNgin MQTT topics
Read the provisioning/login guide before subscribing.
📄️ Connect a Direct Device to the AirNgin MQTT server
MQTT is the primary cloud messaging transport for Direct Device integrations. Before implementing this page, read What is MQTT? and complete the provisioning/login flow.
📄️ Direct Device MQTT Topic Reference
This page lists the Direct Device topics in one place. These topics are not used for Gateway-mediated Children; see the Gateway MQTT reference for that architecture.
📄️ Debugger commands
Debugger commands are sent from Lab → Console → Send Debug Command.
📄️ Direct command exchange without an Analyzer
AirNgin supports a direct command model for products whose firmware already understands the AirNgin logical operation/command structure. In this mode, no Analyzer is required to translate between the mobile application and the device.
📄️ Producer test application
The AirNgin test application is designed for producers who need to validate a device before final approval.
📄️ Invite a user to the producer panel
A producer organization may need more than one person to access its panel. AirNgin lets you invite additional users and give them separate access rather than sharing one account.