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

[willybauss]

Die angefragten Parameter sind zur Beantwortung der Frage nach den +30% Heizkosten im ersten Ansatz relativ uninteressant. Einige der anderen Fragen beantwortet das Manual.

Außerdem wäre die Frage hier
https://forum.fhem.de/index.php/topic,33452.0.html.html
besser aufgehoben. Zeige uns die Plots, so wie ich sie im ersten Beitrag des Links anbiete. Erfahrene Benutzer können daraus meist in Sekunden ersehen, wo das Problem liegt.

[willybauss]

@ immi:
Do we have a mapping table, saying which firmware attribute value should be set in case of THZ firmware rev. xyz? In the 'other' thread we're discussing a question related to that topic:

https://forum.fhem.de/index.php/topic,33452.msg1022908.html#msg1022908

I tried to find the answer in the code. Lines ~1980 ... 2005 look like you're trying to do a best guess mapping already, but I'm not sure if that's right. Could you give us a hint, please?

[immi]

@ immi:
Do we have a mapping table, saying which firmware attribute value should be set in case of THZ firmware rev. xyz?

Hi Willy
I do not have a mapping, therefore I leave the FHEMuser the reponsability to define the firmware parameter.
I check the firmware parameter in Lines ~1980 ... 2005 and if it is not defined, I set 4.39 (the one for early adopters)
immi

[immi]

