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

[immi]

Hi immi,

the Protokoll looks like this:

Code Auswählen Erweitern

  "F4hc1214" => [["outsideTemp: ", 4, 4, "hex2int", 10],
                 [" x08: ",  8, 4, "raw", 1],
                 [" returnTemp: ", 12, 4, "hex2int", 10],
                 [" integralHeat: ", 16, 4, "hex2int", 1],
                 [" flowTemp: ", 20, 4, "hex2int", 10],
                 [" heatSetTemp: ",  24, 4, "hex2int", 10],
                 [" heatTemp: ", 28, 4, "hex2int", 10],
                 [" onHysteresisNo: ", 32, 2, "hex", 1],
                 [" offHysteresisNo: ", 34, 2, "hex", 1],
                 [" hcBoosterStage: ", 36, 2, "hex", 1],
                 [" seasonMode: ", 38, 2, "somwinmode", 1],
                 [" x40: ", 40, 4, "raw", 1],
                 [" integralSwitch: ", 44, 4, "hex2int", 1],
                 [" hcOpMode: ", 48, 2, "opmodehc", 1],
                 [" x50: ", 50, 4, "raw", 1],
                 [" x54: ", 54, 4, "raw", 1],
                 [" x60: ", 58, 4, "raw", 1],
                 [" roomSetTemp: ", 62, 4, "hex2int", 10],
                 [" x66: ", 66, 4, "raw", 1],
                 [" x70: ",  70, 4, "raw", 1],
                 [" insideTempRC: ", 74, 4, "hex2int", 10],
                 [" x78: ", 78, 4, "raw", 1],
                 [" x82: ", 82, 4, "raw", 1],
                 [" ???Temp: ", 86, 4, "hex2int", 10]
         ],


PS.: hat die Reihenfolge Einfluss auf die Heizkurve?
BR Jörg

Hi 
the order in this list has no effect on the heating curve
nevertheless it has an effect on the order in the register
changing the order might be very annoying for other users, which relay on the the actual order.

I understand you changed insideTempRC: from starting at 68 to 72; what else?

p.s. please avoid ???Temp
immi

[hellijo]

Hi immi,

die Korrektur für sHC1 für die FW 2.14:

Code Auswählen Erweitern


"F4hc1214" => [["outsideTemp: ", 4, 4, "hex2int", 10],
                 [" x08: ",  8, 4, "raw", 1],
                 [" returnTemp: ", 12, 4, "hex2int", 10],
                 [" integralHeat: ", 16, 4, "hex2int", 1],
                 [" flowTemp: ", 20, 4, "hex2int", 10],
                 [" heatSetTemp: ",  24, 4, "hex2int", 10],
                 [" heatTemp: ", 28, 4, "hex2int", 10],
                 [" onHysteresisNo: ", 32, 2, "hex", 1],
                 [" offHysteresisNo: ", 34, 2, "hex", 1],
                 [" hcBoosterStage: ", 36, 2, "hex", 1],
                 [" seasonMode: ", 38, 2, "somwinmode", 1],
                 [" x40: ", 40, 4, "raw", 1],
                 [" integralSwitch: ", 44, 4, "hex2int", 1],
                 [" hcOpMode: ", 48, 2, "opmodehc", 1],
                 [" x50: ", 50, 4, "raw", 1],
                 [" x54: ", 54, 4, "raw", 1],
                 [" x58: ", 58, 4, "raw", 1],
                 [" roomSetTemp: ", 62, 4, "hex2int", 10],
                 [" x66: ", 66, 4, "raw", 1],
                 [" x70: ",  70, 4, "raw", 1],
                 [" insideTempRC: ", 74, 4, "hex2int", 10],
                 [" x78: ", 78, 4, "raw", 1],
                 [" x82: ", 82, 4, "raw", 1],
                 [" Temp: ", 86, 4, "hex2int", 10]
         ],

Den letzen Wert und die Raw konnte ich noch nicht übersetzen.

