THZ / LWZ Tecalor Stiebel Eltron Heizung

[willybauss]

why using code for the diagrams? you can choos the values of the diagrams in the plot-gui. thats easier.

I don't believe that's easier than just copy-pasting a gplot file.

[immi]

Tom
i have three ideas:
1)well you can decople the Raspi from the heatpump with a long serail cable (like me), and stop using the direct usb port.
--> I find it uncool.
2) you can forget all your connect-disconnetc and delete them.
---> it is logical but uncool.
3) you can stabilize powersupply of the Raspi, build a EMC-filter, shield the cable and the RASPI with MuSchields (because most of the interference is coming with a magnetic field).
--> if you make a cost-effort analysis does not make any sense...... but you will feel 10 years junger.

immi

[willybauss]

one more idea: did you ever check actual power consumption of your fhem server (Raspi?) against max. allowed power of your power supply? Is there enough space? Don't know if/what you plugged into the USB ports, possibly powered from the Raspi as well.

[micomat]

i use a 3000mA power supply. so thats Not the Problem

[immi]

i use a 3000mA power supply. so thats Not the Problem

current is not everything
not a problem as long as the gnd of your raspi is the gnd of the heatpump usb port
In a small transient could not be the case.
the serial interface has 10V delta between high and low; a usb port has a much smaller tolerance to interference
--> therefore I wrote stabilize powersupply of the Raspi.

immi

[houseowner123]

@willy: Here is the code for the plot:

Code Auswählen Erweitern

set terminal png transparent size <SIZE> crop
set output '<OUT>.png'
set xdata time
set timefmt "%Y-%m-%d_%H:%M:%S"
set xlabel " "
set title 'Energie Wärmerückgewinnung und Warmwasser'
set ytics
set y2tics
set grid ytics
set ylabel "Wh WRG"
set y2label "Wh WW"

#FileLog 4:Mythz.sHeatRecoveredDay\x3a::
#FileLog 4:Mythz.*::

plot "<IN>" using 1:2 axes x1y1 title 'E WRG Tag' ls l0 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'E WW Tag' ls l1 lw 1 with lines

RPi is my shielded network box with all the LAN cables, router and switch. I bet my money on the USB cable. What is an easy and effective way (for testing) to shield this? Aluminium wrap?

Tom

[immi]

hi tom
Aluminion foil cannot stop a magnetic field, only an electric one. Because it is thin and because it is aluminium.
But it is 1:30 and I am just speculating on a magnetic filed.
have a try

try to measure or understand were disturbing noise is coming from
other thing you could do:
- connect nice ground cable between the heatpump and the raspi.
- put a nice capacitor between vdd and gnd in the raspi to stabilize vdd.

immi

[Heiner]

Hi,

may I missed it, but is the Filter-change flag  already identified? It would be very cool to get a alram displayd and perhaps a EMail notification once Filter Need to be changed.

[willybauss]

The flag isn't identified so far, but I don't suggest you to use it anyway. The THZ just takes the fan's power consumption at power-up as a good-condition value. Afterwards it compares actual power values against this good-condition value. As soon as the power consumption increased by a defined percentage the flag will be set.
So if you need to power down your THZ for any reason, the next power-up value will be used as good-condition value, even if the last filter change happened months ago. Therefore I don't use this flag at all. My indicator is simply the color of the foam rubber filters at the exhaust openings. Over time the black color changes to white, caused by dust.
Alternatively you can manually set a good condition value when you change filters. Then let fhem do this comparison and send you the email etc. Attached screen shot shows power consumption difference before/after filter change.

[immi]

dear all
I am using the statistics module frome some days.

Code Auswählen Erweitern


define statistiche statistics Mythz
attr statistiche deltaReadings sHeatDHWTotal,sHeatHCTotal,sElectrDHWTotal,sElectrHCTotal,sBoostDHWTotal
attr statistiche minAvgMaxReadings AussenTemp,RuecklaufTemp,VorlaufTemp,WWTemp


it provide out of the box, interesting information.
have a try and look after some days.
p.s. AussenTemp,RuecklaufTemp,VorlaufTemp,WWTemp are a split of sGlobal.
p.s.2 the reading will get a stat prefix directly in Mythz: e.g. statAussenTemp

