I understand.
Thank you very much for your time…
Good news Juraj 
It works!!!
It was just the wrong password. Atrea has a different password for internet connection and modbus/ethernet connection. The login is the same, but the password is different.
Maybe it will be useful to someone else…
Hi Juraj, thanks a lot for the integration, saved me a lot of time as I was thinking to control over ModBus TCP directly from Home Assistant. This saves a lot of time, thanks!
I happen to have a full ModBus commands table for Atrea RD4 units (like my RA5). But you probably have this too, right? If not, I can share.
Hi Juraj! I know it’s been a long time since the start of this thread but I just got an Atrea unit , tried to set it up in HA, and got the following error : “IP address is not a supported Atrea unit” , here is some info about my unit : Duplex 370 EC5.aM-CE, sw: aMCE-v2.1.3 . Can you help me, is this version supported? Thanks!
Hi, that unit is not supported. Probably uses completely different UI.
Dear Juraj,
First of all, thanks a lot! And here is my use case:) I have my Atrea R-5 RK5 in my HA.
Use case: Whenever my photovoltaic (SOLAX) batteries are full, and I am pushing back energy to the grid, I want to increase the required water temperature so that I “store” the energy in the water via the current system (with no need to add any extra stuff).
The heat pump and two spirals heat water. I found this UI public on the internet - that’s what I have and what Atrea controls. http://46.13.143.144/
I am unsure if I can control the water temperature from Atrea UI. Any tips?
I mentioned earlier that im bashing together ugly code GitHub - xbezdick/amotionatrea that +/- works but is extreme alpha. I will be forcepushing into the repo until it gets more sane code and i can have 0.1 relesae. But ill appreciate second pair of eyes and input. Works only with the amotion version of ateea and i went for not modbus but direct api use with requests.
I have the same Heat pump as Ondrej Strouhal (atrea TCA 3.1). it would be great to have the whole combo, to control both units ie. if my FVE batteries are full, automatically increase the pump temperature to use the exceed energy for heating it, and not sending to the grid for 0.5kc/KWh
for now I have only basic FVE automation, that if the spot price is negative, my Goodwe invertor cuts of sending power TO the grid, to not pay for the sent energy.
if someone need info about that, I can send all needed links and info.
Hi, thanx for the whole work.
i hava an atrea duplex easy 400 with the “normal” cpa controller (without a modbus).
i’m a programmer but a noob in electronics. is it somehow possible to just control the the speed of the ventilation by an esp? how would it work - i need a starting point for my experiment.
Hello!
First of all, thank you Juraj for spend your time to do this for all of us. Your kindness and effort is appreciated.
I have a DUPLEX 370 EC5 unit from Atrea and installed the integration from HACS and added the IP address and port 80 (i do not know what port it uses so I have left the default one) and when I am prompted to the log in screen I get the error that the password is incorrect ot there are too many users logged in.
The unit is controlled only via web, no physical control installed
I’m very new to Home Assistant (using Green) so what am I doing wrong?
@ SpyDrCZ were can I find the correct password?
Later edit: found the password and managed to connect. Super happy!!
Thank you!
Hello!
Is this working with DUPLEX 350 Pro.aM?
I am getting IP address is not a supported Atrea unit.
Anyway other way to control this otherwise?
Thank you!
I have aM unit integrated through Modbus - if you are interested, I can share the configuration
1 Like
Please do. Thank you!
Hi,
I have an Atrea duplex 400 and would like to buy the RD5 controller (I do not have one).
I have a question: the unit has summer bypass, meaning that bellow 18 degrees it recirculates the inside air, above 18 degrees it gets air from outside, this is not helpful during the summer. With RD5 can you see the setting of that sensor and change it?
I have a question: the unit has bypass, meaning that bellow 18 degrees it recirculates the inside air, above 18 degrees it gets air from outside, this is not helpful during the summer (it is actually warming up, I would like to get air from outside only during the night on summer when it is chilly, during the day I am using AC and would like the air to be recirculated all over the house). With RD5 can you see the setting of that sensor and change it? I am not sure if the question was clear. I do not want to pay for the module if not useful.
Sure. It is as simple as this:
modbus:
- name: rekuperace
type: tcp
host: 192.168.138.138
port: 502
sensors:
- name: rekuperace hromadne cteni
address: 1101
input_type: input
count: 5
data_type: custom
structure: ">5h"
- name: rekuperace režim
address: 1001
input_type: input
- name: rekuperace výkon ventilátorů
unit_of_measurement: '%'
address: 1004
input_type: input
fan:
- platform: template
fans:
rekuperace:
friendly_name: "rekuperace"
value_template: "{{ states('sensor.rekuperace_rezim') | int > 0 }}"
percentage_template: "{{ states('sensor.rekuperace_vykon_ventilatoru') }}"
turn_on:
service: modbus.write_register
data:
unit: 1
address: 1001
value: 2
hub: rekuperace
turn_off:
service: modbus.write_register
data:
unit: 1
address: 1001
value: 0
hub: rekuperace
set_percentage:
service: modbus.write_register
data:
unit: 1
address: 1004
value: "{{ percentage }}"
hub: rekuperace
…plus there are some helper templates to get particular data from “hromadne cteni” (bulk read) like exhaust air temperature: {{ states("sensor.rekuperace_hromadne_cteni").split(",")[4] | float * 0.1 | round(1)}} - I’m not sure which one is which one at the moment.
1 Like
Hello!
Could someone provide the Modbus registers for these devices?
DUPLEX 3500 Multi Eco-V and EC 570
What was the default username And password, please? I have only webaccess with password “pass”
Hi all, I’ve been working on a custom Home Assistant integration for Atrea aMotion units. It talks directly to the unit over the local network using the native websocket API, so it is not a Modbus-based integration. The goal is to expose the device in a way that matches how aMotion actually works in practice, including ventilation control, climate-related controls, bypass handling, telemetry, and active-state notifications.
The integration is moving toward a capability-driven model, so entities are created based on what the specific unit actually exposes rather than forcing a fixed layout. There is also a dedicated custom Lovelace card for this integration, intended to provide a cleaner UI for the most important controls and status information.
