Episode 381 – MQTT-Pi

By | January 31, 2018

MQTT

MQTT is a subscription protocol, as opposed to HTTP, which is a request based protocol. If you want to send information/commands over HTTP, you would make a request, and an HTTP server would respond with the information. In an MQTT environment, information is published to the MQTT broker and a client has to keep a constant connection to it to observe events. It is ideal for limited systems, designed for low bandwidth and high latency.

If you are interested in installing an open source broker, you can try Mosquitto, EMQ, or Mosca. MQTT does support access control through a username/password system as well as access control for specific topics. You can bridge multiple brokers, to republish messages on one to the other. You can also bridge your broker to Amazon IoT or an external MQTT server if you want a presence outside of your house. There are advantages to distributing your messaging. If you want to experiment, CloudMQTT offers a free tier.

  • Android News
    • Years old issue may finally be fixed with National Roaming toggle
  • App News
    • New owners of BeyondPod have not kept up with development
    • Google Voice preps VoIP calling functionality
    • Google launches test of hyperlocal news app called Bulletin
  • In Other News
    • Ingvar Kamprad, founder of Ikea, dead at age 91

 

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)

Mentions