Announcement

Collapse
No announcement yet.

Trouble with 5.5.2.0 on 4.1.6.0 (Pi4) Standard

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

    Trouble with 5.5.2.0 on 4.1.6.0 (Pi4) Standard

    Hi,

    After having this working earlier in the day, I lost MQTT functionality. Restarted, restarted plugin, re-entered credentials, install mosquito utilities and verified I could talk with my server from the command line (no issues in connectivity)...

    Debug file shows the following:
    9/18/2020 11:04:01 PM 963 | Spawning MQTT Threads
    9/18/2020 11:04:01 PM 982 | mcsMQTT Debug MQTT Ready
    9/18/2020 11:04:01 PM 996 | MQTT Thread Started with broker 1 192.168.2.25, Shutdown=False, Disconnect=False, Client=False, Connected=False
    9/18/2020 11:04:01 PM 1000 | MQTT Thread Not Connected Yet
    9/18/2020 11:04:01 PM 1000 | Calling MQTTclient for Broker 1
    9/18/2020 11:04:01 PM 1003 | MQTT Thread Client Created for Broker 1
    9/18/2020 11:04:01 PM 1003 | MQTT Thread Client ID=mcsMQTT on PicardPi42M
    9/18/2020 11:04:01 PM 1003 | Calling MQTT Connect
    9/18/2020 11:04:01 PM 1003 | Pre-connect oMQTTClient(0) is Nothing=False
    9/18/2020 11:04:01 PM 1015 | MQTT Thread Broker 1 192.168.2.25 Connect Response=5
    9/18/2020 11:04:01 PM 1015 | MQTT Broker 1 Connection Refused not authorized, Connected=False to broker 192.168.2.25
    9/18/2020 11:04:11 PM 11016 | Calling MQTTclient for Broker 1
    9/18/2020 11:04:11 PM 11016 | Calling MQTT Connect
    9/18/2020 11:04:11 PM 11017 | Pre-connect oMQTTClient(0) is Nothing=False
    ...etc...

    the same credentials used in a mosquito_pub works fine.....
    One issue I did notice - I touched the MQTT Broker Security set to None. Afterwards I get a pop-up saying 'None is invalid selection for SSL'

    Any help is appreciated.

    Thx,
    -Stan

    #2
    A further note - any setting for Broker Security results in the same Pop-Up.

    -Stan

    Comment


      #3
      What is the security level you are using. Username/password, SSL certificates, or open? The status 5 on the attempt to connect to broker means login authorization failure. Make certain you type in your password if updating from an older mcsMQTT version as the method to encrypt into mcsMQTT.ini changed earlier this year.

      Comment


        #4
        User/Password.
        mosquitto_pub with -u and -P with the same info works. The ini had the password in clear text...?

        -Stan

        Comment


          #5
          Strangely, after I entered the password in the web page again, it now shows online in the stats page. However, the errors still show in the log file (yes with the correct times).

          Looked at the ini - password is now stored as dec numbers with dots. I went to install page and disabled then re-enabled - and it started working.....I wish I could say what happened....

          Case closed - I think...

          BTW - Thanks for the quick response.

          -Stan

          Comment


            #6
            That was the problem I was having, the password in the INI file was clear text. Only in my case it also went to 100% CPU after a few minutes. But I was able to get into change settings and set the password and it did manage to log in to the broker. I had to do it a couple of times. It still went to 100%, but after a disable and enable of the plug-in, all seems to be well. I am happy to have mcsMQTT working again. I'm running Linux with Mono 6.12.0.90 and HS4 4.1.9.0.

            Comment

            Working...
            X