MQTT - what happened

@davidmiles

@Costas is not associated with Blynk.

Yes, we provide business services, check: http://blynk.io. And we are discussing with him his business. Which means that he is a client. The same way you are the client of Blynk.

I’m definitely not a client of Blynk.

If you use our services then you are… Otherwise glad to see you in our community anyway :wink:

@scargill just replying to your blog post. 900 energy points might sound a lot for a history graph but putting that into context anyone who pays the modest sum for 28000 points is only paying 46 pence for the widget.

Personally I’m not a big fan of graphs as I prefer functionality over form but for those that like that sort of thing it’s hardly what you would call expensive. I’m sure you can access your data and produce the graphs for yourself if you really wanted to, but is it worth your time?

@davidmiles when I made the post about other suppliers being interested in what Blynk has to offer I wasn’t aware that Sparkfun had partnered with Blynk. I’m not the least bit surprised as it seems an excellent fit which will surely have a benefit for ALL Blynkers. Blynk is not for everyone and some people will choose an alternative approach, that is their choice.

Of course it’s not expertise Costas - we’ve already implemented database IO for Imperihome history graphs - that isn’t the point - clearly what is not a good idea is running multiple apps with some data here, some there - so ideally one would like to commit to one app or the other. And one graph is not an issue, personally I’d want to historically graph everything within Blynk - then it is no longer 46 pence. Still - if this is a one-off it is acceptable - but description “energy” suggests that over time available energy will “run out” - in which case it is not a one-off cost. Can someone clarify? If I have an app with umpteen pages and many buttons - am I paying a one-off cost for this - or will I have to repeatedly pay over time assuming I make no changes?

This is one-off cost.

Thank you for that Dmytiy - with that clarification I’m happier. I’ll amend my information accordingly.

Well I for one love my graphs, they are a big part of my dashboard.

How about having a vote on the forum to help decide which widgets/ functions are most popular?

Sorry if you’ve already done it I’ve only just joined.

They are a big part of my dashboard too and that is another reason I don’t like them. I might like them a little more when tabbed pages are introduced by Blynk.

Blynk knows exactly what widgets we all have and they will have a pretty good idea how much effort goes into supporting each widget. Function over form for me but each user will have different preferences.

Here you go Vote for the next widget

1 Like

Thanks, voting done.

Bumping this old topic as I have seen some recent notes about it.

any news on native MQTT support?

2 Likes

Basic support is there. Also there is a node-red-blynk module.

D, any write up or hints where to start looking.

Currently i use Mosquitto for the devices around the house (I have promised P a full write up too), E.g.:

Action from button:

BLYNK_WRITE(33) //turn Off all home entertainment devices
{
  int a = param.asInt();
  if (a == 0) {
    } else {
    client.publish("/remote/dstv", "0"); // MQTT "0" Triggers action 
    delay(300);
    client.publish("/remote/tv", "0");
    delay(300);
    client.publish("/remote/hifi", "0"); 
    } 
}

Input - e.g. Temperature sensor publishing to MQTT topic, displayed on widget:

void callback(char* topic, byte* payload, unsigned int length) {
if (strcmp(topic, "/topic/Temp") == 0){  //check the topic for new reading
payload[length]='\0';
String temp = String((char*)payload);
Blynk.virtualWrite(8,temp); //sends temp reading to Blynk widget on pin 8
}
else

Hello, I use blynk from the beginning.
But without MQTT direct connection I gonna give up from blynk!!!
Sorry

MQTT is there. However we have no docs yet. On it’s way.

1 Like

Just a thought …I am using an open source App development setup with OpenHAB …not as easy to integrate devices as programming knowlage is a must…Linux and c++ but no money crosses hands which is cool and most protocols come across as well …wondering if blynk would consider an open source setup where developers and programmers can have some fun without paying for it …

Blynk is already fully free for local servers and 2/3 open-sourced. And does many things without coding.

2 Likes

Already looking forward to see this.
Would like to expand my home automation system, and instead of http requests I would like to use mqtt because it is faster and it can talk to all the devices with the same topic. Also easier to connect Node Red with it. Without the need of multiple apps to control everything