Hi Fellow Blynkers.
I am running a data acquisition project successfully on ESP-WROOM-32 with Blynk Library version: 1.3.2.
The only problem I had to face is during network(WiFi) disconnection. The device keeps on trying to reconnect to the network and the consequence of this trial is very hot . My ESP draws more than the normal current (around 140 mA contrary to just 40mA during network connected phase) and hence heats up.
During this reconnection attempts many of the ‘data reading cycles’ miss. Which I cannot afford.
What I have tried so far is to make my device sleep for few moments and then try connecting the WiFi again untill it gets connected. This way I keep my ESP cool but thats not what I wish to do.
I have also tried to disable BlynkEdgent.run() instruction for few moments but the Blynk keeps on connecting to network.
Is there any way that I can keep Blynk sleep or disable for few moments?
Or anyone has some better solution.
Any suggestion or support would be highly appreciable.
If you used a regular Blynk sketch then you could use Blynk.config and Blynk.connect instead of Blynk.begin, and check for Blynk.connected in your void loop before executing Blynk.run.
You’d also need to manage your WiFi connection and have a timed process to attempt reconnections to WiFi and Blynk on a regular basis.
Since, the project is under development, so I am using the Free Version.
Once the project matures, definitely, I will go for a paid version.
Secondly, Mr. Pete, it would be helpful if you could explain me in your words whats the difference between Edgent and non-Edgent model? May be, I could switch from Edgent to simple version.
Ya I know about the cheapest plan and it is worthwhile but for those who are large scale manufacturers. For an entrepreneur who is at the very early stage of development or have a small fleet of devices this plan seems expensive.
One more point regarding the paid plans or billing is that for the manuf. of some under developed countries - countries having high currency conversion factors - these plans are, undoubtedly, not easy to adopt.
Talking about the Edgent Vs. Simple Blynk, me too have the same concept but don’t you think hard coding WiFi + SSID or through a QR Code is something outdated or relatively unattractive for the customers?
I would request the team to consider adding a feature for the user to DISABLE ‘WiFi Reconnection Attempts’. This is the same feature which Android OS in mobile phones implements (that what I have observed). And besides that, the ESP device of every user would have been facing the same issue of heating up.
The Blynk Edgent example is just that - an example.
If you’re planning on developing a commercial application based on Edgent then you should take time to unpick how the sketch works and make suitable changes to meet your specific needs.
You didn’t answer my question about how many devices your free subscription allows. If it’s 10 then you’ll be on one of the new free plans, which limits you to a total of 30,000 messages between your devices and Blynk each month, which may restrict your testing.
I have 10 devices on my free subscription. And I am aware that my max. limit of messages is 30k/month.
I have read the program but could not find a way to solve my problem.
I request again the experts like you or the experts from Blynk Developer’s team to help me find a way out.
The Blynk developers develop the Blynk app and server-side system, as well as assisting commercial (white label) subscribers get their products to market.
If community members read your post and wish to spend time assisting you, either for free or in return for payment, then I guess they’ll contact you.
But, I’d suggest that if you have plans to market a product then you should have enough C++ programming skills to be able to quickly fix issues and ship firmware patches, and to add additional features in future. If you’re replying on others to do that then it’s not likely to be a successful or profitable product.
Beefing-up your personal C++ coding skills should be your first priority in my opinion.
. My ESP draws more than the normal current (around 140 mA contrary to just 40mA during network connected phase) and hence heats up.