search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.26k stars 4.81k forks source link

Better messages (or docs) for "MQT: Connect failed" error #8275

Closed fdcastel closed 4 years ago

fdcastel commented 4 years ago

Have you looked for this feature in other issues and in the docs?
Yes. It appears that this information used to be in https://github.com/arendst/Sonoff-Tasmota/wiki/MQTT-Overview#status-codes (source)

However, since the migration for the new documentation site, I cannot found it anymore. There is nothing in the MQTT section neither in the MQTT commands documentation.

Is your feature request related to a problem? Please describe.
Yes. One of my devices is not connecting to MQTT with the error message

"MQT: Connect failed to xxxx:1883, rc 5. Retry in 10 sec"

being a novice user, I can just wonder what the problem is. Actually, it took some time until I noticed that "rc 5" was something informative.

Describe the solution you'd like
A better error message describing the real problem, without cryptic codes. Like

"MQT: Connect failed to xxxx:1883 (invalid password). Retry in 10 sec"

Alternatively, a table in the documentation explaining what the codes mean would be an acceptable compromise :wink:.

Describe alternatives you've considered
Looked at tasmota source code. Found this table.

Yes. It solved my problem. But now I'm worried that other users may lost the same amount of time I did looking for this info.

Additional context
BTW: a lot of useful information was lost with the deactivation of the GitHub Wiki. I already crossed with several links like this one which now simply redirect to the main GitHub project page. Please consider reactivate the old wiki, even if in some kind of "read-only" mode.

(Please, remember to close the issue when the problem has been addressed)

Jason2866 commented 4 years ago

You are invited to improve the documentation. It is Open Source too and users can contribute. How is explained in the docu šŸ˜€

P.S. The old outdated wiki was long time read only availiable. Google directed always too. So only way was to close the old.

Please check the Contributing Guideline and Policy and the Support.

Thanks.

Support Information

See Documentation for more information. See Chat for more user experience. See Community for forum. See Code of Conduct

device111 commented 4 years ago

I also don't like the output of error Number. i think, we could do this in a better Log message with text. i will release a PR.

Jason2866 commented 4 years ago

Imho, Space waste of flash

ascillato commented 4 years ago

@fdcastel

Hi, please, help us and add this table to the docs. Thanks.

hheimbuerger commented 3 months ago

Seems like there has been a regression? Now in 2024, I'm getting this again:

08:11:36.306 MQT: Connect failed to localhost:1883, rc -2. Retry in 60 sec

Using "Tasmota 14.1.0 (release-tasmota32)". But it's my very first time having any contact with Tasmota and I've done zero further research, so take with a grain of salt.

OP, thanks for linking to the table, that provided me with what I needed.

fdcastel commented 3 months ago

@hheimbuerger I don't think this is a regression.

This issue was closed because the table containing the MQTT error codes was added to the docs (via #543).

It seems Tasmota developers chose not to change the error messages to reduce the firmware size (a sensible decision, IMHO).

hheimbuerger commented 3 months ago

@fdcastel You're right, my bad. I saw the merged docs PR and thought it was a code commit.

I wish these ten strings would appear in the logs, but I cannot judge how tight your space limitations are.

I've resolved my issue. I was just confusing my own network architecture. šŸ™„ Thanks!