Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. ioBroker general
    4. Some states not published by MQTT-client, how to debug why?

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

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

    This topic has been deleted. Only users with topic management privileges can see it.
    • Tomasz Nowak
      Tomasz Nowak last edited by Tomasz Nowak

      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.

      tnowak created this issue in Pmant/ioBroker.mqtt-client

      closed Some states not published #34

      1 Reply Last reply Reply Quote 0
      • Tomasz Nowak
        Tomasz Nowak last edited by Tomasz Nowak

        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

        tnowak created this issue in Pmant/ioBroker.mqtt-client

        closed Some states not published #34

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Support us

        ioBroker
        Community Adapters
        Donate

        634
        Online

        31.8k
        Users

        80.0k
        Topics

        1.3m
        Posts

        deebot ecovacs-deebot mqtt mqtt-client ozmo states
        1
        2
        476
        Loading More Posts
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes
        Reply
        • Reply as topic
        Log in to reply
        Community
        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
        The ioBroker Community 2014-2023
        logo