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

[sunrise]

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

Ok, I will place my RPi with a shorter & hopefully better cable nearer to the heating.

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

I assume that's because I had added comments to my commands when I executed them:

Code Auswählen Erweitern

define Mythz THZ pi.fritz.box:2000
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
attr Mythz interval_sGlobal 300 # Internes Polling Intervall 5 Min.
attr Mythz interval_sHistory 28800 # Internes Polling Intervall 8 Stunden
attr Mythz interval_sLast10errors 120 # Internes Polling Fehlerspeicher - auch schon mit 86400 gesehen
attr Mythz interval_sDHW 400
attr Mythz interval_sElectrDHWDay 2400
attr Mythz interval_sElectrDHWTotal 43200
attr Mythz interval_sHC1 400
attr Mythz interval_sHeatDHWDay 2400
attr Mythz interval_sHeatDHWTotal 43200
attr Mythz interval_sHeatRecoveredDay 2400
attr Mythz interval_sHeatRecoveredTotal 43200
attr Mythz event-min-interval s.*:4800
attr Mythz event-on-change-reading .*
attr Mythz userReadings insideSetTemp:sHC1.* {THZ_Val("sHC1",21)}, insideTemp:sHC1.* {THZ_Val("sHC1",27)}, AussenTemp:sGlobal.* {THZ_Val("sGlobal",1)}
attr Mythz firmware 2.06
attr Mythz room Keller
attr FileLog_Mythz room Keller

Apart from the comments (which I have to omit), do these values make sense?

Code Auswählen Erweitern

attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 120

[immi]

Apart from the comments (which I have to omit), do these values make sense?

Code Auswählen Erweitern

attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 120

Hi sunrise
first: check in your firmware, if you can get the above register.
e.g. in some older tecalor there was not sLast10errors  or sHistory.
second: increase the intervall as  much as you can, in order to decrease the workload of your heatpump
e.g. why you need  sLast10errors every 2 minutes? I pull it every 8h
immi

[sunrise]

Hi sunrise
first: check in your firmware, if you can get the above register.
e.g. in some older tecalor there was not sLast10errors  or sHistory.
second: increase the intervall as  much as you can, in order to decrease the workload of your heatpump
e.g. why you need  sLast10errors every 2 minutes? I pull it every 8h
immi

Yes, it's there, as well as sHistory - see screenshots. And I have another observation, i.e. I restarted FHEM, and realised that the MyTHZ was completely gone. No big deal (though I wonder why it is gone - does it not "stick" after restart?), as I started the definition from scratch with more conservative timings:

Code Auswählen Erweitern

define Mythz THZ pi.fritz.box:2000
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 28800
attr Mythz interval_sDHW 300
attr Mythz interval_sElectrDHWDay 3600
attr Mythz interval_sElectrDHWTotal 43200
attr Mythz interval_sHC1 300
attr Mythz interval_sHeatDHWDay 3600
attr Mythz interval_sHeatDHWTotal 43200
attr Mythz interval_sHeatRecoveredDay 3600
attr Mythz interval_sHeatRecoveredTotal 43200
attr Mythz event-min-interval s.*:4800
attr Mythz event-on-change-reading .*
attr Mythz userReadings insideSetTemp:sHC1.* {THZ_Val("sHC1",21)}, insideTemp:sHC1.* {THZ_Val("sHC1",27)}, AussenTemp:sGlobal.* {THZ_Val("sGlobal",1)}
attr Mythz firmware 2.06
attr Mythz room Keller
attr FileLog_Mythz room Keller

The Log from the time point of the execution of these commands reads this:

Code Auswählen Erweitern

2022.11.17 18:07:14 3: Opening Mythz device pi.fritz.box:2000
2022.11.17 18:07:14 3: Mythz device opened
2022.11.17 18:07:15 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
So I am back to square one and to Willi's recommendation to check the cable.

[sunrise]

@immi

Sorry, I shall not use screenshots anymore, so here it is:

Code Auswählen Erweitern

