THZ / LWZ Tecalor Stiebel Eltron Heizung

[belu]

Ok, es ist wirklich so ich konnte es jetzt an mehreren Stellen in der Log zum Echtzeit verbrauch beweisen es wird immer 1,4 mehr gezählt und angegeben als er auf dem Zähler hat...

Immer...
Da braucht man sich nicht zu wundern das man einen scheiss COP hat..

[willybauss]

anrufen würde ich trotzdem. Vielleicht ist es ja ein Hardwareproblem.

[belu]

Ok, ich weis nun auch woher die Zahl kommt... War jetzt nach der Arbeit nochmal kurz an der Heizung. Je nach Leistung ist der Faktor 1,39 bis 1,41 höher, rund also 1,4...

Ist ne THZ 304, wenn ich mir die Leistungsdaten der THZ 404 anschaue ist die Wärmepumpe genau um diesen Faktor größer also in der elektrischen aufnahme...

Da ist echt schwer ein Bug drin. Mich würde ja mal intressieren wie sie die Leistung bestimmen. Es gibt keine Sensoren, hatte zuerst die Vermutung das da ein falscher Wandler drin ist.
War mutig und habe der Anlage gesagt sie ist ne THZ 404 ich mein ist ja baugleich bis auf den Verdichter.
Angemacht Warmwasser bereitet und siehe da... Noch mehr Leistung... nochmal um den Faktor 1,4 erhöht. Das erklärt so einiges.
Da ist ein Faktor auf dem Faktor...

Was mir noch aufgefallen ist wenn ich es auf THZ 404 sol stelle ist die Software 539 wie bei Peter.. Das heißt die Software ist identisch.
Man kann auch aus der THZ eine LWZ machen... Irgendwie schon komisch..
Ich werde mich am Montag mal bemühen in die Entwicklung durch zu kommen und hoffe das ich da irgendwen erreiche mit schlechtem Gewissen aus das sich dann Kapital für uns schlagen lässt...

[willybauss]

... habe der Anlage gesagt sie ist ne THZ 404
... Man kann auch aus der THZ eine LWZ machen...

Interessant. Wie machst Du das?

[belu]

@willy, ich hab im Punkt Inbetriebnahme Modell drin. Das kann man verändern.

[peter456]

done
v124 uploaded
history register pathed for peter
please test tomorrow

Hallo immi,
das update auf V0124 funktioniert.
Vielen Dank.
Die Werte stimmen mit meiner LWZ überein.
(operatingHours1: 1377 operatingHours2: 1385 heatingHours: 10309 DHWhours: 3581 coolingHours: 1 )

Bei meiner ist es ja möglich die Parameter P01-P12 auszulesen.
Kann man diese Parameter über FHEM auch verändern?
Gruß
Peter

[immi]

Kann man diese Parameter über FHEM auch verändern?

I am quite sure it is possible to change reg 17, but I would wait some weeks, untill when you are more familiar with fhem, and it is not so cold. I cannot debug it, before giving it to you. I would suggest that you remind me in 8 weeks.

[peter456]

Alles klar.

[belu]

@ Immi , what do you think this can be the energy it wrong counting ? I just always 1.4 times more energy to electrical counters as on the calibrated meter . Even sglobal actualPower_Pel is always 1.4 times higher than the current performance on the calibrated meter .
This also explains why I always such a damn bad COP have ...

[immi]

belu
for me it is not clear, if I decode actualPower_Pel correctly for your new firmware.
In my firmware (4.39), I checked it against an old service software.
If also the service software from tecalor reads 1.4 more than your calibrated meeter, then also the energy count could be wrong.

The only way to be sure 100% is:
- to get the service software from tecalor/se (which I do not have for your new firmware)
or even better
- to get a full documentation of the registers from tecalor/se

[immi]

in Line 77
"p15RoomInfluenceHC1"   => {cmd2=>"0B010F", argMin => "0", argMax => "100", type =>"0clean", unit =>" %"},

Do u have a devisor /10 inside after %? In the Manual THZ 304 P15 min value 0 and max 10.

