Azure-docs: MXChip Firmware does not allow IoT connection string

[joslat]

Hi,
the link to https://aka.ms/devkit/prod/getstarted/latest gets a non-working Firmware (devkit-getstarted-1.6.5.bin) that does not allow to add the Connection string.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0cf9b53c-0438-f23c-fd2e-d57481d57e85
• Version Independent ID: f01afd66-d093-ac44-2b20-df225530b39e
• Content: Connect IoT DevKit AZ3166 to an Azure IoT Hub
• Content Source: articles/iot-hub/iot-hub-arduino-iot-devkit-az3166-get-started.md
• Service: iot-hub
• GitHub Login: @wesmc7777
• Microsoft Alias: wesmc

[Alberto-Vega]

Hi @joslat Thanks for reaching out. Can you please describe the issue you are seeing in more detail so I can try to reproduce this issue?

[sewalshmsft]

I just ran into this also. The page only a drop down to select SSID or manually enter one, then enter SSID password. There's no field to enter the connection string.

[joslat]

yes, exactly this.
To reproduce:

1. get the MXchip
2. Drop the 1.6.5 binary on it
3. Trigger the update. (or follow the steps on the "Send DevKit telemetry" section at https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-hub/iot-hub-arduino-iot-devkit-az3166-get-started.md
4. get to point 6.
   
   You will not see the "IoT device connection string box".

That's it.

[asergaz]

@joslat @dootdootbeep can you try an older version of the firmware?

https://microsoft.github.io/azure-iot-developer-kit/versions/

Thanks

[joslat]

Thanks, but I do not need it.
My intention was to try to help you notifying of this issue to so you can fix the HOL either adding that back to the fw or changing the instructions.
If you continue the tutorial-HOL you end up setting the connection string through VS Code.

[liydu]

@joslat , thanks for pointing it out. We found it's an regression issue for the pre-built firmware and will get a hot fix today.

[liydu]

We have got it fixed now and the pre-built firmware should have the connection string input box. Please help verify and close the issue if it works properly.

[Alberto-Vega]

@dootdootbeep Can you please confirm that your issue has been resolved? Please see previous comments and retry

[JonathanAnd]

I just downloaded the latest firmware and it is now fixed

[joslat]

I guess this settles it. Thanks!

[bhavinbdoshi]

I just tried this and I still don't see ConnectionString. I tried both https://aka.ms/devkit/prod/getstarted/latest and https://github.com/microsoft/devkit-sdk/releases/download/1.6.5-release/devkit-firmware-1.6.5.bin

[lokijota]

I have the same issue, the IoT Device Connection string is not there.

I logged into the serial interface and ran version:

version

DevKitSDK version: 1.6.5
Mico version: 31620002.049
mbed-os version: 5.4.3
mbed TLS version: 2.15.0
WIFI version: wl0: Sep 10 2014 11:28:46 version 5.90.230.10

I also tried setting the Iot Hub device connection string on the command line over the serial interface by running:

set_az_iothub "HostName=etc..."
(I also tried without the commas)

But when the device reboots I always get:

Failed to send telemetry data: 400.

Other devices I have in my IoT Hub work fine and send telemetry. I am SURE the connection string is correct, by the way.

[reallybigcatheter]

Yep, same issue here.

Because this issue is marked closed, I doubt anyone will see it. Frustrating to be stopped dead in your tracks before you can even get any telemetry.

[jacqueskang]

Same issue today with my device: "Failed to send telemetry data: 400."

version

DevKitSDK version: 2.0.0
Mico version: 31620002.049
mbed-os version: 5.4.3
mbed TLS version: 2.15.0
WIFI version: wl0: Sep 10 2014 11:28:46 version 5.90.230.10