Android foreground service that bridges BLE (Bluetooth Low Energy) devices to MQTT, enabling Home Assistant integration via a plugin-based architecture.
BLE Plugins:
- OneControl RV Control System
- Micro-Air EasyTouch RV Thermostat (multi-instance support)
- GoPower Solar Controller
- Mopeka Pro Check Fluid Sensors (multi-instance support)
- Hughes Power Watchdog EPO
- Basic BLE scanner plugin
HTTP Polling Plugins:
- Peplink Cellular Router (multi-instance support)
Note: I'm able to build and test these plugins since they are components I have in my RV. There's a good chance your RV is different and adjustments will need to be made. Pleaase help other users by submitting an issue or feature request if you encounter problems.
- Android Device: Android 8.0+ with BLE support (Recommended: Android 12+ for best battery optimization support)
- Tested with tablet, phone and Android TV devices.
- MQTT Broker: Accessible from the Android device (e.g., Mosquitto on Home Assistant)
- Home Assistant: MQTT integration enabled
- Download the latest APK from GitHub Releases
- Enable "Install unknown apps" for your browser/file manager
- Install the APK
- On first launch: Grant required permissions when prompted
- Open the app - the main screen shows service status and configuration options
- Grant permissions: Tap "Request Permissions" in the Permissions & Optimizations section to grant:
- Location (required for BLE scanning)
- Bluetooth Scan/Connect (Android 12+)
- Notifications (for foreground service)
- Battery Optimization (battery-powered devices only): If shown, disable battery optimization for reliable background operation
- Web Interface Configuration: Configure port and authentication if desired
- Access Web UI: Tap the web interface URL or the open icon to access configuration
- Configure MQTT broker settings (Host, Port, Username, Password)
- Topic Prefix:
homeassistant(recommended for auto-discovery) - Configure device plugins (see plugin sections below)
- Enable plugins as needed
- Services auto-start with the app - MQTT and BLE services will activate automatically when plugins are configured
Note: Plugin instances can only be managed through the web interface.
Once connected, devices are automatically discovered via MQTT auto-discovery:
- BLE MQTT Bridge {MAC}: General diagnostic info for the app and Android device
- Each enabled plugin will be a separate device
The devices will have a mix of the following discovered entities which depend on your specific hardware:
- Switches - Binary relays
- Lights - Dimmable with brightness control
- Covers - Slides and awnings
- Sensors - Temperature, voltage, tank levels
- Binary Sensors - Diagnostic indicators
- Climate - Still a work in progress, but OneControl-connected HVAC should be fully supportable
The OneControl plugin connects to LCI/Lippert OneControl BLE gateways found in RVs. This is an unofficial, community-developed integration not affiliated with or supported by LCI/Lippert, and is provided "as-is" without warranty—use at your own risk.
####Tested Gateways The following OneControl gateways have been confirmed working:
- Unity X270D
- X1.5
- x4
The OneControl gateway must be paired to the Android device.
Pairing Steps:
Newer Android OS versions do not show BLE devices in the Bluetooth pairing settings, so there are a couple of ways to accomplish this:
- Use an existing pairing:
- If you previously connected to the OneControl gateway with the same device, you already have a pair bond (you can confirm this by checking devices in Bluetooth settings). In this case, you're good to go.
- Go ahead and configure the plugin in the web UI:
- Make sure the BLE service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Enter the Gateway MAC Address (found in Bluetooth settings after pairing or you can get this from the Advertisement Monitor in Home Aassistant)
- Enter your Gateway PIN/Password (found on a sticker on your OneControl board)
- Toggle the service on
- Plugin status indicators should turn green: Connection → Data → Paired
- Let the app trigger pairing:
-
Make sure the main service toggle is off (you won't be able to make changes while it's running)
-
Add the plugin
-
Enter the Gateway MAC Address (found in Bluetooth settings after pairing or you can get this from the Advertisement Monitor in Home Aassistant)
-
Enter your Gateway PIN/Password (found on a sticker on your OneControl board)
-
IMPORTANT: From here there are two pairing paths depeding upon they style supported by your OneControl hardware
- Path 1 - If you have a 'Connect' button: Put the OneControl gateway in pairing mode by pressing the 'Connect' button (the exact process may vary for different gateways, but this is the same process you do to initially connect using the LCI app)
- Toggle the service on
- Path 2 - If you DO NOT have a 'Connect' button: Toggle the main service on and you should get a pairing request pop-up.
- Enter the same PIN from the sticker on the gateway
- Path 1 - If you have a 'Connect' button: Put the OneControl gateway in pairing mode by pressing the 'Connect' button (the exact process may vary for different gateways, but this is the same process you do to initially connect using the LCI app)
-
The app should then complete pairing with your gateway. You can confirm this by checking Settings → Bluetooth. The Gateway should show as a paired device.
-
Plugin status indicators should turn green: Connection → Data → Paired
-
| Device Type | HA Entity | Features |
|---|---|---|
| Switches | switch |
ON/OFF control |
| Dimmable Lights | light |
Brightness 0-255 |
| Slides/Awnings | cover |
Open/Close/Stop |
| Tank Sensors | sensor |
Fill level % |
| System Voltage | sensor |
Battery voltage |
| HVAC | climate,sensor |
Status monitoring |
- Connection fails: Ensure the gateway shows as paired in Android Bluetooth settings
- No devices appear: The app sends a GetDevices command on connect - toggle the service off/on, or force-close and relaunch the app.
The EasyTouch plugin connects to the EasyTouch RV thermostat by Micro-Air. This is an unofficial, community-developed integration not affiliated with or supported by Micro-Air, and is provided "as-is" without warranty—use at your own risk.
This plugin requires EasyTouch firmware version 1.0.6.0 or newer. The plugin uses the unified JSON protocol introduced in firmware 1.0.6.0. Older firmware versions use model-specific protocols that are not supported. To check your firmware version, check the official EasyTouch RV app.
Special thanks to k3vmcd and his ha-micro-air-easytouch HACS integration. His project inspired this application's creation and his work decoding the thermostat's BLE protocol was essential to this implementation.
- Make sure the main service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Enter the Thermostat MAC Address (you can get this from the Advertisement Monitor in Home Aassistant)
- Enter your Thermostat Password (this is the password you use to login in the Micro-Air app)
- Toggle the service on
- Plugin status indicators should turn green: Connection → Data → Pair
| Feature | Description |
|---|---|
| Multi-Zone Support | Up to 4 climate zones ** Not yet fully tested** |
| Capability Discovery | Only shows modes your device supports |
| Auto Mode | High/low setpoint UI when in Auto |
| Temperature Limits | Min/max from actual device config |
Modes are discovered dynamically from device. Common modes:
- Off, Heat, Cool, Auto, Fan Only
- Dry (only if device supports it)
- Connection drops: Check thermostat is in range and not connected to another device, toggle the service off/on, or force-close and relaunch the app.
The GoPower plugin connects to GoPower solar charge controllers (e.g., GP-PWM-30-SB) commonly found in RVs. This is an unofficial, community-developed integration not affiliated with or supported by GoPower, and is provided "as-is" without warranty—use at your own risk.
- Make sure the main service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Enter the Controller MAC Address (found in Bluetooth settings after pairing or you can get this from the Advertisement Monitor in Home Aassistant)
- Toggle the service on
- Plugin status indicators should turn green: Connection → Data
Note: GoPower controllers do not require pairing or authentication.
| Feature | Description |
|---|---|
| Reboot | Reboot the solar controller |
| No Authentication | Connects without pairing or password |
| Real-Time Data | ~1 second update rate |
| Device Diagnostics | Model, firmware version |
| Sensor | Description | Unit |
|---|---|---|
| PV Voltage | Solar panel voltage | V |
| PV Current | Solar panel current | A |
| PV Power | Solar input power | W |
| Battery Voltage | Battery voltage | V |
| Battery Percentage | State of charge | % |
| Controller Temperature | Internal temperature | °C |
| Energy | Daily energy production (Ah × voltage) | Wh |
| Device Model | Controller model number | text |
| Device Firmware | Firmware version | text |
| Reboot Controller | Soft-reboots the controller | button |
- No data received: Ensure controller is in BLE range (within ~30 feet)
- Connection drops: Verify no other device is connected to the controller
The Hugjes plugin connects to Hughes Power Watchdog EPO surge protectors (e.g., WD30EPO, PWD50EPO) commonly found in RVs. This is an unofficial, community-developed integration not affiliated with or supported by Hughes, and is provided "as-is" without warranty—use at your own risk.
- Make sure the main service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Enter the Device MAC Address (you can get this from the Advertisement Monitor in Home Aassistant)
- Toggle the service on
- Plugin status indicators should turn green: Connection → Data
Note: PWD devices do not require pairing or authentication.
| Feature | Description |
|---|---|
| No Authentication | Connects without pairing or password |
| Real-Time Data | ~1 second update rate |
- No data received: Ensure device is in BLE range (within ~30 feet)
- Connection drops: Verify no other device is connected to the controller and that the device is in range
The Peplink plugin monitors Peplink cellular routers (e.g., MAX Transit) via HTTP API, tracking WAN status, cellular signal strength, and bandwidth usage. This is an unofficial, community-developed integration not affiliated with or supported by Peplink, and is provided "as-is" without warranty—use at your own risk.
Note: This is an HTTP polling plugin, not BLE-based. Multiple instances can be configured to monitor multiple routers.
- Access the web interface
- Add a Peplink plugin instance
- Configure:
- Instance Name: Unique identifier for this router
- Router IP Address: Local IP of your Peplink router
- Admin Username/Password: Router credentials
- Poll Interval: Update frequency (default: 60 seconds)
- Enable the instance
| Feature | Description |
|---|---|
| Multi-Instance | Monitor multiple Peplink routers |
| Authentication Tracking | Monitors API authentication status |
| Diagnostic Sensors | API connection, authentication, and data health |
| Sensor | Description | Unit |
|---|---|---|
| WAN Status | Connection state | text |
| Signal Strength | Cellular signal (RSSI/RSRP/RSRQ) | dBm |
| Bandwidth Usage | Current upload/download rates | Mbps |
| Data Usage | Total data transferred | GB |
| Connection Uptime | Time connected | hours |
| Sensor | Description |
|---|---|
| API Connected | HTTP API reachability |
| Authenticated | Login session status |
| Data Healthy | Valid data being received |
- Authentication fails: Verify router credentials and API access is enabled
- Connection drops: Check network connectivity between Android device and router
- No data: Verify poll interval is reasonable and router is responding
The Mopeka plugin integrates Mopeka Pro Check/Pro Plus/Pro H2O Bluetooth tank level sensors. Unlike other plugins in this system, Mopeka uses passive BLE advertisement scanning - no GATT connection is required. The sensor broadcasts tank level, temperature, and battery status in manufacturer-specific advertisement data.
Credits:
- sbrogan: Original work decoding the Mopeka sensor BLE protocol (mopeka-iot-ble library)
- jrhelbert: Volumetric calculation formulas for accurate tank percentage (HA Community Post)
Supported Models:
- Mopeka Pro Plus (M1015)
- Mopeka Pro Check (M1017)
- Mopeka Pro 200
- Mopeka Pro H2O (water sensors)
- Mopeka Pro H2O Plus
- Lippert BottleCheck
- TD40, TD200
- Make sure the main service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Enter the MAC Address (you can get this from the Advertisement Monitor in Home Aassistant)
- Enter the tank size and fluid type
- Toggle the service on
- Plugin status indicator should turn green
Note: Mopeka controllers do not require pairing or authentication.
| Feature | Description |
|---|---|
| No Authentication | Connects without pairing or password |
| Real-Time Data | ~14 second update rate |
| Sensor | Description | Unit |
|---|---|---|
| Battery Percentage | State of charge | % |
| Temperature | Sensor temperature | °C |
| Tank Level | Tank level percent | % |
- No data received: Ensure sensors are in BLE range (within ~30 feet)
A utility plugin that scans for nearby BLE devices and publishes results to MQTT. This is not needed for anything else to function, but was added as a proof of concept for supporting multiple BLE connected plugins and might be useful, so I left it in.
- Discovering MAC addresses of BLE devices
- Monitoring BLE device presence
- Debugging BLE connectivity issues
- Make sure the main service toggle is off (you won't be able to make changes while it's running)
- Add the plugin
- Toggle the service on
- Scanning is triggered by a button in the MQTT device in Home Assistant
- Results are published as sensor attributes in Home Assistant
See docs/INTERNALS.md for detailed architecture documentation.
For HAOS users who want remote APK deployment without physical device access, this repository includes an optional add-on that maintains wireless ADB connectivity.
- Auto-detection: Automatically chooses wireless or bridge mode based on device network
- Wireless ADB: Keeps wireless ADB alive for WiFi-connected devices
- Bridge Mode: ADB over network for Ethernet-connected devices
- Works with any Android device: Not limited to this app
- Add this repository to Home Assistant:
https://github.com/phurth/ble-plugin-bridge - Install "ADB Bridge" add-on
- Connect Android device via USB to HAOS host
- Enable USB debugging on device
- Start add-on and deploy APKs remotely via
adb connect
See haos-addon/README.md for detailed setup and usage.
MIT License - see LICENSE for details.