define Mythz THZ pi.fritz.box:2000
attr Mythz devStateIcon opened:10px-kreis-gruen disconnected:10px-kreis-rot
attr Mythz event-min-interval s.*:4800
attr Mythz event-on-change-reading .*
attr Mythz firmware 2.06
attr Mythz interval_sDHW 300
attr Mythz interval_sElectrDHWDay 3600
attr Mythz interval_sElectrDHWTotal 43200
attr Mythz interval_sGlobal 300
attr Mythz interval_sHC1 300
attr Mythz interval_sHeatDHWDay 3600
attr Mythz interval_sHeatDHWTotal 43200
attr Mythz interval_sHeatRecoveredDay 3600
attr Mythz interval_sHeatRecoveredTotal 43200
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 28800
attr Mythz room Heating
attr Mythz userReadings insideSetTemp:sHC1.* {THZ_Val("sHC1",21)}, insideTemp:sHC1.* {THZ_Val("sHC1",27)}, AussenTemp:sGlobal.* {THZ_Val("sGlobal",1)}
#   CFGFN     
#   DEF        pi.fritz.box:2000
#   DeviceName pi.fritz.box:2000
#   FD         8
#   FUUID      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#   NAME       Mythz
#   NR         25
#   NTFY_ORDER 50-Mythz
#   PARTIAL   
#   STATE      opened
#   TYPE       THZ
#   VERSION    0.205
#   eventCount 36
#   READINGS:
#     2022-11-17 19:08:56   AussenTemp      8.9
#     2022-11-17 19:08:56   inputVentilatorPower 45 %
#     2022-11-17 19:06:29   mainVentilatorPower 0 %
#     2022-11-17 19:08:35   p01-p12         p01RoomTempDay: 20.5 p02RoomTempNight: 20.5 p03RoomTempStandby: 10 p04DHWsetTempDay: 48 p05DHWsetTempNight: 48 p06DHWsetTempStandby: 10 p07FanStageDay: 2 p08FanStageNight: 2 p09FanStageStandby: 2 p10HCTempManual: 35 p11DHWsetTempManual: 48 p12FanStageManual: 1
#     2022-11-17 19:08:59   p04DHWsetTempDay 48 °C
#     2022-11-17 19:08:35   p11DHWsetTempManual 48 °C
#     2022-11-17 19:08:43   p13GradientHC1  0.4
#     2022-11-17 19:06:21   p20FlowProportionHC2 100 %
#     2022-11-17 19:06:23   p21Hyst1        4 K
#     2022-11-17 19:09:05   p23Hyst3        3 K
#     2022-11-17 19:08:52   p44UnschedVent2 60 min
#     2022-11-17 19:09:02   p57OutTempMinPumpCycles 20 °C
#     2022-11-17 19:09:02   pCircPump       p54MinPumpCycles: 1 p55MaxPumpCycles: 288 p56OutTempMaxPumpCycles: 15 p57OutTempMinPumpCycles: 20 p58SuppressTempCaptPumpStart: 60
#     2022-11-17 19:08:37   pClockMonth     11
#     2022-11-17 19:08:41   pDHWProg        progDHWStartTime: 23:00 progDHWEndTime: 07:00 progDHWMonday: 1 progDHWTuesday: 1 progDHWWednesday: 1 progDHWThursday: 1 progDHWFriday: 1 progDHWSaturday: 1 progDHWSunday: 1 progDHWEnable: 0
#     2022-11-17 19:08:51   pFan            p37Fanstage1AirflowInlet: 100 p38Fanstage2AirflowInlet: 135 p39Fanstage3AirflowInlet: 170 p40Fanstage1AirflowOutlet: 100 p41Fanstage2AirflowOutlet: 135 p42Fanstage3AirflowOutlet: 170 p43UnschedVent3: 60 p44UnschedVent2: 60 p45UnschedVent1: 60 p46UnschedVent0: 60 p75PassiveCooling: 0
#     2022-11-17 19:08:47   pFanProg        progFAN1StartTime: 20:00 progFAN1EndTime: 09:00 progFAN1Monday: 1 progFAN1Tuesday: 1 progFAN1Wednesday: 1 progFAN1Thursday: 1 progFAN1Friday: 1 progFAN1Saturday: 1 progFAN1Sunday: 1 progFAN1Enable: 0 progFAN2StartTime: 13:30 progFAN2EndTime: 14:30 progFAN2Monday: 1 progFAN2Tuesday: 1 progFAN2Wednesday: 1 progFAN2Thursday: 1 progFAN2Friday: 1 progFAN2Saturday: 1 progFAN2Sunday: 1 progFAN2Enable: 0
#     2022-11-17 19:08:43   pHeat1          p13GradientHC1: 0.4 p14LowEndHC1: 3 p15RoomInfluenceHC1: 0 p16GradientHC2: 0.6 p17LowEndHC2: 0 p18RoomInfluenceHC2: 0 p19FlowProportionHC1: 30 p20FlowProportionHC2: 100 MaxSetHeatFlowTempHC1: 45 MinSetHeatFlowTempHC1: 5 MaxSetHeatFlowTempHC2: 35 MinSetHeatFlowTempHC2: 5
#     2022-11-17 19:09:05   pHeat2          p21Hyst1: 4 p22Hyst2: 3 p23Hyst3: 3 p24Hyst4: 2 p25Hyst5: 1 p26Hyst6: 1 p27Hyst7: 1 p28Hyst8: 1 p29HystAsymmetry: 2 p30integralComponent: 100 p31MaxBoostStages: 3 MaxHeatFlowTemp: 75 p49SummerModeTemp: 17 p50SummerModeHysteresis: 2 p77OutTempFilterTime: 1 p78DualModePoint: 0 p79BoosterTimeoutHC: 20
#     2022-11-17 19:08:39   pHeatProg       progHC1StartTime: 23:00 progHC1EndTime: 07:00 progHC1Monday: 1 progHC1Tuesday: 1 progHC1Wednesday: 1 progHC1Thursday: 1 progHC1Friday: 1 progHC1Saturday: 0 progHC1Sunday: 0 progHC1Enable: 0 progHC2StartTime: 00:00 progHC2EndTime: 08:00 progHC2Monday: 0 progHC2Tuesday: 0 progHC2Wednesday: 0 progHC2Thursday: 0 progHC2Friday: 0 progHC2Saturday: 1 progHC2Sunday: 1 progHC2Enable: 0
#     2022-11-17 19:06:19   progDHWMonday   1
#     2022-11-17 19:09:07   progDHWStartTime 23:00
#     2022-11-17 19:08:41   progDHWThursday 1
#     2022-11-17 19:09:09   progFAN1Monday  1
#     2022-11-17 19:08:57   progFAN2Enable  0
#     2022-11-17 19:08:47   progFAN2EndTime 14:30
#     2022-11-17 19:09:03   progFAN2Sunday  1
#     2022-11-17 19:08:45   progHC1Thursday 1
#     2022-11-17 19:08:53   progHC1Tuesday  1
#     2022-11-17 19:06:27   progHC2EndTime  08:00
#     2022-11-17 19:08:49   progHC2Sunday   1
#     2022-11-17 19:08:39   progHC2Wednesday 0
#     2022-11-17 19:08:56   sGlobal         outsideTemp: 8.9 flowTemp: 31.1 returnTemp: 29.9 hotGasTemp: 36.8 dhwTemp: 34.8 flowTempHC2: 0 evaporatorTemp: 15.9 condenserTemp: 30.4 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 1 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 1 lowPressureSensor: 1 evaporatorIceMonitor: 1 signalAnode: 0 evuRelease: n.a. ovenFireplace: 0 STB: n.a. outputVentilatorPower: 45 inputVentilatorPower: 45 mainVentilatorPower: 0 outputVentilatorSpeed: 24 inputVentilatorSpeed: 21 mainVentilatorSpeed: 0 outsideTempFiltered: 10 relHumidity: n.a. dewPoint: n.a. P_Nd: n.a. P_Hd: n.a. actualPower_Qc: n.a. actualPower_Pel: n.a. collectorTemp: 81 insideTemp: 0
#     2022-11-17 19:08:37   sTimedate       Weekday: Thursday pClockHour: 19 pClockMinutes: 9 Sec: 12 pClockYear: 22 pClockMonth: 11 pClockDay: 17
#     2022-11-17 19:05:12   state           opened
#     2022-11-17 19:09:14   z_Last_fhem_err THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 10 ->
#   helper:
#
setstate Mythz opened
setstate Mythz 2022-11-17 19:08:56 AussenTemp 8.9
setstate Mythz 2022-11-17 19:08:56 inputVentilatorPower 45 %
setstate Mythz 2022-11-17 19:06:29 mainVentilatorPower 0 %
setstate Mythz 2022-11-17 19:08:35 p01-p12 p01RoomTempDay: 20.5 p02RoomTempNight: 20.5 p03RoomTempStandby: 10 p04DHWsetTempDay: 48 p05DHWsetTempNight: 48 p06DHWsetTempStandby: 10 p07FanStageDay: 2 p08FanStageNight: 2 p09FanStageStandby: 2 p10HCTempManual: 35 p11DHWsetTempManual: 48 p12FanStageManual: 1
setstate Mythz 2022-11-17 19:08:59 p04DHWsetTempDay 48 °C
setstate Mythz 2022-11-17 19:08:35 p11DHWsetTempManual 48 °C
setstate Mythz 2022-11-17 19:08:43 p13GradientHC1 0.4
setstate Mythz 2022-11-17 19:06:21 p20FlowProportionHC2 100 %
setstate Mythz 2022-11-17 19:06:23 p21Hyst1 4 K
setstate Mythz 2022-11-17 19:09:05 p23Hyst3 3 K
setstate Mythz 2022-11-17 19:08:52 p44UnschedVent2 60 min
setstate Mythz 2022-11-17 19:09:02 p57OutTempMinPumpCycles 20 °C
setstate Mythz 2022-11-17 19:09:02 pCircPump p54MinPumpCycles: 1 p55MaxPumpCycles: 288 p56OutTempMaxPumpCycles: 15 p57OutTempMinPumpCycles: 20 p58SuppressTempCaptPumpStart: 60
setstate Mythz 2022-11-17 19:08:37 pClockMonth 11
setstate Mythz 2022-11-17 19:08:41 pDHWProg progDHWStartTime: 23:00 progDHWEndTime: 07:00 progDHWMonday: 1 progDHWTuesday: 1 progDHWWednesday: 1 progDHWThursday: 1 progDHWFriday: 1 progDHWSaturday: 1 progDHWSunday: 1 progDHWEnable: 0
setstate Mythz 2022-11-17 19:08:51 pFan p37Fanstage1AirflowInlet: 100 p38Fanstage2AirflowInlet: 135 p39Fanstage3AirflowInlet: 170 p40Fanstage1AirflowOutlet: 100 p41Fanstage2AirflowOutlet: 135 p42Fanstage3AirflowOutlet: 170 p43UnschedVent3: 60 p44UnschedVent2: 60 p45UnschedVent1: 60 p46UnschedVent0: 60 p75PassiveCooling: 0
setstate Mythz 2022-11-17 19:08:47 pFanProg progFAN1StartTime: 20:00 progFAN1EndTime: 09:00 progFAN1Monday: 1 progFAN1Tuesday: 1 progFAN1Wednesday: 1 progFAN1Thursday: 1 progFAN1Friday: 1 progFAN1Saturday: 1 progFAN1Sunday: 1 progFAN1Enable: 0 progFAN2StartTime: 13:30 progFAN2EndTime: 14:30 progFAN2Monday: 1 progFAN2Tuesday: 1 progFAN2Wednesday: 1 progFAN2Thursday: 1 progFAN2Friday: 1 progFAN2Saturday: 1 progFAN2Sunday: 1 progFAN2Enable: 0
setstate Mythz 2022-11-17 19:08:43 pHeat1 p13GradientHC1: 0.4 p14LowEndHC1: 3 p15RoomInfluenceHC1: 0 p16GradientHC2: 0.6 p17LowEndHC2: 0 p18RoomInfluenceHC2: 0 p19FlowProportionHC1: 30 p20FlowProportionHC2: 100 MaxSetHeatFlowTempHC1: 45 MinSetHeatFlowTempHC1: 5 MaxSetHeatFlowTempHC2: 35 MinSetHeatFlowTempHC2: 5
setstate Mythz 2022-11-17 19:09:05 pHeat2 p21Hyst1: 4 p22Hyst2: 3 p23Hyst3: 3 p24Hyst4: 2 p25Hyst5: 1 p26Hyst6: 1 p27Hyst7: 1 p28Hyst8: 1 p29HystAsymmetry: 2 p30integralComponent: 100 p31MaxBoostStages: 3 MaxHeatFlowTemp: 75 p49SummerModeTemp: 17 p50SummerModeHysteresis: 2 p77OutTempFilterTime: 1 p78DualModePoint: 0 p79BoosterTimeoutHC: 20
setstate Mythz 2022-11-17 19:08:39 pHeatProg progHC1StartTime: 23:00 progHC1EndTime: 07:00 progHC1Monday: 1 progHC1Tuesday: 1 progHC1Wednesday: 1 progHC1Thursday: 1 progHC1Friday: 1 progHC1Saturday: 0 progHC1Sunday: 0 progHC1Enable: 0 progHC2StartTime: 00:00 progHC2EndTime: 08:00 progHC2Monday: 0 progHC2Tuesday: 0 progHC2Wednesday: 0 progHC2Thursday: 0 progHC2Friday: 0 progHC2Saturday: 1 progHC2Sunday: 1 progHC2Enable: 0
setstate Mythz 2022-11-17 19:06:19 progDHWMonday 1
setstate Mythz 2022-11-17 19:09:07 progDHWStartTime 23:00
setstate Mythz 2022-11-17 19:08:41 progDHWThursday 1
setstate Mythz 2022-11-17 19:09:09 progFAN1Monday 1
setstate Mythz 2022-11-17 19:08:57 progFAN2Enable 0
setstate Mythz 2022-11-17 19:08:47 progFAN2EndTime 14:30
setstate Mythz 2022-11-17 19:09:03 progFAN2Sunday 1
setstate Mythz 2022-11-17 19:08:45 progHC1Thursday 1
setstate Mythz 2022-11-17 19:08:53 progHC1Tuesday 1
setstate Mythz 2022-11-17 19:06:27 progHC2EndTime 08:00
setstate Mythz 2022-11-17 19:08:49 progHC2Sunday 1
setstate Mythz 2022-11-17 19:08:39 progHC2Wednesday 0
setstate Mythz 2022-11-17 19:08:56 sGlobal outsideTemp: 8.9 flowTemp: 31.1 returnTemp: 29.9 hotGasTemp: 36.8 dhwTemp: 34.8 flowTempHC2: 0 evaporatorTemp: 15.9 condenserTemp: 30.4 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 1 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 1 lowPressureSensor: 1 evaporatorIceMonitor: 1 signalAnode: 0 evuRelease: n.a. ovenFireplace: 0 STB: n.a. outputVentilatorPower: 45 inputVentilatorPower: 45 mainVentilatorPower: 0 outputVentilatorSpeed: 24 inputVentilatorSpeed: 21 mainVentilatorSpeed: 0 outsideTempFiltered: 10 relHumidity: n.a. dewPoint: n.a. P_Nd: n.a. P_Hd: n.a. actualPower_Qc: n.a. actualPower_Pel: n.a. collectorTemp: 81 insideTemp: 0
setstate Mythz 2022-11-17 19:08:37 sTimedate Weekday: Thursday pClockHour: 19 pClockMinutes: 9 Sec: 12 pClockYear: 22 pClockMonth: 11 pClockDay: 17
setstate Mythz 2022-11-17 19:05:12 state opened
setstate Mythz 2022-11-17 19:09:14 z_Last_fhem_err THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 10 ->


