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

[immi]

What's the best way to find out about the (subtle?) differences between my FW 2.16 and the FW versions 2.06 and 2.14 that you consider in your code?

Code Auswählen Erweitern

021001000A0910031002100100E309009D009D6F633994000000000010031002100100FDFC100310021001006DFC00040C211A17000B03100310

the best way is to ask tecalor for a documentation of their registers
otherwise:

1) understand the hex comunication protocol --> green is fhem; blue is the heatpump

02 hi heatpump, I want to talk
10 OK
0100 0A09 1003 I would like to read register 09, my checksum is 0A
10 OK
02 sending answer
10 OK
0100 E309 009D009D6F6339940000000000 1003 I send you register 09 with checksum E3
10 OK

2) interprete 009D009D6F6339940000000000
3) improve the mapping at line 113 of andre.k in https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/00_THZ.pm

start the same process for each register

[sunrise]

Fine, but where in your code do I find the codes that you already have?

[immi]

Fine, but where in your code do I find the codes that you already have?

line 113 from andre.k in https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/00_THZ.pm

you can contact andre.k

[TheTrumpeter]

5.39technican

implemented

Thanks a lot!

[abu18]

Hi,

good news about my problem:

Now, I am looking for a solution to activate "Stellventil WW" (control wave?) in the "Fachmann" level with fhem.

Finally, I found out how to activate this by adding the following code to %setsX39technician:

Code Auswählen Erweitern

  "zControlValve_DHW"    => {cmd2=>"0A0653", argMin =>   "0",    argMax =>  "1",    type =>"1clean",  unit =>""}, 

It will be set to 0 automatically apx. 1 minute after activating it...

@immi: Do you want to add this to the "official" version? It works on a LWZ 304 trend (5.39_05.09HW113SW3.17Date)

Now, my idea is to set the "Stellventil WW" when starting WW heating.

That will be the next step: Whenever the WW heating is active and the flowrate is > 23.5l/min, I want to activate zControlValve_DHW. I added zFlowRate to %getsonly539...

"zFlowRate"        => {cmd2=>"0A01DA", type =>"5temp",  unit =>"l/min"}

... and want to read it every 10 seconds for 2 minutes or so after I started DHW heating, but I have to read some fhem docu to learn how to do that...

[zdravec]

Hi, I have a problem with my THZ module.
I was using one year an old raspberry 3a+, but it was slow and often the ui was unresponsive.
Some weeks ago I changed to raspberry 4b and the ui is fast, but since 3 days I have different problem.
Some days ago there was no data for them heating pump. I restarted the raspberry and it worked again. Today it happened again.
Both time there was following error in the log

Code Auswählen Erweitern

2023.11.18 00:11:00 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0  -- 0A0176 ->
I changed to nonblocking to 1 and the simpleReadTimeout to 8, but it didn't  help.
What else can solve the problem?

[sunrise]

Hi immi,

Can you please give me a hint about the exact meaning of these parameters?

Reading from last week:

Code Auswählen Erweitern

operatingHours1: 283 operatingHours2: 283 heatingHours: 28532 DHWhours: 14751 coolingHours: 0

Today:

Code Auswählen Erweitern

operatingHours1: 502 operatingHours2: 501 heatingHours: 28593 DHWhours: 14765 coolingHours: 0
I understand that the last one will always remain zero, as my THZ 303 SOL does not cool. However, I don't understand the meaning of "operatingHours" (operation of what exactly?) and why there are 1+2 (and how they differ from each other). Furthermore, does "heatingHours" mean that the HC pump worked for 28593 hours till now? And the pump for DHW for 14765 hours? Or are these hours of operation of boosters (which would be very high, so I hope rather not).

For comparison, sHistory reported by TheTrumpeter (and others with higher firmware versions than me [using 2.06 in THZ module, which seems to be the closest/best working with my 2.16 firmware in my THZ 303 SOL]) looks like this:

Code Auswählen Erweitern

compressorHeating: 7175 compressorCooling: 1204 compressorDHW: 1887 boosterDHW: 5 boosterHeating: 31
How do these "translate" to my parameters/values?


And why does sControl contain boosterStage2+1 but no boosterStage3?

Code Auswählen Erweitern

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


(btw, sGlobal does have boosterStage3, boosterStage2, and boosterStage1)


Thanks for helping me better understanding this!

[sunrise]

BTW, here's the result of get Mythz debug_read_raw_register_slow in data.txt:

Code Auswählen Erweitern

