That’s because there is no link of any type between Blynk Legacy and Blynk IoT (except the word Blynk).
I assume you mean “to the new app”?
There is no automatic migration process. You create the datastreams you need in the IoT web console, re-create the app in Blynk IoT and modify your sketch so that it’s compatible with Blynk IoT. You also need to upgrade your C++ library to version 1.0.1
As far as your RPI is concerned, it depends what programming language you used for that project.
I’ll update the sketch on the device (I’m using node JS)
a couple of question more:
do you know if the energy purchased in the Blynk Legacy app will be lost?
Pricing | Blynk IoT Platform here it’s written that on free plan device can be added for $4.99 per device but I haven’t seen the option, just the plan upgrade (also do you know if there is still the possibility to buy single feature e.g.: the styled button, instead of upgrading the plan)?
Yes. Blynk IoT doesn’t use energy.
You should have received an email giving you a 50% discount on the first year’s subscription to a Plus or Pro subscription…
Yes that’s an option. I think its done in the Billing section of the web console.
No, that’s not an option.
You’d need to check if the NodeJS library has been updates to be compatible with Blynk IoT.
Personally, I don’t think the RPI makes a good platform for Blynk projects. You’re much better off with a NodeMCU or ESP32 and C++
Indeed I haven’t received any email, actually I realized about the new app randomly on appStore. I’ll foollow up in that thread, thanks for letting me know!
You know everything : ) thanks!!! I’ve seen how to add a device, indeed Billing section in the console.
Probably not, indeed I’ve seen also on Blynk example browser there is no code in NodeJS. How can I check it?
Thanks a lot for the hint (as said I’m beginner and I might have choose the wrong HW), why you think it’s a good choice?
I choosed RPi as has more pin, ethernet port and I easily access from remote (even from mobile) with VNC to work on it if there is any bug. In general I tought it would have been more powerful and scalable (and actually I didn’t know ESP 32 when I started).
Rather early this year I’ve moves the distance sensor on ESP 32 nodeMCU and the implementation has been easier then when I did in RPi.
Happy to receive any feedback or advice on the choice
In my opinion drawbacks of the Pi as a client device are:
Expensive (not a issue if you’ve already bought one)
Requires a beefy power supply
Requires an operating system, and ongoing OS maintenance/updates
Slow to boot after a power interruption
The SD card will die at some point, probably when you least want it to
Can’t be programmed in C++ now that Wiring Pi is deprecated
Larger form factor.
More processing power, so great as a server.
I have several Pi’s but would never consider using them as client devices. As far as the Ethernet port is concerned, it should be a simple task to plug a wireless access point into your Ethernet wiring to give yourself a local wireless network so you can use an ESP device.
Probably download the latest library and try it. Backup your Pi’s SD card and see if you can get it working with the new version of Blynk.