THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.

Begonnen von immi, 02 Februar 2015, 11:42:16

Vorheriges Thema - Nächstes Thema

willybauss

Hi immi,
as he already wrote: LWZ303i, FW rev. 2.03 assumed, Raspberry Pi, connected via serial port (Ser 2 USB converter assumed)
Willy
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS

willybauss

Hi Jens,

herzlich willkommen. Toll, dass so eine alte Anlage noch läuft; das macht mir Hoffnung. Wenn Du mal Zeit hast wäre ich an ein paar Infos über die Anlage interessiert, also was im Lauf der Jahre so an Wartung, Reparaturen, Verschleißteilen usw. anfiel. Allerdings bitte nicht hier (hier ist Modulsupport und Codeentwickling), sondern z.B. hier: https://forum.fhem.de/index.php?topic=33452.new;topicseen#new

Gruß
Willy

PS:
Immer wieder schön zu sehen, wenn meine eigenen Plotdarstellungen woanders auch Gefallen finden  :).
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS

fernsehjens

Hi Immi,
when i do 'get Mythz sFirmware', i get: '010301FD1003 msg2 command not known';
perhaps the version of the LWZ303i is: 2.03 (sticker on Eprom).

FHEM runs on Raspberry B+, thz.pm is 0.153.

Hallo Willi,
im anderen Thread werde ich die Anlage demnächst ein wenig beschreiben.

Thanks Jens

immi

Hi Jens
Zitat von: fernsehjens am 03 Januar 2017, 21:30:10
when i do 'get Mythz sFirmware', i get: '010301FD1003 msg2 command not known';
it is strange, that you cannot read register FD;
have a look again at data.txt
I am missing lots of registers; after readRAWRegisters you should wait more before reading data.txt

Zitat
FHEM runs on Raspberry B+, thz.pm is 0.153.
"Illegal division by zero at ./FHEM/00_THZ.pm line 1686"
it looks like your register F4 is formatted strangely or you have roomSetTemp = 0

try as attribute
attr Mythz firmware 2.14

restart fhem
wait 5 minutes and check agian if it crashes again

immi

fernsehjens

Hi immi,
yes with attr Mythz firmware 2.14 it works without crashes and i have the heat curve.

But on "get Mythz debug_read_raw_register_slow" there are only a few registers in data.txt.
There are some logs after reading the registers:
2017.01.04 00:40:13 3: THZ_Parsing: offset(12) + length(4) is longer then message : '010315111003'
2017.01.04 00:40:13 3: THZ_Parsing: offset(16) + length(4) is longer then message : '0103151110030000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(20) + length(2) is longer then message : '01031511100300000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(22) + length(2) is longer then message : '0103151110030000000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(12) + length(4) is longer then message : '010316121003'
2017.01.04 00:40:13 3: THZ_Parsing: offset(16) + length(4) is longer then message : '0103161210030000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(20) + length(2) is longer then message : '01031612100300000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(22) + length(2) is longer then message : '0103161210030000000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(12) + length(4) is longer then message : '010317131003'
2017.01.04 00:40:13 3: THZ_Parsing: offset(16) + length(4) is longer then message : '0103171310030000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(20) + length(2) is longer then message : '01031713100300000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(22) + length(2) is longer then message : '0103171310030000000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(12) + length(4) is longer then message : '010318141003'
2017.01.04 00:40:13 3: THZ_Parsing: offset(16) + length(4) is longer then message : '0103181410030000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(20) + length(2) is longer then message : '01031814100300000000'
2017.01.04 00:40:13 3: THZ_Parsing: offset(22) + length(2) is longer then message : '0103181410030000000000'
2017.01.04 00:40:14 3: THZ_Parsing: offset(12) + length(4) is longer then message : '010319151003'
2017.01.04 00:40:14 3: THZ_Parsing: offset(16) + length(4) is longer then message : '0103191510030000'
2017.01.04 00:40:14 3: THZ_Parsing: offset(20) + length(2) is longer then message : '01031915100300000000'
2017.01.04 00:40:14 3: THZ_Parsing: offset(22) + length(2) is longer then message : '0103191510030000000000'
2017.01.04 00:40:14 2: Mythz/RAW: 000000000000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 0000000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 000000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 0000
2017.01.04 00:40:14 2: Mythz/RAW: 00000000
2017.01.04 00:40:14 2: Mythz/RAW: 001003
2017.01.04 00:40:15 2: Mythz/RAW: 02
2017.01.04 00:40:16 2: Mythz/RAW: 02
2017.01.04 00:40:17 2: Mythz/RAW: 02
2017.01.04 00:40:18 2: Mythz/RAW: 02
2017.01.04 00:40:19 2: Mythz/RAW: 02
2017.01.04 00:40:21 2: Mythz/RAW: 02

