Hi @Vicar, welcome to Blynk.
The discussions around MQTT are mostly because of integrations with other home automation systems such as Home Assistant etc.
It’s not meant to replace the existing protocol over ssl/tls or tcp/ip, or the existing HTTP(S) REST API, but rather as an alternative method of communication with the Blynk server.
BTW, the topic you linked to has a broken link to the documentation. The full Legacy documentation is here…
Although this is for the Legacy system, the basic protocol is unchanged, but additional protocol definitions have been added.
Personally, I use MQTT and Node-Red for all of my HA projects, with Node-Red providing my logic/rules engine functionality and all devices communication with Node-Red via MQTT messaging.
To facilitate communication with the Blynk server, so that I can use Blynk as my UI front-end, I use the Blynk plug-in for Node-Red, which translates the ssl/tls protocol to MQTT.
It would be far easier if that plug-in wasn’t needed, and we could communicate directly via MQTT if we wanted to.
There’s more info in this more recent post…
Hmmm, we’ve had something like this before, and TBH it didn’t work.
Blynk’s development priorities have always been driven by new business customer requirements, often as part of the onboarding process.
Whilst Blynk are happy to hear suggestions from forum members, a formalised list implies that the idea is somehow in the development pipeline, and leads to “I suggested x three years ago and nothing has happened” type of comments.
Pete.