Chapter 13
Troubleshooting
The things people actually trip over, sorted by what you see. Each one says what causes it and what helps.
No entity is created
Every reading arrives, yet no device in Home Assistant
By far the most common case. The announcement line is missing from the bridge file, or the device ID in it is misspelled:topic homeassistant/+/<NODE>/# in 0Check the spelling against the Device ID in the CampMatic app and restart the Mosquitto add-on afterwards. Saving alone will not do — the file is only read at startup.
The line is right and still nothing
Your CampMatic announces its entities when it connects. Disconnect the box from power briefly; on its next start it announces everything again. Sensors stay empty
Several sensors permanently read "unavailable"
First check whether the word mqtt: appears more than once in your campmatic.yaml. YAML allows each key only once — with several blocks only the last one counts and every sensor listed before it disappears.The nasty part: the configuration check reports no error, the entities stay visible, and when you listen in you can see the values arriving. People then search for a long time in the wrong place.
Correct is: one
mqtt:, one template:, everything else as a list beneath them. Shortly after a restart
Right after restarting the add-on or Home Assistant the Bluetooth values are missing for a few minutes. They are not buffered and only arrive when the sensor next transmits. This sorts itself out — unlike the case above. After adding new sensors
New MQTT sensors only appear after a genuine restart of Home Assistant. Reload the configuration instead and you will see them listed, but permanently without a value. A single sensor without a value
Then the slot number is usually wrong. Read it again with campmatic/<GERAETE_ID>/+/config — it can change when a sensor is paired afresh. The heating cards are empty
Truma Heizung and Truma Wasser read "unavailable"
This is known and not your doing. While the heating is off the box sends nan as the setpoint, which Home Assistant cannot handle. The fix is the replacement sensors from chapter 6. After that you use the Hot Water selector instead of the automatically created card. Hot water cannot be set to 80 degrees
Quite right — for hot water the Truma only knows off, 40 and 60 degrees. That the automatically created card offers 80 is a display fault. The selector from chapter 6 offers only the three real options. Vario Heat: the heat level is displayed wrongly
On a Vario Heat the automatically created Truma Heizung card shows the fan mode permanently as „off", even while it is heating. Switching still works. Rely on the heat level selector instead, which shows the correct value.Also on Vario Heat: the levels are labelled Eco and High in Home Assistant, but the heater itself calls them Night and Auto. The labels are wrong, the effect is right.
Small things
The log keeps showing "Protocol error from ::1"
Harmless. That is the watchdog checking whether the broker responds. It appears in the log for as long as the add-on runs. Setpoint temperatures read "unknown"
Normal while heating and boiler are off. There simply is no setpoint then. The add-on will not start any more
If you have just switched on customize: the folder /share/mosquitto must exist beforehand. Without it the add-on quits immediately and only shows stopped. The log then says Unable to open include_dir. An entity is named differently than expected
Home Assistant strips diacritics: ü becomes u, ä becomes a. Since your device reports its entity names in German, "Truma Lüftermodus" ends up as select.<ENTITY>_truma_luftermodus. Copy entity names from Developer tools → States rather than typing them. Values only arrive now and then
The Bluetooth sensors transmit at intervals from seconds to minutes depending on type. On top of that it depends on the radio path — with the vehicle far away or metal in between, readings come in less often. You can display the signal strength of each sensor as a diagnostic value.
Still stuck?
- Get in touch through the contact form on the help page — ideally telling us which chapter you are stuck on and what the Mosquitto add-on log says.