-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(0.1.2) MQTT connected -> connection failed -> connected .. #8
Comments
To eliminate the possibility that incorrect credentials are being supplied, can you please use deliberately incorrect MQTT information in your config file and see whether you get the same behavior? |
I had a similar issue when setting up the add-on recently. Regardless of the credentials, it would always give me the connection error regardless of whether or not credentials were correct. I had a single quote (') in my mqtt password, and tried enclosing the password in double quotes, but it still would give me the connection error. Once I changed to an alpha-numeric password, everything worked fine. |
@bommel947 Looking at ninja1283's comment above - does your MQTT password contain a single quote character by any chance? |
Nope. The pwd does not contain a single quote character |
I had same issue as bommel947, but I found when I removed the pound sign '#' from my password, MQTT connection was successful. Looking at the log file, the message would truncate at the # suggesting the pound sign was being interpreted as the beginning of a python comment |
Yeah. That could bei the reason. I also have a pound sign in my password!!
Gene LeSage ***@***.***> schrieb am Fr., 16. Juli 2021, 14:55:
… I had same issue as bommel947, but I found when I removed the pound sign
'#' from my password, MQTT connection was successful. Looking at the log
file, the message would truncate at the # suggesting the pound sign was
being interpreted as the beginning of a python comment
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK6HAY57XKSE55KCV3IWMQTTYAT4RANCNFSM45EL435A>
.
|
@deviantintegral and @pbkhrv, while you're troubleshooting the proper escapes for special characters, would it also be possible to add the ability to use data stored in the Home Assistant secrets file? |
I had a similar problem. Using a dash in the mqtt broker's username made the service fail to connect to the broker with the same errors: Example, using a username of "mqtt-service" causes this problem to occur. A username without the dash "mqttservice" does work though. |
Edit: Disregard. Using what I thought was the right password...apparently not. Also, the feature request in #18 does not seem to work as it tries to parse the secrets "${username}" format as the actual configuration values. |
I believe this is fixed since the |
Hi,
When I launch the addon (0.12) I see that it is successfully connecting to the MQTT broker.
But right after that it says "MQTT error 5" - which I suppose is an authentication problem.
It stays in the loop "connected -> connection failed -> connected ..."
Needless to say that the credentials are verified (mqtt lens)
Any help is very much appreciated!
Thank you!
The log shows me:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting rtl_433 -c /config/rtl_433/rtl_433.conf
rtl_433 version 21.05-1-ga773fd0a branch master at 202105091257 inputs file rtl_tcp RTL-SDR
Use -h for usage help and see https://triq.org/ for documentation.
Publishing MQTT data to 192.168.0.21 port 1883
Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".
Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".
Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".
Registered 157 out of 186 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-186 ]
Found Rafael Micro R820T tuner
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 250000 S/s.
Tuner gain set to Auto.
Tuned to 433.920MHz.
MQTT Connected...
baseband_demod_FM: low pass filter for 250000 Hz at cutoff 25000 Hz, 40.0 us
MQTT Connection error: 5
MQTT Connection failed...
MQTT Connected...
MQTT Connection error: 5
MQTT Connection failed...
MQTT Connected...
MQTT Connection error: 5
MQTT Connection failed...
MQTT Connected...
The text was updated successfully, but these errors were encountered: