BLYNK
HOME       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

Weird logs

#1

I’m having some trouble with blynk connect
this is the logs

00:15:38.726 ERROR- Error sending push. Reason MismatchSenderId :thinking:
00:15:58.543 INFO - admin@blynk.cc hardware joined.
02:38:51.705 ERROR- Access restricted for 122.228.19.80. :thinking:
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com :thinking:
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.289 ERROR- Error sending push. Reason fcm.googleapis.com
03:37:41.304 ERROR- Error sending push. Reason fcm.googleapis.com
03:39:34.476 INFO - admin@blynk.cc hardware joined.
03:39:36.319 INFO - admin@blynk.cc hardware joined.
03:40:06.682 INFO - admin@blynk.cc hardware joined.
03:58:48.598 ERROR- Error sending push. Reason MismatchSenderId :thinking:
03:59:13.561 INFO - admin@blynk.cc hardware joined.
04:29:41.031 ERROR- Error sending push. Reason MismatchSenderId
04:30:00.485 INFO - admin@blynk.cc hardware joined.
05:13:40.254 ERROR- Error sending push. Reason MismatchSenderId
05:13:59.539 INFO - admin@blynk.cc hardware joined.
09:13:52.550 INFO - admin@blynk.cc Blynk-app (android-22706) joined.
09:16:36.445 INFO - admin@blynk.cc Blynk-app (android-22706) joined.
10:10:04.295 ERROR- Error sending push. Reason MismatchSenderId
10:12:22.982 INFO - admin@blynk.cc Blynk-app (android-22706) joined.
10:34:39.794 INFO - admin@blynk.cc Blynk-app (android-22706) joined.
12:54:08.411 INFO - admin@blynk.cc Blynk-app (android-22706) joined.
18:34:49.844 INFO - admin@blynk.cc Blynk-app (android-22706) joined.

18:35:37.867 INFO - admin@blynk.cc hardware joined. :sunny:

18h35 , I did a Hardreset on the nodemcu, and now it runs.

ERROR- Access restricted for 122.228.19.80.
I try a Whois IP :
New Jersey (NJ) , Comcast Cable.

I don’t know what makes fcm.googleapis.com here
its seems to be Firebase Cloud Messaging HTTP protocol

very weird :rofl:

additional info : I have 2 Nodemcu running same sketch with different auth
only one of them crash :thinking:

#2

What version of the ESP core did you use when you compiled the sketches for the NodeMCUs?

I think the family.googlips.com service is used for push messaging.

Pete.

#3

I am using 2.5.0 beta 3
I made a mistake, the second MCU is an ESP32 not a Nodemcu.

but why my sketch need to push a message ?
blynk mail is disabled

is it the reason why blynk can’t reconnect ? Access restricted for 122.228.19.80

I’m using @GTT reconnection

void loop() {
  timer.run();
  ArduinoOTA.handle();  // For OTA

  if (Blynk.connected()) {  // If connected run as normal
    Blynk.run();
  } else if (ReCnctFlag == 0) {  // If NOT connected and not already trying to reconnect, set timer to try to reconnect in 30 seconds
    ReCnctFlag = 1;  // Set reconnection Flag
    connectionstatus(); //see if wifi is available
    Serial.println("Starting reconnection timer in 30 seconds...");
    timer.setTimeout(30000L, []() {  // Lambda Reconnection Timer Function
      ReCnctFlag = 0;  // Reset reconnection Flag
      ReCnctCount++;  // Increment reconnection Counter
      Serial.print("Attempting reconnection #");
      Serial.println(ReCnctCount);
      Blynk.virtualWrite(V59, ReCnctCount);
      Blynk.connect();  // Try to reconnect to the server
    });  // END Timer Function
  }
}
#4

ERROR- Error sending push. Reason MismatchSenderId

wrong mail adress in mail.properties !!!

so now, I have to find out why Blynk disconnect more than 6 times a day.

2019-05-31_112732

1 Like
ERROR- Error Sending push. Reason MismatchSenderId
#5

Hello!

what did you meant by wrong e-mail address in mail.properties.

I am getting the same error. I cannot make the notifications work.

I had a different e-mail address set in mail.properties(than the one used for the account in the application) . I set the same e-mail address and restarted the server, yet I get the same error.

any ideas?

#6

I thing you need to tag @Blynk_Coeur to get an answer from him.

Did you re-start the server?

Pete.

1 Like
#7

yes, I meant the server :smiley: . I removed and added the notifications widget again, just in case. same error

#8

I have the same problem. this happened after the application was updated from the playmarket. the old version of the application (I have a clone of the apk) works as before, the new version does not work even with the new server 0.41.15 …

#9

the developers answered me that they know about this problem and they will fix it in the coming days, you need to wait a bit …

#10

It looks like that it is an app side issue. We will upload a new version soon. Just in case, please also update to the latest Blynk server, as recently there have been some updates connected with push support.

#11

I’ve uploaded a new version with a fix to this issue - I suppose in the next 24 hours it will be available to update.

2 Likes
Android app notification doesn't work since 2.27.21
#12

I did not have the chance to update the server yet, but I just tested the app earlier and I can confirm the notifications work :slight_smile:

your effort is much appreciated!

1 Like