Skip to content

Commit b945898

Browse files
Learn Editor: Update troubleshoot-device-update.md
1 parent d4deb75 commit b945898

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/iot-hub-device-update/troubleshoot-device-update.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ This document lists some common questions and issues Device Update users have re
1515

1616
## <a name="import"></a>Importing updates
1717

18+
### Q: I’ve imported an update successfully, but it's not showing as available for me to deploy to devices which it should be compatible with
19+
20+
Double-check that your import manifest .json file doesn’t have any accidental errors, especially in the [Compatibility object](/azure/iot-hub-device-update/import-schema) values. The compatibility properties in the import manifest must match exactly with the properties reported by your devices. This is to ensure that the right updates are always only sent to the right devices. For example, if there's a typographical error in the import manifest that causes a compatibility property to have a missing, transposed or extra character compared to what’s reported by a device, the Device Update for IoT Hub service won’t be able to match the update to that device. If you've already imported an update, you can quickly check for issues with compatibility properties by clicking the "Details" link for that update and then clicking “Additional details” in the right-hand flyout menu. From there, you can view the import manifest JSON content for that update and identify any potential errors.
21+
1822
### Q: I'm having trouble connecting my Device Update instance to my IoT Hub instance
1923

2024
Please ensure your IoT Hub message routes are configured correctly, as per the [Device Update resources](./device-update-resources.md) documentation.

0 commit comments

Comments
 (0)