They are effectively identifiers between the Project, Server and MCU hardware… make data go where it should (remember a Server can host hundreds of users and projects) to make them work differently could effectively change the whole architecture of how Blynk works.
As the Server is central to the whole App ← Server → Hardware infrastructure, each Server (which by definition is the generator and overseer of the Auth codes) can only use it’s own generated codes, not ones that are generated by another completely differing server. It is a very closed in clique
The “local server” is not necessarily local and can be anywhere in the world, it’s just a different server to the official Blynk servers around the world.
It’s not related to FW hashing it’s simply a security measure that applies to using the server, locally or otherwise.
My assumption … all my previous BLYNK interface and code operated… was “thinking” this new interface would also NOT be blocked. Typically, the FW & AVirus ask me to allow things, then I click to allow the exceptions.
As long as everything is on the same network, internet is not required.
But Bridge (along with most everything Blynk), DOES require a server… BT/BLE is a rare exception between App and Hardware (and only supports some Widgets), but still requires the App to connect to a server for login and Auth code generation.
EDIT - And @Costas is correct, the DOS Window MUST stay running, in background (minimised) at least.
The default is now 0.0.0.0/0,::/0 so as long as you haven’t changed this in server.properties then any machine on your network should be able to access the local Blynk server. But as pointed out by @Gunner you need to check firewall and antivirus isn’t blocking the ports etc.
SUCCESS…. Removed the Firewall and now ALL connect. New BLYNK project and tokens created. Thank you BOTH for sticking with this.Firewall back at full strength until I can learn how to allow BLYNK to peak through without turning the FW off.
Education: Still a long way to go. Want to ask again about the new tokens I created. Since they are “registered” to my Email and my IP 10.0.0.166, If I CHANGE my local hard-coded ip in the Comcast modem, will the tokens stop operating??? Or asking different, is the ip hashed into the token with other information, or is it simply a unique identifier?
I do not think there is a detailed description of the interface available to describe this level of understanding, so I need to ask you two.
Truthfully, that works the same for a CLI window into a Linux device as well, just a different procedure to “minimise” it (and yes I am generalizing the similarities)
Glad you got it working !!
The Auth tokens are linked to your account in the server, as are any projects. Your servers IP will have no direct affect on them, but you will need to change any such IP in both your App and Sketches.
Think of it as having the keys to your car in your hand, but also needing to remember where you parked it in order to properly use it
LOL @Gunner
I’m glad my bad experience helped others.
but on the same note… can anyone add to the docs to do this so people won’t get stuck on some technical issues for nothing… just add 2 lines to the blynk docs that says to check for the FW and antivirus…
I guess you are then running your Local Server on a PC (it probably states that somewhere above… but … lazy ;P)
Best to manually allow server full network access in both FW and AV