immi

[micomat]

will try it

[willybauss]

don't understand why some initial values directly after having started the statistics are unequal to zero:

Code Auswählen Erweitern

statSBoostDHWTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSElectrDHWTotal Hour: 3.0 Day: 3.0 Month: 3.0 Year: 3.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSElectrHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSHeatDHWTotal Hour: 12.0 Day: 12.0 Month: 12.0 Year: 12.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSHeatHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36

edit:
ok, a few minutes later the values are zero now - for any reason

[immi]

don't understand why some initial values directly after having started the statistics are unequal to zero:

Code Auswählen Erweitern

statSBoostDHWTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSElectrDHWTotal Hour: 3.0 Day: 3.0 Month: 3.0 Year: 3.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSElectrHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSHeatDHWTotal Hour: 12.0 Day: 12.0 Month: 12.0 Year: 12.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
statSHeatHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-07_23:44:51 ) 2014-07-07 23:56:36
edit:
ok, a few minutes later the values are zero now - for any reason

look at the logs between 23:56:36 and 23:44:51
edit: you probably do not update statSHeatDHWTotal  very often; so when you saved the config, it made an update and you have 12 more

[micomat]

quite different here:
min/max/avg stats are working. deltaReadings not as expected?

Code Auswählen Erweitern

statAussenTempDay Min: 11.1 Avg: 11.7 Max: 12.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statAussenTempMonth Min: 11.1 Avg: 11.7 Max: 12.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statAussenTempYear Min: 11.1 Avg: 11.7 Max: 12.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statRuecklaufTempDay Min: 21.2 Avg: 23.4 Max: 27.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statRuecklaufTempMonth Min: 21.2 Avg: 23.4 Max: 27.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statRuecklaufTempYear Min: 21.2 Avg: 23.4 Max: 27.2 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statVorlaufTempDay Min: 21.1 Avg: 23.7 Max: 28.5 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statVorlaufTempMonth Min: 21.1 Avg: 23.7 Max: 28.5 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statVorlaufTempYear Min: 21.1 Avg: 23.7 Max: 28.5 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statWWTempDay Min: 43.0 Avg: 43.4 Max: 43.7 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statWWTempMonth Min: 43.0 Avg: 43.4 Max: 43.7 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statWWTempYear Min: 43.0 Avg: 43.4 Max: 43.7 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20

statSBoostDHWTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statSBoostDHWTotalLast Hour: 0.0 Day: - Month: - Year: - 2014-07-09 09:59:55
statSBoostHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_09:51:20 ) 2014-07-09 10:50:20
statSBoostHCTotalLast Hour: 0.0 Day: - Month: - Year: - (since: 2014-07-09_09:51:20 ) 2014-07-09 09:59:55
statSElectrDHWTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statSElectrDHWTotalLast Hour: 0.0 Day: - Month: - Year: - 2014-07-09 09:59:55
statSElectrHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statSElectrHCTotalLast Hour: 0.0 Day: - Month: - Year: - 2014-07-09 09:59:55
statSHeatDHWTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statSHeatDHWTotalLast Hour: 0.0 Day: - Month: - Year: - 2014-07-09 09:59:55
statSHeatHCTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_07:21:20 ) 2014-07-09 10:50:20
statSHeatHCTotalLast Hour: 0.0 Day: - Month: - Year: - 2014-07-09 09:59:55
statSHeatRecoveredTotal Hour: 0.0 Day: 0.0 Month: 0.0 Year: 0.0 (since: 2014-07-09_10:30:25 ) 2014-07-09 10:50:20

[immi]

quite different here:
min/max/avg stats are working. deltaReadings not as expected?

What are you expecting?
wait some weeks, as you see, it is collecting data from 2 hours (since: 2014-07-09_07:21:20).
I started looking at it some days ago, in order to understand; fo me it is also interesting for enocean products.
Module statistics does not interact with thz or with filelog. It is a basic feature from FHEM.
I think it is parsing all readings-updates matching the given regular-expression.
immi