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

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

Vorheriges Thema - Nächstes Thema

Heiner

Hi Immi,

danke fuer Dein Feedback. Beide Codeschnipsel  (at und DOIF) gehen leider noch nicht.
Der DOIF meldet aber warum:

PERL WARNING: Argument "" isn't numeric in numeric gt (>) at (eval 144079) line 1.
2020.08.18 04:10:00 3: eval: cooling2: warning in condition c01

Die erste Meldung sagt das die Aussentemperatur keine Numerische Zahl ist - ist Sie aber und auch ohne Einheit. z.B. "16.5". Erwartet fhem eventuell ein Dezimal komma statt Punkt? wie bekomme ich das geloesst?

Die zweite Meldung ist vermutlich weil in der dfefinition 2 mal der Befehl (set Mythz p99startUnschedVent 3) steht, oder?



Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Zitat von: Heiner am 18 August 2020, 07:34:21
Erwartet fhem eventuell ein Dezimal komma statt Punkt? wie bekomme ich das geloesst?
Die zweite Meldung ist vermutlich weil in der dfefinition 2 mal der Befehl (set Mythz p99startUnschedVent 3) steht, oder?
Hi Heiner
no and no-maybe.
I do not get it now; would you mind posting your thz-cfg and a list of register "get Mythz zBackupParameters"?
immi

Heiner

sure here the THZ config:
define Heizung THZ /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0@115200
setuuid Heizung 5c7be3ba-f33f-b5c0-c910-ec9836b0a3b4fb7e
attr Heizung event-on-change-reading .*
attr Heizung interval_sDHW 300
attr Heizung interval_sDisplay 300
attr Heizung interval_sElectrDHWDay 86400
attr Heizung interval_sElectrHCDay 86400
attr Heizung interval_sGlobal 300
attr Heizung interval_sHC1 300
attr Heizung interval_sHeatDHWDay 86400
attr Heizung interval_sHeatHCDay 86400
attr Heizung interval_sHeatRecoveredDay 86400
attr Heizung interval_sHistory 86400
attr Heizung room Heizung
attr Heizung userReadings AussenTemp {(split ' ',ReadingsVal("Heizung","sGlobal",0))[1]},VorlaufTemp {(split ' ',ReadingsVal("Heizung","sGlobal",0))[3]}, RuecklaufTemp {(split ' ',ReadingsVal("Heizung","sGlobal",0))[5]}, WWTemp {(split ' ',ReadingsVal("Heizung","sGlobal",0))[9]}, COP {sprintf("%.2f", (ReadingsNum("Heizung","sHeatHCDay",1) + ReadingsNum("Heizung","sHeatDHWDay",1)) / (ReadingsNum("Heizung","sElectrHCDay",1) + ReadingsNum("Heizung","sElectrDHWDay",1)))}, sD_outsideTemp {(split ' ',ReadingsVal("Heizung","sHC1",0))[1]}, sD_flowTemp {(split ' ',ReadingsVal("Heizung","sHC1",0))[9]}, sD_returnTemp {(split ' ',ReadingsVal("Heizung","sHC1",0))[5]}, sD_insideTempRC {(split ' ',ReadingsVal("Heizung","sHC1",0))[27]}, sD_sFlowRate {(split ' ',ReadingsVal("Heizung","sFlowRate",0))[0]}, sD_dhw_temp {(split ' ',ReadingsVal("Heizung","sDHW",0))[1]}, sD_switchingProg {(split ' ',ReadingsVal("Heizung","sDisplay",0))[1]}, sD_compressor {(split ' ',ReadingsVal("Heizung","sDisplay",0))[3]}, sD_heatingHC {(split ' ',ReadingsVal("Heizung","sDisplay",0))[5]}, sD_heatingDHW {(split ' ',ReadingsVal("Heizung","sDisplay",0))[7]}, sD_boosterHC {(split ' ',ReadingsVal("Heizung","sDisplay",0))[9]}, sD_filterBoth {(split ' ',ReadingsVal("Heizung","sDisplay",0))[11]}, sD_ventStage {(split ' ',ReadingsVal("Heizung","sDisplay",0))[13]}, sD_pumpHC {(split ' ',ReadingsVal("Heizung","sDisplay",0))[15]}, sD_defrost {(split ' ',ReadingsVal("Heizung","sDisplay",0))[17]}, sD_filterUp {(split ' ',ReadingsVal("Heizung","sDisplay",0))[19]}, sD_filterDown {(split ' ',ReadingsVal("Heizung","sDisplay",0))[21]}, roomSetTemp {(split ' ',ReadingsVal("Heizung","sHC1",0))[21]},dhw_set_temp {(split ' ',ReadingsVal("Heizung","sDHW",0))[5]}


the list of register outcome I added, it only includes programming parameter, correct?

Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Hi Heiner
typo: you should keep the same name AusenTemp or AussenTemp 
and maybe write the hour as 04:00 not 4:00

the following script works for me

define cooling DOIF ([04:00-05:00] and [Heizung:AussenTemp] > 17 ) (set Mythz p99startUnschedVent 3) (set Mythz p99startUnschedVent 3)
attr cooling cmdpause 7200
attr cooling devStateIcon cmd_1:vent_ventilation_level_manual_m cmd_2:vent_ventilation_control
attr cooling do always
attr cooling room Heizung
attr cooling wait 3,30

