Debug log has MQTT warning - Show more info for true debugging

[frspp]

Describe the MQTT enhancement

Problem: Data is not sent/delivered via MQTT. On another device similar (but not same) setup works, so guess there must be something in correct in this setup - what?

Logger:Debug gives

18:17:12 [W] [component:317] mqtt cleared Warning flag

But cannot see any details: which flag, why, more info?

Background info: I'm connected to webserver via wifi and cannot (easily) connect via USB as the data and trigger is coming via pins (power meter HAN RJ12 connection ( https://github.com/Beaky2000/esphome-p1mini ).

I read the docs, tried Googling but could not find an answer so seems like this feature is missing.

edit: Found the problem by experimenting with the code: "topic_prefix: null" instead of having a prefix here. No help from logs :(

Use cases

Anyone using MQTT and facing problems.

[ssieb]

It cleared the warning flag. You would need earlier logs to find out why it's set and logs around this line to see why it's cleared. Most likely, it's just mqtt connecting. You haven't said what the problem is or even if there is one.

[frspp]

Problem is data is not sent via MQTT. Use similar setup with another device ( Mitsurunner https://github.com/VeliML/MitsuRunner/blob/main/mqtt_Guru.yaml ) and in there it works. Only difference here - afaik - is the input data and but does not give errors on it.

Input data process:

interval:
  - interval: 60s
    then:
      - mqtt.publish:
          topic: current_phase_1
          payload: !lambda |-
            return esphome::to_string(id(cp1).state);
      - mqtt.publish:
          topic: current_phase_2
          payload: !lambda |-
            return esphome::to_string(id(cp2).state);
      - mqtt.publish:
          topic: current_phase_3
          payload: !lambda |-
            return esphome::to_string(id(cp3).state);
      - mqtt.publish:
          topic: momentary_active_import
          payload: !lambda |-
            return esphome::to_string(id(momentary_active_import).state);

Full log does not give any additional info:

18:17:11 [D] [switch:024]

'p1_rts' Turning OFF.

18:17:11 [D] [switch:063]

'p1_rts': Sending state OFF

18:17:11 [D] [switch:024]

'status_led' Turning OFF.

18:17:11 [D] [switch:063]

'status_led': Sending state OFF

18:17:11 [D] [P1Mini:223]

CRC verification OK

18:17:11 [D] [text_sensor:069]

'Meter ID': Sending state 'ADN9 7534'

18:17:11 [D] [sensor:103]

'Momentary Reactive Import': Sending state 0.00000 kvar with 3 decimals of accuracy

18:17:11 [D] [sensor:103]

'Momentary Active Export Phase 3': Sending state 0.00000 kW with 3 decimals of accuracy

18:17:11 [D] [sensor:103]

'Momentary Reactive Export Phase 3': Sending state 0.12100 kvar with 3 decimals of accuracy

18:17:11 [D] [sensor:103]

'p1mini WiFi Signal': Sending state -60.00000 dBm with 0 decimals of accuracy

18:17:12 [W] [component:317]

mqtt cleared Warning flag

18:17:21 [D] [P1Mini:137]

ASCII data format

18:17:21 [D] [switch:024]

'p1_rts' Turning OFF.

18:17:21 [D] [switch:063]

'p1_rts': Sending state OFF

18:17:21 [D] [switch:024]

'status_led' Turning OFF.

18:17:21 [D] [switch:063]

'status_led': Sending state OFF

18:17:21 [D] [P1Mini:223]

CRC verification OK

18:17:21 [D] [text_sensor:069]

'Meter ID': Sending state 'ADN9 7534'

18:17:21 [D] [P1Mini:293]

No sensor matched line '0-0:1.0.0(250824171720S)'

18:17:21 [D] [sensor:103]

'Cumulative Active Import': Sending state 7553.11816 kWh with 3 decimals of accuracy

18:17:21 [D] [sensor:103]

'Cumulative Active Export': Sending state 0.00000 kWh with 3 decimals of accuracy

18:17:21 [D] [sensor:103]

'Cumulative Reactive Import': Sending state 25.18400 kvarh with 3 decimals of accuracy

18:17:21 [D] [sensor:103]

'Momentary Active Export Phase 3': Sending state 0.00000 kW with 3 decimals of accuracy

18:17:21 [D] [P1Mini:404]

Cycle times: Identifying = 9770 ms, Message = 76 ms (7 loops), Processing = 142 ms (4 loops), (Total = 9988 ms). 705 bytes in buffer

18:17:21 [D] [switch:020]

'p1_rts' Turning ON.

18:17:21 [D] [switch:063]

'p1_rts': Sending state ON

18:17:21 [D] [switch:020]

'status_led' Turning ON.

18:17:21 [D] [switch:063]

'status_led': Sending state ON

18:17:21 [D] [sensor:103]

'p1mini WiFi Signal': Sending state -62.00000 dBm with 0 decimals of accuracy

18:17:22 [W] [component:317]

mqtt cleared Warning flag

[ssieb]

If you're using the same mqtt server as in the linked config, then you're not setting the topics up properly.

[frspp]

MQTT setup

# MQTT IOTguru
mqtt:
  broker: iotguru.cloud    # 159.69.149.145 # iotguru.cloud in Mitsurunner # mqtt.iotguru.cloud # OLD known IPs of iotguru.cloud 116.203.207.226, 195.201.219.208
  id: mqtt_client
  username: !secret mqtt_username # user short identifier
  client_id: !secret mqtt_client_id # device short identifier
  password: !secret mqtt_password # device key
 
  reboot_timeout: 60min   # default: 0s. 0s disables MQTT reboot_timeout

  topic_prefix: !secret mqtt_topic_prefix # without trailing slash. # 'pub/user_id/client_id/node_short_identifier'. Can be found from IoT Guru Field/Help under 'GENERIC MQTT TOPIC'
  log_topic: null       # default: null. no trace-logs over MQTT (function is not supported in IoT-Guru)
  discovery: false      # default: False. Set to false if HomeAssistant is not used. 

[frspp]

@ssieb thanks for the hint about incorrect topic. Found the problem by experimenting: using "topic_prefix: null" and instead putting prefix (seems like only) to payloads made the difference.

This feature request is still very valid as the log did not help forward: too little information.

[frspp]

never mind, i re-read the logger docs and understood that debugger is not the deepest log level.

[frspp]

Reopening as the even deepest log level does not provide any additional MQTT info, at least via wifi.

Use case again: Tried setting up a new connection, once again same "cleared flag" but not telling why the flag is set.

[ssieb]

You need to get serial logs if you want more info. The flag is set before wifi is connected and just means that mqtt isn't connected.