Chapter 1

Overview

Your CampMatic speaks MQTT. So does Home Assistant. Part of your data will therefore show up all by itself, the rest needs a few lines of configuration. This page explains why — so you know what the next chapters are for.

4 minutes Last verified: 22.09.2026 DE EN

What you end up with

Before we start — this is what your motorhome looks like in Home Assistant once you have worked through this guide. Heating and hot water switchable, the gas supply at a glance, indoor climate and battery with history over days, plus the connection status of your box.

Figure 1.1The finished CampMatic dashboard, built from cards that ship with Home Assistant — no extra software needed. The Truma LevelControl figures are example values. Screenshot from the German edition.
It takes about half an hour
Getting there is twelve chapters, but most of them are short. If all you want is the heating, you are done after chapter 5 — the Bluetooth sensors come afterwards and can be tackled one at a time. We supply the finished files to paste in.

Two halves

The Truma heater and everything built into the CampMatic announces itself to Home Assistant. Once the connection is up, those entities are simply there — room temperature, water temperature, energy mix, operating state, onboard voltage and around forty more. You do not write a single line for them.

The optional Bluetooth sensors behave differently. Gas bottle (Mopeka), indoor climate (Ruuvi), battery monitor (BM2) and Truma LevelControl send their readings on their own topics without announcing themselves. For those you create the sensors once, by hand. That sounds worse than it is: we supply the finished file, you replace your device number in it.

Why not everything automatically?
Some of these sensors only send raw bytes. The gas bottle, for instance, does not report a percentage but an ultrasonic time of flight. The maths happens later — server-side in the CampMatic app, and in Home Assistant at your end. The upside: new bottle types and recalibration work without a firmware update.

How we connect

Home Assistant needs an MQTT broker. We recommend the official Mosquitto broker add-on — it runs in your home and fetches your CampMatic readings from our server. This guide follows that route throughout.

The benefit: a broker in your own home shrugs off brief internet outages, works with several CampMatic devices at once — and above all, everything else you run over MQTT keeps working.

Why that matters
Home Assistant allows exactly one MQTT connection — a second one cannot be added. So if you already run a broker at home, say for Zigbee2MQTT, Shelly or Tasmota, and swap it for another one, you cut off all of those devices. They are not deleted and they keep running — Home Assistant simply stops listening, and you can no longer switch them.

With a broker of your own the question never arises: CampMatic just joins in.

What we tested this on

Every step in this guide was carried out on a freshly installed system. What you read here, we saw ourselves. The versions:

Versions tested text 
Home Assistant OS         18.2
Home Assistant Core       2026.9.2
Supervisor                2026.09.2
Mosquitto broker add-on   7.1.1  (Mosquitto 2.1.2)
CampMatic firmware        1.28

Verified on               22 September 2026
Careful with other guides
Nearly every guide on the internet points to Home Assistant at http://…:8123. On current versions of Home Assistant OS that is no longer true — the interface runs on the normal web port, and 8123 only holds a redirect. If a link leads nowhere, just drop the port number.

Everything as a download

All files used in this guide are also available as one package. You can grab them individually in each chapter — if you would rather have the lot at once, take this:

campmatic-homeassistant-en.zip text Download 
campmatic-homeassistant-en.zip

  README.txt                   the short version and the common pitfalls
  campmatic.conf               bridge configuration      -> chapter 4
  campmatic-package-en.yaml    all sensors               -> chapters 6 to 11
  campmatic-dashboard-en.yaml  ready-made dashboard      -> chapter 12
The files will not run unchanged
Every file contains placeholders you need to replace with your own values — device number, credentials and the slot numbers of your sensors. The next chapters explain which ones and where to find them. The README in the package sums it up.
What you need
  • A running Home Assistant you have administrator access to
  • Your CampMatic credentials — we fetch those in the next chapter
  • About half an hour for the full run-through