1.1 Start with your task

You choose the names and organization of your equipment and panels. Names in this guide are examples.

Three useful terms: a device is equipment or a function in your RV; a card shows or controls it; a panel groups cards on the dashboard.

1.2 What’s in the system

The displays are optional. A Hub plus the web dashboard is a complete LaunchControl system.

1.3 How the pieces fit together

The Hub has four jobs:

• RV-C connection — the Hub connects physically to the coach control bus and reads or sends RV-C messages.
• Device integration — the Hub connects to other devices such as Victron equipment, Shelly devices and more through MQTT.
• LaunchControl network — the Hub creates its own Wi-Fi network for Touch 8, Mini, and direct phone/tablet access. The Hub can also join your existing Wi-Fi router so phones and computers on that network can open the dashboard without changing Wi-Fi networks.
• LaunchControl Remote — with the Hub on a network that has internet, the same dashboard is available from anywhere through remote.launchcontrol.tech, with no app and no router configuration. Every new Hub includes 90 days; see Remote Access.

1.4 How to use this guide

The guide is in five parts. Start here is the installation and setup path, in order; Using LaunchControl covers everyday operation; Customize the settings; Something isn’t working is organized by symptom; and the Advanced part holds the technical reference.

Deeper implementation information appears in shaded “Technical detail (optional)” boxes and in the Technical Reference. You can skip those sections during normal setup.

2.1 Before you start

Have the correct Hub cable or adapter for your RV, one supported power source, and a phone, tablet, or computer with Wi-Fi. Have your RV router’s Wi-Fi password available if you plan to use it.

• Required: connect and power the Hub, join its Wi-Fi, confirm preferences, add your equipment, and check the dashboard.
• Only if installed: configure Victron, Shelly, Bluetooth, or other integrations. Your RV’s built-in equipment may be all you need.
• Optional: add displays and enable LaunchControl Remote. Local control needs no internet connection or Remote subscription.

Choose a hotspot password before pairing displays if you plan to use one. You can also set it later and pair the displays again.

2.2 Connect 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. The Hub can be powered from 12–24 V or USB-C. Use only one power source at a time.

2.3 Join LaunchControl

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 steps. Agree to the product terms, then pick your units and confirm your time zone — both are filled in from your phone, and the phone’s clock sets the Hub’s time so schedules work from the first day. Then connect the Hub to your RV or home Wi-Fi, or choose Set Up Without Wi-Fi.

4Finish. The last screen offers Control your coach from anywhere: set a Dashboard PIN and turn on LaunchControl Remote (see Remote Access). You can do this later from Settings → Integrations instead.

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

2.4 The setup guide

The first time the dashboard opens it shows Welcome to LaunchControl, seven steps with a check mark on each one that is done. It stays until the dashboard has cards, and it is always available afterwards under Settings → System → Setup guide. Whenever a step sends you to another page, that page shows a Setting up LaunchControl strip with the step you are on and a Back to setup button, and comes back by itself when the step is done.

1Connect to your RV. Done as soon as the Hub hears the RV’s control network. If it says the network was not detected, press Fix connection: check Hub power and the RV-C cable, and try swapping the two RV-C data wires. Reversed wires do not damage anything, they simply do not work. Never swap the RV-C and power wires. If all your equipment is Victron, Bluetooth or Shelly, this step becomes optional once that equipment is added.

2Preferences. Shows your units, time zone and whether the Hub’s clock is set. When the phone or computer you are using is in a different zone, Use this device’s time zone takes its zone; Change opens the settings. The Hub keeps its clock automatically from then on: internet time when it has it, otherwise the coach network, a GPS, or the browser that is open.

3Find your RV equipment. Find equipment opens the scan described in Add or Change Equipment: it adds the equipment, creates its cards and brings you back here. Load a Floorplan loads a ready-made setup instead, when one exists for your coach. Afterwards the step shows how many RV devices are configured, with Review and Find more.

4Additional equipment. Answer once: press Add other equipment and tick the systems your RV has — Victron, Bluetooth devices, Shelly or network devices, advanced integrations — or press None. Each system you tick gets its own Set up button that opens the right settings, finds the equipment, creates its cards and returns here. The question is asked once; the Hub remembers the answer.

5Dashboard. Completes by itself as cards are created. If something could not be added automatically, Review asks what each switched output is and creates the rest.

6Displays. Optional. Power a Touch 8 or Mini near the Hub to pair it automatically; the step then shows it as connected.

7Remote access. Shows whether LaunchControl Remote is on and linked. Optional.

When the required steps are done, including the Additional equipment answer, the guide reads LaunchControl is ready with Open dashboard. Displays and Remote never hold it up.

2.5 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.6 Load a floor plan (if one exists)

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 adding devices or building dashboards by hand.

A floor plan with Victron equipment still needs its Victron integration configured under Settings → Integrations, because passwords and integration IDs are unique.

1Go to Settings → Floor Plans. The setup guide’s Load a Floor Plan button takes you there.

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.7 No floor plan? Find your equipment

1Open Find equipment from the setup guide.

2Identify and name equipment. Operate one switch at a time in the RV, then choose its type in What is it?. Keep factory-useful names or use your own.

3Add the selected equipment. Add Equipment & Create Dashboard creates devices and their cards. Selected switched outputs need a type or No card before you can continue.

4Check the result. Confirm readings appear and each control operates the intended equipment. Arrange the cards whenever you are ready.

See Add or Change Equipment for the complete scan, identification, and integration procedures; see The Dashboard to arrange cards and panels.

2.8 Add displays and Remote

• Touch 8 and Mini displays connect to the Hub’s own Wi-Fi. A new display powered up near a single Hub joins it by itself; otherwise it shows a QR code to scan. See The Touch 8 Display and The Mini Display.
• LaunchControl Remote puts the same dashboard on the internet, in any browser. Settings → Integrations → LaunchControl Remote → Set up, then link the Hub to your account with Continue in browser or by scanning the QR code. Every new Hub includes 90 days of LaunchControl Remote; see Remote Access.

Setup is complete when the guide says LaunchControl is ready, your expected readings appear, and you have checked that controls operate the intended equipment. Continue with Controls for everyday use.

3.1 Choose the equipment you are adding

Use only the sections that match your installation. Built-in RV equipment may be your only source; integrations are optional.

3.2 RV-C devices

RV-C devices are the coach’s built-in lights, pumps, tanks, thermostats, awnings, slides, generators, batteries, inverters, and similar equipment. The Devices page lists everything currently configured on the Hub, grouped by its source: RV-C devices, Victron devices, and so on.

Add the devices

Everything happens on the one screen:

1Tick the devices to add. Ready-to-add and just-operated devices start ticked; untick any you do not want. Select all and none under Ready to add tick or clear that section.

2Name each device in its row — Bench Light, Kitchen Ceiling, Water Pump.

3Say what each switched circuit is in its What is it? box. A dimmer or relay output can drive a light, a water pump, a fan, an awning, shades, a door lock or a Starlink dish, and only you know which. LaunchControl shows a guess under the box but never picks for you. Choose No card to add the device without a dashboard card; untick the row to leave the device out. Batteries, tanks, thermostats and the like show the card they will get.

4Choose where the cards go — only when you have more than one dashboard, or in Expert mode. Put the cards on, in the bar under the list, picks the panel or makes a new one; otherwise the cards go on your dashboard.

5Press Add Equipment & Create Dashboard. The bar says what one press will do — how many devices and how many cards. If a selected switched circuit has no type, you cannot continue. The red note takes you to the first unfinished row. No card counts as an answer and is not requested again. The devices are added one at a time and their cards are created straight after. From the setup guide it returns you to the guide.

3.3 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. Use the GX integration when you have a supported GX device. Other MQTT equipment can share its broker.

1Enable MQTT on the Cerbo GX. On the GX device: Settings → Services → MQTT on LAN (plaintext) on.

2Find the Cerbo. On the Hub, open Settings → Integrations → Victron GX and press Set up. Press Find Cerbo GX; the Hub looks for the GX device on your network and offers it. Press Use this Cerbo. LaunchControl connects MQTT to it, finds its Portal ID and turns Victron on, in one go.

3Add the equipment. Press Add Victron devices on the Victron GX card, or open Devices and run a Victron scan. Add the discovered equipment; LaunchControl creates matching dashboard cards.

If the Cerbo is not found, press Enter the address manually: under Settings → Integrations → MQTT choose Connect to another broker, enter the Cerbo’s IP address as the Server address (port 1883) and press Save changes, then on the Victron GX card press Find Victron GX to fill in the Portal ID and Save changes.

The Hub always needs to know where to find the Cerbo GX. The Cerbo GX can be accessed directly over its own hosted access point with a static IP, or through your RV router. If you are using an RV router, the Cerbo GX will need a static IP address. See the Wi-Fi setup guide at launchcontrol.tech for additional detail.

3.4 The Hub's own MQTT broker

Under Settings → Integrations → MQTT the Broker choice has two options:

• Connect to another broker — the Hub connects to a broker somewhere else: a Cerbo GX, a Home Assistant broker, or any other. This is the Victron setup above.
• Use Hub's built-in broker — the Hub runs the broker itself. Use this on a coach that has no Cerbo. The card shows the Broker address your devices should use (the Hub's IP address on port 1883) and how many clients are connected. The username and password are optional: leave the username blank and any device on the coach network can connect; enter one and devices must sign in with it and the password.

Shelly, ESPHome and other MQTT devices are pointed at that address in their own settings. Home Assistant, Node-RED or MQTT Explorer can connect to it too and will see the Hub's published fields. The Hub uses one broker at a time: with the built-in broker selected, the Victron GX integration is unavailable, because it reads the Cerbo's broker — the Victron GX card then says Victron isn’t connected.

Publish data to MQTT has three independent options — RV-C data, Victron data and Bluetooth sensor data — and turning one on never starts the others. RV-C data covers the fields marked "MQTT" on the Devices page. The topic prefix is under Advanced settings. Changes take effect when you press Save changes; the card shows Unsaved changes until you do.

3.5 Shelly devices

Shelly relays, inputs and colour lights (Gen2, Gen3 and Gen4 models such as the Plus, Pro and Gen4 lines, and the Plus RGBW PM) connect to the Hub over MQTT and are found automatically: there are no topics to type. The short version:

1Choose the broker. If you use Victron GX, keep Connect to another broker and use the Cerbo’s broker address. Otherwise, in Settings → Integrations → MQTT, turn on MQTT, choose Use Hub's built-in broker, and press Save changes. Note the Broker address.

2Point the Shelly at that broker. On the Shelly's own web page, open Settings → MQTT, turn MQTT on, enter the chosen broker address as the server, and turn on RPC status notifications and Generic status update. Leave the client ID / prefix at its default.

3Add it. On the Devices page choose Add devices → Scan for Shelly devices. Each relay, input and colour light appears within a minute; press Add for the ones you want.

4Create cards. Close the list and accept Create cards. A relay becomes a switch card (with its wired switch input shown under the icon when it has one); an input-only device such as a Plus i4 becomes a card that shows On or Off; a colour light becomes a Color Light card.

A Color Light card switches the light on or off with a tap. Press and hold it for the colour wheel and three sliders: Color (the brightness of the coloured LEDs), White (the white LEDs, set separately) and Master (both together, keeping their balance). Colour lights can be added to a Lighting card's zones and scenes, and a scene remembers each light's colour and levels.

Shelly devices work everywhere other devices do: on the Touch 8, in automations (a Shelly input can trigger a rule, and Switch a card can turn a Shelly relay on or off), and in backups. An input set to Button mode in the Shelly app has no on/off state, so it does not get a card; instead it can run a macro on a single, double, triple or long press.

ESPHome discovery is planned. Until then, add ESPHome and other MQTT devices as Custom MQTT devices (below).

3.6 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, but a Cerbo GX is preferred if available.
• Ruuvi tags — battery-powered temperature and humidity sensors suitable for locations such as a refrigerator or outdoor reading.
• Shelly BLU button remotes — each press of each button runs a macro, recalls a lighting scene, switches a device or turns an automation on or off. See Shelly Setup.
• Garnet SeeLevel — Bluetooth tank monitors; each tank they report becomes a Tank card.

Open Settings → Integrations → Bluetooth, choose On and press Save and restart. The Hub restarts — the dashboard and displays pause for about 30 seconds and reconnect by themselves — and the card confirms Bluetooth is on. Then press Add Bluetooth devices (or use the Devices page) to add the sensors you want; the Hub only reads devices you add.

3.7 Starlink

The Starlink card can show ping success when the integration is activated, which is the best indicator of reliable internet. Enable Starlink in Settings → Integrations. If the card is also bound to a switched power circuit, its toggle can control dish power.

3.8 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.

To set it up, open Settings → Integrations → GL.iNet travel router, turn the integration on and press Find router. Enter the Router admin password — the one you use to sign in to the router's admin page — and press Save changes. The card checks the password and shows Connected with the router model, then offers Add router card. If the router is not the one the Hub connects through, press Enter manually and type its address under Advanced settings.

3.9 Weather

The Weather card shows current conditions and a five-day forecast, with the next hours on a tap; the same weather can also sit in a panel's header. Open Settings → Integrations → Weather, turn weather on and pick a Weather location:

• Use GPS — follows the coach, using a Victron GX device that has GPS. If GPS stops reporting, the Hub keeps the last position until it restarts, then a location you chose earlier.
• Choose a location — type a city or ZIP code, press Search, and pick the right place from the results. The card shows what you selected and what is saved, so you can tell them apart.

Press Save changes; the card then shows Forecast ready and offers Add weather card. Refresh now fetches a new forecast at once. The forecast refreshes every 30 minutes, and again once the coach has moved 20 miles. Forecast data by Open-Meteo.com; no account or key is needed.

3.10 Custom MQTT devices

3.11 Tank Geometry Calibration (Optional)

Tank sensors report the liquid level at the sensor, which may not accurately represent the amount of liquid in an irregularly shaped tank. LaunchControl’s optional Geometry Lookup feature corrects this by comparing the sensor reading with the tank’s actual contents. After calibration the tank will report the actual percentage and amount remaining.

1Level the RV and begin with the tank empty.

2Open Devices , edit the tank, and enable Geometry Lookup.

3Fill in measured increments. A water flow meter helps. Suggested increments are 1–2 gallons; more calibration points improve the result.

4Record each increment by entering the amount of liquid added.

5Finish when full. This also records the tank’s maximum capacity.

LaunchControl uses these calibration points to calculate a corrected percentage and estimate the amount remaining. Volume is displayed in gallons or liters according to the Hub-wide units setting.

Calibration tables can be exported as CSV files for backup or reuse. You can also import a compatible CSV table instead of entering the calibration points manually.

4.1 Panels

Use any names and grouping that suit you. Panels group cards; sub-panels add a second level when you need more room.

4.2 Add cards

Most cards are created when equipment is added (see Add or Change Equipment). For the rest:

• Create cards for new devices — in panel edit mode, under Dashboard Cards. It makes a card for every device, from every source, that has none yet, after asking what each switched output is. The setup guide’s Create dashboard is the same button.
• Add a card… — also under Dashboard Cards. Pick a type from the grouped list (Power, Climate, Water, Lights & switches, Motors, Internet, Utility, Victron) and the card editor opens with its data source to choose. Use it for cards that stand alone: Clock, Weather, Web Link, Sleep Timer, Power Diagram, an extra Lighting card for another part of the coach.
• Add to dashboard — on the Devices page, a device’s ⋮ menu makes its default card.

Cards are placed in the panel you are looking at. Move or copy… in a card’s gear menu puts it on another panel.

4.3 Arrange the cards

1Enter panel edit mode from the menu at the top right.

2Drag cards into position. The grab handle is in the top left of the card. Cards snap into the dashboard grid.

3Open a card’s gear menu to edit, duplicate, move or remove it.

4Exit edit mode. The layout is stored on the Hub. Narrow screens can keep a separate card order, as described below.

4.4 Card gallery

Victron-specific cards appear in the list once the Victron integration is configured.

The card editor shows a preview of the card at its real size, with sample values, for every layout you pick.

4.5 Header icons

The icons at the top right of the dashboard, from left to right:

• Warning triangle — appears when something needs attention; a number on it is the count of unread alerts. Tap it to see them.
• Connection dot — green while the dashboard is receiving live data, amber while it reconnects.
• Cloud — LaunchControl Remote. On a dashboard opened through Remote it shows that page's own link: green while connected, amber while reconnecting. On the coach's own network it appears while someone is viewing the Hub through Remote.
• Menu — Settings, Devices and the other pages.

When a panel header shows the weather and space is tight, the place name is left out so the temperature, wind and rain always fit.

4.6 Where a card gets its data

A card is connected to the device readings and controls it shows. LaunchControl makes those connections when it creates the card, so in normal use there is nothing to set up: test each new card from the dashboard, and if its values appear and its controls operate the intended equipment, you are done.

To check or change a card’s source, enter edit mode, open the card’s gear menu and choose Edit. Data source picks the device; What this card will show lists each reading with an on/off switch. If a card shows a dash, first check that its device is powered and reporting. If data or controls are still missing, check the selected source. If a control operates the wrong device, correct its source before using it again. The full per-slot binding editor is under Advanced, and the Technical Reference lists the usual bindings for each card type.

4.7 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.8 Look and feel

• Themes — choose the dashboard appearance in display settings; the Touch 8 follows the dashboard theme.
• Units — US customary or metric, for the whole product: temperatures, volumes and speeds on every card, display and the weather. Chosen during setup and changed under Settings → System → Units. Individual Victron devices can override units when needed.
• Background regions — optional tinted regions can visually group related cards on a panel.

4.9 Add the dashboard to your home screen

The dashboard can sit on your phone, tablet or computer like an app, with the LaunchControl icon. Open it at the address you want the icon to use: on the coach's Wi-Fi, the Hub's own address; through LaunchControl Remote, your Remote link. A Remote shortcut gets a green cloud on its icon and is named "LC Remote", so you can keep both.

5.1 Set up a Touch 8

1Power the display near the Hub. A new display looks for a LaunchControl Hub hotspot; with exactly one in range and no hotspot password set, it joins by itself and shows the dashboard — nothing else to do.

2If it shows a QR code instead, scan it with your unlocked phone and join the temporary setup network it offers. That happens when no Hub is in range, more than one is, or the Hub hotspot has a password.

3Follow the display setup page. Pick the Hub and enter the hotspot password if there is one.

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

5.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.

5.3 The Settings screen

The hamburger button at the top right of the Touch 8 opens its Settings screen: firmware version and serial, the Hub link, Wi‑Fi signal, the display's address and memory, screen brightness and sleep settings, and a Remote row that mirrors the Hub's LaunchControl Remote state — Off, Connecting, Waiting to be linked with the link code, or Online with the plan's remaining days. The display never turns Remote on or off; that is done on the Hub's Settings page or in the portal.

5.4 Choose which devices it uses

The Hub normally chooses the battery, water pump, climate zone, and other controls 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. For example, assign the climate card for the room where the display is installed.

5.5 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.

6.1 Set up a Mini

1Power the display near the Hub. A new Mini looks for a LaunchControl Hub hotspot; with exactly one in range and no hotspot password set, it joins by itself.

2If it shows a QR code instead, scan it with your unlocked phone and join the temporary setup network it offers. That happens when no Hub is in range, more than one is, or the Hub hotspot has a password.

3Follow the display setup page. Pick the Hub and enter the hotspot password if there is one.

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

6.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

6.3 Choose which devices it uses

The Hub normally chooses the battery, water pump, climate zone, and other controls 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.

7.1 Choose what you need

For a quick check while the RV is in storage or someone else is using it, start with Live status. Check the report’s age before treating its readings as current.

7.2 How it works

You connect the Hub to the internet, and visit the portal at remote.launchcontrol.tech. Everything local keeps working whether or not Remote is on.

Every new Hub includes 90 days of Remote free. The trial starts the first time the Hub is linked to an account. After that it is $6.99 a month or $69 a year, cancel any time.

7.3 Turn it on

Remote needs three things: the Hub on a network with internet access, the Hub's clock set, and a Dashboard PIN set.

1Enable it. On the dashboard, go to Settings → Integrations, press Set up on the LaunchControl Remote card, then Set up LaunchControl Remote. The card shows Connecting, then Ready to link. (The setup wizard offers the same step at the end of a new installation.)

2Link it to you. Press Continue in browser, or Scan with your phone to show a QR code and a six‑digit link code. You can also open remote.launchcontrol.tech in any browser and press Link a hub. Sign in with your e‑mail — a sign‑in link is sent to you; there is no password to remember — and enter the six‑digit link code.

3Open your coach. The portal shows the hub under My hubs; press Open dashboard. Bookmark the remote address: it is yours for as long as the Hub is linked.

7.4 Using it

The remote dashboard is the real dashboard: lights, thermostats, tanks, the Settings pages, automations, alerts, the floor plan. Live values update as they do at the coach.

A small cloud next to the connection dot at the top of the dashboard shows the remote link: green while connected, amber while reconnecting. Tap it for the remote‑use guidance. On the local network the same cloud appears while someone is viewing the Hub through Remote, so people at the coach can see that it is being used from afar.

Awnings, slides and leveling jacks do not move from Remote. You cannot see what is around them, so the Hub refuses those commands when they arrive through Remote, whoever sends them, and their cards say "Not available remotely". Shades still work. Automations that move an awning run on the Hub itself and are unaffected. Siri and Shortcuts never move awnings, shades or slides at all.

If the Hub is not connected to Remote when you open the remote address, the page says Hub offline and when the Hub was last seen, in UTC. The Hub reconnects by itself as soon as it has internet again.

Siri, Shortcuts and other controllers work from anywhere through Remote too: under Shortcuts & API pick LaunchControl Remote as the Connection method before copying a link (see Voice Control, Shortcuts, Siri and Other Controllers (API)).

7.5 Live status

Each hub on My hubs has a Live status button next to Open dashboard and Manage Hub. It opens a one‑page summary of the coach that loads in a second and works even when the Hub is offline. It then shows the last report the Hub sent, and says how long ago that was.

• Power: state of charge, voltage and net power of each battery card on your dashboard, the start battery if an Alternator card shows it, solar power, whether the inverter is on (with its power), charging only or off, and whether shore power is connected (with the power it supplies) or disconnected.
• Tanks: level of each tank card, the water remaining when the tank has a fill table, and a Warning or Alarm tag when the tank's alarm is set off.
• Temperatures: room temperature from each thermostat, temperature sensors, and the outside temperature from a Weather card.
• Alerts: the Hub's recent alerts, with problems that are still active listed first. Tap the arrow on an alert to read it.
• Location: with a GPS on the Hub (Victron GPS), its position with an Open in Maps link, its speed and its elevation.
• Map: where the coach has been over the last 30 days. Drag and pinch to zoom. The green dot is the start of the 30 days, the red‑ringed dot is the coach now, and blue dots are places it stayed two hours or longer; tap one for the dates.

The rows are your own dashboard cards, under the names you gave them, showing the same numbers the dashboard shows. While the page is open it refreshes every 30 seconds.

Two switches on the Hub control what is sent, under Settings → Integrations → LaunchControl Remote: Share Hub status and Include location history. Both are on unless you turn them off. Turning either off deletes what LaunchControl Remote holds for it. The owner can also delete the location history from the Live status page. People you share the hub with see the Live status page too, map included.

7.6 Your plan

Open remote.launchcontrol.tech, sign in and choose the hub. Its page shows the current access and when it ends.