010002011003-01-68010064008700AA0064008700AA0000003C000000000000
01000A091003-09-010901F701F66FB239AE0000000000
010017161003-16-151602FA01CF020900000A003C1200CF00
0100D2D11003-D1-6DD1030300170138064A000F07EE090600170454096A000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0100D3D21003-D2-0100D3D21003-UpTempLimitDefrostEvaporatorEnd: 5499.4 MaxTimeDefrostEvaporator: 4099-decode: command not known
0100E9E81003-E8-0100E9E81003-018255D21003-decode: new unknown answer
0100EAE91003-E9-D2E90000000000000000000003E80000000000121CCE0000000000000000000100
0100F3F21003-F2-1BF20000000202000000101200010100000000
0100F4F31003-F3-A6F301CF003B01A40000121C0F08020100011E9B
0100F5F41003-F4-A1F4003BFF1101DCFFFE0209012201E900010001120000960100000000D200000000000002000000F0
0100F6F51003-F5-68F5003B01DC0000013601DCFC180001121C0100000200000000
0100F7F61003-F6-07F600000000FF1000FFFF0100000000000200000000
0100F9F81003-F8-0100F9F81003-UpTempLimitDefrostEvaporatorEnd: 6476 MaxTimeDefrostEvaporator: 4099-decode: command not known
0100FCFB1003-FB-FBFB02FA003B020901DC03A801CF00000000FFE901F1121C393999CD241B11000031000000000000000202
0100FDFC1003-FC-8EFC000509222D17000B12
0100FEFD1003-FD-D6FD00D8
0100FFFE1003-FE-0100FFFE1003-UpTempLimitDefrostEvaporatorEnd: 76.6 MaxTimeDefrostEvaporator: 4099-decode: command not known
010000FF1003-FF-010000FF1003-UpTempLimitDefrostEvaporatorEnd: 102.3 MaxTimeDefrostEvaporator: 4099-decode: command not known

[sunrise]

@zdravec
These "too slow messages" happen sometimes and were discussed in this thread.

Recommendations were e.g. checking the cable and adapter (serial/USB). Besides, I vaguely remember that there was something "special" about the RS232 interface on Raspberry Pi 3s, but if you use a serial/USB adapter that should not matter (I guess).

Changing "nonblocking" might not help, at least I remember immi telling me that I should leave it.

After I shortened and resoldered my cable (still ~5m long), I still see these "too slow" messages in the log but not so frequently anymore as before. And the plots do not show gaps or something.

Good luck!

[TheTrumpeter]

I was using one year an old raspberry 3a+, but it was slow and often the ui was unresponsive.
Some weeks ago I changed to raspberry 4b and the ui is fast, but since 3 days I have different problem.

Did you just take the SD-card from 3A+ out and put it into 4B or did you start with a complete new installation with maybe a newer version of OS?
If you started with a new installation, through which device do you connect your LWZ?

I did a complete new installation some weeks back (changed from a very old version of the OS to Buster) and face a similar issue with some other devices. Only ones with CH341-chip are affected in my installation (nanoCUL-clone and a RS485-adapter in my case). The issue is also visible in syslog. For nanoCUL as a workaround it works to regularly "redefine" the device in FHEM and for RS485 which I do not directly access through FHEM I simply restart the service which accesses it.

Further you could also check if your power-supply is sufficient as the 4B needs more power than the 3A+ did. As a first indication just check if you see throttling.

[zdravec]

I started completely new installation. I had home assistant running on the pi4, but I had to change the SD card after some years, so I decided to move it to a mini pc.
The raspberry 4 was there unused, I orderd a new SD card and istalled everything, than I created fhem backup from the pi3 and restored it on the new installation.

The pi4 is using different power supply taht the pi3, I checkt the logs, there is no throttling.

But I checked the system log and found following

Code Auswählen Erweitern

Nov 17 21:47:57 fhem kernel: cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -3. I have to search, what exactly the reason for this can be. I changed now to an usb3 port, let see, if it is more stable.

[TheTrumpeter]

I have the same messages but for the CH341 devices.
Also no throttling for me.

Which OS version do you use?

[sunrise]

Old but maybe helpful:
https://github.com/raspberrypi/linux/issues/2406#issuecomment-1685151794

If you use a USB port between, please consider trying without it (directly).

Furthermore:

that the Pi's USB ports can supply a maximum of 6 watts (5V at up to 1.2A, which is shared by all USB ports in use). If the total of all of your USB devices is more than 1.2A they won't work reliably (if at all)

(https://forums.raspberrypi.com/viewtopic.php?p=2038055&#p2038055)

[willybauss]

"unpowered hub"...     

[sunrise]

Ja, wenn's unpowered ist, ist's Mist.