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. General Discussion
  3. MQTT_FIRST_SENSORID in MQTT Client Gateway Dev. Branch 1.5

MQTT_FIRST_SENSORID in MQTT Client Gateway Dev. Branch 1.5

Scheduled Pinned Locked Moved General Discussion
3 Posts 2 Posters 1.2k Views 1 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.
  • FotoFieberF Offline
    FotoFieberF Offline
    FotoFieber
    Hardware Contributor
    wrote on last edited by
    #1

    Today I tried to setup a test env for 1.5 Dev Branch

    With the 1.4 API I am using a patched MQTT Client Gateway which has a setting for the first id, that will be assigned to a node: MQTT_FIRST_SENSORID

    I couldn't find this setting in GatewayW5100MQTTClient of the dev branch. Where can this be set?

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

      The mqtt gateway in dev-branch is quite new and works on both ESP8266 and W5100 equipped AVR boards.

      Good that you've started testing it. I tried to clean up the previous community contributed versions but I might very well have missed a few things.

      Here is a summary of the changes:

      • The mqtt topic of the new version looks a bit different. Now it holds exactly the same information as the serial protocol. There's no longer any textual strings for VARs. They took up too much precious space and required unnecessary maintenance.
      • There is no longer any id-handout functionality in the gateway. This should be handled by the controller (or some other subscriber).
      • Internal commands from nodes (time-request and id-reguest) is send to the broker and someone must publish replies to these requests.
      • Other things like LED blinking and inclusion mode button should now work fine also for the MQTT gateway (when enabled).

      So, the gateway is much smaller (size-wise) and hopefully simpler to use now when documentation on the main site also reflects MQTT.

      1 Reply Last reply
      0
      • FotoFieberF Offline
        FotoFieberF Offline
        FotoFieber
        Hardware Contributor
        wrote on last edited by
        #3

        The nice thing about the MQTT Client Gateway form 1.4 was, that it was the controller too. :)

        If I need a controller, I will use node-red with the serial gateway. MQTT is then handled by node-red. :)

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


        18

        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