does the contact closure push notification for use with MQTT operate on MQTT version 3.1.1 or, the latest, MQTT version 5.0?
It runs on 3.1.1
Let me know if your password contains any non alpha/numeric characters.
thanks for the information, now I know that my edge node and MQTT network are both compliant to the same MQTT version.
I went ahead and tested a password with alpha numeric characters (aruba55) and the result was the same.
It is hard to imagine why I keep getting this as the device is capable of connecting to my broker, so I will include me gateway settings as well.
I have been trying to crack this problem for quite a while, so anything helps!
I really don’t have any idea why that’s happening. I tested with the temperature/humidity mqtt sensor which shares the same code base as the push notification but let me test the push notification specifically to see if somehow it has an issue the Temperature sensor does not.
Thanks, Travis - I really appreciate you going as far as looking into the code of the device. Let me know what you find when you test it specifically. Happy to provide any additional info on my end if needed.
Hi Alex,
I just did a full test with the push notification MQTT unit to make sure it is properly submitting username and password for basic authorization with the broker. Everything is working properly with my MQTT broker when credentials are required. I tested no credentials, username only, and username and password required.
One thing to note I would set Operation Mode setting to 1 so the input change is always published immediately to the broker. Otherwise in the default mode of 2 it will only report when the internal input change counter exceeds the Report Count threshold(I think it’s set to 10 by default so you would have to trigger the input 10 times for it to publish to the broker).