Im Anhang sind die Basics der Übersetzung.
Der log Auszug, der Screenshot der Servicesoftware und die Aufsplittung des Signals.
Ich hoffe ich habe keine Fehler gemacht.

Der Test sah von sHC1 sah gut aus. Ich sehe in der Reihenfolge der Werte die Heizkurve nicht mehr.
Muss ich die Werte noch in der alten Reihenfolge sortieren?

Gruß Jörg

[hellijo]

Hi 
the order in this list has no effect on the heating curve
nevertheless it has an effect on the order in the register
changing the order might be very annoying for other users, which relay on the the actual order.

I understand you changed insideTempRC: from starting at 68 to 72; what else?

p.s. please avoid ???Temp
immi

Yes the beginning of the Message for starting is changed.
And I added the Value für Temp which ist starting at 86 - but I don't know wich Temperatur it is - but ist look like a Temperatur.

[immi]

Der Test sah von sHC1 sah gut aus. Ich sehe in der Reihenfolge der Werte die Heizkurve nicht mehr.
Muss ich die Werte noch in der alten Reihenfolge sortieren?

sorry I gave you the wrong info:
The order matters; E.g. look at line 2055

[hellijo]

Hi immi,

ich habe die unbekannten Strings wieder auf "raw" umgestellt.
Es sind zwar Stati in den Strings drin, aber nichts neues. HC Pumpe ein/aus oder Kompressor ein/aus.
Das sind aber alles Signale die im sGlobal schon vorhanden sind.
Ich konnte zumindest keine Signale mit einem Mehrwert zu den aktuellen Signalen erkennen.

Daher hier der Code mit den raw Strings.

Code Auswählen Erweitern


"F4hc1214" => [["outsideTemp: ", 4, 4, "hex2int", 10],  [" x08: ", 8, 4, "raw", 10],
      [" returnTemp: ", 12, 4, "hex2int", 10],  [" integralHeat: ", 16, 4, "hex2int", 1],
      [" flowTemp: ", 20, 4, "hex2int", 10], [" heatSetTemp: ", 24, 4, "hex2int", 10],
      [" heatTemp: ", 28, 4, "hex2int", 10],  [" seasonMode: ", 38, 2, "somwinmode", 1],
      [" integralSwitch: ", 44, 4, "hex2int", 1],  [" hcOpMode: ", 48, 2, "opmodehc", 1],
          [" roomSetTemp: ", 62, 4, "hex2int", 10],  [" x50: ", 50, 4, "raw", 10],
      [" x54: ",     54, 4, "raw", 10],  [" insideTempRC: ", 74, 4, "hex2int", 10],
      [" x66: ",     66, 4, "raw", 10],  [" x70: ", 70, 4, "raw", 10],
      [" onHysteresisNo: ", 32, 2, "hex", 1],  [" offHysteresisNo: ", 34, 2, "hex", 1],
      [" hcBoosterStage: ", 36, 2, "hex", 1],  [" x40: ", 40, 4, "raw", 1],
          [" x58: ",            58, 4, "raw", 10],  [" x78: ", 78, 4, "raw", 10],
          [" x82: ",            82, 4, "raw", 10],  [" x86: ", 86, 4, "raw", 10]
         ],


Gruß Jörg

[hellijo]

Hallo immi, hallo Andre,

ich habe Andres Anpassung bei mir getestet:

