# Overview Welcome to the KEMPER Connect frontend documentation. This industrial asset management platform enables monitoring and control of KEMPER air filtration and quality monitoring devices. KEMPER Connect is an industrial asset management platform designed for monitoring and controlling air filtration and quality monitoring equipment in industrial environments such as welding shops, manufacturing facilities, and production halls. ## Quick Links ### Register a new Asset Got a new KEMPER filter unit, AirWatch, or any other KEMPER device, powered by KEMPER Connect? See the following guide on how to register this on KEMPER Connect. {% content-ref url="/pages/sEtsGiyW1BUS6H97n841" %} [Register Device](/common/register-device) {% endcontent-ref %} ### License Management Running out of licenses or having questions regarding renewal, grace period, or any other topics on license management? {% content-ref url="/pages/11d1400372bed41d249eedabc8553cdcc997b835" %} [License Management](/common/license-management) {% endcontent-ref %} ### Migration Are you already registered with KEMPER Connect, but are new to the new platform? Are you unsure how to start migrating existing devices to the new platform? {% content-ref url="/pages/dgOdKVpSHAPr0Dz35EPR" %} [Migration Guide](/getting-started/migration-guide) {% endcontent-ref %} ## Key Features ### Asset Management * Centralized device inventory across multiple sites * Real-time device status monitoring (online/offline) * Device configuration and settings management * License management with voucher activation ### Air Quality Monitoring * PM2.5 and PM10 particulate matter measurement via AirWatch sensors * WHO guideline reference values * 4-hour rolling averages for industrial compliance * Historical analysis with day/week/month views * Site-wide aggregated air quality indicators ### Air Filtration Control * Remote start/stop control for filtration devices * Volume flow monitoring * Filter pressure and cleaning cycle tracking * Service status and maintenance scheduling ### Automation * PM10-based automation rules (sensor triggers filter devices) * Time-based scheduling for automated operation * Email notifications for threshold alerts ### Energy and Noise Monitoring * Site-wide energy consumption tracking * Noise level monitoring with OSHA compliance references * Historical trends and device breakdowns ## Supported Device Types | Device | Type | Purpose | | ------------------------------- | ---------- | ------------------------------------- | | AirWatch 3.0 | Sensor | Welding fume and PM monitoring | | AirWatch LTE Europe | Sensor | Cellular-connected PM monitoring (EU) | | AirWatch LTE America | Sensor | Cellular-connected PM monitoring (US) | | AirDome | Filtration | Self-cleaning air filtration tower | | Clean Air Tower (Self-Cleaning) | Filtration | Automatic self-cleaning filter system | | Clean Air Tower (Disposable) | Filtration | Disposable filter system | | VacuFil 125 | Extraction | Mobile extraction system | ## User Roles KEMPER Connect supports team collaboration with three roles: * **Admin**: Full access to all features including member management * **Member**: Standard access to monitoring and control features * **Viewer**: Read-only access to dashboards and data ## Multi-Site Support The platform is organized around workspaces (sites), allowing: * Management of multiple facilities from a single account * Site-specific device inventories * Per-site automation rules and schedules * Team members assigned to specific sites ## Internationalization The interface is available in multiple languages: * English * German (Deutsch) # Migration Guide Migrate your KEMPER Connect Assets from Version 1.0 to Version 2.0 ## Overview This guide explains how to migrate from the legacy KEMPER Connect platform to the new KEMPER Connect platform. The migration process is largely automated and requires minimal interaction. The steps and behavior are described below. ## Concept
### No Manual Migration You do not need to manually transfer devices or configurations. The new KEMPER Connect platform automatically detects when you access it after previously using the legacy platform. If such a transition is detected, your devices become eligible for a temporary grace period. The migration itself happens automatically in the background. The platform will display which devices qualify for a grace period. To activate it, simply click **“Activate Grace Period.”** No additional setup or data migration steps are required. ### Grace Period When switching to the new platform, eligible devices can be assigned a 60-day grace period. During this period, devices remain fully functional without requiring an active license. This allows sufficient time to transition licensing to the new platform. ## FAQs ### What Happens After the Grace Period Ends? Once the 60-day grace period expires, the device no longer has an active license. In this state: * The device remains visible in the platform. * No new data will be displayed. * Device-related functions, automations, and other feature integrations are disabled. The platform automatically notifies users: * 30 days before the grace period expires * Additional reminders as the expiration date approaches ### Reactivating a Device After Grace Period After the grace period ends, a valid voucher code must be entered in the **License** tab of the respective device to restore full functionality. Voucher codes can be purchased directly from KEMPER. Please contact the sales team for pricing and availability. Relevant contact information is also accessible within the platform. ### Purchasing a Voucher To obtain a voucher code, contact the KEMPER sales team. Once purchased, enter the voucher code in the device’s **License** section to activate the license. ## Troubleshooting ### Not All Devices Are Eligible for Grace Period If you activate the grace period but not all devices in your workspace are eligible, this may indicate that: * The device has already been claimed by another user * The device was previously assigned to multiple workspaces or sites In such cases, please contact platform support or use the live chat feature available via the chat icon in the bottom-right corner of the KEMPER Connect platform. # Register Device This page explains how to add a new KEMPER unit to the KEMPER Connect platform. If you have a new KEMPER device that is compatible with the KEMPER Connect platform, it must be registered to your site (workspace) before it can be used. The registration process is straightforward and only takes a few steps. ## Prerequisites To register a KEMPER device on the KEMPER Connect platform, you will need: * The device **serial number** * The corresponding **PIN code** These details can be found on the device’s type plate (also referred to as the license plate), which is attached directly to the unit. The type plate typically includes both the serial number and the PIN required for registration. ### Cannot find the Serial Number or PIN? If you are unable to locate the serial number or PIN code on the device, please contact KEMPER Support for assistance. You can also use the live chat feature available in the bottom-right corner of the KEMPER Connect platform. ## Registration Process
To register a device: 1. Navigate to the **Asset List** within your site. 2. Click the **Add Asset** button. 3. The **“Add New Asset”** dialog will open. 4. Enter the serial number and PIN code exactly as shown on the device’s type plate. 5. Confirm the registration. Once the information is validated, the device will be added to your workspace. ### License Included Newly registered devices automatically include a 180-day (six-month) free access period. This trial period is activated automatically upon successful registration. No additional steps are required. # License Management Licenses enable access to device dashboards and features in KEMPER Connect. This guide covers license activation, management, and grace periods. ## License Overview ### What Licenses Enable Licensed devices have access to: * Real-time dashboard data * Historical data and charts * Device control functions * Automation and scheduling * Site-wide monitoring inclusion * Report generation ### Unlicensed Devices Without a license: * Basic device listing only * No dashboard access * Excluded from site analytics * Limited functionality ## License Status ### Status Types | Status | Description | | ------------ | ---------------------------------- | | Active | Valid license, full access | | Expiring | Active but expiring within 31 days | | Expired | License has ended | | Grace Period | 60-day trial/migration period | | No License | Never activated | ## Activating Licenses ### Voucher Code Activation
Navigate to device detail page and select the "License" tab.
A modal will appear on your screen.
In this, enter the voucher code, click "Activate" and your License becomes active. ### Voucher Code Format Voucher codes are provided by KEMPER: * Alphanumeric format * Case-sensitive * Single-use per device ### First Device Trial
When adding a new asset to KEMPER Connect, depending on the license type, this device might be eligible for a 180-days trail phase. * 180-day trial for new first-time device * Welcome wizard guidance * No voucher required ## Grace Period ### What is Grace Period? A 60-day access period for: * Existing KEMPER Connect 1.0 users trying the platform and which are migrating from KEMPER Connect 1.0 * Evaluating before purchase ### Grace Period Activation
No special actions required. KEMPER Connect will automatically detect if a grace period is valid for you. ### Activate grace period (for eligible devices) You can also start a grace period from within the device license page.
1. Alert banner appears on Assets page 2. Banner shows count of eligible devices 3. Click "Activate for All (X)" 4. 60-day period begins immediately for all devices ### Grace Period Features During grace period: * Full dashboard access * All features available * Same as active license ### After Grace Period When grace period ends: * License status becomes expired * Dashboard access restricted * Voucher activation required ## License Tab Each device has a License tab showing: ### License Information | Field | Description | | -------------- | ----------------------------- | | Status | Current license state | | Expiration | End date/time | | Days Remaining | Countdown | | Type | License type (standard/trial) | ### Actions | Action | Description | | -------- | --------------------------- | | Activate | Enter voucher code | | Renew | Renew expiring license | | Contact | Contact KEMPER for purchase | ## License Warnings ### Assets Page Alerts The assets page shows warnings:
Expired Licenses * Red alert banner * Count of affected devices * Contact support guidance
Expiring Soon * Yellow alert banner * Count expiring within 31 days * Renewal reminder
Grace Period Available * Blue alert banner * Count of eligible devices * Quick activation option
### Individual Device Warning Device cards/rows show: * License badge with days/status * Warning icons for issues * Visual expiration indicators ## Renewing Licenses ### Before Expiration {% stepper %} {% step %} ### Renew before expiration 1. Contact KEMPER support 2. Receive voucher code 3. Activate on device 4. License extends {% endstep %} {% endstepper %} ### After Expiration {% stepper %} {% step %} ### Renew after expiration 1. Contact KEMPER support 2. Receive renewal code 3. Activate to restore access {% endstep %} {% endstepper %} ## Contact Sales Modal {% stepper %} {% step %} ### Request license purchase via Contact Sales 1. Click "Contact Sales" or license-related CTA 2. Modal displays contact information 3. KEMPER sales contact details shown 4. Request voucher codes {% endstep %} {% endstepper %} ## License and Features ### Feature Availability by License | Feature | Active | Expired | No License | | -------------- | ------ | ------- | ---------- | | Device listing | Yes | Yes | Yes | | Dashboard | Yes | No | No | | History | Yes | No | No | | Functions | Yes | No | No | | Automation | Yes | No | No | | Site analytics | Yes | No | No | | Reports | Yes | No | No | ## Best Practices {% hint style="info" %} * Monitor expiration dates * Set calendar reminders * Renew before expiration {% endhint %} * Track all device licenses for multi-device deployments * Plan bulk renewals and consider enterprise licensing * Activate grace period when ready to evaluate and use the full 60 days productively * Plan purchase before grace period end # Settings KEMPER Connect provides settings at multiple levels: site settings, user settings, and device settings. ## Site Settings ### Accessing Site Settings Click "Settings" in the site sidebar.
### Available Settings | Setting | Description | Editable | | --------- | ------------------------------ | -------- | | Site Name | Display name for the workspace | Yes | | Site ID | Internal identifier | No | | Slug | URL-friendly identifier | No | ### Editing Site Name If you want to change the name of your site, use this settings dialog to do so. ### Site ID and Slug These are read-only identifiers: * **Site ID**: UUID for API/internal use * **Slug**: URL-safe identifier ## User Settings ### Accessing User Settings Navigate to the site overview and click your profile in the navigation header, then select "Settings".
### User Settings Modal | Setting | Description | | ---------- | ------------------------------ | | First Name | Your first name | | Last Name | Your last name | | Email | Your email address (read-only) | | Phone | Contact phone number | | Language | Interface language preference | ### Editing User Profile {% stepper %} {% step %} ### Open user settings modal Click your profile and choose "Settings". {% endstep %} {% step %} ### Update fields Modify the editable fields (First Name, Last Name, Phone, Language). {% endstep %} {% step %} ### Save Click "Save" to persist changes. {% endstep %} {% endstepper %} ### Language Selection Available languages: * English * German (Deutsch) * Future translations: * French (Français) * Spanish (Español) * Italian (Italiano) * Dutch (Nederlands) * Polish (Polski) * Portuguese (Português) Language affects: * Interface text * Date/time formats * Number formats ## Device Settings ### Accessing Device Settings Navigate to the device detail page and select the "Settings" tab.
### Common Device Settings
| Setting | Description | Editable | | ------------- | ----------------------------- | -------- | | Device Name | Custom display name | Yes | | Location | Physical location description | Yes | | Serial Number | Device serial | No | ## Settings Best Practices ### Site Names * Use descriptive names * Include location or purpose * Keep consistent naming ### Device Naming * Include location info * Use consistent conventions * Make names searchable ### Location Fields * Be specific * Use a consistent format * Include building/area/zone # Members The Members page allows workspace administrators to manage team access to a site, including inviting new members and viewing current team composition. ## Accessing Members Click "Members" in the site sidebar.
## Members List ### Active Members The page displays all active members with: | Field | Description | | -------- | ---------------------------- | | Name | Member's first and last name | | Email | Member's email address | | Phone | Phone number (if provided) | | Language | Preferred interface language | ### Pending Invitations
Below active members, pending invitations show: * Invited email address * Invitation status * Time since invitation sent ## User Roles ### Role Permissions | Role | Description | Permissions | | ---------- | --------------- | ---------------------------------------------- | | **Admin** | Full access | All features, member management, site settings | | **Member** | Standard access | Monitoring, device control, automation | | **Viewer** | Read-only | View dashboards and data only | ### Role Comparison | Feature | Admin | Member | Viewer | | -------------------- | ----- | ------ | ------ | | View dashboards | Yes | Yes | Yes | | View device details | Yes | Yes | Yes | | Control devices | Yes | Yes | No | | Edit device settings | Yes | Yes | No | | Manage automation | Yes | Yes | No | | Manage schedules | Yes | Yes | No | | Manage notifications | Yes | Yes | No | | Invite members | Yes | No | No | | Edit site settings | Yes | No | No | ## Inviting Members ### Add Member Modal ### Add member
Click "Add Member" button. A modal will appear. On it, enter member's email address and click "Send Invitation". ### Invitation Process {% stepper %} {% step %} ### Send invitation * Invitation email sent to new member {% endstep %} {% step %} ### Accept invitation * Member clicks invitation link {% endstep %} {% step %} ### Account creation / acceptance * Member creates account (if new) or accepts (if existing) {% endstep %} {% step %} ### Access granted * Member gains access to site {% endstep %} {% endstepper %} ### Invitation Expiration * Invitations remain valid until accepted * Admins can resend if needed * Pending invitations visible in list ## Member Details Each member entry shows: ### Name Display * First name and last name * Falls back to email if name not set ### Contact Information * Email address (always visible) * Phone number (if provided) ### Language Preference * Displayed as language code (EN, DE, etc.) * Reflects member's interface language choice ## Managing Members ### Viewing Member Info Click on a member to view full details: * Complete contact information * Role assignment * Account status ## Supported Languages Members can set their preferred language: | Code | Language | | ---- | ---------------- | | EN | English | | DE | German (Deutsch) | # Assets List The Asset List provides a centralized overview of all registered devices in your workspace. ## Overview The Asset List is the central interaction point within your workspace for accessing and managing all Kemper Connect-compatible devices. It provides a structured overview of every registered asset and serves as the primary navigation entry to device-specific views and dashboards. Assets can be displayed either in a structured table format or, alternatively, in a grid view where each asset is represented as an individual card. ## Features The Asset List does more than simply display all registered devices. It also includes key operational indicators that provide a high-level summary of your asset landscape. In this sense, the Asset List can be considered a focused sub-dashboard dedicated specifically to asset management and operational visibility. ### Asset KPI Overview At the top of the page, aggregated KPIs provide a quick overview of the current state of your assets.
#### Total Assets Displays the total number of assets currently registered within your workspace or site. #### Assets with Active Licenses Indicates how many registered assets currently have an active license assigned. #### Online Assets Shows the number of devices that have recently transmitted data. “Online” in this context means that the device has sent data within a defined recent time window. Devices not counted as online are not necessarily offline; they may simply not have transmitted data within that period. #### Assets with Service Required Displays the number of devices that currently require maintenance based on configured service intervals. For detailed service evaluation and status categorization, the dedicated Service Dashboard provides a more comprehensive overview. ### Notification Banners
The Asset List page also serves as a central notification surface. System-relevant issues such as license expirations, service requirements, or other operational alerts are displayed as banners at the top of the page, ensuring immediate visibility. ### Asset Table
The Asset Table is the primary interaction element of the Asset List. It provides a structured overview of all assets currently registered within your workspace, enabling quick navigation, status review, and operational checks. #### Search For workspaces with a large number of assets, the search function allows users to quickly locate specific devices without manually browsing through multiple pages of results. #### Table Columns The Asset Table includes the following information: * **Name of Asset**\ Displays the asset name. A default name is assigned during registration, but it can be customized at any time. * **Operations Status**\ Indicates the current operational state of the device, such as online, offline, running, idle, or reporting issues.\ Operational status definitions may vary depending on the specific device type. * **Key Metrics**\ Shows the primary performance indicator relevant to the respective asset type. Each device category has its own key metric reflecting its core functionality. * **Next Service In**\ Displays the remaining time (in days or hours) until the next scheduled service interval is due. * **License**\ Indicates the current license status directly within the table. * **Product**\ Specifies the asset or product type associated with the device. * **Last Heard**\ Shows the timestamp of the most recent data transmission received from the device. # Error Codes Error Code Reference for KEMPER Connect Assets This reference documents every error and warning code shown by KEMPER Connect for the supported device types. Each entry explains what the code means, the typical cause, the expected impact on extraction performance and the recommended action. ### Overview KEMPER devices report two kinds of conditions, each encoded as a bitmask on a dedicated status register: * **Errors (FAULT register)** — critical faults that stop or seriously degrade operation. Shown in red in the UI. Require immediate attention. * **Warnings (WARNING register)** — non-critical conditions that still allow operation, but indicate that something should be addressed soon. Shown in amber in the UI. A value of `0` on either register means the register is healthy. Any non-zero value is a sum of one or more active bits — the UI decodes the bitmask and displays each active condition with its code, short message and longer description. #### Where codes appear * **Asset list** — affected devices carry a red or amber badge. * **Dashboard** — a colored alert box lists every active code with a detailed description. * **Settings panel** — the current fault / warning register is shown, along with each decoded condition. #### How to read this document Each code is documented in the same format: * **Severity:** `Error` (critical, red) or `Warning` (non-critical, amber) * **Description:** What the condition means and why it matters. * **Typical causes:** Most common real-world reasons for this code. * **What to do:** Immediate actions to resolve or mitigate the issue. Codes that appear on multiple device types are described in full at their first occurrence; later sections cross-reference them. ### Bridge-connected devices Applies to **Automation Line**, **MaxiFil Clean** and **VacuFil Compact** — all devices that connect to KEMPER Connect through the KEMPER Connect Bridge. They share a unified fault and warning register layout. #### Fault codes (FAULT register) **`E01` — Frequency inverter error** * **Severity:** Error * **Description:** The frequency inverter (VFD) driving the fan motor reported a fault. The fan has stopped and extraction is no longer guaranteed. * **Typical causes:** * Motor overload or stalled impeller * Overvoltage, undervoltage or phase loss on the mains supply * Internal inverter fault * **What to do:** * Reset the device once it is safe to do so. * Check that mains supply is within the specified range. * Inspect the fan wheel for mechanical blockage. * If the fault returns immediately, read out the inverter's own diagnostic code and contact service. **`E02` — Modbus communication error** * **Severity:** Error * **Description:** The KEMPER Connect Bridge has lost the Modbus connection to the device controller. Sensor values in the UI may be stale and remote commands may not reach the device. * **Typical causes:** * Damaged, loose or unterminated Modbus cable * Incorrect slave address or baud rate * Electromagnetic interference on the bus * **What to do:** * Verify cabling, connectors and bus termination (120 Ω at both ends). * Confirm the Modbus address matches the Bridge configuration. * Power-cycle the Bridge and the device. **`E03` — Main contactor error** * **Severity:** Error * **Description:** The main contactor (power relay for the motor) did not switch as commanded. Motor power cannot be applied safely and there is a risk of unintended startup. * **Typical causes:** * Stuck or welded contactor contacts * Failed coil or auxiliary feedback contact * Wiring fault between controller and contactor * **What to do:** * **Do not operate** the device until cleared. * Contact KEMPER service — this fault must be resolved by qualified personnel. **`E04` — Motor protection relay error** * **Severity:** Error * **Description:** The motor protection relay tripped because of overcurrent or a short circuit in the motor circuit. * **Typical causes:** * Mechanical blockage of the fan (foreign object, damaged impeller) * Damaged motor winding or cable insulation * Protection relay set too sensitively * **What to do:** * Remove power and inspect the motor for mechanical blockages. * Measure winding resistance and insulation if the fault persists. * Reset the protection relay before restarting; if it trips again, contact service. **`E05` — Voltage supply error** * **Severity:** Error * **Description:** Supply voltage is outside the permitted range. The device shut down to protect its electronics. * **Typical causes:** * Missing phase or unbalanced mains supply * Undervoltage due to overloaded site circuit * Upstream UPS or transformer fault * **What to do:** * Verify mains supply (L1 / L2 / L3, N, PE). * Check the main fuses and any upstream protection. * Measure voltage under load; involve a qualified electrician if values are out of spec. **`E06` — Control unit error** * **Severity:** Error * **Description:** The internal control PCB detected an unrecoverable fault (watchdog, memory or firmware). * **Typical causes:** * Transient electrical disturbance * Corrupted firmware after a failed update * Hardware fault on the control board * **What to do:** * Power-cycle the device — this often clears transient issues. * If the error returns, contact KEMPER service for firmware reload or PCB replacement. **`E07` — Motor temperature too high** * **Severity:** Error * **Description:** The motor thermistor (PTC/KTY) has tripped. Continued operation can permanently damage the winding insulation. * **Typical causes:** * Excessive duty cycle at high extraction volumes * Blocked motor cooling openings * Restricted airflow (clogged filter, closed damper) * High ambient temperature in the installation area * **What to do:** * Let the motor cool down fully before restarting. * Inspect the cooling openings and the filter for blockages. * Reduce the duty cycle if the device is being operated continuously at maximum load. **`E08` — Filter pressure critical** * **Severity:** Error * **Description:** Differential pressure across the filter has exceeded the critical threshold. Airflow is severely restricted and the filter may rupture, allowing unfiltered air into the exhaust. * **Typical causes:** * Heavy filter loading that cleaning can no longer recover * End-of-life filter cartridges * Compressed air supply missing, so self-cleaning did not run * **What to do:** * Stop extraction immediately. * Replace or service the filter cartridges. * Verify that compressed air is connected and self-cleaning is enabled. **`E09` — Dust collection bin open** * **Severity:** Error * **Description:** The dust collection bin / drum is not closed or not seated correctly. Dust-laden air could escape into the workplace. * **Typical causes:** * Bin not re-seated after emptying * Damaged or misaligned door switch * Overfilled bin preventing correct closure * **What to do:** * Empty the bin if full and re-seat it with the safety clamps engaged. * Confirm that the door / bin switch activates when the bin is closed. **`E10` — Compressed air not connected** * **Severity:** Error * **Description:** No compressed air is detected. The automatic filter self-cleaning (jet pulse) cannot run, so the filter will clog rapidly and continuous safe operation cannot be guaranteed. * **Typical causes:** * Compressed air hose disconnected or leaking * Supply pressure below the minimum threshold * Closed shut-off valve upstream of the device * **What to do:** * Connect compressed air at approx. 5–6 bar. * Check for leaks and verify supply pressure at the inlet. * Open any upstream shut-off valves. #### Warning codes (WARNING register) **`A01` — Service overdue** * **Severity:** Warning * **Description:** The scheduled maintenance interval has been reached. The device still operates, but service should be carried out soon to keep it within specification. * **What to do:** * Book a service visit (filter check, seals, inspection, calibration). * Acknowledge the warning in the UI after service is complete. **`A02` — Torch pressure too high** * **Severity:** Warning * **Description:** Back-pressure at the welding torch extraction is above the recommended level. Capture efficiency at the source is reduced. * **Typical causes:** * Clogged or kinked torch extraction hose * Blocked torch inlet or swirl plate * Welding wear parts (nozzle, cone) worn or deformed * **What to do:** * Clean or replace the torch hose. * Inspect and clean the torch inlet and wear parts. **`A03` — Filter pressure too high** * **Severity:** Warning * **Description:** Filter differential pressure is above the warning threshold. Automatic cleaning is no longer fully sufficient. * **What to do:** * Plan a filter replacement before the critical threshold (`E08`) triggers a shutdown. * Verify the compressed air supply so cleaning runs at full effectiveness. **`A04` — No volume flow calculation possible** * **Severity:** Warning * **Description:** The device cannot currently calculate the volume flow (sensor missing / invalid, or the fan has not run long enough). IFA-compliant flow monitoring is temporarily unavailable. * **What to do:** * Let the device run for a minute and re-check. * If the warning persists, contact service — a sensor may need to be replaced or re-calibrated. **`A05` — Volume flow too low (IFA signal)** * **Severity:** Warning * **Description:** The extracted air volume has dropped below the minimum required for IFA-compliant safe operation. Capture of hazardous welding fume is no longer guaranteed. This is the IFA signal used for compliance with German occupational safety regulations for welding fume extraction equipment. * **Typical causes:** * Filter clogging (plan a replacement) * Blocked or closed extraction arms / hoods * Kinked or crushed extraction hoses * Open ducts or branches pulling away suction * **What to do:** * Clear any blockages in the extraction path. * Replace the filter if cleaning no longer recovers performance. * Verify that unused branches are closed. **`A06` — Control unit temperature too high** * **Severity:** Warning * **Description:** The internal electronics temperature is above the normal range. Prolonged operation in this state can trigger a protective shutdown. * **What to do:** * Check ambient temperature around the device. * Ensure ventilation openings on the electronics cabinet are clear. **`A07` — Motor temperature too high (warning)** * **Severity:** Warning * **Description:** The motor is running hot and is approaching the thermal trip threshold. Left unresolved, this will escalate to an `E07` fault and a forced shutdown. * **What to do:** * Reduce the duty cycle. * Check motor cooling and airflow path. **`A08` — H13 filter hours exceeded** * **Severity:** Warning * **Description:** The H13 HEPA filter has exceeded its recommended operating hours. Capture efficiency for hazardous dusts may no longer be guaranteed. * **What to do:** * Schedule a replacement of the H13 filter. * After replacement, reset the filter hour counter in the device controller. ### Clean Air Tower (Self-Cleaning / abreinigbar) #### Fault codes (FEHLERCODE register) **`E01` — Frequency inverter error** * **Severity:** Error * See `E01` under Bridge devices for the full explanation. On the Clean Air Tower this is reported on bit 1 of the `FEHLERCODE` register. **`E03` — Compressed air not connected** * **Severity:** Warning * **Description:** No compressed air is detected. The automatic filter self-cleaning cannot run, so the filter will clog rapidly and continuous safe operation cannot be guaranteed. * **What to do:** Connect compressed air at approx. 5–6 bar; check the supply line and any shut-off valves. * **Note:** If compressed air remains missing, the device escalates to the critical error `F96` below. **`E05` — Control error** * **Severity:** Error * **Description:** The internal controller reported a fault. The device may not respond to commands reliably. * **What to do:** * Power-cycle the unit. * Contact KEMPER service if the error persists. **`F96` — Compressed air not connected (critical)** * **Severity:** Error * **Description:** Compressed air has been missing for too long. Filter cleaning has been stopped and the device can no longer guarantee continuous operation. * **What to do:** * Restore compressed air supply before restarting. * Investigate why the supply was lost (leak, closed valve, failed compressor). ### Clean Air Tower (Disposable / Einweg) #### Fault codes (FAULT\_CODE register) **`E00` — Frequency inverter error** * **Severity:** Error * See `E01` under Bridge devices. On this device it is reported on bit 0 as `E00`. **`E02` — Airflow control error** * **Severity:** Error * **Description:** The airflow / VFD control loop cannot reach its setpoint. * **Typical causes:** * Clogged disposable filter * Closed damper or extraction arm * Faulty airflow sensor * **What to do:** * Replace the disposable filter. * Verify that all extraction paths are open. * If the error persists with a new filter, contact service to check the airflow sensor. **`E03` — Maintenance required** * **Severity:** Warning * **Description:** The device has reached its scheduled maintenance interval. * **What to do:** Book a service visit to replace wear parts and keep performance within specification. **`E04` — Motor temperature too high** * **Severity:** Warning * **Description:** The motor is running hot. Continued operation can damage the winding insulation. * **What to do:** * Reduce load and let the motor rest. * Check cooling openings and airflow path. * If unresolved, this escalates to a motor protection shutdown. **`E07` — Modbus error** * **Severity:** Error * **Description:** Communication fault on the internal Modbus bus between the controller and sub-components. Sensor data may be invalid and commands may not reach sub-components. * **What to do:** * Check bus cabling, terminators and addressing. * Power-cycle the device. * Contact service if the error returns. **`E12` — Airflow too low** * **Severity:** Error * **Description:** Measured airflow is below the required minimum. Capture of welding / grinding dust is no longer guaranteed. * **What to do:** * Replace the disposable filter. * Check the extraction hose for kinks and blockages. * Verify extraction arms and hoods are in the correct position. ### AirDome #### Fault codes (FEHLERCODE register) **`F90` — Frequency inverter error** * **Severity:** Error * See `E01` under Bridge devices. On the AirDome this is reported on bit 0 as `F90`. **`F94` — Critical filter pressure** * **Severity:** Error * **Description:** Filter differential pressure has exceeded the critical threshold. Airflow is severely restricted and the filter may rupture. * **What to do:** * Stop operation and replace the filter immediately. * Verify compressed air is connected so self-cleaning can run after the new filter is installed. **`F95` — Control error** * **Severity:** Error * **Description:** The internal controller reported a fault. The device may not respond to commands reliably. * **What to do:** * Power-cycle the unit. * Contact KEMPER service if the error persists. **`F96` — Compressed air not connected** * **Severity:** Warning * **Description:** No compressed air is detected. The automatic filter self-cleaning cannot run, so the filter will clog faster than normal. * **What to do:** Connect compressed air at approx. 5–6 bar. #### Warning codes (WARNING register) **`SER` — Maintenance overdue** * **Severity:** Warning * **Description:** Scheduled maintenance is overdue. * **What to do:** Book a service visit to keep the AirDome within its specified extraction performance and filter capture efficiency. **`A03` — Filter pressure too high** * **Severity:** Warning * **Description:** Filter differential pressure is in the upper warning band. * **What to do:** Plan a filter change soon to avoid reaching the critical threshold `F94`. **`A04` — No flow rate calculation** * **Severity:** Warning * **Description:** Airflow cannot currently be calculated (sensor missing / invalid, or the fan has not been running long enough). IFA-compliant flow monitoring is temporarily unavailable. * **What to do:** * Let the device run for a minute and re-check. * Contact service if the warning persists after a restart. ### VacuFil 125 The VacuFil 125 currently reports its fault code as a single numeric value without a documented bitmask decoding in KEMPER Connect. A value of `0` means "no fault"; any non-zero value should be resolved with the device's on-unit display and, if needed, KEMPER service. * **What to do on non-zero fault:** * Note the raw fault code value shown in the KEMPER Connect UI. * Read out additional details from the device's local display. * Contact KEMPER service with both the raw code and the device serial number. ### Unknown or undocumented codes If a device reports a bit that is not listed in this document, KEMPER Connect will display it as: * `Exx — Unknown error (bit x) — Contact service` (red), or * `Wxx — Unknown warning (bit x) — Check status` (amber). This usually happens after a firmware update that adds new diagnostic bits. In that case: * Note the exact code (for example `E11`) and device serial number. * Capture a screenshot of the dashboard if possible. * Contact KEMPER service so the new code can be documented and added to KEMPER Connect. ### Severity summary At a glance: #### Critical — stop and act immediately * `E01` / `E00` / `F90` — Frequency inverter error * `E03` / `E04` — Main contactor / motor protection (Bridge devices) * `E05` / `E06` — Voltage supply / control unit (Bridge devices) * `E07` — Motor temperature too high (Bridge devices) * `E08` / `F94` — Filter pressure critical * `E09` — Dust collection bin open * `E10` / `F96` (Clean Air Tower) — Compressed air not connected * `E02` / `E12` (Clean Air Tower Einweg) — Airflow control / airflow too low * `E07` (Clean Air Tower Einweg) — Modbus error * `F95` — Control error (AirDome) #### Plan and act soon * `A01` / `SER` — Service overdue * `A02` — Torch pressure too high * `A03` — Filter pressure too high (warning band) * `A05` — Volume flow too low (IFA signal) * `A06` — Control unit temperature too high * `A07` / `E04` (Clean Air Tower Einweg) — Motor temperature warning * `A08` — H13 filter hours exceeded * `E03` (Clean Air Tower) / `F96` (AirDome) — Compressed air not connected (warning) * `E03` (Clean Air Tower Einweg) — Maintenance required #### Transient / informational * `A04` — No volume flow / flow rate calculation possible * `E02` — Modbus communication error (Bridge) — usually resolved by checking cabling ### Getting support When contacting KEMPER service for an error: * Provide the full code (for example `E07`, `F94`, `SER`) and the device serial number. * Note the device type and where it is installed. * Describe any recent events — new installation, filter change, firmware update, power outage. * List the steps already tried from the "What to do" sections above. # Overview Sites are isolated organizational units that structure devices, members, dashboards, and automation per physical location. ## Overview Sites (also referred to as workspaces) are the primary organizational unit within the KEMPER Connect platform. Each site represents a distinct physical location, facility, or operational area containing industrial assets and associated monitoring data. ## What is a Site? A site is a logical grouping of: * **Assets**: Industrial devices (sensors, filtration units, extractors) * **Members**: Team members with access to the site * **Configuration**: Site-specific settings and automation rules Typical examples of sites: * Manufacturing plant * Welding workshop * Production hall * Regional facility ## Navigation The site view forms the central navigation layer of the platform. Within a selected site, the left-hand sidebar provides access to all available modules and features, such as dashboards, asset lists, automation, reporting, and other operational tools. Navigation is always contextual to the currently selected site. ## FAQs ### Can I have multiple Sites? Yes, multiple sites can be created. However, site creation is not available directly within the user interface. To create additional sites and manage device distribution across them, please contact platform support for assistance. ### What is the purpose of Sites? Sites allow structured grouping of devices, members, dashboards, automation rules, and operational overviews. They are particularly useful when managing multiple buildings, shop floors, or geographically separated facilities. In such cases, it is recommended to create a separate site for each location to maintain clear operational boundaries and reporting structures. Members can belong to multiple sites and switch between them using the site selector. Automation rules, notifications, and scheduling configurations are defined per site. Therefore, if different facilities require distinct automation logic or alert schedules, separate sites must be configured accordingly. # AirDome # dashboard The AirDome dashboard provides real-time monitoring of the air filtration system, including motor status, air flow, filter condition, and service status. ## Dashboard Layout ### Header Section * **Device name** and model * **Status badge** (Running / Stopped / Idle / Offline / Error) * **Location** (if configured) * **Last seen** timestamp * Subtitle: "Self-cleaning air filtration system monitoring" ### Motor Status Card Displays motor operating state: | Field | Description | | --------------- | ------------------------- | | **Status** | Running or Stopped | | **Motor Power** | Current consumption in kW | Visual indicator: * Green icon when running * Gray icon when stopped * Red icon on error ### Volume Flow Card Shows current air filtration rate: | Field | Unit | Description | | --------------- | ---- | ------------------------- | | **Volume Flow** | m³/h | Air volume being filtered | Displays: * Current flow rate value * Unit label (m³/h) * Trend indicator if available ### Filter Status Card Filter health and cleaning information: | Field | Unit | Description | | -------------------- | ----- | --------------------- | | **Filter Pressure** | Pa | Pressure differential | | **Filter Cleanings** | count | Total cleaning cycles | {% hint style="info" %} Higher filter pressure indicates loading. Cleaning cycles reflect filter utilization. {% endhint %} ### Service Due Card Maintenance tracking: | Field | Description | | ----------------------- | -------------------------------- | | **Operating Hours** | Total hours motor has run | | **Hours Until Service** | Time remaining until maintenance | | **Service Progress** | Percentage toward next service | Visual elements: * Progress bar showing service status * Warning indicator if service due soon * "Service recommended soon" message at ≥90% {% hint style="warning" %} When Service Progress is ≥90% the dashboard shows "Service recommended soon" and displays a prominent warning indicator. {% endhint %} ## Status Display ### Device Status Badge | Badge | Meaning | | -------------------- | -------------------------------- | | **Online - Running** | Connected and actively filtering | | **Online - Stopped** | Connected but motor not running | | **Online - Idle** | Connected, standing by | | **Offline** | Not connected | | **Error** | Error code detected |
Error Display When an error is detected: * "Service Required" alert shown * Error code displayed * Error description provided
## Real-Time Updates The dashboard updates when: * Device transmits new data * Motor state changes * Error conditions occur
Offline State When device is offline: * Last known values displayed * "Offline" badge shown * Timestamp of last communication
## Related Documentation * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance over time * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Error codes and configuration # settings The Settings tab displays device configuration, error status, and operating information for the AirDome filtration system. ## Accessing Settings Navigate to the device detail page and select the "Settings" tab. ## Device Information Card ### Basic Settings | Field | Description | Editable | | ----------------- | ----------------- | -------- | | **Device Name** | Display name | Yes | | **Serial Number** | Device identifier | No | | **Location** | Physical location | Yes | ### Device Type Info | Field | Value | | --------------- | -------------------- | | **Device Type** | Air Filtration Tower | | **Filter Type** | Self-Cleaning | ## Error Status Card ### Current Error Status | Field | Description | | -------------- | ------------------------------------- | | **Error Code** | Current error (FEHLERCODE field) | | **Status** | "System Healthy" or error description | ### Healthy State {% hint style="success" %} When no errors: * Shows "0 (OK)" * "No errors detected" message * Green indicator {% endhint %} ### Error State {% hint style="danger" %} When an error is detected: * Shows error code * Error description * Red indicator * "Service Required" alert {% endhint %} ### Error Codes | Code | Description | | ---- | ---------------------------- | | 0 | No error (OK) | | F90 | Frequency inverter error | | F94 | Critical filter pressure | | F95 | Control error | | F96 | Compressed air not connected | ### Warning Codes | Code | Description | | ---- | ------------------------ | | 0 | No warning | | SER | Maintenance overdue | | A03 | Filter pressure too high | | A04 | No flow rate calculation | ## Operating Information Card ### Service Tracking | Field | Unit | Description | | ----------------------- | ---- | ------------------------------------- | | **Operating Hours** | h | Time motor has been running | | **Hours Until Service** | h | Remaining until maintenance needed | | **Service Progress** | % | Progress toward next service interval | ### Service Progress Display * Progress bar visualization * Percentage complete * Warning threshold at 90% * Critical threshold at 100% ### Service Status Messages | Threshold | Message | | --------- | -------------------------- | | < 90% | Normal operation | | ≥ 90% | "Service recommended soon" | | 100% | Service overdue | ## Editing Settings {% stepper %} {% step %} ### Edit Device Name 1. Click edit icon on device name 2. Enter new name 3. Save changes 4. Name updates across platform {% endstep %} {% step %} ### Edit Location 1. Click edit icon on location 2. Enter physical location description 3. Save changes 4. Helps identify device in facility {% endstep %} {% endstepper %} ## Technical Information ### System Information | Field | Description | | -------------- | ---------------------- | | **Model** | AirDome | | **Connection** | Online/Offline status | | **Last Seen** | Last data transmission | ## Troubleshooting
Error F90 - Frequency Inverter * Check inverter connections * Verify power supply * May require service technician
Error F94 - Filter Pressure Critical * Filter may be overloaded * Check cleaning system * May need filter replacement
Error F95 - Control Error * System control issue * Restart may help * Contact support if persists
Error F96 - Compressed Air * Check air supply connected * Verify air pressure adequate * Required for filter cleaning
Warning SER - Maintenance * Schedule maintenance * Operating beyond service interval * Contact KEMPER service
## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Device control * [Error Codes](file:///reference/error-codes.md) - Complete error reference * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # overview AirDome is KEMPER's air filtration tower system, designed for large-scale air cleaning in industrial environments. It features a self-cleaning filter system with automated maintenance. ## Device Identification | Property | Value | | --------------- | -------------------- | | **Slug** | `airdome` | | **Type** | Air Filtration Tower | | **Filter Type** | Self-Cleaning | ## Purpose AirDome units are designed to: * Filter large volumes of air in industrial halls * Remove welding fumes and particulate matter * Operate with automatic filter cleaning * Integrate with air quality sensors for automated control ## Key Measurements ### Motor Status | Measurement | Unit | Description | | ----------------- | ------- | ----------------------------------------------- | | **Motor Running** | Boolean | Current motor operating state (Running/Stopped) | | **Motor Power** | kW | Current power consumption | ### Air Flow | Measurement | Unit | Description | | --------------- | ---- | ---------------------------------- | | **Volume Flow** | m³/h | Air volume being filtered per hour | ### Filter Status | Measurement | Unit | Description | | -------------------- | ----- | ----------------------------------- | | **Filter Pressure** | Pa | Pressure differential across filter | | **Filter Cleanings** | Count | Total automatic cleaning cycles | ### Service | Measurement | Unit | Description | | ----------------------- | ---- | -------------------------------- | | **Operating Hours** | h | Total motor running time | | **Hours Until Service** | h | Time remaining until maintenance | ## Status Indicators | Status | Description | | ----------- | --------------------------------------- | | **Running** | Motor actively operating, filtering air | | **Stopped** | Motor not running | | **Idle** | Online but not actively filtering | | **Error** | Device has reported an error code | ## Error Codes AirDome reports both errors and warnings. ### Errors (FEHLERCODE) | Code | Description | | ---- | ---------------------------- | | 0 | No error (OK) | | F90 | Frequency inverter error | | F94 | Critical filter pressure | | F95 | Control error | | F96 | Compressed air not connected | ### Warnings (WARNING) | Code | Description | | ---- | ------------------------ | | 0 | No warning | | SER | Maintenance overdue | | A03 | Filter pressure too high | | A04 | No flow rate calculation | ## Device Tabs When viewing an AirDome device: | Tab | Description | Documentation | | --------- | ------------------------------- | -------------------------------------------------------------------- | | Dashboard | Current status and measurements | [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) | | History | Performance history charts | [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) | | Functions | Start/Stop control | [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) | | License | License management | [License](file:///common/license.md) | | Settings | Error codes and info | [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) | ## Automation Target Automation flow example: {% stepper %} {% step %} ### Trigger: Elevated PM10 * AirWatch sensor detects elevated PM10. * Automation rule triggers AirDome start. {% endstep %} {% step %} ### Monitoring: PM10 Falls * PM10 falls below threshold. * Automation rule triggers AirDome stop. {% endstep %} {% endstepper %} See [Automation Rules](file:///automation/rules.md) for configuration. ## Scheduler Support AirDome supports time-based scheduling: * Define operating hours * Set days of week * Automatic on/off control See [Schedulers](file:///automation/schedulers.md) for setup. ## Service Intervals AirDome tracks service requirements: * Operating hours counter * Hours until maintenance * Service progress percentage * Warning at 14 days remaining * Critical at 0 days remaining ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control * [Error Codes](file:///reference/error-codes.md) - Complete error reference # history The History tab displays performance trends for the AirDome filtration system over time, showing volume flow, motor status, and cleaning events. ## Accessing History Navigate to the device detail page and select the "History" tab. ## Performance History Chart ### Chart title Performance History (24 Hours) ### Chart subtitle Volume flow and motor status over time ### Data series | Series | Color | Description | | ------------------- | --------- | -------------------------------- | | **Volume Flow** | Blue line | Air volume flow in m³/h | | **Motor Status** | Area fill | Operating state (on/off) | | **Cleaning Cycles** | Markers | Automatic filter cleaning events | ### Time range Default view shows 24-hour history with configurable ranges: * 24 hours (default) * 7 days * 30 days {% hint style="info" %} Default view: 24 hours. {% endhint %} ### Chart legend | Element | Description | | ---------------- | -------------------------------------------- | | Volume Flow line | Air volume being filtered | | Status area | Device operating state (shaded when running) | | Cleaning markers | Points indicating cleaning cycles | ## Reading the chart ### Volume flow line * Shows air filtration rate over time * Higher values indicate more air being processed * Drops to zero when motor stops ### Motor status area * Shaded area indicates motor running * Clear area indicates motor stopped * Correlates with volume flow changes ### Cleaning events * Markers show automatic filter cleaning * Indicates filter maintenance activity * Normal operation includes periodic cleaning ## Chart interaction ### Hover * Shows exact values at cursor position * Displays timestamp * Shows volume flow and status ### Legend toggle * Click legend items to show/hide series * Focus on specific metrics ## Historical patterns ### Normal operation * Consistent volume flow when running * Regular cleaning cycles * Expected on/off patterns ### Performance issues * Decreasing volume flow over time * Increased cleaning frequency * Irregular patterns ### Filter loading * Gradual decrease in flow * More frequent cleanings * Indicates filter approaching capacity ## Data resolution | Time range | Resolution | | ---------- | --------------------- | | 24 hours | 5–15 minute intervals | | 7 days | Hourly intervals | | 30 days | Daily aggregates | ## Export and analysis Historical data supports: * Trend analysis * Performance monitoring * Maintenance planning * Compliance reporting ## Related documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Operating information * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # functions The Functions tab provides remote control capabilities for the AirDome filtration system, allowing operators to start and stop the device remotely. ## Accessing Functions Navigate to the device detail page and select the "Functions" tab. ## Device Control ### Available Functions | Function | Description | | ----------------- | ------------------------------ | | **Start AirDome** | Turn on the filtration system | | **Stop AirDome** | Turn off the filtration system | ### Start AirDome Initiates air filtration: {% stepper %} {% step %} ### Click the action Click the "Start AirDome" button. {% endstep %} {% step %} ### Confirm A confirmation modal appears. Confirm to execute. {% endstep %} {% step %} ### Execution Device begins filtering. {% endstep %} {% step %} ### Status Status updates to "Running". {% endstep %} {% endstepper %} ### Stop AirDome Stops air filtration: {% stepper %} {% step %} ### Click the action Click the "Stop AirDome" button. {% endstep %} {% step %} ### Confirm A confirmation modal appears. Confirm to execute. {% endstep %} {% step %} ### Execution Device stops filtering. {% endstep %} {% step %} ### Status Status updates to "Stopped". {% endstep %} {% endstepper %} ## Function Execution Modal When executing a function: ### Confirmation Dialog | Element | Description | | ------------- | ------------------------------ | | Function name | Which action will be performed | | Device name | Target device | | Warning | Confirmation prompt | | Buttons | Confirm / Cancel | ### Execution States | State | Display | | --------- | ------------------------------- | | Idle | Buttons available | | Executing | Loading spinner, "Executing..." | | Success | Success message, auto-dismiss | | Error | Error message with details | ## Remote Control Considerations {% hint style="info" %} Network Latency * Commands may take seconds to reach device * Status update may be delayed * Refresh page if status doesn't update {% endhint %} {% hint style="warning" %} Device Availability * Device must be online * Commands fail if device offline * Check connectivity before issuing commands {% endhint %} {% hint style="danger" %} Safety * Ensure safe conditions before starting * Verify area is clear * Follow local safety procedures {% endhint %} ## Automation Integration Instead of manual control, AirDome can be automated: ### PM-Based Automation * AirWatch monitors air quality * Rule triggers AirDome start when PM10 high * Rule triggers AirDome stop when PM10 low ### Time-Based Scheduling * Define operating hours * Automatic start/stop at scheduled times * Day-of-week configuration See: * [Automation Rules](file:///automation/rules.md) * [Schedulers](file:///automation/schedulers.md) ## Function Categories ### Device Control Primary control functions: * Start/Stop operations * Power management ### Data Functions May include: * Request data update * Force status refresh ## Error Handling ### Command Failed If function execution fails: {% stepper %} {% step %} ### Error displayed An error message is displayed. {% endstep %} {% step %} ### Check device Check device is online. {% endstep %} {% step %} ### Check network Check network connectivity. {% endstep %} {% step %} ### Retry Try again. {% endstep %} {% endstepper %} ### Device Not Responding If device doesn't respond: {% stepper %} {% step %} ### Verify online Verify device is online. {% endstep %} {% step %} ### Check last seen Check last seen timestamp. {% endstep %} {% step %} ### Physical inspection Device may need physical inspection. {% endstep %} {% endstepper %} ## Permissions Function execution requires: * Member or Admin role * Active license on device * Device online status Viewers cannot execute device functions. ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status monitoring * [Automation Rules](file:///automation/rules.md) - Automated control * [Schedulers](file:///automation/schedulers.md) - Time-based control # AirWatch AirWatch summary page. AirWatch is KEMPER's welding fume and particulate matter monitoring sensor. It measures PM2.5 and PM10 concentrations in ambient air, providing real-time air quality data for industrial environments. ## Overview Everything you need to learn about your AirWatch on KEMPER Connect. {% content-ref url="/pages/a40c7a22ba268c240086abe3e40a5c1b20ad8259" %} [Overview](/asset-types/airwatch/overview) {% endcontent-ref %} ## Value Ranges and Limits Having problems understanding, or want to learn more about value ranges, thresholds and limits? Please take a look at the following guide. {% content-ref url="/pages/0BSZqcGaReKsjk0VozOQ" %} [Measurement Concept & PM Classification](/asset-types/airwatch/measurement-concept-and-pm-classification) {% endcontent-ref %} # Overview AirWatch is KEMPER's welding fume and particulate matter monitoring sensor. It measures PM2.5 and PM10 concentrations in ambient air, providing real-time air quality data for industrial environments. ## Device Variants | Variant | Slug | Description | | ------------------------ | ----------------------------- | ----------------------------------------- | | **AirWatch 3.0** | `airwatch-30` | Standard model | | **AirWatch LTE Europe** | `airwatch-lte-europe` | Cellular-connected (European frequencies) | | **AirWatch LTE America** | `kemper-airwatch-lte-america` | Cellular-connected (American frequencies) | ## Purpose AirWatch sensors are designed to: * Monitor welding fume concentrations * Track particulate matter (PM) levels * Provide ambient air quality data * Enable data-driven ventilation control * Support occupational health monitoring ## Key Measurements | Measurement | Unit | Description | | ---------------- | -------- | ------------------------------------------- | | PM2.5 | µg/m³ | Fine particulate matter (≤2.5 micrometers) | | PM10 | µg/m³ | Coarse particulate matter (≤10 micrometers) | | 4h Average PM2.5 | µg/m³ | 4-hour rolling average | | 4h Average PM10 | µg/m³ | 4-hour rolling average | | Total Particles | count/m³ | Total particle count | ## Particle Size Distribution AirWatch provides detailed particle size distribution across six bins: | Bin | Size Range | | ----- | ---------- | | Bin 0 | > 0.3 µm | | Bin 1 | > 0.5 µm | | Bin 2 | > 1.0 µm | | Bin 3 | > 2.5 µm | | Bin 4 | > 5.0 µm | | Bin 5 | > 10.0 µm | ## Measurement Type AirWatch performs **ambient (hall) measurement**, meaning: * Measures general air quality in the facility * Not a point-source measurement * Represents overall workplace conditions * Distinct from Occupational Exposure Limits (OEL) {% hint style="info" %} Curious about how the AirWatch determines particulate levels and why the scale does not reflect typical legal threshold values? Read more on: [Measurement Concept & PM Classification](/asset-types/airwatch/measurement-concept-and-pm-classification) {% endhint %} ## Use Cases ### Air Quality Monitoring * Track PM levels throughout the day * Identify pollution patterns * Compare against WHO guidelines ### Automation Triggers * Trigger filtration devices based on PM10 thresholds * Integrate with AirDome and Clean Air Tower * Automatic ventilation control ### Compliance Support * Historical data for audits * Report generation * 4-hour average calculations ## Device Tabs | Tab | Description | Documentation | | --------- | ------------------------------- | -------------------------------------------------------------------- | | Dashboard | Current measurements and status | [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) | | History | Historical PM data and trends | [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) | | Functions | Device functions | [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) | | License | License management | [License](file:///common/license.md) | | Settings | Device configuration | [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) | ## Status Indicators | Status | Description | | -------------- | ------------------------------------- | | **Online** | Device connected and transmitting | | **Offline** | Device not connected | | **Monitoring** | Actively measuring (normal operation) | ## Integration with Automation AirWatch sensors can serve as triggers for automation rules: * Set PM10 threshold (e.g., 100 µg/m³) * Select target filtration devices * Automatic start/stop based on air quality See [Automation Rules](file:///automation/rules.md) for details. ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Historical analysis * [Air Quality Levels](file:///reference/air-quality-levels.md) - PM ranges * [Automation Rules](file:///automation/rules.md) - PM-triggered automation # Measurement Concept & PM Classification This section explains how AirWatch measures particulate matter (PM2.5 / PM10) and how the displayed load levels are defined and interpreted. ## Introduction Have you ever wondered why the PM2.5/PM10 display in our dashboard does not work 1:1 with legal limits – or why you rarely see “limit exceeded” despite visible welding fumes?
That is exactly the intention. Our system monitors **indoor air**: it measures the air at typical locations in the workshop or hall – i.e., where air circulates, where pollution is distributed, and where ventilation/extraction should be effective. It is not a personal measurement system directly on the welder, nor is it a compliance measuring device for the legally compliant assessment of an individual workplace. That is why we deliberately use exposure levels (guideline values) instead of “limit values.” The goal is not to replace a legal assessment, but to give you a reliable tool to: * Detect pollution in the hall at an early stage * Control ventilation/extraction as needed * Make improvements measurable (before/after, shift comparison) and all this in a practical way, without being permanently on “red alert.” In short: We optimize control and transparency in the hall – not the legal assessment of personal exposure. ## The Problem Many customers initially compare the **AirWatch** PM2.5/PM10 values to legal workplace limit values.\ That comparison is understandable — but it mixes two different measurement concepts. Legal workplace limits are defined for **personal exposure**. In practice, this means they must be measured **on the worker**, in the **breathing zone**, using **personal sampling equipment** and regulated procedures (often based on time-weighted averages). Depending on the regulation, assessments may also require measurements very close to the emission source under defined conditions. **AirWatch** is not used that way. **AirWatch** is a **stationary ambient monitoring device**. It is typically placed near work areas or distributed across the hall to measure **general hall air conditions**, not the exposure of a specific person. {% hint style="info" %} **Because of that:** * A high AirWatch reading **can be a strong indicator** that overall **conditions are poor** and that exposure at certain workstations could also be elevated. * But it **does** **not** prove that a legal workplace **limit has been exceeded** - because the legally relevant value depends on what a person actually inhales (distance to the source, duration, airflow, work position, PPE, etc.). {% endhint %} On top of that, workplace limits and evaluation methods are **country-specific** and depend on local regulations. For legal compliance checks, dedicated personal measurement solutions exist that are designed and certified for that purpose. **AirWatch** is built for a different job: continuous ambient monitoring to detect rising load early, optimize ventilation/extraction, and make improvements measurable — without turning the dashboard into a “legal compliance” statement. ## The Solution Instead of displaying legal limit values, **AirWatch** uses clearly defined operational load levels for ambient hall air. These levels are intentionally designed to: * reflect realistic industrial conditions * provide early indication of rising particulate load * support stable and demand-based ventilation/extraction control * make trends and improvements measurable over time This approach avoids misleading compliance interpretations while still delivering actionable insight. **In simple terms:** **AirWatch** does not determine whether a legal workplace limit has been exceeded — it provides continuous transparency about hall air conditions and enables operational optimization. ## Details ### Dashboard
Values in the dashboard are **not** intended to check legal limit values in the workplace. It is deliberately designed as a **guide for room or hall air** – i.e. for assessing **air quality, extraction efficiency, trends, and control logic** (e.g., automatically increasing ventilation/extraction), not for occupational health or legal assessments of individual persons. ### Why no “limit values”? In welding and industrial halls, there are two completely different worlds of “values” – and these are often confused in practice: **A) Ambient/environmental guideline values (e.g., WHO)** These guideline values are intended for the **general population** and **long-term 24/7 exposure** and are therefore very strict. They are **not** designed as an assessment standard for production halls. **B) Occupational exposure limits (OEL/AGW)** These limits refer to **personal exposure in the breathing zone** (i.e., what a person actually inhales) – typically as an **8-hour time-weighted average** and with **personal measurement** on the employee. Our measurement in the product is **not** close to the person and not in the breathing zone. It would therefore be technically incorrect (and communicatively risky) to derive statements such as “limit value complied with/exceeded” from our values. ### What our sensor actually measures (measurement context) Our devices measure **stationary hall/room air (ambient)** – typically near work areas or distributed throughout the hall for overall monitoring. This does not answer the question: **“Is a single workstation legally within a limit value?”** Rather, it answers this question: **“How high is the general fine dust pollution in the hall – and how effective is ventilation/extraction?”** Important: In practice, values **directly at the source / in the breathing zone** are often significantly higher than values in the room air – simply due to **dilution, air flow, and distance**. ### What the ranges are intended for (purpose of the scale) Our areas are **exposure levels** – not limit values. They are intended to: * Create **transparency** (What is happening in the hall right now?) * Make **trends** visible (before/after, shift comparison, week comparison) * Evaluate the **effectiveness of extraction** (extraction off/on/optimized) * Provide stable thresholds for **automation** (control ventilation/extraction as needed) * Consciously **avoid making “legal/illegal” statements** In short: **Operational optimization instead of legal limit value testing.** ### Scale is not WHO-compliant In industrial environments (especially welding halls), ambient particle values often **remain permanently above typical environmental guidelines**. A scale that is strictly optimized for environmental values would often lead to a permanent “red” status during operation – without this being helpful. Our scale is therefore chosen so that it: * **reflects real industrial processes** (no permanent alarm) * still **responds appropriately to changes** (when conditions actually worsen/improve) * is suitable for **control logic** (no frantic switching at every short peak) ### What the display explicitly does NOT mean The display does not replace: * occupational health measurements (close to people / breathing zone) * the evaluation of individual workplaces * the legal classification according to OEL/AGW/legal limits It means: * **Orientation** regarding hall air pollution * **Comparability** and **traceability** * **Optimization** of extraction and ventilation measures ### Practical relevance: Control of ventilation & energy efficiency A key use case is **demand-based control**: * Only increase extraction/ventilation when pollution levels rise * Step operation depending on level (e.g., “increased” vs. “very high”) * Reduce again during quiet phases → **Save energy**, **reduce running times**, **protect equipment** {% hint style="info" %} **Note on communication (deliberately chosen):** We use terms such as **“load” / ‘level’ / “guideline values”** instead of “limit value” or “healthy/unhealthy” because the product is conceptually a **monitoring and optimization tool for indoor air** – not a compliance measurement system for personal exposure. {% endhint %} # AirWatch Export & Reports Options on how to export data from your AirWatch or how to create an air quality report. The History tab of an AirWatch device offers two ways to take its data with you: | Action | Output | Best for | | -------------- | ------------------------ | ---------------------------------------- | | **Export** | CSV or Excel data file | Raw data, spreadsheets, custom analysis | | **PDF Report** | Print-ready PDF document | Compliance, sharing, stakeholder reviews | Both are reached from the **History** tab of a single device and always operate on **that one device** only. For a site-wide PDF that aggregates all licensed AirWatch devices, use the Air Quality Reports tab instead. ### Accessing Export & Reports 1. Open the device (sidebar **Sites** → select a site → **Assets** → open an AirWatch device). 2. Select the **History** tab. 3. Use the buttons on the right of the controls row: * **PDF Report** — opens the report configuration dialog. * **Export** — opens the data-export dialog. Both buttons are disabled while data is loading or when the current view has no data. URL pattern: `/sites/[id]/assets/[deviceId]` → tab "History".
### Data Export (CSV / Excel) The **Export** button opens a dialog that turns the chart's underlying data into a downloadable file. The current chart selection (range and resolution) is pre-filled, but everything can be overridden before download.
#### Export options | Setting | Choices | Default | Effect | | -------------------------- | -------------------------------------- | ------------- | ------------------------------------------ | | Format | CSV (`.csv`) / Excel (`.xls`) | Excel | File type and delimiter | | Time range | Current view / Custom range | Current view | Which window to export | | Resolution | Auto / 5 min / 15 min / 1 hour / 1 day | Auto | Averaging interval per row | | Include statistics summary | Toggle | on | Adds avg/min/max/median header block | | Include time distribution | Toggle | on | Adds time-in-range breakdown to the header | | Include comparison period | Toggle | follows chart | Adds previous-period columns | | Apply working-hours filter | Toggle | follows chart | Filter rows vs. add marker columns | Before downloading, an estimate (`Estimated: N rows, ~size`) is shown so you know roughly how large the file will be. #### Format details * **CSV** — comma-separated, universally importable. * **Excel** — tab-separated values saved with a `.xls` extension and a UTF-8 BOM, so Excel opens it cleanly with correct `µ` characters. (No `.xlsx` binary is produced.) #### File contents Each file begins with a `#`-prefixed metadata header, then the data rows: * **Header block** — device label, variant, period, resolution, working-hours configuration, generation timestamp, and (optionally) the statistics summary and time-distribution breakdown. * **Column header** — `Timestamp`, `Time`, `PM2.5 (µg/m³)`, `PM10 (µg/m³)`. * **Optional marker columns** — `is_working_hours`, `is_weekend` are added **when the working-hours filter is *****not***** applied**, so you can filter in your own tool instead. * **Optional comparison columns** — `PM2.5_previous`, `PM10_previous` when *Include comparison period* is on. #### Working-hours behaviour | Apply working-hours filter | Result | | -------------------------- | --------------------------------------------------------------------------------- | | **On** | Rows outside the working window are removed; statistics match the filtered rows. | | **Off** | All rows are kept and `is_working_hours` / `is_weekend` marker columns are added. | #### Caching If the chosen range and resolution match what the chart already loaded, the export reuses that cached data instead of re-fetching. Changing the range or resolution triggers a fresh fetch on download. #### Filename ``` airwatch-history_{device}_{start}_to_{end}.{csv|xls} ``` Example: `airwatch-history_Hall-3-Sensor_20260625-0000_to_20260626-0000.xls` *** ### PDF Report The **PDF Report** button opens a dialog containing a configuration card and, after the first preview, a live preview of the document. The PDF is generated through the browser's print-to-PDF — no separate file is downloaded from a server.
The report is **single-device**: it summarises one AirWatch device, with a built-in executive summary and methodology section so it is self-explanatory when shared. #### Report configuration Before generating a preview, you can define custom report metadata and settings. {% hint style="warning" %} All settings are applied when you click **Generate Preview**. Changing a setting afterwards does not auto-refresh — re-click **Generate Preview**. {% endhint %}
| Setting | Type | Default | Effect | | ---------------------------- | ------------------------ | ------- | --------------------------------------------- | | Time Period | Day / Week toggle | Day | Reporting window and chart resolution | | Period navigation | Prev / Next arrows | Current | Step through past periods | | Chart Size | Compact / Normal / Large | Normal | Pixel height of the Historical chart | | Customer / Company | Free text | empty | Printed on the cover page | | Project / Location | Free text | empty | Printed on the cover page | | Additional Notes | Free text | empty | Printed on the cover page | | Compare with Previous Period | Toggle | off | Adds previous-period overlay and trend deltas | | Working Hours Filter | Toggle (+ sub-settings) | off | Restricts statistics to working hours only | #### Time Period | Time Period | Window | Chart resolution | Comparison range (when enabled) | | ----------- | -------------------------- | ----------------- | ------------------------------- | | Day | Calendar day (00:00–24:00) | 15-minute buckets | Previous calendar day | | Week | Calendar week (Mon–Sun) | 1-hour buckets | Previous calendar week | The period label (e.g. *"May 5, 2026"* or *"Apr 28 – May 4, 2026"*) appears between the navigation arrows. The "next" arrow is disabled on the current period. #### Chart Size Controls the pixel height of the Historical chart on its dedicated page. | Option | Chart height | | ------- | -----------: | | Compact | 420 px | | Normal | 520 px | | Large | 600 px | #### Report Information (custom metadata) Three optional free-text fields printed on the cover page: **Customer / Company**, **Project / Location**, **Additional Notes**. Empty fields are omitted. The device serial number is always printed in the header notes line. #### Report Options **Compare with Previous Period** When enabled, the report fetches the previous period (yesterday for *Day*, last calendar week for *Week*) and: * overlays a dashed previous-period line on the Historical chart for PM2.5 and PM10, * adds previous-period values and trend arrows to the Statistics section. Trend classification uses a 5% deadband: changes smaller than ±5% are reported as *Stable*. **Working Hours Filter** When enabled, all statistics, time distributions, exceedance counts, and trends use only data points inside the configured working hours. The Historical chart shows vertical boundary markers at the start/end times. | Sub-setting | Default | Effect | | ---------------- | ------- | --------------------------------- | | Start Time | 06:00 | Beginning of the working window | | End Time | 16:00 | End of the working window | | Exclude weekends | on | Skip Saturday and Sunday entirely | The working-hours configuration is also printed on the cover page. #### Generating the report
1. Pick the **Time Period** and navigate to the desired window. 2. Optionally fill in **Customer**, **Project**, and **Notes**. 3. Toggle **Compare** and/or **Working Hours** as needed. 4. Click **Generate Preview** — data is fetched and the preview renders. 5. Click **Print / Save PDF** — opens the browser print dialog. 6. Choose **Save as PDF** as the destination (or print directly). #### Print dialog tips
The PDF is hardcoded to **A4 landscape** with 10 mm margins. For best results: * Enable **Background graphics** so coloured badges and chart zones print correctly. * Set margins to **Default** or **None** (margins are controlled by the report's CSS). * If a section looks tight, lower the **Chart Size** to *Compact* and re-generate. #### Report structure The single-device PDF has a deterministic layout: | Page | Section | | ------ | ------------------------------------------------- | | 1 | Header + Executive Summary | | 2 | Historical Air Quality (full-page chart) | | 3 | Statistics & Distribution | | 4 | Methodology | | Footer | Data-coverage note (points received vs. expected) | **Page 1 — Header + Executive Summary** Report title (`AirWatch Device Report`), device name (and site name if available), reporting period, generation timestamp, optional Customer/Project/Notes, working-hours configuration (if enabled), comparison range (if enabled), and a narrative **Executive Summary** of top-line trends. **Page 2 — Historical Air Quality** A full-page time-series chart for the single device, titled `Historical Air Quality — {device}` with a `Single-device readings (SN: …)` scope label. Includes PM10 quality-range background bands, PM2.5 (orange) and PM10 (blue) lines, period-average reference lines, optional previous-period overlay, and working-hours boundary markers. **Page 3 — Statistics & Distribution** 1. **Period Statistics** — average, min, max, median for PM2.5 and PM10 (with previous-period values and trend deltas when comparison is on). 2. **Time Distribution** — percentage of time spent in each air-quality range. 3. **Exceedance Summary** — minutes and number of events above each elevated threshold. 4. **Peak Events** — the five highest PM2.5 and PM10 readings (deduplicated within 30 minutes), with timestamps. All blocks use the working-hours-filtered dataset when the filter is on. **Page 4 — Methodology** A short, always-included section explaining how averages, peaks, 4-hour averages, and air-quality classifications are derived, so the report is interpretable out of context. #### Print format | Property | Value | | -------------------- | ----------------------------------------- | | Page size | A4 landscape (297 × 210 mm) | | Margins | 10 mm on all sides | | Page-break behaviour | Each major section starts on a fresh page | *** ### Export vs. PDF Report — which to use? | Need | Use | | -------------------------------------------------- | ------------------------ | | Open the numbers in Excel / a BI tool | **Export** (CSV / Excel) | | Custom calculations or charts | **Export** | | A polished document to share or archive | **PDF Report** | | Compliance / audit evidence for one device | **PDF Report** | | A single document covering *all* devices on a site | Site Air Quality Reports | ### Report disclaimer {% hint style="warning" %} Both outputs are based on **ambient air monitoring** data from KEMPER AirWatch sensors. They are intended for facility-level monitoring and trend analysis, and are **not** a substitute for personal exposure measurement, a regulatory compliance determination, or an Occupational Exposure Limit (OEL) measurement. PM range labels are health-oriented references derived from WHO 24-hour guideline values, not statutory limits. {% endhint %} ### Related Documentation * History — The tab these features live in * Dashboard — Current measurements * Site Air Quality Reports — Site-wide, multi-device PDF * Air Quality Levels — PM range definitions and WHO reference values # CleanAirTower # settings The Settings tab displays device configuration, error status, and system information for the self-cleaning Clean Air Tower. ## Accessing Settings Navigate to the device detail page and select the "Settings" tab. ## Device Information Card ### Basic Settings | Field | Description | Editable | | ----------------- | ----------------- | -------- | | **Device Name** | Display name | Yes | | **Serial Number** | Device identifier | No | | **Location** | Physical location | Yes | ### Device Type Info | Field | Value | | --------------- | ------------------------------- | | **Device Type** | Clean Air Tower (Self-Cleaning) | | **Filter Type** | Automatic Self-Cleaning | ## Error Status Card ### Current Error Status | Field | Description | | -------------- | ------------------------------------- | | **Error Code** | Current error (FEHLERCODE) | | **Status** | "System Healthy" or error description | ### Healthy State When no errors: * Shows "0 (OK)" * "No errors detected" message * Green indicator ### Error State When an error is detected: * Error code displayed * Description shown * Red indicator * "Service Required" alert ### Error Codes | Code | Description | | ---- | ---------------------------- | | 0 | No error (OK) | | E00 | Frequency inverter error | | E03 | Compressed air not connected | | E05 | Control error | ## System Information Card ### Technical Details | Field | Description | | -------------------- | -------------------------------- | | **Software Version** | Firmware version (SOFTWARESTAND) | | **Device Type** | Clean Air Tower (Self-Cleaning) | ## Operating Information Card ### Service Tracking | Field | Unit | Description | | ----------------------- | ---- | ---------------------------- | | **Operating Hours** | h | Time device has been running | | **Hours Until Service** | h | Remaining until maintenance | ### Service Labels | Field | Label | | ------------------- | ---------------------------------- | | Operating Hours | "Time device has been running" | | Hours Until Service | "Recommended maintenance interval" | ### Service Progress * Progress bar visualization * Percentage complete * Warning at 90% * Critical at 100% ## Editing Settings ### Device Name {% stepper %} {% step %} ### Edit Device Name — Step 1 Click the edit icon. {% endstep %} {% step %} ### Edit Device Name — Step 2 Enter new name. {% endstep %} {% step %} ### Edit Device Name — Step 3 Save changes. {% endstep %} {% endstepper %} ### Location {% stepper %} {% step %} ### Edit Location — Step 1 Click the edit icon. {% endstep %} {% step %} ### Edit Location — Step 2 Enter location description. {% endstep %} {% step %} ### Edit Location — Step 3 Save changes. {% endstep %} {% endstepper %} ## Troubleshooting
Error E00 - Frequency Inverter * Check inverter connections * Verify power supply stable * May require technician
Error E03 - Compressed Air * Check air supply connected * Verify pressure adequate * Required for filter cleaning
Error E05 - Control Error * System control issue * Try restart * Contact support if persists
## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Device control * [Error Codes](file:///reference/error-codes.md) - Complete reference * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # overview The Clean Air Tower Abreinigbar (self-cleaning) is KEMPER's automatic filter cleaning air filtration tower. It features built-in filter cleaning cycles that extend filter life and reduce maintenance requirements. ## Device Identification | Property | Value | | --------------- | ----------------------------- | | **Slug** | `clean-air-tower-abreinigbar` | | **Type** | Air Filtration Tower | | **Filter Type** | Automatic Self-Cleaning | ## Purpose The Clean Air Tower (Self-Cleaning) is designed to: * Filter welding fumes and particulates * Automatically clean filters during operation * Minimize manual maintenance * Provide continuous air quality improvement ## Key Measurements ### Device Status | Measurement | Field | Description | | ----------------- | -------- | -------------------- | | **Device Status** | `ON_OFF` | Power state (On/Off) | ### Air Flow | Measurement | Field | Unit | Description | | --------------- | -------------- | ---- | ------------------------- | | **Volume Flow** | `VOLUMENSTROM` | m³/h | Air volume being filtered | ### Filter | Measurement | Field | Description | | -------------------- | ---------------------- | -------------------------- | | **Filter Cleanings** | `ANZAHL_ABREINIGUNGEN` | Total self-cleaning cycles | ### Service | Measurement | Field | Unit | Description | | ----------------------- | ----------------------------- | ---- | ------------------------- | | **Operating Hours** | `BETRIEBSSTUNDEN` | h | Total device running time | | **Hours Until Service** | `BETRIEBSSTUNDEN_BIS_WARTUNG` | h | Time until maintenance | ### System | Measurement | Field | Description | | -------------------- | --------------- | ---------------------- | | **Software Version** | `SOFTWARESTAND` | Firmware version | | **Error Code** | `FEHLERCODE` | Current error (0 = OK) | ## Status Indicators | Status | Description | | --------- | -------------------------- | | **On** | Device powered and running | | **Off** | Device powered down | | **Idle** | Online but not filtering | | **Error** | Error code detected | ## Error Codes | Code | Description | | ---- | ---------------------------- | | 0 | No error (OK) | | E00 | Frequency inverter error | | E03 | Compressed air not connected | | E05 | Control error | ## Device Tabs | Tab | Description | Documentation | | --------- | ------------------------------- | -------------------------------------------------------------------- | | Dashboard | Current status and measurements | [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) | | History | Volume flow history | [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) | | Functions | Start/Stop, data request | [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) | | License | License management | [License](file:///common/license.md) | | Settings | Error codes and system info | [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) | ## Self-Cleaning Feature * Periodically cleans filter media * Uses compressed air pulses * Requires connected air supply * Tracked via cleaning cycle counter * Extends filter operational life ## Automation Target Can be controlled by automation rules: * Triggered by AirWatch PM10 levels * Automatic start on high pollution * Automatic stop when air quality improves See [Automation Rules](file:///automation/rules.md). ## Scheduler Support Supports time-based scheduling: * Define operating hours * Configure days of week * Automatic on/off control See [Schedulers](file:///automation/schedulers.md). ## Service Tracking Service requirements monitored: * Total operating hours * Hours until maintenance * Service progress percentage * Warning at 14 days remaining ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Device control * [Error Codes](file:///reference/error-codes.md) - Error reference # history The History tab displays performance trends for the self-cleaning Clean Air Tower, showing volume flow, device status, and cleaning events over time. ## Accessing History Navigate to the device detail page and select the "History" tab. ## Performance History Chart ### Chart title "Volume Flow History (24 Hours)" ### Chart subtitle "Air volume flow and operating status over time" ### Data series | Series | Description | | ------------------- | ------------------------ | | **Volume Flow** | Air flow rate in m³/h | | **Device Status** | On/Off state (area fill) | | **Cleaning Cycles** | Filter cleaning events | ### Chart legend | Element | Description | | ---------------- | -------------------------------- | | Volume Flow line | Air volume being filtered | | Status area | Device operating state | | Cleaning markers | Automatic filter cleaning cycles | ## Time range Default: 24-hour view. Options: * 24 hours (detailed) * 7 days (hourly) * 30 days (daily) ### Data resolution | Range | Resolution | | -------- | --------------------- | | 24 hours | 5–15 minute intervals | | 7 days | Hourly aggregates | | 30 days | Daily aggregates | ## Reading the chart ### Volume Flow line * Shows filtration rate over time * Higher values = more air processed * Drops to zero when device off ### Status area * Shaded when device is on * Clear when device is off * Correlates with volume flow ### Cleaning events * Markers indicate cleaning cycles * Shows filter maintenance activity * Normal operation has periodic cleaning ## Chart interaction ### Hover details * Exact value at cursor * Timestamp * Status state ### Legend toggle * Click to show/hide series * Focus on specific metrics ## Historical patterns ### Normal operation * Consistent flow when running * Regular cleaning cycles * Expected on/off patterns ### Potential issues * Declining volume flow * Increased cleaning frequency * Irregular patterns * Zero flow when on ## Use cases ### Performance monitoring * Track filtration consistency * Identify efficiency changes * Monitor cleaning frequency ### Maintenance planning * Predict service needs * Observe filter loading * Plan interventions ### Compliance * Historical records * Operating time documentation * Performance verification ## Related documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - System info * [Service](file:///monitoring/service/overview.md) - Maintenance # functions The Functions tab provides remote control and data management capabilities for the self-cleaning Clean Air Tower. ## Accessing Functions Navigate to the device detail page and select the "Functions" tab. ## Device Control ### Available Functions | Function | Description | | ----------------------- | --------------------------------- | | **Start Tower** | Turn on the filtration system | | **Stop Tower** | Turn off the filtration system | | **Request Data Update** | Force immediate data transmission | ### Start Tower Initiates air filtration. {% stepper %} {% step %} ### Start Tower — Initiate air filtration * Click "Start Tower" button * Confirmation modal appears * Confirm to execute * Device begins filtering * Status updates to "On" {% endstep %} {% endstepper %} ### Stop Tower Stops air filtration. {% stepper %} {% step %} ### Stop Tower — Stop air filtration * Click "Stop Tower" button * Confirmation modal appears * Confirm to execute * Device stops filtering * Status updates to "Off" {% endstep %} {% endstepper %} ### Request Data Update Forces immediate data transmission. {% stepper %} {% step %} ### Request Data Update — Force immediate measurements * Click "Request Data Update" button * Device sends current measurements * Dashboard updates with fresh data {% endstep %} {% endstepper %} Use when: * Data seems stale * Verifying current status * After configuration changes ## Function Execution Modal ### Confirmation Dialog | Element | Description | | ------------- | ---------------------- | | Function name | Action to be performed | | Device name | Target device | | Warning | Confirmation prompt | | Buttons | Confirm / Cancel | ### Execution States | State | Display | | --------- | ------------------ | | Idle | Buttons available | | Executing | Loading spinner | | Success | Success message | | Error | Error with details | ## Remote Control Notes ### Timing * Commands may take seconds to reach device * Status update may be delayed * Refresh if status doesn't update ### Requirements * Device must be online * Commands fail if offline * Check connectivity first ### Safety * Ensure safe conditions * Verify area is clear * Follow safety procedures ## Automation Alternative Instead of manual control, consider: ### PM-Based Automation * AirWatch monitors PM levels * Rule triggers tower on high PM * Rule stops tower on low PM ### Time-Based Scheduling * Define operating hours * Automatic on/off * Day-of-week configuration See: * [Automation Rules](file:///automation/rules.md) * [Schedulers](file:///automation/schedulers.md) ## Error Handling ### Command Failed If a function fails, follow these steps. {% stepper %} {% step %} ### Command Failed — Troubleshooting steps * Error message displayed * Verify device online * Check network * Try again {% endstep %} {% endstepper %} ### Compressed Air Error If E03 error: * Check air supply connected * Verify adequate pressure * Device needs air for cleaning ## Permissions Requires: * Member or Admin role * Active license * Device online Viewers cannot execute functions. ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status * [Automation Rules](file:///automation/rules.md) - Automated control * [Schedulers](file:///automation/schedulers.md) - Time-based control # dashboard The dashboard provides real-time monitoring of the self-cleaning Clean Air Tower, including device status, volume flow, filter cleaning cycles, and service status. ## Dashboard Layout ### Header Section * Device name and model * Status badge (On/Off/Idle/Offline/Error) * Location (if configured) * Last seen timestamp * Subtitle: "Self-cleaning air filtration system monitoring" ### Device Status Card Displays power state: | Field | Description | | ---------- | ----------- | | **Status** | On or Off | Visual indicators: * Green icon when on * Gray icon when off * Red icon on error ### Volume Flow Card Current air filtration rate: | Field | Unit | Description | | --------------- | ---- | --------------------------- | | **Volume Flow** | m³/h | Air volume being filtered | | Label | — | "Air volume being filtered" | ### Filter Status Card Filter health and cleaning information: | Field | Description | | -------------------- | -------------------------- | | **Filter Cleanings** | Total self-cleaning events | | Label | — | {% hint style="info" %} Notes: * Shows cumulative cleaning cycles * Higher count indicates active usage * Normal operation includes regular cleaning {% endhint %} ### Service Due Card Maintenance tracking: | Field | Description | | ----------------------- | ------------------------- | | **Operating Hours** | Total device running time | | **Hours Until Service** | Time until maintenance | | **Service Progress** | Percentage toward service | Visual elements: * Progress bar showing service status * "h operated" label for total hours * "hours remaining" label for service countdown {% hint style="warning" %} Service Warnings: * Normal: Progress bar only * ≥90% to service: "Service recommended soon" message * Service overdue: Critical warning {% endhint %} ## Status Display ### Device Status Badge | Badge | Meaning | | ----------------- | -------------------------- | | **Online - On** | Connected and running | | **Online - Off** | Connected but powered down | | **Online - Idle** | Connected, standing by | | **Offline** | Not connected | | **Error** | Error code detected | ### Error Display When an error is detected: * "Service Required" alert * Error code shown * Error description ## Real-Time Updates Dashboard updates on: * Device data transmission * State changes * Error conditions ## Offline State When offline: * Last known values shown * "Offline" badge displayed * Last seen timestamp visible ## Key Metrics Summary Quick reference for operators: | Metric | Good | Warning | | --------------- | ------------------ | ----------------- | | Status | On/Off as expected | Error state | | Volume Flow | Normal range | Zero when running | | Cleaning Cycles | Incrementing | Not changing | | Service | >10% remaining | ≤10% remaining | ## Related Documentation * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Volume flow over time * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - System information # CleanAirTower SF # settings The Settings tab displays device configuration, fault status, and system information for the disposable filter Clean Air Tower. ## Accessing Settings Navigate to the device detail page and select the "Settings" tab. ## Device Information Card ### Basic Settings | Field | Description | Editable | | ----------------- | ----------------- | -------- | | **Device Name** | Display name | Yes | | **Serial Number** | Device identifier | No | | **Location** | Physical location | Yes | ### Device Type Info | Field | Value | | --------------- | ---------------------------- | | **Device Type** | Clean Air Tower (Disposable) | | **Filter Type** | Disposable cartridges | ## Fault Status Card ### Current Fault Status | Field | Description | | -------------- | ------------------------------------- | | **Fault Code** | Current fault (FAULT\_CODE) | | **Status** | "System Healthy" or fault description | ### Healthy State When no faults: * Shows "0 (OK)" * "No faults detected" message * Green indicator ### Fault State When fault detected: * Fault code displayed * Description shown * Red indicator * "Service Required" alert ### Fault Codes | Code | Description | | ---- | -------------------------- | | 0 | No fault (OK) | | E02 | Airflow control error | | E03 | Maintenance required | | E04 | Motor temperature too high | | E07 | Modbus error | | E12 | Airflow too low | ## Operating Information Card ### Service Tracking | Field | Unit | Description | | ----------------------- | ---- | --------------------------- | | **Operating Hours** | h | Total motor running time | | **Hours Until Service** | h | Remaining until maintenance | ### Service Progress * Progress bar visualization * Percentage complete * Warning at 90% * Critical at 100% ## Connection Information ### Signal Strength (LTE models) | Field | Description | | -------- | ------------------------ | | **RSSI** | Cellular signal strength | Signal quality indicators: * Strong: Good connectivity * Weak: May affect reliability * No signal: Connection issues ## Editing Settings {% stepper %} {% step %} ### Device Name * Click edit icon * Enter new name * Save changes {% endstep %} {% step %} ### Location * Click edit icon * Enter location * Save changes {% endstep %} {% endstepper %} ## Troubleshooting Use the expandables below for fault-specific guidance.
Fault E02 - Airflow Control * Check fan operation * Verify no obstructions * May need technician
Fault E03 - Maintenance Required * Service is due * Schedule maintenance * Filter may need replacement
Fault E04 - Motor Temperature High * Allow cooling * Check ventilation * Reduce boost mode usage * May indicate overload
Fault E07 - Modbus Error * Communication issue * Check connections * May need restart
Fault E12 - Airflow Too Low * Check for blockages * Filter may be clogged * Replace filter if needed
## Filter Replacement Unlike self-cleaning models: * Filters must be replaced * Monitor hours until service * Plan replacement schedule * Keep spare filters available ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Device control * [Error Codes](file:///reference/error-codes.md) - Complete reference * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # dashboard The dashboard provides comprehensive monitoring of the disposable filter Clean Air Tower, including detailed motor metrics, air flow, and operating conditions. ## Dashboard Layout ### Header Section * Device name and model * Status badge (Running/Stopped/Offline/Error) * Mode badge (BOOST if active) * Location (if configured) * Last seen timestamp * Subtitle: "Disposable filter air filtration system monitoring" ### Motor Status Card Detailed motor information: | Field | Unit | Description | | --------------------- | ---- | ------------------------- | | **Status** | - | Running or Stopped | | **Motor Power** | kW | Current power consumption | | **Motor Frequency** | Hz | Operating frequency | | **Motor Current** | A | Current draw | | **Motor Temperature** | °C | Motor temperature | ### Boost Mode Indicator When boost mode is active: * "BOOST" badge displayed * Indicates enhanced operation * Higher power consumption ### Volume Flow Card Current air filtration rate: | Field | Unit | Description | | --------------- | ---- | --------------------------- | | **Volume Flow** | m³/h | Air volume being filtered | | Label | - | "Air volume being filtered" | ### Service Due Card Maintenance tracking: | Field | Description | | ----------------------- | ------------------------- | | **Operating Hours** | Total motor running time | | **Hours Until Service** | Time until maintenance | | **Service Progress** | Percentage toward service | Visual elements and behaviors: {% hint style="info" %} * Progress bar showing service status * Warning indicator when service progress reaches 90% * "Service recommended soon" message displayed as service nears due {% endhint %} ## Status Display {% columns %} {% column %} #### Device Status Badge | Badge | Meaning | | -------------------- | ----------------------- | | **Online - Running** | Connected and filtering | | **Online - Stopped** | Connected, not running | | **Online - Idle** | Connected, standing by | | **Offline** | Not connected | | **Error** | Fault code detected | | {% endcolumn %} | | {% column %} #### Mode Badges | Badge | Meaning | | ---------------- | ------------------------ | | **Normal Mode** | Standard operation | | **BOOST** | Enhanced filtration mode | | {% endcolumn %} | | | {% endcolumns %} | |
Error Display When a fault is detected: * "Service Required" alert shown * Fault code displayed * Fault description provided
## Motor Metrics Explained ### Motor Power (kW) * Current power consumption * Higher in boost mode * Indicates load on system ### Motor Frequency (Hz) * Operating frequency * Varies with load * Standard around 50/60 Hz ### Motor Current (A) * Electrical current draw * Higher values indicate more load * Monitor for overload ### Motor Temperature (°C) * Motor internal temperature * Warning if too high (E04) * Should remain stable {% hint style="warning" %} Monitor Motor Temperature and Motor Current closely. High or rapidly rising values may indicate overload or impending fault. {% endhint %} ## Real-Time Updates Dashboard updates when: * Device transmits data * Motor state changes * Fault conditions occur ## Offline State When offline: * Last known values displayed * "Offline" badge shown * Last seen timestamp visible ## Related Documentation * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance over time * [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) - Start/Stop control * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Fault codes and info # history The History tab displays performance trends for the disposable filter Clean Air Tower, showing volume flow, motor status, and power consumption over time. ## Accessing History Navigate to the device detail page and select the "History" tab. ## Performance History Chart ### Chart Title "Performance History (24 Hours)" ### Chart Subtitle "Volume flow, motor status, and power consumption over time" ### Data Series | Series | Description | | ---------------- | --------------------------- | | **Volume Flow** | Air flow rate in m³/h | | **Motor Status** | Running/Stopped (area fill) | | **Motor Power** | Power consumption in W | ### Chart Legend | Element | Description | | ---------------- | ------------------------- | | Volume Flow line | Air volume being filtered | | Status area | Motor operating state | | Power line | Power consumption | ## Time Range Default 24-hour view with options: * 24 hours (detailed) * 7 days (hourly) * 30 days (daily) ### Data Resolution | Range | Resolution | | -------- | --------------------- | | 24 hours | 5-15 minute intervals | | 7 days | Hourly aggregates | | 30 days | Daily aggregates | ## Reading the Chart ### Volume Flow Line * Shows filtration rate over time * Higher = more air processed * Drops when motor stops ### Motor Status Area * Shaded when running * Clear when stopped * Correlates with flow ### Power Consumption * Shows energy usage * Higher during boost mode * Correlates with operation ## Chart Interaction
Hover Details * Exact values at cursor * Timestamp * All metrics shown
Legend Toggle * Click to show/hide series * Focus on specific metrics
## Historical Patterns
Normal Operation * Consistent flow when running * Stable power consumption * Expected on/off patterns
Boost Mode Periods * Higher power consumption * Potentially higher flow * Short duration typically
Potential Issues * Declining volume flow * Increasing power draw * Irregular patterns
## Use Cases ### Performance Monitoring * Track filtration efficiency * Monitor power usage * Identify anomalies ### Energy Analysis * Power consumption trends * Efficiency optimization * Cost tracking ### Maintenance Planning * Observe performance decline * Plan filter replacement * Schedule interventions ## Related Documentation
TitleTarget
Dashboard/pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3
Settings/pages/77771dd7529569caf13202321a8310a71766035b
Energy Consumptionfile:///monitoring/energy-consumption/overview.md
# overview The Clean Air Tower Einweg (disposable filter) is KEMPER's air filtration tower with replaceable filter cartridges. It provides advanced monitoring of motor performance and operating conditions. ## Device Identification | Property | Value | | --------------- | ------------------------ | | **Slug** | `clean-air-tower-einweg` | | **Type** | Air Filtration Tower | | **Filter Type** | Disposable | ## Purpose The Clean Air Tower (Disposable Filter) is designed to: * Filter welding fumes and particulates * Use replaceable filter cartridges * Provide detailed motor monitoring * Support industrial air quality improvement ## Key Measurements ### Motor Status | Measurement | Field | Unit | Description | | --------------------- | -------------------- | ------- | ------------------------- | | **Motor Running** | `MOTOR_RUNNING` | Boolean | Motor operating state | | **Motor Power** | `MOTOR_ACTUAL_POWER` | kW | Current power consumption | | **Motor Frequency** | `MOTOR_FREQUENCY` | Hz | Operating frequency | | **Motor Current** | `MOTOR_CURRENT` | A | Current draw in Amps | | **Motor Temperature** | `TEMPERATURE_MOTOR` | °C | Motor temperature | | **Boost Mode** | `BOOST_MODE_ACTIVE` | Boolean | Boost mode status | ### Air Flow | Measurement | Field | Unit | Description | | --------------- | ------------------- | ---- | ------------------------- | | **Volume Flow** | `ACTUAL_VOLUMEFLOW` | m³/h | Air volume being filtered | ### Service | Measurement | Field | Unit | Description | | ----------------------- | ------------------- | ---- | ------------------------ | | **Operating Hours** | `OPERATING_HOURS` | h | Total motor running time | | **Hours Until Service** | `MAINTENANCE_HOURS` | h | Time until maintenance | ### System | Measurement | Field | Description | | ------------------- | ------------ | ----------------------- | | **Fault Code** | `FAULT_CODE` | Current fault (0 = OK) | | **Signal Strength** | `RSSI` | Cellular signal quality | ## Status Indicators | Status | Description | | --------------- | ------------------------ | | **Running** | Motor actively operating | | **Stopped** | Motor not running | | **Normal Mode** | Standard operation | | **BOOST** | Boost mode active | | **Error** | Fault code detected | {% hint style="info" %} Boost Mode * Indicated by "BOOST" badge * Increases motor power * Higher air volume flow * Used for demanding conditions {% endhint %} ## Fault Codes
Fault code list (click to expand) | Code | Description | | ---- | -------------------------- | | 0 | No fault (OK) | | E02 | Airflow control error | | E03 | Maintenance required | | E04 | Motor temperature too high | | E07 | Modbus error | | E12 | Airflow too low |
## Device Tabs | Tab | Description | Documentation | | --------- | ----------------------------- | -------------------------------------------------------------------- | | Dashboard | Motor status and measurements | [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) | | History | Performance history | [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) | | Functions | Start/Stop control | [Functions](broken://pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678) | | License | License management | [License](file:///common/license.md) | | Settings | Fault codes and info | [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) | ## Automation Target Can be controlled by automation rules: * Triggered by AirWatch PM10 levels * Automatic start on high pollution * Automatic stop when air quality improves See [Automation Rules](file:///automation/rules.md). ## Scheduler Support Supports time-based scheduling: * Define operating hours * Configure days of week * Automatic on/off control See [Schedulers](file:///automation/schedulers.md). ## Differences from Self-Cleaning Model | Feature | Einweg (Disposable) | Abreinigbar (Self-Cleaning) | | ---------------- | ---------------------- | --------------------------- | | Filter Type | Replaceable cartridges | Self-cleaning | | Compressed Air | Not required | Required | | Cleaning Cycles | N/A | Automatic | | Motor Monitoring | Advanced | Basic | | Boost Mode | Yes | No | ## Related Documentation
TitleTarget
Dashboard — Current measurements/pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3
Functions — Device control/pages/6cafe3f2d09aa17751dc53a1b9f90f7aa5b54678
Error Codes — Error referencefile:///reference/error-codes.md
# functions The Functions tab provides remote control capabilities for the disposable filter Clean Air Tower. ## Accessing Functions Navigate to the device detail page and select the "Functions" tab. ## Device Control ### Available Functions | Function | Description | | --------------- | ------------------------------ | | **Start Tower** | Turn on the filtration system | | **Stop Tower** | Turn off the filtration system | ### Start Tower Initiates air filtration: {% stepper %} {% step %} ### Start Tower — Step 1 Click "Start Tower" button. {% endstep %} {% step %} ### Start Tower — Step 2 Confirmation modal appears. {% endstep %} {% step %} ### Start Tower — Step 3 Confirm to execute. {% endstep %} {% step %} ### Start Tower — Step 4 Motor starts. {% endstep %} {% step %} ### Start Tower — Step 5 Status updates to "Running". {% endstep %} {% endstepper %} ### Stop Tower Stops air filtration: {% stepper %} {% step %} ### Stop Tower — Step 1 Click "Stop Tower" button. {% endstep %} {% step %} ### Stop Tower — Step 2 Confirmation modal appears. {% endstep %} {% step %} ### Stop Tower — Step 3 Confirm to execute. {% endstep %} {% step %} ### Stop Tower — Step 4 Motor stops. {% endstep %} {% step %} ### Stop Tower — Step 5 Status updates to "Stopped". {% endstep %} {% endstepper %} ## Function Execution Modal ### Confirmation Dialog | Element | Description | | ------------- | ------------------- | | Function name | Action to perform | | Device name | Target device | | Warning | Confirmation prompt | | Buttons | Confirm / Cancel | ### Execution States | State | Display | | --------- | ------------------ | | Idle | Buttons available | | Executing | Loading spinner | | Success | Success message | | Error | Error with details | ## Remote Control Notes ### Timing * Commands may take seconds * Status update may be delayed * Refresh if needed ### Requirements * Device must be online * Commands fail if offline * Check connectivity first ### Safety * Ensure safe conditions * Verify area clear * Follow procedures ## Boost Mode Boost mode may be: * Controlled via physical controls * Automatically activated * Device-specific behavior Check device documentation for boost mode control. ## Automation Alternative Instead of manual control: ### PM-Based Automation * AirWatch monitors PM levels * Rule triggers tower on high PM * Rule stops tower on low PM ### Time-Based Scheduling * Define operating hours * Automatic on/off * Day-of-week config See: * [Automation Rules](file:///automation/rules.md) * [Schedulers](file:///automation/schedulers.md) ## Error Handling ### Command Failed If function fails: {% stepper %} {% step %} ### Command Failed — Step 1 Error message shown. {% endstep %} {% step %} ### Command Failed — Step 2 Verify device online. {% endstep %} {% step %} ### Command Failed — Step 3 Check network. {% endstep %} {% step %} ### Command Failed — Step 4 Try again. {% endstep %} {% endstepper %} ### Motor Temperature Error (E04) If motor overheated: * Allow cooling time * Check ventilation * Reduce boost usage ## Permissions Requires: * Member or Admin role * Active license * Device online Viewers cannot execute functions. ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status * [Automation Rules](file:///automation/rules.md) - Automated control * [Schedulers](file:///automation/schedulers.md) - Time-based control # VacuFil # settings The Settings tab displays device configuration, fault status, and operating information for the VacuFil 125 mobile extraction system. ## Accessing Settings Navigate to the device detail page and select the "Settings" tab. ## Device Information Card ### Basic Settings | Field | Description | Editable | | ----------------- | ----------------- | -------- | | **Device Name** | Display name | Yes | | **Serial Number** | Device identifier | No | | **Location** | Physical location | Yes | ### Device Type Info | Field | Value | | --------------- | ------------------------ | | **Device Type** | Mobile Extraction System | | **Filter Type** | Automatic Cleaning | ## Fault Status Card ### Current Fault Status | Field | Description | | -------------- | ------------------------------------- | | **Fault Code** | Current fault (fault\_code) | | **Status** | "System Healthy" or fault description | ### Healthy State When no faults: * Shows "0 (OK)" * "No faults detected" message * Green indicator ### Fault State When a fault is detected: * Fault code displayed * Description shown * Red indicator * "Service Required" alert ## Operating Information Card ### Service Tracking | Field | Unit | Description | | ----------------------- | ---- | ---------------------------- | | **Operating Hours** | h | Time system has been running | | **Hours Until Service** | h | Remaining until maintenance | ### Service Labels | Field | Label | | ------------------- | ------------------------------ | | Operating Hours | "Time system has been running" | | Hours Until Service | "Recommended service interval" | ### Service Progress * Progress bar visualization * Percentage complete * Warning threshold at 90% * Critical at 100% ## Editing Settings ### Device Name {% stepper %} {% step %} Click the edit icon for Device Name. {% endstep %} {% step %} Enter the new name. {% endstep %} {% step %} Save changes. {% endstep %} {% endstepper %} ### Location {% stepper %} {% step %} Click the edit icon for Location. {% endstep %} {% step %} Enter the location description. {% endstep %} {% step %} Save changes. {% endstep %} {% endstepper %} {% hint style="info" %} Location is particularly useful for mobile units that may move between areas. {% endhint %} ## Troubleshooting {% stepper %} {% step %} ### High Differential Pressure If pressure stays high: * Check filter condition * Verify cleaning system working * Filter may need replacement {% endstep %} {% step %} ### System Not Starting If unit won't start: * Check power connection * Verify no fault codes * Check safety interlocks {% endstep %} {% step %} ### Cleaning Not Effective If pressure doesn't drop after cleaning: * Filter may be saturated * Cleaning system may need service * May need filter replacement {% endstep %} {% endstepper %} ## Mobile Unit Considerations ### Location Updates For mobile units: * Update location when moved * Helps track which area served * Useful for service coordination ### Portability The VacuFil 125 is designed for: * Movement between stations * Temporary setups * Flexible deployment Track usage patterns via history to optimize positioning. ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance trends * [Error Codes](file:///reference/error-codes.md) - Complete reference * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # dashboard The dashboard provides real-time monitoring of the VacuFil 125 mobile extraction system, including system status, filter pressure, volume flow, and service status. ## Dashboard Layout ### Header Section * **Device name** and model * **Status badge** (Running / Off / Offline / Error) * **Location** (if configured) * **Last seen** timestamp * Subtitle: "Mobile extraction system monitoring" {% hint style="info" %} Header shows device identity, connectivity/status at-a-glance, and most-recent telemetry timestamp. {% endhint %} ### System Status Card Current operating state: | Field | Description | | ---------- | -------------- | | **Status** | Running or Off | Visual indicators: * Green icon when running * Gray icon when off * Red icon on fault ### Volume Flow Card Current extraction rate: | Field | Unit | Description | | --------------- | ---- | ------------------- | | **Volume Flow** | m³/h | Air being extracted | ### Filter Card Filter health and cleaning: | Field | Unit | Description | | ------------------------- | ----- | ------------------------- | | **Differential Pressure** | Pa | Pressure across filter | | **Filter Cleanings** | count | Automatic cleaning cycles | ### Differential Pressure Explained | Pressure Level | Indication | | -------------- | ----------------------------------- | | Low | Clean filter, good flow | | Medium | Normal operation | | High | Filter loaded, cleaning may trigger | | Very High | Filter needs attention | ### Service Due Card Maintenance tracking: | Field | Description | | ----------------------- | ------------------------- | | **Operating Hours** | Total system running time | | **Hours Until Service** | Time until maintenance | | **Service Progress** | Percentage toward service | Visual elements: * Progress bar for service status * Warning indicator at 90% * "Service recommended soon" message {% hint style="warning" %} Service progress shows remaining time until maintenance. The dashboard highlights when service approaches (90%) to prompt scheduling. {% endhint %} ## Status Display ### Device Status Badge | Badge | Meaning | | -------------------- | ------------------------ | | **Online - Running** | Connected and extracting | | **Online - Off** | Connected, not running | | **Online - Idle** | Connected, standing by | | **Offline** | Not connected | | **Error** | Fault code detected | ### Error Display When a fault is detected: * "Service Required" alert * Fault code shown * Fault description
Error display details * Present a visible alert labeled "Service Required" when a fault occurs. * Show the fault code and a brief fault description to aid diagnosis. * Provide links or navigation to fault-code reference in Settings or Service docs (see Related Documentation).
## Real-Time Updates Dashboard updates when: * Device transmits data * State changes * Fault conditions occur {% hint style="info" %} Real-time updates reflect live telemetry and state transitions to keep the dashboard current. {% endhint %} ## Offline State When offline: * Last known values displayed * "Offline" badge shown * Last seen timestamp visible {% hint style="danger" %} While offline, the dashboard shows the last received values; no new telemetry will be available until the device reconnects. {% endhint %} ## Key Metrics | Metric | Normal | Attention Needed | | ------------- | ----------------------- | --------------------- | | Status | Running/Off as expected | Error state | | Volume Flow | Consistent when running | Low/zero when running | | Diff Pressure | Stable range | Consistently high | | Service | >10% remaining | ≤10% remaining | ## Related Documentation * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance over time * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Fault codes and info * [Service](file:///monitoring/service/overview.md) - Maintenance tracking # overview The VacuFil 125 is KEMPER's mobile extraction system designed for localized fume extraction. It provides portable filtration with automatic cleaning and comprehensive monitoring. ## Device Identification | Property | Value | | --------------- | ------------------------ | | **Slug** | `vacufil-125` | | **Type** | Mobile Extraction System | | **Filter Type** | Automatic Cleaning | ## Purpose The VacuFil 125 is designed to: * Provide mobile, point-source extraction * Filter welding fumes at the source * Offer portability for flexible positioning * Support automatic filter cleaning ## Key Measurements ### System Status | Measurement | Field | Description | | ---------------- | -------------- | ----------------------- | | **System State** | `state_latest` | Current operating state | ### Air Flow | Measurement | Field | Unit | Description | | --------------- | ------------------- | ---- | ------------------- | | **Volume Flow** | `actual_volumeflow` | m³/h | Air extraction rate | ### Filter | Measurement | Field | Unit | Description | | ------------------------- | ------------------------------ | ----- | ---------------------- | | **Differential Pressure** | `Differential_pressure_filter` | Pa | Pressure across filter | | **Filter Cleanings** | `Anzahl_Abreinigungen` | count | Cleaning cycles | ### Service | Measurement | Field | Unit | Description | | ----------------------- | ----------------------------- | ---- | ------------------ | | **Operating Hours** | `Betriebsstunden` | h | Total running time | | **Hours Until Service** | `Betriebsstunden_bis_wartung` | h | Until maintenance | ### System | Measurement | Field | Description | | -------------- | ------------ | ---------------------- | | **Fault Code** | `fault_code` | Current fault (0 = OK) | ## Status Indicators | Status | Description | | ----------- | -------------------------- | | **Running** | System actively extracting | | **Off** | System not operating | | **Idle** | Online but not extracting | | **Error** | Fault code detected | ## Fault Codes | Code | Description | | -------- | ---------------------- | | 0 | No fault (OK) | | (Varies) | Device-specific faults |
Complete error code reference See [Error Codes](file:///reference/error-codes.md) for the complete reference.
## Device Tabs When viewing a VacuFil 125 device:
TabTargetDescription
Dashboard/pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3Current status and measurements
History/pages/5fd1e0508777182bbc170ab955ad9f90429597d8Pressure and status history
Licensefile:///common/license.mdLicense management
Settings/pages/77771dd7529569caf13202321a8310a71766035bFault codes and info
{% hint style="info" %} VacuFil 125 may have limited remote functions compared to stationary units. {% endhint %} ## Differential Pressure The filter differential pressure indicates: * Filter loading condition * Higher pressure = more resistance * Triggers automatic cleaning * Indicates when filter needs attention ## Service Tracking Service requirements monitored: * Total operating hours * Hours until maintenance * Service progress percentage * Warning thresholds ## Mobile Extraction Benefits {% columns %} {% column %} #### Portability * Move to different work stations * Position at point of fume generation * Flexible deployment {% endcolumn %} {% column %} #### Source Capture * Extract fumes at origin * More effective than hall filtration * Complement to air towers {% endcolumn %} {% column %} #### Automatic Cleaning * Self-maintaining filter * Reduced manual intervention * Extended filter life {% endcolumn %} {% endcolumns %} ## Integration VacuFil 125 can be monitored alongside: * AirWatch sensors for air quality * Stationary filtration for hall air * Site-wide energy tracking ## Related Documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current measurements * [History](broken://pages/5fd1e0508777182bbc170ab955ad9f90429597d8) - Performance trends * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Fault codes * [Service](file:///monitoring/service/overview.md) - Maintenance # history The History tab displays performance trends for the VacuFil 125 mobile extraction system, showing differential pressure, system state, and cleaning events over time. ## Accessing History Navigate to the device detail page and select the "History" tab. ## Performance History Chart ### Chart title Performance History (24 Hours) ### Chart subtitle Filter pressure and system state over time ### Data series | Series | Description | | ------------------------- | ----------------------- | | **Differential Pressure** | Filter pressure in Pa | | **System State** | Running/Off (area fill) | | **Cleaning Cycles** | Filter cleaning events | ### Chart legend | Element | Description | | ---------------- | ---------------------------- | | Pressure line | Filter differential pressure | | State area | System operating state | | Cleaning markers | Automatic cleaning events | ## Time range Default 24-hour view with options: * 24 hours (detailed) * 7 days (hourly) * 30 days (daily) ### Data resolution | Range | Resolution | | -------- | --------------------- | | 24 hours | 5–15 minute intervals | | 7 days | Hourly aggregates | | 30 days | Daily aggregates | ## Reading the chart ### Differential pressure line The pressure trend reveals: * Rising trend: Filter loading * Sudden drop: Cleaning cycle occurred * Sawtooth pattern: Normal with periodic cleaning * Consistently high: Filter may need attention ### System state area * Shaded when running * Clear when off * Correlates with usage ### Cleaning events * Markers show cleaning cycles * Normal operation includes periodic cleaning * Frequency indicates filter utilization ## Chart interaction ### Hover details * Exact pressure value * Timestamp * State information ### Legend toggle * Show/hide series * Focus on specific data ## Historical patterns ### Normal operation * Pressure rises during use * Cleaning brings pressure down * Regular sawtooth pattern ### Heavy use * More frequent cleaning cycles * Faster pressure rise * Higher average pressure ### Potential issues * Pressure not dropping after cleaning * Very high sustained pressure * Irregular patterns ## Use cases ### Filter monitoring * Track filter condition * Predict replacement needs * Optimize cleaning ### Usage analysis * Operating time patterns * Identify peak usage * Plan maintenance windows ### Troubleshooting * Correlate issues with pressure * Identify anomalies * Document performance ## Related documentation * [Dashboard](broken://pages/415d6ce9d130a8b6702073901ddc80c6b9901ab3) - Current status * [Settings](broken://pages/77771dd7529569caf13202321a8310a71766035b) - Fault codes * [Service](file:///monitoring/service/overview.md) - Maintenance # KEMPER Connect Bridge KEMPER Connect and the KEMPER Connect Bridge Asset Guide. 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) {% 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) {% 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 | # Air Quality The dashboard aggregates particulate matter data from all connected air quality devices to provide a real-time status indicator and detailed historical performance rankings. ## Overview The Air Quality Dashboard provides a consolidated site-level overview of air quality across all AirWatch and compatible air quality devices within a workspace. It calculates aggregated air quality indicators based on all available devices and displays the overall site status using averaged particulate matter values (PM2.5 and PM10). ### Site Air Quality
At the top of the dashboard, a traffic light visualization summarizes the overall air quality status of the site. The status is calculated using the average PM2.5 and PM10 values across all active air quality devices in the workspace. This provides an immediate indication of whether air conditions are within acceptable ranges or require attention. ### KPIs
The dashboard includes key performance indicators based on aggregated sensor data: * Average PM2.5 * Average PM10 * 4-hour rolling average (PM values)
In addition, the dashboard highlights: * Top 5 devices with the highest pollution levels * Top 5 devices with the lowest pollution levels (best air quality) This enables quick identification of critical zones as well as best-performing areas within the facility. ## Devices
The **Devices** tab provides a detailed table view of all air quality devices within the workspace. For each device, individual measurement values and calculated indicators are displayed to allow device-level analysis and comparison. ## Historical Analysis
The **Historical** tab provides time-based evaluation of air quality data. Users can: * View trends by day, week, or month * Compare selected time periods (e.g., current vs. previous period) * Filter data by defined working hours to exclude non-operational periods * Review percentage-based changes between time ranges * Export data as Excel or CSV files for reporting and documentation This enables structured analysis of long-term air quality development and validation of implemented improvement measures. ## Report Generation
The **Report** tab allows users to generate a structured PDF air quality report directly from the dashboard. Users can configure: * The reporting period (e.g., day-based or week-based ranges) * Custom time intervals * Output format settings The system generates a PDF document summarizing site-level air quality metrics, trends, and key indicators for the selected period. This functionality is particularly useful for: * Demonstrating compliance or improvements * Validating the effectiveness of air quality optimization measures * Providing structured documentation for customers, partners, or internal review # Report Air Quality Report Generation ## Air Quality Reports The Report tab generates a print-ready PDF that summarises air quality across all licensed AirWatch devices on a site. Reports are designed for compliance documentation, stakeholder communication, and internal reviews. Every PDF is fully self-explanatory — even when read out of context — thanks to a built-in methodology section, a table of contents, and an executive summary on the cover page. ### Accessing the Report 1. Open the site you want to report on (sidebar item **Sites** → select a site). 2. In the site sidebar, click **Air Quality**. 3. Open the **Report** tab in the tab bar (next to *Overview*, *Historical*, and *Devices*). URL pattern: `/sites/[id]/air-quality` → tab "Report". The Report tab shows a configuration card on the left/top and, after the first preview, a live preview of the generated PDF below it.
### Report Configuration All settings are applied when you click **Generate Preview**. Changing a setting after generating does not auto-refresh the preview — re-click **Generate Preview** to apply.
#### Configuration overview | Setting | Type | Default | Effect | | ---------------------------- | ------------------------ | ------- | ---------------------------------------------- | | Time Period | Day / Week toggle | Day | Reporting window and chart resolution | | Period navigation | Prev / Next arrows | Current | Step through past periods | | Chart Size | Compact / Normal / Large | Normal | Pixel height of the Historical chart | | Customer / Company | Free text | empty | Printed on the cover page | | Project / Location | Free text | empty | Printed on the cover page | | Additional Notes | Free text | empty | Printed on the cover page | | Compare with Previous Period | Toggle | off | Adds previous-period overlays and trend deltas | | Working Hours Filter | Toggle (+ sub-settings) | off | Restricts statistics to working hours only | | All Devices Table | Toggle | off | Adds a table of every licensed device | | Per-Device Pages | Toggle | off | Adds one detail page per licensed device | #### Time Period Select the reporting window with the **Day / Week** toggle, then use the prev/next arrows to step through history. The "next" arrow is disabled on the current period. | Time Period | Window | Chart resolution | Comparison range (when enabled) | | ----------- | -------------------------- | ----------------- | ------------------------------- | | Day | Calendar day (00:00–24:00) | 15-minute buckets | Previous calendar day | | Week | Calendar week (Mon–Sun) | 1-hour buckets | Previous calendar week | The current period label (e.g. *"May 5, 2026"* or *"Apr 28 – May 4, 2026"*) is shown between the navigation arrows. #### Chart Size Controls the pixel height of the **Historical Air Quality** chart on its dedicated page. The chart now lives on its own A4 landscape page, so all three options use the page generously. | Option | Chart height | When to use | | ------- | -----------: | ---------------------------------------------------- | | Compact | 420 px | Leaves more whitespace below the chart | | Normal | 520 px | Default, balanced | | Large | 600 px | Maximum vertical detail; fills nearly the whole page | This setting only affects the site-wide Historical chart. Per-device pages use a fixed compact chart height because they share the page with a header row and KPI cards. #### Report Information (custom metadata) Three optional free-text fields printed on the cover page: * **Customer / Company** — e.g. `Acme Corporation` * **Project / Location** — e.g. `Production Hall B` * **Additional Notes** — e.g. `Monthly air quality review` All three are optional. Empty fields are simply omitted from the cover page. #### Report Options **Compare with Previous Period** When enabled: * Fetches the previous period's data (yesterday for *Day*, last calendar week for *Week*). * Overlays a dashed previous-period line on the Historical chart for both PM2.5 and PM10. * Adds a **Period Comparison** block to the General Overview page (current vs previous, with trend arrows). * Adds a compact trend summary to each per-device page (when *Per-Device Pages* is also enabled). * Adds a *Period Comparison* line to the Statistics section. Trend classification uses a 5% deadband: changes smaller than ±5% are reported as *Stable*. **Working Hours Filter** When enabled, all statistics, time distributions, exceedance counts, and trends are computed using only data points that fall within the configured working hours. The Historical chart shows vertical boundary markers at the start/end times so the filtered window is visible. Sub-settings appear when the toggle is on: | Sub-setting | Default | Effect | | ---------------- | ------- | --------------------------------- | | Start Time | 06:00 | Beginning of the working window | | End Time | 16:00 | End of the working window | | Exclude weekends | on | Skip Saturday and Sunday entirely | The current Working Hours configuration is also printed on the cover page so the reader knows the reporting scope. **All Devices Table**
Adds a sortable, full-width table listing every licensed AirWatch device on the site, sorted by current PM10 (worst first). Each row shows: * Device name and serial number (claim serial preferred, falls back to device serial) * Online / Offline status pill * Current PM2.5 and PM10 (with quality-level badges) * 4-hour rolling averages for PM2.5 and PM10 Useful as a quick "leader board" for identifying the dustiest devices. **Per-Device Pages** Adds one strict A4 landscape page per licensed device, sorted alphabetically by device name. A title divider page is inserted before the device pages, listing all devices that follow as a contents-style index. Each per-device page contains: * **Header strip** — device name, serial number, online/offline status, location (if known), last-heard timestamp. * **4 compact KPI cards** — Current PM2.5, Current PM10, 4-hour Avg PM2.5, 4-hour Avg PM10. * **Historical chart** — the device's individual time series with the device name in the chart title (`Historical Air Quality — {device}`). When *Compare with Previous Period* is enabled, the previous period is overlaid as dashed lines. * **Inline trend summary** (only when comparison is enabled) — compact one-row PM2.5 / PM10 deltas with arrows. * **No-data fallback** — if a device has no data for the period, a "No data available for this period" placeholder replaces the chart. Header and KPI cards still render. The page is hard-clipped to A4 landscape height in print, so each device gets exactly one page regardless of dataset size. > **Performance note:** Per-Device Pages share the network fetches with the site-wide aggregate — enabling the toggle adds **no extra API calls**. Generation time is unchanged. ### Generating the Report
#### Workflow 1. Pick the **Time Period** and navigate to the desired window. 2. Optionally fill in **Customer**, **Project**, and **Notes**. 3. Toggle the **Report Options** you need. 4. Click **Generate Preview** — data is fetched and the live preview renders below the configuration card. 5. Click **Print / Save PDF** — opens the browser print dialog. 6. In the print dialog, choose **Save as PDF** as the destination (or print directly). #### Print dialog tips The PDF is hardcoded to **A4 landscape** with 10 mm margins. For best results in the print dialog: * Enable **Background graphics** so coloured KPI badges, status pills, and chart zones print correctly. * Set margins to **Default** or **None** (margins are already controlled by the report's CSS). * If a section gets clipped, lower the **Chart Size** to *Compact* and re-generate. #### Re-generating Configuration changes do not auto-refresh the preview. After changing any setting, click **Generate Preview** again. This is intentional — re-fetching can take several seconds when *Per-Device Pages* is enabled with many devices. ### Report Structure The PDF has a deterministic page layout. Pages 1, 2, 3, the Historical page, the Statistics & Distribution page, and the Methodology page are always present. The remaining pages depend on toggles. #### Page-by-page overview | Page | Section | Always present | | ---- | ----------------------------------------------------------- | :---------------: | | 1 | Header + Executive Summary | yes | | 2 | Table of Contents | yes | | 3 | General Overview (Site Status + optional Comparison + KPIs) | yes | | 4 | Historical Air Quality | yes | | 5 | Statistics & Distribution | yes | | 6 | All Devices Table | only if toggle on | | 7 | Per-Device section divider | only if toggle on | | 8…N | Per-Device pages (one per device, alphabetical) | only if toggle on | | Last | Methodology | yes | #### Page 1 — Header + Executive Summary The cover page contains: * Report title (`Air Quality Report`) and site name * Reporting period and generation timestamp * **Customer**, **Project**, and **Notes** (if filled in) * Working Hours configuration (if filter is enabled) * Comparison range (if comparison is enabled) * Total / online device counts * An **Executive Summary** block — narrative top-line trends, highlights, and percentage of time spent in healthy ranges #### Page 2 — Table of Contents A dynamically-built index of the sections that follow, with page numbers. Entries are added or removed depending on which toggles are active. Page numbers are calculated deterministically from the active sections. Example with all toggles enabled and 8 devices: ``` 01. General Overview … p. 3 02. Historical Air Quality … p. 4 03. Statistics & Distribution … p. 5 04. All Devices Table … p. 6 05. Per-Device Details … p. 7 (divider page; devices on pp. 8–15) 06. Methodology … p. 16 ``` #### Page 3 — General Overview A consolidated summary page combining: * **Site Air Quality Status** — overall status indicator, current PM2.5 / PM10 averages with quality labels, and 4-hour rolling averages. * **Period Comparison** *(only when comparison is enabled)* — current vs previous averages and min / max / median for both PM2.5 and PM10, with trend arrows. * **Key Performance Indicators** — 4×2 grid: Avg PM2.5, Avg PM10, 4h Avg PM2.5, 4h Avg PM10, Peak PM2.5, Peak PM10, Best PM10, Devices Online. #### Page 4 — Historical Air Quality A full-page time-series chart of the **site-wide aggregated** average per timestamp. Title and subtitle make the aggregation explicit, e.g. *"Aggregated average across 8 licensed AirWatch devices (7 online) — values represent the workspace mean per timestamp."* Chart features: * Background bands tinted by PM10 quality range (green → purple) * PM2.5 (orange) and PM10 (blue) lines * Dashed reference lines at the period averages * Optional dashed previous-period overlay (when comparison is enabled) * Working-hours boundary markers (when the filter is enabled) * A range legend at the bottom explaining the coloured bands #### Page 5 — Statistics & Distribution Combines four detailed analytical blocks: 1. **Period Statistics** — average, min, max, median for PM2.5 and PM10. With comparison enabled, previous-period values and trend deltas are shown alongside. 2. **Time Distribution** — percentage of time spent in each air-quality range (Very good / Elevated / High / Very high / Extreme), separately for PM2.5 and PM10. 3. **Exceedance Summary** — minutes and number of events above each elevated range threshold. 4. **Peak Events** — the five highest PM2.5 and PM10 readings of the period (deduplicated within 30 minutes of each other) with their timestamps. All four blocks use the working-hours-filtered dataset when the filter is on. #### Page 6 — All Devices Table *(optional)* See the configuration section above. Devices are ranked by current PM10, worst first. #### Page 7 — Per-Device Section Divider *(optional)* A title page that introduces the per-device pages. Contains: * A bordered headline (`Per-Device Details`) * A description with the device count * A 3-column device index listing all devices that follow, alphabetically numbered (`01.`, `02.`, …) #### Pages 8…N — Per-Device Pages *(optional)* One strict A4 landscape page per device, sorted alphabetically by device name. See the *Per-Device Pages* configuration section for the per-page layout. #### Last Page — Methodology A short, always-included summary describing: * How averages are calculated (arithmetic mean across licensed devices) * The difference between Average and Peak / Best values * How 4-hour rolling averages are derived * How the filtered time bucket affects every statistic This makes the report self-explanatory when shared outside the application context — auditors and external stakeholders can interpret the values without prior knowledge of the platform. ### Print Format | Property | Value | | ---------------------- | ------------------------------------------------- | | Page size | A4 landscape (297 × 210 mm) | | Margins | 10 mm on all sides (set via `@page`) | | Effective content area | 277 × 190 mm | | Page-break behaviour | Every major section starts on a fresh page | | Per-device pages | Strict 190 mm height, content overflow is clipped | The page-break behaviour is enforced via CSS, so the PDF page count is deterministic and the table of contents page numbers always match the actual layout. ### Use Cases #### Compliance documentation * Regulatory reporting on workplace air quality * Audit evidence for HSE inspections * Periodic documentation for internal compliance teams #### Stakeholder communication * Management reports with executive summary on the cover * Safety-committee updates with trend visualisation * Customer-facing documentation with custom branding fields #### Internal analysis * Per-device performance reviews using the Per-Device Pages * Period-over-period comparisons for shift / process changes * Working-hours-only analysis for occupational exposure context ### Report Disclaimer Reports are based on **ambient air monitoring** data from KEMPER AirWatch sensors. They are intended for facility-level monitoring and trend analysis. They are **not**: * A substitute for personal exposure measurement * A regulatory compliance determination * A replacement for Occupational Exposure Limit (OEL) measurements The PM range labels (Very good, Elevated, High, Very high, Extreme) are health-oriented references derived from WHO 24-hour guideline values, not statutory limits. ### Related Documentation * Overview — Live monitoring dashboard * Historical — Trend analysis tab * Devices — Per-device breakdown tab * Air Quality Levels — PM range definitions and WHO reference values # Service The Service Dashboard provides a centralized overview of the maintenance status of all service-enabled devices within your workspace. ## Overview The Service Dashboard aggregates operating data such as **Operating Hours** and **Hours Until Service** to determine the current maintenance state of each asset. This enables proactive service planning and immediate identification of critical conditions. ### Accessing the Dashboard Access the service dashboard by clicking on the service icon in the sidebar. See the screenshot below as an example.
## Core Metrics The dashboard is based on two primary service indicators: * **Operating Hours** – Total accumulated runtime of a device * **Hours Until Service** – Remaining operating hours until the next scheduled service interval These values are used to automatically calculate and display the service status of each device. ## Service Status Overview
Upon opening the dashboard, users immediately see a visual summary of the overall service condition across all applicable devices. The service state is represented using a traffic light system: * **Green – OK**\ Devices operating within normal service intervals. * **Yellow – Service Required Soon**\ Devices approaching their service threshold (e.g., within the next 30 days or defined service window). * **Red – Service Overdue**\ Devices that have exceeded their defined service interval and require immediate attention. The dashboard displays the total number of devices in each category, providing an instant overview of current maintenance needs across the site. ## KPIs The dashboard includes aggregated statistics such as: * Total number of service-enabled devices * Number of devices in OK state * Number of devices requiring service soon * Number of devices with overdue service This enables fast operational assessment without the need to inspect each device individually. ## Devices
The **Devices** tab provides a detailed table view of all devices with service tracking enabled. This section allows users to review individual runtime values, remaining hours until service, and the calculated service status per device. ## Use Case The Service Dashboard is designed for preventive and condition-based maintenance management. By monitoring runtime-based service intervals, operators can identify maintenance requirements early, reduce unexpected downtime, and ensure compliance with internal service schedules. # Noise Level ## Note This dashboard is a new feature within the portal and is already available for productive use. However, the respective use case (e.g., energy consumption or noise monitoring) requires specific, dedicated devices. The functionality does not derive data from existing sensors such as air quality or other already integrated devices. {% hint style="info" %} Suitable hardware solutions are currently not listed in the standard device catalog. **Please contact our team for individual consultation, device recommendations, or access to a demo setup.** {% endhint %} ## Overview
The Noise Level Dashboard is a site-wide monitoring tool that provides an aggregated view of sound pressure levels across all configured noise measurement devices within a workspace or site. It enables users to monitor overall acoustic exposure and track noise levels across multiple areas or industrial assets. ### KPIs The dashboard provides a range of noise-related metrics and key performance indicators (KPIs). The most relevant KPIs are outlined below. #### **Daily Noise Metrics** The daily metrics display: * Current or daily average noise level * The device reporting the highest noise level * The device reporting the lowest noise level * The total number of active noise measurement devices These metrics provide an immediate operational overview of current acoustic conditions on site. #### **Noise Distribution Statistics** The Noise Statistics section visualizes the proportional noise contribution per device or measurement point. For each installed measurement device, the dashboard displays its relative contribution to overall site noise levels. This helps identify high-exposure areas and evaluate distribution patterns across the facility. ## Concept The Noise Level Dashboard follows the same structural concept as other dashboards within the KEMPER Connect application. Upon opening the dashboard, aggregated noise data from all configured measurement devices in the workspace or site is displayed. Detailed KPI statistics and device-level breakdowns are then provided to support monitoring and analysis. ## Use Case The dashboard is designed for monitoring industrial noise levels and acoustic exposure across facilities. By integrating compatible noise measurement devices into the KEMPER Connect platform, users can generate a consolidated overview of sound levels across all relevant areas within their workspace. ## Devices In addition to KPIs and noise statistics, the **Devices** tab provides a structured overview of all detected and configured noise measurement devices within the site. This section displays a table containing device-level information for monitoring and management purposes. ## Historical Analysis The **Historical** tab provides time-based analysis of noise trends. Users can: * View noise levels by day, week, or month * Compare current periods with previous periods (e.g., day-over-day, week-over-week, month-over-month) * Analyze percentage changes between selected time ranges * Review average values for selected periods All historical data can be exported as Excel or CSV files for reporting, compliance documentation, or further evaluation. Both absolute values and percentage-based comparisons are available to assess long-term exposure patterns and identify potential compliance or safety risks. # Energy Consumption ## Note This dashboard is a new feature within the portal and is already available for productive use. However, the respective use case (e.g., energy consumption or noise monitoring) requires specific, dedicated devices. The functionality does not derive data from existing sensors such as air quality or other already integrated devices. {% hint style="info" %} Suitable hardware solutions are currently not listed in the standard device catalog. **Please contact our team for individual consultation, device recommendations, or access to a demo setup.** {% endhint %} ## Overview The Energy Consumption Dashboard is a site-wide monitoring tool that provides an aggregated view of total energy consumption across all configured energy meters within a workspace or site. It enables users to monitor overall energy usage and track consumption patterns across multiple assets and locations.
### KPIs The dashboard provides a range of energy-related metrics and key performance indicators (KPIs). The most relevant KPIs are outlined below. #### Daily Usage Metrics The daily metrics display: * Total energy consumption for the current day * The highest consuming device * The lowest consuming device * The total number of active energy meters These metrics provide an immediate operational overview of current site performance. #### Energy Stats The Energy Statistics section visualizes the proportional energy share per device. For each installed meter, the dashboard displays its contribution to overall site consumption. This makes it easy to identify major consumers and evaluate distribution patterns across assets. ## Concept The Energy Consumption Dashboard follows the same structural concept as other dashboards within the KEMPER Connect application. Upon opening the dashboard, aggregated energy consumption data from all configured energy meters in the workspace or site is displayed. Detailed KPI statistics and device-level breakdowns are then provided to support analysis and monitoring. ### What to use it for? The dashboard is designed for monitoring the energy consumption of industrial assets. By integrating compatible energy meters into the KEMPER Connect platform, users can generate a consolidated overview of energy usage across all relevant equipment within their workspace. ## Devices
In addition to KPIs and consumption statistics, the **Devices** tab provides a structured overview of all detected and configured energy meters within the site. This section displays a table containing device-level information for monitoring and management purposes. ## Historical Charts
The **Historical** tab provides time-based analysis of energy consumption trends. Users can: * View consumption data by day, week, or month * Compare current periods with previous periods (e.g., day-over-day, week-over-week, month-over-month) * Analyze percentage changes between selected time ranges * Review average consumption values for selected periods All historical data can be exported as Excel or CSV files for reporting, compliance documentation, or further analysis. Both absolute values and percentage-based comparisons are available to evaluate performance changes and measure the impact of energy optimization efforts. # Notifications Email notifications alert designated recipients when air quality thresholds are exceeded, enabling proactive response to elevated PM levels. ## Accessing Notifications Navigate to `/sites/[id]/notifications` or click "Notifications" in the site sidebar. ## Concept Notification rules define: * **Trigger device**: AirWatch sensor to monitor * **PM10 threshold**: Level that triggers alert * **Recipients**: Email addresses to notify * **Hysteresis**: Prevents notification spam ## Notification Components ### Trigger Device AirWatch sensor that triggers notifications: * AirWatch 3.0 * AirWatch LTE Europe * AirWatch LTE America ### PM10 Threshold The PM10 value (in µg/m³) that triggers notification: * Alert sent when threshold exceeded * Configurable per rule ### Recipients Email addresses to receive alerts: * Multiple recipients supported * Valid email format required * Both internal and external addresses ### Hysteresis Time delay before re-triggering: * Prevents repeated notifications * Configurable duration * Value must drop and rise again to re-trigger ## Creating Notifications ### Add Notification Modal {% stepper %} {% step %} ### Select Create Notification Rule Click "Create Notification Rule" to open the modal. {% endstep %} {% step %} ### Choose Trigger Device Select the trigger AirWatch device for the rule. {% endstep %} {% step %} ### Set Threshold Set the PM10 threshold that will trigger the alert. {% endstep %} {% step %} ### Add Recipients Add recipient email addresses (see Recipient Management). {% endstep %} {% step %} ### Configure Hysteresis (optional) Set hysteresis duration to prevent repeated alerts. {% endstep %} {% step %} ### Save Notification Save the notification rule to activate it. {% endstep %} {% endstepper %} ### Recipient Management Add recipients: * Enter email address * Click "Add" * Repeat for multiple Remove recipients: * Click remove button next to email * Confirm removal ## Notification Cards Each notification displays as a collapsible card. ### Card Header * Notification name * Trigger device name * Enable/Disable toggle * Edit/Delete buttons ### Card Content * Trigger device with current PM10 * Threshold value * Recipient list * Notification status ## Managing Notifications ### Enable/Disable Toggle notifications on/off: * Disabled rules don't send emails * Useful for maintenance periods * Quick pause capability ### Edit Notification Modify existing notifications: * Change threshold * Update recipients * Adjust hysteresis ### Delete Notification Remove notifications: * Confirmation required * Cannot be undone ## Email Content ### Alert Email Contains * Site name * Trigger device name and location * Current PM10 value * Threshold that was exceeded * Timestamp * Link to dashboard (if configured) ### Language Email templates available in: * English * German Based on system configuration. ## Notification Behavior ### Trigger Condition {% stepper %} {% step %} ### Condition: Threshold Crossing PM10 exceeds the configured threshold. {% endstep %} {% step %} ### Condition: Hysteresis Hysteresis period has passed (if applicable). {% endstep %} {% step %} ### Condition: Rule Enabled The notification rule is enabled. {% endstep %} {% endstepper %} ### Hysteresis Logic Prevents spam. Steps for how hysteresis works: {% stepper %} {% step %} ### Initial Alert Alert sent when PM10 crosses the threshold. {% endstep %} {% step %} ### Start Timer A hysteresis timer starts after the alert. {% endstep %} {% step %} ### Suppress Alerts No new alerts sent during the timer period. {% endstep %} {% step %} ### Require Reset PM10 must drop below the threshold to reset state. {% endstep %} {% step %} ### Restart Timer on Drop Timer resets when the value drops below the threshold. {% endstep %} {% step %} ### Next Alert A new alert is sent only on the next threshold crossing after reset. {% endstep %} {% endstepper %} ### Example Threshold: 100 µg/m³, Hysteresis: 30 minutes | Time | PM10 | Action | | ----- | ---- | -------------------------- | | 09:00 | 110 | Alert sent | | 09:05 | 120 | No alert (hysteresis) | | 09:15 | 90 | No alert (below threshold) | | 09:20 | 105 | Alert sent (new crossing) | ## Live Status Notification cards show: * Current PM10 from trigger * Whether threshold exceeded * Active alert state ## Best Practices ### Threshold Selection * Set above normal fluctuations * Consider background levels * Test before production use ### Recipient Selection * Include relevant personnel * Consider shift supervisors * Avoid notification fatigue ### Hysteresis Settings * Too short = notification spam * Too long = missed alerts * 15-30 minutes typical ## Empty State If no notifications exist: * Message indicating no rules * "Create Rule" button ## Permissions Creating/editing notifications requires: * Member or Admin role * Access to trigger devices * Active licenses ## Related Documentation * [Automation Rules](broken://pages/cdce5e0fc1d3faed280c813b56d173ecb9dcaa33) - Automatic device control * [Schedulers](broken://pages/6a965e1dbdaf8fbac4d277148e35412c62efbcad) - Time-based control * [Air Quality](file:///6726661/monitoring/air-quality/overview.md) - PM monitoring # Schedulers Schedulers enable time-based automatic control of filtration devices, turning them on and off at specified times. ## Accessing Schedulers Navigate to `/sites/[id]/schedulers` or click "Schedulers" in the site sidebar. ## Concept Schedules define: * **Target devices**: Filtration devices to control * **Start time**: When to turn on * **Stop time**: When to turn off * **Days**: Which days of the week ## Schedule Components ### Target Devices Filtration devices that can be scheduled: * AirDome * Clean Air Tower (Self-Cleaning) * Clean Air Tower (Disposable) ### Time Settings | Setting | Description | | ---------- | --------------------------- | | Start Time | Hour and minute to turn on | | Stop Time | Hour and minute to turn off | | Timezone | Site timezone for schedule | ### Days of Week Select which days the schedule runs: * Monday through Sunday * Weekdays only * Weekends only * Custom selection ## Creating Schedules ### Add Schedule Modal {% stepper %} {% step %} ### Click "Add Schedule" Open the modal to create a new schedule. {% endstep %} {% step %} ### Enter schedule name Provide a clear, descriptive name. {% endstep %} {% step %} ### Select target device(s) Choose one or more filtration devices to control. {% endstep %} {% step %} ### Set start time Pick the hour and minute when the device should turn on. {% endstep %} {% step %} ### Set stop time Pick the hour and minute when the device should turn off. {% endstep %} {% step %} ### Select days of week Choose which days the schedule runs (individual days, weekdays, weekends, or a custom selection). {% endstep %} {% step %} ### Save schedule Persist the schedule so it becomes active (if enabled). {% endstep %} {% endstepper %} ### Time Format * 24-hour format recommended * Timezone-aware scheduling * Handles overnight schedules ## Schedule Cards Each schedule displays as a collapsible card: ### Card Header * Schedule name * Time range (e.g., "08:00 - 18:00") * Enable/Disable toggle * Edit/Delete buttons ### Card Content * Target device(s) list * Days of week indicators * Next scheduled action * Schedule status ## Managing Schedules ### Enable/Disable Toggle schedules on/off: * Disabled schedules don't run * Preserve for later use * Quick pause capability ### Edit Schedule Modify existing schedules: * Change times * Adjust days * Add/remove devices ### Delete Schedule Remove schedules: * Confirmation required * Cannot be undone ## Schedule Execution ### Start Action {% stepper %} {% step %} ### System checks schedule At the start time on scheduled days, the system verifies the schedule is valid and active. {% endstep %} {% step %} ### Sends start command to devices The system issues the start command to the target devices. {% endstep %} {% step %} ### Devices begin filtering Target devices commence filtering operations. {% endstep %} {% endstepper %} ### Stop Action {% stepper %} {% step %} ### System checks schedule At the stop time on scheduled days, the system verifies the schedule is active. {% endstep %} {% step %} ### Sends stop command to devices The system issues the stop command to the target devices. {% endstep %} {% step %} ### Devices stop filtering Target devices cease filtering operations. {% endstep %} {% endstepper %} ### Crontab Conversion Internally, schedules convert to cron format: * Precise timing * Reliable execution * Timezone handling ## Overnight Schedules For schedules crossing midnight: * Set stop time earlier than start time * System handles day boundary * Works correctly across days Example: Start 22:00, Stop 06:00 = Night shift ## Multiple Schedules Devices can have multiple schedules: * Different times for different days * Overlapping schedules combine * Consider interactions carefully ## Use Cases ### Production Hours | Day | Time | Purpose | | ------- | ----------- | ------------- | | Mon-Fri | 07:00-18:00 | Day shift | | Mon-Fri | 18:00-02:00 | Evening shift | ### Energy Savings * Run only during production * Automatic shutdown * Reduce off-hours consumption ### Air Quality Prep * Start before work begins * Pre-filter the air * Stop after hours ## Best Practices ### Timing * Allow warm-up time * Consider start-up sequences * Account for building access ### Overlap with Automation * Schedulers set baseline operation * Automation can override * Consider combined behavior ### Maintenance Windows * Disable before service * Re-enable after * Use disable toggle ## Empty State If no schedules exist: * Message indicating no schedules * "Add Schedule" button ## Permissions Creating/editing schedules requires: * Member or Admin role * Access to target devices * Active licenses on devices ## Related Documentation * [Automation Rules](broken://pages/cdce5e0fc1d3faed280c813b56d173ecb9dcaa33) - PM-based control * [Notifications](broken://pages/051e9b028bbd84763eebe2cf8123e6858cc5331c) - Email alerts * [AirDome Functions](file:///6726661/asset-types/airdome/functions.md) - Manual control # Rules Automation rules enable automatic control of filtration devices based on air quality measurements from AirWatch sensors. ## Accessing Automation Navigate to `/sites/[id]/automation` or click "Automation" in the site sidebar. ## Concept Automation rules connect: * **Trigger device**: AirWatch sensor measuring PM10 * **Target devices**: Filtration devices to control * **Threshold**: PM10 level that activates the rule When PM10 exceeds the threshold, target devices start. When PM10 falls below, they stop. ## Rule Components ### Trigger Device AirWatch sensors that can be triggers: * AirWatch 3.0 * AirWatch LTE Europe * AirWatch LTE America ### Target Devices Filtration devices that can be controlled: * AirDome * Clean Air Tower (Self-Cleaning) * Clean Air Tower (Disposable) ### PM10 Threshold The PM10 value (in µg/m³) that triggers action: * Below threshold: Target devices stop * Above threshold: Target devices start Typical suggested thresholds: * Conservative: 50 µg/m³ * Standard: 100 µg/m³ * High activity: 150 µg/m³ #### PM10 Threshold Helper A visual helper shows: * Current PM10 level * Historical averages * Suggested threshold range * WHO guideline reference ## Creating Rules ### Add Rule Modal {% stepper %} {% step %} ### Select Create Click "Create Automation Rule". {% endstep %} {% step %} ### Choose Trigger Select trigger AirWatch device. {% endstep %} {% step %} ### Choose Targets Select target filtration device(s). {% endstep %} {% step %} ### Set Threshold Set PM10 threshold. {% endstep %} {% step %} ### Save Save rule. {% endstep %} {% endstepper %} ### Threshold Selection The system suggests thresholds based on: * Historical PM10 data * Average readings * Recommended ranges Typical thresholds: * Conservative: 50 µg/m³ * Standard: 100 µg/m³ * High activity: 150 µg/m³ ## Rule Cards Each rule displays as a collapsible card. ### Card Header * Rule name (auto-generated or custom) * Trigger device name * Enable/Disable toggle * Edit/Delete buttons ### Card Content * Trigger device with current PM10 value * Target device(s) list * Threshold value * Rule status ## Managing Rules ### Enable/Disable Toggle rules on/off: * Disabled rules don't trigger * Keep rules for later use * Quickly pause automation ### Edit Rule Modify existing rules: * Change threshold * Add/remove targets * Update name ### Delete Rule Remove rules: * Confirmation required * Cannot be undone ## Rule Behavior ### Start Rule {% stepper %} {% step %} ### Condition AirWatch reports PM10 > threshold. {% endstep %} {% step %} ### Detection System detects condition. {% endstep %} {% step %} ### Command Start command sent to targets. {% endstep %} {% step %} ### Action Target devices begin filtering. {% endstep %} {% endstepper %} ### Stop Rule {% stepper %} {% step %} ### Condition AirWatch reports PM10 < threshold. {% endstep %} {% step %} ### Detection System detects condition. {% endstep %} {% step %} ### Command Stop command sent to targets. {% endstep %} {% step %} ### Action Target devices stop filtering. {% endstep %} {% endstepper %} ### Paired Rules Automation creates paired rules internally: * One rule for starting (PM10 > threshold) * One rule for stopping (PM10 < threshold) These paired rules are managed together as a single rule in the UI. ## Live Status Rule cards show real-time: * Current PM10 from trigger * Whether threshold is exceeded * Target device status ## Best Practices ### Threshold Selection * Consider normal background levels * Allow for fluctuations * Test before deploying ### Target Selection * Start with devices nearest sensor * Consider air flow patterns * Multiple targets for large areas ### Monitoring * Review rule effectiveness * Adjust thresholds as needed * Check historical data ## Empty State If no rules exist: * Message indicating no automation * "Create Rule" button ## Permissions Creating/editing rules requires: * Member or Admin role * Access to trigger and target devices * Active licenses on devices ## Related Documentation * [Schedulers](broken://pages/6a965e1dbdaf8fbac4d277148e35412c62efbcad) - Time-based control * [Notifications](broken://pages/051e9b028bbd84763eebe2cf8123e6858cc5331c) - Email alerts * [AirWatch](file:///6726661/asset-types/airwatch/overview.md) - Trigger devices * [AirDome](file:///6726661/asset-types/airdome/overview.md) - Target devices # Overview The KEMPER Rule Engine - Automatic, sensor-driven control of your extraction systems The KEMPER Rule Engine is the automatic guardian of your air quality. It teams up your measuring devices (e.g. AirWatch) with your filtration units (e.g. AirDome or Clean Air Tower): the measuring devices constantly watch the air — and the Rule Engine makes sure the filtration units work exactly as hard as currently needed. No more and no less. You can find the Rule Engine for your site via the sidebar under **"Rule Engine"** (address: `/sites/[id]/rule-engine`).
## What can I do with it? **The Rule Engine can do the following for you:** * **React to fumes automatically:** When welding starts in the hall and dust levels rise, the filtration units ramp up on their own. Once the air is clean again, they ramp back down — without you doing anything. * **Control the whole hall as one:** Combine several AirWatch units and several room ventilation systems in **one** rule — the Rule Engine automatically merges all readings into one picture of the hall and controls all units together. Just select all devices; the Rule Engine takes care of the rest (more on this in the next chapter). * **Respect quiet times:** Should it be quiet at night? Should a base level of extraction always run in the morning, no matter what the sensors say? Both can be set up with schedules. * **Save energy and wear:** The units only run as hard as the air requires. That saves electricity and protects filters and motors. * **Play it safe when in doubt:** If a measuring device fails and the Rule Engine is "blind", it switches the units to full power as a precaution — never off. ### **Main building blocks** | Building block | What it does | Where to find it | | --------------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------- | | **Rule** | Connects one or more AirWatch to one or more extraction units and controls them automatically based on air quality | Overview page, **"New rule"** button | | **Schedule** | Gives the automation a frame: minimum operation, upper limit or fixed value within a time window | Inside a rule under **Settings → Schedules** | | **"Set now"** | Immediately and temporarily forces a fixed power — e.g. for a demonstration or maintenance | Button directly on each rule | | **Diagnostics** | Shows what the automation last decided and whether the devices confirmed the commands | Gauge icon on each rule | ### **Short examples** 1. *"The extraction should run automatically when welding takes place."* → Create a rule, select the AirWatch and the extraction units — done. The default settings take care of the rest. 2. *"We have a large hall with four AirWatch and three room ventilation units."* → Create **one** rule and simply select all seven devices. The Rule Engine automatically combines the four readings (by default the worst one counts) and controls all three ventilation units together. 3. *"At night the system may only run quietly at most."* → Add a schedule of type **"Upper limit / quiet hours"** to the rule, e.g. daily 22:00–6:00 with at most 30%. 4. *"During the early shift a base level of extraction should always run."* → Add a schedule of type **"Minimum operation"**, e.g. Monday to Friday, 6:00–16:00 with at least 40%. ## In Detail ### Multiple AirWatch, multiple units {% hint style="success" %} This is one of the biggest advantages of the Rule Engine compared to the previous automation: **you no longer have to wire up each ventilation unit individually to one specific AirWatch.** {% endhint %} Instead, in **one** rule you simply select all measuring devices and all units of an area, the Rule Engine handles the rest on its own. **How the interplay works:** * **All readings are automatically combined into one control value.** By default the **maximum** counts: i.e. the worst AirWatch. If heavy welding happens at just one workstation, the whole rule reacts, even if the rest of the hall is clean. * If you prefer to control by the **average** of all sensors instead, change this under **Settings → Expert → "Combine sensors"**. * **Offline devices are taken out automatically.** If an AirWatch fails, goes offline or stops delivering values for too long, it simply doesn't count for a while, the rule keeps running normally with the remaining sensors. In the expanded rule card you can see for each sensor whether it currently counts (and if not, why), plus the note *"Combined reading based on X of Y sensors"*. * **All units pull together.** Every extraction unit in the rule receives the same target, the whole hall is controlled as one unit, no device works "against" another. * **Only when all sensors fail does the safety net kick in:** the units then ramp up to the failsafe power (see "Built-in safety"). ### **Before/after:** | Previous automation | KEMPER Rule Engine | | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------- | | Each ventilation unit is controlled by exactly one AirWatch — many individual links | One rule for the whole area — simply select all devices | | If "its" AirWatch fails, the ventilation unit is left without control | Offline sensors drop out automatically, the remaining ones take over | | Every link must be maintained individually | Central settings, schedules and stages for everything together | > **Tip for large halls:** Create one rule per connected air area (e.g. "Hall North", "Hall South") and put all AirWatch and ventilation units of that area into it. Separate rules only make sense when areas really have separate air. ### How the Rule Engine thinks: target and reality The Rule Engine works with two simple concepts: * **The target:** How the unit should be running right now. The Rule Engine continuously recalculates the target — from the current readings and your schedules. Example: *"The unit should be switched on and running at 40% power."* * **The reality:** How the unit is actually running right now. The Rule Engine learns this from the devices' feedback. #### The constant reconciliation The heart of the Rule Engine is the **reconciliation**: at short intervals it compares the target with the reality. If both match, nothing happens. If the reality deviates from the target, the Rule Engine sends the unit a command to bring it back on course. **An example you may have experienced yourself:** You switch a filtration unit off by hand at the device. A few minutes later it turns back on by itself. That is not a bug — that is the reconciliation. The Rule Engine noticed: *"The target says ON, the reality says OFF"* — and switched the device back on. > **Rule of thumb:** If you want the unit to run differently on a permanent basis, change the **rules or schedules** — not the switch on the device. A manual change at the device will be reverted at the next reconciliation. #### Why the unit never runs "exactly" on the target value A filtration unit cannot hold its air volume to the exact point — it always oscillates a little around the target value. The Rule Engine knows this: it accepts a **tolerance window** around the target. As long as the unit stays within this window, everything is fine and nothing is readjusted. Only when the unit is clearly off does the Rule Engine step in. ## Creating a rule > **First use:** The very first time you open the Rule Engine for a site, your devices are connected to the Rule Engine once. You will briefly see the message *"Synchronising devices..."* — this only takes a moment and only happens the first time. On the overview page, click **"New rule"** (or **"Create rule"** if no rule exists yet). A wizard guides you through four steps: 1. **Basics:** Give the rule a clear name that describes the area or system — e.g. *"Welding bay north"*. This way you will recognise the rule later. 2. **AirWatch:** Select the measuring devices whose readings should drive this rule. You can **select multiple AirWatch** — the Rule Engine automatically combines their values into one control value (by default the worst one counts, see chapter "Multiple AirWatch, multiple units"). 3. **Extraction units:** Select the filtration units that should react to the air quality. Here too you can select multiple devices — they will all be controlled together. 4. **Review:** Check your selection and click **"Create"**. The rule is now active and works with proven default settings. You can adjust all settings, schedules and expert parameters at any time later.
> **Good to know — which device can do what?** The **AirDome** can adjust its power continuously (run faster or slower). All other devices — e.g. Clean Air Tower — can only **switch on and off**: for them, any target value above 0% means ON, 0% means OFF. #### **Note on old automations** {% hint style="warning" %} If this site still has automations from the older system that connect the same AirWatch to the same devices, the overview shows a red warning. Please disable the old automations first — otherwise both systems will control the same devices at the same time and get in each other's way. {% endhint %}
*** ### The overview page Each rule appears as an expandable card.
#### The card row (collapsed) * **Rule name** and current mode with target value (e.g. "Automatic · 40%") * **"Live"** or **"Test mode"**: In test mode the Rule Engine computes along but sends **no** commands to the devices (more below). * **Status indicator** (appears when needed): e.g. "Command sent" with a spinning icon when a command is on its way, or a red "Send failed". * **Buttons:** "Set now", Diagnostics (gauge icon), "Settings", Delete (trash can) and a **switch to activate/pause** the rule. #### The expanded card Expand a rule to see the current status in detail: * **Current status:** Mode, target power, power on/off, combined reading and when the last calculation ran. If the rule is currently controlled by a schedule, this is shown here too ("Currently controlled by the schedule …"). * **AirWatch:** Each sensor with its current reading and a note if it is currently not counting (offline, no fresh data, out of range). * **Extraction units:** Each device with its **live device status** (see the section "The device status" below). * **Summary:** Number of schedules, how many of them are active now, and the measured value in use (PM10/PM2.5). #### Activating, pausing, deleting a rule * **Switch off = rule paused:** The Rule Engine stops controlling these units — they remain in their last state ("frozen"). Pausing **never** switches anything off automatically. * **Delete** removes the rule permanently — here too, the devices remain in their last state. *** ### Settings: where do I find what, and what does it mean? Click **"Settings"** on a rule. The dialog has five tabs:
#### Tab "General" | Setting | Meaning | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **Name** | The display name of the rule. | | **Active** | The same switch as on the card: off = rule paused, the devices stay as they are. | | **Live / Test mode** (display only) | Whether the rule really sends commands. Live arming can only be changed by an administrator — contact support if needed. | #### Tab "Sensors"
Here you select the AirWatch devices whose readings drive the rule — you can add or remove devices at any time. Multiple sensors are automatically combined into one control value; offline or outdated sensors temporarily don't count. #### Tab "Units"
Here you select the extraction units the rule controls. You can add or remove devices at any time. #### Tab "Schedules"
Here you manage the rule's time windows, explained in detail in the next chapter. #### Tab "Expert" Behind a safety prompt lie the fine-tuning settings of the automation. {% hint style="danger" icon="face-eyes-xmarks" %} **Only change these values if you know what you are doing** — wrong values can make your extraction work incorrectly. When in doubt: contact support. The default values are right for the vast majority of applications. {% endhint %}
The following table gives a quick overview. **A detailed explanation of every single setting** — with its effect, examples and guidance on when a change makes sense — can be found at the end of this document in the chapter **"Reference: the expert settings in detail"**.
| Setting | Meaning | Default | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | | **Control strategy** | **Stages**: fixed power levels per threshold (see "Power stages" below). **Proportional**: power rises smoothly with the reading. | Stages | | **Measured value** | Which dust value the rule reacts to: **PM10** (coarse dust) or **PM2.5** (fine dust). | PM10 | | **Combine sensors** | How multiple sensor readings are combined into one control value: Maximum (safest), Average, Minimum or Weighted. With Maximum, the worst value always counts — a single smoky workstation is never "averaged away". | Maximum | | **Smoothing** | Filters out short measurement spikes before controlling — e.g. a passing forklift. Median (recommended), Mean or None. | Median | | **Smoothing window** | Time window each sensor is smoothed over. | 10 min | | **Compute interval** | How often the Rule Engine recalculates and reconciles. | 10 min | | **Deadband** | Minimum change of the target value (in percentage points) before a new command is sent. Prevents constant "flapping" and protects the devices. | 10 | | **Minimum hold time** | Rest period between two adjustments. Your own interventions ("Set now") and the safety mode still act immediately. | 15 min | | **Sensor timeout** | After this age a reading counts as outdated and no longer contributes. If **all** sensors deliver values that are too old, the safety mode (failsafe) kicks in. | 30 min | | **Unit feedback timeout** | Optional: maximum age of a unit's feedback to count as confirmation. Empty = no check. | empty | | **Failsafe power** | Power the units ramp up to when the rule is "blind" (sensor loss). Safety always ramps UP, never off. | 100% | | **Lower/upper plausibility limit** | Readings outside these limits (e.g. negative or a stuck sensor) are treated as "no value". | 0 / empty | | **Ventilation stages** | The stage table: from which dust level which power applies (only with strategy "Stages"). | see below | | **Proportional mapping** | Only with strategy "Proportional": power rises linearly from the lower to the upper reading, clamped between min and max power. | — | *** ### The power stages: how readings become a decision By default the Rule Engine works with a simple stage table: *the dirtier the air, the more power.* The default stages (PM10): | Dust level in the air | Unit power | | --------------------------------- | ---------- | | Very clean (below 75 µg/m³) | Off | | Slightly elevated (from 75 µg/m³) | 40% | | Clearly elevated (from 200 µg/m³) | 60% | | High (from 400 µg/m³) | 80% | | Very high (from 650 µg/m³) | 100% | Two things are cleverly solved here: * **The worst value counts.** If several measuring devices hang in the hall, the Rule Engine (default setting "Maximum") follows the device with the highest reading. A single smoky workstation is therefore never "averaged away". * **Short spikes are ignored.** A single measurement spike — say, from a passing forklift — does not trigger a reaction yet. Only when an elevated value persists for a while does the unit react. This keeps operation calm. You can adapt the stages to your hall in the **Expert → Ventilation stages** tab. *** ### Schedules: your wishes take precedence You find schedules under **Settings → Schedules**. With them you give the automation a frame. A schedule entry always consists of: a **name**, the **weekdays**, a **time from–to**, a **setpoint** and a **type of intervention** (in the interface: "Type"). There are three types:
#### 1. Minimum operation ("at least this much") *"During this time window the unit runs at least at X%."* The automation may give **more** power at any time if the air is bad — but never less than your minimum. The unit therefore never switches off during this window. **Typical use:** base extraction during working hours. *Example: Monday to Friday, 6:00–16:00, minimum operation 40%.* Even with perfectly clean air the unit then runs at 40% — if dust rises, it automatically ramps up. #### 2. Upper limit / quiet hours ("at most this much") *"During this time window the unit runs at most at X%."* The automation may give less, but never more than your upper limit — no matter what the sensors report. **Typical use:** night quiet hours. *Example: daily 22:00–6:00, upper limit 30%.* The unit stays quiet at night, even if a reading briefly rises. **Special case upper limit 0%:** This means *"during this window the unit is off — period."* This deliberately also applies if a measuring device fails: an off-window means off, for example in an empty hall after closing time. #### 3. Force fixed value ("exactly this much") *"During this time window the unit runs at exactly X% — no matter what else applies."* The fixed value overrides everything: the readings, every minimum and every upper limit. It is the strongest tool and intended for special cases — such as a demonstration, maintenance or deliberate temporary manual operation. If several fixed values overlap in time, the **priority** you assign on the entry decides: the entry with the higher priority wins. #### How the three types get along If several entries are active at the same time, a fixed order of precedence applies — deliberately built so that **safety always wins**: 1. First, the automation calculates its proposal from the readings. 2. Then the **upper limit** is applied (caps upwards). 3. Then the **minimum operation** (raises from below) — **the minimum beats the upper limit**. Example: at night "at most 30%" applies, but a safety minimum of 50% for a critical area prevails. 4. Finally a **fixed value**, if present — it overrides everything. #### Good to know * **Time windows may cross midnight** (e.g. 22:00–6:00). * **Every entry has a switch to activate/deactivate it** — this way you can temporarily disable an entry without deleting it. * **The setpoint percentage applies exactly only to the AirDome.** All other devices can only switch on/off: any value above 0% turns them ON, 0% means OFF. * While editing, the dialog shows a live summary under **"In plain words"** of what the entry will do — e.g. *"Sets Mon–Fri, 06:00–16:00, to exactly 40%."* *** ### "Set now": the quick manual intervention
With the **"Set now"** button on each rule you immediately force a fixed power — regardless of the sensors: 1. Choose the **power**: Off, 25%, 50%, 75% or 100%. 2. Choose the **duration**: 1, 2, 4 or 8 hours. 3. Click **"Apply"**. Technically this creates a high-priority time window for today (type "Force fixed value"). You will find it under **Settings → Schedules** and can delete or deactivate it there early at any time. After the duration expires, normal automation takes over again automatically. *** ### Why do some things not happen immediately? Inertia as protection The Rule Engine is deliberately not a "nervous" system. It protects your units from constant back and forth. You will notice this in four places: **1. Commands go out immediately — confirmations take time.** When you save a rule or a schedule, the Rule Engine sends the matching command to the unit right away. The unit's **feedback** ("I'm now really running at 40%") only arrives with the next regular device report — this can take a few minutes. During this time the device status shows "Command sent". This is normal and not an error. **2. Small changes are deliberately skipped.** If the calculated target only changes minimally (less than the deadband, 10 percentage points by default), the Rule Engine does not adjust the unit. The unit's tolerance window would swallow the difference anyway — and every unnecessary adjustment command means wear. The status display then reads: *"Change too small – not sent (protects devices)."* **3. There is a rest period between two adjustments.** The automation does not adjust the power every minute; after each change it observes a rest phase (minimum hold time, 15 minutes by default). Exceptions: when **you** deliberately change something ("Set now", new schedule) or when **safety** demands it, action is taken immediately. **4. Switching on happens in two steps.** For units with adjustable air volume (AirDome), the Rule Engine first switches on the motor. Only when the unit reports back that the motor is running is the desired air volume set. Right after switching on, the unit may therefore run at a different power than configured for a few minutes — it is then readjusted automatically. In the interface you see two steps on the device for this: *"Switched on ✓"* and *"Adjusting volume flow …"*. *** ### The device status: what the indicators mean
For each unit you can see in the expanded rule card (and in the diagnostics) where it currently stands in the reconciliation: | Indicator | Meaning | What you should do | | ------------------ | ---------------------------------------------------------------------- | --------------------------------------------------------------------------- | | **Change queued** | A change is pending, the command has not been sent yet | Nothing — wait a moment | | **Command sent** | The command is on its way, the unit's confirmation is still pending | Nothing — the confirmation typically arrives within a few minutes | | **Confirmed** | The unit is verifiably running as desired | Nothing — all good | | **Send failed** | The command did not get through; the Rule Engine retries automatically | If it stays this way permanently: check the unit and its connection on site | | **Device offline** | The unit no longer reports in | Check the unit on site (power, connection) | After every save, the interface automatically watches the devices closely until all commands are confirmed — you see the progress live on each device and as a status indicator in the card row, even when the card is collapsed. *** ### Built-in safety: failsafes and protection mechanisms The Rule Engine has several protection mechanisms firmly built in. You don't have to configure anything for them — they are always active: **Failsafe on sensor loss — full power, never off.** When all measuring devices of a rule fail or stop delivering values for too long (sensor timeout, 30 minutes by default), the Rule Engine is "blind". Then the principle is: better to extract too much than too little — the units ramp up to a safe, high value (failsafe power, 100% by default). The failsafe acts **immediately**, without any rest period. The interface shows a red notice for this: *"Safety mode: no fresh sensor data — running at the safe level."* The only exception: a deliberate off-window (upper limit 0%) stays off even in failsafe — e.g. in an empty hall after closing time. **Single sensor failure — the others take over.** If only some of the measuring devices fail, no failsafe is triggered: offline sensors and sensors with outdated values are automatically removed from the calculation, and the rule keeps running normally with the remaining sensors. **Outlier protection.** Implausible readings (e.g. negative values or a stuck sensor, configurable via the plausibility limits) are treated as "no value". Short measurement spikes are filtered out by the smoothing before any control action is taken. **Safety wins with schedules.** In the order of precedence of schedules, minimum operation beats the upper limit — a safety minimum for a critical area therefore prevails even against a night-quiet upper limit. **Device protection: deadband and rest period.** Minimal target changes are not transmitted (deadband), and there is a rest phase between two adjustments (minimum hold time). This protects motors and filters from constant back and forth. Your deliberate interventions and the failsafe still always act immediately. **Pausing a rule means freezing, not switching off.** When you deactivate an entire rule, the Rule Engine stops controlling these units — they remain in their last state. Pausing never switches anything off automatically. **Failed attempts are limited.** If the Rule Engine cannot reach a unit, it retries at growing intervals — but never in rapid fire. After several failed attempts it pauses and automatically tries again later. You can always see the current state on the device status. **No sending to offline devices when the target is "off".** If a unit is offline and the target would be "off" anyway, the Rule Engine deliberately does not send a command into the void — the device status then shows "Device offline". *** ### Test mode and live operation
Each rule is either **Live** or in **Test mode** (shown in the card row): * **Live:** Commands are really sent to the devices. * **Test mode:** The Rule Engine computes normally and logs what it *would* do — but sends **no** commands. The expanded card then permanently shows the notice: *"Test mode – no commands are sent to devices."* This lets you observe a new rule first, before it really intervenes. Switching between test mode and live can only be done by an administrator — contact support for this. *** ### Diagnostics: tracing what happened Via the gauge icon on each rule you open the **Diagnostics**. It has four tabs: | Tab | Content | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Status** | The current state of the rule: mode, target power, combined reading, what is currently driving the rule and the reason for the last decision — in plain language, e.g. *"Change too small – not sent (protects devices)"*. | | **Decision log** | The history: when the automation decided what, with which reading and for what reason. | | **Send attempts** | Every single command to the devices: time, command, whether it was accepted and the result. Entries marked "Test" were only logged, not sent (test mode). | | **Device status** | The live reconciliation status of each device: status, setpoint, number of attempts and last attempt. | With **"Refresh"** you reload all tabs. The diagnostics are also the right tool for support — here it is written in black and white what happened when. *** ### Frequently asked questions **"I switched the unit off at the device — why did it turn back on?"** Because an active rule specifies the target "ON". The Rule Engine restores the target state during reconciliation. If you want to deliberately switch the unit off, use the rules or schedules — for example "Set now" with power "Off" for a certain period. **"I deleted the schedule entry with the minimum operation — why did the unit switch off?"** Without a minimum, the air quality alone decides. If the air was clean, "off" is the correct automatic decision. The minimum was the only reason the unit was running. **"I saved something, but nothing is happening at the unit."** The command is usually already on its way — look at the device status in the expanded card: if it says "Command sent", the Rule Engine is just waiting for the unit's confirmation. This typically takes a few minutes. Also check whether the rule is in **test mode** — then no commands are sent at all. **"Why does the unit show 12,700 instead of the configured 12,800?"** Units never hold their air volume to the decimal point. As long as the value lies within the tolerance window around the target, everything is set correctly — the Rule Engine deliberately does not readjust. **"What is the difference between 'pausing a rule' and 'deactivating a schedule entry'?"** Pausing the **rule** (switch on the card) = stopping the automation completely; the units stay as they currently are. Deactivating a **schedule entry** (switch on the entry) = only this one entry is dropped; the automation keeps running and recalculates the target — the unit may then ramp up or down. **"Saved a small change, but the unit doesn't react?"** Very small changes (less than the deadband, 10 percentage points by default) are deliberately not transmitted by the Rule Engine — they would lie within the unit's tolerance window anyway and would only cause wear. The status display points this out in that case. **"My AirWatch is shown as 'No fresh data' on the rule — what does that mean?"** The sensor has not delivered a reading for longer than allowed (sensor timeout, 30 minutes by default). It temporarily doesn't count. If all sensors of a rule deliver values that are too old, the safety mode kicks in. **"Can I use multiple AirWatch in one rule?"** Yes — that is exactly what the Rule Engine is built for. Simply select all measuring devices of the area; the Rule Engine automatically combines the values (by default the worst AirWatch counts) and independently removes failed sensors from the calculation. Details in the chapter "Multiple AirWatch, multiple units". **"Can I create multiple rules for the same site?"** Yes — for example one rule per hall area, each with its own AirWatch and its own devices. Just make sure that **one device is not controlled by two rules at the same time**, otherwise the rules will get in each other's way. *** ### Reference: the expert settings in detail This chapter is aimed at trained users. You find the expert settings under **Settings → tab "Expert"** — they are only shown after a safety prompt ("I understand"). All settings apply per rule; other rules remain untouched. Changes only take effect with **"Save"**. > **Principle:** The default values are designed for typical welding and hall applications. Always change only one setting at a time and observe the effect via the decision log in the diagnostics. #### Control strategy *Default: Stages* Determines how a reading becomes a target power: * **Stages:** The rule works with a stage table — from threshold X, power Y applies (see "Ventilation stages" below). Predictable and robust; the right choice for almost all applications. * **Proportional:** Power rises smoothly (linearly) with the reading — without fixed stages (see "Proportional mapping" below). Useful when a unit with continuously adjustable air volume (AirDome) should breathe along as evenly as possible. Depending on the selection, either the stage editor or the proportional editor is shown below. #### Measured value *Default: PM10 (coarse dust)* Which dust value the rule reacts to: * **PM10 (coarse dust):** The usual reference value for welding fumes and hall dust. * **PM2.5 (fine dust):** Reacts to the finer dust fraction. Only choose this if your risk assessment explicitly targets PM2.5. Important: The thresholds of the ventilation stages always refer to the measured value chosen here. If you switch the measured value, you should also review the stage thresholds — PM2.5 values are typically much lower than PM10 values. #### Combine sensors *Default: Maximum (safest)* How the values of several AirWatch are combined into **one** control value: | Option | Behaviour | When useful | | -------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | **Maximum (safest)** | The worst sensor determines the power | Recommended. No workstation is "averaged away" — a single smoky area is enough for a reaction | | **Average** | Mean of all sensors | Large, well-mixed halls where the overall load counts | | **Minimum** | The best sensor determines the power | Only for special cases — the rule only reacts when **all** areas are polluted | | **Weighted** | Weighted mean (weights per sensor, assigned via support) | When individual sensors are more important than others, e.g. at the main workstation | Offline sensors and sensors with outdated values are automatically removed from the calculation with all options. #### Smoothing *Default: Median (recommended)* Filters out short measurement spikes before any control action — say, a passing forklift or a single shower of sparks right next to the sensor: * **Median (recommended):** The middle value within the time window. Individual outliers drop out completely — the most robust choice. * **Mean:** The average within the time window. Outliers are dampened but still contribute. * **None (latest value):** The newest reading always counts. Fastest reaction, but also the most nervous — only useful when very fast reaction matters more than smooth operation. #### Smoothing window *Default: 10 minutes* The period over which each sensor is smoothed (works together with the smoothing above). * **Larger value** → calmer but more sluggish behaviour: the rule reacts later to real changes. * **Smaller value** → faster reaction, but more restlessness from short fluctuations. #### Compute interval *Default: 10 minutes* How often the Rule Engine recalculates and reconciles target with reality. Determines the base cycle of the whole system: more frequent calculation means faster reaction to reading changes, but also more frequent opportunities to intervene. Values below 5 minutes bring little benefit in practice, since device reports only arrive every few minutes anyway. #### Deadband *Default: 10 percentage points* The minimum change of the target value before a new command is sent to the devices. Example with the default value: the unit runs at 40%, the newly calculated target is 45% — the difference (5 percentage points) is below the deadband, nothing is sent. Only from 50% would it be adjusted. * **Larger value** → fewer adjustment commands, less wear, but coarser control. * **Smaller value** → finer control, but more switching operations. * **0** disables this protection — not recommended. Note: A switch between ON and OFF as well as your deliberate interventions ("Set now", new schedules) are not subject to the deadband. #### Minimum hold time *Default: 15 minutes* The rest period between two automatic adjustments. After each change, the automation waits at least this long before adjusting again — even if the reading changes in the meantime. * **Exceptions (always act immediately):** your deliberate interventions ("Set now", schedule saved) and the failsafe. * **Larger value** → calmer operation; **smaller value** → faster tracking. #### Sensor timeout *Default: 30 minutes* From this age a reading counts as outdated: the sensor then no longer contributes (shown as "No fresh data" on the rule card). If **all** sensors of a rule deliver values that are too old, the failsafe kicks in. * **Too small:** sensors drop out already during normal reporting pauses, the failsafe kicks in unnecessarily often. * **Too large:** the rule may keep working with outdated values for a long time. * As a rule of thumb: at least twice the normal reporting interval of your sensors. #### Unit feedback timeout *Default: empty (no check)* Optional: the maximum age of a unit's feedback for it to count as **confirmation** of a command. If a value is set, a command only counts as "Confirmed" when the matching feedback from the unit is fresh enough. If the field stays empty, the age of the feedback is not checked. Only set a value here if you deliberately want to verify confirmations more strictly — a value that is too small causes commands to remain stuck as "Sent" permanently. #### Failsafe power *Default: 100%* The power the units ramp up to when the rule is "blind" (all sensors failed or outdated). Safety always ramps **up**, never off — which is why no "off" can be stored here that would apply while flying blind. Only lower this if full power in the failsafe case is demonstrably unnecessary or unreasonable (e.g. noise protection) — and your risk assessment supports it. #### Lower / upper plausibility limit *Default: 0 µg/m³ / empty (no upper limit)* Readings outside these limits are treated as "no value": * **Lower limit:** values below it (e.g. negative readings due to a sensor fault) are discarded. * **Upper limit:** values above it (e.g. a stuck sensor permanently reporting an extreme value) are discarded. Empty = no upper limit. Be careful with the upper limit: if it is set too low, **real** high pollution values are discarded as well — and the rule fails to react exactly when it matters most. #### Ventilation stages *Only with control strategy "Stages". Default table: 0 → Off, from 75 → 40%, from 200 → 60%, from 400 → 80%, from 650 → 100% (µg/m³, PM10)* The stage table: each row consists of a threshold **"From (µg/m³)"** and a **"Power (%)"**. From the threshold onwards, the extraction runs at the given power until the next higher stage is reached. Use **"Add stage"** to add rows and the trash can icon to remove them. Practical notes: * The first stage (0 → 0%) defines the "air is clean" state: unit off. * The thresholds refer to the chosen **measured value** (PM10 or PM2.5) **after** smoothing and sensor combination. * Stages that lie too close together lead to frequent switching back and forth — deadband and minimum hold time dampen this, but cannot prevent it entirely. * For devices that can only switch on/off (everything except the AirDome), only this counts: power 0% = OFF, anything above = ON. #### Proportional mapping *Only with control strategy "Proportional"* Power rises linearly from the lower to the upper reading, clamped between min and max power. Four values: | Field | Meaning | | --------------- | ----------------------------------------- | | **Reading min** | Up to this reading, the min power applies | | **Reading max** | From this reading, the max power applies | | **Power min** | Lower power limit (with clean air) | | **Power max** | Upper power limit (with heavy pollution) | *Example:* reading min 50, reading max 400, power min 20%, power max 100% — at 225 µg/m³ (the middle) the unit runs at 60%. Below 50 µg/m³ it stays at 20%, above 400 µg/m³ at 100%. *** *In short: with rules and schedules you describe how your air should be — the Rule Engine takes care of making it so, around the clock. It checks constantly, corrects gently and always takes the safe path when in doubt.* # Error Codes This reference documents error and fault codes for all device types in KEMPER Connect. ## Error Code Overview Devices report error status via dedicated fields: | Device Type | Error Field | Warning Field | | ------------------------------- | ----------- | ------------- | | AirDome | FEHLERCODE | WARNING | | Clean Air Tower (Self-Cleaning) | FEHLERCODE | - | | Clean Air Tower (Disposable) | FAULT\_CODE | - | | VacuFil 125 | fault\_code | - | A value of **0** indicates no error (system healthy). ## AirDome Error Codes ### Errors (FEHLERCODE) | Code | Name | Description | Action | | ---- | ---------------------------- | ------------------------ | ------------------------------------ | | 0 | OK | No error | None required | | F90 | Frequency inverter error | Inverter malfunction | Check power, contact service | | F94 | Critical filter pressure | Filter pressure too high | Check filter, may need replacement | | F95 | Control error | System control issue | Restart, contact support if persists | | F96 | Compressed air not connected | No air supply | Connect compressed air supply | ### Warnings (WARNING) | Code | Name | Description | Action | | ---- | ------------------------ | ------------------------- | ------------------------------ | | 0 | OK | No warning | None required | | SER | Maintenance overdue | Service interval exceeded | Schedule maintenance | | A03 | Filter pressure too high | Elevated filter pressure | Monitor, schedule service | | A04 | No flow rate calculation | Cannot calculate flow | Check sensors, contact support | ## Clean Air Tower (Self-Cleaning) Error Codes ### Errors (FEHLERCODE) | Code | Name | Description | Action | | ---- | ---------------------------- | -------------------- | ---------------------------- | | 0 | OK | No error | None required | | E00 | Frequency inverter error | Inverter malfunction | Check power, contact service | | E03 | Compressed air not connected | No air supply | Connect compressed air | | E05 | Control error | System control issue | Restart, contact support | ## Clean Air Tower (Disposable) Fault Codes ### Faults (FAULT\_CODE) | Code | Name | Description | Action | | ---- | -------------------------- | --------------------- | ----------------------------------- | | 0 | OK | No fault | None required | | E02 | Airflow control error | Fan/airflow issue | Check fan, verify no obstructions | | E03 | Maintenance required | Service needed | Schedule maintenance | | E04 | Motor temperature too high | Overheating | Allow cooling, check ventilation | | E07 | Modbus error | Communication failure | Check connections, restart | | E12 | Airflow too low | Insufficient airflow | Check for blockages, filter clogged | ## VacuFil 125 Fault Codes ### Faults (fault\_code) | Code | Name | Description | Action | | ---- | ---- | ----------- | ------------- | | 0 | OK | No fault | None required | Additional codes may be device-specific. Consult device documentation. ## Error Severity ### Critical Errors Require immediate attention: * F90/E00: Frequency inverter * F94: Critical pressure * E04: Motor overheating ### Warning Errors Monitor and plan service: * SER: Maintenance overdue * A03: Elevated pressure * E03: Maintenance required ### Communication Errors May resolve on retry: * E07: Modbus error * A04: Calculation failure ## Error Display in UI ### Settings Tab Each device's Settings tab shows: * Current error/fault code * Status message * "System Healthy" or error description ### Dashboard When error detected: * "Service Required" alert * Red status badge * Error details available in Settings ### Assets List Device cards show: * Error badge on affected devices * Quick visual identification ## Common Troubleshooting ### Compressed Air Errors (F96, E03) {% stepper %} {% step %} ### Verify air supply is connected Ensure compressed air lines are connected to the device. {% endstep %} {% step %} ### Check pressure is adequate Typical required pressure: 6-8 bar. Verify actual pressure meets requirements. {% endstep %} {% step %} ### Inspect air lines for leaks Look for visible damage or audible leaks and repair as needed. {% endstep %} {% step %} ### Ensure filter cleaning system functional Confirm the filter cleaning/maintenance system is operating correctly. {% endstep %} {% endstepper %} ### Motor/Inverter Errors (F90, E00) {% stepper %} {% step %} ### Check power supply stable Verify voltage and supply stability to the device. {% endstep %} {% step %} ### Verify no overload condition Confirm the device isn't overloaded or operating beyond rated capacity. {% endstep %} {% step %} ### Inspect electrical connections Check wiring and connectors for looseness or damage. {% endstep %} {% step %} ### Contact service for persistent issues If the error persists after checks, contact KEMPER service. {% endstep %} {% endstepper %} ### Temperature Errors (E04) {% stepper %} {% step %} ### Allow motor to cool down Stop operation to let the motor reach safe temperature. {% endstep %} {% step %} ### Reduce continuous operation time Limit long continuous runs to avoid overheating. {% endstep %} {% step %} ### Check ventilation around motor Ensure adequate airflow and no obstructions to ventilation. {% endstep %} {% step %} ### Reduce boost mode usage Minimize use of high-power/boost modes that increase heat. {% endstep %} {% step %} ### Contact service if recurring If overheating returns, contact KEMPER service. {% endstep %} {% endstepper %} ### Airflow Errors (E02, E12) {% stepper %} {% step %} ### Check for physical obstructions Inspect ducts, intakes, and outlets for blockages. {% endstep %} {% step %} ### Inspect filter condition Look for clogged or damaged filters; replace if necessary. {% endstep %} {% step %} ### Verify fan operation Confirm the fan runs and operates at expected speed. {% endstep %} {% step %} ### Replace filter if clogged If cleaning doesn't restore flow, install a new filter. {% endstep %} {% endstepper %} ### Communication Errors (E07) {% stepper %} {% step %} ### Check cable connections Ensure communication cables are connected and undamaged. {% endstep %} {% step %} ### Verify device powered properly Confirm the device has stable power and is turned on. {% endstep %} {% step %} ### Restart device Power-cycle the device to attempt to clear transient communication faults. {% endstep %} {% step %} ### Contact support if persists If communication doesn't recover, contact KEMPER support. {% endstep %} {% endstepper %} ## Service Contact For unresolved errors: * Contact KEMPER service * Provide error code and device serial * Describe symptoms and troubleshooting attempted ## Related Documentation * [AirDome Settings](file:///6726661/asset-types/airdome/settings.md) * [Clean Air Tower (Self-Cleaning) Settings](file:///6726661/asset-types/clean-air-tower-abreinigbar/settings.md) * [Clean Air Tower (Disposable) Settings](file:///6726661/asset-types/clean-air-tower-einweg/settings.md) * [VacuFil 125 Settings](file:///6726661/asset-types/vacufil-125/settings.md) * [Service Monitoring](file:///6726661/monitoring/service/overview.md) # API Reference KEMPER Connect API Overview ## Overview KEMPER Connect exposes a programmatic API that lets you integrate your existing IT/OT infrastructure with the KEMPER Connect Bridge and all connected KEMPER devices. {% hint style="warning" %} This is advanced topic. Please contact KEMPER Connect support for help on this topic. {% endhint %} ### Is there a public or partner API? Yes. KEMPER Connect offers several integration options, ranging from a ready-to-use **GraphQL API** to advanced real-time streaming and webhook integrations. The GraphQL API is available today; the advanced real-time options are optional, paid add-ons that KEMPER enables for you together with Datacake (see Integration Options). The GraphQL API is a single endpoint. KEMPER Connect does **not** publish a separate REST API; all standard data access and device control is performed through GraphQL. ### Integration options at a glance | Option | What it does | Availability | | ------------------------------ | ---------------------------------------------------------------------------- | ---------------------- | | GraphQL API | Read sites, devices, live telemetry and history; send commands; manage rules | Available now | | MQTT real-time live stream | Continuous real-time push of measurement data to an MQTT broker | Advanced add-on (paid) | | Outgoing webhooks | Immediate HTTPS push of measurement data to your endpoint | Advanced add-on (paid) | | Rule-based webhooks / alerting | Trigger and control third-party systems from rules and alerts | Advanced add-on (paid) | See Integration Options for details on each option and how to request it. ### What the GraphQL API provides | Capability | Supported | | ---------------------------------------------------- | ----------------------------------------- | | Read sites (workspaces) and their devices | Yes | | Read live telemetry (current measurements) | Yes | | Read historical time-series data | Yes | | Send remote commands (start/stop, parameter changes) | Yes (device-dependent) | | Manage automation and scheduling rules | Yes | | Email notifications on thresholds | Yes (via rules) | | Real-time push (MQTT / webhooks) | Advanced add-on — see Integration Options | ### How to get access Access to the GraphQL API is granted through a Datacake API token. {% hint style="danger" %} Tokens **cannot** currently be self-generated in the KEMPER Connect portal. KEMPER provisions them for you as a custom setup step (see Authentication). To request API access, a dedicated API user, adapter scripts, or any of the advanced integration options, contact KEMPER. {% endhint %} *** ## Integration Options KEMPER Connect can expose device data and control through several channels. The GraphQL API is available immediately; the real-time and webhook options are advanced, paid add-ons enabled per customer. ### GraphQL API A standard GraphQL endpoint for reading sites, devices, live telemetry and history, sending commands, and managing rules. This is the interface documented throughout the rest of this guide. It is best suited to request/response access and scheduled polling by middleware, historians, or BI tools. ### MQTT real-time live stream (advanced) A continuous, real-time stream of measurement data to an MQTT broker. Instead of polling, your systems subscribe to topics and receive values as they arrive. Suited to live dashboards, SCADA/OT historians, and low-latency processing. ### Outgoing webhooks (advanced) Measurement data is pushed to an HTTPS endpoint you provide, in real time as it is received. Suited to event-driven pipelines that ingest data without polling. ### Rule-based webhooks and alerting (advanced) Webhooks fired from rules and alerts to actively drive third-party systems (for example, ticketing, alerting, or automation platforms) when a threshold or condition is met. ### Availability and how to request * The **GraphQL API** can be enabled for your workspace today. KEMPER provisions your access token and, where available, adapter scripts to help you get started. * The **MQTT live stream**, **outgoing webhooks**, and **rule-based webhooks** are **advanced topics** offered as a **paid API package**. * These advanced options are delivered together with Datacake: contact KEMPER, we forward your request to Datacake, and Datacake sets up the integration and gets in touch with you directly. To start, contact KEMPER with your use case and the systems you want to integrate. *** ## Authentication The API uses **token-based authentication** (API key style). There is no OAuth2 authorization-code flow and no separate client-id/client-secret handshake. Every request carries a static token in the `Authorization` header. ### Token types | Token type | How it is obtained | Recommended for | | ------------------- | ------------------------------------------ | ------------------------------- | | Personal user token | Returned when a user account authenticates | Quick tests, single-user access | | API user token | Provisioned by KEMPER for a workspace | Production/system integrations | For system-to-system integrations (SCADA, MES, PLC gateways, BI tools) we strongly recommend a **dedicated API user token**. It is not tied to a person, can be scoped to specific workspaces, and can be revoked independently. > Important: API tokens cannot currently be created or managed self-service in the KEMPER Connect portal. KEMPER provisions them for you as a custom setup step, and can provide adapter scripts where available. Contact KEMPER to have your token (and, if needed, a dedicated API user) created. ### Header format All requests must include the token using the `Token` scheme (not `Bearer`): ```http Authorization: Token Content-Type: application/json ``` > Note: The token is a Datacake DRF API key. It must be sent with the `Token` prefix. Sending it as `Bearer` will fail. ### Obtaining a token #### API user token (recommended) Contact KEMPER to have a dedicated API user created for your workspace. You will receive a long-lived token that you store securely in your integration (for example, in a secrets manager or environment variable). ### Security * Always use HTTPS. All API traffic must be encrypted in transit. * Treat the token like a password. Do not embed it in client-side code or commit it to source control. * A request with a missing, invalid, or revoked token returns HTTP `401 Unauthorized`. *** ## Connecting to the API ### Endpoint ``` POST https://api.datacake.co/graphql/ ``` All operations (queries and mutations) are sent as HTTP `POST` requests to this single endpoint. ### Request format The request body is JSON with a `query` string and an optional `variables` object: ```json { "query": "query { ... }", "variables": { "key": "value" } } ``` ### Minimal example ```bash curl -X POST https://api.datacake.co/graphql/ \ -H "Authorization: Token YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"query":"query { user { id email } }"}' ``` ### Schema and introspection The API is a standard GraphQL service and supports GraphQL introspection. You can point any GraphQL client (for example, Insomnia, Altair, or a code-generation tool) at the endpoint to browse the full schema, available types, and fields. *** ## Data Model This section describes the core objects you will work with. ### Entity overview ```mermaid flowchart TB User[User / API User] Workspace["Site (Workspace)"] Device[Device] Product[Product Type] Measurement[Measurement Field] Rule[Automation Rule] User --> Workspace Workspace --> Device Device --> Product Device --> Measurement Workspace --> Rule Rule --> Device ``` ### Sites (Workspaces) A **Site** in the KEMPER Connect UI corresponds to a Datacake **workspace**. It is the top-level container that groups devices and members. Every site is identified by a UUID. | Field | Type | Description | | ------------- | ------ | ---------------------------------------------------- | | `id` | UUID | Unique site identifier (used as `siteId` in the app) | | `name` | String | Display name of the site | | `slug` | String | URL-friendly identifier | | `deviceCount` | Int | Number of devices in the site | | `memberCount` | Int | Number of members | ### Devices A **Device** is a physical KEMPER unit or sensor connected to a site. | Field | Type | Description | | --------------------- | -------------- | ----------------------------------------- | | `id` | UUID | Unique device identifier | | `verboseName` | String | Human-readable device name | | `serialNumber` | String | Device serial number | | `claimSerialNumber` | String | Serial used to claim the device | | `product` | Object | Product type: `{ id, slug, hardware }` | | `online` | Boolean | Whether the device is currently connected | | `lastHeard` | DateTime | Timestamp of last data transmission | | `tags` | \[String] | Free-form tags | | `currentMeasurements` | \[Measurement] | Latest values (see Telemetry) | ### Products Each device has a `product` with a `slug` that identifies its type (for example, `airwatch-lte-europe`, `airdome`, `kemper-connect-bridge`). Product slugs determine which measurement fields and remote commands are available. See Device Types and Their Fields. ### Sensors and actuators Devices fall into two functional roles for integration purposes: * **Sensors** measure the environment. The primary air-quality sensor family is **AirWatch** (PM2.5 / PM10 particulate matter). * **Actuators** are filtration units that can be controlled (AirDome, Clean Air Tower, and Bridge-connected filters). ### The KEMPER Connect Bridge The **KEMPER Connect Bridge** (`product.slug = "kemper-connect-bridge"`) brings existing KEMPER machines online. A single bridge represents one downstream machine. The connected machine type is reported through the numeric `DEVICE_TYPE` measurement: | `DEVICE_TYPE` range | Connected machine | | ------------------- | ------------------------------- | | 1–19 | VacuFil Compact | | 20–29 | MaxiFil Clean | | 30–59 | Automation Line | | 60–69 | AirDome | | 70–79 | Clean Air Tower (self-cleaning) | When controlling a Bridge device, commands are sent to the **bridge device ID** (not a separate downstream ID). See Remote Control. *** ## Sites and Devices ### List all sites Returns every workspace (site) the token has access to. ```graphql query GetSites { allWorkspaces { id name deviceCount memberCount } } ``` ### Get a single site ```graphql query GetSite($workspaceId: String!) { workspace(id: $workspaceId) { id name slug } } ``` ### List devices in a site ```graphql query GetDevices($workspaceId: String!) { allDevices(inWorkspace: $workspaceId) { id verboseName serialNumber product { id slug hardware } online lastHeard tags } } ``` ### Get a single device ```graphql query GetDevice($deviceId: String!) { device(deviceId: $deviceId) { id verboseName serialNumber online lastHeard product { slug } } } ``` *** ## Telemetry and Operating Data Telemetry is exposed through two mechanisms on a device: **current measurements** (latest value per field) and **history** (time-series). ### Current measurements Request the latest value of one or more measurement fields by name. Field names are case-sensitive and vary by product (see Device Types and Their Fields). ```graphql query GetCurrent($deviceId: String!) { device(deviceId: $deviceId) { currentMeasurements( fieldNames: ["PM10_VALUE", "PM25_VALUE", "MOTOR_RUNNING", "FAULT_CODE"] ) { value field { fieldName } } } } ``` ### Historical data Historical values are returned as a JSON-encoded string for the requested fields, time range, and resolution. ```graphql query GetHistory( $deviceId: String! $start: String! $end: String! $fields: [String] $resolution: Int ) { device(deviceId: $deviceId) { history( fields: $fields timerangestart: $start timerangeend: $end resolution: $resolution ) } } ``` ### Data categories and field names The tables below map the common operating data the customer asked about to the underlying field names. Some products use different casing or German field names; both variants are listed. #### Status and connectivity | Data | Field(s) | Notes | | ------------- | ------------------------- | ---------------------------- | | Online status | `online` | Device attribute (boolean) | | Last seen | `lastHeard` | Device attribute (timestamp) | | On/off | `ON_OFF`, `MOTOR_RUNNING` | Boolean operational state | #### Air quality (particulate matter) | Data | Field(s) | Unit | | --------------- | ----------------------------------------- | -------- | | PM2.5 | `PM25_VALUE` / `pm25_value` | µg/m³ | | PM10 | `PM10_VALUE` / `pm10_value` | µg/m³ | | Total particles | `NR_PARTICLES` / `binSum` | count/m³ | | Particle bins | `BIN0_VALUE`–`BIN5_VALUE` / `bin0`–`bin5` | count | #### Alarms, faults and warnings | Data | Field(s) | Notes | | ---------- | ------------------------------------- | -------------- | | Error code | `FEHLERCODE` | 0 = OK | | Fault code | `FAULT_CODE` / `fault_code` / `FAULT` | 0 = OK | | Warning | `WARNING` | Warning status | #### Runtime and maintenance | Data | Field(s) | Unit | | ---------------------- | --------------------------------------------------- | ----- | | Operating hours | `OPERATING_HOURS` / `BETRIEBSSTUNDEN` | h | | Hours until service | `MAINTENANCE_HOURS` / `BETRIEBSSTUNDEN_BIS_WARTUNG` | h | | Filter cleaning cycles | `NR_FILTER_CLEANINGS` / `ANZAHL_ABREINIGUNGEN` | count | #### Filter condition | Data | Field(s) | Unit | | --------------------- | --------------------------------------------------------------- | ---- | | Filter pressure | `PRESSURE_FILTER` / `FILTER_PRESSURE` | Pa | | Differential pressure | `DIFFERENTIAL_PRESSURE_FILTER` / `Differential_pressure_filter` | Pa | #### Motor and air flow | Data | Field(s) | Unit | | ----------------- | --------------------------------------------------- | ---- | | Volume flow | `VOLUMEFLOW` / `ACTUAL_VOLUMEFLOW` / `VOLUMENSTROM` | m³/h | | Motor power | `MOTORPOWER` / `MOTOR_ACTUAL_POWER` | kW | | Motor current | `MOTORCURRENT` / `MOTOR_CURRENT` | A | | Motor temperature | `TEMPERATURE_MOTOR` / `MOTOR_TEMPERATURE` | °C | | Motor frequency | `MOTOR_FREQUENCY` | Hz | #### Energy | Data | Field(s) | Unit | | ------------------ | -------------------- | ---- | | Energy consumption | `ENERGY_CONSUMPTION` | kWh | #### Noise | Data | Field(s) | Unit | | -------------------------------- | -------------- | ---- | | Loudness (A-weighted equivalent) | `LAEQ` | dB | | Instantaneous / max level | `LA` / `LAMAX` | dB | *** ## Device Types and Their Fields Each product exposes its own set of measurement fields. Use the device's `product.slug` to determine which fields to query. This section lists the fields available per product. ### AirWatch (air quality sensor) Variants: `airwatch-30`, `airwatch-lte-europe`, `kemper-airwatch-lte-america`. | Purpose | AirWatch LTE (Europe/America) | AirWatch 3.0 | | -------------------- | ----------------------------- | ------------------------ | | PM2.5 | `PM25_VALUE` | `pm25_value` | | PM10 | `PM10_VALUE` | `pm10_value` | | Particle bins | `BIN0_VALUE`–`BIN5_VALUE` | `bin0`–`bin5` | | Total particles | `NR_PARTICLES` | `binSum` | | PM10 alert threshold | `PM10_LIMIT_SET_VALUE` | `settings_pm10grenzwert` | | LED brightness | `LED_BRIGHTNESS_SET_VAL` | `settings_brightness` | | Signal strength | `SIGNAL_STRENGTH` | — | ### AirDome (air filtration tower) `MOTOR_RUNNING`, `MOTORCURRENT`, `MOTORPOWER`, `VOLUMEFLOW`, `MOTOR_RPM_AVG`, `PRESSURE_VOLUMEFLOW`, `PRESSURE_FILTER`, `TOTAL_PRESSURE`, `WARNING`, `MAINTENANCE_HOURS`, `OPERATING_HOURS`, `NR_FILTER_CLEANINGS`, `FEHLERCODE`, `TARGET_RPM`. ### Clean Air Tower (self-cleaning) `BETRIEBSSTUNDEN`, `BETRIEBSSTUNDEN_BIS_WARTUNG`, `ANZAHL_ABREINIGUNGEN`, `VOLUMENSTROM`, `ON_OFF`, `FEHLERCODE`, `SOFTWARESTAND`. ### Clean Air Tower (disposable filter) `BETRIEBSSTUNDEN`, `BETRIEBSSTUNDEN_BIS_WARTUNG`, `ACTUAL_VOLUMEFLOW`, `PRESSURE_VOLUME_FLOW`, `MOTOR_RUNNING`, `FAULT_CODE`, `TEMPERATURE_MOTOR`, `MOTOR_CURRENT`, `MOTOR_ACTUAL_POWER`, `MOTOR_FREQUENCY`, `BOOST_MODE_ACTIVE`, `DIFFERENTIAL_PRESSURE_FILTER`. ### VacuFil 125 `Betriebsstunden`, `Betriebsstunden_bis_wartung`, `cloud_signal_rssi`, `Anzahl_Abreinigungen`, `Differential_pressure_filter`, `actual_volumeflow`, `state_latest`, `fault_code`. ### Bridge-connected filters Reported through the KEMPER Connect Bridge (`DEVICE_TYPE` resolves the machine type). * **VacuFil Compact:** `MOTOR_RUNNING`, `FAULT`, `WARNING`, `FILTER_CLEANINGS`, `MAINTENANCE_HOURS`, `OPERATING_HOURS`, `SOFTWARE_VERSION`, `MOTOR_TEMPERATURE`, `VOLUMEFLOW_PRESSURE`. * **MaxiFil Clean:** `MOTOR_RUNNING`, `FAULT`, `WARNING`, `FILTER_PRESSURE`, `MAINTENANCE_HOURS`, `OPERATING_HOURS`, `NR_FILTERS_INSTALLED`, `VOLUMEFLOW_PRESSURE`. * **Automation Line:** `MOTOR_RUNNING`, `MOTOR_TEMPERATURE`, `FAULT`, `WARNING`, `FILTER_CLEANINGS`, `NR_FILTERS_INSTALLED`, `VOLUMEFLOW_PRESSURE`, `FILTER_PRESSURE_LIMIT`. ### KemJet / WeldFil / System 9000 Identified by `product.hardware = "dzero"`. Generic I/O pins with fixed wiring semantics: analog `AI_0` (filter pressure, Pa); temperatures `TC_0`–`TC_2` (motor/filter/room, °C); digital inputs `IN1_0`–`IN1_3` (contactor feedback, motor protection, external on/off, phase monitoring). ### Noise sensor (Milesight WS302) `LAEQ`, `LA`, `LAMAX`, `BATTERY`, `SIGNAL`. ### Energy meters Any device reporting `ENERGY_CONSUMPTION` (kWh). *** ## Remote Control The API supports remote control of filtration devices: start/stop, and (for some products) parameter changes. Commands are issued as GraphQL mutations. The mutation to use depends on the product. ### Control mutations by product | Product | Mutation | Purpose | | ----------------------------- | ---------------------- | ----------------------------------------------- | | KEMPER Connect Bridge | `sendApiDownlink` | Start/stop the bridged machine | | AirDome, AirWatch LTE | `sendParticleDownlink` | Downlink command | | Clean Air Tower, AirWatch 3.0 | `callProductFunction` | Predefined function (e.g. start/stop, identify) | | AirWatch LTE | `setValue` | Change a settable parameter | | AirWatch 3.0 | `sendAw3CommandFrame` | Change brightness / PM10 threshold | ### Start / stop Start and stop are performed by sending the product's corresponding downlink or function. For example, to start or stop a Bridge-connected machine: ```graphql mutation SendBridgeCommand($device: String!, $downlink: String!) { sendApiDownlink(device: $device, downlink: $downlink) { ok } } ``` For AirDome and Clean Air Tower devices, use the product's start/stop downlink/function identifiers. Contact KEMPER for the current downlink identifiers for your product, or read them from the device's function catalog exposed in the app. ### Parameter changes AirWatch LTE devices support setting parameters such as the PM10 alert threshold and LED brightness: ```graphql mutation SetValue( $deviceId: String! $fieldName: String! $value: MeasurementValueInput! ) { setValue(deviceId: $deviceId, fieldName: $fieldName, value: $value) { ok error { code details } } } ``` ### Which products support control? | Product | Start/Stop | Parameter changes | | ------------------------------- | :--------: | :----------------------------------: | | AirDome | Yes | — | | Clean Air Tower (self-cleaning) | Yes | — | | Clean Air Tower (disposable) | Yes | — | | KEMPER Connect Bridge | Yes | — | | AirWatch LTE (Europe/America) | — | Yes (`PM10_LIMIT`, `LED_BRIGHTNESS`) | | AirWatch 3.0 | — | Yes (brightness, PM10 threshold) | | Bridge-connected filters | Via Bridge | — | | AirWatch (sensor readings) | — | — | > Automation-driven control (for example, turning filters on when PM10 exceeds a threshold) is best implemented with rules rather than direct commands. See Automation and Rules. *** ## Automation and Rules KEMPER Connect includes a rules engine (Datacake **RuleNG**) that runs server-side. Rules can be read and managed through the API. Three rule patterns are used by KEMPER Connect: ### Time-based schedules Turn devices on or off on a cron schedule (for example, ventilation during shift hours). ### PM-threshold automation Automatically start a filtration device when a paired AirWatch sensor reports PM10 above a threshold, and stop it when it falls back below. Implemented as paired start/stop rules keyed on the sensor's PM10 field. ### Email notifications Send an email to configured recipients when PM10 exceeds a threshold (with hysteresis to avoid flapping). ### Reading and managing rules Rules belong to a workspace and are available through `rulesNG`: ```graphql query GetRules($workspaceId: String!) { workspace(id: $workspaceId) { rulesNG { id name enabled triggerOnSchedule scheduleTriggerCrontab } } } ``` Rules are created, updated, and deleted with the `createRuleNG`, `updateRuleNG`, and `deleteRuleNG` mutations. *** ## Events and Notifications ### Webhooks and real-time push Real-time push integrations are available as **advanced, paid add-ons** rather than through the standard GraphQL API: * **Outgoing webhooks** — measurement data pushed to your HTTPS endpoint as it arrives. * **MQTT live stream** — continuous real-time data via an MQTT broker. * **Rule-based webhooks** — webhooks fired from rules and alerts to drive third-party systems. These are enabled per customer together with Datacake. See Integration Options and contact KEMPER to request them. If you are using only the standard GraphQL API, use polling (below) to detect events. ### Email notifications The only built-in outbound notification channel is **email**, configured through threshold rules (see Automation and Rules). Emails can include templated device data such as the triggering device name and its current PM10 value. ### Detecting events by polling For system integrations that need to react to state changes (alarms, faults, threshold crossings, on/off transitions), poll the relevant `currentMeasurements` or `history` on a schedule and detect changes in your own system. Recommended polling intervals: | Data type | Suggested interval | | ----------------------------- | ------------------ | | Air quality / live telemetry | 1–5 minutes | | Status / faults | 1–5 minutes | | Operating hours / maintenance | Hourly or daily | | Historical backfill | On demand | Avoid polling faster than the device's own reporting interval; most devices report at a fixed cadence, so more frequent polling returns unchanged values. *** ## Example Requests and Responses ### Is there a Postman collection? There is no official Postman collection today. Because the API is standard GraphQL, you can import the schema into any GraphQL client via introspection (see Schema and introspection). The copy-paste examples below cover the most common tasks. ### List devices in a site Request: ```bash curl -X POST https://api.datacake.co/graphql/ \ -H "Authorization: Token YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "query": "query($ws:String!){ allDevices(inWorkspace:$ws){ id verboseName online product{ slug } } }", "variables": { "ws": "YOUR_WORKSPACE_ID" } }' ``` Response: ```json { "data": { "allDevices": [ { "id": "0a1b2c3d-1111-2222-3333-444455556666", "verboseName": "AirWatch Hall 1", "online": true, "product": { "slug": "airwatch-lte-europe" } } ] } } ``` ### Read current air quality Request: ```bash curl -X POST https://api.datacake.co/graphql/ \ -H "Authorization: Token YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "query": "query($id:String!){ device(deviceId:$id){ currentMeasurements(fieldNames:[\"PM10_VALUE\",\"PM25_VALUE\"]){ value field{ fieldName } } } }", "variables": { "id": "YOUR_DEVICE_ID" } }' ``` Response: ```json { "data": { "device": { "currentMeasurements": [ { "value": 42.5, "field": { "fieldName": "PM10_VALUE" } }, { "value": 18.0, "field": { "fieldName": "PM25_VALUE" } } ] } } } ``` ### Send a start command to a Bridge device Request: ```bash curl -X POST https://api.datacake.co/graphql/ \ -H "Authorization: Token YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "query": "mutation($d:String!,$dl:String!){ sendApiDownlink(device:$d, downlink:$dl){ ok } }", "variables": { "d": "YOUR_BRIDGE_DEVICE_ID", "dl": "START_DOWNLINK_ID" } }' ``` Response: ```json { "data": { "sendApiDownlink": { "ok": true } } } ``` *** ## Integrating with Third-Party Systems The GraphQL API is designed to be consumed by middleware and enterprise platforms. Below are integration patterns for common systems. ### SCADA, MES and PLC These systems typically cannot call GraphQL directly. Use a small **integration gateway** (a script or service) that: 1. Authenticates once with an API user token. 2. Polls `currentMeasurements` / `history` on a fixed cadence. 3. Maps KEMPER field names to your process tags. 4. Writes values into your SCADA/MES historian or PLC data table (for example via OPC UA, Modbus, or a REST bridge you control). For control, the gateway issues the relevant GraphQL mutation (start/stop, parameter change) in response to your system's commands. ```mermaid flowchart LR KConnect["KEMPER Connect GraphQL API"] Gateway["Integration Gateway (your side)"] OT["SCADA / MES / PLC"] KConnect -->|"poll telemetry"| Gateway Gateway -->|"process tags (OPC UA / Modbus)"| OT OT -->|"commands"| Gateway Gateway -->|"mutations"| KConnect ``` ### Power BI and BI tools Use a scheduled pull of the data you need: * **Power BI:** Use the *Web* connector (`Web.Contents`) to POST the GraphQL query with the `Authorization: Token` header, then parse the JSON response into a table. Configure scheduled refresh for periodic updates. For historical trending, query `history` over the desired range. * **Other BI tools:** Any tool that can perform an authenticated HTTP POST and parse JSON can consume the API. Prefer querying aggregated/history data on a schedule over high-frequency polling. ### General recommendations * Use a dedicated **API user token** per integration so it can be rotated or revoked independently. * Cache results and respect device reporting cadence; do not poll faster than the data changes. * Batch multiple devices/fields into a single query where possible to reduce request volume. * Build change detection (alarms, thresholds) in your own layer when using the GraphQL API, or request the outgoing webhook / MQTT add-ons for real-time push (see Integration Options). *** ## Limitations and Support ### Current limitations * **Standard interface is GraphQL**, there is and will be **NO separate REST API**. Real-time push (MQTT, outgoing webhooks, rule-based webhooks) is available as a paid add-on; see Integration Options. * **Tokens are provisioned by KEMPER.** API tokens cannot be created self-service in the portal. * **Control availability varies by product and security,** see Remote Control. * **Field names vary by product,** always resolve fields from the device `product.slug`. ### Support and access requests * To request a dedicated **API user** or **partner API** access, contact KEMPER. * To request advanced real-time integrations (MQTT live stream, outgoing webhooks, rule-based webhooks), contact KEMPER; these are offered as a paid API package set up together with Datacake. * Adapter scripts and integration starter code may be available on request. * For product-specific downlink identifiers used in control mutations, contact KEMPER or inspect the device's function catalog in the KEMPER Connect app. * Keep your API token secure and rotate it if you suspect exposure. # Terms of Service Terms of Service for KEMPER Connect Cloud ### General Terms and Conditions (GTC) – KEMPER Connect As of February 12, 2026 *** ## 1. Scope and Contracting Parties ### 1.1 Contracting Parties These General Terms and Conditions (hereinafter referred to as “GTC”) govern the contractual relationship between you (hereinafter referred to as “Customer,” “you,” or “User”) and **KEMPER GmbH** Von-Siemens-Str. 20, 48691 Vreden, Germany Managing Directors: Björn Kemper, Frederic Lanz (hereinafter referred to as “KEMPER Connect,” “we,” or “us”) regarding the use of the KEMPER Connect platform and all associated media forms, media channels, mobile websites, or mobile applications (collectively, the “Platform”). ### 1.2 Scope These Terms and Conditions apply to all contracts for the use of the Platform and the services offered through it. By accessing the Platform or registering, you confirm that you have read and understood these Terms and Conditions and agree to be bound by them. **Note for entrepreneurs:** The Platform is intended exclusively for entrepreneurs within the meaning of § 14 BGB (German Civil Code), i.e. natural or legal persons or partnerships with legal capacity who, when concluding the contract, are acting in the exercise of their commercial or independent professional activity. Use by consumers within the meaning of § 13 BGB is not intended. ### 1.3 Changes to the Terms and Conditions We reserve the right to change or supplement these Terms and Conditions at any time at our own discretion. We will inform you of any changes by updating the “Status” date of these Terms and Conditions. It is your responsibility to review these Terms and Conditions regularly to stay informed of any updates. By continuing to use the platform after the publication of amended Terms and Conditions, you agree to the changes. ### 1.4 Supplementary Terms and Conditions Supplementary terms and conditions or documents published on the platform from time to time are hereby expressly incorporated into these Terms and Conditions. In the event of a conflict between these Terms and Conditions and individually agreed terms and conditions, the latter shall prevail. *** ## 2. Subject matter of the contract and description of services ### 2.1 Platform and services KEMPER Connect is a cloud-based IoT (Internet of Things) platform that enables companies to connect IoT devices and visualize, store, and analyze data. The specific services depend on the selected tariff and the current service description on the platform. ### 2.2 Availability The platform is provided as Software-as-a-Service (SaaS). The specific availability commitments are set out in Section 6 (Service Level Agreement). ### 2.3 Further development We are entitled to further develop, modify, or discontinue the platform and its functions at any time, provided that this is reasonable for the customer and does not impair the essential purposes of the contract. *** ## 3. Registration and user account ### 3.1 Registration requirement Registration is required to use the platform. You agree to provide truthful, current, and complete information when registering and to update this information immediately in the event of any changes. ### 3.2 Account security You are responsible for keeping your access data confidential and are liable for all activities that take place under your account. If you suspect unauthorized use of your account, you are obliged to inform us immediately. ### 3.3 Usernames We reserve the right to remove, reclaim, or change usernames if we determine, at our sole discretion, that a username is inappropriate, offensive, or otherwise unacceptable. ### 3.4 Minimum age The platform is intended for users who are at least 18 years of age. Persons under the age of 18 are not permitted to use or register on the platform. *** ## 4. Contract term and termination ### 4.1 Contract term The contract term is determined by the selected tariff or individual agreement. ### 4.2 Termination by the customer You can terminate your access at any time by logging into your account or contacting us using the contact details provided below. The termination will take effect at the end of the current contract term. ### 4.3 Termination by KEMPER Connect We reserve the right to deny, restrict, or terminate your access to the platform without prior notice and at our sole discretion, in particular in the event of violations of these Terms and Conditions or applicable law. We may terminate or delete your account and any content or information you have posted at any time and without warning at our sole discretion. ### 4.4 Consequences of termination After termination or cancellation of your account, you are prohibited from re-registering under your name, a false or borrowed name, or the name of a third party , even if you may be acting on behalf of the third party. ### 4.5 Complaints If you are dissatisfied with our services, please contact us at or by phone at +49 (0) 2564 68 0. *** ## 5. Licenses and voucher system ### 5.1 License requirement A valid license is required to use the platform for registered devices. Licenses are activated via a voucher system. ### 5.2 Trial licenses for new customers When you register a new device on the platform for the first time, you will receive a free trial license valid for **six (6) months**. The trial license allows full use of all platform functions for the registered device during the trial period. ### 5.3 Trial licenses for migration customers Customers migrating from an older version of the platform to KEMPER Connect will receive a trial license with a term of **sixty (60) days**. This migration period begins at the time of migration of the respective device. ### 5.4 Voucher system After the trial license expires, voucher codes must be purchased in order to continue using the platform: 1. **Purchase:** Vouchers can be purchased directly from KEMPER GmbH or through authorized sales partners. 2. **Redemption:** Voucher codes are entered via the platform and activate the corresponding license for the respective device. 3. **Validity:** The term and scope of the license activated by a voucher depend on the respective voucher type. ### 5.5 Expiration of the license After a trial license or a license activated by a voucher expires without renewal: * Access to the affected device and its data may be restricted or deactivated. * Stored data will be treated in accordance with our privacy policy. * Reactivation is possible at any time by entering a valid voucher code. ### 5.6 No refund Voucher codes are non-refundable after purchase. Unredeemed voucher codes remain usable in accordance with their specified period of validity. *** ## 6. Service Level Agreement (SLA) ### 6.1 Availability KEMPER Connect aims for a monthly platform availability of **99.5%**. Availability is calculated as follows: **Availability (%) = ((Total minutes in the month - Downtime minutes) / Total minutes in the month) × 100** ### 6.2 Exceptions The following times are not taken into account when calculating availability: * **Scheduled maintenance windows:** Maintenance work is announced in advance whenever possible and carried out outside normal business hours. * **Force majeure:** Events beyond our reasonable control (e.g., natural disasters, war, acts of terrorism, power outages, Internet outages caused by third-party providers) . * **Customer-caused outages:** Outages caused by the customer or their end users. * **Third-party services:** Outages of third-party services over which we have no control. ### 6.3 Outage notification In the event of planned maintenance work or known disruptions, we will inform you via the platform, by email, or via our status page, if possible. ### 6.4 Support Support requests can be made via the platform, by email to , or via our live chat. We endeavor to process requests promptly. ### 6.5 No guarantee The SLA represents a target. Failure to meet the targeted availability does not entitle you to compensation, reduction, or credit, unless this has been agreed separately. *** ## 7. Rights of Use and Licenses ### 7.1 Ownership of the Platform Unless otherwise specified, the platform and all content contained therein, including source code, databases, functions, software, website designs, audio, video, text, photos, and graphics (collectively, the “Content”), as well as the trademarks, service marks, and logos contained therein (the “Trademarks”) are our property or are under our control and are protected by copyrights, trademark rights, and various other industrial property rights. ## # 7.2 Limited License Provided that you are authorized to use the Platform, you are granted a limited license to access and use the Platform and to download or print a copy of any portion of the Content to which you have properly gained access, solely for your business purposes. ### 7.3 Reserved Rights We reserve all rights not expressly granted to you in relation to the Platform, the Content, and the Trademarks. No part of the Platform, the Content, or the Trademarks may be copied, reproduced, aggregated, republished, uploaded, posted, publicly displayed, encoded, translated, transmitted, distributed, sold, licensed, or otherwise used for commercial purposes. *** ## 8. User Obligations / Prohibited Activities ### 8.1 General Obligations As a user of the Platform, you represent and warrant that: 1. All registration information you submit is true, accurate, current, and complete. 2. You will maintain the accuracy of this information and update it promptly as necessary. 3. You have the legal capacity to enter into this agreement and agree to comply with these Terms and Conditions. 4. You will not use the Platform for any illegal or unauthorized purpose. 5. Your use of the Platform does not violate any applicable laws or regulations. ### 8.2 Prohibited Activities You may not use the platform for any purpose other than those intended by us. In particular, it is prohibited to: 1. Systematically retrieve data or other content from the platform to directly or indirectly create a collection, compilation, database, or directory without our written permission. 2. Use the platform without authorization, including collecting user names and/or email addresses from users by electronic or other means for the purpose of sending unsolicited emails. 3. Bypass, disable, or otherwise interfere with security-related features of the platform. 4. Disrupt, interrupt, or impose an unreasonable or disproportionately large load on the platform or the networks or services connected to it. 5. Attempt to impersonate another user or person. 6. Sell or otherwise transfer your profile. 7. Decrypt, decompile, disassemble, or reverse engineer any software comprising or in any way part of the platform. 8. Upload or transmit viruses, Trojan horses, or other material that interferes with the uninterrupted use of the platform by third parties. 9. Use automated systems, including spiders, robots, scrapers, or offline readers, to access the platform. 10. Use the platform in a manner that is inconsistent with applicable laws or regulations. *** ## 9. User Content and Contributions ### 9.1 Responsibility for Content You may be given the opportunity to create, submit, post, display, transmit, publish, or distribute content and materials on the Platform (collectively, “Contributions”). You are solely responsible for your Contributions. ### 9.2 Representations Regarding Contributions When you create or make available any Contributions, you represent and warrant that: 1. The creation, distribution, transmission, public display or performance, and access, downloading or copying of your Contributions does not infringe the proprietary rights of any third party, including copyrights, patents, trademarks, trade secrets or personality rights. 2. You are the creator and owner of your Contributions or have the necessary licenses, rights, consents, and permissions to use your Contributions. 3. Your Contributions are not false, inaccurate, or misleading. 4. Your Contributions do not constitute unsolicited or unauthorized advertising. 5. Your contributions do not violate applicable law. ### 9.3 License to Contributions We do not claim ownership of your contributions. You retain full ownership of all your contributions and all associated intellectual property rights. We are not liable for any statements or representations in your contributions. ### 9.4 Feedback By submitting suggestions or other feedback regarding the platform, you agree that we may use and share this feedback for any purpose without compensation to you. *** ## 10. Order processing (AVV) ### 10.1 Customer Processing If, as a customer, you transfer personal data of your end customers, employees, or other data subjects to the platform, you are generally the controller within the meaning of the GDPR. KEMPER Connect processes this data as a processor. ### 10.2 Data Processing Agreement For the processing of personal data on behalf of the customer, we conclude a separate Data Processing Agreement (DPA) in accordance with Art. 28 GDPR. The DPA is available on request at or can be accessed via the platform. ### 10.3 Obligations of the customer As the controller, you are responsible for ensuring that the processing of personal data via the platform is carried out in accordance with the applicable data protection laws, in particular that you have a suitable legal basis for the processing and that you inform the data subjects accordingly. *** ## 11. AI-supported functions ### 11.1 Use of AI services The platform may contain AI-supported features provided by third-party providers such as OpenAI and Anthropic. These features may include, for example, text generation, intelligent assistants, or data analysis. ### 11.2 No warranty We do not guarantee the accuracy, completeness, or suitability of AI-generated content. AI-generated results may contain errors and should be checked before use. ### 11.3 User responsibility You remain responsible for the use and further processing of AI-generated content. The use of AI functions is at your own risk. ### 11.4 Data protection Information on the processing of data by AI services can be found in our privacy policy. *** ## 12. Mobile applications ### 12.1 License of use If you access the platform via a mobile application, we grant you a revocable, non-exclusive, non-transferable, limited right to install and use the mobile application on wireless electronic devices owned or controlled by you, and to access and use the mobile application on those devices, strictly in accordance with the terms of this license agreement. ### 12.2 Restrictions You may not: 1. Decompile, reverse engineer, disassemble, or attempt to derive the source code of the application. 2. Create modifications, adaptations, improvements, or derivative works from the application. 3. Use the application for revenue-generating ventures or commercial purposes for which it is not designed or intended. 4. Make the application available over a network or other environment that allows access or use by multiple devices or users simultaneously. 5. Use the Application to create a product, service, or software that directly or indirectly competes with the Application. ### 12.3 Apple and Android Devices The following terms apply if you use a mobile application from the Apple Store or Google Play (each, an “App Distributor”): The license granted to you for our mobile application is limited to a non-transferable license to use the application on a device that uses the Apple iOS or Android operating system and in accordance with the usage rules set forth in the terms of use of the respective App Distributor. *** ## 13. Third-Party Content and Links ### 13.1 Links to Third-Party Websites The Platform may contain links to other websites (“Third-Party Websites”) as well as articles, photos, text, graphics, images, designs, music, sound, video, information, applications, software, and other content or elements originating from third parties (“Third-Party Content”). ### 13.2 No Responsibility We do not investigate, monitor, or review such third-party websites and third-party content for accuracy, appropriateness, or completeness, and we are not responsible for third-party websites accessed through the platform or for third-party content posted, available or installed on the Platform. ### 13.3 User Risk The inclusion of, linking to, or permitting the use or installation of third-party websites or third-party content does not imply endorsement or approval by us. If you decide to leave the Platform and access third-party websites or use or install third-party content, you do so at your own risk. *** ## 14. Data protection ### 14.1 Privacy policy We attach great importance to data protection and data security. Please read our privacy policy. By using the platform, you agree to our privacy policy, which is part of these Terms and Conditions. ### 14.2 Hosting location The platform is hosted in Germany. If you access the platform from another region of the world, your continued use of the platform constitutes your consent to the transfer of your data to Germany and its processing there. *** ## 15. Warranty and limitation of liability ### 15.1 Provision “as is” The platform is provided on an “as is” and “as available” basis. You agree that your use of the platform and our services is at your sole risk. ### 15.2 Limitation of liability To the extent permitted by law, we shall only be liable without limitation for damages resulting from intentional or grossly negligent breach of duty by us, our legal representatives, or vicarious agents, as well as for damages resulting from injury to life, limb, or health. In the event of a slightly negligent breach of essential contractual obligations (cardinal obligations), our liability shall be limited to the damage typical for the contract and foreseeable at the time of conclusion of the contract. Essential contractual obligations are those whose fulfillment is essential for the proper execution of the contract and on whose compliance the contractual partner may regularly rely. Otherwise, liability for slight negligence is excluded. ### 15.3 Maximum liability limit Notwithstanding the above provisions, our liability for all claims arising from a contractual relationship is limited to the amount of remuneration paid to us by you in the last twelve (12) months prior to the event causing the damage, but at least to an amount of EUR 1,000. ### 15.4 No guarantee for third-party content We do not assume any warranty, endorsement, or responsibility for products or services advertised or offered by third parties via the platform. *** ## 16. Indemnification You agree to indemnify and hold us, our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees harmless from and against any and all losses, damages, liabilities, claims, or demands, including reasonable attorneys' fees and expenses, made by any third party due to or arising out of: 1. Your use of the Platform; 2. Any breach of these Terms and Conditions; 3. Any breach of your representations and warranties under these Terms and Conditions; 4. Your infringement of the rights of third parties, including intellectual property rights; or 5. Any manifestly harmful act towards other users of the Platform. Notwithstanding the foregoing, we reserve the right to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate with our defense of such claim at your expense. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you must indemnify us, and you agree to cooperate at your expense in our defense of such claims. *** ## 17. Changes to the Terms and Conditions We reserve the right to change, modify, or remove the content of the platform at any time and without notice at our sole discretion. However, we are not obligated to update information on our platform. We also reserve the right to change or discontinue the platform in whole or in part without notice. We shall not be liable to you or any third party for any changes, price changes, suspensions, or discontinuations of the platform. *** ## 18. Applicable Law and Jurisdiction ### 18.1 Applicable law These Terms and Conditions are subject to the laws of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). ### 18.2 Place of jurisdiction If you are an entrepreneur, the exclusive place of jurisdiction for all disputes arising from or in connection with these Terms and Conditions is the registered office of KEMPER GmbH (Vreden, Germany). ### 18.3 EU consumers If you have your habitual residence in the EU and are a consumer, you also enjoy the protection of the mandatory provisions of the law of your country of residence. KEMPER GmbH and you agree to submit to the non-exclusive jurisdiction of the courts in North Rhine-Westphalia -Westfalen, which means that you can assert your consumer rights in Germany or in the EU country in which you reside. ### 18.4 Online dispute resolution The European Commission provides a platform for online dispute resolution, which you can access here: . If you would like to bring this issue to our attention, please contact us. *** ## 19. Additional provisions for US users The following provisions apply additionally to users who are located in the United States of America or access the platform from there. ### 19.1 Industry-specific regulations The platform is not designed to comply with industry-specific regulations, including the Health Insurance Portability and Accountability Act (HIPAA), the Federal Information Security Management Act (FISMA), or others. If your interactions would be subject to such laws, you may not use this platform. You may not use the platform in a manner that would violate the Gramm-Leach-Bliley Act (GLBA). ### 19.2 U.S. Government Rights Our Services are “commercial items” as defined in Federal Acquisition Regulation (“FAR”) 2.101. If our Services are purchased by or on behalf of a government agency outside the Department of Defense, our Services are subject to the terms and conditions of these Terms and Conditions pursuant to FAR 12.212 (for computer software) and FAR 12.211 (for technical data). If our Services are purchased by or on behalf of a government agency within the Department of Defense, our Services are subject to the terms and conditions of these Terms and Conditions pursuant to Defense Federal Acquisition Regulation (“DFARS”) 227.7202-3. ### 19.3 California Users and Residents If a complaint is not satisfactorily resolved by us, you may write to the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs at 1625 North Market Blvd. , Suite N 112, Sacramento, California 95834, or by phone at (800) 952-5210 or (916) 445-1254. *** ## 20. Final Provisions ### 20.1 Entire Agreement These Terms and Conditions and any policies or operating rules posted by us on the Platform or in respect to the Platform constitute the entire agreement and understanding between you and us. ### 20.2 Waiver Our failure to exercise or enforce any right or provision of these Terms and Conditions shall not constitute a waiver of such right or provision. ### 20.3 Assignment We may assign our rights and obligations, in whole or in part, to any third party at any time. ### 20.4 Force Majeure We are not responsible or liable for any loss, damage, delay, or failure caused by causes beyond our reasonable control. ### 20.5 Severability If any provision or part of a provision of these Terms and Conditions is found to be unlawful, void, or unenforceable, that provision or part of the provision shall be deemed severable from these Terms and Conditions and shall not affect the validity and enforceability of the remaining provisions. ### 20.6 No joint venture These Terms and Conditions or the use of the Platform do not create a joint venture, partnership, employment, or agency relationship between you and us. ### 20.7 Written form Amendments and additions to these Terms and Conditions must be made in writing to be effective. This also applies to the waiver of this written form requirement. ### 20.8 Electronic communication Visiting the platform, sending emails to us, and filling out online forms constitute electronic communication. You agree to receive electronic communications and you agree that all agreements, notices, disclosures, and other communications that we provide to you electronically via email and on the platform satisfy all legal requirements. *** ## 21. Contact If you have any questions about these Terms and Conditions or the platform, please contact us at: **KEMPER GmbH** Von-Siemens-Str. 20 48691 Vreden Germany Phone: +49 (0) 2564 68 0 Email: *** \#22. User Data We will store certain data that you submit to the platform for the purpose of managing the performance of the platform, as well as data about your use of the platform. Although we perform regular routine backups of data, you are solely responsible for any data you submit or that relates to activities you have undertaken using the platform. You agree that we are not liable to you for any loss or damage to such data, and you hereby waive any right of action against us arising from any such loss or damage to such data. *** ## 23. Administration of the platform We reserve the right, but are not obligated, to monitor the Platform for violations of these Terms and Conditions and to take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms and Conditions, including, but not limited to, reporting such user to law enforcement authorities. We also reserve the right, at our sole discretion and without limitation, notice, or liability: * Deny, restrict, or block access to the platform for certain users * Remove any files and content that are excessively large or burden our systems in any way * Otherwise manage the platform in a manner that protects our rights and property and the proper functioning of the platform *** ## 24. Corrections There may be information on the platform that contains typographical errors, inaccuracies, or omissions, including descriptions, availability, and various other information. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the platform at any time without prior notice. ### General Terms and Conditions (GTC) – KEMPER Connect As of February 12, 2026 *** ## 1. Scope and Contracting Parties ### 1.1 Contracting Parties These General Terms and Conditions (hereinafter “GTC”) govern the contractual relationship between you (hereinafter “Customer,” “you,” or “User”) and **KEMPER GmbH** Von-Siemens-Str. 20, 48691 Vreden, Germany Managing Directors: Björn Kemper, Frederic Lanz (hereinafter referred to as “KEMPER Connect,” “we,” or ‘us’) regarding the use of the KEMPER Connect platform and all associated media forms, media channels, mobile websites, or mobile applications (collectively referred to as the “Platform”). ### 1.2 Scope These Terms and Conditions apply to all contracts for the use of the Platform and the services offered through it. By accessing the Platform or registering, you confirm that you have read and understood these Terms and Conditions and agree to be bound by them. **Note for entrepreneurs:** The Platform is intended exclusively for entrepreneurs within the meaning of § 14 BGB (German Civil Code), i.e., natural or legal persons or partnerships with legal capacity who, when concluding the contract, are acting in the exercise of their commercial or independent professional activity. Use by consumers within the meaning of § 13 BGB is not intended. ### 1.3 Changes to the Terms and Conditions We reserve the right to change or supplement these Terms and Conditions at any time at our own discretion. We will inform you of any changes by updating the “Status” date of these Terms and Conditions. It is your responsibility to review these Terms and Conditions regularly to stay informed of any updates. By continuing to use the platform after the publication of amended Terms and Conditions, you agree to the changes. ### 1.4 Supplementary Terms and Conditions Supplementary terms and conditions or documents published on the platform from time to time are hereby expressly incorporated into these Terms and Conditions. In the event of a conflict between these Terms and Conditions and individually agreed terms and conditions, the latter shall prevail. *** ## 2. Subject Matter of the Contract and Description of Services ### 2.1 Platform and Services KEMPER Connect is a cloud-based IoT (Internet of Things) platform that enables companies to connect IoT devices and visualize, store, and analyze data. The specific services depend on the selected tariff and the current service description on the platform. ### 2.2 Availability The platform is provided as Software-as-a-Service (SaaS). The specific availability commitments are set out in Section 6 (Service Level Agreement). ### 2.3 Further development We are entitled to further develop, change, or discontinue the platform and its functions at any time, provided this is reasonable for the customer and does not impair the essential purposes of the contract. *** ## 3. Registration and user account ### 3.1 Registration requirement Registration is required to use the platform. You agree to provide truthful, current, and complete information when registering and to update this information immediately in the event of any changes. ### 3.2 Account security You are responsible for keeping your access data confidential and are liable for all activities that take place under your account. If you suspect unauthorized use of your account, you are obliged to inform us immediately. ### 3.3 Usernames We reserve the right to remove, reclaim, or change usernames if we determine, at our sole discretion, that a username is inappropriate, offensive, or otherwise unacceptable. ### 3.4 Minimum age The platform is intended for users who are at least 18 years old. Persons under the age of 18 are not permitted to use or register on the platform. *** ## 4. Contract term and termination ### 4.1 Contract term The contract term is determined by the selected tariff or individual agreement. ### 4.2 Termination by the customer You can terminate your access at any time by logging into your account or contacting us using the contact details provided below. The termination will take effect at the end of the current contract term. ### 4.3 Termination by KEMPER Connect We reserve the right to deny, restrict, or terminate your access to the platform without prior notice and at our sole discretion, in particular in the event of violations of these Terms and Conditions or applicable law. We may terminate or delete your account and any content or information you have posted at any time and without warning at our sole discretion. ### 4.4 Consequences of termination After termination or cancellation of your account, you are prohibited from re-registering under your name, a false or borrowed name, or the name of a third party, even if you may be acting on behalf of the third party. ### 4.5 Complaints If you are dissatisfied with our services, please contact us at or by phone at +49 (0) 2564 68 0. *** ## 5. Licenses and voucher system ### 5.1 License requirement A valid license is required to use the platform for registered devices. Licenses are activated via a voucher system. ### 5.2 Trial licenses for new customers When you register a new device on the platform for the first time, you will receive a free trial license valid for **six (6) months**. The trial license allows full use of all platform functions for the registered device during the trial period. ### 5.3 Trial licenses for migration customers Customers migrating from an older version of the platform to KEMPER Connect receive a trial license with a term of **sixty (60) days**. This migration period begins at the time of migration of the respective device. ### 5.4 Voucher system After the trial license expires, voucher codes must be purchased in order to continue using the platform: 1. **Purchase:** Vouchers can be purchased directly from KEMPER GmbH or through authorized sales partners. 2. **Redemption:** Voucher codes are entered via the platform and activate the corresponding license for the respective device. 3. **Validity:** The term and scope of the license activated by a voucher depend on the respective voucher type. ### 5.5 Expiration of the license After a trial license or a license activated by a voucher has expired without renewal: * Access to the affected device and its data may be restricted or deactivated. * Stored data will be treated in accordance with our privacy policy. * Reactivation is possible at any time by entering a valid voucher code. ### 5.6 No refund Voucher codes are non-refundable after purchase. Unredeemed voucher codes remain usable in accordance with their specified validity period. *** ## 6. Service Level Agreement (SLA) ### 6.1 Availability KEMPER Connect aims for a monthly platform availability of **99.5%**. Availability is calculated as follows: **Availability (%) = ((Total minutes in the month - Downtime minutes) / Total minutes in the month) × 100** ### 6.2 Exceptions The following times are not taken into account when calculating availability: * **Scheduled maintenance windows:** Maintenance work is announced in advance whenever possible and carried out outside normal business hours. * **Force majeure:** Events beyond our reasonable control (e.g., natural disasters, war, acts of terrorism, power outages, Internet outages caused by third-party providers). * **Customer-caused outages:** Outages caused by the customer or its end users. * **Third-party services:** Outages of third-party services over which we have no control. ### 6.3 Outage notification In the event of planned maintenance work or known outages, we will inform you via the platform, by email, or via our status page, if possible. ### 6.4 Support Support requests can be made via the platform, by email to , or via our live chat. We endeavor to process requests promptly. ### 6.5 No guarantee The SLA represents a target. Failure to meet the targeted availability does not entitle you to compensation, reduction, or credit, unless this has been agreed separately. *** ## 7. Rights of use and licenses ### 7.1 Ownership of the Platform Unless otherwise stated, the Platform and all content contained therein, including source code, databases, functions, software, website designs, audio, video, text, photos, and graphics (collectively, the “Content”), as well as the trademarks, service marks, and logos contained therein (the “Trademarks”) are our property or are under our control and are protected by copyrights, trademark rights, and various other industrial property rights. ### 7.2 Limited License Provided that you are authorized to use the Platform, you are granted a limited license to access and use the Platform and to download or print a copy of any portion of the Content to which you have properly gained access, solely for your business purposes. ### 7.3 Reserved Rights We reserve all rights not expressly granted to you in relation to the Platform, the Content, and the Trademarks. No part of the Platform, Content, or Trademarks may be copied, reproduced, aggregated, republished, uploaded, posted, publicly displayed, encoded, translated, transmitted, distributed, sold, licensed, or otherwise exploited for any commercial purpose without our express prior written permission. *** ## 8. User Obligations / Prohibited Activities ### 8.1 General Obligations As a user of the Platform, you represent and warrant that: 1. All registration information you submit is true, accurate, current, and complete. 2. You will maintain the accuracy of this information and update it promptly as necessary. 3. You have the legal capacity to enter into a contract and agree to comply with these Terms and Conditions. 4. You will not use the platform for any illegal or unauthorized purpose. 5. Your use of the platform does not violate with any applicable law or regulation. ### 8.2 Prohibited Activities You may not use the platform for any purpose other than those intended by us. In particular, it is prohibited to: 1. Systematically retrieve data or other content from the platform to directly or indirectly create a collection, compilation, database, or directory without our written permission. 2. Use the platform without authorization, including collecting user names and/or email addresses from users by electronic or other means for the purpose of sending unsolicited emails. 3. Bypass, disable, or otherwise interfere with security-related features of the platform. 4. Disrupt, interrupt, or impose an unreasonable or disproportionately large load on the platform or the networks or services connected to it. 5. Attempt to impersonate another user or person. 6. Sell or otherwise transfer your profile. 7. Decrypt, decompile, disassemble, or reverse engineer any software comprising or in any way part of the platform. 8. Upload or transmit any viruses, Trojan horses, or other material that interferes with the uninterrupted use of the platform by third parties. 9. Use automated systems, including spiders, robots, scrapers, or offline readers, to access the platform. 10. Use the platform in a manner that is inconsistent with applicable laws or regulations. *** ## 9. User Content and Contributions ### 9.1 Responsibility for Content You may be given the opportunity to create, submit, post, display, transmit, publish, or distribute content and materials on the platform (collectively, “Contributions”). You are solely responsible for your Contributions. ### 9.2 Representations Regarding Contributions When you create or make available Contributions, you represent and warrant that: 1. The creation, distribution, transmission, public display or performance, and access, downloading or copying of your Contributions does not violate the proprietary rights of any third party, including copyrights, patents, trademarks, trade secrets or personality rights. 2. You are the creator and owner of your Contributions or have the necessary licenses, rights, consents, and permissions to use your Contributions. 3. Your Contributions are not false, inaccurate, or misleading. 4. Your Contributions do not constitute unsolicited or unauthorized advertising. 5. Your contributions do not violate applicable law. ### 9.3 License to Contributions We do not claim ownership of your contributions. You retain full ownership of all your contributions and all associated intellectual property rights. We are not liable for any statements or representations in your contributions. ### 9.4 Feedback By submitting suggestions or other feedback regarding the platform, you agree that we may use and share this feedback for any purpose without compensation to you. *** ## 10. Order processing (AVV) ### 10.1 Customer processing If, as a customer, you transfer personal data of your end customers, employees, or other affected persons to the platform, you are generally the controller within the meaning of the GDPR. KEMPER Connect processes this data as a processor. ### 10.2 Data Processing Agreement For the processing of personal data on behalf of the customer, we conclude a separate Data Processing Agreement (DPA) in accordance with Art. 28 GDPR. The DPA is available on request at or can be accessed via the platform. ### 10.3 Obligations of the customer As the controller, you are responsible for ensuring that the processing of personal data via the platform is carried out in accordance with the applicable data protection laws, in particular that you have a suitable legal basis for the processing and that you inform the data subjects accordingly. *** ## 11. AI-supported functions ### 11.1 Use of AI services The platform may contain AI-supported functions provided by third-party providers such as OpenAI and Anthropic. These functions may include, for example, text generation, intelligent assistants, or data analysis. ### 11.2 No warranty We do not guarantee the accuracy, completeness, or suitability of AI-generated content. AI-generated results may contain errors and should be checked before use. ### 11.3 User responsibility You remain responsible for the use and further processing of AI-generated content. The use of AI features is at your own risk. ### 11.4 Data protection Information on the processing of data by AI services can be found in our privacy policy. *** ## 12. Mobile applications ### 12.1 License of use If you access the platform via a mobile application, we grant you a revocable, non-exclusive, non-transferable, limited right to install and use the mobile application on wireless electronic devices owned or controlled by you, and to access and use the mobile application on those devices, strictly in accordance with the terms of this license agreement. ### 12.2 Restrictions You may not: 1. Decompile, reverse engineer, disassemble, or attempt to derive the source code of the application. 2. Create modifications, adaptations, improvements, or derivative works based on the application. 3. Use the application for revenue-generating ventures or commercial purposes for which it is not designed or intended. 4. Make the application available via a network or other environment that allows access or use by multiple devices or users simultaneously. 5. Use the application to create a product, service, or software that directly or indirectly competes with the application. ### 12.3 Apple and Android devices The following terms apply if you use a mobile application from the Apple Store or Google Play (each an “App Distributor”): The license granted to you for our mobile application is limited to a non-transferable license to use the application on a device that uses the Apple iOS or Android operating system and in accordance with the rules of use set forth in the terms of use of the respective App Distributor. distributor. *** ## 13. Third-Party Content and Links ### 13.1 Links to Third-Party Websites The Platform may contain links to other websites (“Third-Party Websites”) as well as articles, photos, text, graphics, images, designs, music, sound, video, information, applications, software, and other content or elements originating from third parties (“Third-Party Content”). ### 13.2 No Responsibility We do not investigate, monitor, or review such third-party websites and third-party content for accuracy, appropriateness, or completeness, and we are not responsible for third-party websites accessed through the platform or for third-party content posted, available, or installed on the platform. ### 13.3 User Risk The inclusion of, linking to, or permitting the use or installation of third-party websites or third-party content does not imply our endorsement or approval. If you decide to leave the Platform and access third-party websites or use or install third-party content, you do so at your own risk. *** ## 14. Data protection ### 14.1 Privacy policy We attach great importance to data protection and data security. Please read our privacy policy. By using the platform, you agree to our privacy policy, which is part of these Terms and Conditions. ### 14.2 Hosting Location The platform is hosted in Germany. If you access the platform from another region of the world, your continued use of the platform constitutes your consent to the transfer of your data to Germany and its processing there. *** ## 15. Warranty and Limitation of Liability ### 15.1 Provision “as is” The platform is provided on an “as is” and “as available” basis. You agree that your use of the platform and our services is at your sole risk. ### 15.2 Limitation of Liability To the extent permitted by law, we shall only be liable without limitation for damages resulting from an intentional or grossly negligent breach of duty by us, our legal representatives, or vicarious agents, as well as for damages resulting from injury to life, limb, or health. In the event of a slightly negligent breach of essential contractual obligations (cardinal obligations), our liability shall be limited to the damage typical for the contract and foreseeable at the time of conclusion of the contract. Essential contractual obligations are those whose fulfillment is essential for the proper execution of the contract and on whose compliance the contractual partner may regularly rely. Otherwise, liability for slight negligence is excluded. ### 15.3 Maximum liability limit Notwithstanding the above provisions, our liability for all claims arising from a contractual relationship is limited to the amount of remuneration paid to us by you in the last twelve (12) months prior to the event causing the damage, but at least to an amount of EUR 1,000. ### 15.4 No guarantee for third-party content We do not assume any warranty, endorsement, or responsibility for products or services advertised or offered by third parties via the platform. *** ## 16. Indemnification You agree to indemnify and hold us, our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees harmless from and against any and all losses, damages, liabilities, claims, or demands, including reasonable attorneys' fees and expenses, made by any third party due to or arising out of: 1. Your use of the Platform; 2. Any breach of these Terms and Conditions; 3. Any breach of your representations and warranties under these Terms and Conditions; 4. Your infringement of the rights of third parties, including intellectual property rights; or 5. Any manifestly harmful act towards other users of the Platform . Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you must indemnify us, and you agree to cooperate at your expense in our defense of such claims. *** ## 17. Changes to the Terms and Conditions We reserve the right to change, modify, or remove the content of the platform at any time and without notice at our sole discretion. However, we are not obligated to update information on our platform. We also reserve the right to change or discontinue the platform in whole or in part without notice. We are not liable to you or any third party for any changes, price changes, suspensions, or discontinuations of the platform. *** ## 18. Applicable law and place of jurisdiction ### 18.1 Applicable law These Terms and Conditions are subject to the laws of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). ### 18.2 Place of jurisdiction If you are an entrepreneur, the exclusive place of jurisdiction for all disputes arising from or in connection with these GTC is the registered office of KEMPER GmbH (Vreden, Germany). ### 18.3 EU consumers If you have your habitual residence in the EU and are a consumer, you also enjoy the protection of the mandatory provisions of the law of your country of residence. KEMPER GmbH and you agree to submit to the non-exclusive jurisdiction of the courts in North Rhine-Westphalia, which means that you can assert your consumer rights in Germany or in the EU country in which you reside. ### 18.4 Online dispute resolution The European Commission provides a platform for online dispute resolution, which you can access here: . If you would like to bring this issue to our attention, please contact us. *** ## 19. Additional provisions for US users The following provisions apply additionally to users who are located in the United States of America or who access the platform from there. ### 19.1 Industry-specific regulations The platform is not designed to comply with industry-specific regulations, including the Health Insurance Portability and Accountability Act (HIPAA), the Federal Information Security Management Act (FISMA), or others. If your interactions would be subject to such laws, you may not use this platform. You may not use the platform in any manner that would violate the Gramm-Leach-Bliley Act (GLBA). ### 19.2 Rights of the US Government Our Services are “commercial items” as that term is used in the Federal Acquisition Regulation (“FAR”) 2.101. If our Services are purchased by or on behalf of a government agency outside the Department of Defense, our Services are subject to the terms and conditions of these Terms of Service pursuant to FAR 12.212 (for computer software) and FAR 12.211 (for technical data). If our Services are purchased by or on behalf of a government agency within the Department of Defense, our Services are subject to the terms and conditions of these Terms and Conditions pursuant to Defense Federal Acquisition Regulation (“DFARS”) 227.7202-3. ### 19.3 California Users and Residents If a complaint is not satisfactorily resolved with us, you may contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254. *** ## 20. Final Provisions ### 20.1 Entire Agreement These Terms and Conditions and any policies or operating rules posted by us on the Platform or in relation to the Platform constitute the entire agreement and understanding between you and us. ### 20.2 Waiver Our failure to exercise or enforce any right or provision of these Terms and Conditions shall not constitute a waiver of such right or provision. ### 20.3 Assignment We may assign our rights and obligations in whole or in part to any third party at any time. ### 20.4 Force Majeure We are not responsible or liable for any loss, damage, delay, or failure caused by causes beyond our reasonable control. ### 20.5 Severability If any provision or part of a provision of these Terms and Conditions is found to be unlawful, void, or unenforceable, that provision or part of the provision shall be deemed severable from these Terms and Conditions and shall not affect the validity and enforceability of the remaining provisions. ### 20.6 No joint venture These Terms and Conditions or the use of the Platform do not create a joint venture, partnership, employment, or agency relationship between you and us. ### 20.7 Written form Amendments and additions to these Terms and Conditions must be made in writing to be effective. This also applies to the waiver of this written form requirement. ### 20.8 Electronic Communication Visiting the platform, sending emails to us, and filling out online forms constitute electronic communication. You agree to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications that we provide to you electronically via email and on the platform satisfy all legal requirements. *** ## 21. Contact If you have any questions about these Terms and Conditions or the platform, please contact us at: **KEMPER GmbH** Von-Siemens-Str. 20 48691 Vreden Germany Phone: +49 (0) 2564 68 0 Email: *** ## 22. User Data We will retain certain data that you submit to the platform for the purpose of managing the performance of the platform, as well as data about your use of the platform. Although we perform regular routine backups of data, you are solely responsible for any data you submit or that relates to activities you have undertaken using the platform. You agree that we are not liable to you for any loss or damage to such data, and you hereby waive any right of action against us arising from any such loss or damage to such data. *** ## 23. Administration of the platform We reserve the right, but are not obligated, to monitor the Platform for violations of these Terms and Conditions and to take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms and Conditions, including, but not limited to, reporting such user to law enforcement authorities. We also reserve the right, at our sole discretion and without limitation, notification, or liability: * To deny, restrict, or block access to the Platform for certain users * To remove any files and content that are excessively large or burden our systems in any way * To otherwise manage the Platform in a manner serves to protect our rights and property and the proper functioning of the platform *** ## 24. Corrections There may be information on the platform that contains typographical errors, inaccuracies, or omissions, including descriptions, availability, and various other information. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the platform at any time without prior notice. # Privacy Policy Privacy Policy for the KEMPER Connect Cloud ### Privacy Policy – KEMPER Connect As of February 12, 2026 This privacy policy informs you about the nature, scope, and purpose of the processing of personal data (“data”) in the context of our online offering (website, platform/functions, content) and our external online presences (e.g., social media) . We use terms such as “processing,” “controller,” and “processor” in accordance with Art. 4 GDPR. *** ## 1. Controller KEMPER GmbH Von-Siemens-Str. 20, 48691 Vreden, Germany Managing Directors: Björn Kemper, Frederic Lanz Phone: +49 (0) 2564 68 0 Email: *** ## 2. Data protection officer Our external Data Protection Officer is: **Markus Olbring**\ comdatis it-consulting GmbH & Co. KG\ Deventer Weg 8, 48683 Ahaus, Germany\ Email: ****\ Phone: **+49 2567 82900 00**\ Mobile: **+49 173 9799897** For general data protection inquiries, you can also contact: ****. *** ## 3. Categories of data subjects * Visitors to our website * Users of our platform (including administrators, members, test users) * Prospective customers, customers, and business partners * Persons who contact us (support/sales) **Note:** KEMPER Connect is a B2B (business-to-business) platform. Our services are aimed at companies, tradespeople, and professional users. The platform is not intended for use by minors. *** ## 4. Types of data processed Depending on the use, we process in particular: * **Master data** (e.g., name, company, position) * **Contact details** (e.g., email, phone number) * **Account/login data** (e.g., user account, password hash, authentication events) * **Contract data** (e.g., tariff, contract status) * **Content data** (e.g., chat/support messages, form content) * **Usage data** (e.g., functions used, devices/objects created, interaction data) * **Meta/communication data** (e.g., IP address, device and browser information, log files) *** ## 5. Purposes of processing * Provision and operation of website and platform * Registration, login, and account management * Provision of contractual services (SaaS) * Support and communication * Contract management * Security (detection of misuse, fraud, and attacks) * Reach measurement, product analysis, and optimization (only with consent, if necessary) *** ## 6. Legal bases Insofar as the GDPR applies, we process data on the following bases in particular: * **Art. 6 (1) (b) GDPR** (contract/pre-contractual measures) * **Art. 6 (1) (c) GDPR** (legal obligation) * **Art. 6 (1) (f) GDPR** (legitimate interest, e.g., security, operation, optimization) * **Art. 6 (1) (a) GDPR** (consent, e.g., for analysis/marketing technologies) For cookies and similar technologies (storage/retrieval on end devices), we also take into account the requirements of German telecommunications/telemedia law (consent requirements for non-essential technologies). *** ## 7. Operation of the platform: Roles under the GDPR (customer processing) If you use KEMPER Connect as a company/organization and transfer personal data of your end customers, employees, or other data subjects to the platform: * **You** are generally the **controller** (controller). * **We (KEMPER Connect)** process this data as a **processor** within the framework of a data processing agreement (DPA). We are the controller for data that we process for our own purposes (e.g., account management, security, website operation). *** ## 8. Hosting, infrastructure, and data processing (subprocessors) We use service providers who process data on our behalf (Art. 28 GDPR). In doing so, we ensure that suitable contracts (in particular DPA) and appropriate security measures are in place. ### 8.1 Product/platform infrastructure * **DigitalOcean (region: Frankfurt, Germany)** Hosting for **backend, API**, and **relational database**. * **Timescale / TigerCloud (region: Frankfurt; infrastructure on AWS in Frankfurt)** Hosting/management of the **time series database**. * **Vercel** Provision/hosting of the **front end** (delivery of web applications, edge/build infrastructure). ### 8.2 Communication & email * **Brevo** Email delivery (e.g., newsletters/transactional emails—depending on your use case). * **Crisp.chat** Live chat and messaging for support/communication. ### 8.3 AI services * **OpenAI** (OpenAI, L.L.C., USA) AI-supported functions (e.g., text generation, assistants). Third-country transfer to the USA (standard contractual clauses). * **Anthropic** (Anthropic PBC, USA) AI-supported functions (e.g., text processing, analysis). Third-country transfer to the USA (standard contractual clauses). ### 8.4 Consent management * **Cookiebot** (Usercentrics A/S, Denmark) Management of cookie consent and data protection preferences (EU). > Note: Depending on the specific configuration of individual services, data may be transferred to third countries (e.g., USA). In these cases, we ensure compliance with the requirements of Art. 44 et seq. GDPR (e.g., standard contractual clauses, additional protective measures if necessary). *** ## 9. Server log files & security Each time you access the website/platform, we process technical access data (e.g., IP address, date/time, URL accessed, referrer, user agent) in order to * ensure system security, * detect attacks/misuse, * ensure stability and error analysis. The legal basis is **Art. 6 (1) lit. f GDPR** (legitimate interest in secure operation). *** ## 10. Registration, login, user account When registering and using the user account, we process the data required for account creation and authentication (e.g., email, name, password hash, login events) . Legal basis: **Art. 6 (1) (b) GDPR** (contract) and **(f) GDPR** (security/prevention of misuse). *** ## 11. Contact & support (including Crisp.chat) When you contact us (email, phone, form, chat), we process your information to handle your request and communicate with you. * Legal basis: **Art. 6 (1) (b) GDPR** (pre-contractual/contractual) or **(f) GDPR** (general inquiries, efficient customer communication). * Crisp.chat may process **name, email, message content, timestamp**, and technical metadata in particular. *** ## 12. Newsletter & email communication (Brevo) If you subscribe to our newsletter, we process your email address (and name, if applicable) for the purpose of sending the newsletter. * Legal basis: generally **Art. 6 (1) lit. a GDPR** (consent). * Unsubscribe/revoke: at any time via the unsubscribe link in each email or by sending a message to . * Double opt-in/logging: We log registration and confirmation times as well as technical evidence in order to be able to prove your consent (Art. 6 (1) (f) GDPR – legitimate interest in proof). *** ## 13. Analysis & product tracking (Google Analytics, Mixpanel) We use analysis/tracking tools to understand how the website and platform are used and to improve the user experience. * **Google Analytics** (website analysis; e.g., page views, referrers, interactions) * **Mixpanel** (platform/product analysis; e.g., use of functions, created devices/objects, events) **Consent:** If cookies/identifiers or similar technologies are used for this purpose, processing will **only take place after you have given your consent** via our consent tool/banner. Legal basis: **Art. 6 (1) (a) GDPR** (consent). You can change or revoke your consent at any time via the privacy settings (consent banner). *** ## 14. AI-supported functions (OpenAI, Anthropic) We use AI-based services in certain areas of our platform to offer you advanced functions (e.g., intelligent assistants, text generation, data analysis). **Providers used:** * **OpenAI** (OpenAI, L.L.C., USA) – e.g., for text generation and assistance functions * **Anthropic** (Anthropic PBC, USA) – e.g., for text processing and analysis **Processed data:** Depending on the function, input data (texts, queries) may be transmitted to the AI services. We only transmit the data necessary for the respective function. **Third country transfer:** OpenAI and Anthropic are based in the USA. Data is transferred on the basis of standard contractual clauses (Art. 46 (2) (c) GDPR). **Legal basis:** Art. 6 (1) (b) GDPR (performance of a contract, insofar as the AI function is part of the service) or Art. 6 (1) (f) GDPR (legitimate interest in providing innovative functions). **Note on automated decision-making:** There is no automated decision-making within the meaning of Art. 22 GDPR that has legal effect or similarly significantly affects you. *** ## 15. Cookies & consent management We use cookies and similar technologies: * **Necessary technologies** (e.g., session, login, security functions, consent storage) * **Optional technologies** (e.g., analysis/tracking such as Google Analytics, Mixpanel) \*\*Consent management (Cookiebot): \*\* We use **Cookiebot** (Usercentrics A/S, Denmark) to manage your consent. When you first visit our website, a banner will ask for your consent to optional cookies. Your preferences are stored and can be changed at any time via the “Cookie settings” link in the footer of the website or by calling up the banner again. We only activate optional technologies after consent has been given. You can delete/deactivate cookies in your browser; however, this may impair certain functions. *** ## 16. Storage period & deletion We only store personal data for as long as is necessary for the purposes stated. * **Platform data in the event of customer deletion:** When a customer deletes content/personal data from the platform, it is **immediately** removed from the productive systems. Backup processes are also designed so that deleted customer data is **not retained longer than necessary**. * **Contract data:** Storage in accordance with legal retention requirements (e.g., commercial/tax law). * **Support/communication data:** for as long as necessary for processing and, if necessary, for defending/pursuing claims. *** ## 17. Disclosure of data / recipients We only disclose data if * this is necessary for the performance of a contract (Art. 6 (1) (b) GDPR), * there is a legal obligation (Art. 6 (1) (c) GDPR), * you have given your consent (Art. 6 (1) (a) GDPR), or * there is a legitimate interest (Art. 6 (1) (f) GDPR) and no overriding interests. Recipients are, in particular, the processors/sub-processors mentioned in Section 8. *** ## 18. Third country transfers (outside the EEA) If personal data is transferred to countries outside the EEA, this will only be done in compliance with Art. 44 ff. GDPR (e.g., standard contractual clauses, additional measures if necessary) . Whether and to what extent this applies to each service depends on the respective configuration/service provision. *** ## 19. External online presences (social media) We maintain presences on social networks in order to communicate with interested parties, customers, and the public. When you visit our social media pages, data (e.g., usage statistics, interactions) is processed by the respective platform operator. This may involve joint responsibility (in particular for LinkedIn Page Insights, Art. 26 GDPR). **Legal basis:** Art. 6 (1) (f) GDPR (legitimate interest in public relations and communication). **Data protection information for the platforms:** * LinkedIn: * Instagram/Meta: * YouTube/Google: *** ## 20. Technical and organizational measures We take appropriate technical and organizational measures (TOMs) to protect data from loss, misuse, unauthorized access, and unlawful disclosure. *** ## 21. Rights of data subjects You have the following rights, depending on applicability: * **Information** (Art. 15 GDPR) * **Rectification** (Art. 16 GDPR) * **Erasure** (Art. 17 GDPR) * **Restriction of processing** (Art. 18 GDPR) * **Data portability** (Art. 20 GDPR) * **Objection** (Art. 21 GDPR), in particular against processing based on legitimate interests * **Withdrawal of consent** (Art. 7 (3) GDPR) at any time with effect for the future Please address any inquiries to: [**info@kemper.eu**](mailto:info@kemper.eu) *** ## 22. Right to lodge a complaint You have the right to lodge a complaint with a data protection supervisory authority. The competent authority (based in North Rhine-Westphalia) is in particular: **State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia (LDI NRW)** Kavalleriestraße 2–4 40213 Düsseldorf Phone: +49 (0) 211 38424-0 Email: Website: *** ## 23. Changes to this privacy policy We will amend this privacy policy as soon as this becomes necessary due to technical changes, new services, or legal requirements.