2.1 Install the Hub

1Connect RV-C. Connect the Hub to the coach’s RV-C bus using the correct LaunchControl cable, adapter, or harness for your RV.

2Connect power. Connect the Hub using the supported power connection for your installation. The hub can be powered from 12-24 V or USB-C. DO NOT CONNECT BOTH SIMULTANEOUSLY.

2.2 Connect to the Hub and set up Wi-Fi

1Join the Hub network. On your phone or tablet, open Wi-Fi settings and join LaunchControl-Hub-XXXX. The XXXX identifies your Hub. A new Hub has no hotspot password.

2Open the setup page. It should appear automatically, similar to a hotel Wi-Fi login. If it does not, open a browser and try 192.168.4.1 or launchcontrol.local

3Follow the on-screen setup steps. If you want to access through your RV or home Wi-Fi, add that network under Settings > Network.

4Bookmark the dashboard. When you are on the same RV/home network as the Hub, use http://launchcontrol.local.

2.3 Choose security settings

The first time you open the dashboard, LaunchControl offers two optional security layers: a Dashboard PIN and a password for the Hub’s own hotspot. You can set either one now or configure them later under Settings → Network.

• Dashboard PIN — protects the web dashboard when accessed from networks you have not marked as trusted.

• Hotspot password — protects the Hub’s private Wi-Fi network with WPA2.

2.4 Verify RV-C data before continuing

Before loading or building a dashboard, confirm that the Hub can actually see the coach devices.

1Open Settings → Status.

2Find the RV-C row. It should show that the RV-C bus is connected (green) and that data is being received (>0 frames/sec).

3If RV-C is not active, stop here. Check Hub power and the physical RV-C connection before adding devices or cards. Use the FAQ for coach-specific connection guidance. It doesn’t hurt anything if the RV-C L & H wires are reversed, it just won’t work, so you can try swapping those. Just don’t swap RV-C and power wires!

2.5 Load a floor plan (recommended)

A floor plan is a complete pre-built LaunchControl configuration for a specific coach. If one is available for your make and model, use it before spending time adding devices or building dashboards manually.

1Go to Settings → Floor Plans.

2Browse to your manufacturer and model. Select the plan and review its description.

3Press Load. The Hub restarts with the supported devices, panels, cards, and bindings configured for that coach.

4Review the dashboard. Confirm that the panels and controls match your installation.

2.6 No floor plan available? Build the coach manually

If your coach does not have a published floor plan, the setup path is still straightforward: discover the equipment first, then create dashboard cards and bind those cards to the fields you want to display or control.

1Scan and add RV-C devices. Open Devices, choose Add a Device → Add RV-C Device, scan the bus, then name and add the equipment you recognize. See section 3 for details.

2Create or choose a dashboard panel. Enter dashboard edit mode. Add a panel if you need one, or work in an existing panel. See section 4 for details.

3Add a card. Choose + Add Card, select the card type, name it, and choose its size/layout.

4Bind the card. Choose the device and field or fields that provide the card’s live data and controls. Structured cards such as Thermostat expose named slots for items such as mode, setpoint, and fan.

5Arrange and repeat. Move cards into the layout you want, then repeat for the rest of the coach.

6Create a backup. When the dashboard is working correctly, go to Settings → System → Backup and save a copy.

The system is ready for use. For customizations, continue with Chapter 3.

3.1 RV-C devices

RV-C devices are the coach’s built-in equipment: lights, tanks, thermostats, pumps, awnings, slides, generators, and similar systems. Use Add a Device → Add RV-C Device to scan the bus, identify active devices, name them, and add them to LaunchControl. A loaded floor plan performs this work for supported equipment.

3.2 Victron equipment

If your coach has a Victron GX device such as a Cerbo GX, LaunchControl can read and control supported Victron equipment including MultiPlus inverter/chargers, battery monitors, solar chargers, GPS, and temperature sensors.

1Enable MQTT services on the Cerbo GX device: Settings → Integrations → MQTT Access On

2Open Settings → Integrations. Enable the MQTT broker and enter the Cerbo IP address and port (1883) then save. A user name and password is not required for this integration. Scroll down and enable the Victron GX integration. Auto-discover the Portal ID and save. Confirm the MQTT Broker and Victron GX integrations both show connected.

3Open Devices and run a Victron scan. Add the discovered equipment. LaunchControl can also create matching dashboard cards.

3.3 Bluetooth sensors

