A RuuviTag in your motorhome or campervan measures temperature, humidity and air pressure. That is easy while you are standing next to it. But if Home Assistant runs at home and the van sits in winter storage or on a pitch, nothing arrives: Bluetooth only reaches a few metres.
This article shows how the readings still get into your Home Assistant and which entities you end up with. The individual steps are in our Home Assistant guide.
The essentials
- The route: a CampMatic box in the vehicle reads the RuuviTag over Bluetooth and sends the readings over WiFi or 4G via MQTT to your Home Assistant, wherever it runs.
- What arrives: temperature, humidity, air pressure and the tag's battery voltage.
- Effort: set up an MQTT bridge and add the Ruuvi sensors once in YAML. We supply the templates, you only replace placeholders.
- Cost: no subscription. App and server are free.
Why not straight over Bluetooth?
Home Assistant can only read Bluetooth sensors within radio range of its own Bluetooth hardware. That works while the motorhome and Home Assistant are side by side. If the van is somewhere else, in winter storage, on a pitch or on the road, something in the vehicle has to read the sensor and pass the readings on.
That is the CampMatic box's job. It reads the RuuviTag in the vehicle and delivers the readings via MQTT to your Home Assistant. You also see them in the CampMatic app and on Telegram, even when Home Assistant is down. You do not need a Ruuvi Gateway for this (Integrations: RuuviTag).
What you need
- A CampMatic box in the vehicle. Every box reads the RuuviTag: CampMatic Guard (sensors only, for any camper, powered via USB), CampMatic for Truma CP Plus and CampMatic for Truma iNet X. Each box pairs up to eight Bluetooth sensors (FAQ), several RuuviTags included.
- A RuuviTag. It is not included.
- Home Assistant with admin access and the Mosquitto broker add-on.
- Internet in the vehicle: WiFi for the WiFi variant, your own SIM card for the 4G variant (not included, IoT SIM from about €2 a month).
Getting the RuuviTag into Home Assistant
- Pair the RuuviTag. Set the tag up once with the manufacturer's Ruuvi app. Then, in the CampMatic app, go to Settings → Devices → Add device and choose the Ruuvi environment sensor. Tags in range usually appear within a few seconds. Pairing happens in the CampMatic app, not in Home Assistant (Help: External Devices).
- Get your credentials. The Status page of the CampMatic app has the card “MQTT Bridge (Home Assistant)” with broker, port, username, password and topic prefix; the Device Status block shows the Device ID (chapter 2).
- Set up Mosquitto. Install the add-on, create the folder
/share/mosquittoand only then switch on thecustomizeoption. The other way round, the add-on no longer starts (chapter 3). - Create the bridge. The file
/share/mosquitto/campmatic.confconnects your broker to ours. Replace the placeholders, restart the add-on, and the log must show “Connecting bridge”. If you never want to switch anything from Home Assistant, useininstead ofbothin the topic line (chapter 4). - Read your slot number. In the MQTT integration, listen to
campmatic/<GERAETE_ID>/+/config. In theruuvi/configline, the number afterslotbelongs to your tag. Slots run across all sensor types and cannot be guessed (chapter 8). - Add the sensors. The ready-made Ruuvi sensors go into the package file
/config/packages/campmatic.yamlundermqtt: sensor:. Replace<GERAETE_ID>and<SLOT_RUUVI>, check the configuration, restart Home Assistant (chapter 10). You switch on the packages folder once, as described in chapter 6.
The guide puts the full run-through at about half an hour. All files are also available there as a single download.
Which readings arrive
Each reading has its own MQTT topic following the pattern campmatic/<GERAETE_ID>/ruuvi/tag_<SLOT_RUUVI>/…. The names on the right come from our template:
| Reading | Topic ends in | Sensor in the template |
|---|---|---|
| Temperature (°C) | temp_c | Indoor Temperature |
| Humidity (%) | humidity | Indoor Humidity |
| Air pressure (hPa) | pressure_hpa | Indoor Pressure |
| Tag battery (V) | battery_v | Indoor Sensor Battery (diagnostic) |
| Signal strength | rssi | Indoor Signal (in the download package) |
The Ruuvi also sends acceleration on three axes (accel_x, accel_y, accel_z), a movement counter (moves) and a sequence number (seq). Add them the same way if you need them. With several RuuviTags, say in the living area and in the fridge, you create the sensors once per slot number, each with its own name.
Three things worth knowing:
- Readings come at intervals. The Bluetooth sensors usually report only every 6 minutes, and the readings are not buffered. After a restart they are missing for a few minutes. To check, listen to
campmatic/<GERAETE_ID>/ruuvi/#for at least 10 minutes. - No stale values: if nothing arrives for 45 minutes, the templates show the sensor as “unavailable” instead of holding on to the last value.
- Local air pressure. The Ruuvi measures the pressure where it sits. In the mountains the value is therefore much lower than in the weather forecast.
Automation ideas
- Frost warning: if Indoor Temperature stays below a few degrees for a while, Home Assistant sends you a message. With the box for Truma CP Plus the same automation can also switch on the heater (chapter 7). In that case check the heater's operating status, not just the switch. With the box for Truma iNet X you control the heater in the CampMatic app.
- Keep an eye on the fridge: a second tag in the fridge tells you when the temperature there rises.
- Humidity over days: the humidity history shows whether the habitation area stays too damp.
For a simple alert you do not need Home Assistant: the CampMatic app notifies you via the app, Telegram or email as soon as a threshold is reached. Home Assistant pays off for your own rules and for linking the van to the rest of your home.
Dashboard and troubleshooting
The ready-made dashboard from chapter 14 has an “Indoor Climate” group with temperature, humidity, air pressure and a history graph. It needs no extra cards. Delete the cards for sensors you do not have.
If a value stays empty, it is usually one of these (chapter 15):
- Empty reply on
+/config: no sensor is paired. That happens in the CampMatic app. - A single sensor without a value: usually the wrong slot number. It can change after re-pairing.
- Several sensors permanently “unavailable”: check whether
mqtt:appears more than once in your package file. Then only the last block counts. - New sensors without a value: do a genuine restart of Home Assistant. Reloading the configuration is not enough.
Frequently asked questions
I do not have a Truma heater. Does this still work?
Yes. That is what CampMatic Guard is for: it monitors gas, leisure battery and interior climate but does not control a heater. It needs no Truma connection.
What about the leisure battery?
A BM2 battery monitor gets into Home Assistant the same way: Adding a BM2 battery monitor to Home Assistant.
→ CampMatic Guard · WiFi — €89
Further reading: