Web console > Templates > + New Template > fill in the details > Save
then
Web Console > Search (spyglass icon) > + New Device > From Template > select the template created above > add device name > Save
Open mobile app and the device you just created will be visible, but showing as offline.
You can then go back and edit the template to add/edit datastreams etc and when you save these changes they will immediately be updated in the web console device view, and the mobile app.
When you want to upload the sketch to the board and get the device online then you copy the three lines of Firmware Configuration code from the Template screen and paste them into your sketch along with your static WiFi credentials. When the board is powered up and teg serial monitor shows it as having connected to Blynk then the device will appear as online in the app and web console.
If you need to use Edgent then the process is different. The first part is the same, but then the two lines of Firmware Configuration code from the Template screen are copied and pasted into your Edgent sketch and the sketch uploaded to the board. When the board is powered-up and the LED is flashing rapidly then you open the app and hit + New Device and the board is provisioned with WiFi credentials and a dynamic Auth Token and it will then be online.
Once again, you can go and update the datastreams in the Template at any time and these will be reflected in the device view of the web console and the device in the mobile app.
With either process, you can then create your web and/or mobile dashboards with the widgets you require attached to the datastreams you’ve created.
Widgets attached to the same datastream in the web and mobile dashboards will show the same data, and if they are input/action type widgets then either widget will change the value of the datastream which will then be reflected in the other dashboard. But, for example, adding an LED widget to the mobile dashboard does not also add the same LED widget to the web dashboard. The two dashboard layouts are independent of each other.
As you can see, creating the TEMPLATE is always teg first step and always a manual process (unless you use the QuickStart wizard).
DEVICES are created from TEMPLATES, either manually - as described in the first option - or automatically within the app if using Edgent.
That’s why…
makes no sense in terms of the Blynk process. Templates can’t be created by devices, devices are based on templates and the template has to come first and the template creation is done manually.
Pete.