The Hub can listen directly to supported Bluetooth broadcasts without normal Bluetooth pairing:

• Victron Instant Readout — SmartShunts, SmartSolar chargers, and similar supported devices can broadcast readings directly, so a Cerbo is not required for those values.

• Ruuvi tags — battery-powered temperature and humidity sensors suitable for locations such as a refrigerator or outdoor reading.

Turn Bluetooth on in Settings → Integrations, restart the Hub when prompted, then add discovered sensors from the Devices page.

3.4 Starlink

The Starlink card can show dish state and local statistics including connectivity, obstructions, ping success, and throughput. Enable Starlink in Settings → Integrations. If the card is also bound to a switched power circuit, its toggle can control dish power.

3.5 GL.iNet travel router

With a supported GL.iNet router such as the Beryl or Slate family, the Travel Router card can show the active uplink, signal strength, and internet reachability. Tap the card to scan for and join campground or home Wi-Fi without opening the router administration page. Enter the router admin password once under Settings → Network.

3.6 Custom MQTT devices

Advanced users can add devices that publish to an MQTT broker. Map MQTT topics to LaunchControl fields for card bindings; writable topics can accept commands. This provides a general integration path for equipment that LaunchControl does not support natively.

4.1 Panels

• Panel tabs — switch between groups such as Main, Power, and Climate. Each panel has its own name, icon, and layout.

• Graph History — each panel sets the history window used by graphs on that panel.

• Panel editing — panels can be added, renamed, reordered, duplicated, and deleted from edit mode.

4.2 Edit mode: arrange the dashboard

1Enter edit mode from the dashboard.

2Use + Add Card. Choose a card type, name, size/layout, and device bindings.

3Drag cards to reposition them. Cards snap into the dashboard grid.

4Use a card’s gear menu. Edit, resize, or remove the card.

5Exit edit mode. The layout is stored on the Hub and is used by phones, browsers, and Touch 8 displays.

4.3 Card gallery

Victron-specific cards appear after the Victron integration is configured. In device pickers, Victron entries are grouped separately so they are easy to identify.

4.4 Binding cards to devices

A card shows live data because it is bound to a device field. When you add or edit a card, LaunchControl provides a list of functions associated with the card. Select the device field that should be mapped (bound) to that function. Floor-plan cards normally arrive already bound.

4.5 Graphs

Solar, Battery + Power, Alternator, temperature, and similar cards can draw a small history graph. The Hub stores the history, so it remains available after the browser is closed and appears consistently on every display. The panel Graph History setting selects how much graph history should be shown.

4.6 Look and feel

• Themes — choose the dashboard appearance in display settings; Touch 7 follows the dashboard theme.

• Units — the Hub-wide Imperial/Metric setting covers temperatures, pressures, and speeds. Individual Victron devices can override units when needed.

• Background regions — optional tinted regions can visually group related cards on a panel.

5.1 Lighting

The Lighting card provides whole-coach lighting controls:

• Inside / Outside masters — tap to switch each group on or off. Press and hold a master to bring that group to full brightness.

• Four scenes — one-tap lighting scenes such as Evening or Movie. Set the lights as desired, then press and hold a scene to save.

• Automation badge — run lighting on a schedule from the card settings.

Individual lights can use Light Dimmer cards with on/off and brightness control.

5.2 Climate

The Thermostat card is available as a wide card, a large dial, or a compact tile. The dial shows current room temperature and the selected setpoint. Tap the compact tile to open the full mode, fan, and setpoint controls.

5.3 Device Off-timers

Many on/off cards can start a device with a countdown timer to automatically turn off the device when the time expires. Press and hold a device to start the timer. Tap the device again to cancel the timer (device remains on).

5.4 Sleep Timer

The Sleep Timer card turns selected devices off at the same time every night. Choose the devices, set the time, and arm the timer.

6.1 Automation rules

An Automation card watches one sensor and acts when the reading crosses a threshold.

• Sensor — any supported RV-C or Victron reading such as battery percentage, voltage, or temperature.

• Trigger — above or below a value, optionally held for a selected period so a short excursion does not fire the rule.

• Release — a second value where the rule resets. The gap between trigger and release prevents rapid on/off cycling.

• Actions — up to four actions on trigger and four on release, including device switching, lighting masters, and thermostat changes.

The card shows whether the rule is armed and whether it is currently triggered. Tap the card to enable or disable the rule. Common templates can pre-fill the editor.

6.2 Macros

