Read 433 MHz sensors

Sensors Updated 2026-05-27

RF-HUB reads 20+ different 433 MHz sensor protocols and picks up the sensors automatically as soon as they send their first signal. You don't need to specify brand or model — RF-HUB identifies the protocol from the signal itself.

Supported sensor types

Thermometers and hygrometers:

  • Oregon Scientific — protocols v1 (THR128, THR238), v2 (THGR122/228/268, BTHR918), v3 (THGR810, RGR968)
  • UPM — WT450, RTGR318, RGR126, RFA1 and others
  • Telldus Temp — FineOffset-based temperature sensors sold by Telldus
  • TFA Dostmann — weather stations (Oregon-compatible)
  • MarQuant — generic FineOffset1 sensors
  • Mandolyn — no-name models (FineOffset)
  • Everflourish — certain models

Weather stations:

  • Bresser 5-in-1 and 7-in-1 — temperature, humidity, wind, rain, air pressure
  • Rubicson — Bresser-compatible
  • Froggit, Ventus — Bresser/FineOffset derivatives

Rain gauges:

  • MtxRain / Jula / Schou / Motonet / ADE — same protocol, sold under different brands

Motion and door sensors:

  • MarQuant PIR — sold by Clas Ohlsson, Biltema
  • Nexa — motion sensors, magnetic contacts
  • Everflourish — certain models

Where do I see the sensors?

  • RF-HUB web interfaceDevices: each sensor is shown as a card with the current values (e.g. 21.1°C, 4.6 mm for a rain gauge)
  • Home Assistant via MQTT auto-discovery — the sensors appear as entities without any configuration
  • Homey (Pro, Bridge or Cloud) via our Homey app and the qtrl.me cloud
  • Signal tab in the RF-HUB web interface — for debug, shows raw pulse patterns

What RF-HUB shows per sensor

  • Values — temperature, humidity, wind, rain, battery status etc.
  • RSSI — signal strength (see the range guide)
  • Low-battery flag — some sensors report a low battery level
  • Last received signal — time since the sensor last transmitted

Sensor not showing up — troubleshooting

  1. Wait a few minutes — sensors typically transmit every 30 to 60 seconds, some only every 5 minutes.
  2. Insert fresh batteries — weak batteries give a weak transmission, both RSSI and correct decoding suffer.
  3. Move the sensor closer to RF-HUB temporarily — if it appears then, you know the problem is range.
  4. Trigger the sensor manually — for PIR: wave in front of it; for thermometer: move in or out for a temperature change.
  5. Check the Signal tab — if you see incoming pulse patterns but no sensor — the protocol may not be supported. Contact us and we'll be happy to add support.

My sensor isn't in the list

Two possibilities:

  • It uses one of the supported protocols anyway — many cheap sensors are "white labels" of the same protocol. Just try it — if the sensor appears as e.g. "MarQuant", it works.
  • It's a new protocolcontact us and we'll be happy to add support. Please send the model name and a picture of the back.

RF-HUB's CustomMatch function is made for remotes (one button = one signal), not for sensors that send varying data. For sensors, real protocol support is needed.