IoT Edge Runtime Response 406: Device Offline or Not Sending Status Reports when Configured with Device Provisioning Service (DPS)

28711978 0

I am using a pre-built template to deploy a Linux machine with the IoT Edge runtime as an edge device. Initially, I successfully added the SimulatedTemperatureSensor module and received a response of "200 OK" from the IoT Edge runtime.

However, when I configured it for deployment using the Device Provisioning Service (DPS), I encountered an issue. The IoT Edge runtime now responds with "406 - The device is offline or not sending status reports."

Could you please help me understand why I am receiving this response and how I can resolve it?

Screenshot from 2023-05-24 12-03-55

AshokPeddakotla-MSFT 27,311 Reputation points

2023-05-24T07:50:21.3333333+00:00
95603302 Greetings!

When you configure an IoT Edge device with the Device Provisioning Service (DPS), the device is required to send status reports to the IoT Edge runtime to confirm that it is online and ready to receive deployment updates. If the device is not sending status reports, the IoT Edge runtime will respond with a "406 - The device is offline or not sending status reports" error.

Could you please help me understand why I am receiving this response and how I can resolve it?

Please check the connection string for the device in the DPS enrollment. Make sure that it is correct and that it matches the connection string in the IoT Edge runtime.

Check the logs for the IoT Edge runtime to see if there are any errors or warnings related to the device. You can use the following command to view the logs: sudo iotedge logs <module name>

Replace <module name> with the name of the module that is failing to send status reports.

Check the firewall settings on the device to make sure that it is not blocking traffic to the IoT Edge runtime.

Check the network connectivity between the device and the IoT Edge runtime. Make sure that the device is able to connect to the IoT Edge runtime and that there are no network issues.

Please check Common issues and resolutions for Azure IoT Edge. Use this article to find steps to resolve common issues that you may experience when deploying IoT Edge solutions.

If you need to learn how to find logs and errors from your IoT Edge device, see Troubleshoot your IoT Edge device.

You can also refer to the IoT Edge agent and the error codes.

Do let us know if that helps or have any further queries.
28711978 0 Reputation points

2023-05-24T10:28:29.39+00:00
Greetings, Ashok

Thank you for your prompt response. I attempted the solution you provided and encountered an error.

**sudo iotedge logs <module name>** Replace `<module name>` with the name of the module that is failing to send status reports.

ERROR -

This issue arose specifically after I included DPS configurations in the config.toml file. Prior to that, everything was functioning correctly.
28711978 0 Reputation points

2023-05-24T10:32:23.5266667+00:00

.....
AshokPeddakotla-MSFT 27,311 Reputation points

2023-05-25T08:22:56.8433333+00:00

28711978 Thanks for sharing the additional details. For a deeper investigation and immediate assistance on this issue, please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, could you please send an email to azcommunity@microsoft.com with the below details, so that we can work closely on this matter.

Thread URL: Link to this thread.

Azure Subscription ID:

Email Subject : Attn Ashok
AshokPeddakotla-MSFT 27,311 Reputation points

2023-05-29T15:36:48.3733333+00:00

28711978 Did you get a chance to see suggestion from Sander? If that is not helping, as suggested please file a support request or send us an email for further assistance.

1 answer

Sander van de Velde 28,311 Reputation points MVP

2023-05-24T20:21:04.1866667+00:00
Hello @28711978,

it seems the config.toml file on your edge device is not configured correctly for DPS usage.

Please first roll back to the version where you used the test connection string.

Once you can confirm it runs as expected, modify the config.toml file again.

If you use DPS with a symmetric key, your configuration will look like this:

[provisioning] source = "dps" global_endpoint = "https://global.azure-devices-provisioning.net" id_scope = "<DPS-ID-SCOPE>" [provisioning.attestation] method = "symmetric_key" registration_id = "<my-device-registration-id>" symmetric_key = { value = "<Device symmetric key>" } # inline key (base64)

Check the documentation for more variations like provisioning with X.509 certificates or provisioning with TPM.

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.
Please sign in to rate this answer.
28711978 0 Reputation points

2023-05-25T07:58:32.37+00:00

Hello @Sander van de Velde ,

I did this configurations in config.toml file.

[MODERATED: image removed to protect client secrets]

Then used this command to apply the changes.

sudo iotedge config apply

Still getting the same error

Sander van de Velde 28,311 Reputation points MVP

2023-05-25T13:14:03.34+00:00

Hello 28711978,

Note: your post is moderated. The image was removed to protect device secrets.

If the registration name and symmetric key are from the DPS (individual enrollment), this seems ok.

Is IoT Edge enabled in your enrollment?

Please first check the configuration with the 'simple' IoT hub registration/deviceid/symmetric key to be sure your initial solution works.

From there, only change the DPS connection. To make the test complete, first, delete the IoT Hub registration

Warning: you will lose the module registrations!

You will notice, after the assignment of the enrollment, the device should be registered again in the IoT Hub.

Note: Your modules need to be added again to the new registration. This step could be automated using layered deployment but that is out of scope for your test.
Sign in to comment