Code Auswählen Erweitern


    "F4hc1214" => [["outsideTemp: ", 4, 4, "hex2int", 10], [" x08: ", 8, 4, "raw", 1],
      [" returnTemp: ", 12, 4, "hex2int", 10], [" integralHeat: ", 16, 4, "hex2int", 1],
      [" flowTemp: ", 20, 4, "hex2int", 10], [" heatSetTemp: ", 24, 4, "hex2int", 10],
      [" heatTemp: ", 28, 4, "hex2int", 10], 
      [" seasonMode: ", 38, 2, "somwinmode", 1],
      [" integralSwitch: ", 44, 4, "hex2int", 1], [" hcOpMode: ", 48, 2, "opmodehc", 1],      
          [" roomSetTemp: ", 62, 4, "hex2int", 10], [" x50: ", 50, 4, "hex2int", 10],
      [" x66: ", 66, 4, "raw", 1], [" insideTempRC: ", 74, 4, "hex2int", 10],
      [" x70: ", 70, 4, "raw", 1], [" x76: ", 78, 4, "raw", 1],
      [" onHysteresisNo: ", 32, 2, "hex", 1], [" offHysteresisNo: ", 34, 2, "hex", 1],
      [" hcStage: ", 36, 2, "hex", 1],# 0=Aus; 1=Solar; 2=V1
          [" boosterStage2: ", 40, 1, "bit3", 1],
          [" x58: ", 58, 4, "raw", 1], [" x54: ", 54, 4, "raw", 1],
          [" blockTimeAfterCompStart: ", 82, 4, "hex2int", 1], [" insideTemp: ", 86, 4, "hex2int", 10],
          [" solarPump: ", 40, 1, "bit2", 1],
  [" boosterStage1: ", 40, 1, "bit1", 1],
  [" compressor: ", 40, 1, "bit0", 1],
  [" heatPipeValve: ", 41, 1, "bit3", 1],
  [" diverterValve: ", 41, 1, "bit2", 1],
  [" dhwPump: ", 41, 1, "bit1", 1],
  [" heatingCircuitPump: ", 41, 1, "bit0", 1],
  [" mixerOpen: ", 43, 1, "bit1", 1],
  [" mixerClosed: ", 43, 1, "bit0", 1],
         ],

Nur der Wert bei Werteposition 86 sollte vielleicht "heatSetTempRC", "InsideTemp" passt nicht. Siehe Plot im Anhang.
In Braun ist die Innentemperatur.
Rot ist die Kurve "heatSetTemp" und Blau "x86".
Der erste Einbruch der Temepratur ist die programmtechnische Raumtemperaturabsenkung.
Der zweite Einbruch, hier hatte ich den Raumtemperatureinfluss auf 10 gestellt.
Der Anstieg danach, hier hatte ich den Raumtemperatureinfluss auf 0 gestellt.

Ich glaube man könnte den Code oben fix in das nächste THZ update einbinden.

VG Jörg

[immi]

Nur der Wert bei Werteposition 86 sollte vielleicht "heatSetTempRC", "InsideTemp" passt nicht. Siehe Plot im Anhang.
In Braun ist die Innentemperatur.
Rot ist die Kurve "heatSetTemp" und Blau "x86".

Hi Jörg
if you change the order and position, you will beak all scripts, which are based on the order and position.
In your case probably you are defining  Innentemperatur with userseadings, and by inserting x50 you are shifting all the rest.
Suggestion: Put the newly discovered stuff at the end.


Changing the order might be very annoying for other users, which relay on the the actual order.
I have uploaded your code as firmware 2.14j, including  F4hc1214j.
in this way you can play arround without affecting other users.
immi

[Shenja]

Guten Tag,

Ich betreibe die LWZ 403sol (sw 4.39) und würde gerne den Volumen Strom der Heizkreispumpe gerne erfassen.
Leider habe ich bisher keinen Parameter dafür gefunden in fhem.
An der LWZ wird dieser Wert doch bestimmt irgendwo erfasst. Manuel kann ich diesen Wert an der LWZ messen lassen, dauert aber immer ziemlich lange.
Könnte mir da jemand helfen?

[willybauss]

Falscher Thread für solche Fragen. Schau mal auf der 1. Seite im 1. Beitrag. Dort ist der Link.

[LeJoke]

Guten Tag,

