search

raomin / ESPAltherma

Monitor your Daikin Altherma / ROTEX heat pump with ESP32
MIT License
317 stars 105 forks source link

Support for Altherma 3 EDLA #328

Open arc12 opened 8 months ago

arc12 commented 8 months ago

Is this unit supported? https://www.daikin.co.uk/en_gb/products/product.html/edla04-08e3v3.html I consulted setup.h but none of the options matched.

Thanks in advance...

IamMattM commented 8 months ago

I'll be interested to verify this as well as I expect to have this same Altherma 3 EDLA monoblock model installed in the not too distant future by Octupus Energy UK.

Alibloke commented 8 months ago

It appears to be, just not listed in the setup.h file explicitly: https://github.com/raomin/ESPAltherma/blob/main/include/def/ALTHERMA(EBLA-EDLA%20%20EWAA-EWYA%20D%20SERIES%209-16KW).h

pokery commented 7 months ago

I got it working with the EDLA09DA3V3 in the UK which is essentially the same unit but a different size I think.

The only thing that threw me was that the voltage value ("Voltage (N-phase) (V)") doesn't seem to be in any of the locations mentioned in various issues on here. If you're wanting to calculate the COP, you can hard code the UK voltage or use another HA sensor (ours is using the live voltage from our Powerwall).

greem commented 6 months ago

I've just created a PR for my changes to the def file for an EDLA09DA3V3 installed by Octopus Energy.

https://github.com/raomin/ESPAltherma/pull/372

As stated in the PR, the 'Voltage (V)' value needs work but the important bits like flow rates, inlet/outlet temps etc seem sane and match the basic info provided by the indoor unit/controller and the bits reported in the Onecta app or HomeAssistant integration.

raomin commented 5 months ago

@simonebortolin suggested that the voltage was actually double. Can you check if using this as definition for the voltage gives accurate result? {0x21,4,111,2,-1,"Voltage (V)"},

Converter 111 would make *0.5 for the value.

greem commented 5 months ago

Sadly I removed the template sensor I had for the voltage reading, so I've no graphs for this :( however:

Observation is that both 'Voltage (V)' tracks 'INV fin temp.' multiplied by 10, and that 'Voltage (N-Phase) (V)' tracks 'INV secondary current (A)' also multiplied by 10:

'Voltage (V)' == 'INV fin temp.' * 10 'Voltage (N-Phase) (V)' == 'INV secondary current (A)' * 10

simonebortolin commented 5 months ago

Keep calm.

You are using the wrong definition of Voltage (V) (0x21,2) that has already been established. Since the register is the same of the ampere.

Use the other one (0x21,4) and divide by 0.5 or 0.7.

0x21,0 ampere before inverter 0x21,2 ampere after inverter 0x21,4 voltage after inverter

@raomin can you fix de default.h file?

simonebortolin commented 5 months ago

@simonebortolin suggested that the voltage was actually double. Can you check if using this as definition for the voltage gives accurate result? {0x21,4,111,2,-1,"Voltage (V)"},

Converter 111 would make *0.5 for the value.

I'm not sure of factor 0.5 and arent the correct converter since

case 101:
            dblData = (double)getSignedValue(data, num, 0);

case 111:
            dblData = (double)getSignedValue(data, num, 1) * 0.5;
simonebortolin commented 5 months ago

@raomin

with the new files of the new version of d-checker 0x21,4,105,2,1,"INV fin temp."

swalsh11 commented 4 months ago

I am logging the output for the 3way valve, to try and determine when DHW is called, however, the signal never changes, IS anyone else seeing this? or is there another way to see DHW?

greem commented 4 months ago

I am logging the output for the 3way valve, to try and determine when DHW is called, however, the signal never changes, IS anyone else seeing this? or is there another way to see DHW?

I've just created a template binary sensor following the attribute "3way valve(On:DHW Off:Space)", which will next change state (in theory!) tomorrow morning when the schedule runs. Unless the kids get home and use all the water showering after school :)

swalsh11 commented 4 months ago

Looks like I Made a mess of my template.yaml, I have it working now.

abmantis commented 3 months ago

@simonebortolin why you mention 0.7 for INV fin temp? Also, isn't INV fin temp the temperature of the inverter board fin?

simonebortolin commented 3 months ago

@simonebortolin why you mention 0.7 for INV fin temp? Also, isn't INV fin temp the temperature of the inverter board fin?

Because it was thought to be the tension.

abmantis commented 3 months ago

@simonebortolin why you mention 0.7 for INV fin temp? Also, isn't INV fin temp the temperature of the inverter board fin?

Because it was thought to be the tension.

But why 0.7?

simonebortolin commented 3 months ago

@simonebortolin why you mention 0.7 for INV fin temp? Also, isn't INV fin temp the temperature of the inverter board fin?

Because it was thought to be the tension.

But why 0.7?

Please read old message. I wrote that I thought that value if it was really the voltage (which it isn't!!!!) was to be reduced by 0.5 or 0.7 (sqrt(2)/2, which if you know how AC voltage works you know why).

Now there is no point in applying this value since we finally know that this figure is a temperature and not a voltage.

Now what temperature it represents I do not care, it is an internal temperature of the inverter, I do not care more than that.

abmantis commented 3 months ago

@simonebortolin why you mention 0.7 for INV fin temp? Also, isn't INV fin temp the temperature of the inverter board fin?

Because it was thought to be the tension.

But why 0.7?

Please read old message. I wrote that I thought that value if it was really the voltage (which it isn't!!!!) was to be reduced by 0.5 or 0.7 (sqrt(2)/2, which if you know how AC voltage works you know why).

Now there is no point in applying this value since we finally know that this figure is a temperature and not a voltage.

Now what temperature it represents I do not care, it is an internal temperature of the inverter, I do not care more than that.

I already read the old comments, that is why I was asking "why 0.7 (sqrt(2)/2)?". I don't "know AC voltage", otherwise I wouldn't be asking. I was just curious about where that value comes from.

If that value is not voltage and EDLA is supported (that I can confirm), this issue can be closed I guess.

simonebortolin commented 3 months ago

"know AC voltage", "why 0.7 (sqrt(2)/2)?"

JFK

RMS voltage = 0.7 Peak Voltage

image

what we call 220/380/110V is RMS voltage

If that value is not voltage and EDLA is supported (that I can confirm)

this has been discovered for a long time. and anyway the values, some of them change from HP to HP and generation to generation.

acabadora commented 3 months ago

is EBLA09DV3 same model with the one of discussion in this topic? and does it share compatibility?

greem commented 2 months ago

Looks like I Made a mess of my template.yaml, I have it working now.

Can you tell us what you did? If I refer to the state_attr for '3way valve(On:DHW Off:Space)', I always get null as a result.

swalsh11 commented 2 months ago

Try this

template.yaml

On Mon 15 Apr 2024, 14:49 Graeme Fowler, @.***> wrote:

Looks like I Made a mess of my template.yaml, I have it working now.

Can you tell us what you did? If I refer to the state_attr for '3way valve(On:DHW Off:Space)', I always get null as a result.

— Reply to this email directly, view it on GitHub https://github.com/raomin/ESPAltherma/issues/328#issuecomment-2056909899, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP6FYJOPDCSTD7JJ6N4LF5DY5PLGLAVCNFSM6AAAAAA524W3I6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJWHEYDSOBZHE . You are receiving this because you commented.Message ID: @.***>

greem commented 2 months ago

Dammit! The underscore. Name has "3way valve(On:DHW Off:Space)" but the sensor has "3way valve(On:DHW_Off:Space)".

I feel rather daft now! Thanks for opening my eyes to a rather obvious typo.