• Subscribe. Press Subscribe · $69 a year or Subscribe · $6.99 a month. The plan starts when the access the hub already has runs out, so subscribing during the free trial does not shorten it: your card is saved now and first charged on that day. Payment is by card; the receipt and card details live under Card & receipts on the same page. Your first paid subscription carries a 30‑day money‑back guarantee from the first charge.
• Auto‑renew. Shown plainly beside the end date: Auto‑renew on — renews on … ; your card is charged … then, or Auto‑renew off — access ends on …. Turn it off and nothing more is charged; turn it back on before the end date and nothing is lost.
• Switch plans. A switch takes effect when the current paid period runs out; until then nothing changes and nothing is charged. The page says so while a switch is scheduled, and you can keep the current plan instead.
• Reminders. LaunchControl e‑mails you before a renewal and before access ends, and the same notices appear in the dashboard's alert inbox (the triangle in the header).
• If a card is declined, remote access continues for 14 days while the charge is retried; update the card under Card & receipts.

The ledger at the bottom of the page lists every piece of access the hub has had — the trial, each subscription period, every code — with dates.

7.7 Sharing a hub

The owner can share a hub with other people — a partner, a co‑owner, a technician — under Share with others on the hub's page. Each person signs in with their own e‑mail address and finds the hub under My hubs. They can open it and use it; only the owner can change the plan, the name or the sharing, and the owner can remove anyone at any time. A shared user can also leave on their own. The Dashboard PIN applies to them as it does to you.

7.8 Letting LaunchControl support in

If support asks to look at your hub, you decide, and you hold the key. On the hub's page in the portal press Allow remote support for 24 hours. The page shows a six-digit PIN; send it to LaunchControl support. Only an admin who enters that PIN can open your dashboard, and only for the next 24 hours, or until you press Turn off remote support, whichever comes first.

While the window is open, every page of your hub, on your own screen as well as theirs, shows a yellow border with "Remote support enabled". The moment an admin is actually connected the border turns red and reads "Remote support active" with your serial number, so there is never any doubt about who is in. Local control is never affected.

7.9 Selling the coach, or starting over

Turn off pauses Remote and keeps the Hub linked to your account. Unlink removes the Hub from your account, cancels your plan, and gives the Hub a new code for its next owner. Find both under Turn off or unlink on the LaunchControl Remote card in Settings, or unlink from the Hub’s page in the portal. To close your account entirely, use Delete my account at the bottom of the portal: every hub is unlinked, every plan cancelled, and your sign‑in is removed.

7.10 Free remote access

8.1 Lighting Masters & Scenes

The Lighting card provides whole-coach lighting controls:

• Two zone 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. Scene names and icons may be customized in the card editor.
• Automation badge — run lighting on a schedule from the card settings. Lights can be controlled by time of day or by using solar panels as a sensor.

The Lighting card setup lets you choose which lights are controlled by Zone 1 master, Zone 2 master, and lighting scenes. Each Lighting card maintains its own list of lights, allowing you to create multiple cards for different zones throughout the coach.

When the master is turned off, LaunchControl remembers the state of each light. Turning the master back on restores the lights to their previous settings. To turn all lights on at 100%, press and hold the On button.

Each lighting zone and scene list supports up to 32 lights. The settings page warns when a list is full.

8.2 Lighting Dimmers

The Light Dimmer card provides controls for an individual light. Dimmers for small cards can be accessed by pressing and holding the card. Lights remember their last value when turned back on. This setting can be changed in the device setup for each light.

8.3 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.

8.4 Tanks

Fluid tanks with heaters that have been bound to a card may be toggled by pressing and holding the card.

For an irregularly shaped tank, Geometry Lookup maps sensor readings to measured contents. Calibrate once under Devices → edit the tank; see Tank Geometry Calibration (Optional) in Add or Change Equipment. The Hub then shows corrected percentage and estimated volume in your selected units.

8.5 Awnings & Shades

Awning and Shades cards have two direction buttons. Depending on the device, a button is either hold-to-move (the motor runs while you hold it) or press-to-command (window-shade controllers start on a press and stop on the next press). The card settings say which.

Move several shades at once — when you add or edit a Shades card yourself, the card editor lists every other shade on the Hub under Also move these shades. Tick the ones that should follow. One press then moves the card's own shade and every ticked shade, from the dashboard or a Touch display. Cards created automatically are one shade each; edit a card to group them.

8.6 Graphs

Solar, Shore Power, Alternator, Generator, Battery and Net Power cards have graphs that can be configured for time and scale markers from the panel edit mode.

8.7 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).

8.8 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.

9.1 The Automations page

Settings → Automations lists every automation rule and macro with its status, the alert channels it uses, whether it has a dashboard card, and an enable switch (or a Run button for a macro). Click a row to edit it, or use New Automation / New Macro. The notification services — Phone notifications, Text messages, Email and Notification limits — sit below the list under Notifications.

9.2 Automation rules

An automation rule watches one sensor and acts when the reading crosses a threshold.

• Sensor — press Choose sensor and expand a device to pick one of its readings: battery percentage, a tank level, a temperature, shore voltage. Any value a dashboard card can show can be watched.
• 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: device switching, lighting masters, thermostat changes (Off, A/C, Heat or Fan Only), and Send alert (see Alerts).

Common templates can pre-fill the condition.

9.3 Macros

A macro runs up to eight actions in order. For example, an Away macro might switch off the water pump and lower the thermostat; a Return macro can reverse those actions. Run it from the Run button in the list or from its dashboard card.

Extra choices available in a macro:

• Lighting scene — recalls one of a Lighting card's scenes.
• Toggle a card — switches a card's device to the opposite of how it is now (Switch a card sets it on or off).
• Automation on/off — enables a disabled automation rule, or disables an enabled one.
• Wait (delay) — pauses for 1 to 3600 seconds before the next action, for example to let the inverter come up before the water pump starts. The wait runs on the Hub, so the macro finishes even if you close the page. Each wait uses one of the eight action slots. Running the macro again while it is waiting starts it over from the first action; editing or deleting the macro cancels the wait.

9.4 Dashboard cards

Cards are optional. In dashboard edit mode, use Add a card… under Dashboard Cards, choose Automation or Macro, then pick the rule or macro. An Automation card shows whether the rule is armed and whether it is triggered; tapping it enables or disables the rule. A Macro card runs the macro on a tap. Each automation can have one card. Removing the card keeps the automation; deleting the automation removes its card.

10.1 Choose a delivery method

Set up the service you want, send a test, then add Send alert to an automation. You can select several delivery methods on one alert.

10.2 Where alerts appear

Every alert lands in the alert list. A red triangle with a count appears at the top right of the dashboard whenever the list holds anything; click it to open the list. The same list is always available under Settings → Status → Alerts.

• New alerts are shown bold until you have looked at them; alerts you have already seen turn gray.
• Alerts from your automations stay in the list until you delete them, one at a time with the trash can or all at once with Delete all.
• Hub health alerts cannot be deleted; they clear on their own when the problem is fixed.
• The triangle stays lit until the list is empty.
• History, beside Delete all, lists every alert since the Hub last started, including the ones you deleted and the health alerts that have cleared, with when and how each left the list. Press Back to return to the list. The history starts over when the Hub restarts.

10.3 Hub health alerts

The Hub watches itself and raises an alert when something has been wrong for a while: no RV-C data arriving, MQTT or Victron turned on but not connected, the network down, the clock not set, memory running low, or CAN frames being dropped. These are marked active in the list and go away as soon as the condition clears.

10.4 Update notices

Once a day, when a browser is open on the dashboard or Settings and has internet access, the Hub checks for a newer firmware release. If one is available, an Update available alert appears; delete it once you have seen it, and it does not come back for the same release. Install from Settings → System → Software updates.

10.5 How automation alerts fit together

An alert is an action on an automation, in the same list as "turn the pump off":

1Open Settings → Automations and create or edit an automation.

2Add Send alert as one of its actions and write the message.

3Tick where it should go: On-screen (the alert list), Push, SMS, E-mail (Remote).

On-screen needs no service setup. E-mail (Remote) uses the account linked to the Hub and requires active Remote access; see Remote Access. Set up Push and SMS below under Settings → Automations. SMS charges are paid to the message service.

