What does the GWV2 feature of the IoT Hub mean?

Vladimir Shurakov 21

Hi,

We have an old IoT Hub configured by a colleague which is no longer with our company.
ARM template has the following property: "features": "GWV2". Devices can connect to it, all good.
Recently we have created another IoT Hub for production and have not specified this feature for it, because have no idea what does it mean.
But devices cannot connect to a new Hub.
Could you please explain what this feature means?

Thank you in advance.

AshokPeddakotla-MSFT 33,756 Reputation points

2022-12-02T10:56:42.71+00:00

@Vladimir Shurakov Welcome to Microsoft Q&A forum!

Can you share more details so we can help you accordingly?

ARM template has the following property: "features": "GWV2". Devices can connect to it, all good.

Where exactly this has been defined? Can you share the sample ARM template without any PII information for better understanding?

Recently we have created another IoT Hub for production and have not specified this feature for it, because have no idea what does it mean.
But devices cannot connect to a new Hub.

How are you connecting devices? Using ARM templates? Did you follow any reference document for steps?
Vladimir Shurakov 21 Reputation points

2022-12-02T11:20:51.997+00:00

Hello @AshokPeddakotla-MSFT ,

In deed we don't have the ARM template the old IoT Hub was created with.
Probably, it's been created manually.
But it has value "GWV2" in Features property for sure (see screenshot).

We have tried to deploy production IoT Hub with this value specified in the ARM template, but it did not take effect (ARM template deployed without issues).

My question is about to understand the meaning of this GWV2 value, and then we could decide if it affects the connection or not.
So if you could give us a description of this value it would be great.
Thank you.

Accepted answer

QuantumCache 20,266 Reputation points

2022-12-05T03:16:54.257+00:00

Hello @Vladimir Shurakov ,

Regarding the initial query: Features : GWv2

GWv2 is our shorthand for Gateway V2. We internally track what Gateway version a customer is on and are working to migrate all hubs from GWv1 to GWv2. This is not something the customer controls.

We are working with the Product Team to check if changes to the ARM template affect the GW migration or not, please stay tuned on this thread.

Updated: 12-04-2022: Response from Engineering team

That property can be ignored and should not affect ARM templates, this is only an indication of which version of the Gateway that hub has provisioned. It cannot be changed by the customers.

If the response is helpful, please click "Accept Answer" and upvote it. So that we can close this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

chbeier 1,866 Reputation points

2022-12-02T12:06:36.51+00:00

Hello @Vladimir Shurakov ,
I believe the feature "GWV2" is for internal service purposes only and it should not be required in your ARM template to deploy a working IoT Hub instance.

Have you imported the device registry for your existing devices in the new IoT Hub instance (or setup DPS) already?
If you create a new (test) device in the new IoT Hub instance, does it connect properly?

If the new device connects, ensure your existing devices use the right connection string (URL, credentials, etc) or DPS is setup correctly.
If possible, inspect a device log on the reported connection error. Feel free to share it here.

In case a new device cannot connect as well, I would recommend opening a support ticket.

----------

If your question was answered, please use "Accept Answer". If not, please share more details so we can try to help you.
Please sign in to rate this answer.
Vladimir Shurakov 21 Reputation points

2022-12-02T12:53:52.09+00:00

Hello @chbeier ,

Thanks for your reply.

We use brand new devices to connect to empty DPS.
They are with Azure Sphere MCU on board and have been claimed into Sphere Catalog recently.
Enrollment group is created in DPS and has verified CA certificate from that Catalog.
The device connects to DPS and then it is enrolled in the IoT Hub.
Then it tries to connect to the IoT Hub and we see connections in the logs, but for some reason it is disconnected with error (see screenshot).
Configuration of both IoT Hubs are the same except this feature GWV2, so we thought this could be the reason.
If that feature cannot cause such issue, then OK, we will check other parts of equation.

Thank you.

chbeier 1,866 Reputation points

2022-12-02T13:02:05.49+00:00

I recommend testing the connection with a simulated device, as mentioned in the troubleshooting section of the https://aka.ms/iothub404104.
This should provide additional insights into the error and device behavior.

Vladimir Shurakov 21 Reputation points

2022-12-02T13:15:23.613+00:00

Ok, we will try, but it is a bit tricky to emulate Sphere Device.
Any way thank you!
Now we know GWV2 is for internal use only ).

Anton Bastiuchenko 0 Reputation points

2023-06-30T04:39:15.0166667+00:00

Hello,

If I use MQTT protocol and .NET SDK on device side, my c2d messages are rejected because of my Azure IoT Hub instance doesn't have this feature GWv2. I described this issue here - https://github.com/MicrosoftDocs/azure-docs/issues/98930#issuecomment-1596319291

I want to understand is it a bug in Azure IoT Hub or in Azure IoT SDK .NET or in MQTTNet (that is used in Azure IoT .NET SDK).

Is it possible to update Azure IoT Hub Features to GWV2 somehow from my side?

Should I share with you any other information to shed light on the situation? Maybe somehow export schema of IoT Hub and share with you?

Why newly created Azure IoT Hub still use GWv1 if you are already upgrading all existing Azure IoT Hub to GWv2 as I understood?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

What does the GWV2 feature of the IoT Hub mean?

1 additional answer

Your answer