Chapter 4

Connecting to CampMatic

Now we link your broker to ours. It fetches your device readings and stores them locally — Home Assistant never notices and simply treats them as its own. That takes a file of about twenty lines. One of them matters more than the rest.

7 minutes Last verified: 22.09.2026 DE EN

The bridge file

Create the file /share/mosquitto/campmatic.conf — with the File editor or Terminal & SSH. Replace the four placeholders with your values from chapter 2.

/share/mosquitto/campmatic.conf conf Download

# CampMatic -> Home Assistant
connection campmatic-<GERAETE_ID>
address campmatic.de:8883
bridge_capath /etc/ssl/certs

remote_username <MQTT_USER>
remote_password <MQTT_PASSWORT>

# Your own client ID. It must NOT match the one your device uses,
# nor that of a second Home Assistant installation.
remote_clientid ha-bridge-<GERAETE_ID>

cleansession false
start_type automatic
notifications false
try_private false

# Readings and commands for your device
topic # both 0 campmatic/<GERAETE_ID>/ campmatic/<GERAETE_ID>/

# The entity announcements — see below
topic homeassistant/+/<NODE>/# in 0

Encryption without uploading a certificate

The line bridge_capath /etc/ssl/certs is all it takes. Our broker uses an ordinary certificate your system already trusts — nothing to upload, nothing to confirm. We verified this on a fresh installation.

Read-only instead of control

If you would rather not be able to operate anything from Home Assistant, change both to in in the second-to-last line. Readings then only flow towards you, and a stray click cannot fire up the heater.

The line everything depends on

The last line of that file is the single most important one in this guide:

Without this line, not one entity is created conf

topic homeassistant/+/<NODE>/# in 0

Your device does not announce its entities under your topic prefix. Following MQTT convention it uses homeassistant/… instead, and there under the device ID from chapter 2. That sits outside campmatic/<GERAETE_ID>/ and is therefore not covered by the line above it.

The classic symptom

If this line is missing, or the device ID in it is misspelled, every reading arrives — you can watch them come in — but Home Assistant creates not a single entity. People then suspect the bridge or the sensor and look in entirely the wrong place.

Where the device ID comes from

Use the Device ID from the CampMatic app for <NODE> — Status page, Device Status block. Not the three-digit device number and not the display name. See chapter 2.

Check the connection

Save the file and restart the add-on. Saving alone will not do — the file is only read at startup. The log then shows:

Add-on › Log text

Loading config file '/share/mosquitto/campmatic.conf'
Bridge support available.
TLS support available.
Connecting bridge campmatic-<GERAETE_ID> (campmatic.de:8883)

**Figure 4.1**The Log tab after the restart. The line that matters is "Connecting bridge" with your device number. The "Protocol error from ::1" line above it is harmless. Screenshot from the German edition.

Give it a moment after a restart

Right after restarting the add-on some values will read unavailable for a few minutes. The Bluetooth sensors only transmit every few seconds to minutes and their values are not buffered. This sorts itself out.

Before you move on

The file sits at /share/mosquitto/campmatic.conf
The log shows Connecting bridge with your device number
The last line contains your device ID, not the device number
You restarted the add-on after saving