MQTT: switching to HAOS from Debian

Configuration Frontend
1

It’s driving me nuts. I’m trying to switch over to HAOS from a Debian/Supervisor installation and I can’t get rtl_433 to publish to the mosquitto broker. I can go into the rtl_433 log and I see the values for my sensors rolling past, but they’re not being published.

[rtl_433] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
[rtl_433] 
[rtl_433] time      : 2025-12-13 22:56:32
[rtl_433] model     : Acurite-5n1
[rtl_433] message_type: 56
[rtl_433] id        : 2482
[rtl_433] channel   : C
[rtl_433] sequence_num: 2
[rtl_433] Battery   : 1
[rtl_433] wind_speed: 0.0 km/h
[rtl_433] temperature: 54.5 F
[rtl_433] humidity  : 96 %
[rtl_433] Integrity : CHECKSUM
[rtl_433] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Thanks for any help, I’m probably missing something stupid, but Ive been stuck on this for days w/o any success.

2

How do you know?

3

Neither MQTT explorer or rtl_433 autodiscovery see any messages.

5

What does it say at the start of the log re MQTT connection?
Maybe post your RTL433 config

6

Make sure both the device and MQTT Explorer are connecting to the same broker. What hardware are you running RTL433 on? Can you ping it?

7

I was using the addon rtl_433. As I said, it didn’t seem to be sending any data to the addon mosquitto broker. I’m sure it was a configuration error on my part but moving on I spun up a debian container using proxmox and installed rtl_433. It’s happily sending data to my HA broker and all is well.

I tried dozens of config strings for the rtl_433 addon. It was a very frustrating experience.

OT: I’m pleased with my move from supervised on debian to haos. This glitch with mqtt was the only bump in the road!

8

I don’t understand the fascination with ProxMox or VMs on minimal hardware.

I run HAOS on bare metal.

  1. Flash the HAOS image to the boot drive.
  2. Reboot.
  3. That’s it. Done. No learning curve for Proxmox, Docker, VM’s. No USB or Network issue. No managing disk or memory allocations.
    The downside of bare metal? Your Home Assistant host computer is just that. Dedicated to one task. It just works.

If the user needs to run other programs on their Home Assistant server that aren’t available in an add-on, migrating to ProxMox can always be a solution later.

9

I run 4 always-on VMs on my (repurposed mac mini) proxmox server plus 2 that I run ad hoc basis; rookie numbers for someone with big iron. I find it to be very handy, but the learning curve is admittedly stiff.

10

Proxmox is not needed to run some Docker containers.