I’m working with the contact closure push notification (PR58-1_MQTT_2002) for use with MQTT over wifi.
I am trying to connect it to an MQTT broker, running CirrusLink’s MQTT Distributor module in Ignition.
The device connects successfully when I enable anonymous MQTT connections, but fails when authentication is required.
I’ve verified that the correct username (admin) and password are configured on the device.
The broker logs show that while the username is being sent, the password is missing in the MQTT CONNECT packet:
This suggests that the device is not sending the password at all, even though it’s configured. Is there a known issue/firmware update that addresses this?
Hi Alex,
These devices have been on the market for a couple of years now. I did just test with a broker which requires a username and password just to check and it definitely works. The password is being submitted to the broker correctly.
One thing I was thinking though is do you have special characters in the password? If so can you try with only alpha numeric characters?
Thank you,
Travis Elliott
You’re right that the device definitely works, that is why I am eager to configure the device as I have noticed a couple of topics related to problems very similar to mine however none have a clear solution defined in them, so hopefully we can provide that solution with this case study.
I went ahead and tested a password with alpha numeric characters (aruba55) and the result was the same.
I can use my username & password on MQTT Explorer, but not with the ncd gateway or MQTT.fx.
After some research, I found out that my broker is not compatible with MQTT.fx because the open source client tool utilizes MQTT 5.0 whereas MQTT Distributor is compliant with the MQTT 3.1.1 standard.
does your device operate on MQTT version 3.1.1 or, the latest, MQTT version 5.0? if it is 5.0 I believe that is why it will not connect to my server as it’s version 3.1.1. (or maybe something else)