Home Assistant integration for the Micro-Air EasyTouch RV thermostat, connected over Bluetooth Low Energy (BLE).
This integration exposes your EasyTouch thermostat as a native Home Assistant climate entity so you can monitor and control it from the dashboard or from automations.
Core:
- Climate entity per zone (temperature, HVAC mode, fan mode, setpoints)
- Automatic multi-zone detection, single-zone and multi-zone units are both supported
- Ambient temperature sensor from the faceplate
- HVAC modes: Heat, Cool, Auto, Dry
- Fan modes: Off, Low, High, Auto (where supported by the current HVAC mode)
Additional:
- Reboot button for the thermostat
set_locationservice so the device can display local weather
Known limitations:
- When the unit is powered off from the device itself, this state is not reflected in Home Assistant
- Not all fan modes are settable in Home Assistant, "Cycled High" and "Cycled Low" are not available in Home Assistant - this is due to limitations in the Home Assistant Climate entity
- Whenever the manufacturer mobile app connects to the device via bluetooth, Home Assistant will be temporarily disconnected and does not receive data
- Home Assistant 2024.10.1 or newer
- A Bluetooth adapter or proxy that supports active (connectable) connections. The EasyTouch does not advertise its data passively, so any adapter or proxy limited to passive mode will not work, regardless of brand. An ESPHome Bluetooth proxy with
active: true, a supported USB Bluetooth adapter, or your Home Assistant host's built-in Bluetooth all work. - The same email and password you use to log in to the Micro-Air mobile app, there is no separate integration login.
This repository is not yet in the HACS default store, so it needs to be added as a custom repository:
- In Home Assistant, open HACS
- Click the three-dot menu in the top right corner and choose Custom repositories
- Add the repository URL:
https://github.com/k3vmcd/ha-micro-air-easytouch - Set Type to Integration (required, otherwise HACS reports the repository as invalid)
- Click Add
- Find Micro-Air EasyTouch Thermostat in HACS and click Download
- Restart Home Assistant
- Download the latest release from the Releases page
- Copy the
custom_components/micro_air_easytouchfolder into thecustom_componentsfolder of your Home Assistant configuration directory (create the folder if it doesn't exist) - Restart Home Assistant
- Go to Settings > Devices & Services
- Home Assistant should auto-discover the thermostat over Bluetooth and notify you. If not, click Add Integration and search for Micro-Air EasyTouch
- When prompted for credentials, enter the same email and password you use to sign in to the Micro-Air mobile app
- Confirm the discovered device
Home Assistant creates one climate entity per zone: one for single-zone units, one per zone for multi-zone units.
Allow a few minutes after setup for all entities to populate.
Sets the latitude and longitude the thermostat uses to display local weather.
| Field | Description |
|---|---|
address |
Bluetooth MAC address of the thermostat, e.g. 00:11:22:33:44:55 |
latitude |
Latitude, between -90.0 and 90.0 |
longitude |
Longitude, between -180.0 and 180.0 |
Example:
service: micro_air_easytouch.set_location
data:
address: "00:11:22:33:44:55"
latitude: 40.7128
longitude: -74.0060Pairs well with an automation that updates location from a device_tracker or person entity as the RV moves.
"Invalid auth" during setup Use the same email and password you use to log in to the Micro-Air mobile app. There is no separate password for this integration.
HACS says the repository is invalid Make sure Integration is selected as the type when you add the custom repository. This is the most common cause of that error.
The integration can't find or connect to the device Your Bluetooth adapter or proxy must support active connections, see Requirements above. A passive-only adapter can see the device advertise but can't complete the connection this integration needs.
Home Assistant loses connection while using the mobile app This is expected. BLE devices only support one active connection at a time, so Home Assistant and the manufacturer's app can't both be connected simultaneously.
- Questions: GitHub Discussions
- Bugs: GitHub Issues