Consider MQTT input

[jsilence]

MQTT (http://mqtt.org) seems to be an appropriate protocol for data transfer from small embedded machines. Client libraries for a wide range of languages are available. The broker of choice currently seems to be Mosquitto, but other MQ brokers also understand the mqtt protocol.
Would be nice, if phant could subscribe to a mqtt topic and collect data from there.

[toddtreece]

I've personally never used MQTT, but I've been planning on seeing how to integrate it. I'll let you know once I take a look at how it works.

[johncohn]

+1 for mqtt.. I use it for everything. for many things I find it easier to use than REST (eg, no need to poll for input). It's also very light weight.

[toddtreece]

@jsilence & @johncohn:

I have spun up a new test server with a new (hopefully better) topic format at http://phantmqtt.sparkfun.com. You can test the server by downloading this Gist: https://gist.github.com/toddtreece/feb66ddef602c8ec0c1e

You'll need to run npm install and then node client.js from the extracted folder to start the client.

Topics

I'm going to use PUBLIC and PRIVATE as placeholders for your keys. Replace the placeholders with the hashes given to you during the creation process.

Pushing data

Payloads should be JSON encoded, and should only include the fields you defined when creating your stream.

Topic for pushing data

input/PUBLIC/PRIVATE

Push confirmations

Confirmations about the status of pushes can be subscribed to using the following topic.

Topic for responses about status of pushed data

response/PUBLIC/input

Live data output

Phant can receive data from multiple sources (HTTP, TCP, UDP, MQTT, etc), so if you'd like to receive the data from all sources, you can subscribe to the stream by using the following topic format.

Topic for subscribing to JSON encoded payloads with all fields

output/PUBLIC

If you would like to subscribe to a specific field, you can use the following format and replace FIELD_NAME with the name of your field.

Topic for subscribing to a specific field

output/PUBLIC/FIELD_NAME

[johncohn]

Todd,
I still can't build on x64 Win 7.. I will try to test at the end of the
week. In the mean time, do you have a broker set up on your end that I can
try to hit ?
-jc

John Cohn Ph.D,
IBM Fellow , Corporate Technical Strategy
phone 802-578-0985

From: Todd Treece notifications@github.com
To: sparkfun/phant phant@noreply.github.com
Cc: John M Cohn/Burlington/IBM@IBMUS
Date: 08/12/2014 10:53 AM
Subject: Re: [phant] Consider MQTT input (#55)

@jsilence & @johncohn:
I have spun up a new test server with a new (hopefully better) topic
format at http://phantmqtt.sparkfun.com. You can test the server by
downloading this Gist:
https://gist.github.com/toddtreece/feb66ddef602c8ec0c1e
You'll need to run npm install and then node client.js from the extracted
folder to start the client.
Topics
I'm going to use PUBLIC and PRIVATE as placeholders for your keys. Replace
the placeholders with the hashes given to you during the creation process.
Pushing data
Payloads should be JSON encoded, and should only include the fields you
defined when creating your stream.
Topic for pushing data
input/PUBLIC/PRIVATE

Push confirmations
Confirmations about the status of pushes can be subscribed to using the
following topic.
Topic for responses about status of pushed data
response/PUBLIC/input

Live data output
Phant can receive data from multiple sources (HTTP, TCP, UDP, MQTT, etc),
so if you'd like to receive the data from all sources, you can subscribe
to the stream by using the following topic format.
Topic for subscribing to JSON encoded payloads with all fields
output/PUBLIC

If you would like to subscribe to a specific field, you can use the
following format and replace FIELD_NAME with the name of your field.
Topic for subscribing to a specific field
output/PUBLIC/FIELD_NAME

—
Reply to this email directly or view it on GitHub.

[toddtreece]

@johncohn
http://phantmqtt.sparkfun.com is the instance of phant with the broker running on port 1883. You shouldn't need to build anything if you have your own MQTT client.

[johncohn]

So fat so good . I can connect with the broker and publish

-jc

John Cohn
+1 802 578 0985

On Aug 12, 2014, at 4:22 PM, "Todd Treece" notifications@github.com wrote:

@johncohn
http://phantmqtt.sparkfun.com is the instance of phant with the broker running on port 1883. You shouldn't need to build anything if you have your own MQTT client.

—
Reply to this email directly or view it on GitHub.

[jsilence]

Was able to connect, subscribe and publish with the WMQTT Sample client (ia92).
Thank you for implementing this protocol!

[toddtreece]

MQTT over websockets is now live on data.sparkfun.com. I'm currently trying to get the load balancer to forward tcp traffic to 1883 and 8883 for ssl. I'll close the bug when mqtt over tcp is live.

[johncohn]

I am out of the office until 09/02/2014.

I am out of the office until 9/2/2014 having my turboencabulator
refragulated. I will not have access to email. Talk to you then. Thanks !

Note: This is an automated response to your message "Re: [phant] Consider
MQTT input (#55)" sent on 08/21/2014 19:06:10.

This is the only notification you will receive while this person is away.

[toddtreece]

MQTT on data.sparkfun.com port 1883 is live, and I'm working on getting SSL enabled on port 8883. I'm going to close this issue, but I'll post once SSL is enabled.

[bbhoss]

I'm trying to publish to "input/PUBLIC/PRIVATE" to no avail. The server just immediately closes the connection without cause. Can someone confirm this still works?

Thanks

[hollie]

I'm using the MQTT interface to receive values from a datastream on data.sparkfun.com and it works well.

One question: would be possible to set the 'retained' flag to data that is posted to the MQTT broker? This way a new client gets an update of the last received value from the broker upon connecting. Otherwise the client needs to wait for a new value to be posted to the broker before it receives its first value. If there are only a few values posted per day then the client is in the blue about the status of the data source for quite an extended time. The retained flag solves this. See here for some more details on this.

Regards,
Lieven.