EKHBRD016ACV1

[stav242]

Hi
I have just found this. But I cannot find a X10 connector on the main PCB.

The system is a EKHBRD016ACV1
https://www.daikin.co.uk/en_gb/products/ekhbrd-adv1.html

And the main PCB inside has a few blue





connectors but no X10.

Can anyone help identify which connector I need to use ?

I have the esp32 setup ready to connect.

[raomin]

Hi @stav242
I've looked closely at your pics and I could not find it either... nor that I could find one on the manuals of your model...
You might have one that is not supporting it.

If I were you I would try to see what is it next to the CPU of your board, it could be a serial port... But it's unlikely.

Maybe you're left with the P1P2Serial.

[KalaNagHTD]

Seeing the big capacitors I doubt that this board is the A1P (Inverter Control PCB)! You have to find the A1P board!

Karl

Edit: You have the V1 unit w/o A1P :-(

[julianbl]

Hi I have just found this. But I cannot find a X10 connector on the main PCB.

The system is a EKHBRD016ACV1 https://www.daikin.co.uk/en_gb/products/ekhbrd-adv1.html

And the main PCB inside has a few blue connectors but no X10.

Can anyone help identify which connector I need to use ?

I have the esp32 setup ready to connect.

Hi! I have the same model, similar layout. I was thinking on using the X41A port, as it's indicated to be a service port in the manual. Have you tried it? have you made any progress?

Btw, do you know the pins to use an external thermostat? I'd also like to control the heater on/off.

Thanks!

[raomin]

Are you sure it's not this one?

[stav242]

Hi. No I gave up. Let me know if you work it out!

…

On Tue, 22 Nov 2022, 22:29 Raomin, ***@***.***> wrote: Are you sure it's not this one? [image: image] <https://user-images.githubusercontent.com/4460208/203434339-2073f73b-2c2a-48f4-993c-87f38b0235a9.png> — Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOJGGXECQA3EZD4WRYL5BLWJVCMNANCNFSM5SZMZ7TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[julianbl]

Hi! Here is a close up. There is no conector there... :(

[glosair]

Do you have a picture of PCB 2?

[julianbl]

Just realized that the Main PCB is not this one. In fact it's the smaller one. Still no X10A, bue it has some interesting connectors. What do you think?


Would this do the job? There is no info about X24A.

Thanks!

[stav242]

Hi, im not attempting to do anything unless someone else can confirm what works first. i cant afford to break my heatpump and loose my home heating. really need some schematics to understand the PCB connections.

…

On Mon, 12 Dec 2022 at 14:30, Julián Blomberg ***@***.***> wrote: Just realized that the Main PCB is not this one. In fact it's the smaller one. Still no X10A, bue it has some interesting connectors. What do you think? [image: image] <https://user-images.githubusercontent.com/36976865/207070452-4f658de8-8364-4433-9343-de76e358f999.png> [image: image] <https://user-images.githubusercontent.com/36976865/207070617-5b5270c5-ea86-4e03-8494-b285deca0940.png> Would this do the job? There is no info about X24A or X17A. Thanks! — Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOJGGS77K4YLVJ3DECDBCTWM4ZIZANCNFSM5SZMZ7TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[DDoykov]

Hi,
Two years ago i ran diagnostics on three phase indoor unit and i remember, that i hooked up indoor unit with D-Checker and outside unit with my DIY Bluetooth D-Checker .

That machine is two stage high temperature refrigerant system with R410A and R134A.
The single and three phase versions do look alike on the outside, but are totally different in term of hardware.
That is one hell of a complicated machine which is pain in the a*$ to diagnose and repair.

Outdoor unit is MiniVRV4 like RXYSQ-t for example. It is very good unit with subcooling controll. I suppose that the sortware was changed to work as altherma only.
Indoor unit can be looked as "indoor unit" with Main PCB (A1P) used in smal inverter chillers and "outdoor unit" with Inverter PCB (A5P) ( + Inverter control PCB (A4P) for 3P models ) and R134A compressor.

And like any Daikin Chiller, VRV or SkyAir unit, the diagnostics are made from the outdoor unit ONLY.
On single phase units you have to connect the D-Checker to the X41A connector on the Inverter PCB (A5P).
On three phase units X41A is used again but is located on Inverter control PCB (A4P) ( the one with LED's and buttons).
In my practice i found that there are data that is not shown in D-Checker software, and if that is critical data, i use Service Checker for VRV which is hooked on the F1/F2 line.

That was the easy part. Now you have to implement the PROTOCOL @!
If you manage to make it read data form the indoor unit, i suggest you to hook the outdoor unit with another ESP32. That way you will receive more data comming from both units.

Good luck :)

[PiotrBeeScale]

Hi.
The X10A connector is located on the Control-PCB-A3P board.
The X21A connector is located in the upper part of the board.
I measured the voltage between the extreme pins - it is 5V.
Is it possible it's the RS port? If so, how to check?

[julianbl]

Hi all!
I finally got enough courage to connect the ESP32 and start testing...
I've connected it to the X14A connector on the inverter PCB and got lots of data!

{"*Refrigerant type":"Conv 801 not avail.","Sensor Data Qty":10,"INV compressor Qty":1,"STD Compressor":0,"Fan Data Qty":0,"Expansion Valve Data Qty":1,"4 Way Valve Data Qty":1,"Crank Case Heater Qty":1,"Solenoid valve Qty":1,"Max. connectable indoor units":4,"Connected Indoor Unit Qty":1,"O/U MPU ID":"Conv 213 not avail.","O/U MPU ID":"Conv 213 not avail.","NextDataGrid":"Conv 995 not avail.","NextDataGrid":"Conv 995 not avail.","In-Out separator":"Conv 998 not avail.","Operation Mode":"Fan Only","Thermostat ON/OFF":"OFF","Restart standby":"OFF","Startup Control":"OFF","Defrost Operation":"OFF","Oil Return Operation":"OFF","Pressure equalizing operation":"OFF","Demand Signal":"OFF","Low noise control":"OFF","Other control 1":"OFF","Other control 2":"OFF","Other control 3":"OFF","Other control 4":"OFF","Other control 5":"OFF","Other control 6":"OFF","Other control 7":"OFF","Other control 8":"OFF","Other control 9":"OFF","Other control 10":"OFF","Other control 11":"OFF","Other control 12":"OFF","Other control 13":"OFF","Other control 14":"OFF","Other control 15":"OFF","Other control 16":"OFF","Error type":"Normal","Error Code":" 0","Target Evap. Temp.":1.99219,"Target Cond. Temp.":"---","Discharge Temp. Drop":"OFF","Discharge Temp. Protection Retry Qty":"Conv 310 not avail.","Comp. INV Current Drop":"OFF","Comp. INV Current Protection Retry Qty":"Conv 311 not avail.","HP Drop Control":"OFF","HP Protection Retry Qty":"Conv 310 not avail.","LP Drop Control":"OFF","LP Protection Retry Qty":"Conv 311 not avail.","Other Control":"OFF","Outdoor air temp.":0,"Outdoor heat exchanger temp.":0,"Discharge pipe temp.":47.6,"Suction pipe temp.":22.2,"Outdoor heat exchanger mid temp.":-47.5,"Liquid pipe temp.":22.2,"INV fin temp.":29.6,"Low Pressure":5.6,"Low Pressure(T)":"Conv 405 not avail.","Sensor data 9":2816.1,"Sensor data 10":0,"Sensor data 11":0,"INV primary current (A)":0,"INV secondary current (A)":0,"INV fin temp.":-2688,"Sensor data 4":0,"Sensor data 5":0,"Sensor data 6":0,"Sensor data 7":0,"Sensor data 8":0,"Sensor data 9":0,"Sensor data 10":0,"Sensor data 11":0,"INV frequency 1 (rps)":0,"INV frequency 2 (rps)":0,"STD Compressor 1":"OFF","STD Compressor 2":"OFF","Fan 1 (step)":0,"Fan 2 (step)":0,"Expansion valve 1 (pls)":0,"Expansion valve 2 (pls)":0,"4 Way Valve 1":"OFF","4 Way Valve 2":"OFF","Crank case heater 1":"OFF","Crank case heater 2":"OFF","Solenoid Valve 1":"OFF","Solenoid Valve 2":"OFF","Solenoid Valve 3":"OFF","Solenoid Valve 4":"OFF","Solenoid Valve 5":"OFF","Solenoid Valve 6":"OFF","Solenoid Valve 7":"OFF","Solenoid Valve 8":"OFF","Solenoid Valve 9":"OFF","Solenoid Valve 10":"OFF","WifiRSSI":"-68dBm","FreeMem":"218024"}

I'm using the default.h with all the options enabled, just for testing.

I've also tried the 4 pin blue connector on the control PCB, but even it got information from it, ESPAltherma could not interpret any of it.

Any ideas on how to move forward now?
Can I get a dump of the reading so we can improve it or create a definition file for our EKHBRD devices?

Thanks!

[PiotrBeeScale]

Hi!
I managed to get the service manual. It confirms that the connection is correct.

[julianbl]

what would be the best (closeset) definition to use with this device? tnx!!

[PiotrBeeScale]

Today I connected the M5StickPlus to the X41A ALtherma. In setup.h
I set #define PROTOCOL 'I' to #define PROTOCOL 'S' and //#include "def/PROTOCOL_S.h to #include "def/PROTOCOL_S.h.

EKHBRD is really Altherma 2.

With these settings, no errors appear (Error 0x15 0xEA returned from HP), but there is a small amount of data.

I tried inserting a line into def/PROTOCOL_S.h - "{0x50, 1, 103, 2, -1, "XXX"},".

After compiling and uploading to M5StickPlus, I can see in the Home Assistant log how the value for "XXX" changes in different readings, e.g. -43.9609, -21.9609, -7.96094, -43.9609, -28.9609 ..etc.
Altherma replies to the query, but I don't know what it answers and what parameter it is.
I don't know what to do next.

[selman61]

@stav242 Thanks a lot for taking the time, really appreciate it!

[stav]

31. @stav Thanks a lot for taking the time, really appreciate it!

@stav242

[selman61]

@stav242 Thanks, really useful! Only these differ:

0x001 model type: 07 → 08
0x003 inverter/hot water settings: 00 → 2E
0x062–0x067 spec/EC number: default placeholder → AS1704403-02, EC 23 30
Two quick questions: do you have a hot water tank, and has the indoor unit ever had a board replaced?

[julianbl]

Hi @raomin!

I ran a synchronized comparison of the controller, P1P2MQTT and ESPAltherma.
The controller showed about 40.5–40.7°C and 49.5–49.7°C on the two water temperature screens, plus 45.4°C for the hot water tank. The 20.0°C screen shows a house icon, so it is room temperature; I had previously mislabeled it as outdoor temperature. I didn’t get a clear outdoor air reading. The two water values are likely return and leaving water, but I’ll verify their labels by recording the manual’s display sequence more carefully.
During the same capture, P1P2MQTT’s R3T was about 40.7°C, close to the lower controller water reading. Since R3T is a refrigerant sensor, this is only a numerical match so far, not confirmation that it measures return water.
ESPAltherma’s 0x20 values stayed at off4=35.8, off6=22.8, off10=22.8 and off12=23.3; they did not follow either controller water reading. ESPAltherma continued reporting Fan Only, thermostat OFF and Stop control while P1P2MQTT showed the pump and compressor on and defrost off.
Relevant capture excerpt (local timestamps):

[
  {
    "ts": "2026-10-15T19:22:27+02:00",
    "P1P2MQTT": {
      "Temperature_R3T_Refrigerant": 40.703,
      "Circulation_Pump": 1,
      "Compressor": 1,
      "Defrost_Active": 0
    },
    "ESPAltherma_API": "timeout"
  },
  {
    "ts": "2026-10-15T19:22:37+02:00",
    "ESPAltherma": {
      "20-4 (unknown)": 35.8,
      "20-6 (unknown)": 22.8,
      "20-10 (unknown)": 22.8,
      "20-12 (unknown)": 23.3,
      "Operation Mode": "Fan Only",
      "Thermostat ON/OFF": "OFF",
      "Defrost Operation": "OFF",
      "Operation control mode": "Stop control"
    }
  }
]

Thank you!!!

heatpump-capture-20261015-1924.jsonl.txt

[stav242]

@stav242 Thanks, really useful! Only these differ:

0x001 model type: 07 → 08
0x003 inverter/hot water settings: 00 → 2E
0x062–0x067 spec/EC number: default placeholder → AS1704403-02, EC 23 30
Two quick questions: do you have a hot water tank, and has the indoor unit ever had a board replaced?

@selman61
Yes it's got a hot water tank, and heater and no, never had any board replaced.

from the original Quote

• To supply and install 1 No 16kw Daikin Altherma EKHBRD016ACV1 high temperature Outdoor unit.
• To supply and install 1 No 16kw Daikin Altherma EKHBRD016ACV1+EKBUHAA6V3 high temperature indoor unit.
• To supply and install 1 No Daikin EKHTSU260AC 260ltr domestic hot water cylinder.
• To supply and install 1 No Daikin PCB for use with 3rd party control system.

[raomin]

Thanks @julianbl, that comparison is really useful. It matches what Selman found: the hydrobox port has no water temperature at all. The leaving and return water are only on the outdoor board.

Your capture shows something else: 0x10 never changes. It's the same 16 bytes on every read, and the same on all three of your units. So "Operation Mode", "Thermostat ON/OFF", "Defrost Operation" and "Operation control mode" don't describe this box; they read "Fan Only / OFF / Stop" because those bytes are always zero. I'll take them out of the HT definition. To see the compressor, select "INV Comp. Frequency(Hz)" (0x30): it was at 128 Hz in your survey.

The API timeout is probably your WiFi: the board reports −85 to −93 dBm, which is at the edge. Moving the board or adding an antenna should fix it.

[raomin]

Moving this thread to Discussions: it's the reference for the HT units, still alive with @selman61 and @stav242's dumps, and that is what Discussions are for. The HT definitions are in ESPAltherma 2.

[PiotrBeeScale]

I see that a lot has changed and there’s a light at the end of the tunnel—@raomin hasn’t abandoned support for the older Atherma2 units in his project. Many thanks! I’ve connected an ESP module to the outdoor unit, as that’s the only way to obtain all the necessary data.
I’ll provide an explanation for those interested.
First, you need to unscrew all the bolts securing the top cover and remove it.
Next, unscrew the single bolt at the very bottom that holds the front-right panel in place; you can then remove that panel and set it aside.
I’ve included some photos, marking the location of the X41A port.
It’s a good idea to use a long cable so that the ESP module can be placed outside, ensuring it has a Wi-Fi signal. In my setup, I routed the cable out through the top-right corner (under the top cover)—just make sure the cable is thin and flat, and it’s best to add some extra insulation/protection at that point.

Important: Do not leave screws loose with the intention of tightening them later. Two screws at the rear of the top cover are critical; they stabilize the position of the turbine blades. If these screws are not fully tightened, the blades will rub against the housing.

[PiotrBeeScale]

For the Daikin Altherma 2, you will need long, 1-meter cables terminated with a female JST-EH-5 connector. Since I couldn't find a suitable cable anywhere, I made one myself.
You will need:

• 10-conductor ribbon cable (DuPont style) – 1 meter
• JST-EH-5 connectors (2.54 mm pitch) – available on AliExpress
• 2.54 mm male pin header
• Soldering iron, solder
• Epoxy resin
• Adhesive tape
  Assembly:
  Strip a short section of insulation from the wires at one end, and use small pliers to crimp the metal JST-EH terminals onto each wire. For added reliability, solder the terminal to the wire. [1] Note: Insert a trimmed matchstick into the terminal barrel to prevent solder from flowing inside and clogging it [2]. Slide the completed terminals into the plastic connector housing. Next, solder the connector for the other end of the cable (for the M5StickPlus, this will be a 2.54 mm pitch pin header). Secure the underside of the connector terminals with transparent tape, and apply epoxy resin to the points where the wires meet the connectors [3]. Once the resin has cured, the tape can be removed. The finished cable [4] is reinforced with epoxy resin at the X41A connector end, which makes it much easier to insert into the outdoor unit’s socket—space is quite tight in that area. The M5StickPlus is highly convenient for use with both the outdoor and indoor units, as it can be easily attached to the pump housing using its built-in magnet, with the cable routed to the outside through a gap between the housing segments.
  If you do not feel confident about making such a cable from scratch, you can purchase pre-terminated, short lengths of JST-EH5 connectors on AliExpress and then extend them by soldering on additional wire to reach the desired length.

[raomin]

@selman61 @stav242 @julianbl @SqualeDev @PiotrBeeScale The outdoor unit is in v2.0.0-beta.17.

On the HT the water is only on the outdoor board, so the indoor-only rule doesn't make sense for this series. The new definition, "Altherma(HT ERRQ-ERSQ outdoor unit 11-16kW)", is Selman's map with the two "R134a" fields of the hydrobox block named as what they are, leaving and return water.
ESPAltherma now reads the hydrobox address from 0x40 and asks 0x50 with it (04 40 50 ), as Selman's local build did. It's recognised by the shape of its replies: the HT header, a 21-byte 0x20 and 0x40 answering, no 0x60. Piotr's ERRQ016AAV1 matched the map byte for byte on the registries we already had.

On the outdoor board you get the leaving and return water, outdoor air, discharge, suction and liquid, both pressures with their R410A saturation temperatures, fan, expansion valves, compressor, defrost, errors, and the hydrobox's state and error. The drawing should work on it, and the Home Assistant card follows with 1.0.22.

If you run both boards, give the second one its own MQTT base topic in Settings → MQTT output so they don't overwrite each other. The README's troubleshooting page now describes both ports.

What would help: a survey from the outdoor board on beta.17 (Diagnostics → Heat pump survey, it now includes 0x40 and 0x50), and the two water values next to your remote controller's. Selman, your "?" fields in 0x20 are still there with their question marks, if you ever pin them down.

[stav242]

Survey from my ERSQ016AAV1

have it connected with a second ESPAlthermaODU

{ "v": 1, "fw": "2.0.0-beta.21", "board": "esp32", "protocol": "I", "key": "I|63:------------|60:----|CAP:--|11:------------|00:----", "id": { "iu_eeprom": null, "iu_sw": null, "iu_cap": null, "iu_opt": null, "iu_eeprom_ver": null, "iu_code": null, "ou_eeprom": null, "ou_mpu": "----", "ou_cap": null }, "regs": { "10": "0000000000003C000000000000000000", "11": null, "20": "81009300C4005701FA00B000B60081008000820000", "21": null, "30": "00000000000000800000", "40": "0100", "50": "80010000000000000000000000000000000000", "60": null, "00": "0A010001020201054101", "A0": null, "A1": null }, "detect": { "model": "Altherma(HT ERRQ-ERSQ outdoor unit 11-16kW)", "family": "L", "confidence": "high", "method": "fingerprint", "margin": 0, "candidates": [ { "model": "Altherma(HT ERRQ-ERSQ outdoor unit 11-16kW)", "score": 14 } ] } }

[selman61]

@raomin pinned them down. The ERRQ D-Checker file leaves those three as "German only", but its 0x20 layout is byte-identical to the VRV3S (RXYSQ4-6P) file, which names them:

//{0x20,4,105,2,1,"R6T (subcool hex gas)"},
//{0x20,8,105,2,1,"R3T (suction 1)"},
//{0x20,18,105,2,1,"Heat exchanger liquid temp."},
Live on the ERSQ016:

20-8 reads a few K below outdoor air, which fits the evaporator outlet.
20-18 stays within about 1 K of Low Pressure(T), which fits the evaporator inlet.
20-4 is named from the VRV3S file only. I haven't checked it separately against live data.

The same file fills a few other "German only" gaps:

//{0x10,1,305,1,-1,"Startup control"},
//{0x30,8,307,1,-1,"SV (hot gas)"},
//{0x30,8,305,1,-1,"SV (unload)"},

Checked over 24 h on the live unit (mild weather, ~14 °C outdoor):

Startup control: comes on about 60 s before each compressor start and goes off 30–95 s after it.
SV (unload): on 100 % of the time at 30–49 Hz, mixed at 50–79 Hz, never on at 80 Hz or above. This matches the compressor step table in the ESIE09-08B service manual exactly: Y3S (SVUL) on = unload steps 36–78 Hz, off = full load, with the two overlapping at 52–78 Hz.
SV (hot gas): less sure. It's never on while running, but it comes on in the minute before each start and during the short compressor stops around defrost. The service manual lists Y2S (SVP) as off during stop and pre-start equalisation, and on only for low-pressure protection, so either the name is wrong for this unit or the manual's tables are simplified.

30-8 bit6 (liquid pipe shut, the bit currently in the file) never came on in 24 h. In the ERRQ D-Checker file that bit is flagged hidden (0,0). Bits 7 and 5 are flagged shown (1,1) but left as "German only".

Separately, I can also read the water pump speed from the outdoor board: the hydrobox's DIII-NET E0 frame passes through its RAM once a minute, and the ESP catches it with the read-only memory command ('R', 04 52). The value tracks the pump (it went up when I lowered the ΔT target from 10 K to 5 K; around 3500, likely rpm). The same method also gives inverter current (whole amps only), fin temperature and the remote's room temperature. The buffer addresses are specific to this board's firmware, so other units would need checking. If you're interested, I can open a PR for the definition changes and the capture.

[raomin]

@selman61 thanks, and sorry the names sat for a week. They go into the next beta: R3T (suction 1), Heat exchanger liquid temp., R6T (subcool hex gas), Startup control, SV (unload) and SV (hot gas), with you as co-author. If you had the old "?" values ticked, Home Assistant creates new entities for them.
The DIII reader is a nice piece of work. Could you open it as a pull request against beta? I'd rather review it there, then make a dev build for the ESP32 boards on the same outdoor unit before it goes into a beta. @PiotrBeeScale @stav242 @julianbl, would you try it then?

[julianbl]

yes!

[selman61]

I opened the PR: #630. Tested only on our modified old ESPAltherma build (ESP8266), not on the beta.

[raomin]

Testers wanted: more readings from the HT outdoor unit (@PiotrBeeScale @stav242 @julianbl)

@selman61's reader is now ready in a development build. On the board on the outdoor unit (X41A), it catches the frames the hydrobox and the outdoor unit exchange as they pass through the outdoor controller's memory, and adds values the registries don't give: the pump speed, the remote controller's room temperature, the inverter current, speed and fin temperature, the whole unit's input current and load, and the leaving and return water at a finer resolution. It only reads memory, never writes, and it switches itself off unless it recognises the outdoor controller's software (DP0009, the one on Selman's ERSQ016). It has run daily on his unit (esp8266), but never on an ESP32: that's what we need you for.

To install: System → Firmware update, tick Development builds, Check for an update. Or the preview installer over USB. Only the outdoor board needs it; the board on the hydrobox stays as it is.

What to report after 10 minutes or so:

1. Whether new sensors appeared in Home Assistant on the outdoor device, named "E0: ...", "63: ..." and "RAM: ...". They show up once the reader has found its unit, about 90 s after the start and a few minutes to learn the timing.
2. If none appear: the log (Diagnostics → Log) says why, for instance another controller software. Paste the lines that start with "DIII reader", "E0" or "63".
3. If they appear: do "E0: Leaving water" and "E0: Return water" match the outdoor unit's own leaving and return water, and "E0: Remote room temp" your remote controller?
4. Anything odd in the usual readings: gaps, a slower update, check the errors in the log.

To go back: untick Development builds and Check for an update, or install beta.24 from the web installer.

[stav242]

update

1. no new sensors shown
2. logs shows E0.

0x00 0xa0 0x00 0x00 0x00 0x00 0x62 0x00 0x96 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x03 Querying register 0x20... 0x40 0x20 0x17 0x51 0x00 0x4e 0x00 0x7a 0x00 0xab 0x00 0x8d 0x00 0x7f 0x00 0x8a 0x00 0x5e 0x00 0x5c 0x00 0x50 0x00 0x00 0x24 Querying register 0x30... 0x40 0x30 0x0c 0x00 0x08 0x00 0x00 0x00 0x00 0x80 0x80 0xa8 0x00 0xd3 Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x18 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x38 0x01 0x78 0x00 0x35 0x01 0x00 0x00 0x00 0x00 0x0c Done. Waiting 29635 ms...Sending values in MQTT.E0 outdoor locked, phase 45447 msUpdate check: 2.0.0-beta.24 on the site, this board runs dev-2044f6aQuerying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x00 0xa0 0x00 0x00 0x00 0x00 0x62 0x00 0x96 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x03 Querying register 0x20... 0x40 0x20 0x17 0x4f 0x00 0x4c 0x00 0x7b 0x00 0xa8 0x00 0x8e 0x00 0x7d 0x00 0x89 0x00 0x5d 0x00 0x5b 0x00 0x4c 0x00 0x00 0x32 Querying register 0x30... 0x40 0x30 0x0c 0x00 0x08 0x00 0x00 0x00 0x00 0x80 0x80 0xa8 0x00 0xd3 Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x18 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x38 0x01 0x78 0x00 0x35 0x01 0x00 0x00 0x00 0x00 0x0c Done. Waiting 29634 ms...Sending values in MQTT.E0 hydro locked, phase 25947 msQuerying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x01 0xa0 0x00 0x00 0x00 0x00 0x63 0x00 0xbf 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0xc8 Querying register 0x20... 0x40 0x20 0x17 0x4d 0x00 0x46 0x00 0x7a 0x00 0xbf 0x00 0x82 0x00 0x5f 0x00 0x8a 0x00 0x56 0x00 0x99 0x00 0x45 0x00 0x00 0x1d Querying register 0x30... 0x40 0x30 0x0c 0x39 0x09 0x27 0x00 0x00 0x00 0x80 0x00 0xa8 0x00 0xf2 Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x18 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x1a 0x01 0x77 0x00 0x21 0x01 0x00 0x00 0x00 0x00 0x3f Done. Waiting 29557 ms...Sending values in MQTT.Querying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x01 0xa0 0x00 0x00 0x00 0x00 0x63 0x00 0xd3 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0xb4 Querying register 0x20... 0x40 0x20 0x17 0x4c 0x00 0x38 0x00 0x78 0x00 0x2f 0x01 0x54 0x00 0x

3. some errors
   0x40 0x50 0x15 0x80 0x01 0x18 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x41 0x01 0x55 0x00 0x51 0x01 0xd0 0x07 0x00 0x00 0x33 Done. Waiting 26783 ms...Sending values in MQTT.Starting heat pump survey...Querying register 0x60... Error 0x15 0xEA returned from HPQuerying register 0x60... Error 0x15 0xEA returned from HPQuerying register 0x10... 0x40 0x10 0x12 0x01 0x80 0x00 0x00 0x00 0x00 0x63 0x00 0xc4 0x00 0x00 0x00 0x00 0x13 0x00 0x00 0xe2 Querying register 0x60... Error 0x15 0xEA returned from HPQuerying register 0x60... Error 0x15 0xEA returned from HPQuerying register 0x10... 0x40 0x10 0x12 0x01 0x80 0x00 0x00 0x00 0x00 0x63 0x00 0xc4 0x00 0x00 0x00 0x00 0x13 0x00 0x00 0xe2 Querying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x11... Error 0x15 0xEA returned from HPQuerying register 0x11... Error 0x15 0xEA returned from HPQuerying register 0x20... 0x40 0x20 0x17 0x4c 0x00 0x2d 0x00 0x54 0x00 0xd8 0x01 0x5e 0x00 0x54 0x00 0x81 0x00 0x54 0x00 0x9e 0x00 0x2b 0x00 0x00 0x92 Querying register 0x21... Error 0x15 0xEA returned from HPQuerying register 0x21... Error 0x15 0xEA returned from HPQuerying register 0x30... 0x40 0x30 0x0c 0x24 0x05 0x36 0x00 0x07 0x00 0x80 0x00 0x28 0x00 0x75 Querying register 0xa0... Error 0x15 0xEA returned from HPQuerying register 0xa0... Error 0x15 0xEA returned from HPQuerying register 0xa1... Error 0x15 0xEA returned from HPQuerying register 0xa1... Error 0x15 0xEA returned from HPQuerying register 0x40... 0x40 0x40 0x04 0x01 0x00 0x7a Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x18 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x41 0x01 0x55 0x00 0x51 0x01 0xd0 0x07 0x00 0x00 0x33 Survey done: protocol I, 11 registries.Querying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x01 0x80 0x00 0x00 0x00 0x00 0x64 0x00 0xc4 0x00 0x00 0x00 0x00 0x13 0x00 0x00 0xe1 Querying register

4. nothing noticablly different

[julianbl]

Just added a 2nd ESP32 with ESPAltherma to my outdoor unit!
It got detected automatically. Here is the survey:

{
"v": 1,
"fw": "2.0.0-beta.23",
"board": "esp32c3",
"protocol": "I",
"key": "I|63:------------|60:----|CAP:--|11:------------|00:----",
"id": {
"iu_eeprom": null,
"iu_sw": null,
"iu_cap": null,
"iu_opt": null,
"iu_eeprom_ver": null,
"iu_code": null,
"ou_eeprom": null,
"ou_mpu": "----",
"ou_cap": null
},
"regs": {
"10": "01800000000096000901000000130000",
"11": null,
"20": "64003E007000D30148004D00C3005500B0003E0000",
"21": null,
"30": "24072000070080002800",
"40": "0100",
"50": "80011800C290A04001B801CF000302D0070000",
"60": null,
"00": "0A010001020201054101",
"A0": null,
"A1": null
},
"detect": {
"model": "Altherma(HT ERRQ-ERSQ outdoor unit 11-16kW)",
"family": "L",
"confidence": "high",
"method": "fingerprint",
"margin": 0,
"candidates": [
{
"model": "Altherma(HT ERRQ-ERSQ outdoor unit 11-16kW)",
"score": 14
}
]
}
}

Qq. I added different base topic (espaltherma-odu) to the mqtt settings, and I see it in the mqtt devices in HA, but the dashboard does not show any information from this device. Is it there any setting in the dashboard I can set to it uses both? Thank you!

[raomin]

@julianbl the protocol follows the model: choose "Altherma(HT EKHBRD-ERRQ series 11-16kW protocol S)" in Setup and save. "Detect again" goes back to protocol I by design, because auto-detection keeps I when the board answers both. Two questions: which EKHBRD is yours (the label on the indoor unit), and could you paste the indoor board's survey (Diagnostics → Heat pump survey) with the protocol S model chosen? Note that this model only reads the second stage, both pressures and the discharge and liquid temperatures. The water values come from the outdoor board.

[PiotrBeeScale]

I tried to bring up the topic of Altherma 2 in the "ESPAltherma v2! #599" discussion thread, but it got too crowded with development topics related to Altherma 3, so I’m returning here—back to familiar ground! :)
I’ve installed one ESP unit on the ERRQ and another on the EKHBRD. I assigned them the identifiers espaltherma-odu and espaltherma-idu, respectively. In Home Assistant, two devices will appear via MQTT, each with its own entities: "Daikin Altherma via ESPAltherma (espaltherma-idu)" and "Daikin Altherma via ESPAltherma (espaltherma-odu)."
I did some work with an AI, and through our combined efforts, we managed to display the data retrieved from the ERRQ and EKHBRD units on a diagram.
Once you have the ESP units installed on your ERRQ and EKHBRD, here is what you need to do in Home Assistant:

1. Install the espaltherma-card and activate it according to the provided instructions.
2. Create a new dashboard: Settings -> Dashboards -> Add dashboard -> New dashboard from scratch (enter a title—e.g., "EKHBRD"—choose an icon, and click "Create").
3. Select "Edit dashboard" -> "Raw configuration editor" and paste the YAML code (the starter file is attached).

That’s a starting point. Perhaps someone could arrange and group these elements in a sensible way on the screen?

Key parameters (shortcuts) that you can override:

YAML key:
out - Outdoor temperature
lw1 - Water outlet temperature before the backup heater
lw2 - Water outlet temperature after the backup heater
inlet - Water return temperature (from the system to the heat pump)
tank - Current domestic hot water (DHW) tank temperature
mixed - Mixed water temperature (required for the 2nd zone underfloor heating graphic)
v3 - Three-way valve (switching between space heating and DHW heating)
inv - Inverter (compressor) frequency – triggers the fan animation
flow - Water flow rate in liters per minute
bar - System water pressure

views:
  - title: ESPAltherma
    type: panel
    cards:
      - type: vertical-stack
        cards:
          - type: custom:espaltherma-card
            stats: top
            entities:
              lw1: sensor.espaltherma_idu_discharge_pipe_temp
              inlet: sensor.espaltherma_odu_inlet_water_temp_hydrobox
              out: sensor.espaltherma_odu_r1toutdoor_air_temp
              inv: sensor.espaltherma_odu_inv_comp_frequencyhz
              mode: sensor.espaltherma_odu_operation_mode
              r3t: sensor.espaltherma_idu_r134a_liquid_temp
              lw2: sensor.espaltherma_odu_leaving_water_temp_hydrobox
              v3: binary_sensor.espaltherma_idu_4_way_valve
          - type: grid
            square: false
            columns: 5
            cards:
              - type: tile
                entity: sensor.espaltherma_odu_r1toutdoor_air_temp
                name: Outside
              - type: tile
                entity: sensor.espaltherma_odu_inv_comp_frequencyhz
                name: Compressor ODU
              - type: tile
                entity: sensor.espaltherma_idu_inv_comp_frequencyhz
                name: Compressor IDU
              - type: tile
                entity: sensor.espaltherma_odu_operation_mode
                name: Mode
              - type: tile
                entity: binary_sensor.espaltherma_idu_crankcase_heater
                name: Aux. Heater
              - type: tile
                entity: sensor.espaltherma_idu_discharge_pipe_temp
                name: Discharge IDU
              - type: tile
                entity: binary_sensor.espaltherma_idu_4_way_valve
                name: 4 Way Valve
          - type: history-graph
            title: Water temperature
            hours_to_show: 24
            entities:
              - entity: sensor.espaltherma_odu_leaving_water_temp_hydrobox
                name: Heat pump out
              - entity: sensor.espaltherma_odu_inlet_water_temp_hydrobox
                name: Return
              - entity: sensor.espaltherma_odu_r1toutdoor_air_temp
                name: Outside
          - type: history-graph
            title: Compressor
            hours_to_show: 24
            entities:
              - entity: sensor.espaltherma_odu_inv_comp_frequencyhz
                name: Compressor frequency

[julianbl]

Thank you!
And if I may ask, how are you pulling the values from the devices? how do you configure them and set the definitions? I'm missing most of the values you are using.

[stav242]

goto your ESPaltherma local device webpages, and enable all the values.. on both indoor unit and outdoor.
they will be pushed via mqtt and automatically includeed in HA.

[stav242]

i also used AI to write a heatpump advisor... using all the data, suggest what its doing, how its performing and advice any changes. this will most likell not work as its got other device sensors... but you get the idea.

add it to your main configuration.yaml

heatpump_advisor.txt

[raomin]

whoo that's pretty cool @stav242! A very nice idea! I would add a mode gate at the beggining to avoid alerts when defrost, or first minute of run...
I believe it would only work for a specific model... It would have been great to generalise it. I'll think about it...

[stav242]

another thing ive done, as the controller is not online or accessible in HA for the WD Curve, is to set some number values in HA, where i can record my controller settings. allows me to check how the system is working based on my WD curve expected temperatures. i calc the WD curve temp then to show on a graph.

{% set t_out = states('sensor.openweathermap_temperature') | float(0) %}

{# --- CONFIGURATION START --- #}
{# High Temp Point: 16C outside -> 40C Water (Cooler Target) #}
{% set Hi_A = states('input_number.heatpump_hi_a') | float(16) %}
{% set Hi_Ti = states('input_number.heatpump_hi_ti') | float(40) %}

{# Low Temp Point: -5C outside -> 45C Water (Hotter Target) #}
{% set Lo_A = states('input_number.heatpump_lo_a') | float(-5) %}
{% set Lo_Ti = states('input_number.heatpump_lo_ti') | float(45) %}
{# --- CONFIGURATION END --- #}

{# Safety Check: Prevent division by zero #}
{% if Hi_A == Lo_A %}
{{ Hi_Ti }}
{% else %}
{# Calculate Slope (m) = (Change in Water Temp) / (Change in Outside Temp) #}
{% set m = (Hi_Ti - Lo_Ti) / (Hi_A - Lo_A) %}

{# Calculate Target (y = mx + c) #}
{# We anchor this to the Low Ambient Point (Lo_A) #}
{% set target = Lo_Ti + m * (t_out - Lo_A) %}

{# Output the result clamped to safety limits (30C to 55C) #}
{{ [30, [target, 55]|min]|max | round(1) }}
{% endif %}

[selman61]

HT outdoor unit (ERSQ/ERRQ + EKHBRD): read-only DIII E0/63 values

https://github.com/selman61/ESPAltherma/tree/diii-comm (on beta 1ca3797)

It reads leaving/return water every 60 s, plus room temp, pump, inverter values and the outdoor input current, from the outdoor RAM over X41A. It only reads, and only on outdoor software DP0009. It also names a few HT outdoor fields (commented out).

Not tested with the beta on a unit: our outdoor board is an ESP8266. It has been running since October on our own modified build of the old ESPAltherma (ESP8266). On the beta it builds and passes a unit test. Feel free to try it.

[stav242]

Logs shows DII Reader... heres a snip of that section. but dont see E0: or 63: bf 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x7c Querying register 0x20... 0x40 0x20 0x17 0x50 0x00 0x51 0x00 0x7b 0x00 0xb8 0x00 0x8f 0x00 0x81 0x00 0x8d 0x00 0x5f 0x00 0x5e 0x00 0x52 0x00 0x00 0x08 Querying register 0x30... 0x40 0x30 0x0c 0x00 0x00 0x00 0x00 0x00 0x00 0x80 0x80 0x08 0x00 0x7b Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x10 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x3c 0x01 0x7e 0x00 0x39 0x01 0x00 0x00 0x00 0x00 0x06 Done. Waiting 29554 ms...Sending values in MQTT.Firmware update started (esp32-ota.bin)Firmware update done, rebootingQuerying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x00 0x00 0x00 0x00 0x00 0x00 0x62 0x00 0xbf 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x7c Querying register 0x20... 0x40 0x20 0x17 0x50 0x00 0x4f 0x00 0x7c 0x00 0xaf 0x00 0x8f 0x00 0x81 0x00 0x8c 0x00 0x5f 0x00 0x5e 0x00 0x54 0x00 0x00 0x11 Querying register 0x30... 0x40 0x30 0x0c 0x00 0x00 0x00 0x00 0x00 0x00 0x80 0x80 0x08 0x00 0x7b Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x10 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x3c 0x01 0x7e 0x00 0x39 0x01 0x00 0x00 0x00 0x00 0x06 Done. Waiting 29610 ms...Telemetry sent (200). Thank you!Sending values in MQTT.DIII reader: ready, software DP0009_003Sending HA discovery: 68 sensors, 0 removed, 28341 bytesQuerying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x00 0x00 0x00 0x00 0x00 0x00 0x62 0x00 0xbf 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x7c Querying register 0x20... 0x40 0x20 0x17 0x52 0x00 0x50 0x00 0x7a 0x00 0xab 0x00 0x8e 0x00 0x7f 0x00 0x8c 0x00 0x5e 0x00 0x5e 0x00 0x53 0x00 0x00 0x19 Querying register 0x30... 0x40 0x30 0x0c 0x00 0x00 0x00 0x00 0x00 0x00 0x80 0x80 0x08 0x00 0x7b Querying register 0x50... 0x40 0x50 0x15 0x80 0x01 0x10 0x00 0xc2 0x90 0xa0 0xdc 0x00 0x3c 0x01 0x7e 0x00 0x39 0x01 0x00 0x00 0x00 0x00 0x06 Done. Waiting 29632 ms...Sending values in MQTT.Querying register 0x00... 0x40 0x00 0x0c 0x0a 0x01 0x00 0x01 0x02 0x02 0x01 0x05 0x41 0x01 0x5b Querying register 0x10... 0x40 0x10 0x12 0x00 0x00 0x00 0x00 0x00 0x00 0x62 0x00 0xbf 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x7c Querying register 0x20... 0x40 0x20 0x17 0x51 0x00 0x4e 0x00 0x7b 0x00 0xad 0x00 0x8d 0x00 0x7f 0x00 0x8a 0x00 0x5f 0x00 0x5e 0x00 0x51 0x00 0x00 0x1d Querying register 0x30... 0x40 0x30 0x0c 0x00 0x00 0x00

…

On Tue, 3 Nov 2026 at 22:57, Raomin ***@***.***> wrote: *Testers wanted: more readings from the HT outdoor unit* ***@***.*** <https://github.com/PiotrBeeScale> @stav242 <https://github.com/stav242> @julianbl <https://github.com/julianbl>) @selman61 <https://github.com/selman61>'s reader is now ready in a development build. On the board on the *outdoor unit* (X41A), it catches the frames the hydrobox and the outdoor unit exchange as they pass through the outdoor controller's memory, and adds values the registries don't give: the pump speed, the remote controller's room temperature, the inverter current, speed and fin temperature, the whole unit's input current and load, and the leaving and return water at a finer resolution. It only reads memory, never writes, and it switches itself off unless it recognises the outdoor controller's software (DP0009, the one on Selman's ERSQ016). It has run daily on his unit (esp8266), but never on an ESP32: that's what we need you for. To install: System → Firmware update, tick *Development builds*, Check for an update. Or the preview installer <https://preview.espaltherma.pages.dev/> over USB. Only the outdoor board needs it; the board on the hydrobox stays as it is. What to report after 10 minutes or so: 1. Whether new sensors appeared in Home Assistant on the outdoor device, named "E0: ...", "63: ..." and "RAM: ...". They show up once the reader has found its unit, about 90 s after the start and a few minutes to learn the timing. 2. If none appear: the log (Diagnostics → Log) says why, for instance another controller software. Paste the lines that start with "DIII reader", "E0" or "63". 3. If they appear: do "E0: Leaving water" and "E0: Return water" match the outdoor unit's own leaving and return water, and "E0: Remote room temp" your remote controller? 4. Anything odd in the usual readings: gaps, a slower update, check the errors in the log. To go back: untick Development builds and Check for an update, or install beta.24 from the web installer <https://espaltherma.pages.dev/>. — Reply to this email directly, view it on GitHub <#624?email_source=notifications&email_token=ABOJGGW6RLTSTIPJV4JOX635XJPGLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTHA2TCNJRUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19385151>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOJGGT3GT77TUW5G6HLGM35XJPGLAVCNFSNUABIKJSXA33TNF2G64TZHMZTEMZRHAYTMOJUHNCGS43DOVZXG2LPNY5TCMJRGM2DIMJXUF3AE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[raomin]

@stav242 thanks, that is the first ESP32 it ever ran on, and it got further than it looks: "DIII reader: ready, software DP0009_003" means it recognised your outdoor controller, the same software as Selman's, and the discovery line right after it carried its sensors. What is missing is a catch of the frames. @selman61 is right! The hydro frame passes through the controller's memory once a minute and stays there less than a second, so the first values come after the first catch, a few minutes in, and the lock after two catches a minute apart, which the log reports as "E0 hydro locked" and "E0 outdoor locked". The 63 frame only comes every five minutes or so. Your excerpt stops about a minute after "ready", so it had not had its chance yet.

Could you look again now that it has run a while?

Settings → Devices & services → the outdoor board's device, its entity list: are there entries named "E0: ..." and "63: ..."? They exist as "Unknown" until the first catch, so they do not show on a dashboard by themselves.
Diagnostics → Log: any line with "E0 hydro locked", "E0 outdoor locked", "63 locked", or "lost, relearning".
If after fifteen minutes there is still no "locked" line and the E0 entities stay unknown, paste the log of those fifteen minutes and @selman61 and I will look at the timing on your board.
Nothing changed in the usual readings, which is the other good news.

[stav242]

its been running from 23:13 to 00:01
logs.txt

[selman61]

Thanks! No "lost, relearning" in 35 min, and the poll timing shows it waits for the E0 windows, so it looks locked. The "locked" lines were before this part of the log. Could you check in HA that E0: Sync is 3 and the E0 / 63 / RAM values are not null?

[stav242]

checking in MQTT explorer i see

"E0: Leaving water (C)": 35,
"E0: Return water (C)": 33,
"E0: Remote room temp (C)": 22,
"E0: Pump": 3075,
"E0: EVL (pls)": 1140,
"E0: EVH (pls)": 150,
"E0: INV current (A)": 7,
"E0: INV speed (rps)": 18,
"E0: INV fin temp (C)": 17,
"E0: Sync": 3,
"63: Leaving water (C)": null,
"63: Return water (C)": null,
"63: R410A liquid (C)": null,
"63: BRC1 room temp (C)": null,
"RAM: Outdoor input current (A)": 2.93,
"RAM: Outdoor rated current (A)": 27,
"RAM: Outdoor load (%)": 10,

[selman61]

The 63 values were null because the check expected my system id and BRC1 value, and it dropped the frame without a log line. It's fixed in the diii-comm branch (also PR #631). If 63 is still null after ~15 min, look for a 63 rejected / 63REJ line in the log and paste it.

E0: Pump is Daikin's "pump revolution speed", but I'm not sure it's a real rpm. From my energy balance, flow ≈ 5.5 L/min per 1000 of E0: Pump (range 4.5–6.6), so your 3075 would be ~17 L/min. Since you have a real flow sensor, could you post a few pairs of E0: Pump and measured flow at different pump values? That would check the factor.

[stav242]

no 63, rejected, or 63REJ still got... "63: Leaving water (C)": null, "63: Return water (C)": null, "63: R410A liquid (C)": null, "63: BRC1 room temp (C)": null, E0 pump was 0 when flow rate was 0. E0 Pump was "E0: Pump": 4100, when flow rate was 23.55 L/min I need to get some sleep, ill be back online tomorrow .

…

On Wed, 4 Nov 2026 at 00:21, selman61 ***@***.***> wrote: The 63 values were null because the check expected my system id and BRC1 value, and it dropped the frame without a log line. It's fixed in the diii-comm branch (also PR #631 <#631>). If 63 is still null after ~15 min, look for a 63 rejected / 63REJ line in the log and paste it. E0: Pump is Daikin's "pump revolution speed", but I'm not sure it's a real rpm. From my energy balance, flow ≈ 5.5 L/min per 1000 of E0: Pump (range 4.5–6.6), so your 3075 would be ~17 L/min. Since you have a real flow sensor, could you post a few pairs of E0: Pump and measured flow at different pump values? That would check the factor. — Reply to this email directly, view it on GitHub <#624?email_source=notifications&email_token=ABOJGGTTS5QJNXZC5SH5QKD5XJY63A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTHA3DIMBRUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19386401>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOJGGS2OPXLCUNPFNSVHA35XJY63AVCNFSNUABIKJSXA33TNF2G64TZHMZTEMZRHAYTMOJUHNCGS43DOVZXG2LPNY5TCMJRGM2DIMJXUF3AE> . You are receiving this because you were mentioned.Message ID: ***@***.***>