With the exception of the "too slow" and "interface not responding" message, this seems to be ok. Do you agree?

I looked into the commandref about the THZ but could not find an explanation for the meaning of these attributes:

Code Auswählen Erweitern


interval_sDHW
interval_sElectrDHWDay
interval_sElectrDHWTotal
interval_sGlobal
interval_sHC1
interval_sHeatDHWDay
interval_sHeatDHWTotal
interval_sHeatRecoveredDay
interval_sHeatRecoveredTotal
interval_sHistory
interval_sLast10errors


Some of them I think I know about (e.g., DHW=domestic heating water?) but others I have no idea about. If I looked in the wrong place, where can I find more background information about them?

Is there a GitHub repo (e.g. https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/00_THZ.pm), where I could find more information and maybe ask questions or report issues about the THZ module?

Or rather there? https://svn.fhem.de/trac/browser/trunk/fhem/FHEM/00_THZ.pm

[sunrise]

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

@immi
Now I have attached a new cable (3 wires à 2.5 mm² each, 10 cm long) between the serial plug at the THZ and the USB-serial adapter (Prolific). I still have these "too slow" messages:

Code Auswählen Erweitern


2022.11.19 16:58:16 1: pi.fritz.box:2000 reappeared (Mythz)
2022.11.19 16:58:19 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.19 16:59:38 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0B ->
2022.11.19 16:59:38 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1460.
2022.11.19 16:59:38 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1488.
2022.11.19 17:06:31 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0D ->
2022.11.19 17:10:12 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0D ->


