mqtt select calls' timeouts cluttering debug level logs (IDFGH-7893)

[KaeLL]

• IDF version: 36f49f3

Problem Description

Do these really need to be DEBUG rather than VERBOSE?

D (16:26:43.753) TRANSPORT_BASE: poll_read: select - Timeout before any socket was ready!
D (16:26:43.754) TRANSPORT_BASE: poll_read: select - Timeout before any socket was ready!
D (16:26:43.754) mqtt_client: esp_mqtt_handle_transport_read_error: transport_read(): call timed out before data was ready!

Setting these components' log level to INFO would hide other relevant DEBUG level logs.

[moefear85]

the timeouts are logged using the "TRANSPORT_BASE" tag, not "mqtt_client", so just use:

esp_log_level_set("TRANSPORT_BASE",ESP_LOG_NONE);

but place it after all setup so it doesn't get changed back.

[KaeLL]

@moefear85 🤔

Again I ask: do these really need to be DEBUG rather than VERBOSE?

[moefear85]

I'm neither a contributor nor maintainer... but you can search for the error message in vscode (or use grep) , then simply replace ESP_LOGD with ESP_LOGV. most likely it would be a one-liner edit.

[KaeLL]

@euripedesrocha

[euripedesrocha]

@KaeLL this was already fixed in IDF 5.2, but looking closely to your new logs that are few other places in the mqtt client that have similar behavior. I'm fixing it.

Thanks for reopening.

[AxelLin]

@euripedesrocha
IDF 5.0 and 5.1 still need fix.

[AxelLin]

@euripedesrocha IDF 5.0 and 5.1 still need fix.

@euripedesrocha
There is no update for IDF 5.0 and 5.1.
Now I'm wondering if you stop maintaining esp-mqtt for older release branches?

[euripedesrocha]

@AxelLin we didn't stop maintaining 5.0 and 5.1 branches. We just decided to not backport this at the moment. I'll reassess and maybe start the backport process. Sorry for let you request without an answer.