App & Integration Strategy

The connection layer for your vehicle.

OpenCamperCore is not another isolated solution. The app runs locally in the vehicle, works offline and connects what other systems cannot see: heating, lighting, water, energy, sensors, bus systems and climate.

Offline-firstNo cloud dependencyBrowser & DisplayGerman status messages

Local App

Runs in the vehicle, browser-based and offline-capable – on smartphone, tablet, display or browser. No cloud dependency, no internet required.

Heating, climate, lighting
Water, energy, sensors
Vehicle data & status
Clear status messages

Victron Integration

Victron remains the energy hub. OpenCamperCore extends it with vehicle technology, bus systems and devices that would otherwise not be clearly visible.

Cerbo GX / Venus OS
MQTT & Modbus TCP
Bidirectional data exchange
Extension, not replacement

Mastervolt prepared

The architecture is designed to connect further energy and data platforms later via defined device profiles, MQTT mapping and gateway modules.

Standardized device profiles
MQTT mapping prepared
Gateway module architecture
Planned integration direction

Victron Integration

Victron stays energy hub. OpenCamperCore connects the rest.

Connection to Victron Cerbo GX / Venus OS is made via MQTT and/or Modbus TCP. OpenCamperCore extends Victron with vehicle technology and bus systems – it does not replace Victron. Victron remains the energy manager, OCC connects additional vehicle technology.

Data from Victron → OCC

Battery & state of charge
Solar & generation
Charger & inverter
Tanks & temperatures
System status & alarms

Data from OCC → Victron

Tank levels (custom sensors)
Temperatures (1-Wire / Analog)
Switch states & relays
Heating status

Architecture

Open interfaces. One system.

The OCC Gateway connects vehicle devices via CAN, LIN, 1-Wire, I²C and Modbus. Data flows via MQTT, REST and WebSocket to the app, Victron, Home Assistant and Node-RED.

Vehicle devices

Heating · Lighting
Water · Climate
Sensors

CAN · LIN → 1-Wire · Modbus

OCC Gateway

Hardware Core

MQTT · REST → WebSocket

App

Browser · Display

Victron

Cerbo GX · Venus OS

Home Assistant

Automation

Node-RED

Flows & Logic

Future Integrations

Prepared for further energy systems.

The OCC architecture uses standardized device profiles and MQTT mapping so that further energy and data systems can be connected later without modification. Mastervolt / MasterBus systems are planned as an integration direction – via MasterBus gateways, CAN-based data transfer or MQTT bridges.

Standardized device profilesMQTT mappingGateway modulesMasterBus / NMEA 2000 preparedCAN-based data transferAchievable on project basis

Note: This integration is architecturally prepared but not yet available as a finished product.

Frequently Asked Questions

Questions about App & Integration

Does the app work without internet?

Yes. The OpenCamperCore app runs entirely locally in the vehicle. It requires no cloud connection and is fully offline-capable – even without mobile coverage.

Do I need Victron to use OCC?

No. OpenCamperCore works independently of Victron. The Victron integration is optional and can be added at any time when Victron hardware is present in the vehicle.

Can OCC send data back to Victron?

Yes. OpenCamperCore can return tank levels, temperature sensors, switch states and heating status to Victron Venus OS / Cerbo GX – making this data visible in the Victron dashboard.

Is Mastervolt / MasterBus fully integrated?

Not yet as a finished product. However, the OCC architecture is designed to connect Mastervolt / MasterBus systems via gateways, CAN data transfer or MQTT bridges. The integration is achievable on a project basis.

Can the integration be extended via update?

Yes. The modular architecture of OpenCamperCore allows new integration interfaces to be unlocked via firmware or software update – without hardware changes.

The App

Get to know the app

The OpenCamperCore app for iOS & Android – features, screenshots and beta access.

Go to the app →