I am facing the following issue with the new Blynk IoT. Please let me know if you have any suggestions.
If the WiFi credentials change, not able to update it to ESP8266 through the Blynk IoT app.
If the WiFi is not connected, how to control the microcontroller manually? Currently, I am calling the BlynkEdgent.run() only if the WiFi is connected. In this way, OTA is not working. So First I am uploading an example sketch to update the WiFi credentials, Then uploading the main code.
When the microcontroller reconnects with Blynk Server after WiFi comes back, it restarts.
Please let me know if you have any solutions for these issues.
Thanks.
I hope the “OFFLINE AUTOMATION” will NOT be a part of pro n plus plans. But removing the timer input n timer widget was a huge bummer. It was a very basic things to have. As said earlier paying 5$ per device I have nothing to play with… REAL DISSAPPOINTMENT.
Offline automations will only be available in PRO plan. We might consider returning time input.
Also, Automations are under design review as we got a lot of feedback on this feature here and from commercial client. It will be WOW ! )
[Free plan story]
One fine morning we will be left with a single widget called ON button from which you can turn on the device… but not turn off. Turning off the device is only available for plus n pro models.
Which we can never taste so it doesnt matter if it is wow or terrible …
BLYNK is really starting to control people.
Is there still the ritual to keep the loop clean in 2.0 ?
And
Connection check to reconnect ?
What if the wifi or the internet is down ?
Will the code still works or the whole device freezes ?
I am going to do something strange here… and “defend” Blynk on (this particular) issue…
Having a clean structured loop with timed functions and such is not about Blynk’s limitations.
Not doing so is an issue that affects all connected services, when running on legacy devices with legacy Arduino style coding structure: EG. Fast sequential code, punctuated with erupt delays… AKA the “stop and go traffic jam” of the microcontroller world. This method of programming carried on for years as IoT was just a typo back then.
But now, unless you have much faster devices, preferably with WiFi running in some form of multitasking process (and even then), a clean loop with structured and timed functions is the new norm for all methods of DIY coded IoT.
Of course, Blynk 2.whateveritiscalledtoday may introduce all sorts of paid for automations that reduce the programming needs of the end user. Personally, I say good on them for the effort… it is just not my “make it, buy it, own it” DIY style.
That might be a good idea, thanks! Will share your idea with our financial department. They’ll love it.
As always, the code stays open-source, so you can implement any logic you want. You choose whether you want to spend your time on learning how to code and actual coding/debugging or save time by purchasing something that already works.
During last 6 years we only made it easier to control devices, but I appreciate your humor.
yes, it’s called good C++ programming
You can do it with firmware API
You can check the connections status using firmware API and code whatever you need
…