update to 0.184
THZ: z_Last_fhem_err implemented, aesthetics and DevIo (Forum #110125)

[sunrise]

Hello,

My THZ 303 SOL has firmware 2.16, but the module does not seem to include this version - only 2.06 and newer ones. Can you please give me a hint how I should handle this?

I would like to add the status (over time) of the pump that transports the water through the heating in the floor (German "Umwälzpumpe") to my graph/plot of various temperatures. Any hints are very welcome!

[immi]

Hello,
My THZ 303 SOL has firmware 2.16, but the module does not seem to include this version - only 2.06 and newer ones. Can you please give me a hint how I should handle this?

Hi sunrise,
2.06 or 2.14
no idea which one is better for you
just try
I have not tested both, my tecalor is newer.
Fell free to reverse engineer your firmware and I will add your parameters to the module.
immi

[sunrise]

SwitchingProg seems to belong to sDisplay, right? However, I cannot find sDisplay on my heating (which is from 2008 and has the very old LCD, i.e. not even that "ipod"-like display that followed, if I remember correctly)

I would like to rebuild willibauss' code from there to fit my heating, but currently, I do not really know how to start.

Thanks for more hints in this regard! 

[sunrise]

A separate post for a separate problem:

My heating's firmware is 2.16.

When I set the firmware to 2.04, I get the following for sControl (which seems plausible):

heatRequest: 5 heatRequest2: 5 hcStage: 0 dhwStage: 0 heatStageControlModul: 0 compBlockTime: 0 pasteurisationMode: 0 defrostEvaporator: 10 boosterStage2: 0 solarPump: 0 boosterStage1: 0 compressor: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 mixerOpen: 0 mixerClosed: 0 sensorBits1: 01 sensorBits2: 01 boostBlockTimeAfterPumpStart: 0 boostBlockTimeAfterHD: 0

However, when I set the firmware to 2.14 (which should be "closer" to my 2.16), I get the following for sControl:

13F20505000000000000100004010100000000

A little bit later this:

2BF2050500000000000010001C010100000000

The other "s" parameters (e.g. sGlobal) look right with the firmware set to 2.14, but not sControl.

When I set the firmware back to 2.06, sControl again looks right:

heatRequest: 5 heatRequest2: 5 hcStage: 0 dhwStage: 0 heatStageControlModul: 0 compBlockTime: 0 pasteurisationMode: 0 defrostEvaporator: 10 boosterStage2: 0 solarPump: 0 boosterStage1: 0 compressor: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 mixerOpen: 0 mixerClosed: 0 sensorBits1: 01 sensorBits2: 01 boostBlockTimeAfterPumpStart: 0 boostBlockTimeAfterHD: 0

Under Internals, the model appears as "2.06_02.16". Is this as it should be? Is my heating's firmware 2.06 or 2.16? The read firmware parameter tells me it is 2.16 (as well as on the plate stuck on the heating).

DEF    /dev/ttyUSB0@9600
DeviceName    /dev/ttyUSB0@9600
FD    7
FUUID    xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx (I anonymised this)
NAME    Mythz
NR    14
PARTIAL
STATE    opened
TYPE    THZ
VERSION    0.184
model    2.06_02.16

PS:
About 40 minutes after my above posting, I set the firmware of the THZ module again to 2.14 and read sControl. Interestingly, I again get only these 2 values (after several readings), nothing else, i.e. the same as 40 minutes ago (see 2 quotes above):

13F20505000000000000100004010100000000
2BF2050500000000000010001C010100000000

When setting the firmware value back to 2.06, sControl is again ok.

How can I help to "disassemble" (or shall I name it "reverse engineer") this? The hex values above mean nothing to me, and I have no clue which values I could look up from the display or from the correct ones via FHEM in order to "guess" how the firmware could be amended. Thanks, immi, for your help!

[andre.k]

However, when I set the firmware to 2.14 (which should be "closer" to my 2.16), I get the following for

2.14 ist not closer to 2.16 based on information from Tecalor "Ersatzteilkatalog":

THZ 303 INTEGRAL
2.03 (2002/01-2004/04)
2.05 (2004/04-2006/11)
2.06 (2006/12-2008/08)
THZ 303 SOL
2.14 (2002/10-2004/08)
2.15 (2004/09-2006/08)
2.16 (2006/09-2008/08)

I would suggest to start with firmware 2.06 in your case.

[willybauss]

Hello,

My THZ 303 SOL ...

So, why do you suggest 2.06 for a SOL model?

[sunrise]

2.14 ist not closer to 2.16 based on information from Tecalor "Ersatzteilkatalog":

THZ 303 INTEGRAL
2.03 (2002/01-2004/04)
2.05 (2004/04-2006/11)
2.06 (2006/12-2008/08)
THZ 303 SOL
2.14 (2002/10-2004/08)
2.15 (2004/09-2006/08)
2.16 (2006/09-2008/08)

I would suggest to start with firmware 2.06 in your case.

As willybauss noted, I have the THZ SOL, i.e. firmware 2.06 is actually not applicable for me. Why it works better for me (regarding the sControl reading) than with 2.16, I do not know. Well, the firmware 2.16 is officially not supported by THZ module. Immi kindly offered to support it, but of course he would need more input from me or other users with the 2.16 firmware for debugging/reverse engneering.

Now I wonder whether I should use the 2.06 (which is for the INTEGRAL) or the 2.14 (for my SOL) for further testing etc.

[andre.k]

I know, that's a little bit confusing. Currently the SOL related code in the THZ module is generic for firmware 2.xx. But in firmware 2.06 are two  special get commands sLast10errors and sFirmware and modifications in sHC1 and sGobal.


 

[sunrise]

As I do not know these details, would you suggest that I try 2.06 or 2.14? How can I contribute to "disassemble" something? I am really willing to do so but do not know how and where to start. The THZ is connected to a Raspi with FHEM. Via ser2net, I can also read and write from other devices.

[immi]

How can I contribute to "disassemble" something? I am really willing to do so but do not know how and where to start. The THZ is connected to a Raspi with FHEM. Via ser2net, I can also read and write from other devices.

excellent attitude
let us start by forgetting  the name from tecalor 2.xx let us call a new one 2.16 for now.
look at the code https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/00_THZ.pm

line 900
chage it to ."firmware:4.39,2.06,2.14,2.16,5.39,4.39technician "

line 1897
i tell fhem which %sets and %gets to use for 2.14
just add a simical case for 2.16


line 829
here I define %getsonly214 as a list of registers 01,02,F2,F4,FB and how we decode the answer from the heatpump (respectively 01pxx214, 02pxx206 ....)


line 73
here is defined how to decode the answer from the heatpump for 01pxx214

so far easy

now, find out your registers with their encoding.
if you can follow me so far, I can explain you how

immi

[sunrise]

Great, thank you! I am new to GitHub (have an account there as '7wells'). Am I allowed to edit the code there? Or is this going to work via pull requests or something?

And yes, I will definitely be able to get the values for all parameters etc.