Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

BenjaminDannegard
Copy link
Contributor

What This PR Changes

  • Added new device provisioning documentation

Contribution Guidelines

Copy link
Contributor

@jhansson-ard jhansson-ard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some updates on sentences and formatting 🙏🏼

Copy link

github-actions bot commented Jun 27, 2025

Preview Deployment

🚀 Preview this PR: https://68c29c4df203cd14611f11cd--docs-content.netlify.app
📍 Commit SHA: 487f8d4

Copy link
Contributor

@jhansson-ard jhansson-ard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some comments @BenjaminDannegard 🙏🏼

Copy link
Contributor

@fabik111 fabik111 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Throughout the document we always talk about wifi credentials, but with provisioning 2.0 all network types are supported if the board compatible with provisioning 2.0 supports them.

For example with the Portenta H7 are supported also the Ethernet, CAT-M1 and Cellular connectivities. Opta supports both WiFi and Ethernet.
So, via BLE is possible to configure all these connectivity types


Here are the boards that are compatible with Bluetooth provisioning via a Bluetooth connection:

- [Arduino UNO R4 WiFi](https://docs.arduino.cc/hardware/uno-r4-wifi/) (Wi-Fi firmware version 0.6.0 or later required)
Copy link
Contributor

@fabik111 fabik111 Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the Arduino Uno R4 the only listed because it's the only currently produced from factory with the new Provisioning sketch 2.0 installed?

Keep in mind that in the future also the other boards (Opta, Portenta H7, Giga, Nicla Vision....) will be produced in this way.

At that point what will differentiate a board that can be provisioned via BLE or not is whether there is a pulsating LED after the boot.
So the user can easily recognize if he can (or not) have the provisioning via BLE by the pulsing LED.
The pulsing LED can be

  • blue led if the board has an RGB led
  • the LED_BUILTIN in case the board doesn't have an RGB led


![Board connected to the cloud](assets/succesfull-connection-with-usb.png)

You will now be taken to the device page. Here you can see the details of the board, change the name, attach it to a thing and change the network configuration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No! After the click on "continue" the user will be asked to insert the network credentials as using BLE. It's the same flow as via BLE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants