Hi everyone,
I’m interested in using Blynk to control multiple boards running WLED… has that capability been reintroduced to the Blynk app?
From the WLED Developer here:
“This only works with the legacy Blynk app, for which new signups have been closed by the Blynk developer. WLED will either move to Blynk 2.0 or a different solution soon.”
Thank you
Next in que. Looks like WLED is something i’m fixing to use a lot. Would be nice to have an integration of sorts that actually works. It was there but got broken earlier. Can we fix it?
Looking at the WLED website linked above, it seems that the “Blynk integration” was merely a QR code to be scanned, and the instruction to add the Blynk Auth token into the WLED sync settings.
Blynk legacy Auth QR codes were a way to share a project with other uses. Scanning the QR code would create a clone of the project for the new users, without allowing access to the original authors personal Blynk project.
Blynk IoT doesn’t use QR codes in this way, and it no longer uses Projects. Instead it uses Templates and Devices, and datastreams and dashboards linked to templates.
The Legacy QR code would in effect simply recreate the legacy dashboard that had been created by the original author of the project. As Blynk IoT doesn’t have a way to share dashboard setups in this way (because it’s now a much more complex task of creating templates, datastreams, dashboards and devices) it’s not possible to share a clone of the dashboard setup with other users.
If someone knew what the dashboard setup created automatically by the QR code looked like, and how it worked in terms of virtual pins, then it would presumably be able to be recreated manually in Blynk IoT.
But, as there is now no way to share that setup easily, once all of this reverse engineering has been done, every user would need to follow a detailed set of instructions necessary to create the template, datastreams, dashboards widgets (including layout and which datastreams they linked to) and devices.
Presumably the original author of WLED haas looked into this and decided that it’s no longer an attractive proposition for potential Blynk users, as it’s now far more complex than simply scanning a QR code.
So, although it might be technically possible for you to create your own Blynk integration (provided you knew exactly what the original QR code created) its probably not worth the effort.
Pete.
Appreciate such an in-depth breakdown on how ways blynk treats templates. It totally explains the issue and where we stand with it right now. And frankly it’s restoring ease of use rather the template we are after. It feels like such a loss that these two wonderful platforms need a jump through a fire hoop and back to work together. Obviously WLed can be compiled from a arduino IDE sketch. And implementing Blynk at that point is doable, but WLed code spans across multiple files and can be extremely confusing for beginners to compile from scratch. Most users compiled and install WLed via ESP Web Tools never visiting the IDE. If presented with a Blynk Token at the point of SSID input can burn it in. But that’s for WLed team to consider. Alternatively Blynk has a wonderful tutorial section with a wizard to deploy a simple code and go from there. It can have a WLed deployment with there latest version fetched as one of the examples. Just thinking out loud…