Added missing $ in topic for MQTT PUBLISH messages #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While until now the Azure IoT Hub Gateway v1 accepted this typo (the missing dollar sign), the Gateway v2 will simply close the MQTT connection when receiving a topic without the
$beforerid. Microsoft is gradually upgrading existing IoT Hubs to Gateway v2 and there seems to be nothing the customer can do about it. Whether the IoT Hub is already upgraded to Gateway v2 can be seen in the "Properties" tab of the IoT Hub. If it was already upgraded, the "Features" will containGWV2. We are in contact with Microsoft but don't know yet if they will continue to support the broken topic this library is currently sending.Therefore I think it's important this will be fixed as soon as possible, as devices running the current library version will not be able to connect once the IoT Hub is updated to v2.