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

[mlb]

I was also looking at PQc and Pel. Most of times values seem rather reasonable, but sometimes they look too good to be true - like the peak here: can it be the heatpump temporarily has over 700% of  efficiency gain?

[willybauss]

Still I was hoping to register values like sElectrDHWDay or sElectrHCDay on daily basis just to track usage in different months, just for some reason they are not shown on graphs reasonably.

you simply could write the daily values to the log file at 23:59 every night and create a graph later on

Thanks - good itea, I will look at it. Just I noticed it needs the old type of meter with rotating plate, they are no longer used here... maybe I could find a used one.

The Youless has a config menu where you can enter the numper of pulses per kWh, so you're completely free on which kind of meter you choose.

[houseowner123]

@mlb: Good news for you: The Youless LS110 can be programmed in FHEM to take care of the low and high priced energy usage: http://forum.fhem.de/index.php/topic,16105.msg162791.html#msg162791

[immi]

I was also looking at PQc and Pel. Most of times values seem rather reasonable, but sometimes they look too good to be true - like the peak here: can it be the heatpump temporarily has over 700% of  efficiency gain?

I also have such peaks somtetimes; do not know where they come from

[belu]

Hi,

it looks like my MyTHZ Module does not work. Stop Working Yesterday at 15:02. Version 1.37

This is the actual answer Log Verbose 5

2015.02.28 13:10:31 5: Mythz start Funktion THZ_ReadAnswer
2015.02.28 13:10:31 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.02.28 13:10:31 5: THZ_Get: Error msg2: 'InterfaceNotRespondig error found at step1 error found at step2'
2015.02.28 13:10:32 5: THZ_Get: Try to get 'programHC2_Tu_1'
2015.02.28 13:10:32 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.02.28 13:10:32 5: Mythz sending 02
2015.02.28 13:10:32 5: SW: 02
2015.02.28 13:10:32 5: Mythz start Funktion THZ_ReadAnswer
2015.02.28 13:10:32 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.02.28 13:10:32 5: THZ_Get: Error msg2: 'InterfaceNotRespondig error found at step1 error found at step2'

i checked the USB connection on linux, restart raspberry update raspberry, all ok, mythz does not work.

Thats not good...

My THZ works without problems. i Checked Display and Paramter, works....

Restart THZ.... Now THZ and MyTHZ Modul works again.

Can the MyTHZ Modul kill the THZ UART USB Modul?

[immi]

Have I understood correctly?
your UART USB interface in your heatpump stopped working and restarted only after you restarted the heatpump.
If this is the case, only Tecalor can anwser your question.

[belu]

Hi,

Also nochmal zum Verständnis, MyTHZ Modul bekommt keine Antwort mehr von der THZ. Habe dann alles geupdatet und mehrmals neugestartet ohne Erfolg. Im Raspian dann USB überprüft alles Ok und da.

Verbose auf 5 gestellt und da ist dann das von eben gekommen. Keine Antwort.
War schon recht ratlos. Habe die THZ dann geschaut ob alles ok ist. Istwerte alle ok und verändern sich. Habe dann einen 10 Sekunden reset gemacht und dann ist alles wieder in Ordnung.

Ist jetzt natürlich nicht so prall. Ursachenforschung ist hier schwierig.

Hast schon recht. Mal beobachten. System war so 60 Tage an.

LG

[immi]

v 0.138 uploaded
- p32HystDHW added

[micomat]

Hi,

it looks like my MyTHZ Module does not work. Stop Working Yesterday at 15:02. Version 1.37

This is the actual answer Log Verbose 5

2015.02.28 13:10:31 5: Mythz start Funktion THZ_ReadAnswer
2015.02.28 13:10:31 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.02.28 13:10:31 5: THZ_Get: Error msg2: 'InterfaceNotRespondig error found at step1 error found at step2'
2015.02.28 13:10:32 5: THZ_Get: Try to get 'programHC2_Tu_1'
2015.02.28 13:10:32 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.02.28 13:10:32 5: Mythz sending 02
2015.02.28 13:10:32 5: SW: 02
2015.02.28 13:10:32 5: Mythz start Funktion THZ_ReadAnswer
2015.02.28 13:10:32 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.02.28 13:10:32 5: THZ_Get: Error msg2: 'InterfaceNotRespondig error found at step1 error found at step2'

i checked the USB connection on linux, restart raspberry update raspberry, all ok, mythz does not work.

Thats not good...

My THZ works without problems. i Checked Display and Paramter, works....

