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. Development
  3. MQTTClient Qos 1

MQTTClient Qos 1

Scheduled Pinned Locked Moved Development
2 Posts 2 Posters 1.3k Views 3 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.
  • G Offline
    G Offline
    gok
    wrote on last edited by
    #1

    I've been playing around with the GatewayW5100MQTTClient from the MySensors 1.6 Beta, using DHCP.

    There are a couple of things that I think would improve it: (I've prototyped most of them)

    Item 1:
    Ability to optionally use URL rather than IP address (have implemented for TCP)

    Item 2:
    If gateway IP address is DHCP assigned, I think that the gateway should be calling Ethernet.maintain() as part of the bool gatewayTransportAvailable() call.

    Item 3:
    Ability to send messages from gateway with QOS value 1 - this is really important as it allows the MQTT server to store messages for mqtt clients when they are disconnected. When the clients come back on line they will be delivered all stored messages for their subscription (assuming they subscribed with QOS 1)

    As the standard PubSub client doesn't implement this, I have prototyped this by merging in code from https://github.com/knolleary/pubsubclient/pull/100 - although this implementation required a couple of minor fixes and I'm still testing.

    Item 4:
    Ability to send messages with 'retained' flag set. So that new mqtt clients will get 'last sensor values' and also 'sensor and node presentation' messages when they connect.

    Item 5:
    Reduce the size of the PubSubClient code to just the necessary stuff to reduce size.

    Does anyone have any thoughts on this?

    1 Reply Last reply
    1
    • T Offline
      T Offline
      tante ju
      wrote on last edited by
      #2

      I'm in favor of this.

      I would add Item 6: Have (configurable) symbolic names for the values.
      I' using the gateway with FHEM where readings are automatically created and symbolic names are much easier to handle than the raw numbers. I've pacthed that in the version I'm using, but a general approach would be great.

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


      20

      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