What are the other warnings and errors about?

[sunrise]

@immi @willi
Despite the very short cable and another USB-serial adapter I still see these messages. What else can I do about them? Thanks for your help!

[willybauss]

Is there really no change - number of such messages per day is still same as before?
Then I don't have an idea.
In my case the number of such issues decreased by >80% by using a better cable connection.

[sunrise]

There are even more messages, so I fear that I messed with the cable soldering. Which kind of cable and plug do you use? Do you have a USB-serial adapter or have you connected the 3 serial wires (Tx, Rx, GND) directly to your e.g. Raspberry Pi GPIOs?

[willybauss]

USB-serial adapter. But am using a shielded cable; shield to be connected to ground as always for shieldings. 2.5mm² isn't a sign of quality for a data cable at all. Such cable is for high current usage, not for data transmission. But with 10cm a shielding may also not make sense.

[sunrise]

Yes, I agree with you. I didn't mean that the 2.5 mm² was good for this, but just wanted to let you know. And indeed there increase of numbers of these messages seems to correlate with the new but unshielded cable. What the exact reason is. I don't know yet, but I will switch back to the original cable (3 wires. rather thin, but shielded). About the shield (thin foil): Where should I connect it to? The old cable (with less problems) is shown in the screenshots.

[willybauss]

Shield goes always to Ground connection; for Sub-D 9 this is pin 5:
https://jo-fri.github.io/Eisenbahn/ProLok/download/RS232Pinbelegung.pdf

