search

warp-more-hardware / esp32-firmware

TinkerForge WARP software for more hardware
16 stars 1 forks source link

MQTT: Error while Connecting, "Not Authorized" #59

Open Kleinheribert opened 11 months ago

Kleinheribert commented 11 months ago

MQTT: Not Authorized, but correct Username/Password

MQTT: Keine Verbindung möglich, trotz Username/Passwort korrekt

Describe the bug

No Connection to my MQTT Broker (Mosquitto on HA) due to failed Authorization. Log from MQTT Broker: 2024-01-05 11:32:35: New connection from 192.168.0.93:53706 on port 1883. error: received null username or password for unpwd check 2024-01-05 11:32:35: Client Wallbox disconnected, not authorised. 2024-01-05 11:32:50: New connection from 192.168.0.93:53707 on port 1883. error: received null username or password for unpwd check 2024-01-05 11:32:50: Client Wallbox disconnected, not authorised. 2024-01-05 11:33:05: New connection from 192.168.0.93:53708 on port 1883. error: received null username or password for unpwd check 2024-01-05 11:33:05: Client Wallbox disconnected, not authorised.

To Reproduce

Steps to reproduce the behavior:

  1. Enter MQTT Credentials
  2. Activate MQTT in Webserver
  3. Wallbox reported "connected to Broker"
  4. See in Logfile: Password for MQTT User is always "null", but entered many times.

Expected behavior

MQTT authorization and auto-discovery

Screenshots & Logfiles

debug-report-AC011K-10052109275264-2024-01-05T11-40-41-156.txt debug-report-AC011K-10052109275264-2024-01-05T11-39-16-334.txt

Versions:

Additional context

It seems the MQTT password entered on the Webinterface couldn't be saved successfully. So my MQTT Broker denies the Authorization.

almera8 commented 2 months ago

FYI I have a very long password for my Home Assistant MQTT addon. I couldn't get it to work. I now have a new MQTT broker with a short password in proxmox and that works. I copy the information from this broker to my HA broker for use of EVCC (not sure how that's called).