THZ / LWZ Tecalor Stiebel Eltron Heizung

[houseowner123]

Thanks, immi! That did it! 

[Heiner]

Hi,

the Software becomes better and better. I am impressed, a great thank you to everyone involved and mainly to Immi.

I try currently to make use of the Outside Temp elsewhere in fhem but THZ is a bit too precise. I like to round the reading for it but have no clue how to do it.

I know how to split out this specific reading (as per WIKI)                        attr Mythz userReadings AussenTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[1]}

and I know that for the readinggroup you do the rounding (as per WIKI)  attr rg_thz valueFormat { AussenTemp => '%1.f °C'}

But how to round already the split oout Reading, to as well record for the log only one digit less, I have no clue, and as well not found anything which works elsewhere in the forum.

Can one of you help here?

Many Thanks.

[micomat]

immi,

just replaced with 0.088 now fhem is quite poor in performance and my mythz.log shows me:

Code Auswählen Erweitern

2014-04-23_09:04:51 Mythz DISCONNECTED
2014-04-23_09:04:59 Mythz CONNECTED
2014-04-23_09:05:00 Mythz DISCONNECTED
2014-04-23_09:05:09 Mythz CONNECTED
2014-04-23_09:05:09 Mythz DISCONNECTED
2014-04-23_09:05:18 Mythz CONNECTED
2014-04-23_09:05:19 Mythz DISCONNECTED


any ideas?

EDIT:
strange... when i change the interval attributes to at-command to get all my data from the THZ, it's back to work

[willybauss]

I try currently to make use of the Outside Temp elsewhere in fhem but THZ is a bit too precise. I like to round the reading for it but have no clue how to do it.

Possibly you could try to use outside_tempFiltered instead - value no. 69 of sGlobal. Difference to outside_temp can be seen in attached screen shot.

[willybauss]

... please find enclosed v0.088; small bug fix, making the system unstable
immi

question: after update to 0.086 I had twice an issue with missing entries in THZ-log for hours. shutdown restart solved both issues. Is this the instability you mentioned above?


Since Markus has obviously different issues using 0.088 I'll wait before I update again.

[immi]

I should not try to do 3 things at once.
1) I changed the names.
2) I fixed the sync problem for Tom(firmware 4.09): added a delay of 100ms
3) I enabled the possibility to change an attribute, and make it effective without restarting fhem.

The 3) is affecting the connect/disconnect (indirect connection with ser2net) issue drammatically.
In the meanwhile after every change restart fhem!!!
In v 0.089 should be better.

I uploaded v0.089 in the repository now.

immi

[micomat]

okay so i will update the Wiki tomorrow

[willybauss]

there are many more eggs to find.

after having compared v0.085 vs. v0.086 the differences in parameters are
p46UnschedVent0
p45UnschedVent1
p44UnschedVent2
p43UnschedVent3
p07DHWsetManual
p06DHWsetStandby

[immi]

I know how to split out this specific reading (as per WIKI)                        attr Mythz userReadings AussenTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[1]}

and I know that for the readinggroup you do the rounding (as per WIKI)  attr rg_thz valueFormat { AussenTemp => '%1.f °C'}

But how to round already the split oout Reading, to as well record for the log only one digit less, I have no clue, and as well not found anything which works elsewhere in the forum.

Hi Heiner
%1.f doesn't properly round; it deletes the decimal
you can use it like this

Code Auswählen Erweitern

attr Mythz userReadings outTemp0dec { sprintf('%1.f ',   ((split ' ',ReadingsVal("Mythz","sGlobal",0))[1]) ) }

sfprint is very powerfull in perl
http://www.perlmonks.org/?node_id=20519

immi

[micomat]

hi immi,

installes 0.089 and have a question regarding a reading:

Code Auswählen Erweitern

sHC1
outsideTemp: 12.6 x08: 51.3 returnTemp: 28.9 integralHeat: 1 flowTemp: 28 heatSetTemp: 26.8 heatTemp: 28.6 seasonMode: winter integralSwitch: 100 opMode: setback roomSetTemp: 20.5

sHC2
outsideTemp: 12.7 returnTemp: 31 vorlaufTemp: -60 heatSetTemp: 33.4 heatTemp: 31 stellgroesse: -100 seasonMode: winter opMode: normal

2014-04-24 09:06:24

pOpMode shows me automatic
opMode in HC1 is setback? is that meanig, that the time-range definied is in setback mode for HC1 this time?

opMode in HC2 is normal as i dont use HC2 so there is no time-range defined?

EDIT:
do you see any chance to read the heat recovery values, too? that would be great!

Markus

[immi]

Hi Markus
I cannot reproduce it, because I am ( and want to be) in standby untill sunday (not at home).

FYI: opMode in sHCx and pOpMode are different. I start to think that 3 different guys worked on the firmware of the heatpump and never spoke with another.

Code Auswählen Erweitern


pOpMode  ("1" =>"standby", "11" => "automatic", "3" =>"DAYmode", "4" =>"setback", "5" =>"DHWmode", "14" =>"manual", "0" =>"emergency");   

opMode in sHCx   ("1" =>"normal", "2" => "setback", "3" =>"standby", "4" =>"restart", "5" =>"restart");


How the two are connected and if HC1 or HC2 should be different. No Idea.
With time we will understand it.

You ask about heat recovery values: do you mean actualPower_Qc:  actualPower_Pel: from sGlobal?
Could you be more specific? Like where are described on the manual?

p.s. when you update the wiki please do not forget offFor60min with the new png
http://forum.fhem.de/index.php/topic,13132.msg160381.html#msg160381

best regards
immi

[houseowner123]

Immi,

I think Markus want the values for the amount of heat that is recycled through the heat exchange (WRG in German). There is battery of actual values and summary values of them relating to the amounts of energy produced. These reading would be cool to have.
I would love to have P70 - bivalance point as parameter.

Can we get the most current 00_THZ.pm updates through the regular "update" command again?

Tom

[micomat]

hi Tom
0,089 can get via update. should be the latest

[immi]

still not clear WGR?, I will have a look.

@Tom do you mean p78dualMode?

immi

[micomat]

in german it is Wärmerückgewinnung. it's a kilowatthours value which shows you how much energy was recycled from the heat exchanger