Did you know that over 40% users fail when connecting IoT devices to the internet? 

This is one of the biggest IoT issues because so many pieces of software should work seamlessly together. 

We have streamlined a process for connecting your devices to the Internet (also called "device provisioning") so that your customers can get products online with no hassle.

Blynk.Inject™️ is a workflow for device provisioning that includes Firmware API and a Mobile Connection Wizard to simplify life for your customers and for you, as a manufacturer or developer.

Blynk.Inject™️ was tested extensively in various environments and with different audiences. It currently provides the most reliable connectivity process combined with one of the best user experiences on the market.

Every app published with Blynk includes a Blynk.Inject™ workflow.

---

What is Blynk.Inject™️ and how it helps with device provisioning?

By now you should know, that every device on Blynk IOT platform needs to have a unique Auth Token

But what if you have thousands of products? How can you provide the Auth Token to every product? How your customers will connect the device to Internet after they unbox it and power it on for the first time.
 
Device provisioning is a process of passing a set of data to the hardware that will be used to connect it to the Internet (and authenticate it in Blynk Cloud). This data may include WiFi network credentials (SSID and password), Auth Token, email address of the user and other.


From hardware standpoint device provisioning process includes 2 steps:

  1. Connecting your product to the Internet using the available connectivity on board (WiFi, Ethernet, etc)
  2. Authenticating your product in Blynk Cloud with Auth Token

Depending on the hardware and connectivity used in your product, there are two types of provisioning:

    • Dynamic Auth Token Provisioning
    • Static Auth Token Provisioning

Dynamic Auth Token Provisioning

 
This type is used for devices that connect to the Internet over WiFi and can act as an Access Point (AP). ESP8266, ESP32, NodeMCU, Blynk SparkFun are examples of such hardware.

As a manufacturer you don't need to provide Auth Token to every device before it's sent to the client. Blynk.Inject™ will get your device connected to customer's  WiFi network, register it in the Blynk Cloud and assign this customer as the owner of this device  

👉 Read more about how Dynamic Auth Token Provisioning works

Static Auth Token Provisioning

This type is used for devices that connect to the Internet over Ethernet, Cellular (GPRS, 2G, 3G, 4G, LTE), and others.

As a manufacturer you would need to provide Auth Token to every device before getting it to the customer.

👉 Read more about how Static Auth Token Provisioning works

---

If you have any questions - contact us or post to our forum.

Did this answer your question?