you can also log everything with high verbose.

attr cooling verbose 5
define coolingLog FileLog ./log/cooling-%Y.log cooling
attr coolingLog logtype text
attr coolingLog room Heizung

Heiner

oh shit, how stupid can I be....

Thanks for letting me know this typo, I will try over night and let you know tomorrow
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

TheTrumpeter

Zitat von: Heiner am 12 August 2020, 16:23:59
but it seems the passive cooling function as such in the system, can not be adjusted to work on hot nights as well.
I have now checked if it works, it does: https://forum.fhem.de/index.php/topic,33452.msg1079209.html#msg1079209
FHEM auf RPi3, THZ (LWZ404SOL), RPII2C & I2C_MCP342x (ADCPiZero), PowerMap, CustomReadings, RPI_GPIO, Twilight, nanoCUL (WMBus für Diehl Wasserzähler & Regenerationszähler für BWT AqaSmart), ESPEasy, TPLinkHS110

Heiner

Hi, code from Immi works,

The Trumpeter suggestion to reduce PI target temp in the moment where colling should start, and changing it back once cooling is finished would work likly as well, but you do 2 changes and if something fails, your heating might be wrongly configured and your house do not heat if needed, in that moment to remeber the rout cause is tricky.

In my way if something goes wrong, there os no cooling in hot nights, the rest is normal, that points you directly into the right direction.
I think i prefer this route and keep it as is.

Many Thanks anyhow for your support and thoughts and suggestions
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Hi heiner
2 further suggestions

1) consider updating fhem and changing your userreadings; it should have better performance than your.
attr Heizung userReadings AussenTemp:sHC1.* {THZ_Val("sHC1",21)}, .....................


2) consider making an average over the day before triggering the cooling
[03:00-04:50] and [Heizung:AussenTemp] < 19  and [Heizung:AussenTemp:avg201] > 23 and [Heizung:sD_insideTempRC] > 22.5

it checks if the air outside is fresh
and
it takes the last 201 readings; makes the average and see if it was a hot day
and
it checks if tooo hot inside


Heiner

Hi Immi,

thanks for the suggestion, I did update but have now the problem that the log shows:

Zitat2020.08.23 18:58:21 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 disconnected, waiting to reappear (Heizung)
2020.08.23 18:58:21 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step1  -- FE ->
2020.08.23 18:58:22 3: Setting Heizung serial parameters to 115200,8,N,1
2020.08.23 18:58:22 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 reappeared (Heizung)
2020.08.23 19:00:01 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 disconnected, waiting to reappear (Heizung)
2020.08.23 19:00:01 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0  -- 0A1D82 ->
2020.08.23 19:00:03 3: Setting Heizung serial parameters to 115200,8,N,1
2020.08.23 19:00:03 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 reappeared (Heizung)

shutdow restart  does not help, neither power off/on

I have Version 0.187 now.

Any Idea what I could do?
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Hi Heiner,
it should be fixed with 0.188.
you can update in 2-3 hours
as always do not forget to restart fhem after update
immi

Heiner

Hi Immi,

I installed 0.188 and reboot already twice but no effect, still no syncing....

Any idea what this could be,
could I somehow from somewhere load 0.186 again?

kind regards

Heiner
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Zitat von: Heiner am 24 August 2020, 09:46:43
I installed 0.188 and reboot already twice but no effect, still no syncing....
what do you mean by no syncing?

if you still get error "Maybe too slow THZ_Get_Com: error found at step"  please try

attr Mythz simpleReadTimeout 1

in your case Mythz is Heizung

Heiner

Hi Immi,
yes I mean those messages which effectively shows me not to get updated values  - hence heating is running but not "in sync" with fhem.

I add the attribute but no effect. I shutdown restart but no effect.

The latest in the log:
Zitat2020.08.24 14:44:41 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 disconnected, waiting to reappear (Heizung)
2020.08.24 14:44:41 3: THZ_Get: Error msg2:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0  -- 0B1441 ->
2020.08.24 14:44:41 3: Setting Heizung serial parameters to 115200,8,N,1
2020.08.24 14:44:41 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 reappeared (Heizung)

Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Zitat von: Heiner am 24 August 2020, 14:48:50
Hi Immi,
yes I mean those messages which effectively shows me not to get updated values  - hence heating is running but not "in sync" with fhem.
I add the attribute but no effect. I shutdown restart but no effect.
Hi Heiner
you can update to  0.189 in 2 hours.

check it over 1 day and tell me:
1) how often you get the problem for step0, step1 and step2
2) which is the register in which you have the problem ofter e.g.  0B1441
3)  please upload the log file with all errors

if you do not see an improvement (less error in 1 day), please set the attribute

attr Mythz simpleReadTimeout 2


immi

Heiner

will try, still only V0.188.

I recognised if I do a manul Get request over various register, sometimes data are arrieving.

most of my current problems are step 0 in an about 2min cycle.

But I will wait for 0.189 and be more detailed tomorrow
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2