No MQTT after backup restore

Configuration
1

Hello experts,

I am having problems with MQTT.

I built my PI4 in a Geekworm case with SSD and power management board and set it up again.

Then I restored a backup.

Pretty much everything is going fine, but the MQTT broker does not want to receive any data.

In the LOGs of the MQTT broker it says
that he gets a connection, but when I monitor the relevant topics, nothing arrives.

1639038697: New connection from 192.168.178.7 on port 1883.
1639038697: New client connected from 192.168.178.7 as heatronic (p1, c0, k10).
1639038697: Client heatronic disconnected.

The MQTT user and password have been properly restored by the backup and nothing has been changed on the server.

The server also sends decent data.

Does somebody has any idea?

By the way, here’s my configuration.yaml.
Maybe there’s an error in it.

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

sensor:
  - platform: mqtt
    name: "Heizung Aussentemperaturfühler"
    unique_id: "heatronic_aussen"
    unit_of_measurement: "°C"
    state_topic: "home/heizung/aussen"
    state_class: "measurement"
  - platform: mqtt
    name: "Warmwasser Sollwert"
    unique_id: "heatronic_ww_soll"
    unit_of_measurement: "°C"
    state_topic: "home/heizung/ww_sollwert"
    state_class: "measurement"
  - platform: mqtt
    name: "Warmwasser Istwert"
    unique_id: "heatronic_ww_ist"
    unit_of_measurement: "°C"
    state_topic: "home/heizung/ww_istwert"
    state_class: "measurement"
  - platform: mqtt
    name: "Fußbodenheizung Istwert"
    unique_id: "heatronic_fbh_ist"
    unit_of_measurement: "°C"
    state_topic: "home/heizung/fbh_vorlauf_ist"
    state_class: "measurement"
  - platform: mqtt
    name: "Fußbodenheizung Sollwert"
    unique_id: "heatronic_fbh_soll"
    unit_of_measurement: "°C"
    state_topic: "home/heizung/fbh_vorlauf_soll"
    state_class: "measurement"
  - platform: mqtt
    name: "Heizungsmischer Stellgroesse"
    unique_id: "heatronic_mischer_y"
    unit_of_measurement: "%"
    state_topic: "home/heizung/mischery"
    state_class: "measurement"
  - platform: command_line
    name: CPU Temperatur
    command: "cat /sys/class/thermal/thermal_zone0/temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | multiply(0.001) | round(1) }}'
    scan_interval: 10

http:
  server_port: 8123
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1
    - 192.168.178.7
    - 192.168.178.8
    - 192.168.178.0/24

google_assistant: !include g_ass_integr.yaml

spotify:
  client_id: ********************************
  client_secret: ********************************

binary_sensor:
  - platform: mqtt
    name: "Heizungsbrenner"
    unique_id: "heatronic_brenner"
    state_topic: "home/heizung/brenner"
    payload_on: "1"
    payload_off: "0"
  - platform: template
    sensors:
      alexa_ha_drucker_schalten:
          friendly_name: "Alexa HA - Drucker"
          device_class: garage_door
          value_template: "{{ is_state('input_boolean.alexa_ha_drucker_schalten', 'on') }}"

switch:
  - platform: rpi_gpio
    ports:
      13: RPI Ventilator

climate:
  - platform: generic_thermostat
    name: RPI Kühlung
    heater: switch.rpi_ventilator
    target_sensor: sensor.cpu_temperatur
    min_temp: 45
    max_temp: 75
    ac_mode: true
    target_temp: 65
    cold_tolerance: 0.1
    hot_tolerance: 0.1
    min_cycle_duration:
      seconds: 30
    keep_alive:
      minutes: 5
    initial_hvac_mode: "cool"
2

Did you ever find a solution to this? I restored from a backup today and now none of my mqtt stuff is working.

3

Same here. Had a sd card die and mqtt won’t work after restore from backup.

4

My issue was that, after restore, the MQTT clients needed to have authentication. I ended up rewriting my scripts to use auth and things began working. It’s odd that the auth requirement didn’t have them stop working before.

5

It’s late 2023 and I am having the same problem. I switched from a Pi4 to a Pi3 by creating a new SD card with the Pi3 image and then restoring from backup. None of my MQTT automations work anymore. I’ve removed and reinstalled the MQTT server, rebooted, and then tried to rework one of the MQTT based automations. Nothing works.

For background, I am using Shelly devices to publish their state to MQTT and then use that as a trigger for automations. I have the switches in detaced mode so the power to the bulbs is always on. This worked fine until the restore from backup on the new Pi.

This seems like a bug that should be addressed for others in the future.

I STILL don’t have my lights working again so I have to use the app to switch the lights on and off, which is annoying but works.

6

I’m in the same boat. Upgraded to raspberry pi 5, got everything else working but my MQQT devices. spent a few hours trying to delete the addon and integration, starting over, but no luck. neither the old devices or mqqt explorer can connect. the logs show the attempted connection, but it immediately disconnects. it doesnt appear to the a username/password issue, since if I purposely put an incorrect user or pw, it will show an authorization error instead.

Went back to my older hardware/setup, and luckily it is still working.

Spent a couple days on this now and can’t figure this out. Anyone figure it out?