I have a few old projects that are based on Legacy Blynk - running on a local server. No particular reason I haven’t converted to Blynk 2.0 - just that they exist have been doing great - are on my own server - and “they work”. And I just dont have the time bandwidth to convert them over. Though that may have to change :-).
So the Legacy Blynk App features (running on iOS 17.61 - iPhone SE-2ndGen) - functions just fine (i.e. all the displays and inputs work fine) - it appears that the “NOTICEs” are no longer working.
This was a surprise and I don’t have a clue exactly “when” - but seems to be around early-mid Aug 2024.
Given all other aspects are doing well - it seems a bit confusing. And while I know this is a low priority thing - was hoping someone may have a comment.
The only thing I am suspicious of - is that this was about the time iOS 17.6.1 was upgraded on my phone.
Anyone have a thought / knowledge / comment?
Note: I have fully recompiled the code on a test device - no joy.
I have removed and re-installed the “Notification” widget - no joy.
As I stated - I have 4 old projects for my home that is not worth the time/cost to migrate them to the new Blynk (plus the one has over 60 data values). Of course - that may change now - haha.
Anyway 3 have not had any code changes (or been recompiled or downloaded) in the past 6 months - yet “no Notifications are received”. The sending side - appears fine. Even the “device offline” notification from the app itself - does not work.
Well another NEW error - I thought I would “create a new project”. However I can NOT email the Authorization Code - it gets an error within the APP
So I am very suspicious that something with iOS 17.6.1 is NOT allowing things. But I could always be wrong - haha.
I am not using GMAIL - but I did as you commented to get it running. This was just a test with a whole new PROJECT and New IoT Board.
However it did not change - and side note the “Device is Offline” notification does NOT work either. Now I dont know if that routes from the APP back to Server and then back to the Notification - or if there is a direct path in the phone. But bottom line - it doesnt work either - bummer.
I’m guessing that you either didn’t read, or didn’t understand my comment in the other topic that I linked to.
Notifications are (or at least were until very recently) sent from the server via a 3rd party service to the app.
Pete,
First - thanks for still providing guidance and assistance for the Legacy Blynk.
I need to get myself fully converted - but with some of the interesting limits on the new environment - it has just been easier to hang with the legacy stuff.
Anyway - understand about the MAIL stuff - no worries there - didnt mean to create a confusing side-note.
If I understand things - Notifications go from the Server via a 3rd party - to the APP - which then creates the notification “message” on the phone. Correct?
Am I then of the understanding that Blynk has “discontinued” this 3rd party service for Notifications - and therefore Legacy Blynk Notifications are “No Longer Functional”?? - !!! Correct?
No, it’s a service provided by a THIRD PARTY - not Blynk. If you look at the other post I linked to you’ll see who I think that there part is.
It would appear so, from what you and other legacy users are saying.
There’s nothing to stop you using a different messaging service for notifications, although it wouldn’t replace the offline notifications from the server, but TBH you’d be better upgrading to Blynk IoT.
I am also experiencing the notification issues many of us have been facing with the Blynk local server since September 9th. It appears that this problem is not limited to iOS devices but also affects Android users, as I am experiencing the same issue.
From my research, it seems that the Blynk local server relies on the legacy Google Cloud Messaging (GCM) protocol, which has been deprecated. The legacy GCM service has been replaced by Firebase Cloud Messaging (FCM), and as of June 20, 2023, the legacy APIs are no longer supported, with full removal scheduled for June 2024. More details can be found here: (Protocolo HTTP de mensajería en la nube de Firebase | Firebase Cloud Messaging).
The migration to the new FCM HTTP v1 API is necessary to restore notification functionality. I have attempted to migrate to the new protocol with the help of AI tools, but have encountered some obstacles. Specifically, it appears that an additional device may be required to run Python scripts and handle OAuth 2.0 access tokens for the new FCM system.
I hope this information helps other local server users who might be looking for a solution. If anyone has successfully navigated this migration or has additional insights, your input would be greatly appreciated!
I also use the local blynk server, which is no longer supported. I would be very grateful if someone has enough experience to carry out the new implementation/migration. I can confirm what Gerrie4280 wrote. I couldn’t find out more myself. I tried testing the following command in the console and it also responded with 302.
Thanks Pete for the alternative. I will try to incorporate it into my projects and use it as an alternative.
Unfortunately you have to pay for multi-notifications, if I understand correctly.
If you mean different device operating systems then yes, you’d need a $5 one-off subscription for both iOS and Android apps, and if you want to use desktop messaging as well then that would be an additional $5 one-off payment.
You can add these to the same Pushover account (i used to use this before I started using Blynk, but still have my account which hasn’t seen any use for over 7 years)…
Just confirming what Pete has stated. Migration toe Pushover is the easiest solution (IMHO).
There are several examples around - both using Normal or Secure Wifi Client.
JSON can be used to create the data structure if desired - or it can be handled with simple String blending.
Anyway - Gratitude that Legacy Blynk Notifications lasted as long as they did.
Pushover is an easy solution - and the cheapest i found.
Thanks for the insight! I plan to setup a reverse proxy server between my network and the Blynk local server to convert ‘NOTIFY’ type messages into Pushover requests. This should be the least amount of work for my environment.
