> For the complete documentation index, see [llms.txt](https://docs.kemperconnect.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kemperconnect.de/asset-types/kemper-connect-bridge.md). # KEMPER Connect Bridge The **KEMPER Connect Bridge** is a small gateway that brings existing KEMPER machines online. Unlike a smart device with built-in connectivity, the Bridge is connected to a KEMPER machine and forwards its data to KEMPER Connect. This lets you monitor and control machines that would otherwise have no cloud connection. {% hint style="info" %} The most important thing to understand: **the Bridge is one physical device, but in KEMPER Connect it shows up as the machine it is plugged into.** Once the Bridge knows which machine it is connected to, the whole asset automatically turns into that machine's dashboard. {% endhint %} ### Device Identification | Property | Value | | ---------------- | ----------------------------------------------------- | | **Type** | Gateway / retrofit module | | **Connectivity** | Connects an existing KEMPER machine to KEMPER Connect | | **PIN code** | None - the serial number is used as the claim code | ### What Makes the Bridge Special
A normal KEMPER device already "is" its product (for example an AirDome). The Bridge is different: 1. On its own, the Bridge has no machine behind it. It must first be **physically connected** to a KEMPER machine. 2. After it is connected and powered, the Bridge reports **which machine** it is attached to. 3. KEMPER Connect then **automatically adapts** the asset: the name, product image, dashboard, history and controls all change to match the connected machine. This means you do not configure the machine type by hand. You simply connect the Bridge, and the platform figures out the rest. #### Great for Sales and Distributors (Demos) Because a single Bridge can be moved between machines and the dashboard adapts automatically, the Bridge is ideal for **demonstrations**. A sales colleague or distributor can: * Carry one Bridge to a customer site or trade show. * Plug it into different KEMPER machines. * Show the live, machine-specific dashboard for each one - without owning every smart product. One piece of hardware can therefore demonstrate the KEMPER Connect experience for many different machines. ### Adding a Bridge > **Connect first, then register.** Always connect the Bridge to your KEMPER machine *before* you add it in KEMPER Connect. The platform needs the machine connection to recognize the device type. #### Step 1 - Install the Bridge 1. Connect the Bridge to your KEMPER machine following the wiring guide. 2. Power on the machine. 3. Check the Bridge status LED - it lights up **green** when the connection is working. #### Step 2 - Register the Bridge 1. On a site's **Assets** page, click **Add Device**. 2. Choose **KEMPER Connect Bridge** as the device type. * The dialog shows a product image so you can confirm you have the right hardware.
3. Confirm the connection reminder *"Did you connect the Bridge to your KEMPER device?"* - expand it for an example photo and a link to the connection guide. 4. Enter the **serial number** printed on the Bridge. * There is **no PIN code** for the Bridge. The serial number is also used as the claim code, so the serial is all you need. 5. Click **Add Device**.
The expandable reminder shows an example of a correctly connected Bridge (status LED green) and links to the connection guide:
After a short setup, the device is added with the standard **180 days of free access**, and you can jump straight to the new device with **View Device**. #### Regular Device vs. Bridge | | Regular KEMPER Device | KEMPER Connect Bridge | | -------------------------- | ----------------------- | ------------------------------------------- | | Device type choice | "Regular KEMPER Device" | "KEMPER Connect Bridge" | | Serial number | Required | Required | | PIN code | Required | **Not required** (serial is the claim code) | | Connect to a machine first | Built in | **Yes - connect before registering** | ### After Adding: Awaiting Data Right after registration, the Bridge may briefly show an **"Awaiting data"** state. This is normal: * The Bridge has been added, but it has not yet reported which machine it is connected to. * The asset shows a Bridge setup screen with the connection guide and online/offline status. As soon as the Bridge sends data, the asset **automatically transforms** into the connected machine - correct name, product image, dashboard, history and controls. ### Supported Connected Machines When the Bridge reports its connected machine, the asset becomes one of these types: | Connected Machine | Shown In KEMPER Connect As | | -------------------------------- | -------------------------- | | VacuFil Compact | VacuFil Compact dashboard | | MaxiFil Clean | MaxiFil Clean dashboard | | Automation Line / PAL-Filterunit | Automation Line dashboard | | AirDome | AirDome dashboard | | Clean Air Tower (Self-Cleaning) | Clean Air Tower dashboard | From this point on, a Bridge-connected machine behaves like the native machine: same dashboard layout, the same **Functions** tab for remote start/stop, and the same history charts. In the assets list, a Bridge-connected machine is listed under its real product name (here an AirDome), not as "Bridge":
Opening the device shows the machine-specific dashboard - for example the full AirDome dashboard, even though the underlying device is a Bridge:
### Device Tabs | Tab | Description | | --------- | ----------------------------------------------------- | | Dashboard | Live status and measurements of the connected machine | | History | Historical performance charts (with license) | | Functions | Remote start/stop of the connected machine | | License | License management | | Settings | Device name, location and technical info | The **Functions** tab lets you start and stop the connected machine remotely through the Bridge:
### Using the Bridge in Automation A Bridge-connected machine can be **controlled automatically** by an AirWatch air-quality sensor, exactly like a native filtration device. How it works for the end user: * An **AirWatch** sensor measures the air quality (PM10). * When PM10 rises above your chosen threshold, the connected machine is turned **on**. * When PM10 falls back to or below the threshold, the machine is turned **off**. To set this up, open **Automation** for the site, create a rule, pick the AirWatch as the trigger, and select your Bridge-connected machine as the target. The machine appears in the device list under its real name (for example "VacuFil Compact"), not as "Bridge". **Step 1 - choose the AirWatch sensor that triggers the rule:**
**Step 2 - select the Bridge-connected machine(s) to control:**
{% hint style="info" %} The Bridge is always a **target** (a machine being controlled), never the trigger. Only AirWatch sensors act as triggers. {% endhint %} See Automation Rules for details. {% content-ref url="/pages/F7bAH0RekBubqgdomLMO" %} [Automation](/automation/notifications.md) {% endcontent-ref %} ### Using the Bridge in the Scheduler A Bridge-connected machine can also be switched **on or off by time**, just like native devices.
How it works for the end user: * Open **Schedulers** for the site and create a schedule. * Choose the machine(s) to control - Bridge-connected machines appear under their real machine name. * Set the **time**, the **days of the week**, and whether the schedule should **switch on** or **switch off**.
{% hint style="info" %} Each schedule performs **one action at one time**. For "on in the morning and off in the evening", create two schedules (one ON, one OFF). {% endhint %} See Schedulers for details. {% content-ref url="/pages/06f4a6d4c4f1e700dffca2a4604596770e07f573" %} [Schedulers](/automation/schedulers.md) {% endcontent-ref %} ### Things to Keep in Mind * **Connect before you register.** The Bridge must be wired to a KEMPER machine first; otherwise it cannot report its device type. * **No PIN code.** Only the serial number is needed when adding a Bridge. * **Wait for data.** Automation and Scheduler can only use a Bridge-connected machine after it has reported its type. While a Bridge is still "Awaiting data", it will not appear in the device pickers. * **It looks like the machine, not the Bridge.** Across the assets list, dashboards, automation and scheduler, the asset is shown as the connected machine - this is intentional. ### Related Documentation * Assets List - Adding and managing devices * Automation Rules - AirWatch-triggered control * Schedulers - Time-based control * License Management - Vouchers and grace periods ### The Bridge Hardware This section summarizes the physical Bridge module for end users. For the full details, see the official operating manual that ships with the product. #### How it connects * The Bridge plugs into the filter machine through a **4-pin M8 connector**. This single cable both **powers** the Bridge and carries the machine's data - the Bridge has no separate power supply or battery. * It connects to the internet over the **mobile network** (primarily LTE / 4G), automatically falling back to **3G or 2G** where coverage is weaker. No Wi-Fi or cabling to your network is required. * Once connected, it sends the machine's operating data to the KEMPER Connect cloud **every 5 minutes**. * The Micro-USB port is for KEMPER service/programming only - it is **not** used during normal operation. * An integrated **magnet** lets you attach the Bridge to a metal surface on or near the machine. > Indoor use only. The Bridge is not weatherproof. #### Status LED The Bridge has a single status LED that shows its current connection state. This is the quickest way to check whether the Bridge is working before looking in the app. | LED | Meaning | | -------------------------------------- | -------------------------------------------------------------------------------------- | | **Blue, blinking** | Offline - the Bridge is trying to connect to the mobile network. | | **Green, blinking fast** | Connected to the mobile network and establishing the connection to the cloud. | | **Green, pulsing (fading in and out)** | Fully connected to the mobile network and the cloud. This is the normal working state. | | **Red, blinking** | Error - no data is being transmitted. | > When the LED is **green and pulsing**, data is reaching the cloud. Shortly after, the device leaves the **"Awaiting data"** state in KEMPER Connect and shows its real machine type. ### Troubleshooting | Symptom | Possible cause | What to do | | ------------------------------------------ | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Bridge has no function, status LED is off | No power supply | Make sure the connected filter machine is switched on and powered. | | Bridge has no function, status LED is off | Data cable not connected correctly, or defective | Check the plug connections. Replace the cable if it is damaged. | | No data transmission | No mobile network connection | Check mobile coverage at the location. If needed, move the machine/Bridge to a spot with better reception. Check the plug connections. | | Irregular data transmission | Weak mobile signal or network congestion | Check mobile coverage at the location. | | Status LED blinks red (10x short) | Software error or system crash | Disconnect the Bridge from power for 10 seconds. If it persists, disconnect the filter machine from power for 10 seconds. If it still persists, contact KEMPER service. | | Device stays on "Awaiting data" in the app | Bridge not yet connected to the cloud, or not reporting its machine type | Check the status LED (it should be green and pulsing). Work through the steps above. Make sure the Bridge is connected to a supported machine. | > If a fault remains after these steps, contact KEMPER service. ### Care and Maintenance The Bridge is **maintenance-free** and needs no routine servicing. To keep it running reliably: * Occasionally check the module and cable for damage, corrosion or dirt, and confirm the status LED shows a normal state. * Clean with a slightly damp, soft cloth only. Do not use solvents or abrasive cleaners, and never immerse the Bridge in water. * Firmware and software updates are performed by KEMPER or authorized service partners only. ### Placement and Safety * **Indoor only**, in air free of dust, acids and corrosive gases; up to 1000 m above sea level. * Operating temperature: **+5 °C to +40 °C**. * The Bridge contains a mobile radio module. Do not use it near medical devices (e.g. pacemakers, insulin pumps), in hospitals, at filling stations, near high-precision electronics, or in strong electromagnetic fields. * Do not use the Bridge as a shelf for objects or liquids, and do not expose it to direct water jets. ### Technical Data | Property | Value | | ----------------------- | --------------------------------------------------------------- | | Protection class | IP 42 | | Mobile networks | LTE / 4G, with automatic fallback to 3G / 2G (country-specific) | | Data interval | Every 5 minutes | | Operating temperature | +5 °C to +40 °C | | Weight | 0.2 kg | | Connection cable length | 0.6 m | | Machine connection | 4-pin M8 | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kemperconnect.de/asset-types/kemper-connect-bridge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.