Connect just the Sub-D side to ground, but let the opposite side unconnected.

[hellijo]

Shield goes always to Ground connection; for Sub-D 9 this is pin 5:
https://jo-fri.github.io/Eisenbahn/ProLok/download/RS232Pinbelegung.pdf

Connect just the Sub-D side to ground, but let the opposite side unconnected.

I have the wiring as described. Sometimes the error message appears that the heat pump is responding too slowly.
You also get the error message if you query data too quickly in a row.

I had discussed this with andre.k and he also suspects that it is due to the connection being established. No handshake to know that there is a correct connection.

[sunrise]

What do you mean about the handshake? It's there none? Should there be one? I have now ordered a female Sub-D9 screw port and hope to get improved connectivity. BTW, the baud rate (ser2net.yaml) is set to 9600, i.e. according to what I understand should be used for older THZs (without the "iPod" dial but with the plain LCD display with rubber buttons). Do I have to set the baud rate elsewhere, too?

[sunrise]

@immi @willybauss
I have now a new cable connection (shielded) with only very few "too slow" messages. Maybe it's because of the slow RPi2 and/or the slow serial connection (9600 baud rate) of this old heating.

However, I'm not sure what these mean:

Code Auswählen Erweitern


2022.11.26 16:52:04 3: Mythz/RAW: THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow
2022.11.26 17:03:04 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 17 ->
2022.11.26 17:03:04 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1460.
2022.11.26 17:03:04 1: PERL WARNING: Use of uninitialized value $msg2 in concatenation (.) or string at ./FHEM/00_THZ.pm line 1488.
2022.11.26 17:18:33 3: THZ_Set: Error msg:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- 0180051700CF00CD006401E001E00064020202015E01E0011003 ->
2022.11.26 18:12:25 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->
2022.11.26 18:22:28 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- F4 ->


[sunrise]

By the way, does it matter on which side of the cable the shield is grounded?