thanks
Jens

immi

Hi Jens
you restart your system
if you are happy, just keep it like this, otherwise
attr Mythz verbose 5
wait 10min
post the fhemlogfile as file

immi

fernsehjens

Hi immi,
i´m happy but i do no trust myself to send a parameter to the LWZ.
Here is the logfile with "verbose 5", at 09:43 i send "get Mythz debug_read_raw_register_slow" again.

Thanks for support
Jens

immi

hi jens
the logfile is ok, thanks
before writing back to the heatpump I would try to get p01-p12 with verbose5
I would like to see the log when you get p01-p12 with verbose5.
I, also, would like you to check all parameters connected with p01-p12.
Are they all well interpreted from fhem and equal to what you have in the heatpump?
p01RoomTempDay: p02RoomTempNight: p03RoomTempStandby: p04DHWsetTempDay: p05DHWsetTempNight: p06DHWsetTempStandby:   p07FanStageDay:  p08FanStageNight: p09FanStageStandby: p10RoomTempManual: p11DHWsetTempManual:  p12FanStageManual:
immi

fernsehjens

hi immi,
the parameters from p01-p12 are all the same like the heatpump:
p01RoomTempDay: 21.5 p02RoomTempNight: 21 p03RoomTempStandby: 16 p04DHWsetTempDay: 48 p05DHWsetTempNight: 43 p06DHWsetTempStandby: 38 p07FanStageDay: 2 p08FanStageNight: 0 p09FanStageStandby: 2 p10RoomTempManual: 26 p11DHWsetTempManual: 40 p12FanStageManual: 0
Jens

immi

hi Jens
I do not see any problem:
Search in internet the tel-number of a tecalor technician ;)
Try to change p03RoomTempStandby from fhem and look if your tecalor accepted the change.
immi

fernsehjens

Hi immi,
yes i do it!
I can change all Parameters to my heatpump,
thanks for help!
Jens

kriforum

Dear all,

Happy New Year!
I'm running your module roughly one year now and everything's working fine - thanks so much for all your ongoing efforts.
I used to use an ISG gateway from Stiebel earlier (and then in parallel to the FHEM-Raspi), but actually I don't use the gateway any longer actively.

Last night I got some emails that the booster had been used (outside temp around -10°C), and I checked the plots (mainly the ones from Willy), then it came to my attention that in the power consumption plot there is only visible the power which goes to the compressor, not the one to the booster - which would be much nicer!

Looking to the available parameters, there are no daily booster power values (like for the HC), only total ones since commission. So for every refresh/reading a difference (sBoostDHWTotal_old - sBoostDHWTotal_ new) would need to be added to the HC power to show total power.

Do you agree?
Anyone already had the same wish/idea?

Thanks
Christian

willybauss

Zitat von: kriforum am 06 Januar 2017, 17:24:49
--- it came to my attention that in the power consumption plot there is only visible the power which goes to the compressor, not the one to the booster - which would be much nicer!
Don't know which plot you're talking about. Is it one of mine, or a self made one?

Zitat von: kriforum am 06 Januar 2017, 17:24:49
Looking to the available parameters, there are no daily booster power values (like for the HC), only total ones since commission. So for every refresh/reading a difference (sBoostDHWTotal_old - sBoostDHWTotal_ new) would need to be added to the HC power to show total power.
You can do this easily using a userReading.

It never came to my mind to check heating power (I assume in fact you're not talking about power, but energy) on daily basis.
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS

immi

Hi Christian
i really appreciate that you like more fhem than ISG

I also do not understand really what you nead
I try to guess:
instead of sBoostDHWTotal_old - sBoostDHWTotal_ new
why don't you plot sBoostDHWTotal with delta-h or delta-d?
https://wiki.fhem.de/wiki/Creating_Plots
immi

kriforum

Thanks for getting back quickly.
I double checked the plot I were talking about, indeed it's the only one I made myself, beside others taken over from Willy. And yes, it shows the consumed energy for heating and water (wrong legend naming, true...). Sorry for not being more clear.

Basically I'm interested in the consumed energy to not get surprises - actually a fear which goes back to the times of the initial heating up of the house floors for drying them. Quite an amazing energy bill...

Your ideas are helpful and obvious and clearly show me that I have to get more involved again after a year of just using the system.

Thanks.