Announcement

Collapse
No announcement yet.

No MQTT topics from WLED

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    No MQTT topics from WLED

    Looking for some help to resolve an issue with my new WLED / mcsMQTT setup.

    None of the MQTT topics for WLED are being received and none show in the Association table. This is a new mcsMQTT install and is NOT something that was working before then stopped.
    • mcsMQTT v5.2.4.9 installed on HS3 v3.0.0.548.
    • Statistics show zero MQTT Received & Accepted by mcsMQTT -and zero MQTT Received & not Accepted by mcsMQTT.
    • HS3/mcsMQTT/LWT is published by mcsMQTT with online payload and is displayed in the auto association table. Table does not show any other topics.
    • Enabled MQTT on nodemcu WLED and set broker to the HS3 IP on port 1883, same as mcsMQTT broker port on HS3.
    • WLED MQTT username and password are empty. WLED device topic is set wled/deviceid and Group topic is set wled/all.
    • Saved and rebooted. Reconfirmed all settings retained.
    • mcsMQTT is set to discover all published MQTT topics and auto create.
    I rebooted nodemcu and HS3 several times and restarted, uninstalled, reinstalled mcsMQTT plugin while trying to figure out the issue. I confirmed WLED broker IP is the HS3 IP and can ping nodemcu WLED from HS3.

    No errors in debug log:
    • 6/1/2020 3:11:31 PM 4 | mcsMQTT Version 5.2.4.9 running at <PATH>, HS is at <PATH>
    • 6/1/2020 3:11:31 PM 8 | mcsMQTT InitHW ComputerName= <NAME>, IOEnabled=False
    • 6/1/2020 3:11:31 PM 79 | mcsMQTT Debug InitHW Database Ready
    • 6/1/2020 3:11:31 PM 83 | mcsMQTT Debug Receive Ready
    • 6/1/2020 3:11:31 PM 83 | mcsMQTT Debug Trigger Ready
    • 6/1/2020 3:11:31 PM 115 | HW Init Complete
    • 6/1/2020 3:11:31 PM 116 | Background Init Started
    • ....
    • 6/1/2020 11:55:30 PM 31438515 | HSEvent VALUE_CHANGE| 1024| | 262| 260| 347
    • 6/1/2020 11:55:31 PM 31439315 | HSEvent VALUE_CHANGE| 1024| | 262| 262| 347
    • 6/1/2020 11:55:32 PM 31440515 | HSEvent VALUE_CHANGE| 1024| | 264| 262| 347
    • 6/1/2020 11:55:33 PM 31441315 | HSEvent VALUE_CHANGE| 1024| | 264| 264| 347
    • 6/1/2020 11:55:34 PM 31442518 | HSEvent VALUE_CHANGE| 1024| | 266| 264| 347


    #2
    Statistics show zero MQTT Received & Accepted by mcsMQTT

    set broker to the HS3 IP on port 1883, same as mcsMQTT broker port on HS3.
    Do you have a broker setup on your HS3 computer? Does the first row of the statistics tab show that mcsMQTT is online with the broker?

    If you want mcsMQTT to be the broker then you need to leave the Broker IP field blank.

    mcsMQTT is set to discover all published MQTT topics and auto create
    Topic wled/# is one of the special case topic where you likely do not want auto create as you will get many devices that are not of interest. mcsMQTT will auto create the typically used devices setup publish topics and status icons are also setup for the special case wled topic.

    Comment


      #3

      Do you have a broker setup on your HS3 computer? Does the first row of the statistics tab show that mcsMQTT is online with the broker?

      If you want mcsMQTT to be the broker then you need to leave the Broker IP field blank.
      Hi Michael. Yes, the first row on the Statistics tab shows mcsMQTT is online with date/time and run time. Where I have a broker IP set is on WLED's MQTT config. IP is set to the HS3 computer where mcsMQTT broker is running.



      Topic wled/# is one of the special case topic where you likely do not want auto create as you will get many devices that are not of interest. mcsMQTT will auto create the typically used devices setup publish topics and status icons are also setup for the special case wled topic.
      On HS3, under the mcsMQTT General tab I've changed 'Enable Auto Device Creation' so it's now disabled.

      I rebooted nodemcu WLED and no topics came through. I then restarted the mcsMQTT plugin and that also didn't help. Do you think there's an issue with WLED and it's not publishing anything to the broker? Not sure if there's a way to monitor and determine if that's the issue.

      Thanks!

      Comment


        #4
        I have my own mqtt client for debugging, but there are several in the public domain. Mqtt explorer is a popular one.

        i believe there is a enable mqtt checkbox just above the broker ip in the WLED setup. Take a look to confirm it is set.

        you can post or email to mcsSolutions at CenturyTel dot net Your config for mcsMQTT which is at /Config/mcsMQTT.ini and I can see how it works at my end.

        Comment

        Working...
        X