10.6 Push notifications (free)

This uses ntfy, a free notification service with an app for iPhone and Android.

1Turn it on. Settings → Automations → Phone notifications → Set up → Turn on phone notifications → Save changes. The Hub generates a private topic name for you.

2Install the ntfy app from the App Store or Google Play.

3Subscribe to your topic. Scan the QR code on the Settings page with your phone, or open the app, tap +, and type the topic exactly as shown.

4Send test notification. It should arrive in a second or two.

Repeat steps 2–4 on every phone that should get alerts.

10.7 Text messages (prepaid)

This uses Textbelt, where you buy a block of messages up front.

1Buy credits. Open textbelt.com/purchase and choose generate a new API key. Choose a pack, and pay. Packs start around $3 for 50 messages. Save the key; it cannot be retrieved if lost.

2Set a sender name. On the Textbelt Account page, fill in the sender name. Textbelt will not send anything until you do, and it is the step almost everyone misses.

3Paste the key into Settings → Automations → Text messages → API key, add your 10-digit phone number, turn on Turn on text messages, and press Save changes.

4Send test text. This sends a real message and uses one credit.

10.8 Writing the message

• Channels. On-screen is always available; E-mail (Remote) appears while the hub is linked to LaunchControl Remote; Push and SMS appear once set up.
• Message. A sensible message is filled in for you. Edit it freely.
• Insert value. Drops a live reading into the message at the cursor.

You can have one alert in each action list. If you want the same event sent two ways, tick two channels on the one alert rather than adding a second.

10.9 What happens when there is no internet

On-screen alerts never need it. For push and SMS the Hub holds the message and keeps trying — after 30 seconds, a minute, five minutes, then hourly, giving up after a day. When the connection comes back the message arrives, and it still reports the reading that set the automation off, not whatever the sensor says by then.

10.10 If an alert does not arrive

• Check the list under Settings → Status → Alerts. An on-screen alert there means the automation fired; the Automations page also shows "fired 2 min ago" on the rule.
• Nothing fired at all? The rule may have been already past its threshold when you enabled it ("Triggered · at start, not fired"). Enable it while the reading is on the normal side, then let it cross.
• Push: confirm the phone is subscribed to the topic shown in Settings — a New topic press unsubscribes every phone.
• SMS: check the credit count, and check you set a sender name on the Textbelt account page.
• SMS says 0 credits right after you bought some? Textbelt reports 0 both for an empty balance and for a key it does not recognise, so the likely cause is the key rather than the purchase. Each time you press generate a new API key you get a different key, and the credits belong to the one you paid with. The Settings card shows the length and last four characters of the key the Hub is holding — compare that with the key on your Textbelt account page, and paste the right one if they differ.
• Send test in Settings tells you what the service said, in its own words.

11.1 What a web kiosk is

A web kiosk is the ordinary LaunchControl dashboard, in a display mode: one panel, edge to edge, no tabs or menus, scaled up to fill the screen. It shows exactly what your phone shows, because it is the same dashboard — so every card you have, and every card added in a future update, works on a TV with nothing extra to set up.

A kiosk is read-only by default. To control equipment from a wall tablet or a TV with cursor mode, turn Allow touch on for that display alone.

11.2 What to plug into the TV

A wall-mounted tablet is also a good kiosk. On an iPad, add the page to the Home Screen so it opens without Safari's toolbars; on Android, use Fully Kiosk Browser as above.

11.3 Set up a display

1Get the display address. Open Settings → Displays on the Hub and copy the web address shown.

2Open it on the TV or stick. The device must be on the same network as the Hub.

3Set the size while watching the TV. The controls under that display's name take effect on the screen within a few seconds — no reloading, no walking back and forth. Adjust them with the TV in view.

4Make it start by itself. In your kiosk browser's settings, set the same address as the start page, and turn on "launch on boot" and "keep screen on" if it offers them.

11.4 If the edges are cut off

Most televisions crop the outside of the picture slightly — it is called overscan, and it can cut off cards at the edges.

1Fix it on the TV first. In the TV's picture settings, find the aspect or size option and choose Just Scan, Screen Fit, Full Pixel or 1:1 — the name varies by brand. This is the real fix and costs no screen space.

2Then use Safe area for whatever is left. Raise the Safe area control for that display until nothing is clipped. It pulls the whole dashboard in from every edge.

11.5 The other controls

11.6 Designing a panel for a TV

A TV cannot scroll. It shows the top of the panel and cuts off anything below — so a panel built for a phone, which scrolls happily, usually has more rows than a TV can show.

The dashboard's panel editor can outline exactly what a TV will show: enter edit mode, and under Dashboard Cards press TV panel guide until it reads 16×9. A blue outline marks the boundary. Keep the cards you want on the TV inside it.

11.7 Pinning a display to fixed settings

If you would rather not pair a display at all — say a stick you set up once and forget — use the Kiosk builder at the bottom of Settings → Displays. Choose the panel and the size controls, then either copy the link or scan the QR code with a phone to send it on. Set that whole address as the kiosk browser's start page.

A link built this way carries its settings in the address, so it overrides anything stored in Settings for that display. That makes it the right choice for a display you want to behave identically no matter what.

11.8 Removing a display

Press Remove beside it in Settings → Displays. Its settings are erased and the screen goes back to showing a pairing code, ready to be added again — so this is also how you start a display over.

On the display itself, a long press in the bottom-left corner brings up a small panel with "Reload now" and "Forget this display". This recovery panel remains available when Allow touch is off, so you can use it without a phone.

12.1 Choose a shortcut

• One shortcut for everything: Siri asks what you want, then sends your spoken command to the Hub.
• One-tap shortcuts: create a specific action you can run by name, button, or widget.
• Other phones and apps: use the API & custom integrations tab; parameter details are in Technical Reference.

Use your existing card, zone, scene, macro, or automation names. You do not need to reorganize your dashboard.

12.2 How it works

Every control on your dashboard already has a name — the card name you gave it. The Hub accepts a simple web address that uses those names, such as turn Kitchen Pendants on or set Bedroom to 72.

For Siri, a Shortcut opens that address; Siri runs the Shortcut when you say its name. The Hub works out which device, which command and which setting, and answers with a short sentence that Siri can show or speak.

What you can address by name:

• Switches and lights — Light, Switch, Water Pump, Starlink, Inverter, Tank Heat and Linked Switch cards: on, off, toggle, status. Lights also take a brightness.
• Thermostats — a temperature, a mode (heat, cool, auto, fan, off), or status.
• Lighting zones and scenes — each zone of a Lighting card (on, off) and every saved scene (run).
• Door locks — lock, unlock, status.
• Shore power — a current limit.
• Macros and automations — run a macro; enable or disable an automation.
• Readings — ask for the status of any card that shows a value: battery, tanks, solar, temperatures.

Awnings, shades and slides are deliberately excluded. They move only while a button is held, and a voice command has no way to stop them.

12.3 Set it up

1Open the settings. On the dashboard, go to Settings → Integrations → Shortcuts & API and press Set up shortcuts. The card has two tabs: Apple Shortcuts & Siri, and API & custom integrations for other apps.

2Choose the connection method. RV network makes links that work while the phone is on a network that can reach the Hub; LaunchControl Remote makes links that work from anywhere the phone has internet (it needs Remote linked and active, see Remote Access). A VPN address such as Tailscale can be used as a Custom address once Expert mode is on (at the bottom of the LaunchControl Remote card). The choice is remembered on this browser only.

3Try a command. Type turn on the kitchen lights (using one of your own names) in Try a command and press Test command. The Hub's answer appears below it — exactly what Siri will say. Testing really sends the command to your RV; copying a link never does.

12.4 One shortcut for everything

Build this one first. It takes whatever you say and lets the Hub work it out, so you never build a shortcut per device unless you want to.

1Copy the voice link. On the Apple Shortcuts & Siri tab, choose Control by voice and press Copy shortcut link. View setup guide shows these steps on the page.

