Closed Bettapro closed 2 years ago
Is it will be send all data to blynk server as mqtt messages?
Basically I use a blynk local server, is it possible to use this feature later in local server?
Is it will be send all data to blynk server as mqtt messages?
Basically I use a blynk local server, is it possible to use this feature later in local server?
This will allow to use different servers (other than blynk) using mqtt protocols. As far as I know blynk doesn't use mqtt (I've seen projects implementing a bridge between blynk server and mqtt broker)
I've used thingsboard in my tests, I'm keeping it as simple and "universal" as possibile, but it's parked at the moment... waiting for some time to spend here 😞 )
Is it will be send all data to blynk server as mqtt messages? Basically I use a blynk local server, is it possible to use this feature later in local server?
This will allow to use different servers (other than blynk) using mqtt protocols. As far as I know blynk doesn't use mqtt (I've seen projects implementing a bridge between blynk server and mqtt broker)
I've used thingsboard in my tests, I'm keeping it as simple and "universal" as possibile, but it's parked at the moment... waiting for some time to spend here 😞 )
Understood. So is there any big improvement or any comparison send a data between mqtt and blynk messages protocol ?
Is it will be send all data to blynk server as mqtt messages? Basically I use a blynk local server, is it possible to use this feature later in local server?
This will allow to use different servers (other than blynk) using mqtt protocols. As far as I know blynk doesn't use mqtt (I've seen projects implementing a bridge between blynk server and mqtt broker) I've used thingsboard in my tests, I'm keeping it as simple and "universal" as possibile, but it's parked at the moment... waiting for some time to spend here 😞 )
Understood. So is there any big improvement or any comparison send a data between mqtt and blynk messages protocol ?
They're doing basically the same thing, mqtt protocol is more flexible and supported by a wide rage of other platforms. Blynk is using a different protocol just because when the project started, mqtt was not fitting their needs.
Blynk is "self sufficient", more convinient and ready to use... mqtt is just a protocol nothing more so server and UI implementations are up to you.
Please use Discussion for this kind of question as they're not related to code or issues. 📓
Basic support has been merged in v3.x.x, will keep in this status until any reasonable needs.
Could be integrated as alterative to blynk or run together (DEPENDING on resource consumption)
Variables name could be mapped to topics USING OTHER DIFINES like:
#define MQTT_TOPIC_STAT_ENERGY_GENERATED_THIS_YEAR "solartracer/<ID>/enegy_generated_this_year"