Re: [rtl_433] Digest for rtl_433@googlegroups.com - 1 update in 1 topic

11 views
Skip to first unread message

Steve Wilson Jr

unread,
Jul 19, 2026, 12:30:35 PM (5 days ago) Jul 19
to rtl...@googlegroups.com
Use helpers. Set up a helper that combines them and updates on the latest change of either. Then point whatever uses the data at the helper instead of one sensor or the other.

There is an option when you go to add a helper to Combine the state of several sensors,

image.png



On Tue, Jul 14, 2026 at 8:49 PM <rtl...@googlegroups.com> wrote:
Greg Troxel <g...@lexort.com>: Jul 14 04:26PM -0400

I was pointed to
 
https://rtl-433-hass.github.io/rtl_433/latest/
 
and it looks interesting.
 
I have two small/old computers running rtl_433 in different places.
Both of them listen to 433. Each runs rtl_433_mqtt_relay and I have
hand yaml for entities. This results in the 433 entities having data if
either radio is powered on and can hear the radio.
 
Is there a way to fuse multiple receivers with the integration?
You have received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to rtl_433+u...@googlegroups.com.

Greg Troxel

unread,
Jul 19, 2026, 12:57:34 PM (5 days ago) Jul 19
to Steve Wilson Jr, rtl...@googlegroups.com
Steve Wilson Jr <steve.w...@gmail.com> writes:

> Use helpers. Set up a helper that combines them and updates on the latest
> change of either. Then point whatever uses the data at the helper instead
> of one sensor or the other.
>
> There is an option when you go to add a helper to Combine the state of
> several sensors,

I could, but I think this is a bandaid on an architecture problem.
There is one transmitter out there, and there are redundant radios
receiving it. Logically we should be modeling the transmitter as a
single device, and it's an artifact of the HA rtl_433 integration that
you end up with two devices, as children of different "hubs".

Sorry if it wasn't clear that I was asking if there was a way to make
the integration represent them as one device from the start, and that I
didn't clearly exclude coping strategies that didn't address the root
cause.

The corresponding situation would be if I had a sensor that reported
over BLE (like an Aranet, for example), and I had 4 esphome BLE proxies
scattered about. It would be a bug for that one physical device to show
up as 4 HA devices, one per proxy.

If I had two different temp sensors and I wanted to treat them as one
logical entity in HA, then the helper suggestion would be entirely
applicable.

Steve Wilson Jr

unread,
Jul 19, 2026, 1:13:16 PM (5 days ago) Jul 19
to Greg Troxel, rtl...@googlegroups.com
You'd have to statically assign your rtl-433 entities and in the config assign the same state-topic via mqtt to each radio on each PC. I would think that would do it as long as everything matches and your radios are assigned the same frequency per number assignment in the rtl_433.conf file.
Reply all
Reply to author
Forward
0 new messages