MQTT bridge | Feature Requests | Forum

Avatar

Please consider registering
Guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed sp_TopicIcon
MQTT bridge
No permission to create posts
February 4, 2014
8:54 pm
Avatar
rw950431

Top
Members
Forum Posts: 262
Member Since:
January 30, 2014
sp_UserOfflineSmall Offline

From the website http://www.mqtt.org
MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

December 28, 2014
11:34 pm
Avatar
jonn26
New Member
Members
Forum Posts: 1
Member Since:
December 29, 2014
sp_UserOfflineSmall Offline

+1 : )

December 30, 2015
3:27 am
Avatar
lingvo
New Member
Members
Forum Posts: 3
Member Since:
December 30, 2015
sp_UserOfflineSmall Offline

It would be nice if you could add MQTT support for thingspeak - e.g. that my IoT devices could publish and subscribe to topics using MQTT. This is very lightweight and easiest way to update topic feeds and receive updates from thingspeak apps.

You don't have to implement any API, as MQTT is supported already by many platforms, just provide ability to either connect to your MQTT broker, or thingspeak should act like a MQTT client, connecting to any online MQTT broker as client.

January 1, 2016
11:48 pm
Avatar
JoeQ
New Member
Members
Forum Posts: 1
Member Since:
January 2, 2016
sp_UserOfflineSmall Offline

This would be a great feature to have, as MQTT has become something of a standard, and ThingSpeak provides complementary functionality (the ability to archive and graphically display data). It would be wonderful to be able to have ThingSpeak "subscribe" to an MQTT topic on a given broker and display and archive the data that comes in.

March 10, 2016
6:16 am
Avatar
buben
New Member
Members
Forum Posts: 3
Member Since:
March 10, 2016
sp_UserOfflineSmall Offline
July 11, 2016
7:36 pm
Avatar
Vinod

MathWorks
Members
Forum Posts: 202
Member Since:
May 1, 2016
sp_UserOfflineSmall Offline

Thank you for your feature request. The development team is actively investigating support for MQTT protocol in Thingspeak. It will be very helpful to the team to get additional details of your application; Specifically, your anticipated workflows, performance requirements, and details about how you intend to use MQTT support. Please write to support@thingspeak.com and someone on the development team may be in touch with you directly.

December 5, 2016
6:41 pm
Avatar
rw950431

Top
Members
Forum Posts: 262
Member Since:
January 30, 2014
sp_UserOfflineSmall Offline

Holy smokes Batman!  When did this happen? https://au.mathworks.com/help/thingspeak/mqtt-api.html

 

Seems like its publish-only at this stage (no documented way to subscribe to a channel) but still a big step forward.  Good work guys

December 6, 2016
8:32 am
Avatar
Rob Purser
Natick, MA

MathWorks
Members
Forum Posts: 46
Member Since:
August 22, 2015
sp_UserOfflineSmall Offline

Sharp eyes -- we went live yesterday with this.   And yes -- It's MQTT publish only at this point.

All the best,

-Rob

Senior Development Manager for IoT and Hardware Interfacing for MATLAB at MathWorks.  Visit ThingSpeak.com to explore the IoT Analytic platform that speaks MATLAB made for engineers and scientists.  You can collect, analyze, and act in 5 minutes or less!

December 6, 2016
4:55 pm
Avatar
Joe_1
New Member
Members
Forum Posts: 1
Member Since:
May 7, 2016
sp_UserOfflineSmall Offline

Top job, sterling work, well done! Is there any documentation available RE MQTT publish performance / latency / limits etc for free accounts?

December 6, 2016
7:20 pm
Avatar
Vinod

MathWorks
Members
Forum Posts: 202
Member Since:
May 1, 2016
sp_UserOfflineSmall Offline

Here's the documentation: https://www.mathworks.com/help/thingspeak/mqtt-api.html

Users with free thingspeak accounts can only push data to a channel once every 15s. That holds true via the REST API and the MQTT API. The MQTT publish service is a Quality of Service (QoS) = 0 level API. There is currently no difference in the MQTT API for free v/s paid accounts.

December 7, 2016
12:16 pm
Avatar
kilian
New Member
Members
Forum Posts: 3
Member Since:
December 7, 2016
sp_UserOfflineSmall Offline

First of all, thank you very much for implementing the MQTT publish.

In my tests I have however noticed, that the server ignores Keep Alive values of greater than 60 seconds (technically speaking greater than 40) and drops the connection after short below 60 seconds of inactivity. The same is true for sessions with a Keep Alive value of 0 (i.e. disabled).

This is standard-conforming behavior, as the server is allowed to disconnect at any time, regardless of the Keep Alive. However, it is not really nice regarding low-power applications, as one of two things currently have to happen:

  1. A Keep Alive of less than 60 has to be chosen and the client device has to wake up and send a packet every 55 seconds (to be safe). Or
  2. For every data packet with a period of greater than one minute, a new TCP connection and MQTT session have to be established.

This is would normally not be necessary, as TCP connections are able to stay inactive yet connected ("established") for hours (days, really). In fact, TCP itself knows no idle timeouts at all but has the capability of sending keep-alive packets on its own.

So, I would like to request considering to significantly raise the server-side timeout, or even better adhere to the Keep Alive requested by the client. If there are any concerns that led to implementing this extremely short timeout (e.g. fear of DOS attacks), I would love to hear about them.

For the time being, I recommend to all users to set a Keep Alive value of 55 seconds or less in their clients. Quite a few implementations seem to use a default value of 60, which is nasty in this case, as it is just over the threshold and will unfortunately lead to a full reconnect every minute instead of just a ping.

Anyway, thanks again for the MQTT implementation and maybe someone is able to sort this out.

 

Best regards,

Kilian

December 7, 2016
4:15 pm
Avatar
JasonW

MathWorks
Members
Forum Posts: 29
Member Since:
October 21, 2016
sp_UserOfflineSmall Offline

This being our initial release of the MQTT service, we had to make some trade-offs in our broker configuration.  This is because we don't have an infinite number of TCP sockets on the broker.  We want to give everyone a chance to try it out. So that means, at this time at least, the client connection time with the broker is limited. For now, MQTT clients should connect -> publish -> disconnect.  Once we get some usage data from the broker, we'll be able to optimize where we can.

December 8, 2016
2:24 am
Avatar
kilian
New Member
Members
Forum Posts: 3
Member Since:
December 7, 2016
sp_UserOfflineSmall Offline

Thank you for the quick reply and the clarification. I understand your point. I have seen that the service is based on AWS but did not know how scalable the architecture of your implementation is. Maybe you could add some hints regarding the recommended use to the documentation. The provided examples sort of suggest a continuous connection.

Anyway, thanks again for the MQTT service.

 

Best regards,

Kilian

July 29, 2017
1:34 am
Avatar
ChungTran
New Member
Members
Forum Posts: 1
Member Since:
July 29, 2017
sp_UserOfflineSmall Offline

Hi, 

When we use MQTT protocol to send data to server, can we check the response to verify if it was sent complete? And what function to get data use MQTT API.

 

Thanks,

Chung

Forum Timezone: America/New_York

Most Users Ever Online: 114

Currently Online:
22 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

rw950431: 261

Vinod: 196

piajola: 85

turgo: 70

vespapierre: 63

Adarsh_Murthy: 62

Member Stats:

Guest Posters: 1

Members: 5703

Moderators: 0

Admins: 2

Forum Stats:

Groups: 4

Forums: 17

Topics: 1313

Posts: 4565

Newest Members:

BarryMaync, ThomasRougs, DonaldGen, prince, JrGordon, Elamsweems

Administrators: Hans: 387, lee: 457