MicrosoftDocs / azure-sphere-issues

Creative Commons Attribution 4.0 International
11 stars 8 forks source link

Can't connect using "direct connection" #269

Closed ericmitt closed 3 years ago

ericmitt commented 3 years ago

I followed the steps in the article but impossible to connect my devices via direct connection. I gote the message: Azure IoT connection status: IOTHUB_CLIENT_CONNECTION_NO_NETWORK Azure IoT connection status: IOTHUB_CLIENT_CONNECTION_BAD_CREDENTIAL Azure IoT connection status: IOTHUB_CLIENT_CONNECTION_NO_NETWORK Azure IoT connection status: IOTHUB_CLIENT_CONNECTION_BAD_CREDENTIAL

I redo all the steps twice but same result :-(

So I changed gears and tried to follow the steps with DPS, worked fine.

Perhaps we need to revisit and validate the steps for "direct connection"

To reproduce, follow the steps in the article for "direct connection"

ericmitt commented 3 years ago

In the DPS approach, can I control the name of the device (it appear with a very long Unique ID) ?

ericmitt commented 3 years ago

To be able to see telemetry in iotexploer or from Azure CLI, I have to create a new consumergroup.... Why ?

HarshitaSingh-MSFT commented 3 years ago

Hello @ericmitt , thank you for reaching out to us! Could you please share the link of the MS Doc you are referring to here?

HarshitaSingh-MSFT commented 3 years ago

Just checking in to see if you could provide an associated doc link for this issue.

HarshitaSingh-MSFT commented 3 years ago

Just checking in to see if you could provide an associated doc link for this issue.

HarshitaSingh-MSFT commented 3 years ago

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.