Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. English
  3. ioBroker general
  4. Some states not published by MQTT-client, how to debug why?

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.2k

Some states not published by MQTT-client, how to debug why?

Geplant Angeheftet Gesperrt Verschoben ioBroker general
mqttmqtt-clientstatesecovacs-deebotdeebotozmo
2 Beiträge 1 Kommentatoren 617 Aufrufe 1 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Tomasz NowakT Offline
    Tomasz NowakT Offline
    Tomasz Nowak
    schrieb am zuletzt editiert von Tomasz Nowak
    #1

    Hi.

    I've already described my problem as MQTT-client issue here, please read:
    https://github.com/Pmant/ioBroker.mqtt-client/issues/34

    But I'm not sure if this is caused by MQTT-client adapter at all. Maybe Ecovacs-deebot adapter.... or my just lack of knowledge. Could somebody point me in some direction? How to find out why those four states are not published to Mosquito? Other are published fine. I also able to control Deebot with MQTT subscribe just fine.

    1 Antwort Letzte Antwort
    0
    • Tomasz NowakT Offline
      Tomasz NowakT Offline
      Tomasz Nowak
      schrieb am zuletzt editiert von Tomasz Nowak
      #2

      Anyone? Please!
      I have such a great integration with Loxone to be shared, but lack of that data would be just a shame :(

      8788d930-fa56-4c38-b355-c9ff8efda1f3-image.png

      I have already found that if I manually change value within ioBroker panel (for instance: remaining filter, from 92% to 90%) then the value gets published to MQTT instantly. But they don't get published upon MQTT-client adapter restart, despite setting publish - enabled ("changes only" is not checked). And as those values change very rarely, I would need to wait long tome to get them published for the first time....

      Any idea on workaround such as forcing initial publish of all mqtt-client configured values?

      Update: Seems I've sorted it out (kind of) with adapter author, see link below if interested
      https://github.com/Pmant/ioBroker.mqtt-client/issues/34

      1 Antwort Letzte Antwort
      0
      Antworten
      • In einem neuen Thema antworten
      Anmelden zum Antworten
      • Älteste zuerst
      • Neuste zuerst
      • Meiste Stimmen


      Support us

      ioBroker
      Community Adapters
      Donate

      286

      Online

      32.4k

      Benutzer

      81.4k

      Themen

      1.3m

      Beiträge
      Community
      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
      ioBroker Community 2014-2025
      logo
      • Anmelden

      • Du hast noch kein Konto? Registrieren

      • Anmelden oder registrieren, um zu suchen
      • Erster Beitrag
        Letzter Beitrag
      0
      • Home
      • Aktuell
      • Tags
      • Ungelesen 0
      • Kategorien
      • Unreplied
      • Beliebt
      • GitHub
      • Docu
      • Hilfe