Works with Daikin Altherma 3 R ECH2O (ERGA06EAV3H / EHSXB08P50EF)

[forTT78]

Hi, here is my short installation note and big thank you for the project.

My System:
Indoor: EHSXB08P50EF
Outdoor: ERGA06EAV3H

P1P2MQTT directly connected to the P1P2 port via 3 m cable.

Works! 👍

[universal-dilettant]

Just jumping on this discussion: what is the meaning of "works!"? Works as in reading parameters or works as in writing commands?
I have the same Daikin HW as mentioned before, had acquired the P1P2mqtt box from Arnold in Jan this year and installed some days ago. After upgrading to the latest FW for both ESP and atmega, the box shows up in mqtt and can be accessed via telnet alright. However, and this is maybe a dumb question: I don't succeed to send commands like i.e. "Heating on" (= E 35002F01 according to the documentation for E-series) via telnet. Any help is appreciated.

[Arnold-n]

Your bridge is not yet operating in control mode. If you enter "L1" it should start control mode, and you can enter commands like "E35002F01".

[forTT78]

Yes, "heating on" and controlling works, e.g. like adjusting the LWT temperature. I use home assistant for it.

[universal-dilettant]

Works! At least, to start the heat pump alright. Sometimes, you can't see the wood for the trees. Thank you for the hint.

However, next question. Is it normal to get those messages after enabling command mode, like:
paramNr 0x017C > expected nr_params 380 for packetType 0x35
paramNr 0x00AF > expected nr_params 175 for packetType 0x3B

[Arnold-n]

Daikin continues to increase the number of parameters reported in newer models, which causes these error messages. E-series firmware v0.9.54rc4 should resolve this error message.

[forTT78]

Only flashing of the new bridge firmware necessary, right?
Directly via the web portal.

[Arnold-n]

Indeed!

[forTT78]

Thank you. Up and running:

[ESP] 2024-10-11 15:26:12 P1P2MQTT bridge v0.9.54rc4
[ESP] 2024-10-11 15:26:12 Compiled Oct 11 2024 13:30:30 for Daikin E-Series

[universal-dilettant]

Flashed alright.

If I may (mis-?) use this thread again: what is the meaning of
Throttling at 70 ... 1?

[Arnold-n]

It throttles outgoing MQTT traffic during the first 100s after boot/reconnection/D3/... to prevent MQTT output buffer overruns.