Just to mention, when I try to ping blynk-cloud.com I am getting 139.59.206.133 but there are no projects in this account. I created one and it works but I lost all my old projects.
When I am logged in with 45.55.130.102 I can see all my existing projects and I have around 30000 energy points, but all the hardware cannot push data.
When I am logged in without custom IP I cannot see my projects and I have no energy points. I can create a simple project and my hardware pushes data successfully. The same happens if I am logged in with the IP I am getting when ping blynk-cloud.com - 139.59.206.133.
No I did not. I have hardware in Tanzania, Kenya and Bulgaria. When I am in Kenya or Tanzania I can monitor them all, recently I moved to Bulgaria and lost them all.
So did you put IP in app? In case you can monitor them all from other locations it should work. However for your case I would recommend to use Local Server until we release fix for this issue.
I cannot put a fixed IP in the hardware because I am traveling a lot. Obviously I’ll have to wait for an update to fix that one.
Lets hope You will come out with something soon.
Blynk have the fix available but it will break the service for too many static Blynkers until they are using the newer libraries. How does travelling stop you using a fixed IP in the Blynk app?
AFAIK if you move all your projects to one server, i.e one IP address in the app, you will see the projects in Dar Es Salaam, Nairobi, Bulgaria, Isle of Man, Timbuktu and everywhere in between.
Do you mean if I put 45.55.130.102 in the hardware located in Bulgaria and then log in with the same IP in BLYNK it will work?
if (WiFi.status() == WL_CONNECTED && Connected2Blynk == 0) {
Serial.println("BLYNK RE CONNECTING … … ");
Blynk.config(auth); // in place of Blynk.begin(auth, ssid, pass);
Blynk.connect(3333); // timeout set to 10 seconds and then continue without Blynk
// Blynk.begin(auth, SSID, pass, IPAddress(XXX,XXX,XXX,XXX));
}
Regards, Ivan