Hi @DJSures
Was wondering if you would be interested in adding the ability to printto / readfrom an MQTT broker for IoT connectivity.
Not wishing to tell my grandmother how to suck eggs, as the saying goes, the MQTT brokerage seems to be a good vehicle for IoT connectivity. Ref to the following:
If I could suggest using the basic functionality of the PRINT command and adapting it so that a user could PRINTMQTT("Hello World" ) to a predefined MQTT brokerage defined earlier in a script as $MQTTBroker="http://www.mosquitto.org";... (There are a few more variables that would be needed like $MQTT_PORT and $MQTT_QOS but this would be a good start)
This reference sheet may be of help www.hivemq.com/mqtt-essentials-part-3-client-broker-connection-establishment/
Here's an informative but not necessarily stimulating video...
Thoughts?
@Tameion
With all of the iot "brokers" and protocols - would this option be the best investment? Do you have an existing relationship with them? If so it would be useful to know why we should choose them. Specifically over the initiatives that Google is currently taking in the same space by introducing a standardized iot protocol.
Okay.... I can guess from the well defined response that you get a lot of these requests.
Q: With all of the iot "brokers" and protocols - would this option be the best investment? A: Hard to say... there are a lot of players coming into the market and muddying the waters...
Q: Do you have an existing relationship with them? A: No - this is not really a 'them' and it is open source... been around for a bit though....
Q: If so it would be useful to know why we should choose them. A: Ease of use, already developed, cross platform with scripts available for android, Raspberry Pi, Windows, Mac, etc., multi-code implementation Python, C++ etc, very light weight with built in security and QoS.... but see next answer.... Broker is also relatively easy to host on your own network or on the web.... but there are also free to access ones available....
Q: Specifically over the initiatives that Google is currently taking in the same space by introducing a standardized IOT protocol. A: Now that Google is jumping in I guess it would be prudent to take a 'Wait-n-see' approach...
I will continue to work around it.
Thanks for taking the time to answer.
ps. The video has no relationship to any company.... just a random selection.
Adding weight to the argument for MQTT...
IBM have adopted the protocol for their Cloud and Node-Red for displaying the live MQTT data. See: internetofthings.ibmcloud.com/
But Google's recent acquisition of NEST is notable and may indicate their direction www.theguardian.com/technology/2014/jan/13/google-nest-labs-3bn-bid-smart-home-devices-market NEST devices use MQTT to relay their data to the IoT. See: www.ibm.com/developerworks/community/blogs/mobileblog/entry/how_mqtt_helps_drive_internet_of_things?lang=en
Quoting a somewhat aged but relevant article ...
ref: www.computerworld.com/article/2496621/emerging-technology/the-internet-of-things-gets-a-protocol----it-s-called-mqtt.htmlFurther reading blogs.vmware.com/vfabric/2013/02/choosing-your-messaging-protocol-amqp-mqtt-or-stomp.html
So its still a wait and see game.... as aptly pointed out here readwrite.com/2013/06/14/whats-holding-up-the-internet-of-things
@Tameion
