Blynk 1.0 (legacy) retirement timeline announced!

Oh no ! Blynk 1 was so simple to use and there are features such as “bridge” which I will miss sorely for sending data to a different device. To me Blynk 2 still looks like a “work in progress” in many areas, example (the mobile dashboard and screens where customization is lacking).

4 Likes

@sri_c focusing on only one platform will mean more resources will be dedicated to the new features and overall improvement. It means moving forward faster with better quality.

1 Like

We dont ask for further development. Let it be as it is. Let the server run. 99% of us will be happy to be on the old platform. It was such a breeze to setup virtual pins n stuff n much much more.

Today without a computer one cannot get started with. (Create template, datastream etc etc)

Viewing the console on mobile is definitely a bad experience for me.

9 Likes

I think the issue is not so much not having a server anymore. Because with a Raspberry you can make one (at least I think you can). The problem is that with the IOS/Android updates in a short time the App will no longer work.

4 Likes

It is interesting. Can you give a little more details on how it works with ESP?

1 Like

Yes, you can set-up a local Legacy server running on a Pi or Windows machine, but as you say that approach won’t buy you an indefinite solution.

Without updates to the local server software it won’t keep-up with Java releases and won’t get security fixes. Because the local server source code is publicly available, it could be updated by people with the relevant skills, but there’s obviously a risk associated with trusting a 3rd party to make these changes.

As far as the phone app is concerned, having it removed from the App Store will be a major issue for iOS users, as most people don’t want to jailbreak their brand new iPhone to enable them to load the app, and it won’t be too long before an iOS update would make the app incompatible anyway.

Life is a little simpler for Android users, as they could side load the app, but newer versions of Android OS and new phone hardware will eventually become incompatible with the Blynk Legacy app.

This will create a situation where users have to maintain an old phone to enable them to still run Blynk Legacy, which negates the usefulness of the app.

There is also quite a large overhead attached to setting-up and maintaining a local server. A Raspberry Pi with an SD card will eventually fail without motive, as SD cards have a limited read-write life. Installing an SSD is a better option, but obviously more costly.
Some skills are also needed to configure port forwarding and DDNS to enable the app to be used outside of the local server.
There’s also work to do in terms of maintenance and backups, and the recent changes to Gmail that no longer allows the use of insecure apps means that emailing Auth tokens, report links etc will no longer work.

Considering all of this, and having run a Blynk local server myself for a while, I wouldn’t recommend anyone going down this route at this stage, unless they need to run Blynk in an environment where no internet or GPRS access is available.

Pete.

1 Like

Kodular is used to create your UI which communicates with Google Firebase which in turn communicates with the esp, so as an example if you turn a switch on on your UI you send a signal 1 to firebase. The esp reads the 1 on firebase and takes action. Simple as that

1 Like

Yeah, that’s will be fixed at some point.

1 Like

Sounds great.
Also a mobile viewable web console would be really good. Because choosing desktop view on a mobile browser will make the content ant tiny and will be hard to work with.

This would solve the problem of having a computer to start with. But again to program the device one needs a computer :stuck_out_tongue_winking_eye:.

1 Like

I wouldn’t call end of 2022 plenty of time. I basically have to migrate donzens of iot devices in 2 homes to the new platform. Ideally using OTA but if that fails it will be desoldering, reprogramming, resoldering.
And if i don’t find the time to do this in the next 7 months multiple sensors, lights and windows will be unusable.
I guess this is what you get when you rely on external software.

7 Likes

I get sad. But deeply grateful to have used the platform all these years.
I can’t migrate from legacy to 2.0 as it doesn’t have a map widget or custom button.
There is a monthly package, but it is out of reality for Brazilians since it is in Dollars.

4 Likes

Its better to buy a ready device. These days they come in cheap. And there is no monthly subscription. If you are not a maker then just install the ready product n you are done. Looks like you dont often try to modify your devices.

Blynk is suitable only for those who want to create, tinker etc etc…

Blynk 2.0 has all of that

2 Likes

All my devices are custom made PCB’s when i did have time to tinker. But that is about 5 years ago when i first started using Blynk.

2 Likes

Oops. Then you will have to subscribe to plus plan.

They will work fine with Blynk IoT, unless they use Bluetooth.

Pete.

1 Like

Yup. I know.
Only available on the monthly plan. In the free plan, it doesn’t.
The Brazilian currency is not worth anything, so $6.99 is a lot for us.

Ohhh , it is very sad this :frowning: , can not understand that also the server goes down for 1mil. users in 7 months ???
It was easy when it is nessesary to fill the energie time by time with some money to have a payment to keep this server alive i believe please …

3 Likes

Please provide us legacy application resources if possible because we have done many of our projects based on Blynk Legacy :upside_down_face: :cry: :sob:

3 Likes

…adding to that: anyone knows how to save the App locally for a later re-install?
As the App will disappear from the phone’s OS app-stores, when you switch phones or loose a phone backup, your local projects will be dead in the water as well, won’t they.