Hi - I am a Blynk newbie, although I am pretty familar with various Cloud IoT technologlies (which is part of my professional business).
In my leisure times I am a Garden Modelrailway Club member and I am controlling all kind of actors (sensors) such as locomotives, switches, signals etc via my Smartphone in WiFi environments.
Actors / Sensors are connected via RasPIs and Espressif Microcontrollers (all acting as IP- Servers/nodes in a model railway network).
On user side I use a Smartphone based interface (the NETIO App Framework NetIO APP ) for years now - until today.
NETIO is capable to set up IP based connections to all kinds of Network nodes / devices and let the user control their devices with knobs, sliders, etc. - always without the need of a Cloud server inbetween.
All my devices are all self-programmed in C++ / python / shell scripts (with socket interface connections)
As NETIO is being discontinued end of '21 I am looking for a substitute - Blynk looks very interesting.
Now my questions please:
- List item
Does the Blynk System Architectures demand for a (Blynk) Cloud server as an intermediate node to connect to my devices. Would mean Blynk is not usable for me - as Internet connectity (mobile networks) are not always available ?
- List item
Are there symbol / functionality / library limitations in quantity and/or quality (affecting the number of switches / locomotives / signals or limitations to functionality) when using a non-commercial license ?
20 devices limit per Smartphone is not a problem - would match, as switches and signals are controlled by a central node, 19 locomotives would be sufficent per Smartphone.
But what about “max 2000 Blynk.energy” ? What does this mean - symbols (sliders, knobs in the GUI)?
- List item
Is the non-business use “friendly tolerated” by your business?
I do note want to “misuse” a non-commercial license when hobby activities are not welcome in a professional business environment.
Being a Senior Manager in world-wide professional Cloud IoT business (as system supplier to mobility operators) I can fully understand that your strategy is fully concentrated on professional deployment and therefore hobbyist are considered ballast.
Nevertheless, it could be seen as an added value that also hobbyist can contribute good ideas and can also give valuable hints when tracking down errors.
Thanks in advance for your time and effort!
Best Regards