A Macro card runs up to four actions with one tap. For example, an Away macro might switch off the water pump and lower the thermostat; a Return macro can reverse those actions. Configure the action list in the card settings.

7.1 Set up a Touch 8

1Power the display. It shows a QR code.

2Scan the QR code with your unlocked phone. Join the temporary setup network it offers.

3Follow the display setup page. Connect the display to the Hub.

4Finish. The display downloads the dashboard and reconnects automatically after future restarts.

7.2 Use the Touch 8

• Panel tabs — switch panels just like the web dashboard.

• Card controls — toggles, sliders, thermostat controls, lighting scenes, and timers work like their web versions.

Touch 8 is a control surface, not a configuration interface. Device setup, card editing, schedules, scenes, and automations are configured in the web dashboard.

7.3 Choose which devices it uses

The Touch 8 asks the Hub for semantic roles such as “the battery,” “the water pump,” or “the climate zone.” The Hub normally resolves those roles from your dashboard cards automatically. If the coach has multiple devices that could fill the same role, use Settings → Displays to choose which card each Touch 8 should use. (in a different room for example)

7.4 If the Hub changes

If the Hub is reset or its hotspot credentials change, the display can return to its QR setup screen while continuing to retry the previous connection. If the Hub returns with the original credentials, the display rejoins automatically; otherwise pair it again.

8.1 Set up a Mini

1Power the display. It shows a QR code.

2Scan the QR code with your unlocked phone. Join the temporary setup network it offers.

3Follow the display setup page. Connect the display to the Hub.

4Finish. The display downloads the dashboard and reconnects automatically after future restarts.

8.2 What it shows

• A status face with essential power, temperature, and device controls. A long press will toggle devices. A longer press will start a device timer.

• A sleep timer page

• A master lighting page

• A climate page with thermostat controls

• A detailed power page

• A vehicle leveling page (long press to calibrate)

• A Settings page

• A night friendly large clock that can be set very dim with essential coach information

• Two buttons for additional quick controls

8.3 Choose which devices it uses

The Mini asks the Hub for semantic roles such as “the battery,” “the water pump,” or “the climate zone.” The Hub normally resolves those roles from your dashboard cards automatically. If the coach has multiple devices that could fill the same role, use Settings → Displays to choose which card each Mini should use.

9.1 Saved Wi-Fi networks

The Hub remembers up to 8 networks in priority order. At boot, and whenever it is disconnected, it joins the highest-priority saved network it can see. It also periodically checks for a higher-priority saved network. Reorder the list or forget networks you no longer use.

9.2 The Hub hotspot

The Hub always broadcasts LaunchControl-Hub-XXXX. Touch 8 and Mini displays use this network, and it is the guaranteed direct-access path if the RV router is unavailable. A WPA2 password can be configured under Settings → Network.

9.3 Backup & restore

Settings → System → Backup downloads one file containing panels, cards, devices, lighting scenes, schedules, display assignments, and automations. Save a backup after significant configuration work. This contains all the same data as a Floor Plan and may be shared with others.

9.4 Clock & time

Schedules and timers need valid time. The Hub can use time from RV-C, Victron GPS, or a manual setting. The Clock & Time page shows available sources and lets you select which source to trust. Timezone and DST settings apply to the GPS and NTP sources. System time can be published back to the RV-C bus so your factory panels always have the correct time.

9.5 RV-C Tools

RV-C Tools provides a live, decoded view of traffic on the coach control bus. It is intended for diagnosis and advanced troubleshooting, such as confirming what a particular device is transmitting.

A logger may be started to record a few minutes of RV-C data which may be useful for analysis.

10.1 Dashboard PIN

The Dashboard PIN is 4–32 digits. LaunchControl requests it only on networks the Hub does not trust. Mark your own RV/home network as trusted to avoid repeated prompts while still protecting access from an untrusted campground network.

10.2 Hotspot password

The Hub hotspot can use a WPA2 password of 8–63 characters. Saving a new password restarts the hotspot and disconnects anything currently using it.

10.3 Locked out?

Power-cycle recovery provides a way back in without a cable or support call:

• 3 quick power cycles — opens the hotspot for 2 minutes so you can reconnect. The Dashboard PIN still applies.

• 5 quick power cycles — clears both the Dashboard PIN and hotspot password so you can set new ones.

Only rapid cycles during the startup window count. Normal power interruptions do not accumulate into a reset.

11.1 Update the system

