◆ azure_iot_hub_evt_type

#include <include/net/azure_iot_hub.h>

Azure IoT Hub notification events used to notify the user.

Enumerator
AZURE_IOT_HUB_EVT_CONNECTING	Connecting to Azure IoT Hub. The event has no associated data.
AZURE_IOT_HUB_EVT_CONNECTED	Connected to Azure IoT Hub. The event has no associated data.
AZURE_IOT_HUB_EVT_CONNECTION_FAILED	Connection attempt failed. The reported error code from the IoT Hub is available in the `data.err` member in the event structure. The error codes correspond to return codes in MQTT CONNACK messages.
AZURE_IOT_HUB_EVT_READY	Azure IoT Hub connection established and ready to receive data. The event has no associated data.
AZURE_IOT_HUB_EVT_DISCONNECTED	Disconnected from Azure IoT Hub. The event has no associated data.
AZURE_IOT_HUB_EVT_DATA_RECEIVED	Device-bound data received from Azure IoT Hub. The event contains the received data in the `data.msg` member, and the topic it was received on in the `topic` member, including message properties in `topic.properties`.
AZURE_IOT_HUB_EVT_PUBACK	Acknowledgment for data sent to Azure IoT Hub. The acknowledged message ID is in `data.message_id`.
AZURE_IOT_HUB_EVT_PINGRESP	Acknowledgment for ping request message sent to Azure IoT Hub. The event has no associated data.
AZURE_IOT_HUB_EVT_TWIN_RECEIVED	Device twin has been received. The event contains the received data in the `data.msg` member, and the topic it was received on in the `topic` member, including message properties in `topic.properties`.
AZURE_IOT_HUB_EVT_TWIN_DESIRED_RECEIVED	Device twin has received a desired property update. The event contains the received data in the `data.msg` member, and the topic it was received on in the `topic` member, including message properties in `topic.properties`.
AZURE_IOT_HUB_EVT_TWIN_RESULT_SUCCESS	Device twin update successful. The request ID and status are contained in the data.result member of the event structure. The received payload is in the `data.msg` member, and the topic it was received on is in the `topic` member.
AZURE_IOT_HUB_EVT_TWIN_RESULT_FAIL	Device twin update failed. The request ID and status are contained in the `data.result` member of the event structure.
AZURE_IOT_HUB_EVT_DIRECT_METHOD	Direct method invoked from the cloud side. The event contains the method data in the `data.method` member, and the topic it was received on in the `topic` member. Note After a direct method has been executed, azure_iot_hub_method_respond must be called to report back the result of the method invocation.
AZURE_IOT_HUB_EVT_FOTA_START	FOTA download starting. The event has no associated data.
AZURE_IOT_HUB_EVT_FOTA_DONE	FOTA update done, reboot required to apply update. The event has no associated data.
AZURE_IOT_HUB_EVT_FOTA_ERASE_PENDING	FOTA erase pending. On nRF9160-based devices this is typically caused by an active LTE connection preventing erase operation. The event has no associated data.
AZURE_IOT_HUB_EVT_FOTA_ERASE_DONE	FOTA erase done. The event has no associated data.
AZURE_IOT_HUB_EVT_FOTA_ERROR	FOTA failed. The event has no associated data.
AZURE_IOT_HUB_EVT_ERROR_MSG_SIZE	A received message is too large for the payload buffer and cannot be processed. The event has no associated data.
AZURE_IOT_HUB_EVT_ERROR	Internal library error. The event has no associated data.