Restart THZ.... Now THZ and MyTHZ Modul works again.

Can the MyTHZ Modul kill the THZ UART USB Modul?

did you try to disconnect/reconnect the USB cable before resetting everything? sometimes a hard break is needed on USB. that may belong to the THZ, but it also may belong to the (sometimes quite instable) USB on the RasPi.
I also saw such behavior sometimes in the past.

[belu]

Hi micomat,

Yes i have disconnect the cable from the Usb port and changed to an other. But no connect with MyThz the THZ will not give a answer...

[micomat]

hm... so that may be a special problem

[immi]

my 2 cents:
Belu's UART USB interface in his heatpump stopped working
Belu said that restarting the PI or disconnecting the cable did´t help.
The  UART USB interface  restarted only after Belu resetted the heatpump.

I see 3 possible root-cause
1)   Firmware bug. The heatpump went in a Software-State which did not support serial communication.
2)   Hardware problem: The heatpump went in a Hardware-State which did not support serial communication.
        a.      Emv/emc caused it
        b.         An electronic component of the heatpump electronics is wearing out

1 and 2a are statistical events equally distributed over time. I would do nothing.
2b is also a statistical event but will increase its frequency of appearance. Keep an eye on it.
immi

[willybauss]

@ belu:
Could it have happened that the USB port had a small line drop and afterwards got a new port number, e.g. switched from ...USB0 to ...USB1? That's what I had a few days ago. Locking the port number by using a udev definition didn't help reliably. My solution was quite simple.

[willybauss]

it is possble to set the time from fhem, if someone implements it.
nevertheless I do not see how this feature could be usefull. you set it  and do not change it for 10 years.

Today I got the reason for having the THZ's time synchronized tu the FHEM server. I added a few rows to my config in order to get total values per day:

Code Auswählen Erweitern

define GetsHeatHCDay at *23:59:00 get Mythz sHeatHCDay
attr GetsHeatHCDay room Heizung
define GetsElectrDHWDay at *23:59:00 get Mythz sElectrDHWDay
attr GetsElectrDHWDay room Heizung
define GetsElectrHCDay at *23:59:00 get Mythz sElectrHCDay
attr GetsElectrHCDay room Heizung
define GetsHeatDHWDay at *23:59:00 get Mythz sHeatDHWDay
attr GetsHeatDHWDay room Heizung
define GetsHeatRecoveredDay at *23:59:00 get Mythz sHeatRecoveredDay
attr GetsHeatRecoveredDay room Heizung

Surprisingly all the logged values were close to zero. Debugging showed that there's a time offset between the THZ and the fhem server; so the values had been read at approx. 00:01 instead of 23:59. As a workaround I use 23:55:00 now, hoping that the difference won't increase so far.

btw: monthly values can be read using this code:

Code Auswählen Erweitern

define GetsBoostDHWTotal at *00:01:00 {if($mday == 1) { "get Mythz sBoostDHWTotal" }}
attr GetsBoostDHWTotal room Heizung
define GetsBoostHCTotal at *00:01:00 {if($mday == 1) { "get Mythz sBoostHCTotal" }}
attr GetsBoostHCTotal room Heizung
define GetsElectrDHWTotal at *00:01:00 {if($mday == 1) { "get Mythz sElectrDHWTotal" }}
attr GetsElectrDHWTotal room Heizung
define GetsElectrHCTotal at *00:01:00 {if($mday == 1) { "get Mythz sElectrHCTotal" }}
attr GetsElectrHCTotal room Heizung
define GetsHeatDHWTotal at *00:01:00 {if($mday == 1) { "get Mythz sHeatDHWTotal" }}
attr GetsHeatDHWTotal room Heizung
define GetsHeatHCTotal at *00:01:00 {if($mday == 1) { "get Mythz sHeatHCTotal" }}
attr GetsHeatHCTotal room Heizung
define GetsHeatRecoveredTotal at *00:01:00 {if($mday == 1) { "get Mythz sHeatRecoveredTotal" }}
attr GetsHeatRecoveredTotal room Heizung
define GetsHistory at *00:01:00 {if($mday == 1) { "get Mythz sHistory" }}
attr GetsHistory room Heizung

edit: code updated

[immi]

>> .. hoping that the difference won't increase so far.
Hi Willy
you can monitor the drift with

Code Auswählen Erweitern


sTimedate
Weekday: Monday Hour: 23 Min: 2 Sec: 30 Date: 2015/3/2
2015-03-02 23:01:43


I see 7 second drift in the last 10 month.
immi