Willy, Belu
I remember an unfinished discussion on this parameter.
Do you prefer it in % (more readable, like flow-proportion,  like in the display) or from 1..10 (like in the manual)?
100% full-infl and 0% empty   -vs-  10 full-infl and 0 empty
immi

[godmorgon]

@ Immi , what do you think this can be the energy it wrong counting ? I just always 1.4 times more energy to electrical counters as on the calibrated meter . Even sglobal actualPower_Pel is always 1.4 times higher than the current performance on the calibrated meter .
This also explains why I always such a damn bad COP have ...

The electrical energy values of my 404SOL match the values of the electrical meter pretty good. Though, I would say that the heat values exceed the expected values by approximately 40 %. From these values the COP would be 4.7-4.8. I would expect it somewhere in the area of 3.2-3.4 (for the temperature range of -2°C .. +2 °C). As far as I know the heat metering in the heat pump is based on discrete sensors (temperature, flow rate) which are not calibrated. Therefore, I think that the internal sensors provide messy data for the computation. Garbage in, garbage out.

[willybauss]

@willy, ich hab im Punkt Inbetriebnahme Modell drin. Das kann man verändern.

cool, habe ich nicht.

[willybauss]

belu
for me it is not clear, if I decode actualPower_Pel correctly for your new firmware.
In my firmware (4.39), I checked it against an old service software.
If also the service software from tecalor reads 1.4 more than your calibrated meeter, then also the energy count could be wrong.

The only way to be sure 100% is:
- to get the service software from tecalor/se (which I do not have for your new firmware)
or even better
- to get a full documentation of the registers from tecalor/se

it's not that complicated. You should be able to do the following:

at 0:01 am (= 1 minute past midnight)  read and note
1. value of EVU energy meter for your heatpump (Stromzähler im Sicherungskasten)
2. value in FACHMANN - LAUFZEITEN - E.HEIZUNG TAG => should be close to zero
3. value in FHEM - Mythz.sGlobal.sElectrHCDay => should be close to zero

If values of 2. and 3. are not close to zero => wait another few minutes until daily reset happened.

at 11:59 pm (= 1 minute before next midnight, thus 23:58 hours later) read and note
4. value of EVU energy meter for your heatpump (Stromzähler im Sicherungskasten)
5. value in FACHMANN - LAUFZEITEN - E.HEIZUNG TAG
6. value in FHEM - Mythz.sGlobal.sElectrHCDay

Expected result: difference (value4 - value1) should be same as (value5 - value2) and same as (value6 - value3).

If the FHEM values (value6 - value3) differ from the THZ values (value5 - value2) ==> the decoding is wrong.

If the EVU values (value4 - value1) differ from the THZ values (value5 - value2) ==> the measurement inside the heatpump is wrong, thus decoding cannot fix that. The heatpump itself has a wrong measurement.

[willybauss]

Willy, Belu
I remember an unfinished discussion on this parameter.
Do you prefer it in % (more readable, like flow-proportion,  like in the display) or from 1..10 (like in the manual)?
100% full-infl and 0% empty   -vs-  10 full-infl and 0 empty
immi

After having checked both the manuals of 303 and 304 I noticed that in both manuals the allowed value range is same: 0 ... 10. So no change in  value range btw. 303 and 304(as I had expected before).For me it is unclear why SE doesn't have a clear logic, being same for all parameters. In the manual I see e.g.P15 range 0 ... 10P19 range 0 ... 100%It is a philosophic discussion if we use same values as SE (0 ... 10) or if we prefer the user friendly 0 ... 100% range. In case of the 0 ... 100% solution Mythz has to ensure that the division by 10 is done before the value is being transfered to the heatpump during set action (and multiplication by 10 in case of readings of course).

Now I checked which value range the display allows to be entered: it is 0 ... 100. So the value range of 0 ... 10 mentioned in the manual is simply a bug in the manual, which never had been fixed. The heatpump itself works with a 0 ... 100 range.

@belu:
Please check in your 304 which entries the display allows. I strongly believe that it is 0 ... 100 as well.

If that's the case the discussion can be stopped. In this case we do not need to change anything, since 0 ... 100 is used in the THZ as well as in FHEM.Mythz.