2Create a Shortcut. Open the Shortcuts app, tap +, and add the action Ask for Input. Choose Text and set the prompt to something like What should LaunchControl do?

3Add the web request. Add the action Get Contents of URL and paste the link. Expand its options and leave Method set to GET. Under Headers, add the key X-Say; for its value choose Select Variable and pick Ask for Input (usually shown as Provided Input) near the top. Do not pick Shortcut Input.

4Hear the answer. Add the action Speak Text with Contents of URL from the previous step. To see the answer instead, use Show Result.

5Name it. Tap the name at the top and call it Coach (or anything you like). That name is the Siri phrase.

Now say "Hey Siri, Coach". Siri asks what you would like; answer in plain words:

Filler words are ignored, so please turn on the kitchen lights and kitchen lights on are the same request. If two names match equally, the Hub answers Which one: …? — say the full name next time, or rename one card.

12.5 One-tap shortcuts

A phrase of its own is faster when you say it often: "Hey Siri, kitchen lights on" with no follow-up question. Each needs its own small Shortcut.

1Pick the action. On the Apple Shortcuts & Siri tab, choose Create a specific shortcut. Find the Device, choose the Action, and enter a value where the action takes one (50 %, 72°, 30 A). The command is summarized below.

2Copy it. Press Copy shortcut link. This makes the link only; it does not operate the device. Test command tries it for real.

3Create the Shortcut. In Shortcuts, tap +, add Get Contents of URL, and paste the link. Add Show Result if you want to see the Hub's answer.

4Name it with the phrase. The Shortcut's name is what you say: Kitchen Lights On.

Shortcuts can also be put on the Home Screen, in a widget, on the Action Button, in the Apple Watch Shortcuts app, or run from a Shortcuts automation — for example when I arrive at the campground, run Return.

12.6 Away from the coach

A link works from anywhere the phone can reach the Hub. On the coach's Wi‑Fi that is the local address. From the road, use LaunchControl Remote: under Connection method pick LaunchControl Remote before copying, and the links — and Siri — work wherever the phone has internet; the API key is accepted there too. A VPN such as Tailscale on the coach router works the same way with its address. The Hub does not need to be exposed to the internet — never forward its port.

12.7 Other phones and apps

Any tool that can open a web address can use the same links: Android's Shortcut Maker or Tasker, a browser bookmark, a Stream Deck, or a Home Assistant rest_command. The API & custom integrations tab builds request URLs for them — by device and action, or as a plain‑language command — with a text or JSON response, and API documentation lists every parameter. The link is a plain GET request; the answer is one line of text, or JSON if you leave fmt=text off.

12.8 API reference

For request parameters, authentication, response formats, and error codes, see The control address in Technical Reference.

13.1 Find a common setting

13.2 Settings tabs

13.3 Integrations

Each integration is one card. Closed, it shows a status badge, a one‑line summary and anything that needs your attention; Set up or Manage opens its settings in place, and Close folds them away again without losing what you typed. Several cards can be open at once — handy for MQTT and Victron GX together.

• Edits remain a draft until you press Save changes. Until then the card shows Unsaved changes, and the page warns before you leave it. The badge always shows what is saved and running, never an unsaved switch.
• After a successful setup the card offers the next step — Add Victron devices, Add Bluetooth devices, Add router card, Add weather card — but never forces it.
• Advanced settings holds optional configuration; Technical details holds diagnostics, with Copy diagnostics for support (passwords and keys are never included).
• Expert mode, at the bottom of the LaunchControl Remote card, is the one Expert mode for the whole product: it shows the relay override and the Shortcuts custom address here, and the technical detail everywhere else — DGNs, instances, source addresses, raw bindings. The same switch sits at the top of the Devices page. It is remembered on this browser only.

13.4 LaunchControl Remote (Integrations)

The first card under Integrations. Set up turns LaunchControl Remote on; it needs a Dashboard PIN and a valid clock. While the Hub waits to be linked the card offers Continue in browser and Scan with your phone (a QR code and six‑digit code); once linked it shows the account and your access, with Open remote dashboard and Manage remote access. Turn off or unlink pauses Remote or hands the Hub to a new owner with a fresh code. See Remote Access.

13.5 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.

13.6 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.

13.7 System

Settings → System contains Date & time, Units, Setup guide, Expert mode, Software updates, Backup & restore, Connection protocol, Factory reset, and About & Legal.

• Units changes the whole product between US customary and metric.
• Setup guide reopens the seven-step checklist with completed and remaining steps.
• Expert mode shows technical detail throughout the product. The Devices page has the same switch.
• Save changes applies your draft edits. For the connection protocol, use Apply and restart instead. The page warns before you leave with unsaved changes.
• Only one restart action can run at a time. Restart Hub is under Settings → Status.

Before changing the connection protocol or restoring a backup, read what will be replaced and download your current backup.

13.8 Date & time

Schedules and timers need valid time. The card shows the Hub's current time and date, a status — Synced, Manually set or Not synchronized — and where the time came from and when. The time source is Automatic unless you change it: internet time whenever the Hub has it, otherwise the RV-C network, then Victron GPS, then the browser that is open. The card warns when two sources disagree by more than a couple of minutes, and says which one is being used.

• Time zone and Daylight saving time apply to Victron GPS and internet time, which report UTC. RV-C and manual time are already local. Daylight saving time is unavailable for zones that do not observe it.
• Send Hub time to the RV-C network lets factory panels and thermostats use the Hub's time. It is sent once a minute while the clock is set, unless the time comes from the RV-C network itself.
• Time source (advanced) lists Automatic (recommended) and the four manual choices — RV-C network, Victron GPS, Manual and Internet time (NTP) — each with the time it is offering and, if it cannot be used, why — for example No GPS data available. Pick a source only to force one.
• Manual shows a date and a time, and Set to this device's time, which saves at once. Manual time is lost when the Hub loses power. Set the time from this browser whenever the clock is not set restores it simply by opening Settings after a power loss.
• Technical details shows the RV-C address the time comes from and whether the Hub is sending time to RV-C.

13.9 Backup & restore

Download backup saves one file, named after the Hub and the date, for example launchcontrol-backup-hub-1001-2026-10-05-1348.json. The page tells you the download started; where it is saved is up to your browser.

• Included: devices and their names, dashboards, panels and cards, lighting zones and scenes, automations, macros and schedules, alert settings, TV displays, display assignments, clock and unit settings, and the connection protocol. It contains the same kind of data as a Floor Plan and may be shared with others.
• Not included: Wi-Fi networks, the Dashboard PIN, the hotspot password, the text message key, the API access key, and the connections to MQTT, Victron GX, the travel router, weather and Remote Access. After restoring to a replacement Hub, enter those again.

Restore from backup never starts on its own:

1Choose backup file. The page checks the file and shows what is in it — devices, cards, panels, automations, its protocol and the file date — or says why it cannot be used.

2Read what will be replaced. Download current backup first if you may want today's setup back.

3Restore backup , then confirm Restore this backup? The page shows Restoring backup…, Restarting Hub… and Reconnecting…, and confirms once the Hub is back. If the Hub does not answer in time, it says the result is not confirmed — reload the page a minute later.

13.10 Connection protocol

The Hub talks to the coach's devices in one protocol at a time: RV-C (most RVs) or OneControl (Lippert coaches). The card shows the one in use. Change protocol opens a choice; picking one is only a draft, and the card lists exactly what the switch removes:

Victron, MQTT and Bluetooth devices, dashboards, Wi-Fi and every other setting are kept. Download backup first, then Apply and restart and confirm. Restoring a backup made before the switch brings everything back, including the protocol.

13.11 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.

14.1 Before updating

Keep the Hub and displays powered until the update finishes. The Hub restarts during installation. For an online update, the phone or computer running the browser needs internet; for an offline update, use Install from file below.

14.2 Update the system

1Open Settings → System → Software updates 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.

14.3 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.
• Each display has its own basic update page for manual fallback.

14.4 Install from file

When the Hub's browser has no internet access, download the update file (.bin) on another device and use Settings → System → Software updates → Install from file:

