You should probably read this…
I said then…
“In Blynk IoT, licencing is based around devices and users, with limits set on each by the subscription plans. As far as I’m aware, Blynk don’t currently prevent or specifically look for another device connecting with the same auth token as one is already connected. But, think about how you would approach this if you were Blynk and you were looking to protect your revenue by preventing fraudulent use of multiple devices via auth token sharing. If it was me, I’d implement a system where if there was already an Always On connection with a specific auth token, and another connection was requested with the same auth token, I’d terminate the first connection and accept the second connection.
It may not work that way at the moment, but Blynk would be crazy not to implement this sort of checking in future.”
Looks like my prediction came true!
Pete.