1Open Settings → System → Update and select Check for Updates. The phone or computer running the browser needs internet access. The Hub does not require internet access to update.

2Review the available versions and release notes.

3Select Update All. Update order is handled automatically.

4Wait for completion. The Hub restarts, then touchscreen updates are delivered through the Hub. The page reports each result.

11.2 Safety nets

• The Hub and each display keep the previous firmware alongside the new version and can fall back if the new firmware does not start correctly.

• A display that cannot be reached is skipped and does not block the rest of the update.

• The Update page accepts a firmware file for manual fallback, and each display has its own basic update page.

14.1 Architecture in one paragraph

The Hub connects to the coach RV-C bus (CAN at the physical layer), decodes bus traffic into a live device model, and serves the dashboard locally over HTTP. Dashboard state changes are pushed over WebSockets. Touch 8 subscribes to the dashboard card model so it can mirror the configured panels and cards, while Mini asks the Hub for semantic roles such as “the battery.” Commands flow back through the Hub, which is the only LaunchControl device that transmits on RV-C.

14.2 Hardware

14.3 Versions

Each component reports its own vMAJOR.MINOR.BUILD version in Settings → Status and on the Update page. Hub, Touch 8, and Mini can version independently, while releases are verified as a compatible set.

14.4 Network details

• Friendly names — launchcontrol.local (mDNS/Bonjour), launchcontrol-xxxx.local (per-device name), the DHCP hostname launchcontrol-xxxx, and http://launchcontrol on Windows.

• Hub hotspot — the Hub is 192.168.4.1 on its own hotspot. Touch 8 and Mini displays live on this private network.

• Network separation — the Hub does not route traffic between its hotspot and the RV/home router network.

• Captive setup portal — the automatic setup portal exists only on an unconfigured Hub. After commissioning, the hotspot behaves as a normal local network.

14.5 Glossary

14.6 Understanding RV-C Devices, DGNs, and Instances

RV-C is the communication network used by many RV systems to share status information and commands between devices. The specifications can be found on the RVIA web site. Rather than each device having its own dedicated connection to LaunchControl, devices communicate over a shared two-wire RV-C bus.

At a basic level, LaunchControl identifies RV-C information using two important pieces: a DGN and an instance.

DGN — Data Group Number

A DGN (Data Group Number) identifies the type of RV-C message being sent. You can think of it as describing the function or category of information.

Examples include data groups for:

Lighting dimmers

Tank levels

Thermostats

Water pumps

Battery information

Generator status

A DGN does not necessarily represent one physical device. The same DGN can be used by many devices of the same type.

The instance identifies which device or function the message belongs to when several use the same DGN.

For example, an RV may have several dimmable lights:

DGN Instance Example Device

Lighting Dimmer 22 Kitchen Overhead

Lighting Dimmer 24 Bedroom Light

Lighting Dimmer 32 Main Ceiling

Lighting Dimmer 35 Bench Light

All four lights use the same lighting-dimmer message type, but each has a different instance number so the system can tell them apart.

Suppose the Main Ceiling light is represented by the lighting-dimmer DGN with Instance 32.

When that light reports its current brightness, LaunchControl sees a lighting status message for Instance 32 and updates the corresponding device.

When you move the brightness slider on a LaunchControl dashboard, the Hub sends the appropriate lighting command for Instance 32. Other dimmers using the same DGN ignore the command because it is not addressed to their instance.

This is why a single RV-C device type may appear several times when LaunchControl scans the bus.

Status and Command DGNs

Some RV-C functions use separate DGNs for status and commands. A lighting dimmer, for example, may report its current state using a lighting status DGN while accepting on/off or brightness changes through a related command DGN.

LaunchControl handles these relationships for you. In normal use, you simply add the discovered device, give it a meaningful name such as Main Ceiling, and bind its fields to a dashboard card.

Device Fields

Within a device, LaunchControl exposes individual pieces of information as fields. Such as a dimming level of a light, or the mode of the thermostat.

Dashboard cards are then bound to these fields. For example, a Climate card might bind its mode control to the mode field of a thermostat device.

The Device > Edit > Expert mode will expose additional device fields and allow for changing the field name and unit rounding as well as changing the calculated offset and multiplier (which are set by default to the RV-C specification).

You normally do not need to know the underlying DGN or instance numbers. LaunchControl discovers and manages them automatically, but understanding the relationship can be helpful when identifying devices or troubleshooting an RV-C installation.