1Choose update file. Nothing is installed yet. The page reads the file and shows what it is — Firmware update or Web interface update — and its version, or why it cannot be used (for example, firmware for a different device).

2Install update. Keep the Hub powered on until installation is complete. The page shows Uploading…, Installing update…, Restarting Hub… and Reconnecting…, then confirms the version now running. Devices, dashboards and settings are kept.

3After a web interface update, reload the page to use it.

If the Hub does not answer within the wait, the page says the result is not confirmed rather than guessing; reload a minute later and check the versions shown in the card.

15.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.

15.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.

15.3 API key

Shortcuts, Siri and other integrations (see Voice Control and Shortcuts) use an API key instead of the Dashboard PIN. It is kept masked under Settings → Integrations → Shortcuts & API → API access key and works for the control address only: a key that leaks can operate named controls, but cannot change settings, read a backup or join a network. Press Replace key to replace it; every shortcut then needs its link updated. The key is not included in configuration backups.

15.4 Remote access

LaunchControl Remote (see Remote Access) makes the dashboard reachable from the internet through LaunchControl's service, never by opening a port on the coach. It cannot be enabled without a Dashboard PIN, and every remote browser is asked for that PIN as it would be on an untrusted network — your account proves who you are to LaunchControl, the PIN proves it to the Hub. The Hub treats a connection arriving through Remote as untrusted no matter which network it is on. Share a hub only with people you would hand the PIN to; the owner can remove a shared user at any time, and Unlink cuts the hub off from the account entirely.

15.5 Remote support

LaunchControl staff cannot open your hub through Remote on their own. You open a 24-hour support window on the hub's page and give them its PIN; they must enter it to get in, and the hub shows a yellow border while the window is open and a red one while someone is connected (see Remote Access). Turn it off at any time; it closes by itself after 24 hours.

15.6 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.

16.1 Start with these checks

1Check power and connection. Is the Hub powered, and are you using its local network or Remote?

2Check Settings → Status if the dashboard opens. Note the reported problem before changing anything.

3Follow the matching symptom below. Start with connection and device checks before resetting configuration.

For detailed notification checks, see Alerts. For Shelly relay, button, and color-light issues, see Shelly Setup.

16.2 I can't connect to LaunchControl

• launchcontrol.local does not open. Make sure your phone or computer is on the coach Wi-Fi. On Android, use the router's device list to find launchcontrol-xxxx. For direct access, join LaunchControl-Hub-XXXX and open 192.168.4.1. If you cannot join or have forgotten credentials, see Security.
• New router, or the router changed. Join the Hub hotspot, open the dashboard, and add the new network under Settings → Network.
• Everything froze after a power blip. The Hub and router may be rebooting together. Give the router time to return; the Hub keeps retrying its saved network.
• The setup page did not pop up. Open a browser and go to 192.168.4.1 while on the Hub's Wi-Fi.

16.3 No RV equipment appears

• Settings → Status shows no RV-C activity, or the setup guide's first step is not done. Check Hub power and the physical RV-C connection. Reversed RV-C H and L wires do not damage anything, they simply do not work, so try swapping them. Never swap the RV-C and power wires. Confirm the correct coach connection or adapter using the LaunchControl FAQ.
• The scan is empty but Status shows data. Operate one light, pump, or switched circuit in the RV and watch Devices you just operated. Devices awaiting identification may also be under Needs identification. Everything you already added is folded under Already configured; press Show to see it.
• A Lippert coach. Lippert OneControl coaches do not speak RV-C. Switch the protocol under Settings → System → Connection protocol and restart; the scan then lists OneControl devices. The setup guide’s Fix connection says the same.

16.4 A device is missing

• It is not in the scan. Turn Expert mode on (top of the Devices page). Some device types are listed only there.
• It shows as "Moved here from …". The coach gave its controller a new network address. The Hub updates the saved device, its cards and lighting zones by itself within a couple of minutes. Nothing to do.
• Cards stopped updating after the coach was powered off and on. Same cause. Lights, switches, loads, shades and door locks follow their device automatically; other readings may need their device re-added from a new scan.

16.5 A card has no data

• The card shows "—". The bound device is not reporting. Check device power; for Victron readings check Settings → Integrations; then open the card's edit menu and check its data source.
• A Victron card is blank. Victron reads the GX device's own broker. Settings → Integrations → Victron GX: press Find Cerbo GX, or under MQTT choose Connect to another broker with the GX device's address.
• The Starlink card is blank. The Hub must be on a network that can reach the dish. Check Starlink under Settings → Integrations and confirm the dish is powered.

16.6 Remote isn't working

• LaunchControl Remote stays on "Connecting". The Hub needs internet and a valid clock. Check Settings → Status for the network, and Settings → System → Date & time. Whether the service itself is up is shown at remote.launchcontrol.tech/status.
• "Identity conflict". The Hub was reset or re-flashed while linked. Sign in at remote.launchcontrol.tech, open the hub under My hubs and press Unlink, then enable Remote again and link it with the new code.
• "Access expired" or "Payment needed". The trial or plan ran out, or a renewal charge failed. Local control is unaffected. Open the hub's page in the portal to subscribe, update the card, or redeem a code.
• An awning, slide or leveler will not move. They never move through Remote, by design; use the dashboard on the coach's own Wi-Fi or a Touch display.

16.7 A display won't connect

• The Touch 8 or Mini shows its QR code. On its first start a display joins the only LaunchControl Hub hotspot in range by itself. It shows the QR code when there is no Hub in range, more than one, or the Hub hotspot has a password: scan the code and follow the pairing page.
• It shows the QR code again later. The display lost the Hub, or the Hub hotspot credentials changed. If the original network returns, wait for automatic reconnection. Otherwise pair the display again.
• It shows the wrong cards. Settings → Displays assigns which card each display uses for each role.

16.8 Notifications aren't arriving

• Nothing fired at all. Check the alert list under Settings → Status → Alerts. The rule may have been past its threshold when it was enabled ("Triggered · at start, not fired"). Enable it while the reading is on the normal side, then let it cross.
• Push. Confirm the phone is subscribed to the topic shown in Settings; a New topic press unsubscribes every phone.
• SMS. Check the credit count, and that a sender name is set on the Textbelt account page. Textbelt reports 0 credits both for an empty balance and for a key it does not recognise.
• E-mail (Remote). Needs the Hub linked to LaunchControl Remote with access running.
• Send test in Settings → Automations tells you what the service said, in its own words.

16.9 Schedules run at the wrong time, or won't enable

• A schedule will not enable. The Hub's clock is not set. The Hub sets it automatically from the internet, the coach network, a GPS or the browser that is open; Settings → System → Date & time shows which source it is using and offers Set to this device's time.
• Events fire an hour off. Check the time zone and daylight saving under Settings → System → Date & time. The card warns when two sources disagree.

16.10 Bluetooth says "Restart needed"

This is expected after changing Bluetooth without restarting. Open Settings → Integrations → Bluetooth and press Restart now; Save and restart does both in one step.

16.11 I forgot my PIN

Power-cycle recovery works without a cable or a support call: 3 quick power cycles temporarily opens the hotspot; 5 quick cycles clears both the Dashboard PIN and the hotspot password. See Security.

16.12 The update check finds nothing

The phone or computer running the browser needs internet access for the update check. The Hub itself does not.

16.13 Still need help?

Open Settings → Status → Debug data and download the support information. Include the symptom, the device or card affected, the software version, whether you were local or using Remote, and what you already tried. Use LaunchControl support for installation and connection guidance.

18.1 Use this reference when you need to…

• Understand network addresses, connection paths, or hardware.
• Inspect a card’s source and individual bindings.
• Interpret RV-C DGNs, instances, and device fields.
• Build API requests or understand their responses.

For installation, start with Set Up Your Hub. For an equipment problem, use Troubleshooting before changing advanced fields.

18.2 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.

18.3 Hardware

18.4 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.

18.5 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.

18.6 Glossary

18.7 Understanding Devices, Cards, and Dashboards