Ich betreibe die LWZ 403sol (sw 4.39) und würde gerne den Volumen Strom der Heizkreispumpe gerne erfassen.
Leider habe ich bisher keinen Parameter dafür gefunden in fhem.
An der LWZ wird dieser Wert doch bestimmt irgendwo erfasst. Manuel kann ich diesen Wert an der LWZ messen lassen, dauert aber immer ziemlich lange.
Könnte mir da jemand helfen?

FBglob-flowRate Pos. 110 sollte ist seit ein paar Jahren im Code (zumindest für sw 5.39 und funktioniert auf unserer 304). Ggf, aber auf der x03 nicht verfügbar oder an anderer Stelle ... evtl. mal per debug die komplette sGlob auslesen und die oberen Positionen durchsuchen
claus

[sunrise]

Hi immi, I hope you are doing well!

I have not dealt with my Tecalor THZ 303SOL for a while, as it runs without problems (at least as far as I can tell) but now started to play with Home Assistant etc., which stirred again my interest about your very cool THZ module for FHEM. According to our conversation in June 2020 (https://forum.fhem.de/index.php/topic,33211.msg1061911.html#msg1061911) etc., there was no support for the 2.16 firmware, which I have on my heatpump, so I provided some further information I could get hold on. Referring to the available information about the different SE/Tecalor firmware...

Code Auswählen Erweitern

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)
... at that time, the FHEM THZ 2.06 FW was the one that worked best for me (with a few errors I reported back then). Is this FW version still the one that I should use? Thanks for your time and great work!

PS: Where can I find some "ready-to-use/test" configs that draw some nice plots and maybe even have some buttons to control my 2.16 FW THZ 303SOL? Or should I ask this question over there? https://forum.fhem.de/index.php/topic,33452.0.html.html

[immi]

... at that time, the FHEM THZ 2.06 FW was the one that worked best for me (with a few errors I reported back then). Is this FW version still the one that I should use? Thanks for your time and great work!

Hi sunrise
the firmwares are still not documented from tecalor
no real big improvement in the last years; you can chose among 2.06, 2.14 or 2.14j (which I added for hellijo in Jun22)

Or should I ask this question over there? https://forum.fhem.de/index.php/topic,33452.0.html.html

it makes sense

[sunrise]

Hi sunrise
the firmwares are still not documented from tecalor
no real big improvement in the last years; you can chose among 2.06, 2.14 or 2.14j (which I added for hellijo in Jun22)

I use the 2.06, and my FHEM instance is running on an old RPi 2 (fresh installation with latest Raspberry Pi OS lite 32bit and LXDE on top, with all packages up to date). I use ser2net and have the baud rate set to 9600.

Am I right that the "Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow" messages are because if the poor performance of the RPi2. Or maybe due to the USB-serial adapter cable between the THZ and the RPi that is about 6 m long. Maybe too long? Apart from using a better host for FHEM or trying to place the host device (RPi etc.) closer to the heating with a shorter cable, is there anything else I should look at?

Besides, I see several error messages (see below). Would you mind having a look and let me know if there is something critical I need to deal with? Thank you so much!

Code Auswählen Erweitern

