Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Controllers
  3. Is MQTT Necessary? or, Use Case for MQTT?

Is MQTT Necessary? or, Use Case for MQTT?

Scheduled Pinned Locked Moved Controllers
mqttmqtt openhabgatewayopenhab
18 Posts 10 Posters 8.6k Views 11 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • TRS-80T Offline
    TRS-80T Offline
    TRS-80
    wrote on last edited by
    #9

    Thanks for the clarification, @hek!

    I think I have done just about as much research as is needed to select hub hardware, software, and sort of overall topology and protocols, etc... And I've already got several ideas for various nodes, of course!

    Which means, time to order parts soon and start tinkering! I'm excited! :)

    1 Reply Last reply
    0
    • UglyKidJoeU Offline
      UglyKidJoeU Offline
      UglyKidJoe
      wrote on last edited by
      #10

      @TRS-80, this topic is very interesting (so I though I would revive it :) )

      I'm building my system based on Openhhab2 which it a pretty awesome framework to say the least. Immensely powerful.

      Your post here touches on one area that I just can't get my head around - the link between OH2 on the Pi and Arduino RF boards. I'm probably missing something obvious but it's never been clear to me.

      Admittedly I haven't set up any Arduino-based sensors yet but I'm hoping to start shortly (my dream is to build motion sensors as they are horribly expensive to buy manufactured (i.e. Aeotec etc)).

      Have you bypassed MQTT or has it become integral in your workflow?

      1 Reply Last reply
      0
      • gohanG Offline
        gohanG Offline
        gohan
        Mod
        wrote on last edited by
        #11

        With OH2 you can use either serial gateway or mqtt. Mqtt allows you to have much more flexibility in terms of monitoring data or send data to your controller: for example if you want to tinker with sensor values for testing purposes, you could just power off sensor and send data you want using a simple mqtt client, or if you want to play around with multiple controllers you only need to configure them to subscribe to mqtt and they can run simultaneously. I've even seen a post about using zabbix to plot data from mqtt

        UglyKidJoeU 1 Reply Last reply
        0
        • hekH Offline
          hekH Offline
          hek
          Admin
          wrote on last edited by
          #12

          Sidenote: MySensors has a Node RED plugin available as well. It's also a good alternative for tinkering/route messages from a MySensors network. Even more flexible then a raw MQTT broker.

          UglyKidJoeU 1 Reply Last reply
          0
          • gohanG gohan

            With OH2 you can use either serial gateway or mqtt. Mqtt allows you to have much more flexibility in terms of monitoring data or send data to your controller: for example if you want to tinker with sensor values for testing purposes, you could just power off sensor and send data you want using a simple mqtt client, or if you want to play around with multiple controllers you only need to configure them to subscribe to mqtt and they can run simultaneously. I've even seen a post about using zabbix to plot data from mqtt

            UglyKidJoeU Offline
            UglyKidJoeU Offline
            UglyKidJoe
            wrote on last edited by
            #13

            @gohan

            Thanks for the quick response.

            It will be my first implementation of MQTT so I'm pretty much a blank canvas. I'll go with setting up the MQTT broker (server it's called now I believe) on my Raspberry Pi 3.

            Installing OpenHAB2 on the Pi has been made a breeze by an unattended installer called OpenHABian. Bundled with the installer is an MQTT option which should set it up (it's accessed via a menu).

            I'll be happy to share my lessons learned here, no doubt there will be a few :)

            I've still got to order a few sensors and boards etc to get started so it will take a little while. That;s why I read this thread to get an idea of how the components all talk to each other. That would at least help me determine what I need to buy upfront so I can get busy with it. Any advice would be appreciated (just to get a motion sensor up and running)

            I imagine it can become addictive!

            gohanG 1 Reply Last reply
            0
            • T Offline
              T Offline
              TimO
              Hero Member
              wrote on last edited by
              #14

              For the OpenHAB users: take a look at the MQTT eventbus. This is really cool!
              I'm using OpenHAB 2 with the MySensors binding and currently three serial gateways. From OpenHAB 2 the messages are send to the MQTT broker to Node Red.

              So:
              Serial gateway <-> OpenHAB 2 (with binding) <-> MQTT (Mosquitto) <-> Node Red

              UglyKidJoeU 1 Reply Last reply
              0
              • UglyKidJoeU UglyKidJoe

                @gohan

                Thanks for the quick response.

                It will be my first implementation of MQTT so I'm pretty much a blank canvas. I'll go with setting up the MQTT broker (server it's called now I believe) on my Raspberry Pi 3.

                Installing OpenHAB2 on the Pi has been made a breeze by an unattended installer called OpenHABian. Bundled with the installer is an MQTT option which should set it up (it's accessed via a menu).

                I'll be happy to share my lessons learned here, no doubt there will be a few :)

                I've still got to order a few sensors and boards etc to get started so it will take a little while. That;s why I read this thread to get an idea of how the components all talk to each other. That would at least help me determine what I need to buy upfront so I can get busy with it. Any advice would be appreciated (just to get a motion sensor up and running)

                I imagine it can become addictive!

                gohanG Offline
                gohanG Offline
                gohan
                Mod
                wrote on last edited by
                #15

                @UglyKidJoe
                I started with openhabian too, but I figured it's too complicated to start with. So now I moved to domoticz that's much simpler for beginners: at the moment I'm only using one ethernet gateway for sensors but I am planning to move to mqtt later on, after I learned better how to make sensors nodes.

                1 Reply Last reply
                0
                • hekH hek

                  Sidenote: MySensors has a Node RED plugin available as well. It's also a good alternative for tinkering/route messages from a MySensors network. Even more flexible then a raw MQTT broker.

                  UglyKidJoeU Offline
                  UglyKidJoeU Offline
                  UglyKidJoe
                  wrote on last edited by
                  #16

                  @hek

                  This got me interested so I looked at Node Red. Wow! I started looking at some youtube intros and it looks very good. So let the learning curve begin :)

                  I suppose the first challenge will be to figure out how the architectures relate to one another.

                  Would I be able to use Node Red with the OH2 Z-Wave binding as well as mysensors for instance? Similarly, OH2 controls my WEMO lights, so they will also play with Node Red via OH2?

                  I know these are real noob questions but it would be a huge help to get set off in the right direction

                  1 Reply Last reply
                  0
                  • T TimO

                    For the OpenHAB users: take a look at the MQTT eventbus. This is really cool!
                    I'm using OpenHAB 2 with the MySensors binding and currently three serial gateways. From OpenHAB 2 the messages are send to the MQTT broker to Node Red.

                    So:
                    Serial gateway <-> OpenHAB 2 (with binding) <-> MQTT (Mosquitto) <-> Node Red

                    UglyKidJoeU Offline
                    UglyKidJoeU Offline
                    UglyKidJoe
                    wrote on last edited by UglyKidJoe
                    #17

                    @TimO said:

                    So:
                    Serial gateway <-> OpenHAB 2 (with binding) <-> MQTT (Mosquitto) <-> Node Red

                    Interesting infrastructure. I would imagine there are endless possibilities with it. Thanks for the pointer :)

                    I got some homework to do on this, but looks like a helpful introduction video is here: here

                    1 Reply Last reply
                    0
                    • bgunnarbB Offline
                      bgunnarbB Offline
                      bgunnarb
                      wrote on last edited by
                      #18

                      @UglyKidJoe
                      I have been using OpenHAB and MQTT for a number of years now.

                      The reason for using MQTT and not just a serial connection from the MySensors GW is partly the flexibility as many have stated previously here. Easy to test, using e.g. the mqtt.fx tool. If you want to know what is going on you simply connect to the MQTT stream and "snoop" on the messages.

                      Another reason is that I am running three geographical sites on one OH installation. OH is running on a NUC at my home. There is also an MQTT GW here. Two other My Sensors MQTT-GW are running remotely in two summer houses. The three GW connect over internet to a cloud-based MQTT broker and OH connects to the same broker. In that way I do not have to open any ports into my home network for access should I have had a local MQTT-broker at home.

                      I have never been so busy since I retired!

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      24

                      Online

                      11.7k

                      Users

                      11.2k

                      Topics

                      113.1k

                      Posts


                      Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • MySensors
                      • OpenHardware.io
                      • Categories
                      • Recent
                      • Tags
                      • Popular