Four things work together to turn information from your RV’s equipment into an organized control panel.

Device — a piece of equipment or a function in the RV, such as a light, water pump, thermostat, tank sensor, inverter, or battery monitor. Devices are discovered through RV-C or added through integrations such as Victron, Bluetooth, or MQTT.

Card — the control or information display for a device. A Light Dimmer card controls a light, a Tank card shows a tank level, a Thermostat card displays and controls the climate system.

Dashboard — cards organized into one or more panels. Cards can be rearranged to match how you use your RV.

Binding — the link between a card and the device information it displays or controls. LaunchControl creates the normal bindings automatically when it creates a card; this chapter lists them.

18.8 Expert mode

Expert mode is one switch for the whole product — at the top of the Devices page, in the scan, and at the bottom of the LaunchControl Remote card in Settings — remembered in the browser you set it in. Off, LaunchControl shows equipment by name; on, it also shows the protocol underneath: DGNs, instance numbers, source addresses, every field a device defines, raw bindings in the card editor, the relay override and the custom Shortcuts address. Nothing is removed by turning it off; it is only hidden.

18.9 Card bindings

A binding connects an element on a dashboard card to information or controls provided by a device. For example a Tank card’s level display is bound to the level field of a tank device; a Light Dimmer card to the status and brightness of a lighting device; a Thermostat card to temperature, setpoint, mode and fan fields; a Battery + Power card may combine information from a battery, a shunt and other power devices.

To inspect a card’s bindings: enter dashboard edit mode, open the card’s edit menu, and review the device selected as the card’s data source. Advanced shows every slot. Change a binding only when the suggested source is incorrect or the card needs information from another device. Structured cards use named function slots so the card knows which field represents mode, setpoint, fan, status, and similar functions.

The following table illustrates typical bindings for cards that refer to multiple source devices.

Bindings may point to an RV-C instance/field, a Victron MQTT value, a Bluetooth sensor reading, a Shelly/MQTT device field or a OneControl device.

18.10 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:

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 LaunchControl creates and binds its dashboard card.

Device Fields

A device exposes individual readings and controls as fields, such as a light’s brightness or a thermostat’s mode.

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.

A device’s Advanced settings expose its individual fields and allow changing the field name and unit rounding as well as the calculated offset and multiplier (which are set by default to the RV-C specification); Expert mode lists every field the device defines.

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.

18.11 The control address

GET /api/control on the Hub, authenticated by a session (the Dashboard PIN or a trusted network) or by the API key as ?key=<key> or an Authorization: Bearer <key> header. The key is accepted by this address only.

A successful reply means the Hub accepted and sent the command, not that the device obeyed; the dashboard and displays show the real state as the device reports it.

A.1 Choose your setup path

• Wi-Fi relay, input, or RGBW light: follow the MQTT steps below.
• Shelly BLU RC Button 4: skip MQTT and go directly to Shelly BLU button remote (RC Button 4). It uses the Hub’s Bluetooth.
• Already connected but not working: use the troubleshooting table near the end of this appendix.

A.2 What you need

• A Shelly Gen2, Gen3 or Gen4 device: the Plus and Pro lines, Gen3 and Gen4 relays, input devices such as the Plus i4, and the Plus RGBW PM colour LED controller. First-generation Shelly devices (the original Shelly 1 and Shelly 2.5) are not discovered automatically yet.
• The Shelly joined to the same network as the Hub: the RV router's Wi-Fi, or the network the Hub is connected to.
• Your selected broker address: the Hub’s address shown on the MQTT card when using its built-in broker (for example 192.168.8.8:1883), or the Cerbo’s IP address and port 1883 when using Victron GX.

A.3 Turn on the Hub's broker

Skip this section if you are keeping a Cerbo’s broker; continue with Configure the Shelly using the Cerbo’s address.

1Open the MQTT card. Go to Settings → Integrations → MQTT and press Set up (or Manage).

2Choose the built-in broker. Turn on MQTT and choose Use Hub's built-in broker.

3Leave sign-in blank. Leave the username and password empty unless you want devices to sign in. If you set them, every Shelly needs the same username and password.

4Save. Press Save changes. The card shows the Broker address and how many clients are connected.

A.4 Configure the Shelly

Open the Shelly's own web page by typing its IP address into a browser (the Shelly app shows the address in the device's settings). Then open Settings → MQTT and set:

Press Save. Some models restart to apply the change. When using the Hub’s built-in broker, its MQTT card then counts one more client.

A.5 Add Shelly devices

1Open the scan. On the Devices page choose Add devices → Scan for Shelly devices. The list shows the Hub's address to use, and fills in by itself.

2Wait for the device. A Shelly appears within about a minute of connecting, with its model name, its relay state (On or Off) and its internal temperature.

3Add each channel. Press Add next to each relay or input you want. A device with several relays, such as a Pro 4PM, lists each relay separately; each becomes its own LaunchControl device.

4Create cards. Close the list. When it offers Create cards, accept it.

What each kind becomes:

Rename devices and cards as you like; the name has no effect on how they work. To show a relay as a fan, add a Fan card and bind its Switch to the Shelly's Relay field. Already-added channels show Added in the scan.

You can also select Shelly devices on the Devices page and press Create cards for selected later.

A.6 Colour lights (Plus RGBW PM)

The Plus RGBW PM drives an RGBW LED strip: red, green and blue LEDs that mix into a colour, plus a separate white LED.

A.7 Inputs: Switch and Button mode

Each Shelly input has a type, set in the input's settings in the Shelly app or on the Shelly's web page:

• Switch (a toggle or rocker switch that stays on or off): the input reports On or Off. LaunchControl shows it on a card and can use it as an automation trigger.
• Button (a momentary push button): the input reports presses only, not a state. It appears in the scan as Button mode and does not get a card. Use it to run a macro instead (below).

A.8 Run a macro from a Shelly button

1Set the input to Button. In the Shelly app, set the input type to Button, and make sure the Shelly is connected to the Hub's broker.

2Press it once. A button appears in LaunchControl after its first press.

3Attach it to a macro. Open Settings → Automations, open a macro (or create one), and under Also run when a Shelly button is pressed choose the input and Single press, Double press, Triple press or Long press.

4Save. Press Save. The macro now runs within about a second of that press.

Each macro can have one button trigger. Different presses of the same button can run different macros, for example a single press for "Lights on" and a long press for "All off".

A.9 Shelly BLU button remote (RC Button 4)

The BLU RC Button 4 talks to the Hub directly over Bluetooth; it needs no broker and no Shelly gateway. Bluetooth must be on (Settings → Integrations → Bluetooth).

1Add it. On the Devices page choose Add devices → Scan for Bluetooth devices and press any button on the remote while the scan runs. Press Add beside it.

2Name it , and enter its encryption key only if encryption is turned on for it in the Shelly app.

3Pick what each press does. Each of the four buttons has seven press types (press, double, triple, long, long double, long triple, hold). For each, choose Run a macro, Recall a lighting scene, Toggle a device, Turn a device on, Turn a device off or Turn an automation on/off, then press Save.

The editor's Last press line shows what the Hub heard, which is the quickest way to tell the buttons apart. While a remote is added the Hub listens to Bluetooth continuously, so a press acts at once.

A.10 Use Shelly devices in automations

• As a trigger: in an automation's Sensor, choose the Shelly device (marked MQTT) and its field: Relay, Switch input, Input or Temperature. On and off read as 1 and 0, so a rule with Above 0.5 fires when the input turns on.
• As an action: use Switch a card with the Shelly's switch card and On or Off. The same works from Siri shortcuts and the Touch 8.

A.11 After a restart

Shelly devices do not repeat their state on their own, so the Hub asks each one for it whenever it reconnects. After the Hub restarts, Shelly cards show their state again within about 35 seconds: that is how long a Shelly waits before reconnecting.

Shelly devices, their switch settings, their macro button triggers, colour lights' remembered colours and the colours saved in Lighting scenes are included in Download backup and come back with a restore.

A.12 Troubleshooting