2022.11.14 21:30:49 1: Including fhem.cfg
2022.11.14 21:30:51 3: WEB: port 8083 opened
2022.11.14 21:30:51 2: eventTypes: loaded 0 lines from ./log/eventTypes.txt
2022.11.14 21:30:51 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2022.11.14 21:30:51 1: usb create starting
2022.11.14 21:30:51 3: Probing ZWDongle device /dev/serial0
2022.11.14 21:30:52 3: Probing CUL device /dev/ttyAMA0
2022.11.14 21:30:52 3: Probing TCM_ESP3 device /dev/ttyAMA0
2022.11.14 21:30:52 3: Probing ZWDongle device /dev/ttyAMA0
2022.11.14 21:30:52 3: Probing SIGNALDuino device /dev/ttyAMA0
2022.11.14 21:30:52 3: Probing MYSENSORS device /dev/ttyAMA0
2022.11.14 21:30:53 3: Probing ArduCounter device /dev/ttyAMA0
2022.11.14 21:30:53 3: Probing ElsnerWS device /dev/ttyAMA0
2022.11.14 21:30:54 3: Probing FRM device /dev/ttyAMA0
2022.11.14 21:30:59 1: usb create end
2022.11.14 21:30:59 0: Featurelevel: 6.1
2022.11.14 21:30:59 0: Server started with 6 defined entities (fhem.pl:26635/2022-11-01 perl:5.032001 os:linux user:fhem pid:1040)
2022.11.14 21:52:28 3: FHEMWEB WEB CSRF error:  ne csrf_656581069972857 for client WEB_192.168.178.81_57934 / command xmllist. For details see the csrfToken FHEMWEB attribute.
2022.11.15 18:07:03 0: Server shutdown
2022.11.15 18:07:14 1: Including fhem.cfg
2022.11.15 18:07:15 3: WEB: port 8083 opened
2022.11.15 18:07:15 2: eventTypes: loaded 1 lines from ./log/eventTypes.txt
2022.11.15 18:07:15 1: Including ./log/fhem.save
2022.11.15 18:07:15 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2022.11.15 18:07:15 1: usb create starting
2022.11.15 18:07:15 3: Probing ZWDongle device /dev/serial0
2022.11.15 18:07:16 3: Probing CUL device /dev/ttyAMA0
2022.11.15 18:07:16 3: Probing TCM_ESP3 device /dev/ttyAMA0
2022.11.15 18:07:16 3: Probing ZWDongle device /dev/ttyAMA0
2022.11.15 18:07:16 3: Probing SIGNALDuino device /dev/ttyAMA0
2022.11.15 18:07:16 3: Probing MYSENSORS device /dev/ttyAMA0
2022.11.15 18:07:16 3: Probing ArduCounter device /dev/ttyAMA0
2022.11.15 18:07:17 3: Probing ElsnerWS device /dev/ttyAMA0
2022.11.15 18:07:18 3: Probing FRM device /dev/ttyAMA0
2022.11.15 18:07:23 1: usb create end
2022.11.15 18:07:23 0: Featurelevel: 6.1
2022.11.15 18:07:23 0: Server started with 6 defined entities (fhem.pl:26635/2022-11-01 perl:5.032001 os:linux user:fhem pid:416)
2022.11.15 18:31:49 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:31:49 3: Mythz device opened
2022.11.15 18:31:50 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:33:02 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0A0574 ->
2022.11.15 18:33:05 3: Mythz/RAW: C70A010120009600C8003C
2022.11.15 18:35:26 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0A1732 ->
2022.11.15 18:37:47 3: THZ_Get: Error msg2:  decode: command not known -- FE -> 010302FE1003
2022.11.15 18:37:47 1: PERL WARNING: Use of uninitialized value $sFirmware in sprintf at ./FHEM/00_THZ.pm line 1084.
2022.11.15 18:39:59 1: PERL WARNING: Argument "C70A010120009600C8003C" isn't numeric in multiplication (*) at ./FHEM/00_THZ.pm line 1484.
2022.11.15 18:39:59 1: PERL WARNING: Argument "C70A010120009600C8003C" isn't numeric in addition (+) at ./FHEM/00_THZ.pm line 1484.
2022.11.15 18:40:09 1: PERL WARNING: Argument "120 # Internes Polling Fehlerspeicher" isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:40:17 3: THZ_Get: Error msg3:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0A092B ->
2022.11.15 18:42:26 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0A0928 ->
2022.11.15 18:43:22 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:43:22 3: Mythz device opened
2022.11.15 18:43:24 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:45:04 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:45:04 3: Mythz device opened
2022.11.15 18:45:05 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:45:59 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:45:59 3: Mythz device opened
2022.11.15 18:46:00 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:46:40 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:46:40 3: Mythz device opened
2022.11.15 18:46:41 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:48:56 3: Opening Mythz device pi.fritz.box:2000
2022.11.15 18:48:56 3: Mythz device opened
2022.11.15 18:48:57 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.15 18:52:08 1: PERL WARNING: Argument "28800 # Internes Polling Intervall 8 Stunden" isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:53:27 1: PERL WARNING: Argument "120 # Internes Polling Fehlerspeicher - auch schon mit 8..." isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:54:03 1: PERL WARNING: Argument "300 # Internes Polling Intervall 5 Min." isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:54:25 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0D ->
2022.11.15 18:54:25 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1460.
2022.11.15 18:54:25 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1488.
2022.11.15 18:57:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.15 20:32:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.15 20:37:38 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.15 20:41:01 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.15 21:04:22 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.15 21:30:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.15 21:34:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.15 22:22:39 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.15 23:26:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.15 23:44:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.15 23:46:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.15 23:59:30 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.15 23:59:30 3: Mythz/RAW: number_of_faults: 0 fault0CODE: n.a. fault0TIME: 00:00 fault0DATE: 00.00 fault1CODE: n.a. fault1TIME: 00:00 fault1DATE: 00.00 fault2CODE: n.a. fault2TIME: 00:00 fault2DATE: 00.00 fault3CODE: n.a. fault3TIME: 00:00 fault3DATE: 00.00
2022.11.16 00:19:32 3: THZ_Get: Error msg2:  decode: CRC error in request -- D1 -> 0102FEFB1003
2022.11.16 01:09:19 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 01:33:01 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 01:33:03 3: Mythz/RAW: number_of_faults: 0 fault0CODE: n.a. fault0TIME: 00:00 fault0DATE: 00.00 fault1CODE: n.a. fault1TIME: 00:00 fault1DATE: 00.00 fault2CODE: n.a. fault2TIME: 00:00 fault2DATE: 00.00 fault3CODE: n.a. fault3TIME: 00:00 fault3DATE: 00.00
2022.11.16 02:07:44 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 02:20:25 3: THZ_Get: Error msg2:  decode: new unknown answer  -- D1 -> 018254D11003
2022.11.16 02:46:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 03:04:37 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 03:09:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 03:14:00 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 07:06:41 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.16 07:21:45 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 07:49:51 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 09:13:26 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.16 10:38:06 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.16 11:13:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.16 11:24:50 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.16 11:37:34 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 12:13:35 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F3 ->
2022.11.16 12:36:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 12:41:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 13:05:44 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 13:24:55 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FB ->
2022.11.16 14:29:15 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 15:45:25 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 15:49:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 16:03:32 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->
2022.11.16 16:03:33 3: Mythz/RAW: number_of_faults: 0 fault0CODE: n.a. fault0TIME: 00:00 fault0DATE: 00.00 fault1CODE: n.a. fault1TIME: 00:00 fault1DATE: 00.00 fault2CODE: n.a. fault2TIME: 00:00 fault2DATE: 00.00 fault3CODE: n.a. fault3TIME: 00:00 fault3DATE: 00.00
2022.11.16 16:15:36 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- D1 ->

[willybauss]

My experience is that a shorter and better quality canle reduces the mentioned issues "InterfaceNotRespondig. Maybe too slow".

[immi]

Hi Sunrise
you should pay attention to your config file: there is something very wrong here

Code Auswählen Erweitern


2022.11.15 18:52:08 1: PERL WARNING: Argument "28800 # Internes Polling Intervall 8 Stunden" isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:53:27 1: PERL WARNING: Argument "120 # Internes Polling Fehlerspeicher - auch schon mit 8..." isn't numeric in numeric lt (<) at ./FHEM/00_THZ.pm line 1077.
2022.11.15 18:54:03 1: PERL WARNING: Argument "300 # Internes Polling Intervall 5 Min." i


you should consider the hint from Willy on the cable
you can try all 3 2.06, 2.14 or 2.14j what is best for you
immi