
Atrea aMotion is the new-generation control system for Atrea DUPLEX heat recovery ventilation (MVHR) units, replacing the older RD5 controller. The aMotion system is available with aDot and aTouch user interface panels. TapHome connects directly to the aMotion controller via Modbus TCP over Ethernet on port 502 — no additional gateway is required.
The template provides full operating mode control (8 modes), thermostat with temperature setpoint, fan power adjustment (0–100%), bypass damper and zone control, circulation ratio setting, pressure level selection, two temperature sensors (outdoor and indoor), and comprehensive diagnostics monitoring 50+ alarm, warning and info registers.
Network connection
The aMotion controller has a built-in Ethernet interface. Connect it to the same local network as TapHome Core using a standard Ethernet cable.
- Protocol: Modbus TCP
- Port: 502
- Slave ID: 1–255 (configurable via aTool)
- Data encoding: Int16, temperature values divided by 10, airflow values multiplied by 10
When reading or writing multiple registers in one batch, maintain at least a 5-second interval between requests. Shorter intervals may cause communication timeouts.
Enabling Modbus communication
Modbus TCP must be explicitly enabled using the aTool service software before TapHome can communicate with the unit.
- Open the aTool application and connect to the aMotion unit
- Navigate to section Komunikace (Communication)
- Enable Modbus
- Configure the desired Slave Address (default: 1)
If Modbus is not enabled in aTool, the aMotion controller will not respond to any Modbus TCP requests on port 502.
The HTTP/XML API used by older Atrea RD5 integrations (e.g., pyatrea library) is not compatible with aMotion units. Direct Modbus TCP is the recommended and supported integration method.
Configuration
When importing the template in TapHome, provide:
- IP Address — the aMotion controller’s IP on the local network
- Slave ID — Modbus slave address (default: 1, configurable 1–255 via aTool)
Assign a static IP address or DHCP reservation to the aMotion controller in the router settings to prevent the address from changing after a power cycle.
Device capabilities
The template exposes the following devices:
Operating mode and zone control
- Mode Control — multi-value switch for selecting the operating mode via registers H:1001 (write) / I:1001 (read). Available modes: Off, Auto, Ventilation, Circulation + Ventilation, Circulation, Night Cooling, Disbalance, Overpressure.
- Zone Control — multi-value switch for selecting the active zone via registers H:1003 (write) / I:1003 (read). Options: Zones 1+2 (both), Zone 1 only, Zone 2 only.
- Pressure Level — multi-value switch for pressure level setting via registers H:1007 (write) / I:1007 (read). Options: Off, Low, Normal.
Thermostat and temperature monitoring
- Thermostat — room temperature control reading the current indoor temperature from I:1104 (T-IDA) and setting the desired temperature via H:1002. Temperature range -30.0 to 90.0 °C with 0.1 °C resolution.
- Outdoor Air Temperature (T-ODA) — reads outdoor air temperature from I:1101 (value / 10 = °C).
- Indoor Air Temperature (T-IDA) — reads indoor air temperature from I:1104 (value / 10 = °C).
Fan and airflow control
- Fan Power — dimmer controlling fan power from 0% to 100% via register H:1004. Adjusts the ventilation intensity for both supply (M-SUP) and exhaust (M-ETA) fans simultaneously.
- Circulation Ratio — dimmer controlling the mixing proportion between recirculated and fresh air from 0% to 100% via register H:1008.
- Bypass Damper Command — multi-value switch for bypass damper position via registers H:1008 (write) / I:1009 (read). Options: Auto, Open, Closed.
Module-level monitoring
The template includes 27 service attributes providing detailed real-time status information:
| Category | Monitored values |
|---|---|
| Fan commands | Supply fan M-SUP (%), exhaust fan M-ETA (%) |
| Airflow | Supply fan (m³/h), exhaust fan (m³/h), fresh air (m³/h), ventilation setpoint (m³/h), circulation setpoint (m³/h) |
| Temperatures | Supply air T-SUP (°C), extract air T-ETA (°C), exhaust air T-EHA (°C), average outdoor (°C) |
| Actuator commands | Circulation damper (%), preheater (%), heater A (%), heater B (%), cooler (%), bypass transition time (ms) |
| Equipment status | Fan status, dampers open/closed, preheater, heating, heater A/B, cooler A, pumps (heater A/B, cooler A) |
Module-level diagnostics
The aMotion template monitors 50+ discrete registers (D:6003–D:6111) for errors, warnings, and informational messages, including:
- Alarms: Frost protection (1st/2nd), stop signal, unit overheating, unbalanced airflow, manometer faults, heater A/B faults, cooler A fault, internal/external bus faults, Ethernet communication fault, temperature sensor faults (T-EHA/T-ETA/T-ODA/T-IDA/T-SUP), confirmed stop signal, anti-freeze capillary, device not ready, airflow sensor faults (SUP/ETA/ODA)
- Warnings: Insufficient airflow/preheating, heat pump defrost, heater/cooler overload, heat exchanger freeze, airflow learning, UVC lamp change, trial operation end, clogged filters, cooling blocked
- Info: Heat exchanger defrost, HDO higher tariff, learning process, filter PF1/PF2/PF3 clogged, max heater A/B power, fault inputs IN1/IN2/IN3, anti-freeze DI1–DI4, airflow increase for heating, device inspection interval, filter replacement interval
Additional capabilities
The aMotion units also expose Modbus registers for current season indicator, detailed operation mode (17 internal states from Off through Manual control), fan control method, maximum/minimum configurable airflow, airflow measurement source, circulation and bypass damper control methods, external temperature inputs from BMS (T-IDA and T-ODA), alarm/filter/UVC lamp reset commands, and scene trigger addresses. These can be added to the TapHome template in a future update.
Troubleshooting
No Modbus communication
- Verify that Modbus is enabled in aTool — section Komunikace (Communication)
- Confirm the aMotion controller’s IP address — check the router’s DHCP lease table or the unit’s display
- Ensure TapHome Core and the aMotion controller are on the same network/subnet
- Check that no firewall is blocking port 502
- Verify the Slave ID matches between TapHome and the unit configuration
Temperature values appear incorrect
Temperature registers use Int16 encoding with the value divided by 10. For example, a register value of 215 represents 21.5 °C. Values above 32767 represent negative temperatures: (value - 65536) / 10. For example, value 65516 = (65516 - 65536) / 10 = -2.0 °C.
Airflow values appear incorrect
Airflow registers use Int16 encoding with the value multiplied by 10. For example, a register value of 35 represents 350 m³/h.
Communication timeouts
The manufacturer recommends a minimum 5-second interval between batch register reads. If TapHome reports frequent communication errors, ensure no other Modbus client (e.g., Home Assistant, BMS) is polling the same unit simultaneously with short intervals.
