THZ / LWZ Tecalor Stiebel Eltron Heizung

Begonnen von Heiner, 02 Juni 2013, 11:39:13

Vorheriges Thema - Nächstes Thema

maximalz

Hi Martin,
this is a very useful application imho. Did you manage it to get the AussenTemp queried less often?

Frank
THZ (403 SOL), OBIS (2x EDL21), SolarEdge (SE10k), Sun+Luna 2000

immi

Zitat von: mvb am 27 Juli 2014, 11:28:35
What I dislike now is that AussenTemp is updated every second. I was looking for a solution with less "RS232-traffic".
Hi Martin
I  just noticed your sentence, which I do not understand.
Why  do you think you are generating more RS232-traffic?
RS232-traffic will increase only if you poll ofter sGlobal.
Your THRESHOLD script works perfectly, if you poll sGlobal every 5 minutes.
immi


mvb

Hi,

RS-232-traffic:
I defined: attr LWZ interval_sGlobal 300 to have it updated every 5 min.
But, once I open the LWZ readings window, defined by: define LWZ THZ /dev/ttyUSB0@115200
I see the timestamp of "Aussentemp" attr LWZ userReadings AussenTemp {(split ' ',ReadingsVal("LWZ","sGlobal",0))[1]} being updated every second.
Thus I concluded it to be updated every second. But I could be wrong, maybe it's only a feature of the webfrontend and noting happens on the RS-232-Interface.

Anyhow: All work's fine! My compliment to all the guys wrirting this great application.

Today I defined the following. Because LWZ 303 doesn't know public holidays which are on weekdays. When I'm home and not out for work I'd like it a bit warmer:
define BY_Feiertag Calendar ical url http://www.schulferien.org/iCal/Feiertage/icals/Feiertage_Bayern_2014.ics 86400
define HeizungTagbetrieb at *06:00 { if ( !($we) && (Value("BY_Feiertag")) ) { fhem("set LWZ pOpMode DAYmode");; } }
attr HeizungTagbetrieb room Heizung
define HeizungTagbetriebEnd at *21:00 { if ( !($we) && (Value("BY_Feiertag")) ) { fhem("set LWZ pOpMode automatic");; } }
attr HeizungTagbetriebEnd room Heizung

immi

Hi Martin
AussenTemp (as you defined it) has no access to the serial port.
Check sGlobal:
If sGlobal is updated every 5 minutes (as you defined), then you are on the safe side.
If sGlobal is updated ofter, you have a problem, which we have to fix.
immi

lwzler

...so time for a 1st resumée  8)

Thanks to all for the hard work on the script.
FHEM is running now for almost three months a my raspberry pi without any problems.
The only restarts I had to make, were after updates.

The LWZ itself also is running rockstable with different parameters changed via FHEM often.

So I am very happy!  ;D

...the only point I am wondering about is my "Vorlauf- / Rücklauftemperatur" which stays always at ~25°C even when there is noch heating action in the LWZ (and VL-Temp set to 20°C). There also seems to be no influence by the room temperature...a miracle?

micomat

yep, it's called the perpetuum-mobile ;D

same here, awesome work, awesome function. i love it!
Synology DS218+ with fhem+iobroker in docker, 2x RasPi w. ser2net, CUL433+868, IT, EGPM2LAN, THZ/LWZ, FB_Callmonitor, HMS100TF, Homematic, 2x TX3-TH, Pushover, USB-IR-SML-Head, SONOS, GHoma, MBus, KLF200

willybauss

#816
During summer time the room temperature is above 20°C normally, in my case currently approx. 23 ... 24°C. So how should the water in your underfloor heating have any chance to be colder? As long as the heating circle pump is switched off (what's the case for almost 100% of the time in summer mode) there's no way to show varying room temperatures (possibly causing varying water temperatures) to the temperature sensors.

Same with e.g. DHW if you set the target value to 10° during vacation. There's no function cooling down the DHW below normal room temperature.
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS

Floru

Hello together,

first of all a big compliment especially to immi for creating this excellent FHEM Plugin!
I am using this plugin now for about 5 month after I realized that the heatpumpMonitor-project stopped. And with the help of the Wiki, it was quite easy to get FHEM and the THZ-Plugin running.
In the meanwhile I also got used to the overall handling of FHEM and enjoy the comfort of handling my LWZ.

The first real Problem I had, was after updating from v0.101 to v0.108 last week. From this moment on, I realized strange jumps inside my plots.
After debugging a little bit, I found out, that especially long readings were not received completely. A comparison of these revisions showed that the command
select(undef,undef,undef,0.001);
in the function THZ_ReadAnswer was removed. Then I inserted it in line 697 of 00_THZ.pm v0.108 and everything worked fine for me again. For me it seemed to be neccessary for IO synchronisation and maybe only relevant with direct serial connection.
So immi, can you please check, if it is possible to include this command again? Or does this lead to any problems?
Has anybody else realized similar problems since V0.105 (where this line was deleted)?

Thanks,
Florian

p.s. my setup:
LWZ 403 sol with firmware V4.39
FHEM on RaspberryPi connected with 7 m serial cable directly to the front connector of LWZ

immi

Hi Florian
you have the same problem as willy and me. It seams that your timing is even worse than willy's.
The people with direct usb connection do not have it, but have other issues.

I have a solution for you, I will send you a version to test this night.
immi


immi

Dear all
if i define performance as
Performance = heat_transferred_inside_house/electrical_energy_taken_from_the_grid

my heating performance in the last years is 3,2
sHeatHCTotal 7437kWh / sElectrHCTotal 2257 kWh

my hot water performance in the last years is 2,6
sHeatDHWTotal 5751kWh / sElectrDHWTotal 2161kWh

The manual is not really dealing with these topics.
Can anybody confirm my assumption? or ask in http://www.haustechnikdialog.de/?
Are my performances bad, good or excellent?
It would be great if someone from tecalor/StiebelEltron could support us a little.
immi

micomat

Mine is for Heating:
9033/2353 =3.83

for DHW
1090/353 = 3.09
Synology DS218+ with fhem+iobroker in docker, 2x RasPi w. ser2net, CUL433+868, IT, EGPM2LAN, THZ/LWZ, FB_Callmonitor, HMS100TF, Homematic, 2x TX3-TH, Pushover, USB-IR-SML-Head, SONOS, GHoma, MBus, KLF200

houseowner123

Hi immi,

I miss the heat recovered in your equation. Electrical energy + heat recovered is the energy needed to heat your house. For hot water your calc seems right. The values seem right and realistic.

Tom

immi

Tom
I have no idea how to include the heat recovered with the fan.
I just wanted to fix an indicator for benchmarking the heatpump status; something like... if something is wrong the performance should decrease.
I really would appreciate some contribution from tecalor, explaining the readings.

Hi Markus
It is clear that you have solar panels; with such low DHW values
immi

houseowner123

For performance you can use to as rough benchmark but for system efficiency, e.g. energy needed to heat house, you need to consider recovered heat. I have so things in German about all this.
Tecalor can't help you with this. These values vary so much because they depend so much on outside temp. What you need to create is a plot with daily performance ratio on the x-axis and average daily temp on the y-axis. We can then all compare this plot, or the equation of it. But it is hard to compare anyway. Think of Markus with the solar and willy and I have an oven as additional heating source.

firebal301

Hi

Has anyone of you the same error in his logs since friday? (01.08.14)

Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1062.
Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1067.

my new logfile is full of them.

Has anyone an idea why?

thx