FHEM Forum

FHEM => Codeschnipsel => Thema gestartet von: Heiner am 02 Juni 2013, 11:39:13

Titel: THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 02 Juni 2013, 11:39:13
Hi,

ich bin recht neu im Forum und tu mich noch recht schwer. In einer Google Gruppe hat ein User IMMI eine THZ.pm gebaut um  die THZ von Tecalor oder baugleiche LWZ von Stiebel Eltron mit FHEM zu loggen. Leider ist die Google gruppe geschlossen und die Software in einem recht frühen Stadium.

Link: https://groups.google.com/forum/#!msg/fhem-users/ANgUIF9Qea4/wXsU6HeF4MoJ (//groups.google.com/forum/#!msg/fhem-users/ANgUIF9Qea4/wXsU6HeF4MoJ)

Ich habe nun dieses modul ausprobiert und siehe da, erste Erfolge. Das Heizungslog zeigt Connceted, jedoch wird igendwie beider zyklischen Pruefung ob die Anlage noch verbunden ist auch immer wieder ein Disconnected gesendet.
2013-06-01_13:29:59 Heizung DISCONNECTED
2013-06-01_13:29:59 Heizung CONNECTED
2013-06-01_13:31:59 Heizung DISCONNECTED
2013-06-01_13:31:59 Heizung CONNECTED

Das Log bleibt aber leer, ich hab da her den loglevel auf 5 gesetzt  und hab in die THZ.pm je Submodul einen Logeintrag erzeugt, und bekomme ein paar Details mehr:

2013.06.01 12:48:22 5: Notify loop for Heizung CONNECTED
2013.06.01 12:49:40 1: THZ_GetUpdate
2013.06.01 12:49:40 1: THZ_Get
2013.06.01 12:49:40 1: THZ_Write
2013.06.01 12:49:40 5: Heizung sending 02                    
2013.06.01 12:49:40 5: SW: 02
2013.06.01 12:49:40 1: THZ_ReadAnswer
2013.06.01 12:49:40 1: THZ_Write
2013.06.01 12:49:40 5: Heizung sending 0100FCFB1003
2013.06.01 12:49:40 5: SW: 0100FCFB1003
2013.06.01 12:49:40 1: THZ_ReadAnswer
2013.06.01 12:49:40 1: THZ_Write
2013.06.01 12:49:40 5: Heizung sending 10
2013.06.01 12:49:40 5: SW: 10
2013.06.01 12:49:40 1: THZ_ReadAnswer
2013.06.01 12:49:40 1: THZ_Parse
2013.06.01 12:49:40 1: THZ_checksum
2013.06.01 12:50:07 1: THZ_GetUpdate
2013.06.01 12:50:07 1: THZ_Get
2013.06.01 12:50:07 1: THZ_Write
2013.06.01 12:50:07 5: Heizung sending 02
2013.06.01 12:50:07 5: SW: 02
2013.06.01 12:50:07 1: THZ_ReadAnswer
2013.06.01 12:50:07 1: THZ_Write
2013.06.01 12:50:07 5: Heizung sending 0100FCFB1003
2013.06.01 12:50:07 5: SW: 0100FCFB1003
2013.06.01 12:50:07 1: THZ_ReadAnswer
2013.06.01 12:50:07 1: THZ_Write
2013.06.01 12:50:07 5: Heizung sending 10
2013.06.01 12:50:07 5: SW: 10
2013.06.01 12:50:07 1: THZ_ReadAnswer
2013.06.01 12:50:07 1: THZ_Parse
2013.06.01 12:50:07 1: THZ_checksum
2013.06.01 12:50:12 1: THZ_GetUpdate
2013.06.01 12:50:12 1: THZ_Get
2013.06.01 12:50:12 1: THZ_Write
2013.06.01 12:50:12 5: Heizung sending 02
2013.06.01 12:50:12 5: SW: 02
2013.06.01 12:50:12 1: THZ_ReadAnswer
2013.06.01 12:50:12 1: /dev/ttyUSB0 disconnected, waiting to reappear

Leider komm ich dennoch nicht weiter. Gib es eigentlich sowas wie einen Debugger wo man Schritt für Schritt durch den Code geht, und immer sehen kann was passiert? Ich sehe hier nur das die Anlage mit FHEM "spricht" aber es gibt offensichtlich keine korrekte Interpretation der Daten die das logfile füllen.

Kann mir hier irgendjemand helfen? Gibt es noch den Google-Group USER Immi der hier so eine tolle vorarbeit geleistet hat? und der/die ggf. helfen kann?

Vielen Dank schon mal.



Titel: Aw: THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 03 Juni 2013, 08:43:02
Hi,

wenn ich das richtig sehe geht die Kommunikation laut Rober Prenz eigentlich so:
# would be a nice help in THZ.pm header
# 02                   THZ:10                       #are you ready?     THZ:ok
# 01 00 FE FD 10 03    THZ:10 02                    #Firmware No?       THZ:ok, are you ready?
# 10                   THZ:01 00 B5 FD 01 B6 10 03  #ok                 THZ:01 B6 is  Firmware
# 01 00 FC FB 10 03    THZ:10 02                    #Tell me the data?  THZ:ok, are you ready?
# 10                   THZ:"all Data"               #ok                 THZ:Data
#
# in general:          01 00 xx xx = Header
#                      10 03 = Footer

Das bedeutet in meinem Log dann wohl schlicht das die Anfrage kommt aber eben keine Antwort. Daraus schliesse ich das vermutlich der Speed noch nciht stimmt, also am besten mal mit einem Terminalprogramm direkt versuchen ob man die Kommunikation hinbekommt, also auf eine 02 die Antwort 10.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 Januar 2014, 13:59:38
Hallo zusammen
I had again some time during Christmas and therefore I restarted the porting to FHEM of a monitor interface for the tecalor/Eltron heatpump.
http://forum.fhem.de/index.php/topic,8018.msg53948.html (http://forum.fhem.de/index.php/topic,8018.msg53948.html)

I am running it since ca 14 months and Heiner, Matthias and Steffen are kindly helping testing it. Some of them offered to write an how-to in german and make some support in the forum, sharing their experience. The  firmware of our heatpump is 4.39 but we have different THZ versions (403 and 303) and different serial interface speeds (57600 or 115200)
Please find  enclosed the THZ-module v0.060

config example:

  define Mythz THZ /dev/ttyUSB0@115200
  attr Mythz room waermepumpe
  define atMythzFB at +*00:05:00 {fhem "get Mythz allFB","1";;return()}   
  define atMythz09 at +*05:00:00 {fhem "get Mythz history","1";;return()}
  define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
  attr FileLog_Mythz logtype thz:plot,text
  attr FileLog_Mythz room waermepumpe
  define wal_0 SVG FileLog_Mythz:thz:CURRENT
  attr wal_0 room waermepumpe


with version 0.060:
   
THZ.pm has been testd on fritzbox, nas-qnap, raspi and macos.
This module is not working if you have an older firmware; Nevertheless, "parsing" could be easily updated, because now the registers are well described.
https://answers.launchpad.net/heatpumpmonitor/+question/100347 (https://answers.launchpad.net/heatpumpmonitor/+question/100347)

In the next week-ends I would like to clean up and improove the readings.
I read cerefully the guidelines for developers and the discussions on the units % °C K bar kWh...

At the time, I am reading from the heatpump only a very small part of the available settings.
The heatpump is providing hundreds of parameters, and the units are somewhere necessary; otherwise the user would be very very confused.
Therefore I added (in some cases) the units  to the value during parsing.
I know this is very bad, but I do not have a better idea.
Actually I liked very much the proposal from Markus Block;
http://forum.fhem.de/index.php?topic=18238.0 (http://forum.fhem.de/index.php?topic=18238.0)
readingsBulkUpdate($hash, $reading, $value, $changed, $unit)
But I acknolege that the vision of Rudolf has lead FHEM to a great architecture, and therefore I respect his opinion.


Any suggestion is very welcome, I do not want to leave the readings section like this.
Feel free to reply in german, I write faster in english if you do not mind.

l.g.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 20 Januar 2014, 07:32:18
Thanks a lot :)
Will try this instead of Robert Penz HeatpumpMonitor which is no longer supported.

Best,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: rudolfkoenig am 23 Januar 2014, 10:36:00
immi asked me through a private message that i add a comment:

I don't really know what you expect: if you wish to add this module to the FHEM distribution, you are welcome, if you want to distributed by update, then you have to support it. Send me your sourceforge-id, so you can check in this module directly.

Btw.
- requiring the user to do some additional at definitions is unusual/inelegant, usually this is done by the module itself with InternalTimer.
- i have the feeling, that the module triggers one large/long reading instead of a list, if this is correct, than it makes reacting to only parts of this message harder then necessary.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 Januar 2014, 15:35:12
Hi Rudolf
Concerning InternalTimer; I used it in the previous version; I took it away thinking to give more power to the users. They decide to update what they want when they want. I can put it back. Easy.

The readings in the THZ_define subfunction have to be optimized, you are right; it is on my opl. I wanted to refresh all parameters once at the fhem-start.

Concerning  FHEM distribution, please wait; I would like to have more feedback from users before taking the ownership.

My big question still remains unsolved.
how can I implement units in readings (see my post above) in an elegant way?

thanks for your comments
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: rudolfkoenig am 23 Januar 2014, 16:08:52
ZitatThey decide to update what they want when they want.
They could also do that with attributes. I'm not against your solution, I just think it is unusual and inelegant. And this is only my opinion, and not the law.

Zitathow can I implement units in readings (see my post above) in an elegant way?
Just put it space separated after the value. Or set only the value, and describe the unit in the documentation.
A complete documentation should describe all possible events (see e.g. http://fhem.de/commandref.html#ZWaveevents), so that users can create notifies/FileLogs/etc before the first such event arrives (e.g. battery empty/etc).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Januar 2014, 22:07:30
Many many thanks to immi  :)
It's working absolutely perfect! I would say much better than the heatpumpmonitor from Robert :)

Best,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 Januar 2014, 19:10:50
Hey,

again thanks to immi for adding the collector_temp in v.0.061.
Now i can see all the plots i need, but i also want to see some additional information in the "room" where i have added the heating.
So how can i show the data from long readings like "history" or "allFB" as shown in the graphics added by immi? For example i want to display the compressor_heating value from the history reading.

Thanks for help :)
Attached is the V0.061 with the solar collector temp added.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2014, 20:30:17
Hi Markus
i do not know if I have got your question
if you want a title in plots you can use

define wal_2 SVG FileLog_Mythz:thz1:CURRENT
attr wal_2 title "Temp --> Max $data{max1}, Min $data{min1}, Current $data{currval1}"


if you want to show some values in a nice way, have a look at the new module readingsGroup
http://forum.fhem.de/index.php/topic,14425.210.html
It looks really great how Adam organized his data.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 Januar 2014, 20:49:05
Hi immi,

thanks for that hint :)
It's getting better and better. Configured 5 plots for the heatpump now.

Best,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Februar 2014, 11:09:54
Dear all
please find enclosed v 0.063:
I reintroduced InternalTimer for polling automatically some registers at regular intervals.
As suggested by Rudolf, you can now control the interval with an attribute.
define Mythz THZ /dev/ttyUSB0@115200
attr Mythz interval_allFB 300      # internal polling interval 5min 
attr Mythz interval_history 28800  # internal polling interval 8h   
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz

If the attributes interval_allFB and interval_history are not defined (or 0), their internal polling is disabled. 
Clearly you can also define the polling interval outside the module with the "at" command, as before.
define Mythz THZ /dev/ttyUSB0@115200
define atMythzFB at +*00:05:00 {fhem "get Mythz allFB","1";;return()}   
define atMythz09 at +*08:00:00 {fhem "get Mythz history","1";;return()}   
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz

     
Please test both configurations. Please tell me if you see differences or issues.
best regards
immi

@micomat: I am happy for your success!! Please share your plots, configs, and screenshots. Comment them in german, so that more users can benefit from the THZ module. 
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Februar 2014, 16:50:54
Heres my Config:

define Mythz THZ 192.168.18.151:2003
attr Mythz room Heizung
define atMythzFB at +*00:05:00 {fhem "get Mythz allFB","1";;return()}   
define atMythz09 at +*05:00:00 {fhem "get Mythz history","1";;return()}
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
attr FileLog_Mythz logtype thz:plot,text
# attr FileLog_Mythz room Heizung
define plot_0 SVG FileLog_Mythz:thz:CURRENT
attr plot_0 room Heizung
define plot_1 SVG FileLog_Mythz:thz1:CURRENT
attr plot_1 room Heizung
define plot_2 SVG FileLog_Mythz:thz2:CURRENT
attr plot_2 room Heizung
define plot_3 SVG FileLog_Mythz:thz3:CURRENT
attr plot_3 room Heizung
define plot_4 SVG FileLog_Mythz:thz4:CURRENT
attr plot_4 room Heizung


Plots showing:
0 = Temperaturen mit Kollektor/Temps including solar collector
1 = Wassertemperaturen / water temps
2 = interne Druecke / internal pressures
3 = interne Temperaturen / internal temperatures
4 = Lüfter in % / Fans in percent

Ich kann gerne auch die plot-files bereitstellen.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Februar 2014, 23:52:29
dear all
please find enclosed version 0.065


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 11 Februar 2014, 17:17:03
Great work!
Runs like a charm :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 14 Februar 2014, 09:10:49
Thank you very much. It works fine and much more stable than the heatpumpmonitor on the Fritzbox 7270, fortunately.

One small thing which is not working:
The Booster values are always Zero, even when the heatpump runs on first or second Booster (see attached screenshot)
I assume this may be due to manufacturer- model- and Firmwareversion differences.

@immi: My time is limited - and yours as well I am sure - but could you maybe though give me a hint/how you Analyse the traffic and find out the values etc?
... what I have up and running: FHEM on 7270 with usbserial/FTDI kernel Drivers. LWZ303Sol connected via USB/RS232 Adapter to the Fritzbox. Additionally Network Connection to that via ser2net and HWVirtualSerialPort on the Laptop. On it running the Stiebel Eltron Service Software for the LWZ.

Thanks for your time
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Februar 2014, 09:50:32
Hi xyz_fhem
if you have  a Network Connection  via ser2net to HWVirtualSerialPort, run the Stiebel Eltron Service Software and log.
You can activate the logging function of ser2net: the command of ser2net "TB" is your friend.

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=40216
please share your finding in this forum

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 Februar 2014, 15:31:11
Zitat von: xyz_fhem am 14 Februar 2014, 09:10:49
One small thing which is not working:
The Booster values are always Zero, even when the heatpump runs on first or second Booster (see attached screenshot)
I assume this may be due to manufacturer- model- and Firmwareversion differences.

you better be lucky that the booster is always 0. The booster is the electrical auxiliary heating which is only activated in the case the heatpump cannot reach the designated temperatures itself. This can maybe caused by very low temperatures like below -10°C.

auf deutsch:
der booster ist nur fuer den fall, dass die waermpepumpe die solltemperaturen alleine nicht schafft. das ist beispielsweise bei sehr niedrigen aussentemperaturen unter -10°C der fall. somit solltest du dich eigentlich freuen das der booster aus ist ;)

gruß
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 Februar 2014, 01:53:22
v 0.067
-- Party_time register discovered and implemented (read-only)
-- 00_THZ.pm added to  FHEM directory. Update fhem or download it directly.

https://sourceforge.net/p/fhem/code/HEAD/tree/trunk/fhem/FHEM/00_THZ.pm

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 Februar 2014, 12:14:50
working :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 20 Februar 2014, 08:44:15
Hallo,

habe eine LWZ 404 und bisher noch keinen Erfolg mit der serialen Schnittstelle gehabt, läuft das Modul auch mit der x04 Serie, oder nur mit den 303/403?

Gruß
Micha
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 20 Februar 2014, 12:33:34
Hi,
keine Ahnung obs mit der 404er auch geht.
Versuch doch mal mit den seriellen Geschwindigkeiten zu spielen.
Oder den USB onboard zu nutzen (sollte der noch an der gleichen Stelle sein).
Bei USB sollte es mit 115200bau funktionieren.
Welche Software ist denn drauf?

Gruß,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Februar 2014, 15:54:17
Hi michaelk68
Markus is right: No Idea if the 404 is using the same comunication protocoll.
There is no documentation of the protocolls from Tecalor :(
Old protocolls have been described by reverse engeneering (logging of the serial comunication).

Let us start slowly
First we need to understand:
1) do you have a bad serial communication (hardware/cable/contacts defect) ?
2) Do you have a bad configuration of the serial port (wrong baudrate/wrong port) ?
3) does the protocoll of 404 differ from 403/303?


for 1 and 2 test your hardware with another serial appliance.
for 3 tell us which firmware do you have on the heatpump


best regards
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 20 Februar 2014, 17:44:45
Hi immi and Markus,

I have a 404 with software release 5.39.
I tested with a laptop and a raspberry with a serial-USB adapter and different baudrates without success over a serial cable, with the pin layout from Robert Penz.
I think the cable is right.


Best regards
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Februar 2014, 17:51:13
Hi Michael
you have to be sure that
1) do you have a bad serial communication (hardware/cable/contacts defect) ?
2) Do you have a bad configuration of the serial port (wrong baudrate/wrong port) ?

in order to be sure send hex "02" from a terminal emulator.
If you have 1 and 2 without errors, the heatpump answers Hex "10"

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 20 Februar 2014, 18:33:23
Hi,

5.39 sounds to me like a modified 4.39 to fit the new hardware in the 404.

You could try to connect via the internal USB interface on the controller board with 115200 baud.
On my 303 the serial interface did not work at all. Only with the onboard USB i got the connection running.

Could you provide a ZIP code from where you live?

regards,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 21 Februar 2014, 10:16:37
Hi,

I'm located in 88699, will test it over the weekend with an USB cable.
Do you have an idea, with which program I can test the connection under windows?

br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: olindner am 21 Februar 2014, 14:39:31
Hallo Zusammen, ich habe eine 303 (Version noch nicht herausbekommen). Bekomme leider keine Daten geleifert. Muss ich den LOG bei der LWZ aktivieren? Brauche ich zwingend, die Service Software von Stiebel?
Im Log sehe ich diese Einträge
2014.02.21 14:25:51 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.02.21 14:25:52 3: Setting Mythz baudrate to 115200
2014.02.21 14:25:52 1: /dev/ttyUSB0 reappeared (Mythz)
2014.02.21 14:26:01 2: Mythz/RAW: 000000000000
2014.02.21 14:26:01 2: Mythz/RAW: 00000000000000
2014.02.21 14:26:04 2: Mythz/RAW: 00000000
2014.02.21 14:26:04 2: Mythz/RAW: 0000000000000000
2014.02.21 14:28:09 2: Mythz/RAW: 000000
2014.02.21 14:28:09 2: Mythz/RAW: 00000000000000
2014.02.21 14:28:10 2: Mythz/RAW: 000000
2014.02.21 14:28:13 2: Mythz/RAW: 0000
2014.02.21 14:28:13 2: Mythz/RAW: 00000000000000000000
2014.02.21 14:30:18 2: Mythz/RAW: 000000
2014.02.21 14:30:18 2: Mythz/RAW: 00000000000000000000
2014.02.21 14:30:22 2: Mythz/RAW: 000000
2014.02.21 14:30:22 2: Mythz/RAW: 000000000000000000


vielen vielen Dank für Eure Unterstützung uvg Olaf
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 14:41:31
oh thats not so far :)
i'm in 86920.

just take an ordinary USB cable Type A to Type B like it's used for printers.
http://www.amazon.de/USB-2-0-Kabel-grau-3m/dp/B0013F8R8I
If the USB is the same as on 303 it fits perfectly.

I will look for the tool i used for testing and let you know the name today.

Best,
Markus

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 14:43:01
Zitat von: olindner am 21 Februar 2014, 14:39:31
Hallo Zusammen, ich habe eine 303 (Version noch nicht herausbekommen). Bekomme leider keine Daten geleifert. Muss ich den LOG bei der LWZ aktivieren? Brauche ich zwingend, die Service Software von Stiebel?
Im Log sehe ich diese Einträge
vielen vielen Dank für Eure Unterstützung uvg Olaf


Okay, wie bist DU mit der 303 verbunden? Seriell oder USB?
Hast Du ein Terminalprogramm mit dem Du die grundlegende Kommunikation testen kannst?
Auf der 303 muss nichts weiter konfiguriert werden, das funktioniert out-of-the-box.

Gruß,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 15:25:29
hallo zusammen,

ich hab immer das hterm verwendet.
http://www.der-hammer.info/terminal/

gruß
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 15:35:36
Here is a plot file config from my setup:

# Created by FHEM/98_SVG.pm, 2014-01-31 14:27:59
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 'Temperaturen'
set ytics
set y2tics
set grid
set ylabel "Temp"
set y2label "°C"

#FileLog 5:Mythz.allFB\x3a::
#FileLog 83:Mythz.allFB\x3a::
#FileLog 13:Mythz.allFB\x3a::

plot "<IN>" using 1:2 axes x1y2 title 'Aussen Temp' ls l0 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'Kollektor Temp' ls l1 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'Warmwasser' ls l2 lw 1 with lines


FileLog 5, 83 and 13 are the counts of the variables used in the graphs from the allFB output. Just separated by space. You can count on your own.

And here is the code from fhem.cfg
define plot0 SVG FileLog_Mythz:thz:CURRENT
attr plot0 room Heizung


best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: olindner am 21 Februar 2014, 15:39:40
Zitat von: micomat am 21 Februar 2014, 14:43:01
Okay, wie bist DU mit der 303 verbunden? Seriell oder USB?
Hast Du ein Terminalprogramm mit dem Du die grundlegende Kommunikation testen kannst?

Hallo Markus, ich habe einen USB to TTL RS232 Adapter "FTDI USB Serial Device converter now attached to ttyUSB0" am PI dran. Habe ich das falsche Kabel? :( Wie kann ich die Kommunikation unter Linux testen?

vielen Dank uvg Olaf
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 16:41:53
Hi,

also unter Linux hab ich immer das python tool von Robert Penz genutzt das dem heatpumpmointor beiliegt. Ich kenne leider derzeit kein passendes Terminalprogramm. Ob Minicom hex senden kann weiß ich nicht.

http://robert.penz.name/heat-pump-lwz/

Gruß
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 21 Februar 2014, 18:57:54
Hallo,

also ich habe jetzt mit meinem Laptop ein USB Kabel dran, mit hterm und 115K Baudrate kommt nach 2 eine 10 hex zurück.

Jetzt werd ich mich mal an die Installation von fhem auf meinem Raspi machen.
Kann ich mit dem Laptop noch mehr testen?

Gruß
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Februar 2014, 19:23:48
perfekt also funktioniert die Verbindung.
mehr brauchst's du nicht zu testen :)
fhem ran konfig rein glücklich sein ;)
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Februar 2014, 20:10:13
Great job Markus and Michael
in the meanwhile, I uploaded version 0.068; tomorrow you can test it with fhem update.

https://sourceforge.net/p/fhem/code/HEAD/tree/trunk/fhem/FHEM/00_THZ.pm

changelog
-- now you can also define the time at which holiday begins and ends (before was read-only)
-- corrected some typos

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Februar 2014, 20:24:48
Zitat von: michaelk68 am 21 Februar 2014, 10:16:37
Hi,

I'm located in 88699, will test it over the weekend with an USB cable.
Do you have an idea, with which program I can test the connection under windows?

br
Michael
Hi Michael
,
I used Bray++for the same reason:  https://sites.google.com/site/terminalbpp/ (https://sites.google.com/site/terminalbpp/)

Bray++'s advantage is that you can write macros to send a number of hex commands in sequence, including defineable delays. For example using the macro
$02%DLY0010$01$00$FE$FD$10$03%DLY0010$10
will do the whole communication in order to request the firmware revision from the THZ (while ignoring the intermediate answers from the THZ, but just waitung a few milliseconds, assuming that the answer is being sent correctly).

$02%DLY0010$01$00$FC$FB$10$03%DLY0010$10

will request the 59 byte data string instead.

So using one of these macros in Bray++'s hex mode you should get an answer. If not play a bit with the communication settings. These should be

8 data bits
no parity
1 stop bit
57600 or 115200 baud

Good luck
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 21 Februar 2014, 20:26:53
I'm a newbie to Fhem, could you quickly explain, what I need to do, to run your module in fhem.
In the meantime I installed fhem on my raspi and downloaded your module.
but whats next?

br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Februar 2014, 20:41:59
unter Linux tut CuteCom gute Dienste als Terminalprogramm zum testen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Februar 2014, 20:52:07
Hi Michael
easy:
in ./fhem.cfg you fix all pathes and add

define Mythz THZ /dev/ttyUSB0@115200
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz


then you start fhem with

perl ./fhem.pl ./fhem.cfg


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 21 Februar 2014, 20:55:31
Hi immi,

do I need to copy your module 00_THZ.pm anywhere within fhem?

Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Februar 2014, 21:49:05
hi michael
the module 00_THZ should be in ./FHEM/

if you start fhem and give the command "update", you will fetch the new version in the right directory

after that, you restart
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Februar 2014, 22:45:16
Was mir noch nicht klar ist: in welcher Form werden die ausgelesenen Daten gespeichert - z.B. sqlite-DB? Kann ich auch nachträglich noch z.B. eine Ein-Tages-Grafik von vor 3 Monaten abrufen und anzeigen? Kann ich den Speicherort z.B. per nfs mount auf mein NAS auslagern, um nicht pausenlos auf der SD-Karte des raspi rum schreiben zu müssen? Generell ist ja die SD-Karte mit ihren begrenzten Schreibzyklen der Hasenfuß des raspi ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Februar 2014, 00:08:07
fhem schreibt die Daten in Text Logs. wo diese liegen ist frei definierbar.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Februar 2014, 10:52:14
Hi immi,

i have a lot of such log in my fhem log:
2014.02.21 19:36:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 19:36:00 1: 192.168.178.50:2003 reappeared (Mythz)
2014.02.21 19:36:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 19:36:00 1: 192.168.178.50:2003 reappeared (Mythz)
2014.02.21 19:36:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 19:36:00 1: 192.168.178.50:2003 reappeared (Mythz)
2014.02.21 19:36:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 19:36:00 1: 192.168.178.50:2003 reappeared (Mythz)
2014.02.21 19:36:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 19:36:00 1: 192.168.178.50:2003 reappeared (Mythz)
2014.02.21 21:25:00 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.02.21 21:25:00 1: 192.168.178.50:2003 reappeared (Mythz)


is there maybe some kind of timeout problem?
the system with .50 is always reachable.

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 Februar 2014, 17:36:41
Zitat von: micomat am 22 Februar 2014, 00:08:07
fhem schreibt die Daten in Text Logs. wo diese liegen ist frei definierbar.

markus
o.k., das könnte man ja wahrscheinlich leicht in ein csv-Format ändern, womit recht einfach der Zugriff auf irgendwelche alte Daten möglich wird.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Februar 2014, 18:18:13
Hi Markus
I am aware of the log-garbage: connect/disconnect/conect...
very annoying, I noticed it 3 weeks ago.
I hope that it is sporadic also for you and not connected with the last version.
The THZ module is loosing contact to ser2net and tries to reconnect too fast.
In 1 second you get 50 retries; and each retry is logged; look at the timestamp.
I have to find a way to delay the reconnect, without affecting overall fhem performance.
Maybe some fhem expert developers can help me, but I cannot post on the developer-subforum.

I will try to fix it in 1 or 2 weeks.

Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 22 Februar 2014, 18:52:47
Hi,

it seems to work :-)

2014-02-22_18:44:48 Mythz programHC1_Mo-So_1: 00:00--24:00
2014-02-22_18:44:49 Mythz party-time: 26:15--05:45
2014-02-22_18:44:49 Mythz firmware: version: 5.39
2014-02-22_18:44:49 Mythz holidayEnd_year: 0
2014-02-22_18:44:49 Mythz allFB: outside_temp: 4.8 flow_temp: 50.6 return_temp: 45.2 hot_gas_temp: 91.6 dhw_temp: 41.8 flow_temp_HC2: 22.4 evaporator_temp: 5.1 condenser_temp: 46.8 Mixer_open: 1 Mixer_closed: 0 HeatPipeValve: 0 DiverterValve: 0 DHW_Pump: 0 HeatingCircuit_Pump: 0 Solar_Pump: 0 Compressor: 0 BoosterStage3: 0 BoosterStage2: 0 BoosterStage1: 0 HighPressureSensor: 1 LowPressureSensor: 0 EvaporatorIceMonitor: 0 SignalAnode: 0 EVU_release: 1 OvenFireplace: 0 STB: 0 OutputVentilatorPower: 38 InputVentilatorPower: 38 MainVentilatorPower: 70 OutputVentilatorSpeed: 22 InputVentilatorSpeed: 32 MainVentilatorSpeed: 22 Outside_tempFiltered: 3.7 Rel_humidity: 0 DEW_point: 390 P_Nd: 3.9 P_Hd: 20.95 Actual_power_Qc: -9442 Actual_power_Pel: 16397 collector_temp: -60

how can I get a plot of these values?

br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Februar 2014, 19:59:28
@immi
okay, thanks for the info. i don't know when it start, but as long as it's no problem for the system i can live with that.

@michael
great job! so it's proved to work with the 404, too =)
i recently posted a version of one of my plot files. mybe this helps you creating your own.
here is a start config, just add to the fhem.cfg where the thz is defined
define plotname SVG FileLog_Mythz:thz:CURRENT
attr plotname room wherever


then cklick on the plotname in the room and you can edit the plot details
plot title, labels and so on.
for the data you have to count the output on the bottom of the config page.
you can see the Aussen Temp in my example is on the 5th position in the output, so it is #5 in the plot config. and so on... just follow the picture added and it should work.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Februar 2014, 20:48:15
great michael
happy that it THZ is working with a LWZ404 with firmware 5.39

2 small hints

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Februar 2014, 20:52:39
Immi,
by the way i translated the THZ commandref to German.
I translated some other modules before and now i did this to the THZ.  I think it should be online the next days.

Best
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 24 Februar 2014, 20:04:05
Hi immi,

I think, not all values are correct, for example compressor is allway 0.
I attached one record as sample, temperature values seems to be right.

outside_temp: 1.9 flow_temp: 33.4 return_temp: 27.4 hot_gas_temp: 74.7 dhw_temp: 44.5 flow_temp_HC2: 29.5 evaporator_temp: 0.1 condenser_temp: 30.1 Mixer_open: 0 Mixer_closed: 1 HeatPipeValve: 1 DiverterValve: 0 DHW_Pump: 0 HeatingCircuit_Pump: 0 Solar_Pump: 0 Compressor: 0 BoosterStage3: 0 BoosterStage2: 0 BoosterStage1: 0 HighPressureSensor: 1 LowPressureSensor: 0 EvaporatorIceMonitor: 0 SignalAnode: 0 EVU_release: 1 OvenFireplace: 0 STB: 0 OutputVentilatorPower: 38 InputVentilatorPower: 38 MainVentilatorPower: 70 OutputVentilatorSpeed: 21 InputVentilatorSpeed: 31 MainVentilatorSpeed: 22 Outside_tempFiltered: 2.6 Rel_humidity: 0 DEW_point: 333 P_Nd: 3.33 P_Hd: 13.73 Actual_power_Qc: 27851 Actual_power_Pel: 16343 collector_temp: -60

br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 24 Februar 2014, 21:33:08
Hi michaelk68.

I have the same "issue".

2014-02-24 21:19:59 THZ Mythz allFB: outside_temp: 6.4 flow_temp: 28.8 return_temp: 24.2 hot_gas_temp: 65.4 dhw_temp: 43.6 flow_temp_HC2: -60 evaporator_temp: -2.4 condenser_temp: 29.8 Mixer_open: 0 Mixer_closed: 1 HeatPipeValve: 0 DiverterValve: 0 DHW_Pump: 0 HeatingCircuit_Pump: 0 Solar_Pump: 0 Compressor: 0 BoosterStage3: 0 BoosterStage2: 0 BoosterStage1: 0 HighPressureSensor: 1 LowPressureSensor: 0 EvaporatorIceMonitor: 0 SignalAnode: 0 EVU_release: 1 OvenFireplace: 0 STB: 0 OutputVentilatorPower: 44 InputVentilatorPower: 44 MainVentilatorPower: 60 OutputVentilatorSpeed: 17 InputVentilatorSpeed: 45 MainVentilatorSpeed: 17 Outside_tempFiltered: 6.9 Rel_humidity: 0 DEW_point: 373 P_Nd: 3.73 P_Hd: 12.43 Actual_power_Qc: -29770 Actual_power_Pel: 16279 collector_temp: 7.1

I have a SE LWZ303Sol with Firmware 4.19. What machine do you have?
Maybe the pattern differs between brands/Versions/firmwares like described in the heapumpmonitor protocolVersions ini files.
http://bazaar.launchpad.net/~robert-penz-name/heatpumpmonitor/trunk/files/head:/protocolVersions/


xyz_fhem
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 25 Februar 2014, 06:36:58
Hi xyz_fhem,

I have a 404 with 5.39.

Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 Februar 2014, 06:38:25
Some values are mostly 0. Thats correct :)
But they should change once the state changes, for example the solar pump or the compressor switches on.
So did you check the compressor state while the compressor is surely running?

Best
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 25 Februar 2014, 07:47:17
Hi Markus,

deshalb habe ich es ja geschrieben. Ich habe die Werte zwischen fhem und den Werten im Display verglichen und gesehen, das laut Log der Compressor state nie an war, obwohl die Anzahl compressor Stunden hoch gegangen ist!
Auch die Werte für Drücke sind entweder 0 oder 1, zeigen aber keinen Druck an, wie in deinem Plot.


Grüße
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 Februar 2014, 08:51:06
Hm... in der Tat, da stimmt dann wohl etwas nicht :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 Februar 2014, 21:02:29
dear all
version 0069 has been uploaded, tomorrow you can use "update"

changelog
- added command_ref in german, thanks Markus
- added debug command "get Mythz debug_read_raw_register_slow"; it reads raw registers and writes them in data.txt, which each time will be overwritten; path of data.txt is depending how you start of fhem: for me it is /data.txt.


If you are interested in improving the module, please write lots of nice emails to Tecalor/StiebelEltron asking for an open documentation of their funny comunication protocol  :o

If you are able to make some reverse engineering of the heatpump, please focus on register FB.
FB-99FBFDA8007700CD00CD00C5010FFDA8FDA800AB00D0200011000000000000000000000000008400000000034F03430000000000000000
And now the code I use to parse FB, it is quite self-explaining.
To help to count consider that  substr($message, 8,4) is 0077, the value  starts at char 8 and is 4 char long;;;    substr($message, 12,4) is 00CD, the value  starts at char 12 and is 4 char long.......


$message =
"outside_temp: "               . hex2int(substr($message, 8,4))/10 . " " .
"flow_temp: "                  . hex2int(substr($message,12,4))/10 . " " .  #Vorlauf Temperatur
"return_temp: "                . hex2int(substr($message,16,4))/10 . " " .  #Rücklauf Temperatur
"hot_gas_temp: "               . hex2int(substr($message,20,4))/10 . " " .  #Heißgas Temperatur       
"dhw_temp: "                   . hex2int(substr($message,24,4))/10 . " " .  #Speicher Temperatur current cilinder water temperature
"flow_temp_HC2: "              . hex2int(substr($message,28,4))/10 . " " .  #Vorlauf TemperaturHK2
"evaporator_temp: "            . hex2int(substr($message,36,4))/10 . " " .  #Speicher Temperatur   
"condenser_temp: "             . hex2int(substr($message,40,4))/10 . " " .
"Mixer_open: "                 . ((hex(substr($message,44,1)) &  0b0001) / 0b0001) . " " .    #status bit
"Mixer_closed: "              . ((hex(substr($message,44,1)) &  0b0010) / 0b0010) . " " .    #status bit
"HeatPipeValve: "             . ((hex(substr($message,44,1)) &  0b0100) / 0b0100) . " " .    #status bit
"DiverterValve: "              . ((hex(substr($message,44,1)) &  0b1000) / 0b1000) . " " .    #status bit
"DHW_Pump: "                  . ((hex(substr($message,45,1)) &  0b0001) / 0b0001) . " " .    #status bit
"HeatingCircuit_Pump: "       . ((hex(substr($message,45,1)) &  0b0010) / 0b0010) . " " .    #status bit
"Solar_Pump: "                  . ((hex(substr($message,45,1)) &  0b1000) / 0b1000) . " " .    #status bit
"Compressor: "                  . ((hex(substr($message,46,1)) &  0b1000) / 0b1000) . " " .    #status bit
"BoosterStage3: "              . ((hex(substr($message,47,1)) &  0b0001) / 0b0001) . " " .    #status bit
"BoosterStage2: "              . ((hex(substr($message,47,1)) &  0b0010) / 0b0010) . " " .    #status bit
"BoosterStage1: "              . ((hex(substr($message,47,1)) &  0b0100) / 0b0100). " " .    #status bit
"HighPressureSensor: "         . ((hex(substr($message,48,1)) &  0b0001) / 0b0001). " " .    #status bit  #P1     inverterd?
"LowPressureSensor: "          . ((hex(substr($message,48,1)) &  0b0010) / 0b0010). " " .    #status bit  #P3  inverterd?
"EvaporatorIceMonitor: "       . ((hex(substr($message,48,1)) &  0b0100) / 0b0100). " " .    #status bit  #N3
"SignalAnode: "                  . ((hex(substr($message,48,1)) &  0b1000) / 0b1000). " " .    #status bit  #S1
"EVU_release: "                  . ((hex(substr($message,49,1)) &  0b0001) / 0b0001). " " .     #status bit
"OvenFireplace: "                . ((hex(substr($message,49,1)) &  0b0010) / 0b0010). " " .      #status bit
"STB: "                          . ((hex(substr($message,49,1)) &  0b0100) / 0b0100). " " .    #status bit     
"OutputVentilatorPower: "      . hex(substr($message,50,4))/10      . " " .
"InputVentilatorPower: "       . hex(substr($message,54,4))/10      . " " .
"MainVentilatorPower: "        . hex(substr($message,58,4))/10      . " " .
"OutputVentilatorSpeed: "      . hex(substr($message,62,4))/1       . " " .  # m3/h
"InputVentilatorSpeed: "       . hex(substr($message,66,4))/1       . " " .  # m3/h
"MainVentilatorSpeed: "        . hex(substr($message,70,4))/1       . " " .  # m3/h
"Outside_tempFiltered: "       . hex2int(substr($message,74,4))/10     . " " .
"Rel_humidity: "               . hex2int(substr($message,78,4))/10    . " " .
"DEW_point: "                  . hex2int(substr($message,86,4))/1    . " " .
"P_Nd: "                        . hex2int(substr($message,86,4))/100    . " " .    #bar
"P_Hd: "                        . hex2int(substr($message,90,4))/100    . " " .  #bar
"Actual_power_Qc: "            . hex2int(substr($message,94,8))/1      . " " .    #kw
"Actual_power_Pel: "           . hex2int(substr($message,102,4))/1     . " " .    #kw
"collector_temp: "             . hex2int(substr($message, 4,4))/10 ;
}


@Markus & Michaelk68: from char44 to 49, we have only status-bits, therefore "HighPressureSensor" or "compressor" can only be 1 or 0
I did not test the status bits, because I have no real interest in them. They are still on my opl.

I am gratefull for any hint or improvement
best regards
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 26 Februar 2014, 01:13:34
Ich habe noch eine ältere Version am laufen.
Wir funktioniert das "Update"?
Bitte um eine kurze Anleitung.


@micomat
Bitte schicke mir noch die Plotdateien ( 03.02.2014)
thz1.gplot bis thz4.gplot
Danke
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 26 Februar 2014, 06:20:26
Hi Gassi,

das Update funktioniert ueber den fhem-Befehl "update" :)
Dann werden alle neuen Module runtergeladen. Durch den Befehl "shutdown restart" wird fhem neu gestartet und die neu geladenen Module verwendet.

Ich hab hier schon mal ein Plot-File gepostet. Das kannst Du problemlos verwenden und auch fuer weitere Plots kopieren.
Da die allFB Ausgabe vermutlich nicht ueberall genau die gleiche Ausgabe bringt musst Du wohl so oder so noch die Felder anpassen.

Gruß,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Februar 2014, 23:11:54
version 0.070 uploaded.
found and corrected a trivial bug in the status-bits....
please try tomorrow with fhem update.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Februar 2014, 09:04:15
thanks immi :)

do you know how i can extract single data fromthe allFB to use them in readingsgroup? as all relevant data is in this string i have now idea how to get some of them it into the dashboard.

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 27 Februar 2014, 13:33:02
Hi immi,

after the update to 0,70 compressor state is now correct.

thanks for your work

Br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Februar 2014, 13:34:56
Hi Markus
Have you tried userReadings?
Something like:
attr MyTHZ userReadings singleData_returnTemp {(split ' ', ReadingsVal("MyTHZ ","allFB",0))[8]};

p.s. Markus, we have really lots of infos hidden in this post and private emails; would you be so nice to start a wiki?
I would like to concentrate on programming. It would be great if you could lead the support/documentation of the THZ module.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Februar 2014, 17:17:33
thanks for the user-readings tip =) will try this.

i already started the wiki article. im have holidays next week so i think i will finish it also next week :)
today i received tow HMS100TF, i will try to set the fan stages depending on the humidity :)

best markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Februar 2014, 17:27:36
Hi Markus
when you succeed setting the fan-stage depending on humidity, please post it,
I want to do the same but with my  CO20-sensor, which measures the air quality (co2 equivalent).
I wanted also to switch off the fan when is very cold (during the night) and switch on when the compressor is running or the CO20-module shows bad air values.


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Februar 2014, 20:12:10
sure but this can take some time ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Februar 2014, 09:32:20
okay, the userreading is working but it's reporting only "1" :)
not sure what i did wrong.

attr Mythz userReadings AussenTemp {split ' ', ReadingsVal("Mythz ","allFB",0),[5];;}

i should do some coding training ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Februar 2014, 20:26:15
Hi Markus
coding helps me to relax. i learned basics of perl while programming THZ.

try like this

attr Mythz userReadings AussenTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[1]}, VorlaufTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[3]}


immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Februar 2014, 21:30:46
That's working :) Thanks

I never learned coding. I just did some scripting work like PHP, some SQL and HTML in the past. Sure i did also some perl and python work but mostly just changed existing code to fit my needs. Never started some from scratch. So you have my full respect!

When i need to relax i cook or ride my motorbike :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 März 2014, 10:44:47
Just loaded 0.071 :)
Whatever changed, it's working.

By the way, the German WIKI Article is online / Der deutsche Wiki-Artikel ist online.
http://www.fhemwiki.de/wiki/Tecalor_THZ_W%C3%A4rmepumpe
Englisch version will follow in a few days

Best,
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 17:46:52
Zitat von: micomat am 02 März 2014, 10:44:47
...
By the way, the German WIKI Article is online / Der deutsche Wiki-Artikel ist online.
http://www.fhemwiki.de/wiki/Tecalor_THZ_W%C3%A4rmepumpe (http://www.fhemwiki.de/wiki/Tecalor_THZ_W%C3%A4rmepumpe)
...
Habe dann auch gleich einen Fehler entdeckt. Die serielle Geschwindigkeit kann je nach Modell bis zu 115200 Baud betragen. Meine Anlage ist der Beweis dafür (rev. 4.19). Dennoch eine schöne Anleitung, die ich dann gleich mal ausprobieren will.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 18:09:01
Und gleich die nächsten Fragen dazu:
attr Mythz interval_allFB 300 # Internes Polling Intervall 5min
attr Mythz interval_history 28800 # Internes Polling Intervall 8h

Bedeutet das, dass die gesamte History auf 8 Stunden begrenzt ist, oder nur die Anzeige im Graph? Gesamt wäre mir deutlich zu wenig. Angenommen, die Anlage geht kaputt und ich komme erst 10 Stunden später heim, dann sehe ich gar nichts mehr.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 20:54:28
Ich vermisse die Innentemperatur in den ausgelesenen Daten.  :-[

Lösung:
in 00_THZ.pm nach Zeile 712 folgende Zeile einfügen

"inside_temp: " . hex2int(substr($message,32,4))/10 . " " .  #Innen Temperatur


Die Grafiken müssen dann natürlich angepasst werden, weil bei allen folgenden Werten der Index jetzt um 2 höher ist.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 März 2014, 21:20:04
Hi Willy,

mal eine Zusammenfassung deiner Postings :)

Habe den WIKI Artikel upgedatet.

ZitatBedeutet das, dass die gesamte History auf 8 Stunden begrenzt ist, oder nur die Anzeige im Graph? Gesamt wäre mir deutlich zu wenig. Angenommen, die Anlage geht kaputt und ich komme erst 10 Stunden später heim, dann sehe ich gar nichts mehr.
Das ist das Intervall mit dem FHEM die Daten aus der Anlage ausliest.
Die allFB Werte alle 5 Minuten, die History-Werte und die Systemeinstellungen alle 8Stunden. Das kann natuerlich nach Belieben variiert werden. Die Speicherdauer ist quasi nur durch die Festplatte des Systems begrenzt auf dem Du die Daten aufzeichnest :)

ZitatIch vermisse die Innentemperatur in den ausgelesenen Daten.  :-[
Ja, doch die Anlage hat standardmaessig keinen Innentemperaturfühler im Wohnraum verbaut.
Daher muss man hier auf andere Fühler wie beispielsweise den HMS100TF ausweichen. Ging mir genauso.

Gruß
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 22:08:46
Innentemperatur:
Lösung:

in 00_THZ.pm nach Zeile 712 folgende Zeile einfügen

"inside_temp: "            . hex2int(substr($message,32,4))/10 . " " .  #Innen Temperatur


Die Grafiken müssen dann natürlich angepasst werden, weil bei allen folgenden Werten der Index jetzt um 2 höher ist.


Wenn man keinen Fühler hat wird dann halt ein Defaultwert (das müsste vermutlich die Solltemperatur sein) ausgegeben.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 22:11:26
Ich suche grade nach einer Möglichkeit
- die Grafiken in Y-Richtung größer zu machen
- die Farben (speziell 5 - 8, die alle schwarz sind) zu ändern.


Jemand eine Idee dazu?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 März 2014, 22:20:37
Inside temp ist bei mir immer -60. 
das gleiche Tritt auf wenn man keinen Solar Kollektor hat.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 März 2014, 22:48:53
Zitat von: micomat am 02 März 2014, 22:20:37
Inside temp ist bei mir immer -60. 
das gleiche Tritt auf wenn man keinen Solar Kollektor hat.
eben. Deshalb  sehe ich nicht, weshalb man die Innentemperatur außen vor lassen sollte. Wer sie nicht mag kann sie ja ignorieren. Wenn sie ans Ende der Datenliste angehängt wird bleiben alle existierenden Grafikdefinitionen erhalten - kompatible Erweiterung.
Habe immi mal gefragt,ob er das macht, plus ein paar andere Kleinigkeiten.


PS:
Luftfeuchtigkeit dürfte bei Dir dann auch "im Wald stehen", oder?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 März 2014, 23:18:28
Hi Willybauss
I test the inside_temp some days, as always before roll-out.

if you want to compensate a value from thz, try something like this: in the followings I added an offset of 0.5 to Assentemp and divided VorlaufTemp by 0.9

attr Mythz userReadings AussenTemp {((split ' ',ReadingsVal("Mythz","allFB",0))[1]) + 0.5 }, VorlaufTemp {((split ' ',ReadingsVal("Mythz","allFB",0))[3])/0.9}

Hi Markus
excellent wiki!!

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 08:10:35
ok, I'll try it. Currently I don't have a clue what [1] and [3] means in your example.
And: I assume this compensation just works in the graphs; values wrote to log file might still be wrong (=not compensated), right? If that's the case I'd really prefer an offset calculation during read-out. Maybe I need to do it on my own and re-implement with every updateed 00_THZ version manually.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 08:33:40
Hi Willy,

yes humidity is also out of range. Here i use the HMS100TF, too.
[1] and [3] is the position of the data inside the string separated by spaces.
So AussenTemp is the second data position in the allFB string, VorlaufTemp the fourth if we start with the first at 0.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 08:55:11
thanks, I got it by try and error meanwhile. Now the log looks like
2014-03-03_08:48:35 Mythz allFB: outside_temp: 3.3 flow_temp: 46.6 return_temp: 46.9 hot_gas_temp: 94.7 dhw_temp: 45.1 flow_temp_HC2: -60 evaporator_temp: -4.4 condenser_temp: 47.8 Mixer_open: 0 Mixer_closed: 0 HeatPipeValve: 0 DiverterValve: 0 DHW_Pump: 1 HeatingCircuit_Pump: 0 Solar_Pump: 0 Compressor: 1 BoosterStage3: 0 BoosterStage2: 0 BoosterStage1: 0 HighPressureSensor: 0 LowPressureSensor: 1 EvaporatorIceMonitor: 0 SignalAnode: 0 EVU_release: 1 OvenFireplace: 0 STB: 0 OutputVentilatorPower: 34 InputVentilatorPower: 27 MainVentilatorPower: 70 OutputVentilatorSpeed: 16 InputVentilatorSpeed: 30 MainVentilatorSpeed: 21 Outside_tempFiltered: 2.2 Rel_humidity: 22.7 DEW_point: 409 P_Nd: 4.09 P_Hd: 20.93 Actual_power_Qc: -31709 Actual_power_Pel: 16329 collector_temp: -60 inside_temp: 22.3
2014-03-03_08:48:35 Mythz inside_temp: 21.7
2014-03-03_08:48:35 Mythz Rel_humidity: 34.2

By using  'Mythz inside_temp:' instead of  ' Mythz allFB:   inside_temp:' I managed to get the right values into the graph  :) 
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 11:05:46
good work :) after you created a userReading named inside_temp you can use it for sure.

Oh i see your humidity is as low as ours... disadvantage of the ventilating system.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 13:17:14
The Wiki Article is now available in englisch
http://www.fhemwiki.de/wiki/Tecalor_THZ_Heatpump

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 15:59:29
Zitat von: micomat am 03 März 2014, 11:05:46
Oh i see your humidity is as low as ours... disadvantage of the ventilating system.
yes, that's the reason why I'd like to have the value corrected. Without offset correction it looks much worse:
Rel_humidity: 22.7  :-[ :-\ :'(
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 16:03:36
But this value could be correct. I don't know where your humidity sensor is, but my three sensors in our house reporting me rel. humidity between 27% and 34% depending on the room.
I believe that this is a special problem of ventilation systems with a cross counterflow heat exchanger (Kreuzgegenstrom Wärmetauscher) as this system is also dehumidifying the air.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 März 2014, 16:59:03
dear both
feauture or bug.... I fight low humidity with
1) several plants. I give to my green friends more than 1l water per day, which they distribute in the ambient as humidity.
2) using the cloth-dryer only if needed.
3) i deactivate the ventilation system for from 21:00 to 01:00 and from 1:45 to 7:00. I keep on monitoring the CO2 level and I do not see a degradation of the air quality.
4) cooking a lot.

my house humidity is between 30% and 40% in winter, and my family is happy with it.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 17:24:06
happy you :)
i have half a Jungle in the House, no cloth dryer and our vent is also off at Night. but no More hum as 35% ;) thats why i want to Control vent deprnding on humidity in the House

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 17:52:37
So langsam wirds Zeit für einen Vergleich heatpumpMonitor vs. FHEM.
Noch habe ich beim  heatpumpMonitor Features, die ich in FHEM noch vermisse: Das ist alles nicht so tragisch. die wirklichen Unterschiede sind:


Die Protokollverarbeitung:
In FHEM ist das Protokoll tief im Sourcecode vergraben. Bei anderer Firmwareversion wirds richtig richtig schwer, das Ding wieder ans laufen zu bekommen. Bei jedem Update der 00_THZ.pm darf man dann seine manuellen Anpassungen wiederholen.  :-[
Der heatpumpMonitor hat die Protokolldefinition ausgelagert in Protocol.ini Dateien. Neue Firmware mit geänderter Datenstruktur => neue ini Datei erstellen, anwenden, fertig.  ;D


Die Art der Datenverarbeitung:
Der HeatpumpMonitor liest die Daten aus und verarbeitet sie sofort: FHEM liest die Daten nur aus und schreibt sie ins log-File (pure ASCII).Womit wir beim Webzugriff wären:So kann man natürlich nicht arbeiten. Ich kann nicht jede Minute 600MB auf den Webserver schreiben. Evtl. könnte man auch über ftp die Daten  inkrementell schreiben. Aber beim auslesen sind es immernoch 600MB.
Zugegeben: ich bin vom heatpumpMonitor verwöhnt; man kann sich auch mit 2 oder 3 Minuten-Rastern zufrieden geben. Aber das verringert das Problem nur, wirklich gelöst wird es nicht. Und Lösungen wie "lege doch jeden Monat ein neues log-File an" sind eine Krücke.

An dieser Stelle bin ich noch nicht zu einer Lösung gekommen. Evtl. werde ich doch wieder Bitmaps erstellen und per ftp online stellen. Es sei denn mir fällt noch was besseres vor die Füße. Es müsste doch irgendwie gehen, dass man die Plots in Bitmap-Dateien schreibt und alle 15 Minuten per ftp auf einen Webserver schiebt. Wenn man sich auf das Aller nötigste beschränkt kommt man da mit 100 - 200kB gut hin.
Das Szenario ist dabei: ich bin ein paar Tage weg, die Heizung spinnt. Bevor meine Frau zuhause kalte Füße bekommt kann ich ihr schon Bescheid sagen, wie sie den Fehler beheben kann - weil ich Letzter und für mich entscheidender Unterschied: Werte schreiben, d.h. die Wärmepumpe nicht nur kontrollieren, sondern auch steuern.
Der heatpumpMonitor hat da gar nichts anzubieten; das Projekt ist tot, von ehemals maßgeblichen Entwicklern bekommt man auf Anfragen gar keine Antwort.

FHEM scheint das zu können - ich habs noch nicht versucht. Aber ohne Risiko ist das nicht, weil ... sh. Protokoll-Story weiter oben ... Wenn der Servicetechniker eine neue Firmware aufspielt und man lässt die alte FHEM-Steuerung drauf los, kann man sich einiges kaputt machen, falls sich die Registeradressen geändert haben.
Dennoch werde ich das angehen. Ziel ist z.B. eine sinnvolle Steuerung der Passivkühlung im Sommer. Warum muss ich der Anlage erst per Displaytastatur sagen, dass ich ein Fenster aufgemacht habe, und dass sie jetzt Passivkühlung Mode 1 wählen soll? Das Fenster soll gefälligst selbst Vollzug an FHEM melden, und FHEM meldet dann der THZ was zu tun ist. Und wenn ich mitten in der Nacht wegen pöbelnder Disco-Heimkehrer das Fenster im Schlafzimmer zu mache, dann kann FHEM ohne mein Zutun von Passivkühlung Mode 1 auf Mode 2 umschalten, damit ich nicht im Schlaf ersticke.


Wenn man lange genug nachdenkt fallen einem sicher noch ein paar weitere Steuerungsanwendungen ein. Man sollte sich halt gut überlegen, ob man auch so riskante Sachen wie Heizkreispumpe und Booster anfasst. Wenn man sich da vertut ...  :o
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 18:49:52
wow da brauch ich ja fast n bier bis ich den text durch hab ;)
du darfst fhem nicht mit dem heatpumpmonitor vergleichen. die ziele beider systeme sind grundegend verschieden. das eine ist nur dazu da die wärmepumpe auszulesen das andere ist ein komplexes system zu heimautomatisierung in das die waermpepumpe erst seit wenigen wochen integriert werden kann.

mal ein paar auskuenfte zu einigen deiner punkten:
eine email im alarmfall kann auch FHEM verschicken, musst du nur implementieren. du kannst die errorcodes abfragen und natuerlich auch ob die wp verbunden ist.

die grafikerstellug ist in fhem grundlegend anders als in heatpumpmonitor (hpm).
beides hat vor- und nachteile.

wenn du selbst entwickelst und aenderungen einpflegst oder das gerne haettest, dann kann immi das sicherlich fuer dich einbauen. er ist diesbezueglich sehr kommunikativ. ansonsten richtig, musst du deine eigenen aenderungen wieder einbauen.

zum logging: es gibt bereits die moeglichkeit die daten statt in textfiles in eine sql-db zu schreiben. noch effizienter als json :)
uebrigens ich hab eine 50MBit/s leitung, also mir is die dateigroesse "wurschd" ;)
du kannst alernativ die logfiles auch in monatliche logs unterteilen. da wuerde die einzelgroesse reduzieren.

das mit dem schreiben habe ich ausgiebig getestet :) funktioniert perfekt.
am einfachsten kannst du das mit der luefterstufe testen. einfach mal die tag-stufe erhoehen oder reduzieren. da kann eigentlich (natuerlich gibts ne garantie nicht) nix schief geben da die hex-daten die dabei uebertragen werden bei einem fehler einfach verworfen werden sofern sie nicht unwahrscheinlicherweise ein anderes gueltiges register treffen.

ich hatte vorher auch hpm und habe erst nach etwas zoegern komplett auf fhem umgestellt. nicht zuletzt dank der unterstuetzung und der programmierung von immi :)
und da ich hier einfach viel mehr potential sehe als beim schon toten hpm habe ich mich auch hierfuer entschieden. mit allen vor- und auch den nachteilen. erstere ueberwiegen aber fuer mich :)
die eierlegende wollmilchsau wirds wohl nie geben, aber fhem kann einfach viel viel viel mehr als hpm und ist somit fuer mich erste wahl.
vielleicht kann dein upload-thema ja mit dblog geloest werden? dann brauchst du garnix uploaden sondern kannst (je nach fritzbox oder router) per vpn deine daten direkt im fhem sehen.
http://www.fhemwiki.de/wiki/Neues_Charting_Frontend#DbLog_installieren_und_konfigurieren

gruß
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 03 März 2014, 19:10:05
Hi Immi,
long time not spoken. I am very happy about this very interactive page and all the Progress in the Software.

I have as well playd a lot with this SW and it is great. When I tried to set the next Holiday period, I was confused to see that somehow the internal time of THZ is not in sync wiht the normal time and fhem time, In fact the date was completly old and as i could not set it correctly from remote, I adjusted my Holiday accordingly..... But in fact all my Error. now I remember that the "timedate" get only read at start of fhem, therafeter it always looks outdated. Could I suggest in one of the next updates to hide this usually wrong Info? OR that it gets updated once I open the Parameter page of my THZ? OR it could say "timedate of last FHEM start"

reagrds Heiner
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 19:18:54
Hi Heiner,

as far as i can see the timedate is read all 8h (default setting) along with the history data. But if you set only the holiday time there should be no problem with the time setting at the heatpump.
Can you check the time setting at the display? Maybe the setting of time and date is wrong there?
What do you mean with "completely old" time?

EDIT:
sorry, just tested it ;) it's not read with the history data.
But you can set an "at" command to read the timedate all x-min if you want to.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 19:30:04
attr Plot_Temp plotsize 840,420
löst auch die Frage mit dem zu kleinen Plot. Sieht jetzt viel übersichtlicher aus.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 19:37:30
Zitat von: micomat am 03 März 2014, 16:03:36
But this value could be correct. I don't know where your humidity sensor is, but my three sensors in our house reporting me rel. humidity between 27% and 34% depending on the room.
I believe that this is a special problem of ventilation systems with a cross counterflow heat exchanger (Kreuzgegenstrom Wärmetauscher) as this system is also dehumidifying the air.
I simply put three different weather stations (different models, different manufacturers) close to the external display, where the humidity sensor is built in. All three reported exactly same value, but external display of heatpump was 11.5% off. So I believe that these three are right and just one is wrong.
Question is still, if it's an additional offset or a factor. This question can be answered in summer, when humidity will rise typically.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 19:43:58
Sounds like a high Quality sensor  ;D
EDIT:
according to the Installation Manuals of the THZ, there is no Offset for humidity Sensors.
maybe its defect? still covered by guarantee?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 März 2014, 20:06:52
Hi Heiner
happy that you are back; you were the first tester of 00_THZ.
concerning timedate you can always look at the right colum, which you should compare with the middle one: middle is timedate of the tecalor, right is the timestamp of your linux computer when the reading has been taken.
I have an offset of 22seconds.

The information is read only by fhem start automatically. I do not see any need for periodic update. I find the information relevant if current goes away and I am abroad. I do not know how long the tecalor internal timer keeps the time without current.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 20:48:11
Zitat von: micomat am 03 März 2014, 18:49:52
vielleicht kann dein upload-thema ja mit dblog geloest werden? dann brauchst du garnix uploaden sondern kannst (je nach fritzbox oder router) per vpn deine daten direkt im fhem sehen.
http://www.fhemwiki.de/wiki/Neues_Charting_Frontend#DbLog_installieren_und_konfigurieren (http://www.fhemwiki.de/wiki/Neues_Charting_Frontend#DbLog_installieren_und_konfigurieren)
Auch dann habe ich den Upload als Flaschenhals. Aber mit ner sqLite DB wäre ich aus dem Thema raus, dass das ganze Textfile gelesen werden muss. Das könnte den Traffic deutlich verringern.
Mir ist allerdings noch nicht klar, wie ich die Daten da rein bekomme. Das 00_THZ Modul schreibt ja definitiv ins Textfile. Ich muss mir mal an einem verregneten Wochenende das Thema DbLog rein ziehen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 März 2014, 20:51:31
Zitat von: micomat am 03 März 2014, 19:43:58
according to the Installation Manuals of the THZ, there is no Offset for humidity Sensors.
maybe its defect? still covered by guarantee?
I'm pretty sure there's no warranty at all for a THZ display which I got from Ebay for 21,50€ ... The sensor works basically. As long as I can manage the issue by offset correction it's ok for me.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 März 2014, 21:01:45
Hi Willi
Zitat von: willybauss am 03 März 2014, 20:48:11
Das 00_THZ Modul schreibt ja definitiv ins Textfile. Ich muss mir mal an einem verregneten Wochenende das Thema DbLog rein ziehen.
not correct; 00_THZ does not write in text file. I write back to fhem global variables, called readings. The module FileLog is writing  the readings to a file, as DBlog could write to  a database.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 März 2014, 21:31:56
Zitat von: willybauss am 03 März 2014, 20:51:31
I'm pretty sure there's no warranty at all for a THZ display which I got from Ebay for 21,50€ ... The sensor works basically. As long as I can manage the issue by offset correction it's ok for me.
lol =) thats the reason...
Titel: Neues Charting Frontend für THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 März 2014, 16:09:59
Ich folge grade dem Rat von micomat und versuche auf das neue Charting Frontend zu wechseln. Dabei kommt es noch zu (für mich) ungeklärtem Fehlverhalten.
Die fhem.cfg sieht grade so aus:
attr Mythz userReadings inside_temp {((split ' ',ReadingsVal("Mythz","allFB",0))[81]) - 0.6 }, Rel_humidity {((split ' ',ReadingsVal("Mythz","allFB",0))[67]) + 11.5}
define FileLog_Mythz FileLog /mnt/fhem/log/Mythz-%Y-%m.log Mythz
define myDbLog       DbLog   /mnt/fhem/db.conf             Mythz


Die letzte Zeile ist fürs schreiben in die Datenbank hinzugekommen, die erste existiert nur wegen der früher beschriebenen Problematik mit den Offsets der Sensoren.
Wenn ich nun im neuen Frontend ein Chart bauen will, dann sehe ich zwar inside_temp und Rel_humidity in der Liste der möglichen Daten für die Y-Achse (das kommt dann aus der 1. Zeile), aber alle Werte von allFB sind in einem einzigen Datenbankeintrag als String enthalten. Den kann das Frontend nicht auflösen, um die Werte darzustellen. Ich habe dann mal die Syntax von FileLog und DbLog lt. CommandReference verglichen; dabei fällt mir nichts ungewöhnliches auf. Es heißt bei DbLog sogar ausdrücklich "<regexp> ist identisch wie FileLog." Demnach sollte "Mythz" als <regexp> ja funktionieren - tut es aber nicht. :-\ 


Vermutlich gibt es auch an dieser Stelle wieder eine ganz einfache Lösung, die ich aber nicht kenne. Mir fällt spontan nur ein, alle Werte von allFB nochmal separat zu definieren änlich wie in der 1. Zeile (attr Mythz userReadings ...). Das klingt aber ziemlich aufwändig - auch für den Server.


Gibt es was einfacheres?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 März 2014, 17:39:47
Hi Willi
keep it simple, start without DBLOG and FILElog.
Are you sure you have 81 separated words in allFB?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 05 März 2014, 18:04:20
Hi immi,

thats possible, the collector temp is on my position 83 ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 März 2014, 18:42:38
Markus
You are right. I just checked. 81 is plausible.
----------
It is some weeks that I am thinking how to improve allFB.
At the time, I only see two solutions and I am not happy with both:
1) separating all 40 parameters hidden behind allFB in 40 readings. It would be easy to implement, but the logfille-size will explode if you update too frequently allFB, because each parameter would also get a timestamp and some overhead.
2) giving full flexibility to the user, shifting the whole parsing to the config file; drawback is that the config file will become huge and really complicated. Newbies will get completely confused, and will give up.

I would like to have your feedback
thanks

@ Willi I will try bdlog on the weekend

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 März 2014, 18:55:58
Zitat von: immi am 05 März 2014, 17:39:47
keep it simple, start without DBLOG and FILElog.
don't understand what you mean. How should I show graphs without logging values to anywhere, neither DB nor FILE? Or did you mean I should stay with FileLog and not use DbLog? That's not really an option, at least long term. I'd really like to have the tooling all right before going into broadly using it.

Zitat von: immi am 05 März 2014, 17:39:47
Are you sure you have 81 separated words in allFB?

Please have a look on attached screen dump. I didn't check if it's really 81 items wide, but from what I see I don't doubt about it. Same issue with 'history' and 'last10errors'.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 05 März 2014, 18:59:51
Hi immi,

could we modify the first option? =)
Keep the readings in allFB (getting them separated with userReadings is documented in the wiki and quite easy) but making the reading names shorter? maybe in three/fur letter-codes like clt for collector_temp or mvp for mainventilatorpower. this would decrease the log-size without changing the whole parsing. to prevent all old data becomes obsolete automatically while doing this you could set up a paramter like "attr Mythe shortnames" to use them? just a suggestion :)

do you separate the logfiles into months or do you store all in one file?

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 März 2014, 20:12:03
looks like new frontend's charting function, reading from FileLog, doesn't manage the way how allFB data is stored in FileLog, see attached screen dump.
blue chart: Rel_humidity read from DbLog ==> o.k.
green chart: inside_temp read from FileLog ==> every second value is correct, showing the value stored in FileLog (e.g. 22.5), but the ones inbetween show zero, obviously read from the allFB row wrongly.


related part of FileLog looks like (line breaks added for better reading):
2014-03-05_19:35:33 Mythz allFB: outside_temp: 4.6 flow_temp: 23.5 return_temp: 24.5 hot_gas_temp: 40.5 dhw_temp: 47.5
    flow_temp_HC2: -60 evaporator_temp: 13.8 condenser_temp: 24.8 Mixer_open: 0 Mixer_closed: 0 HeatPipeValve: 0 DiverterValve: 0
    DHW_Pump: 0 HeatingCircuit_Pump: 0 Solar_Pump: 0 Compressor: 0 BoosterStage3: 0 BoosterStage2: 0 BoosterStage1: 0
    HighPressureSensor: 0 LowPressureSensor: 1 EvaporatorIceMonitor: 0 SignalAnode: 0 EVU_release: 1 OvenFireplace: 0 STB: 0
    OutputVentilatorPower: 34 InputVentilatorPower: 27 MainVentilatorPower: 0 OutputVentilatorSpeed: 23 InputVentilatorSpeed: 28
    MainVentilatorSpeed: 0 Outside_tempFiltered: 6.1 Rel_humidity: 24.8 DEW_point: 719 P_Nd: 7.19 P_Hd: 11.36 Actual_power_Qc: 0
    Actual_power_Pel: 0 collector_temp: -60 inside_temp: 23.1
2014-03-05_19:35:33 Mythz inside_temp: 22.5
2014-03-05_19:35:33 Mythz Rel_humidity: 36.3




Don't know what would happen if DbLog would manage allFB in a better way. Maybe the values would oscillate between corrected and uncorrected ones - what's not really better than now.  Since the issue is with DbLog it's useless to give the old graph method with DbLog a try.


Bottom lime there's currently no other way than using FileLog and old graph method.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 März 2014, 20:27:13
Hi willi
please forget my previus post 17:39:47.
Please post your plotting configuration for both; it is getting interesting.

Hi Markus,
I think that your third option is very diskspace friendly and new user friendly, but I am afraid the readability would be terrible.
I want something diskspace friendly, user friendly and readable. I would also like to add units....

There is also a possibility of improving option 1 with a blacklist as attribute. The user could decide which parameters should be ignored. (e.g. I do not have a solarcollector --> Attr Mythz ignore_parameter solarcollector).

p.s. I am now dividing the the logfiles into months, polling every 5 minutes.
The logfilesize is acceptable.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 05 März 2014, 21:13:07
Zitat von: immi am 05 März 2014, 20:27:13
I think that your third option is very diskspace friendly and new user friendly, but I am afraid the readability would be terrible.
right, but when i think about other systems, a lot of themhave abbreviations for the readings.
e.g. the HMS has T, H and Bat. for Temperature, Humidity and Battery.
we need to find the happy medium way ;)

Zitat
There is also a possibility of improving option 1 with a blacklist as attribute. The user could decide which parameters should be ignored. (e.g. I do not have a solarcollector --> Attr Mythz ignore_parameter solarcollector).
thats also a great idea =)

best,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 März 2014, 22:07:31
dear all
version 0.072 uploaded
changelog:
1) all programHC1*, programHC2*, programFan* and programDHW* have been implemented with get and set
2) inside_temp  has been added to the end of allFB
3) connect/disconnet bug related to ser2net has been extremely improved: max one retry per second

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 März 2014, 22:40:59
Zitat von: immi am 05 März 2014, 20:27:13
Please post your plotting configuration for both; it is getting interesting.
Hi immi,
don't know if there's a ascii file output of new graphing system's config anywhere. So I send you the setup as screen dump. Hope that helps.


Willy


btw: I would prefer having a blacklist too, since I need just a small part of all possible values currently - might increase over time of course.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 März 2014, 10:00:23
Zitat von: immi am 05 März 2014, 22:07:31
dear all
version 0.072 uploaded
added to wiki pages
sadly my internet provider has a problem today so i cannot connecto to the internet to install it =(

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 06 März 2014, 10:49:36
as I described earlier I added corrections to fhem.cfg  due to the sensor offsets. So it looks like
define Mythz THZ /dev/ttyUSB0@115200
attr Mythz interval_allFB 120
attr Mythz interval_history 28800
attr Mythz userReadings inside_temp {((split ' ',ReadingsVal("Mythz","allFB",0))[81]) - 0.6 }, Rel_humidity {((split ' ',ReadingsVal("Mythz","allFB",0))[67]) + 11.5}
define FileLog_Mythz FileLog /mnt/fhem/log/Mythz-%Y-%m.log Mythz


meanwhile I observed that the userReadings are also done after every  interval_history reading row, resulting in e.g.
2014-03-05_21:42:47 Mythz programHC1_Sa_0: n.a.--n.a.
2014-03-05_21:42:47 Mythz inside_temp: 22.5
2014-03-05_21:42:47 Mythz Rel_humidity: 36.3
2014-03-05_21:42:47 Mythz programHC1_Mo_0: n.a.--n.a.
2014-03-05_21:42:47 Mythz inside_temp: 22.5
2014-03-05_21:42:47 Mythz Rel_humidity: 36.3
2014-03-05_21:42:48 Mythz programHC1_We_0: n.a.--n.a.
2014-03-05_21:42:48 Mythz inside_temp: 22.5
2014-03-05_21:42:48 Mythz Rel_humidity: 36.3
2014-03-05_21:42:48 Mythz programHC1_Tu_2: n.a.--n.a.
2014-03-05_21:42:48 Mythz inside_temp: 22.5
2014-03-05_21:42:48 Mythz Rel_humidity: 36.3


So there's a lot of unnecessary stuff written to the log. Does anyone know how I can limit execution of userReadings to allFB rows only?

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 06 März 2014, 12:31:21
my thoughts about new log file format

Hi immi,

I have a few ideas to changed file format in regards to
compatibility:
Improvement in efficiency might be limited, as long as log file format has to be compatible. Therefore a new approach: leave the output format as it is and don't touch this code area in future, to limit your effort. Implement code for new file format in addition to existing code, and limit your future work to this code. User can select data format by using either


attr Mythz interval_allFB 120
attr Mythz interval_history 28800


or


attr Mythz interval_allFB_new 120
attr Mythz interval_history_new 28800




Saving disk space by
completely different approach - don't know if possible without inventing fhem newly ...:
Already existing question are still valid, e.g.
Advantage of new graphing system is ease of use, e.g. change time frame for a graph on the fly, select variables t.b. used from pull down menu instead of counting entry numbers ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 März 2014, 12:46:23
0.072 installed :) working like a charm!
thanks!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 März 2014, 14:00:37
Hallo Willy
thanks for brainstorming.
I am slowing getting the big picture.
The first priority of 00_THZ is to be mainstream for fhem and control the interface to the heatpump.
I did not and I am not going to save data with THZ (exept for debugging) in any format.
I will keep on using FHEM-system-calls given by FHEM to DBLOG or FILELOG or other modules.
The module DBLOG or FILELOG will provide inputs for plotting. I am not the manteiner of plotting interfaces, of filelog nor dblog.

for history interval polling,  I did not implement a full refresh  (with stuff like programHC1_Tu_2 ....). It is  probably a bug.
I will check tonight.

Hi Markus
for the documentation following information could be interesting
A full refresh (of all parameters) is done only at systemstart, very very slowly (not to decrease performance of FHEM), and takes ca 3 or 4 minutes.
After(*note)  that the intervall polling of allFB and History register should start.

(*note) If the FB-intervall or History-Intervall attributes are lower than 3 minutes, there clould be a concurrency. But I do not expect any problems.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 März 2014, 14:13:35
will add this to the wiki
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 März 2014, 20:28:36
Hy Willy
no bug in 00_THZ
commandref is always your friend:
Zitat
userReadings
A comma-separated list of definitions of user-defined readings. Each definition has the form:
    <reading>[:<trigger>] [<modifier>] { <perl code> }
After a single or bulk readings update, the user-defined readings are set by evaluating the perl code { <perl code> } for all definitions and setting the value of the respective user-defined reading <reading> to the result. If <trigger> is given, then all processing for this specific user reading is only done if one of the just updated "reading: value" combinations matches <trigger>, which is treated as a regexp.
if you do not use the :<trigger>, each time MyTHZ is updated also the userreading will be updated
here the corrected version

attr Mythz userReadings inside_temp:allFB {((split ' ',ReadingsVal("Mythz","allFB",0))[81]) - 0.6 }, Rel_humidity:allFB {((split ' ',ReadingsVal("Mythz","allFB",0))[67]) + 11.5}

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 06 März 2014, 23:25:15
Zitat von: immi am 06 März 2014, 20:28:36
Hy Willy
no bug in 00_THZ...


Hi immi,
thanks so far. I apologize for not having used commandref. I simply copy-pasted the code from your suggestion of 02 März 2014, 23:18:28.
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 März 2014, 15:15:14
Zitat von: immi am 06 März 2014, 14:00:37

for the documentation following information could be interesting
A full refresh (of all parameters) is done only at systemstart, very very slowly (not to decrease performance of FHEM), and takes ca 3 or 4 minutes.
After(*note)  that the intervall polling of allFB and History register should start.

(*note) If the FB-intervall or History-Intervall attributes are lower than 3 minutes, there clould be a concurrency. But I do not expect any problems.

added to wiki pages
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 März 2014, 15:50:27
Zitat von: immi am 06 März 2014, 14:00:37
(*note) If the FB-intervall or History-Intervall attributes are lower than 3 minutes, there clould be a concurrency. But I do not expect any problems.
I can confirm that the concurrency works without any trouble. My allFB intervall are 2 minutes, so first allFB call is done when the full refresh is not yet finished. allFB row sorts into log file smoothly.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 März 2014, 16:32:12
So far we reached a nice beta... what do you want next?
Serialize allFB (one parameter per line) with blacklist (really a lot of work, because of the blacklist).......
or search for new parameter of your choice to be programmed in the heatpump.

p.s. I would appreciate if you tel me where you buy (possibly in germany and in internet) the filters for the ventilation.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 März 2014, 18:01:42
I bought at http://luftladen.de/ (http://luftladen.de/)


That's what I ordered:
Produkt ID:12
Produkt Name:hochwertige Universal - Filtermatte G4 1m * 1m
Bestellnummer: G4-20mm-1qm
Hauptkategorie:Filtermatten -vlies
Unterkategorie:Filtermatten G2-G4,F5-F8
Anzahl: 1
MwSt. Anteil: 2.39 EUR (19.00%)
Position gesamt: 14.98 EUR
It's a big part, 1 x 1 Meter. You can cut it easily using a pair of scissors.They also can sell you filters for the exhaust openings inside your rooms, if you have any. I additionally installed a filter before the ventilation air comes into the house, see attached picture. But that's possible just in case your ventilation input is separated from the heatpump's input (has to be installed separately).
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 März 2014, 18:14:52
Might be that I need another value, but I have to ask for more details first in a different forum. And: that's a very special case, so don't hesitate to reject if it's out of your scope. Topic is:
Today I tried to get rid of the separate inside_temp sensor and use the sensor in the external display instead, which is located in living room. Goal was to no more need the correction by userReading. But as soon as I cut the line from sensor to heatpump the reported value in allFB was always -60°. The heating curve calculation in fact uses the value of external display now, but allFB doesn't do so, even after reset of heatpump. So might be that there's a different command to call the external display's inside_temp.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 März 2014, 23:53:58
Zitat von: immi am 07 März 2014, 16:32:12
So far we reached a nice beta... what do you want next?
Serialize allFB (one parameter per line) with blacklist (really a lot of work, because of the blacklist).......
or search for new parameter of your choice to be programmed in the heatpump.

p.s. I would appreciate if you tel me where you buy (possibly in germany and in internet) the filters for the ventilation.

immi
hey immi,
yes you did a lot of hard work :)
blacklist without serialization would be a good compromise maybe. i'm happy with the allFB for now :)
i don't know what i would need else to set at the THZ. maybe things like the ventilations volume in cubice meter per hour? maybe a timesync between fhem and the THZ would be an idea?

for the filter i just go to the hardware store around the corner and get some filter mats for the kichtchen hood. just cut it and it's fine.
for the exhaust air inlets i bough this one in the past: http://www.amazon.de/Kegelfilter-Tellerventil-Aussenluft-Ansaugturm-cooling/dp/B00FIKD63U/ref=sr_1_1?ie=UTF8&qid=1394232811&sr=8-1&keywords=kegelfilter+dn125
10pcs for 16,99EUR

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 März 2014, 07:45:28
in case of DbLog there exists an attribute
DbLogExclude
  set <device> DbLogExclude regex:MinInterval

Would it be possible to request a similar attribute from the 'inventer' of FileLog? That would ease up your work a lot.
edit: might not work unfortunately, since it would either exclude whole allFB row or nothing  :( -


Drawback of allFB seems to be incompatibility with DbLog, as I mentioned above. I could live with it (would use FileLog plus blacklist), but for a release it might be sub optimal.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 März 2014, 08:27:15
Zitat von: immi am 07 März 2014, 16:32:12
So far we reached a nice beta... what do you want next?


what about
attr Mythz interval_last10errors 14400

Currently last10errors are obviously just read at startup. To get alarmed in case of defect last10errors might be helpful (?).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 März 2014, 21:38:58
Dear Willy and Markus
thanks for the hints on the filter supply

@Willy: What you are asking (last10errors intervals) would be very easy to implement.
I have never had a failure in my tecalor, so I never had the possibility to debug really last10errors.
I do not have a good feeling for programming a regular update for something I did not test properly.
you can use the AT syntax for updating, or tell me how to simulate a failure.
p.s. when filter has to be changed (because dirty), the info will be written somewhere else.


@Markus: as wished new version 0.074 uploaded; we have to get ready for summer :)
Zitat"passiveCooling"        => 0, 1 or 2
"fanstage1-Airflow-inlet"    =>     m3/h  #zuluft
"fanstage2-Airflow-inlet"    =>   m3/h  #zuluft
"fanstage3-Airflow-inlet"    =>  m3/h #zuluft
"fanstage1-Airflow-outlet"    =>   m3/h #abluft extrated
"fanstage2-Airflow-outlet"    =>   m3/h #abluft extrated
"fanstage3-Airflow-outlet"    =>   m3/h  #abluft extrated
I expect fanstage1-Airflow to be in m3/h but I am not 100% sure


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 März 2014, 21:51:08
ok, let me think about simulating a failure. Sorry, if I'm asking a stupid question: why do you need to program a polling interval - just for code testing? I expected the interval t.b. defined in fhem.cfg by
attr Mythz interval_last10errors 14400
where 14400 is the polling interval in seconds.


I would additionally suggest to support parameter

P75 PassiveCooling   (important for me in summer)


PS:
Thanks so far for your hard work and cooperation  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 März 2014, 22:08:01
an easy way for simulating a failure is to set the outside_temp sensor out of order. To do so you just need to open its case, open one of the two screws and remove one of the two wires. Failure should show up immediately. There's no risk of damaging anything.
If you don't know the pass code for the technician login to reset the error log afterwards I can send you by private message.


If you feel that's too dangerous for you I can test it of course. Send me the beta version in this case, please.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 März 2014, 23:07:15
Zitat von: immi am 08 März 2014, 21:38:58
@Markus: as wished new version 0.074 uploaded; we have to get ready for summer :)I expect fanstage1-Airflow to be in m3/h but I am not 100% sure

awesome :) will test this tomorrow.
@willy passive cooling is a good suggestion and as i see also implemented now

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 März 2014, 23:40:50
sorry, again a question:
I added a two rows to fhem.cfg
define myDbLog DbLog /mnt/fhem/db.conf Mythz
attr Mythz DbLogExclude allFB,timedate,history

Commandref says "A new Attribute DbLogExclude will be propagated to all Devices if DBLog is used." Nevertheless my try ends up in
ZitatMythz: unknown attribute DbLogExclude. Type 'attr Mythz ?' for a detailed list.

Bug or user error?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 März 2014, 23:46:10
i never did something with dblog but isn't the DbLogExclude attribute part of the dblog instead of THZ?
so i guess it should be

define myDbLog DbLog /mnt/fhem/db.conf Mythz
attr myDbLog DbLogExclude allFB,timedate,history

shouldn't it?

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 März 2014, 23:56:59
Zitat von: willybauss am 08 März 2014, 22:08:01
an easy way for simulating a failure is to set the outside_temp sensor out of order. To do so you just need to open its case, open one of the two screws and remove one of the two wires. Failure should show up immediately. There's no risk of damaging anything.
If you don't know the pass code for the technician login to reset the error log afterwards I can send you by private message.
If you feel that's too dangerous for you I can test it of course. Send me the beta version in this case, please.
Hi Willy
it would be great if you could try it.
I just need the answer to last10errors and the raw register D1
you can get D1 with
get Mythz debug_read_raw_register_slow
you find a file called data.txt in the directory, from which you started fhem (probably root /data.txt )

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 März 2014, 08:55:30
0.074 installed and working :) ready for the summer!

now when i look at the userReadings in my dashboard i asked myself how i add a button (or maybe 3 buttons) for the passive cooling there?

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 09:30:06
Zitat von: micomat am 09 März 2014, 08:55:30
0.074 installed and working :) ready for the summer!

now when i look at the userReadings in my dashboard i asked myself how i add a button (or maybe 3 buttons) for the passive cooling there?

markus
such buttons would be nice, would like it too. Did you ever think about turning passive cooling on/off automatically by information comming from window sensors? In my case this would look like:
If you can manage to create such buttons I would use the same solution to temporarily switch off ventilation or set it to max. volume temporarily, e.g. in case of smoke inside/outside.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 09:30:51
Zitat von: immi am 08 März 2014, 23:56:59
Hi Willy
it would be great if you could try it.
I just need the answer to last10errors and the raw register D1
you can get D1 with
get Mythz debug_read_raw_register_slow
you find a file called data.txt in the directory, from which you started fhem (probably root /data.txt )

immi
will do it today. Answer will follow.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 09:38:45
Zitat von: micomat am 08 März 2014, 23:46:10

i never did something with dblog but isn't the DbLogExclude attribute part of the dblog instead of THZ?
so i guess it should be

define myDbLog DbLog /mnt/fhem/db.conf Mythz
attr myDbLog DbLogExclude allFB,timedate,history

shouldn't it?

Markus


not really. Answer in this case
ZitatmyDbLog: unknown attribute DbLogExclude. Type 'attr myDbLog ?' for a detailed list.


Commandref says
ZitatA new Attribute DbLogExclude will be propagated to all Devices if DBLog is used.
So any device should know this attribute, Mythz as well. Is  myDbLog really a device in his case?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 09:45:44
regarding to DbLog:


looks like an error in Commandref's example. Trying
set Mythz DbLogExclude allFB,timedate,history
ends up in

Unknown argument DbLogExclude, choose one of holidayBegin-time holidayBegin_day holidayBegin_month holidayBegin_year holidayEnd-time holidayEnd_day holidayEnd_month holidayEnd_year p01RoomTempDayHC1 p01RoomTempDayHC2 p02RoomTempNightHC1 p02RoomTempNightHC2 p03RoomTempStandbyHC1 p03RoomTempStandbyHC2 p04DHWsetDay p05DHWsetNight p07FanStageDay p08FanStageNight p09FanStageStandby p99FanStageParty programDHW_Fr_0 programDHW_Fr_1 programDHW_Fr_2 programDHW_Mo-Fr_0 programDHW_Mo-Fr_1 programDHW_Mo-Fr_2 programDHW_Mo-So_0 programDHW_Mo-So_1 programDHW_Mo-So_2 programDHW_Mo_0 programDHW_Mo_1 programDHW_Mo_2 programDHW_Sa-So_0 programDHW_Sa-So_1 programDHW_Sa-So_2 programDHW_Sa_0 programDHW_Sa_1 programDHW_Sa_2 programDHW_So_0 programDHW_So_1 programDHW_So_2 programDHW_Th_0 programDHW_Th_1 programDHW_Th_2 programDHW_Tu_0 programDHW_Tu_1 programDHW_Tu_2 programDHW_We_0 programDHW_We_1 programDHW_We_2 programFan_Fr_0 programFan_Fr_1 programFan_Fr_2 programFan_Mo-Fr_0 programFan_Mo-Fr_1 programFan_Mo-Fr_2 programFan_Mo-So_0 programFan_Mo-So_1 programFan_Mo-So_2 programFan_Mo_0 programFan_Mo_1 programFan_Mo_2 programFan_Sa-So_0 programFan_Sa-So_1 programFan_Sa-So_2 programFan_Sa_0 programFan_Sa_1 programFan_Sa_2 programFan_So_0 programFan_So_1 programFan_So_2 programFan_Th_0 programFan_Th_1 programFan_Th_2 programFan_Tu_0 programFan_Tu_1 programFan_Tu_2 programFan_We_0 programFan_We_1 programFan_We_2 programHC1_Fr_0 programHC1_Fr_1 programHC1_Fr_2 programHC1_Mo-Fr_0 programHC1_Mo-Fr_1 programHC1_Mo-Fr_3 programHC1_Mo-So_0 programHC1_Mo-So_1 programHC1_Mo-So_3 programHC1_Mo_0 programHC1_Mo_1 programHC1_Mo_2 programHC1_Sa-So_0 programHC1_Sa-So_1 programHC1_Sa-So_3 programHC1_Sa_0 programHC1_Sa_1 programHC1_Sa_2 programHC1_So_0 programHC1_So_1 programHC1_So_2 programHC1_Th_0 programHC1_Th_1 programHC1_Th_2 programHC1_Tu_0 programHC1_Tu_1 programHC1_Tu_2 programHC1_We_0 programHC1_We_1 programHC1_We_2 programHC2_Fr_0 programHC2_Fr_1 programHC2_Fr_2 programHC2_Mo-Fr_0 programHC2_Mo-Fr_1 programHC2_Mo-Fr_3 programHC2_Mo-So_0 programHC2_Mo-So_1 programHC2_Mo-So_3 programHC2_Mo_0 programHC2_Mo_1 programHC2_Mo_2 programHC2_Sa-So_0 programHC2_Sa-So_1 programHC2_Sa-So_3 programHC2_Sa_0 programHC2_Sa_1 programHC2_Sa_2 programHC2_So_0 programHC2_So_1 programHC2_So_2 programHC2_Th_0 programHC2_Th_1 programHC2_Th_2 programHC2_Tu_0 programHC2_Tu_1 programHC2_Tu_2 programHC2_We_0 programHC2_We_1 programHC2_We_2

still not perfect, but at least Mythz accepts DbLogExclude now.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 16:51:33
Zitat von: immi am 08 März 2014, 23:56:59
Hi Willy
it would be great if you could try it.
I just need the answer to last10errors and the raw register D1
you can get D1 with
get Mythz debug_read_raw_register_slow
you find a file called data.txt in the directory, from which you started fhem (probably root /data.txt )

immi


Hi immi,


data.txt attached.


last10errors:
number_of_faults: 257 fault0CODE: 5376 fault0TIME: 97:6 fault0DATE: 34563 fault1CODE: 0 fault1TIME: 0:0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0:0 fault2DATE: 0 fault3CODE: 0 fault3TIME: 0:0 fault3DATE: 0 fault4CODE: 0 fault4TIME: 0:0 fault4DATE: 0 fault5CODE: 0 fault5TIME: 0:0 fault5DATE: 0 fault6CODE: 0 fault6TIME: 0:0 fault6DATE: 0


The display reported
no. of faults: 1
fault code: 21 (outside temp sensor fault)
fault time stamp: 9. March 2014  16:33:xx  (sorry, can't remember seconds, if you need it let me know and I'll repeat the test)

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 März 2014, 20:07:30
immi,

when restarting fhem and having a look at the mythz readings i found some interesting behaviour.
as we know the initial readings will take some minutes. but i saw in the event monitor every second one reading updated, AND all of my userreadings were updated once per second, too as long as the initial readings took. after all readings were updated, the secondly updates of my userreadings stopped.
it that normal?

markus
PS: i also never had any errors on my THZ
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 20:31:41
sounds like same issue as I had here:


Zitat von: immi am 06 März 2014, 20:28:36
Hy Willy
no bug in 00_THZ
commandref is always your friend:if you do not use the :<trigger>, each time MyTHZ is updated also the userreading will be updated
here the corrected version

attr Mythz userReadings inside_temp:allFB {((split ' ',ReadingsVal("Mythz","allFB",0))[81]) - 0.6 }, Rel_humidity:allFB {((split ' ',ReadingsVal("Mythz","allFB",0))[67]) + 11.5}

immi
please have a look at  :allFB
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 März 2014, 20:41:32
corrected the reading, will have an eye on it ;)

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 März 2014, 20:56:28
Hi
I played around with dblog.
The standard installation of dblog restricts the reading to 32 char and event 512 char
CREATE TABLE `fhem`.`history` (TIMESTAMP TIMESTAMP, DEVICE varchar(32), TYPE varchar(32), EVENT varchar(512), READING varchar(32), VALUE varchar(
32), UNIT varchar(32));

Therefore allfb will get a trunkation after the given length: e.g last parameter in allFB is InputVentilatorPower

Concerning blacklisting in dblog, the right sysntax is
define myDbLog DbLog /opt/fhem/configDB.conf  .*:.* 
attr  Mythz DbLogExclude allFB:600,P75passiveCooling 
 
In this way allFB will be written every 600s and P75passiveCooling will be ignored.

There is a trick which I did not find in any documentation; you have to add  DbLogExclude to the userattributes...
attr global userattr DbLogExclude devStateIcon devStateStyle fp_Pianoterra fp_Secondopiano fp_primopiano icon room_map sortby structexclude webCmd.....

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 21:34:28
A look into the data inside the database shows that allFB is being stored as a long string containing a sequence of all the different readings (same as the long row in FileLog). Did you manage to access single date out of this string? I don't have a clue how this could look like. Therefore for me it looks like it's useless to store allFB at all.
ZitatConcerning blacklisting in dblog, the right sysntax is

define myDbLog DbLog /opt/fhem/configDB.conf  .*:.*  
Using this   .*:.* syntax leads to logging everything in the database, even the useless (?) string based data allFB, history, last10errors. Therefore (and because  DbLogExclude didn't work) I used this one instead, in order to store just a few values:
define myDbLog DbLog /mnt/fhem/db.conf .*:.*(dhw_temp|Rel_humidity|flow_temp|return_temp|inside_temp|outside_temp).*
ZitatThere is a trick which I did not find in any documentation; you have to add  DbLogExclude to the userattributes...

attr global userattr DbLogExclude devStateIcon devStateStyle fp_Pianoterra fp_Secondopiano fp_primopiano icon room_map sortby structexclude webCmd.....
I did not yet catch how this translates into the Mythz example  :-\ . Could you give me an additional hint?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 März 2014, 21:40:26
forget my last sentence. I managed it meanwhile. fhem.cfg now looks like
define myDbLog DbLog /mnt/fhem/db.conf .*:.*(dhw_temp|Rel_humidity|flow_temp|return_temp|inside_temp|outside_temp).*
attr global userattr DbLogExclude
attr Mythz DbLogExclude allFB

and works  :) . Thanks for the hint!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 März 2014, 22:41:46
Hi Willi
could you repeat the same experiment with failure 21.
Exacltly the same but tomorrow and another time.
The data that you provided is precius; with another dataset I think i can interprete the register, and confirm my hypothesis.
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 März 2014, 07:14:53
ok, will do it this evening
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 März 2014, 19:48:01
2nd experiment result:
last10errors:
number_of_faults: 257 fault0CODE: 5376 fault0TIME: 141:7 fault0DATE: 60163 fault1CODE: 0 fault1TIME: 0:0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0:0 fault2DATE: 0 fault3CODE: 0 fault3TIME: 0:0 fault3DATE: 0 fault4CODE: 0 fault4TIME: 0:0 fault4DATE: 0 fault5CODE: 0 fault5TIME: 0:0 fault5DATE: 0 fault6CODE: 0 fault6TIME: 0:0 fault6DATE: 0
data.txt attached

heatpump reported in display:

error# 21  19:33  10-March 14
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 März 2014, 20:56:11
Ok the second dataset confirmed my hypothesis for last10errors
this is my interpretation for error# 21  19:33  10-March 14

D1-6B D1 01 01 15 00 8D07 EB03 0000000000000000000....
6B --> CRC
D1 --> register
01 --> number of failures
01 --> no idea (maybe year)
15 --> hex of 21
00 --> no idea (maybe year)
8D07 --> turn 078D --> hex of 19:33
EB03 --> turn 03EB --> hex of 10.03

In this heatpump, each register has a different representation of variable .
There are 8 different ways of representing the time..
Never seen such a funny firmware.
I do not find year 2014. We need to repeat this failure, next year or after changing the date.

I will finish implementing the code tonight and I will commit version 0.075 including an interval parameter.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 März 2014, 21:18:27
Zitat von: immi am 10 März 2014, 20:56:11
In this heatpump, each register has a different representation of variable .
There are 8 different ways of representing the time..
Never seen such a funny firmware.
Sounds like the software engineers moved to my company when their work had been finished  ;)


ZitatI do not find year 2014. We need to repeat this failure, next year or after changing the date.
of course we can do it. On the other way - if one could ignore a failure over a period of a year he might not need this code at all ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 März 2014, 21:35:10
Hi willy
please test v0075, download it directly or update tomorrow.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 März 2014, 08:56:02
using v0075 I tried
attr Mythz interval_last10errors 120

without success:
Mythz: unknown attribute interval_last10errors. Type 'attr Mythz ?' for a detailed list.


So far I didn't have time to search for right syntax in THZ code. Could you give me a hint, please? Or did I misunderstand the goal?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 März 2014, 11:46:58
Hi willy
syntax is correct and yesterday night worked.
please  make sure that you have the last version and that after update you restarted fhem

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 März 2014, 12:22:10
Zitat von: immi am 11 März 2014, 11:46:58
... after update you restarted fhem
that's the topic I missed. Will try again this evening.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 11 März 2014, 19:41:45
working here also :)
added v0.075 info to the wiki pages
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 März 2014, 20:50:07
 yes, works basically. Decoding of result is fine.
What I do not yet understand is, that it's named last10errors but it reports  just  3 errors:
2014-03-11_20:34:15 Mythz last10errors: number_of_faults: 1 fault0CODE: 21 fault0TIME: 19:33 fault0DATE: 10.03 fault1CODE: 0 fault1TIME: 0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0 fault2DATE: 0 fault2CODE: 0 fault2TIME: 0 fault2DATE: 0
previous THZ versions reported 7 errors:
number_of_faults: 257 fault0CODE: 5376 fault0TIME: 97:6 fault0DATE: 34563 fault1CODE: 0 fault1TIME: 0:0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0:0 fault2DATE: 0 fault3CODE: 0 fault3TIME: 0:0 fault3DATE: 0 fault4CODE: 0 fault4TIME: 0:0 fault4DATE: 0 fault5CODE: 0 fault5TIME: 0:0 fault5DATE: 0 fault6CODE: 0 fault6TIME: 0:0 fault6DATE: 0
HeatpumpMonitor indeed reports 10 errors, so it should be possible to do so.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 März 2014, 21:46:56
willy
I log only 4 errors to save disk-space.
I have cut 60% of the register, considering that:
1) we have not tested the errors >1; could be that an offset is needed before the second error.
2) I have never had an error; very unlikely that I get more than 4 errors at the same time.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 März 2014, 22:27:14
that's reasonable of course. But as you mentioned "I log only 4 errors  ..." I noticed that there's really an error. Again the result:
2014-03-11_22:18:17 Mythz last10errors: number_of_faults: 1 fault0CODE: 21 fault0TIME: 19:33 fault0DATE: 10.03 fault1CODE: 0 fault1TIME: 0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0 fault2DATE: 0 fault2CODE: 0 fault2TIME: 0 fault2DATE: 0
Please scroll to the right and read carefully. You will notice that there's no fault3* at all, but all the fault2* entries exist twice. Looks like a copy-paste error.


I'll go on forcing errors next weekend, in order to verify if they're logged correctly.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 März 2014, 23:22:02
thanks willy
In this way we can be really sure
fault2-fault2 is now fixed but I will wait untill weekend before uploading.
I am currently working on register F4 and F5; and I do not want to fork the code.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 März 2014, 07:43:16
hey immi,
i have a feature request for you :)
the THZ is having a function called "unscheduled ventilation" (see screenshot) (in german Lüftung ausserplan.)
now when the bbq season starts i discovered the problem that the ventilation soaks up the smoke.
is it possible to implement the unscheduled ventilation function to disable the ventilation for a specific time and automatically re-enable it (to not forget it)?

regards
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 März 2014, 11:54:39
Hi Markus
I didn´t know about the feature, which is nothing else than a reverse party time.
I have problems writing in the party time register, I can only read it.
I do not use party time anymore, because we have fhem "at" command, which is much better.
The helper modules of fhem are simple but very very powerfull!!

To make it short, schedule an "at" changing of the ventilation-stage.
something like

define bbqbegin at 18:00:00 set p07FanStageDay 0
define bbqend at 20:00:00 set p07FanStageDay 1



http://fhem.de/commandref.html#at
You do not need to write them in the config files. If they are one time-events, use the command interface.


immi



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 März 2014, 12:34:24
Okay, so i will create a command like "disable ventilation for 1h" for the case my neighbour is burning some smelly things in his fireplace ;)

by the way i discovered a strange behavoir.
while having the thz-log on tail -f i saw the log going wild some time.
i was looking at the fhem-log and saw a depndence to the disappear-message for thz.
the thz started to update the values uncontrolled as it seems...

here are the logs:

fhem.log

2014.03.12 12:27:35 1: 192.168.178.50:2003 reappeared (Mythz)
2014.03.12 12:27:36 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.03.12 12:27:36 1: 192.168.178.50:2003 reappeared (Mythz)
2014.03.12 12:27:37 1: 192.168.178.50:2003 disconnected, waiting to reappear
2014.03.12 12:27:37 1: 192.168.178.50:2003 reappeared (Mythz)


thz.log

2014-03-12_12:28:37 Mythz programHC2_Sa_2: 00:00--24:00
2014-03-12_12:28:37 Mythz programFan_Tu_0: 08:30--20:45
2014-03-12_12:28:37 Mythz programFan_Tu_0: 08:30--20:45
2014-03-12_12:28:38 Mythz programHC1_Th_2: n.a.--n.a.
2014-03-12_12:28:38 Mythz programHC1_Sa-So_0: 08:15--21:15
2014-03-12_12:28:38 Mythz programHC1_Sa-So_0: 08:15--21:15
c2014-03-12_12:28:39 Mythz programFan_Tu_0: 08:30--20:45
2014-03-12_12:28:39 Mythz programDHW_Tu_2: n.a.--n.a.
2014-03-12_12:28:39 Mythz programDHW_Tu_2: n.a.--n.a.
2014-03-12_12:28:40 Mythz programHC1_Sa-So_0: 08:15--21:15
2014-03-12_12:28:40 Mythz programHC2_Mo-So_1: 00:00--24:00
2014-03-12_12:28:40 Mythz programHC2_Mo-So_1: 00:00--24:00
2014-03-12_12:28:41 Mythz programDHW_Tu_2: n.a.--n.a.
2014-03-12_12:28:41 Mythz programFan_Sa_2: n.a.--n.a.
2014-03-12_12:28:41 Mythz programFan_Sa_2: n.a.--n.a.
2014-03-12_12:28:42 Mythz programHC2_Mo-So_1: 00:00--24:00
2014-03-12_12:28:42 Mythz programHC1_Mo-So_0: 00:00--24:00
2014-03-12_12:28:42 Mythz programHC1_Mo-So_0: 00:00--24:00
2014-03-12_12:28:43 Mythz programFan_Sa_2: n.a.--n.a.
2014-03-12_12:28:43 Mythz programFan_So_0: 08:45--20:45
2014-03-12_12:28:43 Mythz programFan_So_0: 08:45--20:45
2014-03-12_12:28:44 Mythz programHC1_Mo-So_0: 00:00--24:00
2014-03-12_12:28:44 Mythz programFan_Mo-So_2: n.a.--n.a.
2014-03-12_12:28:44 Mythz programFan_Mo-So_2: n.a.--n.a.
2014-03-12_12:28:45 Mythz programFan_So_0: 08:45--20:45
2014-03-12_12:28:45 Mythz programDHW_Fr_2: n.a.--n.a.


there are several duplicate entrys and also fhem performance was quite poor while this happens.
the fhem.pl process was hat 100% load.

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 März 2014, 13:58:18
Hi markus
both logs are linked to the connect/disconnect issue with ser2net.
I improved (but not solved) the issue completely.
I had a single event in 3 weeks.
Nonetheless, a network connection is not as stable a  direct connection. There will be always anomalies (e.g. too much bittorrent), which fhem has to be compatible with.

One solution could be to wait 10 second before reconnecting.
The solution is not easy, because there is no way to check properly if the network connection is active.
There is a discussion between FHEM expert-developers running.
When they come to a decision (how to detect a disconnect), I will try to fix.

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 März 2014, 14:15:22
thanks for the answer, i can wait for it :)

attached a screenshot of a part of my readings-dashboard :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 März 2014, 15:11:10
Markus
it looks really good.
when you have time, post the code it in the wiki

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 März 2014, 18:03:47
of course i will share it on the wiki pages ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 März 2014, 21:47:50
Markus:
your dashboard looks very nice, I need the code as soon as it's on wiki. I didn't know how to manage this, so I put all necessary data into the graph header, as attached picture shows.

The logic of "unscheduled ventilation" is a bit different from party time. While party time defines two time stamps for start and stop (both to be in future), the "unscheduled ventilation" starts immediately after being set; end is not defined as a time stamp, but as a duration. And while party time can just increase ventilation for a time period, "unscheduled ventilation" can be used with any ventilation setting. So you can either say "stop for an hour", or "full throttle for an hour" (in case you burned your steaks), or "level x for an hour", where 0<=x<=3. But I agree with immi: by using at commands all of these should be doable without writing anything to the heatpump's registers. I don't know yet how to do it, ideally by just pressing a button to execute the code, but I will find out sooner or later. Using Excel's VBA I would have done it within 2 minutes.


btw: the whole program* stuff and holiday* stuff could also be managed using at commands, right? But at least in case of program* it might be better to be independent from externals like fhem.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 März 2014, 21:52:31
willy, code with all description will follow on wiki in the next few days, so be patient :)
it's not so difficult as it maybe looks like.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 März 2014, 22:36:03
v 0.076


for "Status_HC1_F4"   I need some help for validating the given values:

outside_temp: 8.5 x08: 13.9 return_temp: 35.3 integral_heat: 82 flow_temp: 35.2 heat-set_temp: 25.6 heat-actual_temp: 35.2 x32: 0.1 x36: 0.1 x40: 819.2 integral_switch: 100 x48: 51.2 x52: 0 room-set-temp: 20.8 x60: 39.1 x64: 563.2 x68: 20.8 x72: 51.2 x76: 2.2 x80: 0


maybe you have better names for the interpreted values (like integral_heat,  integral_switch);
maybe you have an idea what are the vaue I have not discovered (like x08,x32,x40,x48....)

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 13 März 2014, 06:34:54
thanks immi,

i will check this at my side asap and tell you the results. i have already an idea for one or two values but i will check first.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 März 2014, 08:07:26
will check @ weekend; sorry, no free time before
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 März 2014, 15:47:30
here's my HC1-F4
outside_temp: 17.5 x08: 48.4 return_temp: 27.3 integral_heat: 40 flow_temp: 26.7 heat-set_temp: 27.6 heat-actual_temp: 27.1 x32: 0.2 x36: 0.1 x40: 0 integral_switch: 100 x48: 128 x52: 0 room-set-temp: 22.5 x60: 0 x64: 563.2 x68: 22.5 x72: 51.2 x76: 2.2 x80: 0

as i don't have a HC2 connected to the heatpump, the settings there are not made correctly.

unfortuneatly i was not able to identify more values while scrolling through the heatpump menus.
the only parameter looks familiar is x68, this looks like the room-set-temp, too.
maybe these parameters are hidden to the "normal" display.

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 14 März 2014, 18:05:34
Hi,

i have hc2 in use,

Status_HC1_F4
outside_temp: 12 x08: -8.5 return_temp: 25.9 integral_heat: 4 flow_temp: 27.1 heat-set_temp: 26.8 heat-actual_temp: 26 x32: 0.1 x36: 0.1 x40: 0 integral_switch: 100 x48: 25.6 x52: 0 room-set-temp: 22 x60: 0 x64: 691.2 x68: 22 x72: 51.2 x76: 2.7 x80: 1.7
2014-03-14 18:02:41
Status_HC2_F5
outside_temp: 12 x08: 26 return_temp: 25.4 integral_heat: 256 flow_temp: 25.4 heat-set_temp: 0 heat-actual_temp: 0.1 x32: 0 x36: 25.6 x40: 0 integral_switch: 0 x48: 0 x52: 0
2014-03-14 18:02:07
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 14 März 2014, 18:09:04
btw,

when I try to create a chart with the new chartmodul from filelog_thz, I allways gets 0's.
Why is my inside temp allways -60?

br
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 März 2014, 18:10:36
Inside temp is -60 when You dont have an inside sensor. Same here.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 14 März 2014, 18:27:11
but I have a separat FES for HC2! I need it for cooling.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 März 2014, 18:50:47
what is a FES?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 14 März 2014, 19:32:27
Das ist das 2.Bedienteil, das bei mir im Wohnzimmer hängt. Ist das gleiche wie in der Wärmepumpe, nur ohne Brücke!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 März 2014, 19:35:14
i see... so there should be a temp value. so can you See it in allfb?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 März 2014, 19:46:15
Michael
F5 was only  copy and paste from f4; It was not meat to be released, but to be commented out.
if you identify the parameters of F5 clearly I can fix it.
My HC2 is not connected.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 14 März 2014, 23:32:46
same at my side. FES measured inside_temp isn't shown in data report. You need an external temperature sensor. That's obviously the only way to get something different from -60. I tried to get rid of this sensor, but didn't manage to get the FES's temperature measurement to be reported.


PS:
FES is the external display. Identical to internal one, but located in e.g. living room and connected by CAN bus.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 März 2014, 13:38:12
Zitat von: michaelk68 am 14 März 2014, 18:09:04
btw,

when I try to create a chart with the new chartmodul from filelog_thz, I allways gets 0's.
Why is my inside temp allways -60?

br
Michael
one more chance to fix it: go to menu
INBETRIEBNAHME - RT.ERFASSUNG HK
and set the value to "HK1".


If that fixes the issue please let me know. I tried to do so without success, but a member of a different forum told me that it works in this way in his heatpump.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 März 2014, 13:48:51
Zitat von: immi am 12 März 2014, 22:36:03
new parameter "Status_HC1_F4"   
for "Status_HC1_F4"   I need some help for validating the given values:

outside_temp: 8.5 x08: 13.9 return_temp: 35.3 integral_heat: 82 flow_temp: 35.2 heat-set_temp: 25.6 heat-actual_temp: 35.2 x32: 0.1 x36: 0.1 x40: 819.2 integral_switch: 100 x48: 51.2 x52: 0 room-set-temp: 20.8 x60: 39.1 x64: 563.2 x68: 20.8 x72: 51.2 x76: 2.2 x80: 0


maybe you have better names for the interpreted values (like integral_heat,  integral_switch);
maybe you have an idea what are the vaue I have not discovered (like x08,x32,x40,x48....)

immi
Hi immi,


sorry, don't have any idea for interpretation of the remaining values. May these values be encrypted, and after being decrypted they may fit some definitions of heating curve, e.g. foot point, gradient, etc., t.b. found in menu HEIZEN - HEIZKURVE HK1 ?
The value of integral_switch fits the value of "Integralanteil" in my case (good luck or correct assumption?). So I wonder if integral_quota might be a better name? Don't have a clue what  integral_heat could mean. Do you have a german translation?


Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 März 2014, 13:53:52
a different topic:
I would like to get alarmed e.g. by email as soon as specific things happen, e.g. booster usage (=> booster usage hours increase), no. of errors increases, room temperature is below a specific value, ...


Since I'm new to fhem I don't yet have a plan on how to do that, nor how to start with it. So could one of you give me a few hints, please?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 März 2014, 14:48:33

If you find a better wording (or interpretation) for the parameters please let me know.
sreenshot from the servicesoftware,

F4
outside_temp: 9 x08: 29.3 return_temp: 32.8 integral_heat: 16 flow_temp: 33.7 heat-set_temp: 26.1 heat-actual_temp: 33 x32: 0.1 x36: 0.1 x40: 0 integral_switch: 100 x48: 25.6 x52: 0 room-set-temp: 21.2 x60: 0 x64: 563.2 x68: 21.2 x72: 51.2 x76: 2.2 x80: 0

F5
outside_temp: 10.3 return_temp: 37.7 vorlauftemp: -60 heat-actual_temp: 25.4 heat-set_temp: 37.7 stellgroesse: -100 x28: 0.1 x32: 819.2 x36: 51.2 x40: 0.2 x44: 0 x48: 0 x52: 0


@willy
if you want to configure the email in fhem
http://www.fhemwiki.de/wiki/E-Mail_senden

if you want to trigger an email for a certain event, use "notify"

define Sonstiges notify Fenster:Window:.*,.*Low.Batt*. {\
DebianMail('email@@email.domain','Subject','Text');;\
}

if you want an email at a certain time use "AT"

define Sonstiges at *01:00:00 {\
DebianMail('email@email.domain','Subject','Text');;\
}



immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 15 März 2014, 17:47:01
Hi Willibaus,

I cant set it to HK1, because I use HK2.
My HK1 is only from the heatpump to the buffer. HK2 is my underfloor heating!


Michael

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 März 2014, 18:52:26
intresting installation differences :)
i have only one HC for both. floor heating and warm water :)

@immi,
i just set some fan stages and now i see two fanstage readings? the old and the new one. the old one seems not to be updated.

2014-03-15 18:43:28
P37fanstage1-Airflow-inlet

50 m3/h

2014-03-14 09:18:53
P38fanstage2-Airflow-inlet

80 m3/h

2014-03-14 09:20:59
P39fanstage3-Airflow-inlet

220 m3/h

2014-03-14 09:20:35
P40fanstage1-Airflow-outlet

50 m3/h

2014-03-14 09:19:34
P41fanstage2-Airflow-outlet

80 m3/h

2014-03-14 09:20:11
P42fanstage3-Airflow-outlet

220 m3/h

(snip... some output omitted)

2014-03-15 18:45:18
p07FanStageDay

2

2014-03-15 18:43:50
p08FanStageNight

1

2014-03-15 18:45:09
p09FanStageStandby

0

2014-03-15 18:44:11
p37fanstage1-Airflow-inlet

50 m3/h

2014-03-15 18:45:22
p38fanstage2-Airflow-inlet

80 m3/h

2014-03-15 18:44:42
p39fanstage3-Airflow-inlet

120 m3/h

2014-03-15 18:45:10
p40fanstage1-Airflow-outlet

50 m3/h

2014-03-15 18:44:46
p41fanstage2-Airflow-outlet

80 m3/h

2014-03-15 18:44:41
p42fanstage3-Airflow-outlet

120 m3/h



an ideas? i saw they have a yesterday date. maybe since the last update?
btw, there is a spelling mistake in some standby values. they are called stendby instead of standby :)

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 März 2014, 20:22:36
Markus
you did nothing wrong.
please delete the old readings with
deletereading Mythz P37fanstage1-Airflow-inlet
....

Now all pxx are lowrcase, and some typos have been corrected (some version ago)
Old readings names will not be deleted automatically.

p.s.
I just  uploaded version 0.078, you can update tomorrow
- new parameters Status_Sol_16  and Status_DHW_F3

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 März 2014, 22:50:46
you are too fast man ;)
i still have to add the last version inormation to the wiki.

thanks for info 'bout the readings. will delete them.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 März 2014, 08:51:12
Zitat von: michaelk68 am 15 März 2014, 17:47:01
Hi Willibaus,

I cant set it to HK1, because I use HK2.
My HK1 is only from the heatpump to the buffer. HK2 is my underfloor heating!


Michael
in this case set it to HK2 of course. If you still have inside_temp = -60 in your allFB reading you definitely need an external sensor to fix it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 März 2014, 09:13:10
information about v0.076 and 0.079 now added to wiki

[EDIT]
Configuration example is now also available on wiki
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 März 2014, 21:39:20
As usual exellent documentation from markus
immi

p.s.
I just played around, I wanted a button for the ventilator in the frontend.
Expert fhem users have much better code; but it is a good starting point, therefore I share

define FanSelector dummy
attr FanSelector group THZ
attr FanSelector setList 0 1 2 3
attr  FanSelector webCmd 0:1:2:3
attr FanSelector devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageDay notify FanSelector set Mythz p07FanStageDay $EVENT
define Notify_Fanselector notify (Mythz.p07FanStageDay.*) setstate FanSelector $EVTPART1
attr FanSelector room pompa

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 März 2014, 21:45:51
ah nice :)
will Test this Code also.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 März 2014, 12:29:19
Zitat von: immi am 17 März 2014, 21:39:20
I just played around, I wanted a button for the ventilator in the frontend.
...
works smoothly  :) .
Unfortunately there seems to be no automatic refresh of the icon, same as with e.g. lamp icon for light switches. Refreshing the whole page takes some seconds because of the slow graph update.


btw:
Zitat von: immi am 15 März 2014, 14:48:33
if you want to trigger an email for a certain event, use "notify"

define Sonstiges notify Fenster:Window:.*,.*Low.Batt*. {\
DebianMail('email@@email.domain','Subject','Text');;\
}

I did not yet manage to translate the 'notify' row into being alarmed in case of failures. Need to try and error again next weekend.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 März 2014, 16:00:05
Hi Willy
Unfortunately there seems to be no automatic refresh of the icon, same as with e.g. lamp icon for light switches. Refreshing the whole page takes some seconds because of the slow graph update.

Are you sure?
The icon  updates itself after ventilation stage changes: you have to wait that the command is written in the heatpump and that fhem reads the command back. This takes circa 3 seconds.


for the emailnotification: I find also interesting the pushover module.


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 März 2014, 17:47:14
Zitat von: immi am 21 März 2014, 16:00:05
The icon  updates itself after ventilation stage changes: you have to wait that the command is written in the heatpump and that fhem reads the command back. This takes circa 3 seconds.
o.k. was a browser issue: doesn't update with Opera, but does update with Chrome. Need to search inside Opera settings.


Zitat von: immi am 21 März 2014, 16:00:05
for the emailnotification: I find also interesting the pushover module.
will have a look into. Thanks so far.


Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 März 2014, 18:40:02
I added to my frontend a second vent button for the night speed stage,
I am sure Markus can integrate in dashboard the buttons in a much more elegant way ;)
worth a wiki update ?

define FanSelectorDay dummy
attr FanSelectorDay group THZ
attr FanSelectorDay setList 0 1 2 3
attr  FanSelectorDay webCmd 0:1:2:3
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageDay notify FanSelectorDay set Mythz p07FanStageDay $EVENT
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1
attr FanSelectorDay room pompa

define FanSelectorNight dummy
attr FanSelectorNight group THZ
attr FanSelectorNight setList 0 1 2 3
attr  FanSelectorNight webCmd 0:1:2:3
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageNight notify FanSelectorNight set Mythz p08FanStageNight $EVENT
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1
attr FanSelectorNight room pompa


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 21 März 2014, 18:54:07
Hi, I am newbie and I really admire all your efforts. In the past I have tried to get the heatpump monitor to work on a NSLU2 but I already had trouble getting the new diabian on there. I have a SE LWZ303i running version 4.09. I have a RPi and got FHEM in there and the latest THZ.pm. And I plant to connect RPi_USB to LWZ_USB directly. I really appreciate the wiki which is extremely helpful. However, I have a few questions for which I just need brief answers:
1. Can I copy and past the code from the sample config directly into fhm.cfg? only difference would be:
define Mythz THZ /dev/ttyUSB0@115200
because of the direct USB connection?
2. I am a little nervous about connecting an interior port of a heat pump to an external device...if done right, meaning to plug in and than start the RPi...it only sits and reads the output, never by default alters anything on the LWZ board. Right?
3. Are there other files that need to be modified with local settings?

I like the idea to have actual input. My dream would be able to connect somehow with a local weather station, pull the 24hr forecast from there and so if temp. are about change, the smart LWZ would enter to a pre-programmed setting.

Greetings,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 März 2014, 19:36:51
Hi Tom
the best compliment would be that you make 00_THZ work for you.
Zitat von: houseowner123 am 21 März 2014, 18:54:07
1. Can I copy and past the code from the sample config directly into fhm.cfg? only difference would be:
define Mythz THZ /dev/ttyUSB0@115200
because of the direct USB connection?
Have a try. no Idea if it is working with your firmware.

Zitat von: houseowner123 am 21 März 2014, 18:54:07
2. I am a little nervous about connecting an interior port of a heat pump to an external device...if done right, meaning to plug in and than start the RPi...it only sits and reads the output, never by default alters anything on the LWZ board. Right?
Set commands write back to the hetpump; get commands read from the heatpump.
Always pay attention on what you are doing.

Zitat von: houseowner123 am 21 März 2014, 18:54:07
3. Are there other files that need to be modified with local settings?
start simple; keep (at the beginning) your config as short and mainstream as possible


Zitat von: houseowner123 am 21 März 2014, 18:54:07
I like the idea to have actual input. My dream would be able to connect somehow with a local weather station, pull the 24hr forecast from there and so if temp. are about change, the smart LWZ would enter to a pre-programmed setting.

Already implemented in fhem from other nice developers.


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 März 2014, 00:38:13
Hi Tom,

i'm the author of the wiki articles.
And i started just like you. I also was unsure to connect on this internal interface. But i guesst it's only internal because there was no way out of the heatpump ;) For me the serial interface was never connecting so i started with heatpumpmonitor on USB and it was fine for me from the beginning. Then immi wrote me and so i started to migrate to fhem as i already had a fhem server on a RPi. The only difference is that i connect via Ser2Net.

So the 4.09 is not so far away from the 4.19 thats why i would say it should work.
You can start with the configuration example from the wiki, sure.
Or you begin with a simple configuration like this one:

define Mythz THZ /dev/ttyUSB0@115200
attr Mythz room THZ
attr Mythz interval_allFB 300
attr Mythz interval_history 28800
define FileLog_Mythz FileLog ./log/Mythz-%Y-%m.log Mythz

You should now have the room THZ with the Mythz inside. If you can see the readings after a click on Mythz in this room your fine =) Then you can add the readings, the logs and so on.

You can also ask me via direct messages if you want to. I'm sure you will love it :)

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 März 2014, 09:03:18
Zitat von: immi am 21 März 2014, 18:40:02

define Notify_p07FanStageNight notify FanSelectorNight set Mythz p08FanStageNight $EVENT
>> define Notify_p08FanStageNight notify FanSelectorNight set Mythz p08FanStageNight $EVENT


just working on an update :)
i guess in the second part (FanSelectorNight), the first notify should be on p08FanStageNight not on p07, right?

but sorry i cannot make it nicer then you, i just would prefer blue for the ventilation icons.
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0@blue 1:vent_ventilation_level_1@blue 2:vent_ventilation_level_2@blue 3:vent_ventilation_level_3@blue

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 März 2014, 14:12:08
Zitat von: micomat am 22 März 2014, 09:03:18
just working on an update :)
i guess in the second part (FanSelectorNight), the first notify should be on p08FanStageNight not on p07, right?

JAp,
in the name of the notify 08 or 07 will make no difference; both work.
But Markus you are right Notify_p08FanStageNight is much more elegant.

Zitat von: micomat am 22 März 2014, 09:03:18
but sorry i cannot make it nicer then you, i just would prefer blue for the ventilation icons.
actually I meant a nice integration in your dashboard; but you had a good idea blue for the night setting and green for the daysetting

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 März 2014, 14:14:04
it's already part of my dashboard ;)
i just didn't find some time to update the wiki. but i guess i will make it within the weekend.

THZ is getting better and better every day :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 März 2014, 18:38:40
As promised weeks ago I tried to force additional failures today, in order to give immi a chance to check the code. Unfortunately I didn't succeed. Obviously the THZ doesn't log the same failure again, as long as the first one isn't removed from the history. The only thing what happened is, that the THZ calculated the desired temperature value for HC1 based on the outside_temp of -60°C and heated up my house :-\ .
My only chance would be forcing other failures, different from outside temp sensor failure. I didn't do so, since none ot the other failures can be forced easily and/or without risk of damaging anything. Since noone of you had a failure yet, and my THZ as well had just one failure in last 4 years I believe we can live with the current situation. I'll try to find a way to send an email in case of no. of failures <>0. So total number of failures is not of highest interrest.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 März 2014, 18:57:46
you can try to reset the failure-log of the heatpump in the "installer"-menu. installer-code  should be 1000 if nobody changed it ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 März 2014, 20:53:14
willi
thanks anyhow for trying.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 März 2014, 22:31:41
Zitat von: micomat am 23 März 2014, 18:57:46
you can try to reset the failure-log of the heatpump in the "installer"-menu. installer-code  should be 1000 if nobody changed it ;)
Goal was to have more than 1 failure in history. Resetting failure-log will reset the failure counter to zero, what's in contradiction to the goal.
btw: For "Fachmann" actions like resetting the failure counter you need the "Fachmann-Login" which is different from 1000. I don't provide the code here ...  ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 März 2014, 06:38:25
on mine, 1000 enters the "god mode" :D
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 März 2014, 18:55:45
if you are able to delete the failure history using passcode 1000 someone changed the passcode from the original one to 1000.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 März 2014, 19:18:07
i don't care :) for me 1000 is no problem as nobody as myself is changing something on the THZ.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 März 2014, 19:25:46
@ immi
while searching for the solution to get emails in case of failure I stumbled over the argument event-on-change-reading. Am I right assuming that the THZ module doesn't support it?

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 März 2014, 19:33:02
@willy, try to create an "if" enquiry like "IF fault0DATE=today then send email".
so you could create and email when the last error date is up to date.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 März 2014, 22:47:20
meanwhile I managed to get informed by email in case of faults.


1st Solution:
define Mythz.alarm1 at +*01:00:00 { if (ReadingsVal("last10errors","number_of_faults",0) > 0 ) { DebianMail('MYNAME@t-online.de','Tecalor Mythz Alarm', 'ErrorLog hat ausgeloest: '. $EVENT) ;; } }
attr Mythz.alarm1 room Heizung


2nd Solution:
define Mythz.alarm notify .*fault.* { if (ReadingsVal("last10errors","number_of_faults",0) > 0 ) { DebianMail('MYNAME@t-online.de','Tecalor Mythz Alarm','ErrorLog hat ausgeloest: '. $EVENT);; } }
attr Mythz.alarm room Heizung



2nd solution is preferred, since email is being sent immediately. And there's no need to adjust time intervals if reading intervals are changed.


Unfortunately $EVENT doesn't work, don't know why  :-[ . The email just shows the phrase '$EVENT'
issue fixed meanwhile; code updated in examples.

Additionally I do not yet understand why I have to use wildcards   '.*fault.*'  instead of  'number_of_faults'  :-\ .
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 März 2014, 22:50:40
Zitat von: micomat am 24 März 2014, 19:33:02
@willy, try to create an "if" enquiry like "IF fault0DATE=today then send email".
so you could create and email when the last error date is up to date.
This would reduce no. of emails to max. 24, since I check for errors once per hour. I'd really like to wait for immi's answer for the event-on-change-reading feature before searching for a limitation of email count in different way.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 26 März 2014, 10:10:30
issue with $EVENT fixed. solutions updated in code above.

@micomat:
please feel free to copy the code into your wiki. It could be helpful ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 26 März 2014, 10:19:07
sure will add it next time i update the wiki =)
thanks!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 März 2014, 19:32:29
sorry guys,
I am currently not at home, bad internet connection, less time for private stuff.
Nevertheless i read that you made great progress without me.
good job willy

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 März 2014, 10:42:15
Hi Willy
There are several answers to your problems.
1) if you have a big issue in last10errors, I do not see a problem to get 20 emails. You should (let) repair it very fast, before something goes reaaly wrong.
2) if you really want only one email, you can set a variable like $emailsent after sending email and test it before sending.
3) event-on-change-reading is not fully implemented (and tested) so far in thz; actually I do not fully understand the command.ref: Double negations are quite tricky to interpret... The german version is not much better.

Zitatevent-on-update-reading
If not set, every update of any reading creates an event, which e.g. is handled by notify or FileLog. The attribute takes a comma-separated list of readings. You may use regular expressions in that list. If set, only updates of the listed readings create events.
event-on-change-reading
The attribute takes a comma-separated list of readings. You may use regular expressions in that list. If set, only changes of the listed readings create events. In other words, if a reading listed here is updated with the new value identical to the old value, no event is created.
The precedence of event-on-update-reading and event-on-change-reading is as follows:
    If both attributes are not set, any update of any reading of the device creates an event.
    If any of the attributes is set, no events occur for updates or changes of readings not listed in any of the attributes.
    If a reading is listed in event-on-update-reading, an update of the reading creates an event no matter whether the reading is also listed in event-on-change-reading.

Moreover: event-on-change-reading and event-on-update-reading and event-min-interval are very interesting because are standard attributes solving one open issue on my opl "blacklist some parameters from being logged and/or from generating notify". I have a week holiday for Easter  ...

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 März 2014, 22:49:20
Hi immi,

your 2nd option (set a variable like $emailsent after sending email and test it) sounds very easy; I'll try to do it in this way - thou version 1) is also absolutely right.

I played around with event-on-change-reading but observed that logging stops as soon as I try to use it. Might be caused by not being implemented fully. Then I thought about using the "differnce" option of userReadings. But  $emailsent seems indeed to be the easiest way.

I want to use email information not just in case of failures but also in case of e.g. booster usage. And in this case it's really not necessary to get tons of emails instead of one per day.

event-on-change-reading would  - as I understand the commandref -  not allow more than one different email triggers. But my current solution combined with  $emailsent does.

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 April 2014, 20:13:10
summer is definitely coming. Therefore v0.080

changelog:
-bit responsible for summer/winder mode identified
-Status_HC1_F4 and Status_HC2_F5 present now "mode: Summer" (or Winter)
-p49SummerModeTemp and p50SummerModeHysteresis implemented read/write

from the heatpump datasheet following rule:
if outsidetemp > p49SummerModeTemp + p50SummerModeHysteresis ---> Summermode
if outsidetemp < p49SummerModeTemp - p50SummerModeHysteresis ---> Wintermode

e.g.
p49SummerModeTemp =15 °C
p50SummerModeHysteresis =3 K
if outsidetemp > 18 °C ---> Summermode
if outsidetemp < 12 °C ---> Wintermode


@Markus please check the version and update the wiki

thanks
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 April 2014, 20:50:54
Great invention :) will Check and update tomorrow :)

edit: i can already See the icons representing Winter/Summer State in my mind :)

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 April 2014, 15:14:40
hi immi,

i updated to 0.80 and i can see the values P49 and P50 now. in HC2 the display of the mode is visible:
outside_temp: 21.3 return_temp: 29.2 vorlauftemp: -60 heat_temp: 20.4 heat-set_temp: 29.2 stellgroesse: -100 mode: winter x32: 0 x36: 256 x40: 2 x44: 0 x48: 0 x52: 0
in HC1 i miss the mode description?
outside_temp: 21.2 x08: 51.5 return_temp: 29.1 integral_heat: 0 flow_temp: 29.4 heat-set_temp: 24.9 heat_temp: 29.1 x32: 0.2 x36: 0.2 x40: 0 integral_switch: 100 mode: x52: 0 room-set-temp: 21 x60: 0 x64: 5632 x68: 210 x72: 512 x76: 22 x80: 0

i also noticed that i saw the value of P49 coming up in the thz-log while restarting fhem but i first saw it in fhem after manually klicking on "get p49". P50 was showing up from the beginning.
and ideas? i only use HC1.

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 03 April 2014, 15:18:12
Hello, thanks for everybody's hard work on this project. I can confirm that so far all code is working on version 4.09.  :)

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 April 2014, 15:32:12
Zitat von: immi am 02 April 2014, 20:13:10
from the heatpump datasheet following rule:
if outsidetemp > p50SummerModeHysteresis + p50SummerModeHysteresis ---> Summermode
if outsidetemp < p50SummerModeHysteresis - p50SummerModeHysteresis ---> Wintermode
immi:
I can't believe that the formula fits. You have  p50SummerModeHysteresis twice in same formula. I believe one of them should be something like pxxSummerModeValue
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 April 2014, 15:37:06
Zitat von: houseowner123 am 03 April 2014, 15:18:12
Hello, thanks for everybody's hard work on this project. I can confirm that so far all code is working on version 4.09.  :)

Tom

thanks for that info. will add it to the wiki :)
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 April 2014, 16:53:44
Zitat von: willybauss am 03 April 2014, 15:32:12
I can't believe that the formula fits. You have  p50SummerModeHysteresis twice in same formula. I believe one of them should be something like pxxSummerModeValue

I edited my original post, thanks.. p49SummerModeTemp + p50SummerModeHysteresi... it is from the manual.. bad copy and paste

@Markus
IAt fhem-start, it takes some minutes to read all pXX. No alphabetical order, random. Could be that p50 is read immediately and p49 after 4 minutes.
For HC1, I will check this night.

I shouldn´t write code while my children jump on me: it leads to very bad quality :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 April 2014, 16:54:17
hi tom
happy that you got it working

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 April 2014, 17:51:27
Zitat von: immi am 03 April 2014, 16:53:44
@Markus
IAt fhem-start, it takes some minutes to read all pXX. No alphabetical order, random. Could be that p50 is read immediately and p49 after 4 minutes.
For HC1, I will check this night.

yes i know immi but i saw the p49 showing up in the mythzlog while the updates are running after fhem-start. so i was wondering why it wasn't displayed in fhem.
maybe just some mysterious thing ;)

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 April 2014, 19:28:06
v 0.081
bufix summermode
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 April 2014, 21:48:58
Test will follow ob sunday. off to Holiday this Weekend.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 April 2014, 07:09:03
Wiki updated :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 April 2014, 11:28:01
hey immi,

in 0.81 i can see all modes :) thanks.

a suggestion... i was on a short holiday this weekend and i was missing a way to set the THZ manually to the setback mode. on the touchpanel of the heating you can switch between automatic, hand-mode, standby and so on with the arrow-keys. is ist possible to set these modes via fhem, too? =)

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 06 April 2014, 11:38:09
Zitat von: micomat am 06 April 2014, 11:28:01

a suggestion... i was on a short holiday this weekend and i was missing a way to set the THZ manually to the setback mode. on the touchpanel of the heating you can switch between automatic, hand-mode, standby and so on with the arrow-keys. is ist possible to set these modes via fhem, too? =)


this would be a great feature. i set my water-temp to 42°C and when i want to take a bath, i have to set the heatpump to hand-mode (50°C) for approx one hour. this would be more comfortable with a touch on a switch in the bathroom (so my wife can do this too)

i know you can switch the mode via webinterface, but i don't own this device. maybe someone with this device can log the commands?

greetings
Kai
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 April 2014, 11:41:42
if there is a way, i'm sure immi will find it :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 April 2014, 16:39:04
Zitat von: micomat am 06 April 2014, 11:28:01
a suggestion... i was on a short holiday this weekend and i was missing a way to set the THZ manually to the setback mode. on the touchpanel of the heating you can switch between automatic, hand-mode, standby and so on with the arrow-keys. is ist possible to set these modes via fhem, too? =)

@Markus: Up to now, I have not already found this feature. Will see..
@Kai: for what you want, everything is already implemented, I am already using it; do the following
1) buy a button (e.g. enocean) which you can read with fhem
2) call it Button4WIFE or whatever
3) test the status of Button4WIFE: in case of enocean can be "B0" (up) or "BI" (down)
4) use the notify command for changing "Mythz p04DHWsetDay".... something like

define Notify_HotWater4WiFE  notify Button4WIFE {my $rvar=Value("Button4WIFE");; \
if ($rvar =~ m/B0/) {fhem "set Mythz p04DHWsetDay 46"} \
elsif ($rvar =~ m/BI/) {fhem "set Mythz p04DHWsetDay 42"}}



immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 April 2014, 16:53:00
Hi Willy
I cleaned up today the code; this night or tomorrow you shoud update to v0.082, then restart.
After the cleanup (I do not know if the things are related) event-on-change-reading worked well.

pay attention to the following!!

event-on-change-reading blocks all notifies (or logs) for all readings which are not listed.
For the listed readings, the notify (or log) is done only in case of change.


attr Mythz event-on-change-reading allFB,Status_DHW_F3
In this example "history" will never be logged.

Userreadings need the parent reading: e.g. RuecklaufTemp needs also allFB

attr Mythz event-on-change-reading RuecklaufTemp,allFB,Status_DHW_F3,WWTemp,VorlaufTemp


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 April 2014, 20:39:10
immi, what is the read interval of the Status_XXXXX readings and how can i change it? =)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 April 2014, 22:20:26
Markus
you cannot change it before that it is implemented.
I will do it now.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 April 2014, 22:27:37
Great :) thanks
the Reading if Summer/Winter Mode is already Part of my dashboard.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 April 2014, 12:44:56
Zitat von: firebal301 am 06 April 2014, 11:38:09
this would be a great feature. i set my water-temp to 42°C and when i want to take a bath, i have to set the heatpump to hand-mode (50°C) for approx one hour. this would be more comfortable with a touch on a switch in the bathroom (so my wife can do this too)
I have a similar use model but a different solution: since long term planning is not one of my strengths I need an immediately working way of additional dhw heating. So I change the time delay to allow booster usage for dhw from 90 minutes to 0 for an hour.

Are we already able to switch this parameter (P33)? If not: immi ... please ...  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 April 2014, 12:56:28
Zitat von: immi am 06 April 2014, 16:53:00
Hi Willy
I cleaned up today the code; this night or tomorrow you shoud update to v0.082, then restart.
After the cleanup (I do not know if the things are related) event-on-change-reading worked well.

pay attention to the following!!

event-on-change-reading blocks all notifies (or logs) for all readings which are not listed.
For the listed readings, the notify (or log) is done only in case of change.


attr Mythz event-on-change-reading allFB,Status_DHW_F3
In this example "history" will never be logged.

Userreadings need the parent reading: e.g. RuecklaufTemp needs also allFB

attr Mythz event-on-change-reading RuecklaufTemp,allFB,Status_DHW_F3,WWTemp,VorlaufTemp


immi

Hi immi,

I cannot yet imagine what this finally means. Sounds like a lengthy row starting with "attr Mythz event-on-change-reading " followed by a long long list of all readings and userreadings I currently have in my Mythz.log file, right?

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 April 2014, 13:50:49
Zitat von: willybauss am 07 April 2014, 12:56:28
I cannot yet imagine what this finally means. Sounds like a lengthy row starting with "attr Mythz event-on-change-reading " followed by a long long list of all readings and userreadings I currently have in my Mythz.log file, right?
Hi Willy,
if long or short is your decision. I read somewhere that wildcards are allowed (".*"). Have a try.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 07 April 2014, 17:48:13
Zitat von: immi am 06 April 2014, 16:39:04

@Kai: for what you want, everything is already implemented, I am already using it; do the following
1) buy a button (e.g. enocean) which you can read with fhem
2) call it Button4WIFE or whatever
3) test the status of Button4WIFE: in case of enocean can be "B0" (up) or "BI" (down)
4) use the notify command for changing "Mythz p04DHWsetDay".... something like


Hi immi
this is exactly what i need. thanks. until now i do not trust the FHEM-server because i had some issues with logfiles and my raspberry pi quits his job two times. so i am not sure to switch the heatpump-programs to FHEM. You know: never touch a running system :-)

which kind of switch from enocean do you use? does it work good? i am not sure which system i should use? homematic hast nice features...

other issue: i used my own phython-script to write the temperatures from the heatpump to a mysql-db. Now FHEM blocks the RS232-interface. do you know, how i can use your readings and write them to my own mysql-db?

Kai
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 April 2014, 18:45:52
Zitat von: firebal301 am 07 April 2014, 17:48:13
other issue: i used my own phython-script to write the temperatures from the heatpump to a mysql-db. Now FHEM blocks the RS232-interface. do you know, how i can use your readings and write them to my own mysql-db?
Yes, I tested it. The FHEM module name for it is dblog.

Which radio switch to use?
It is a teological question :)
I use enocean because my house was built basing on Eltako (all shutters, lights, thermostats). Enocean (eltako) is quite expensive, but working really well for me.
Search in the forum for Homematic, onewire, or others. I think CUL could be a cheaper solution, if you want only one switch.
If you have a fritzbox, you can also use, a tel number as switch...

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 08:42:09
Zitat von: immi am 06 April 2014, 16:53:00
event-on-change-reading blocks all notifies (or logs) for all readings which are not listed.
For the listed readings, the notify (or log) is done only in case of change.

The longer I think about this the more I believe that it can't help me in solving the "just-one-single-email-in-case-of-failure" topic.
My hope for using event-on-change-reading would have beenBut in fact event-on-change-reading will trigger events all the time, no matter if contents of allFB changes or anything else. So I still have to evaluate manually if  number_of_faults is different from it's previous value.

Now I'll try to use something like

define notify_number_of_faults  notify number_of_faults {my $rvar=Value("number_of_faults");; \
if ($rvar =~ Value("number_of_faults_old")) {[DO-NOTHING]} \
else [SEND-EMAIL]; {fhem "set Mythz number_of_faults_old  Value("number_of_faults") "}}

Will need some fine tuning of course.

Currently I have just limited time to play around with this, so I might have to wait for bad weather to succeed.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 April 2014, 10:00:17
Willy
you asked for bad weather. Here it is  :(

Zitatevent-on-change-reading would trigger an event just in case of changes of number_of_faults
everything else stays as it is, especially all loggings defined by attr Mythz interval_... would still work without any change
It is not how event-on-change-reading has been programmed from the module owner.

why don´t you ask in the forum for help under automation or sonstiges.

Another idea, much easier: before sending the email, set the updateinterval of last10errors to 0.
It will not be updated, and there will be no notify
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 12:36:03
Zitat von: immi am 08 April 2014, 10:00:17
It is not how event-on-change-reading has been programmed from the module owner.
I know. My expectation was just based on a similar named (but differently working) solution in heatpumpMonitor.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 April 2014, 13:18:05
Willi
>>I know. My expectation was just based on a similar named (but differently working) solution in heatpumpMonitor.
HOW?????

I gave you the final solution, Why don´t you like it?
Before sending the email, set the updateinterval of last10errors to 0.
last10errors will not be updated, and there will be no notify and no further email


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 14:39:48
Zitat von: immi am 08 April 2014, 13:18:05
Willi
>>I know. My expectation was just based on a similar named (but differently working) solution in heatpumpMonitor.
HOW? ??? ?
The corresponding solution in heatpumpMonitor looks as follows in heatpumpMonitor.ini:
[Threshold]
# List here all from the heatpump extracted values (seperated by space) about which you want to get an email
# if they change. e.g. I want to get informed if the booster has been used, as this shows that
# something is wrong, as normally the compressor should be enough
thresholdCounters = booster_dhw booster_heating  number_of_faults

# How many queries to the heat pump need to fail in a row to send you a mail?
queryErrorThreshold = 2

Zitat von: immi am 08 April 2014, 13:18:05
I gave you the final solution, Why don´t you like it?
I never sait that I don't like it. If I fail implementing it in same way as described above (like heatpumpMonitor does) I will do it as you suggested.  :)   Advantage of the heatpumpMonitor solution is that it will go on sending emails as soon as further changes occur. So I don't need to restart anything manually after the failure is fixed.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 April 2014, 18:40:55
V0.084
changelog

p.s. if you have a better name for OpMode like Pxx ...

@Markus, as always thanks for testing and updating the wiki

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 08 April 2014, 21:04:06
Hallo,

ich bin neu hier und finde das Projekt echt toll. Ich habe meine THZ 403 SOL per USB angeschlossen und den letzten Stand des Projekts aus dem SVN mit der Beispielkonfiguration aus dem Wiki auf einem Linux-PC installiert.
Leider bekomme ich im Log der "Mythz" ständig nur folgende Ausgaben:

...
2014-04-08_20:58:52 Mythz CONNECTED
2014-04-08_20:58:52 Mythz DISCONNECTED
2014-04-08_20:58:53 Mythz CONNECTED
2014-04-08_20:58:53 Mythz DISCONNECTED
...

Daher folgende Fragen:

1) ist das hier der richtige Ort für solche Fragen? Die Suche im Forum hat sonst nichts ergeben.
2) was mache ich falsch? Ich habe das Ganze auch zuerst seriell probiert, mit demselben Ergebnis, habe das aber auf meine Unfähigkeit beim Löten geschoben.

Vielen Dank

-----

Hello,

I'm new here and really curious of this project. I connected my THZ 403 SOL via USB and installed the latest revision of fhem from SVN using the example configuration from the wiki.
Unfortunately I always get the following lines in my logfile of "Mythz":

...
2014-04-08_20:58:52 Mythz CONNECTED
2014-04-08_20:58:52 Mythz DISCONNECTED
2014-04-08_20:58:53 Mythz CONNECTED
2014-04-08_20:58:53 Mythz DISCONNECTED
...

so I would like to ask 2 questions:

1) is this here the right place for the questions? The search yielded nothing useful.
2) what am doing wrong? I first tried to connect by serial port, but I considered these failures a result of my poor soldering skills.

Thanks in advance
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 April 2014, 21:33:18
hey immi,

thanks for the improvement :) wiki update will follow soon.

@maximalz
welcome to the happy THZ+fhem users ;)

so you don't get anything else than the error message? what kind of software-version do you use?
connecting with USB might be less defective when starting with this topic.
yes, this is the right thread for all your THZ questions.
can you copy your config here, please?

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 08 April 2014, 21:39:08
Hi micomat,

where can I find the software-version of my THZ?

My config is the stock config to which I appended the wiki config. The full config is below.

fhem.cfg
---------------------
attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global motd SecurityCheck:\
\
WEB,WEBphone,WEBtablet has no basicAuth attribute.\
telnetPort has no password/globalpassword attribute.\
\
Restart FHEM for a new check if the problem is fixed,\
or set the global attribute motd to none to supress this message.\

attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global userattr devStateIcon devStateStyle icon sortby webCmd
attr global verbose 3

define telnetPort telnet 7072 global

define WEB FHEMWEB 8083 global

define WEBphone FHEMWEB 8084 global
attr WEBphone stylesheetPrefix smallscreen

define WEBtablet FHEMWEB 8085 global
attr WEBtablet stylesheetPrefix touchpad

# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog

define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log

define eventTypes eventTypes ./log/eventTypes.txt

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create

# THZ 404 SOL
define Mythz THZ /dev/ttyUSB0@115200
attr Mythz room Sysintern

# userReadings
attr Mythz userReadings AussenTemp:allFB {(split ' ',ReadingsVal("Mythz","allFB$

# interval Defintionen
attr Mythz interval_allFB 300
attr Mythz interval_history 28800
attr Mythz interval_last10errors 120

# Definition von file-log und den SVG-Plots einiger Daten
define FileLog_Mythz FileLog ./log/Mythz-%Y-%m.log Mythz
define wal_0 SVG FileLog_Mythz:thz:CURRENT
attr wal_0 room Heizung
define wal_1 SVG FileLog_Mythz:thz1:CURRENT
attr wal_1 room Heizung
define wal_2 SVG FileLog_Mythz:thz2:CURRENT
attr wal_2 room Heizung
define wal_3 SVG FileLog_Mythz:thz3:CURRENT
attr wal_3 room Heizung
define wal_4 SVG FileLog_Mythz:thz4:CURRENT
attr wal_4 room Heizung

# readingsGroup
define rg_thz readingsGroup Mythz:<%temp_outside>,<Aussen>,AussenTemp Mythz:<%s$
attr rg_thz alias Heizung Temperaturen
attr rg_thz group THZ
attr rg_thz room Sysintern
attr rg_thz valueFormat { AussenTemp => '%1.f °C', VorlaufTemp => '%1.f °C', Au$

# Dashboard
define MyDashboard Dashboard
attr MyDashboard dashboard_lockstate unlock
attr MyDashboard dashboard_row top-center
attr MyDashboard dashboard_showhelper 0
attr MyDashboard dashboard_showtooglebuttons 0
attr MyDashboard dashboard_tab1groups THZ
attr MyDashboard dashboard_tab1name micofhem
attr MyDashboard dashboard_tab1sorting t0c100,THZ,true,170,253
attr MyDashboard dashboard_tabcount 1
attr MyDashboard dashboard_webfrontendfilter WEB
define MyDashboard_weblink weblink htmlCode {DashboardAsHtml("MyDashboard")}
attr MyDashboard_weblink room DashboardRoom
---------------------
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 April 2014, 21:48:39
the Software Version should be Displayed somewhere in the Panel in the Heating.
are you sure that the Heating is USB0? you can Check this with lsusb in the Linux console

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 08 April 2014, 21:54:22
When I rebbot the THZ it shows "311-19" for a short time in the display.

The heating is the only USB device connected. lsusb shows

---------------------
root@monitor:/opt/fhem# lsusb
Bus 002 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
---------------------

In fhem-...log I get the following: (sorry, did not look there before)
---------------------
2014.04.08 21:52:26 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.04.08 21:52:26 3: Setting Mythz baudrate to 115200
2014.04.08 21:52:26 1: /dev/ttyUSB0 reappeared (Mythz)
2014.04.08 21:52:27 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.04.08 21:52:27 3: Setting Mythz baudrate to 115200
2014.04.08 21:52:27 1: /dev/ttyUSB0 reappeared (Mythz)
2014.04.08 21:52:28 1: /dev/ttyUSB0 disconnected, waiting to reappear
---------------------
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 April 2014, 21:58:17
hmmm okay can you Check /var/log/messages when Connecting the thz?
the cp201x is the hab Controller in the Heating
you can also try 57600 as the Speed value.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 22:01:37
at Display select:
Menü - Inbetriebnahme- Softwarestand


If you're familiar with Linux you can try the attached script, which was basically my entry to getting answers from THZ.


Additionally please have a look into  http://robert.penz.name/heat-pump-lwz/ (http://robert.penz.name/heat-pump-lwz/)  to understand the basics of THZ communication.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 22:05:45
did you ever try to use this USB port for anything else - does it work? In my case it had been an access right issue. So you could also try if it works as root user.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 08 April 2014, 22:08:25
Thanks a lot, the setting @57600 did it!

After checking the kernel log and supposing

Apr  8 21:42:15 monitor kernel: [ 3210.800014] usb 2-1: reset full-speed USB device number 3 using uhci_hcd
Apr  8 21:42:15 monitor kernel: [ 3210.947452] usb 2-1: cp210x converter now attached to ttyUSB0

are the lines I needed (so it was /dev/ttyUSB0) I tried the 57600 setting and it worked like a charm. Thanks very much!

So now I can tell the SW-version without going three stairs down and up again, it's 4.39 ;)


Now I will go on to port this setup to a RPi. Has anyone successful used the RPi's GPIO for serial communication to the THZ? I've read that the voltage levels could be a problem. Or is USB the better solution for a long-time-setup?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 April 2014, 22:14:36
in the thz the USB is more reliable. the serial is outside ;)
as serial is neandertal Technology i recommend USB.

by the Way: congratulations to the connect
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 22:16:28
 Are you really connected via USB to the heatpump, or do you use a USB-RS232 adapter to connect to serial port of THZ?


I've never tried the GPIO of my Raspi. If your USB-RS232 adapter works on a 'normal' Linux PC that's not a guarantee that it will work on Raspi as well. Here is a copy of my findings, posted months ago in a different forum:
ZitatDie Kommunikation vom RasPi zur Anlage habe ich mit einem USB-RS232 Adapter gelöst, der dann als ttyUSB0 am RasPi sichtbar ist. Treiber brauchts dafür nicht, die sind im Kernel des RasPi bereits drin. ABER: Das Netz ist voll von Berichten über Probleme, denn der RasPi akzeptiert z.B. keine älteren Versionen von FTDI, z.B. den FT232BM Chip. Solche Kabel werden oft billig angeboten - und führen beim RasPi zum Kernel-Crash, sobald man auf sie zugreift. Kabel mit dem neueren FT232R Chip sollen angeblich funktionieren, sind dann auch gleich teurer. Bei mir werkelt ein Kabel mit einem 2303 Chip von Prolific erfolgreich.

Fast vergessen: für das Verzeichnis /dev/ttyUSB0 muss der User schreibrechte haben, sonst klappt das rausschreiben nicht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 April 2014, 22:21:13
Is the new version of THZ already available for download. Update and Restart don't do anything for me. No new parameters. Anyone else with the same issue?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 April 2014, 22:24:21
Willy the internal USB Port of the thz is also just a serial to USB converter cp201x.

the new Version should be online tomorrow.
Update 00_THZ.pm is the cmand to update.
shutdown restart recommended

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 April 2014, 22:27:24
Thanks for the info! Won't be back until Sunday. Guess I have to wait until then. :-\
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 22:27:46
Zitat von: micomat am 08 April 2014, 22:24:21
Willy the internal USB Port of the thz is also just a serial to USB converter cp201x.
... with the small difference that it is not powered by the Raspi, and (assumption) the Raspi doesn't need to use it's USB-RS232 drivers to access it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 April 2014, 22:29:13
Zitat von: houseowner123 am 08 April 2014, 22:27:24
Thanks for the info! Won't be back until Sunday. Guess I have to wait until then. :-\
in case of doubt simply have a look on timestamp of the file 00_THZ.pm or look into it using a text editor. Version is shown in header as usual.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 April 2014, 22:39:20
Thanks willybaus! No new version today but that's ok. Something to look forward to when I get home on the weekend.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 08 April 2014, 22:44:36
Yes, I'm connected directly via USB without RS232-converter, but with a normal PC. My next step would be getting the RS232 from normal PC working, so I'm not forced to manipulate in an area of the THZ, which has high voltage.
Surely, I could implant an USB port into the cover of the main electric area but ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 April 2014, 23:47:40
I have a 3 m long USB cable that, with small manipulations on your THZ, you can feed out via the middle panel without too much bending. It comes out on top. It would be best if you have a RaspberryPi with FHEM server that you can then access remotely via your local network.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 06:38:02
@houseowner, could you please take a picture? so everybody can see how you're cabling is made :)

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 April 2014, 07:36:33
Zitat von: immi am 06 April 2014, 16:53:00
Hi Willy
I cleaned up today the code; this night or tomorrow you shoud update to v0.082, then restart.
I can't find anything else but v0.080 after update and restart.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 07:55:57
willy, wait until today and load 0.084.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 April 2014, 08:02:35
If you are in a hurry :)
https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/00_THZ.pm

@houseowner123, I think you have to setup a VPN.
The only reason I started coding 00_THZ is that I want to control all my home from remote.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 08:46:27
i just downloaded 0.084 :)
working like a charm!

thanks immi!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 April 2014, 10:37:52
Zitat von: micomat am 09 April 2014, 07:55:57
willy, wait until today
ups - I thought today is today ...  :) o.k. obviously I've been a few minutes too early
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 10:40:02
Zitat von: willybauss am 09 April 2014, 10:37:52
ups - I thought today is today ...  :) o.k. obviously I've been a few minutes too early

depends on the time-zone and your day-night-rythm ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 12:57:11
wiki is already updated :)

immi, can we set the refresh interval for the operating mode, too? and for me, the update interval of HC_xxx seems not to work. mine is still updated on restart only. will check again. maybe i just forgot to save after set this attr... ;)

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 April 2014, 13:57:29
Zitat von: micomat am 09 April 2014, 12:57:11
wiki is already updated :)
immi, can we set the refresh interval for the operating mode, too? and for me, the update interval of HC_xxx seems not to work. mine is still updated on restart only. will check again. maybe i just forgot to save after set this attr... ;)
Hi Markus
It could be implemented very easily. The question is if it makes sense.

Dear all
I would like to start a structured discussion.
We have status-parameters (   Status_Sol_16, Status_DHW_F3, Status_HC1_F4, Status_HC2_F5, last10errors, allFB,  firmware) and programmable-parameter (all the others incl. OpMode).
Status Parameters cannot be written in the heatpump.
Maybe we should standardize the names: e.g all names of Status-parameters start with S, all Programmable- start with P...
What do you think?

To my opinion, all status-parameter need a refresh intervall attribute.
Programmable-parameter should be changed with fhem, so they do not need a refresh intervall.
If someone goes in the basement and changes the parameters of the heatpump directly,  a complete refresh of fhem is needed.

please give me feedback
immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 April 2014, 16:01:22
hi immi,

good idea to have S and P values.
but when i think about the P-parameters, i guess they also need a refreshment not to have a problem with old values when they were changed on the THZ it'self. maybe once an hour or so? maybe im also weird in this topic...

all in all 00_THZ has grown to a wonderful tool :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 April 2014, 22:51:19
don't know what's going wrong: a few minutes ago I entered "update" and "shutdown restart" in the web interface as usual, but I'm still on version 0.080.  :-[ Any hint what I'm doing wrong?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 April 2014, 23:25:30
 Hi immi,

having S and P prefixes is a very good idea to give it more structure.

Regarding to P parameters  I'm thinking similar to Markus: I can't ensure that nobody will change parameters manually, especially since I have a 2nd display in my living room. So for my wife it's more easy to change via display instead of using one of these monsterous power consuming and time eating devices named computer  ;) . 

I assume it's possible to get any one of the P parameters updated using "at" commands instead of implementing intervalls for all of them. But this would lead to a huge list of "at" rows due to the high number of P parameters.

So it might be useful to have a kind of interval_allTHZ (= update everything in one shot) or alternatively intervall_EverythingWhatsNotUpdatedElsewhere (= update all values which cannot be updated by one of the other intervall definitions). Who doesn't care about these values doesn't need to define intervals for them, all the other people (like me  ;) ) will have a chance to get the P parameters updated frequently.

If logfile will get too big in this case: Would we have a chance to log just in case of changed values, similar to "event-on-change-reading"?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 10 April 2014, 06:41:26
Zitat von: willybauss am 09 April 2014, 22:51:19
don't know what's going wrong: a few minutes ago I entered "update" and "shutdown restart" in the web interface as usual, but I'm still on version 0.080.  :-[ Any hint what I'm doing wrong?

first try update check. so fhem will provide a list of all modules changed.
then you can also try to update the THZ manually. update 00_THZ.pm
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 April 2014, 08:31:05
I did a reboot of Raspi and now the update works obviously, thanks.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 April 2014, 11:13:17
Zitat von: willybauss am 09 April 2014, 23:25:30
Hi immi,
having S and P prefixes is a very good idea to give it more structure.
.....
So it might be useful to have a kind of interval_allTHZ (= update everything in one shot) or alternatively intervall_EverythingWhatsNotUpdatedElsewhere (= update all values which cannot be updated by one of the other intervall definitions). Who doesn't care about these values doesn't need to define intervals for them, all the other people (like me  ;) ) will have a chance to get the P parameters updated frequently.
A command "refresh-everything" is possible, not hard to implement (both with intervall or AT). You have to pay attention that during the big refresh of 200 parameters fhem performance will be low.
Therefore a fhem restart would have the same impact.
My family uses fhem from 2 years, mainly from  smart-phone. They never go in the basement and touch the heatpump!!

Zitat
If logfile will get too big in this case: Would we have a chance to log just in case of changed values, similar to "event-on-change-reading"?
00_THZ will remain FHEM-mainstream. To my opinion it is working well with dblog and filelog modules. If you want another logging modules, someone has to write it and support it

@Willy 0.080 was very old; in between there have been 3 version; repeat all your tests with the newst version; I made lots of clean-up.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 10 April 2014, 13:36:22
Zitat von: immi am 10 April 2014, 11:13:17
My family uses fhem from 2 years, mainly from  smart-phone. They never go in the basement and touch the heatpump!!

that's what i'm dreaming of ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 April 2014, 19:39:55
v 0.085
changelog
- OpMode readwrite


I want to bring back the conversation to the naming. I want to change them only once.
It costs programming time to me, Doku-time to Marcus and config-time to everyone.

We have decided that the names should be divided between S (status) and P (Programm)
untill now we have the following arguments:

Status_DHW_F3 Status_HC1_F4 Status_HC2_F5 Status_Sol_16 allFB firmware history holidayBegin-time holidayBegin_day holidayBegin_month holidayBegin_year holidayEnd-time holidayEnd_day holidayEnd_month holidayEnd_year last10errors p01RoomTempDayHC1 p01RoomTempDayHC2 p02RoomTempNightHC1 p02RoomTempNightHC2 p03RoomTempStandbyHC1 p03RoomTempStandbyHC2 p04DHWsetDay p05DHWsetNight p07FanStageDay p08FanStageNight p09FanStageStandby p33BoosterTimeoutDHW p37fanstage1-Airflow-inlet p38fanstage2-Airflow-inlet p39fanstage3-Airflow-inlet p40fanstage1-Airflow-outlet p41fanstage2-Airflow-outlet p42fanstage3-Airflow-outlet p49SummerModeTemp p50SummerModeHysteresis p75passiveCooling p79BoosterTimeoutHC p99FanStageParty pOperatingMode party-time programDHW_Fr_0 programDHW_Fr_1 programDHW_Fr_2 programDHW_Mo-Fr_0 programDHW_Mo-Fr_1 programDHW_Mo-Fr_2 programDHW_Mo-So_0 programDHW_Mo-So_1 programDHW_Mo-So_2 programDHW_Mo_0 programDHW_Mo_1 programDHW_Mo_2 programDHW_Sa-So_0 programDHW_Sa-So_1 programDHW_Sa-So_2 programDHW_Sa_0 programDHW_Sa_1 programDHW_Sa_2 programDHW_So_0 programDHW_So_1 programDHW_So_2 programDHW_Th_0 programDHW_Th_1 programDHW_Th_2 programDHW_Tu_0 programDHW_Tu_1 programDHW_Tu_2 programDHW_We_0 programDHW_We_1 programDHW_We_2 programFan_Fr_0 programFan_Fr_1 programFan_Fr_2 programFan_Mo-Fr_0 programFan_Mo-Fr_1 programFan_Mo-Fr_2 programFan_Mo-So_0 programFan_Mo-So_1 programFan_Mo-So_2 programFan_Mo_0 programFan_Mo_1 programFan_Mo_2 programFan_Sa-So_0 programFan_Sa-So_1 programFan_Sa-So_2 programFan_Sa_0 programFan_Sa_1 programFan_Sa_2 programFan_So_0 programFan_So_1 programFan_So_2 programFan_Th_0 programFan_Th_1 programFan_Th_2 programFan_Tu_0 programFan_Tu_1 programFan_Tu_2 programFan_We_0 programFan_We_1 programFan_We_2 programHC1_Fr_0 programHC1_Fr_1 programHC1_Fr_2 programHC1_Mo-Fr_0 programHC1_Mo-Fr_1 programHC1_Mo-Fr_3 programHC1_Mo-So_0 programHC1_Mo-So_1 programHC1_Mo-So_3 programHC1_Mo_0 programHC1_Mo_1 programHC1_Mo_2 programHC1_Sa-So_0 programHC1_Sa-So_1 programHC1_Sa-So_3 programHC1_Sa_0 programHC1_Sa_1 programHC1_Sa_2 programHC1_So_0 programHC1_So_1 programHC1_So_2 programHC1_Th_0 programHC1_Th_1 programHC1_Th_2 programHC1_Tu_0 programHC1_Tu_1 programHC1_Tu_2 programHC1_We_0 programHC1_We_1 programHC1_We_2 programHC2_Fr_0 programHC2_Fr_1 programHC2_Fr_2 programHC2_Mo-Fr_0 programHC2_Mo-Fr_1 programHC2_Mo-Fr_3 programHC2_Mo-So_0 programHC2_Mo-So_1 programHC2_Mo-So_3 programHC2_Mo_0 programHC2_Mo_1 programHC2_Mo_2 programHC2_Sa-So_0 programHC2_Sa-So_1 programHC2_Sa-So_3 programHC2_Sa_0 programHC2_Sa_1 programHC2_Sa_2 programHC2_So_0 programHC2_So_1 programHC2_So_2 programHC2_Th_0 programHC2_Th_1 programHC2_Th_2 programHC2_Tu_0 programHC2_Tu_1 programHC2_Tu_2 programHC2_We_0 programHC2_We_1 programHC2_We_2 timedate

I would appreciate improvements (feedback) in the naming: I would like something more consistent

p_OpMode or pOpmode or pOperatingMode
s_allFB or s_general_FB or status_general_FB or something else
s_DHW_F3 or Status_DHW_F3 or sDHW
programHC2_Tu_2  or p_programHC2_Tu_2  or PprogramHC2_Tu_2
pholidayEnd_month or p_holidayEnd_month
...

thanks
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 April 2014, 23:09:31
immi,

As I understand, the question basically consists of different topics:My answers:That's just my humble opinion. Others migh think different.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 12 April 2014, 16:31:43
Hi immi,

1) Keep it short: P and S are fine with me
2) I like separators "_". Makes reading and also understanding where something ends and begins much easier, especially for newbies like me.
3) Similar to 1) Keep it short but still understandable: p_OpMode would be my choice.
4) s_allFB, s_DHW_F3,  p_programHC2_Tu_2, p_holidayEnd_month

Thanks for all your hard work.  Is op_mode a parameter or a status. Would be great if it was a parameter that one could set remotely. Do I need VPN to accesss FHEM when I am not at home? And where do I need it: on the router or the RPi?

Tom

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 April 2014, 17:45:30
Hi tom
From v0.085 op_mode is readwrite.

p.s. Waiting for some more feedback and then I start to work.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 April 2014, 22:01:46
will answer tomorrow :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 April 2014, 23:29:36
it looks like some parameters exist twice:

P37fanstage1-Airflow-inlet - p37fanstage1-Airflow-inlet
same with P38, P39, P40, P41, P42

P75passiveCooling - p75passiveCooling
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 April 2014, 10:08:30
Hi willy
I have no way to delete the obsolete readings after a name change (version change).
Same question has been made by Markus 4 weeks ago.
You have to delete them manually :(
e.g.
deletereading Mythz P49SummerModeTemp

or you can stop fhem and delete (fully or partially) ./log/fhem.save
or you let fhem crash :)

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 April 2014, 10:59:44
ok, thanks.
deletereading Mythz... will do the job.


Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 April 2014, 09:53:38
i would prefer short acronyms for status and program values.
else the names will become too long.

will add 0.85 info to wiki
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 April 2014, 06:48:47
added 0.085 info to wiki and integrated the configuration example for the fan selector :) thanks for that hint immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: THZ_Haus am 15 April 2014, 18:35:44
Hallo,
super Sache, Kommunikation steht und auch die FHEM Oberfläche funktioniert.

Nun meine Frage:
Können auch die Lüfterstufen geändert werden -> Funktion über dem Bedienpult -> Lüfterstufen-> Ausserplanmäßig u. deren Zeit?

MfG Jens
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 April 2014, 19:48:38
Zitat von: THZ_Haus am 15 April 2014, 18:35:44
Nun meine Frage:
Können auch die Lüfterstufen geändert werden -> Funktion über dem Bedienpult -> Lüfterstufen-> Ausserplanmäßig u. deren Zeit?

Hallo Jens,
freut mich das die Konfiguration geklappt hat.
Schau mal in fhemwiki.de, da findest Du seit heute in der Beispielconfig einen Fan-Selektor ;)

Gruß
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 15 April 2014, 20:00:51
Das ist ganz nett, mit der Lüfterstufenanwahl, allerdings trifft das nicht den Kern der Frage. Ich glaube, es ging um diese Einstellung, die nur eine gewisse Zeit hält.

Ich stelle z.B. auch immer  Lüfterstufen-> Ausserplanmäßig 0 / 60 min. ein, wenn ich Rasen mähe, damit ich mir nicht die Abgase reinziehe.

Gibt es die Einstellung auch irgendwo?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 April 2014, 20:19:24
Ah, verstehe ;)
Nein diese Funktion wurde bislang nicht implementiert.

@immi, this is the "unscheduled ventilation" feature. do you see any chance to implement? or to implement a feature to disable ventilation for X (user defineable) hours?

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 April 2014, 21:42:47
yes Markus,
I could try to search for this useless parameter, and implement it

nevertheless, I am sad that nobody is really using the powerfull features of FHEM like "at"
I cite myself 3 weeks ago

define bbqbegin at 18:00:00 set p07FanStageDay 0
define bbqend at 20:00:00 set p07FanStageDay 1


how easy it is?
A button can be implemented also; "at" is so flexible

switch-off now and after 30 min switch-on

set p07FanStageDay 0
define dreizigminuten  at +00:30:00 set p07FanStageDay 1



immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 April 2014, 07:03:06
good idea :) as i'm not a programmer i won't ever think about the "at" feature.
i will try to configure a button like this.

EDIT
i gave up =( i only can create a button for switching it off with an off;;sleep 120;;on command chain. for more, my perl is too poor.

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: THZ_Haus am 16 April 2014, 07:35:56
Ich stelle z.B. auch immer  Lüfterstufen-> Ausserplanmäßig 0 / 60 min. ein, wenn ich Rasen mähe, damit ich mir nicht die Abgase reinziehe...

-> Jupp genau diese Funktion suche ich, gerade jetzt wo die ersten Osterfeuer angezündet werden, ist diese Funktion wirklich Gold wert.
Nun muß ich immer noch bis unten in den Keller flitzen und die Lüftung abschalten!

-> Zudem wäre es auch Klasse, die Lüftung z.b. in den Pollenflugzeiten zu deaktivieren z.B. zwischen 1.00 bis 3.00 Uhr, gerade für Allergiker wünschenswert.

MFG Jens
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: THZ_Haus am 16 April 2014, 07:37:17
Zitat von: maximalz am 15 April 2014, 20:00:51
Das ist ganz nett, mit der Lüfterstufenanwahl, allerdings trifft das nicht den Kern der Frage. Ich glaube, es ging um diese Einstellung, die nur eine gewisse Zeit hält.

Ich stelle z.B. auch immer  Lüfterstufen-> Ausserplanmäßig 0 / 60 min. ein, wenn ich Rasen mähe, damit ich mir nicht die Abgase reinziehe.

Gibt es die Einstellung auch irgendwo?
Jupp genau diese Funktion meine ich, gerade jetzt wo die Osterfeuer vor der Tür stehen!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: THZ_Haus am 16 April 2014, 07:45:07
Zitat von: micomat am 15 April 2014, 19:48:38
Hallo Jens,
freut mich das die Konfiguration geklappt hat.
Schau mal in fhemwiki.de, da findest Du seit heute in der Beispielconfig einen Fan-Selektor ;)

Gruß
Markus
Super sache, nur bekomme ich das Ventilator zeichen nicht angezeigt?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 April 2014, 08:07:52
taeglich zu einer bestimmten uhrzeit deaktivieren geht via "at", das kann sogar ich ;)

zeig mir mal deine config mit den luefterstufen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 April 2014, 09:39:32
Zitat von: micomat am 16 April 2014, 07:03:06
good idea :) as i'm not a programmer i won't ever think about the "at" feature.
i will try to configure a button like this.
EDIT
i gave up =( i only can create a button for switching it off with an off;;sleep 120;;on command chain. for more, my perl is too poor.

Markus, Do not give up, post what you have done (exact code); someone will help you understand: collective intelligence :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 April 2014, 10:05:17
Zitat von: immi am 15 April 2014, 21:42:47
...
A button can be implemented also; "at" is so flexible
switch-off now and after 30 min switch-on


set p07FanStageDay 0
define dreizigminuten  at +00:30:00 set p07FanStageDay 1

...
Hi immi

Drawback of this solution is, that it relies on FanStageDay to be active for the whole time frame between pressing the button AND end of 'dreizigminuten'. Having a second button for night times doesn't help.
Example:
Assuming that night mode gets active at 22:00 (programmed inside THZ) and I press the button at 21:59 ==> FanStage 0 will be active for just one minute, until the THZ switches to FanStageNight. To work around this potential issue I always have to have all my programmed switches between day and night mode in mind. Since they are different from day to day that's not so easy ...

The requested "unscheduled ventilation" feature doesn't care about any FanStageDay or FanStageNight setting and really keeps the FanStage 0 until defined time is over. Therefore I don't think this parameter is useless.

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 April 2014, 10:31:53
Hi Willy
I am not a programmer; therefore I always start simple, when I write code.
Clearly if you want to make a nice button, you start as I suggested and then increase the complexity.
e.g.
1) you put in a variable p07FanStageDay and p07FanStageNight; which could be different
2) you set them to 0: set p07FanStageDay 0 // set p07FanStageNight 0
3) you give an "at" command setting back the old stage values to the tecalor.


p.s. I am going in a completely other direction. I am going away from all automatic "feature" of tecalor. I want to stop using party time, night mode, holyday mode. FHEM has to take care of it, looking in my calendar or wheater forecast and set THZ accordingly.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 April 2014, 10:41:55
Zitat von: immi am 16 April 2014, 10:31:53
p.s. I am going in a completely other direction. I am going away from all automatic "feature" of tecalor. I want to stop using party time, night mode, holyday mode. FHEM has to take care of it, looking in my calendar or wheater forecast and set THZ accordingly.
sounds intresting :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 April 2014, 11:26:23
Zitat von: immi am 16 April 2014, 10:31:53
Hi Willy
I am not a programmer; therefore I always start simple, when I write code.
Clearly if you want to make a nice button, you start as I suggested and then increase the complexity.
e.g.
1) you put in a variable p07FanStageDay and p07FanStageNight; which could be different
2) you set them to 0: set p07FanStageDay 0 // set p07FanStageNight 0
3) you give an "at" command setting back the old stage values to the tecalor.
Man kann sich auch die Hose mit der Kneifzange anziehen.

Zitat von: immi am 16 April 2014, 10:31:53
p.s. I am going in a completely other direction. I am going away from all automatic "feature" of tecalor. I want to stop using party time, night mode, holyday mode. FHEM has to take care of it, looking in my calendar or wheater forecast and set THZ accordingly.

immi
I'm pretty sure you're the only one here going so consequently into this direction. But it's your module, not the users' one.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 April 2014, 11:29:23
willy, saying phrases in german is not a fair way to communicate...

i'm very intrested in immi's target to have more control on fhem in order to save energy :)
so when i think about my DHW is heated up every morning and a few hours later there is perfect sunshine to do this inseat, i would love to have a configuration which tells the heating not to heat up the water and wait for the sunshine :)

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 April 2014, 11:50:48
Zitat von: willybauss am 16 April 2014, 11:26:23
Man kann sich auch die Hose mit der Kneifzange anziehen.
Hi Willy
if with the sentence you are refering to complexity; trust me, writing the 3 line of code (which I suggested) is much, much more easy than reverse engineer the undocumented unstructured comunication protocol from tecalor.

moreover 00_THZ is a opensource module is not mine; I am only the actual manteiner.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 17 April 2014, 20:21:54
First, let me say once more how deeply I appreciate the work of immi and all co-developers here in the forum. It is us, the unknowing crowd that really draws from your wisdom.
I love the idea of the "at" command, and I have a practical application from which all 303i/304i owner can benefit from. We want to reheat the warm water when it is pretty warm outside because then it the LWZ runs most efficiently. I noticed that I can reach (for my settings) that if the last heating period occurs around 8 PM if the WW temp is 45°C around that time (e.g. somebody has just showered). It the reheat does not occur between 8 and 9 PM then it most likely happens early in the morning when it is pretty cold and the LZW is inefficient. Right now I can circumvent this by setting the OpMode to manual because my set temp in manual mode is 1,5K higher than in automatic mode. But then I need to switch things back.

define reheat at 20:00:00 set OperatingMode Manual
define reheat end at 21:00:00 set OperatingMode Automatic


So, I wonder I can use an if command to check the temp at 8 PM and if the temp is lower than 44°C to initiate the reheat. This would be relevant if somebody has showered at 7 PM the reheat is not needed.

In addition I would only use this of the season mode=winter

How would I implement all this into code language?  8)

Thanks and Happy Easter everyone!
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 April 2014, 20:41:29
Hey
you could read the Commandref Part of the IF command. this could be what youre looking for.
sorry i didnt ever use this in my own so i cannot really help in this matter. but post what you have so we can work in it together.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 17 April 2014, 21:45:27
OK Markus, I give it a beginners try:

define reheat_begin at 20:00:00 IF (Season Mode winter) (IF (WWTemp<=44)) (set OperatingMode Manual) ELSE (set OperatingMode Automatic)
define reheat_end at 21:00:00 IF (OperatingMode Manual)  (set OperatingMode Automatic)


Config file did not complain.  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 April 2014, 21:54:34
tom,

looks quite good to me :) IF it works, perfect!

here is more information about if conditions in at-definitions: http://www.fhemwiki.de/wiki/If-condition
but please be patient, there is a difference between the IF-module and a perl if-function... hard to get, but true :) more about the IF-COMMAND is here http://forum.fhem.de/index.php?topic=17895.0

i'm also working on a more complexe if-at-combination for having an automatic shutdown of the ventialtion with and restart to the last condition before the shutdown. but unfortunately time is what i don't have at the moment ;)

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 17 April 2014, 22:09:56
Irgendwas scheint nicht so richtig zu sein:

Error messages while initializing FHEM:
statefile: reheat_end already defined, delete it first
reheat_start already defined, delete it first

:-[
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 April 2014, 22:15:02
show me the config :)
i will check and read the IF manual tomorrow. i guess there is a declaration error.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 17 April 2014, 22:20:05
Revision (got rid of the error message):

define reheat_begin at *20:00:00 IF (Season Mode winter) (IF (WWTemp<=44)) (set OperatingMode Manual) ELSE (set OperatingMode Automatic)
define reheat_end at *21:00:00 IF (OperatingMode Manual)  (set OperatingMode Automatic)


-but it didn't work either.  :(
I use the sample config from the wiki. I know what is missing: the reference that these commands relate to mythz
And thanks for your offered help, Markus! These parentheses drive me crazy. :-/
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 April 2014, 00:36:20
we will find a way ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 April 2014, 12:01:38


define reheat_begin at *20:00:00 IF (Season Mode winter) (IF (WWTemp<=44)) (set OperatingMode Manual) ELSE (set OperatingMode Automatic)
define reheat_end at *21:00:00 IF (OperatingMode Manual)  (set OperatingMode Automatic)


Hi Tom
do not give up, we get it done.
I am quite far away and the internet connection is bad. I cannot make any tests.
1 hints from me: start easy, without if, then only with one IF....
The syntax should be like this

define reheat_end at *21:00:00 IF ([Mythaz:OperatingMode] eq "Manual") (set Mythz OperatingMode Automatic)


have a look in the reference
http://fhem.de/commandref_DE.html#IF
p.s. Pay attention that OperatingMode is not refreshed automatically. If you change it manually downstairs, you have to read it periodically.

buona pasqua
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 April 2014, 17:15:35
Hi Markus
maybe you have time to update the wiki,
I added one line to the script taking care of the ventilator icon, including offFor60min.


define FanSelectorDay dummy
attr FanSelectorDay group THZ
attr FanSelectorDay setList 0 1 2 3 offFor60min
attr  FanSelectorDay webCmd 0:1:2:3:offFor60min
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageDay notify FanSelectorDay  IF ([FanSelectorDay] eq "offFor60min") (define at_D_offFor60min at +00:59:00 set Mythz p07FanStageDay [Mythz:p07FanStageDay],set Mythz p07FanStageDay 0, setstate FanSelectorDay offFor60min) ELSE (set Mythz p07FanStageDay $EVENT)
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1
attr FanSelectorDay room heatpump



define FanSelectorNight dummy
attr FanSelectorNight group THZ
attr FanSelectorNight setList 0 1 2 3 offFor60min
attr  FanSelectorNight webCmd 0:1:2:3:offFor60min
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p08FanStageNight notify FanSelectorNight IF ([FanSelectorNight] eq "offFor60min") (define at_N_offFor60min at +00:59:00 set Mythz p08FanStageNight [Mythz:p08FanStageNight],set Mythz p08FanStageNight 0, setstate FanSelectorNight offFor60min) ELSE (set Mythz p08FanStageNight $EVENT)
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1
attr FanSelectorNight room heatpump


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 April 2014, 20:59:52
Tried the kings road...

define reheat_start at *20:20:00 IF ([Mythz:SeasonMode]="winter" (IF ([Mythz:WWTemp]<=44.5)) (set Mythz OperatingMode Manual) ELSE (set Mythz OperatingMode Automatic)
define reheat_end at *21:00:00 IF ([Mythz:OperatingMode]="Manual") (set Mythz OperatingMode Automatic)


but didn't work.  :'(  Guess I have to take one of the Ifs out. On a positive note. The association with Mythz however was recognized.

thanks for the 60 min off implementation. Our neighbor likes to burn his trash. So this elegant option will come in handy.  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 April 2014, 21:24:45
mimi, will update this Weekend

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 April 2014, 21:37:33
define reheat_start at *20:20:00 IF ([Mythz:SeasonMode]="winter" (IF ([Mythz:WWTemp]<=44.5)) (set Mythz OperatingMode Manual) ELSE (set Mythz OperatingMode Automatic)
define reheat_end at *21:00:00 IF ([Mythz:OperatingMode]="Manual") (set Mythz OperatingMode Automatic)

some hints:



immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 April 2014, 23:01:10
Success.  :D Figured out the eq. thing before I read immis post:

define reheat_start at *20:00:00 IF ([Mythz:WWTemp]<44.5) (set Mythz OperatingMode Manual) ELSE (set Mythz OperatingMode Automatic)
define reheat_end at *21:00:00 IF ([Mythz:OperatingMode] eq "Manual") (set Mythz OperatingMode Automatic)


Now we start implementing the season mode IF. I have defined it as user reading
attr Mythz userReadings SeasonMode:Status_HC2_F5 {(split ' ',ReadingsVal("Mythz","Status_HC2_F5",0))[13]}
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 April 2014, 10:03:56
Hi Tom
2 questions:

why do you need in the the reheat_start ELSE (set Mythz OperatingMode Automatic) ?
From your description, you are always in auto-mode during the whole day. Less is always better.

Are your issues solved with "InterfaceNotRespondig"? have you tested select(undef, undef, undef, 0.1); ?
I need to know for the next version, if this 100ms delay is necessary or not.

best regards
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 19 April 2014, 12:28:16
Hi immi,

You are right, the ELSE Commando is not needed.
Habe not tested the delay yet. But the log States that the error is still present. Could you be so kind and send a test version of the module with the delay in it. Maybe via PM. Won' be around til Monday.
Best wishes,
  Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 April 2014, 14:29:54
Dear all
please find v0.086: no upload in FHEM-repository (you have to copy the file manually)
In this version the readings names has been standardized
please test it, please keep in mind that:
1) you have to update all your scripts (e.g. search "allFB" and replace "sGlobal"
2) you have to update all your old logs (also here search and replace is needed)
3) you have to delete your obsolete readings manually

Program
p01RoomTempDayHC1 p01RoomTempDayHC2 p02RoomTempNightHC1 p02RoomTempNightHC2 p03RoomTempStandbyHC1 p03RoomTempStandbyHC2 p04DHWsetDay p05DHWsetNight p06DHWsetStandby p07DHWsetManual p07FanStageDay p08FanStageNight p09FanStageStandby p33BoosterTimeoutDHW p37Fanstage1AirflowInlet p38Fanstage2AirflowInlet p39Fanstage3AirflowInlet p40Fanstage1AirflowOutlet p41Fanstage2AirflowOutlet p42Fanstage3AirflowOutlet p43UnschedVent3 p44UnschedVent2 p45UnschedVent1 p46UnschedVent0 p49SummerModeTemp p50SummerModeHysteresis p75passiveCooling p79BoosterTimeoutHC p99FanStageParty pHolidayBeginDay pHolidayBeginMonth pHolidayBeginTime pHolidayBeginYear pHolidayEndDay pHolidayEndMonth pHolidayEndTime pHolidayEndYear pOpMode party-time programDHW_Fr_0 programDHW_Fr_1 programDHW_Fr_2 programDHW_Mo-Fr_0 programDHW_Mo-Fr_1 programDHW_Mo-Fr_2 programDHW_Mo-So_0 programDHW_Mo-So_1 programDHW_Mo-So_2 programDHW_Mo_0 programDHW_Mo_1 programDHW_Mo_2 programDHW_Sa-So_0 programDHW_Sa-So_1 programDHW_Sa-So_2 programDHW_Sa_0 programDHW_Sa_1 programDHW_Sa_2 programDHW_So_0 programDHW_So_1 programDHW_So_2 programDHW_Th_0 programDHW_Th_1 programDHW_Th_2 programDHW_Tu_0 programDHW_Tu_1 programDHW_Tu_2 programDHW_We_0 programDHW_We_1 programDHW_We_2 programFan_Fr_0 programFan_Fr_1 programFan_Fr_2 programFan_Mo-Fr_0 programFan_Mo-Fr_1 programFan_Mo-Fr_2 programFan_Mo-So_0 programFan_Mo-So_1 programFan_Mo-So_2 programFan_Mo_0 programFan_Mo_1 programFan_Mo_2 programFan_Sa-So_0 programFan_Sa-So_1 programFan_Sa-So_2 programFan_Sa_0 programFan_Sa_1 programFan_Sa_2 programFan_So_0 programFan_So_1 programFan_So_2 programFan_Th_0 programFan_Th_1 programFan_Th_2 programFan_Tu_0 programFan_Tu_1 programFan_Tu_2 programFan_We_0 programFan_We_1 programFan_We_2 programHC1_Fr_0 programHC1_Fr_1 programHC1_Fr_2 programHC1_Mo-Fr_0 programHC1_Mo-Fr_1 programHC1_Mo-Fr_3 programHC1_Mo-So_0 programHC1_Mo-So_1 programHC1_Mo-So_3 programHC1_Mo_0 programHC1_Mo_1 programHC1_Mo_2 programHC1_Sa-So_0 programHC1_Sa-So_1 programHC1_Sa-So_3 programHC1_Sa_0 programHC1_Sa_1 programHC1_Sa_2 programHC1_So_0 programHC1_So_1 programHC1_So_2 programHC1_Th_0 programHC1_Th_1 programHC1_Th_2 programHC1_Tu_0 programHC1_Tu_1 programHC1_Tu_2 programHC1_We_0 programHC1_We_1 programHC1_We_2 programHC2_Fr_0 programHC2_Fr_1 programHC2_Fr_2 programHC2_Mo-Fr_0 programHC2_Mo-Fr_1 programHC2_Mo-Fr_3 programHC2_Mo-So_0 programHC2_Mo-So_1 programHC2_Mo-So_3 programHC2_Mo_0 programHC2_Mo_1 programHC2_Mo_2 programHC2_Sa-So_0 programHC2_Sa-So_1 programHC2_Sa-So_3 programHC2_Sa_0 programHC2_Sa_1 programHC2_Sa_2 programHC2_So_0 programHC2_So_1 programHC2_So_2 programHC2_Th_0 programHC2_Th_1 programHC2_Th_2 programHC2_Tu_0 programHC2_Tu_1 programHC2_Tu_2 programHC2_We_0 programHC2_We_1 programHC2_We_2 

status
sDHW sFirmware sGlobal sHC1 sHC2 sHistory sLast10errors sSol sTimedate

In some days, if we do not find any bugs, I will also upload to the repository

p.s. Tom: I added the 100ms delay here; please tell me if you see an improvement
p.s.2 I also added some new features for the others  8)

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 April 2014, 09:26:56
some new features? tell me more =)
i was not at home during the weekend so i will test these days.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 April 2014, 12:29:18
Hi Markus
I have added lots of Pxx


Dear all
here version 0.087
I would like your feedback on the names of the readings.
Rudolf wrote, that there will be a major release in 2 weeks.
We have to speed up. I would like to have a clean 00_THZ for the major release.
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 April 2014, 12:32:54
0.086 was working fine for me :)
will test 0.087 today or tomorrow.

was a lot of work to correct all the readings and so.
do you know if there is a command like "deletereading Mythz *" or so? that could help cleaning up all the old readings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 April 2014, 13:00:48

Hi Markus
no, there is not such a command deletereading Mythz *

I stop fhem and edit ./log/fhem.save (or delete)
then  start

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 April 2014, 14:31:01
okay, i guess i will keep working with deletreading ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 April 2014, 17:17:02
errata http://forum.fhem.de/index.php?topic=14041.0

I still prefer deleting fhem.save
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 April 2014, 17:22:40
thanks :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 22 April 2014, 20:59:38
So, to get this right: We manually have to replace 168 parameters and settings in our logs, otherwise the logs are useless? Most important is the config. I understand that. I don't get the fhem.save and delete reading. How can one use this and why is it risky business?  ;)

So, I compared the old and new parameters and following list contains the list which have changed names. And all these we have to find and replace, right?

old                                           new
p37fanstage1-Airflow-inlet     p37Fanstage1AirflowInlet
p38fanstage2-Airflow-inlet           p38Fanstage2AirflowInlet
p39fanstage3-Airflow-inlet      p39Fanstage3AirflowInlet
p40fanstage1-Airflow-outlet   p40Fanstage1AirflowOutlet
p41fanstage2-Airflow-outlet   p41Fanstage2AirflowOutlet
p42fanstage3-Airflow-outlet   p42Fanstage3AirflowOutlet
holidayBegin-time                   pHolidayBeginDay
holidayBegin_day                   pHolidayBeginMonth
holidayBegin_month                   pHolidayBeginTime
holidayBegin_year                   pHolidayBeginYear
holidayEnd-time                   pHolidayEndDay
holidayEnd_day                           pHolidayEndMonth
holidayEnd_month                   pHolidayEndTime
holidayEnd_year                   pHolidayEndYear
OperatingMode                           pOpMode
Status_DHW_F3                   sDHW
firmware                                   sFirmware
allFB                                           sGlobal
Status_HC1_F4                           sHC1
Status_HC2_F5                           sHC2
history                                   sHistory
last10errors                           sLast10errors
Status_Sol_16                           sSol
timedate                                   sTimedate
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 April 2014, 21:50:52
Hi houseowner123 you got it right;
therefore I am annoying you so much on the topic from some days; I want to standardize only once and make no big change for lots of time... therefore i have not uploaded the new version in the repository
Please give me feedback untill tomorrow or stay with the new names forever :)

I converted all logs in 5 minutes; "vi" is my friend :) maybe you are familiar with other editors.
houseowner123: I do not care of the p** readings; I delete them; I only renamed the s* status settings.

houseowner123: yes outside temp is in sGlobal now; the readings that you see online (not the logs) have to be resetted threfore delete fhem.save or use command
deletereading Mythz *

p.s. please find enclosed v0.088; small bug fix, making the system unstable
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 April 2014, 22:50:55
Zitat von: immi am 22 April 2014, 13:00:48
Hi Markus
no, there is not such a command deletereading Mythz *

I stop fhem and edit ./log/fhem.save (or delete)
then  start

immi
deletereading Mythz .*
shutdown restart

worked well for me. Much less effort than doing it one by one.


Most of the new names are ok, graphs are looking good after rename action. But p07DHWsetManual should be named p11DHWsetManual (p07 is FanStageDay).

And the units of p4*UnschedVent* don't fit. You need to change m³/h against min in your code (row 795 of 00_THZ.pm).

btw: thanks for the easter eggs. Setting the values (duration of each UnschedVent setting) works well, but activating the  UnschedVent modes doesn't work unfortunately. Using the THZ's user interface you just need to change the duration, press OK and exit the menu. Afterwards the fan icon shows up, indicating that the  UnschedVent mode is active.
If I change the duration via fhem the value changes, but the mode isn't getting activated (no fan icon, no change of fan speed). I played around for hours to find out if it needs a sequence of e.g. get ... set ..., but I didn't manage to activate it. Then I noticed that there's an obviously unused addredd 0A056E near the  UnschedVent addresses. I modified the code to be able to read this value, but it didn't change in any way. My next hope was that there's  another OpMode, being activated as soon as you select the  UnschedVent menu, but reading the OpMode value didn't show useable results either. 
So I finally believe that there's e.g. an unknown flag to be set in order to activate  UnschedVent mode. Unfortunaltely I don't have a monitoring capability for the CAN bus, so I don't know how to find it out. Any idea?



And finally I'd like to let you know why I don't want to rely on fhem to do things instead of Tecalor's THZ control. Reason is simply reliability. I'll never ever replace the THZ control with it's double digit year MTBF against a sequence of cheap consumer parts like raspberryPi (using flash card as mass storage), low budget chinese power supply, LAN switch (again with  low budget chinese power supply), PowerLAN-adapters, USB-RS232-adapter etc. My goal is to minimize risk. If I can influence what the THZ does by still relying on its own control I'll do it. But I don't e.g. use fhem switch to manual mode for a while in order to heat up water. If during this period of time one of the affected components dies, or a fhem command of a different unit hangs up for any reason, the THZ will never go back into automatic mode. Worst case I'm on vacation far away from home and can't do anything beside checking how it goes wrong.
Second goal is that the solution doesn't need to rely on myself. If I'm not at home and anything goes wrong it must be enough for my wife to simply remove the RS232 cable from the THZ and the THZ goes on working as if there would never have been a cable. So a service technician can do his job without any problems, no matter if I'm accessible or not.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 April 2014, 23:34:33
Hi Willy
thanks for the feedback
Zitat von: willybauss am 22 April 2014, 22:50:55
Most of the new names are ok, graphs are looking good after rename action. But p07DHWsetManual should be named p11DHWsetManual (p07 is FanStageDay).
I will fix it now; bad coy and paste;
ZitatAnd the units of p4*UnschedVent* don't fit. You need to change m³/h against min in your code (row 795 of 00_THZ.pm).
fixed yesterday in v 0.088 should be clear

Zitat
btw: thanks for the easter eggs. Setting the values (duration of each UnschedVent setting) works well, but activating the  UnschedVent modes doesn't work unfortunately... 
I was aware of it; therefore I did not advertize too much on it. I am fighting on this and on Partytime.
UnschedVent and maybe Partytime are a combination of a flag somewhere and the registers I found.
I have an idea; but quite risky, because I am debugging from VPN. In 2 weeks I will have a look.
p.s. there are many more eggs to find.

Zitat
And finally I'd like to let you know why I don't want to rely on fhem to do things instead of Tecalor's THZ control. Reason is simply reliability.....
reliability, what a bad word.... no I am joking.... I understand what you think and I agree.
The house has to be independent, it has to work without FHEM. I did the same with enocean thermostats, lights and shutters. But I want to be able to schedule automatic events, and fhem is really great for it.
If I lose fhem (e.g. my NAS crashes), no problem I can press the old buttons or if I  am far away I can always call my nice neighbours, which are also taking care of my flowers :)

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 23 April 2014, 00:33:35
After the update I got an error message

Mythz: unknown attribute interval_history. Type 'attr Mythz ?' for a detailed list.
configfile: Mythz: unknown attribute interval_history. Type 'attr Mythz ?' for a detailed list.

list looks like this:
Mythz: unknown attribute ?, choose one of verbose:0,1,2,3,4,5 room group comment alias eventMap userReadings IODev do_not_notify:1,0 ignore:0,1 dummy:1,0 showtime:1,0 loglevel:0,1,2,3,4,5,6 interval_sGlobal:0,60,120,180,300,600,3600,7200,43200,86400 interval_sSol:0,60,120,180,300,600,3600,7200,43200,86400 interval_sDHW:0,60,120,180,300,600,3600,7200,43200,86400 interval_sHC1:0,60,120,180,300,600,3600,7200,43200,86400 interval_sHC2:0,60,120,180,300,600,3600,7200,43200,86400 interval_sHistory:0,3600,7200,28800,43200,86400 interval_sLast10errors:0,3600,7200,28800,43200,86400 event-on-change-reading event-on-update-reading event-min-interval stateFormat devStateIcon devStateStyle icon sort by webCmd

Any ideas, what this means?

immi: The delay did the trick! :) Thanks so much!
love the gradient and the low_end_points for the heating curve. Bivalence point anywhere? ;)

Markus: Please add firmware version 4.09 to the Wiki!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 April 2014, 00:52:28
yes look at the help at the bottom of the 00_thz
instead of interval_history use interval_sHistory
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 23 April 2014, 01:13:53
Thanks, immi! That did it!  8)
Titel: rounding of readings
Beitrag von: Heiner am 23 April 2014, 08:17:48
Hi,

the Software becomes better and better. I am impressed, a great thank you to everyone involved and mainly to Immi.

I try currently to make use of the Outside Temp elsewhere in fhem but THZ is a bit too precise. I like to round the reading for it but have no clue how to do it.

I know how to split out this specific reading (as per WIKI)                        attr Mythz userReadings AussenTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[1]}

and I know that for the readinggroup you do the rounding (as per WIKI)  attr rg_thz valueFormat { AussenTemp => '%1.f °C'}

But how to round already the split oout Reading, to as well record for the log only one digit less, I have no clue, and as well not found anything which works elsewhere in the forum.

Can one of you help here?

Many Thanks.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 April 2014, 09:06:13
immi,

just replaced with 0.088 now fhem is quite poor in performance and my mythz.log shows me:
2014-04-23_09:04:51 Mythz DISCONNECTED
2014-04-23_09:04:59 Mythz CONNECTED
2014-04-23_09:05:00 Mythz DISCONNECTED
2014-04-23_09:05:09 Mythz CONNECTED
2014-04-23_09:05:09 Mythz DISCONNECTED
2014-04-23_09:05:18 Mythz CONNECTED
2014-04-23_09:05:19 Mythz DISCONNECTED


any ideas?

EDIT:
strange... when i change the interval attributes to at-command to get all my data from the THZ, it's back to work :)
Titel: Antw:rounding of readings
Beitrag von: willybauss am 23 April 2014, 10:04:17
Zitat von: Heiner am 23 April 2014, 08:17:48
I try currently to make use of the Outside Temp elsewhere in fhem but THZ is a bit too precise. I like to round the reading for it but have no clue how to do it.
Possibly you could try to use outside_tempFiltered instead - value no. 69 of sGlobal. Difference to outside_temp can be seen in attached screen shot.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 April 2014, 14:17:39
Zitat von: immi am 22 April 2014, 21:50:52
... please find enclosed v0.088; small bug fix, making the system unstable
immi
question: after update to 0.086 I had twice an issue with missing entries in THZ-log for hours. shutdown restart solved both issues. Is this the instability you mentioned above?


Since Markus has obviously different issues using 0.088 I'll wait before I update again.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 April 2014, 16:43:01
I should not try to do 3 things at once.
1) I changed the names.
2) I fixed the sync problem for Tom(firmware 4.09): added a delay of 100ms
3) I enabled the possibility to change an attribute, and make it effective without restarting fhem.

The 3) is affecting the connect/disconnect (indirect connection with ser2net) issue drammatically.
In the meanwhile after every change restart fhem!!!
In v 0.089 should be better.

I uploaded v0.089 in the repository now.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 April 2014, 17:25:51
okay so i will update the Wiki tomorrow :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 April 2014, 21:53:32
Zitat von: immi am 22 April 2014, 23:34:33
there are many more eggs to find.
after having compared v0.085 vs. v0.086 the differences in parameters are
p46UnschedVent0
p45UnschedVent1
p44UnschedVent2
p43UnschedVent3
p07DHWsetManual
p06DHWsetStandby
Titel: Antw:rounding of readings
Beitrag von: immi am 23 April 2014, 22:34:22
Zitat von: Heiner am 23 April 2014, 08:17:48


I know how to split out this specific reading (as per WIKI)                        attr Mythz userReadings AussenTemp {(split ' ',ReadingsVal("Mythz","allFB",0))[1]}

and I know that for the readinggroup you do the rounding (as per WIKI)  attr rg_thz valueFormat { AussenTemp => '%1.f °C'}

But how to round already the split oout Reading, to as well record for the log only one digit less, I have no clue, and as well not found anything which works elsewhere in the forum.

Hi Heiner
%1.f doesn't properly round; it deletes the decimal
you can use it like this
attr Mythz userReadings outTemp0dec { sprintf('%1.f ',   ((split ' ',ReadingsVal("Mythz","sGlobal",0))[1]) ) }

sfprint is very powerfull in perl
http://www.perlmonks.org/?node_id=20519

immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 09:14:41
hi immi,

installes 0.089 and have a question regarding a reading:

sHC1
outsideTemp: 12.6 x08: 51.3 returnTemp: 28.9 integralHeat: 1 flowTemp: 28 heatSetTemp: 26.8 heatTemp: 28.6 seasonMode: winter integralSwitch: 100 opMode: setback roomSetTemp: 20.5

sHC2
outsideTemp: 12.7 returnTemp: 31 vorlaufTemp: -60 heatSetTemp: 33.4 heatTemp: 31 stellgroesse: -100 seasonMode: winter opMode: normal

2014-04-24 09:06:24


pOpMode shows me automatic
opMode in HC1 is setback? is that meanig, that the time-range definied is in setback mode for HC1 this time?

opMode in HC2 is normal as i dont use HC2 so there is no time-range defined?

EDIT:
do you see any chance to read the heat recovery values, too? =) that would be great!

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 April 2014, 11:41:35
Hi Markus
I cannot reproduce it, because I am ( and want to be) in standby untill sunday (not at home).

FYI: opMode in sHCx and pOpMode are different. I start to think that 3 different guys worked on the firmware of the heatpump and never spoke with another.

pOpMode  ("1" =>"standby", "11" => "automatic", "3" =>"DAYmode", "4" =>"setback", "5" =>"DHWmode", "14" =>"manual", "0" =>"emergency");   

opMode in sHCx   ("1" =>"normal", "2" => "setback", "3" =>"standby", "4" =>"restart", "5" =>"restart");


How the two are connected and if HC1 or HC2 should be different. No Idea.
With time we will understand it.

You ask about heat recovery values: do you mean actualPower_Qc:  actualPower_Pel: from sGlobal?
Could you be more specific? Like where are described on the manual?

p.s. when you update the wiki please do not forget offFor60min with the new png
http://forum.fhem.de/index.php/topic,13132.msg160381.html#msg160381

best regards
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 24 April 2014, 16:27:09
Immi,

I think Markus want the values for the amount of heat that is recycled through the heat exchange (WRG in German). There is battery of actual values and summary values of them relating to the amounts of energy produced. These reading would be cool to have.
I would love to have P70 - bivalance point as parameter. :)

Can we get the most current 00_THZ.pm updates through the regular "update" command again?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 19:12:15
hi Tom
0,089 can get via update. should be the latest :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 April 2014, 19:13:07
still not clear WGR?, I will have a look.

@Tom do you mean p78dualMode?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 20:08:03
in german it is Wärmerückgewinnung. it's a kilowatthours value which shows you how much energy was recycled from the heat exchanger :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 20:35:58
wiki updated. please report any errors. i have less time this week ;)

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 20:55:53
okay, i have again the problem with summer mode.
sHC1 tells me summer

outsideTemp: 12.5 x08: 21.5 returnTemp: 21.7 integralHeat: 0 flowTemp: 22.5 heatSetTemp: 25.8 heatTemp: 21.8 seasonMode: summer integralSwitch: 100 opMode: normal roomSetTemp: 21

but 12.5°C is out of summer range ;)
p49SummerModeTemp

17.5 °C

p50SummerModeHysteresis

1 K
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 April 2014, 21:17:28
Zitat von: micomat am 24 April 2014, 20:55:53
okay, i have again the problem with summer mode.
sHC1 tells me summer

outsideTemp: 12.5 x08: 21.5 returnTemp: 21.7 integralHeat: 0 flowTemp: 22.5 heatSetTemp: 25.8 heatTemp: 21.8 seasonMode: summer integralSwitch: 100 opMode: normal roomSetTemp: 21

but 12.5°C is out of summer range ;)
p49SummerModeTemp

17.5 °C

p50SummerModeHysteresis

1 K


Hi Markus
I understood. Your faulure is a feature, not a bug :)
The p49SummerModeTemp refers to outside_tempFiltered.
please confirm
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 24 April 2014, 21:29:44
Hi Markus,

this is a different summer mode and refers the number of pump cycles. If the threshold for p49 + p50 hysteresis is met, then the pump tries then the LWZ only attempts to use the min number of pump cycles. You can find it under "Fachmann" --> Pumpzyklen.

And can you add version 4.09 to the wiki, please! :)

@immi: since the manual update I have the following problem:
2014-04-24 21:34:10 Global global update get http://fhem.de/fhemupdate4/svn/FHEM/00_THZ.pm
2014-04-24 21:34:11 Global global update Can't write ./FHEM/00_THZ.pm: Permission denied


What can I do get updates again? I want new readings too! :-\

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 21:58:43
@immi, i will check this with the filtered outside temp :)

@tom, i also guess that in summer mode the heating circles should be disabled... that is what i know from other heatings. even if the circles are open, the heatpump should not heat them up.

the update promlem is a permission problem. you have two options:
1. delete the manually updated version of 00_THZ.pm and then update again
2. change the owner to fhem:dialout or the permission to 666 (sudo chown fhem:dialout 00_THZ.pm or sudo chmod ogu+rw 00_THZ.pm) and then update again.

will add 4.09 to the wiki next minutes

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 April 2014, 22:11:20
Hi Markus and tom
v0.090 uploaded; tomorrow you can update.
changelog
-->p78DualModePoint implemented (Bivalenzpunkt)
-->4 more readings with preliminary names s0A03AE s0A03AF s0A03B0 s0A03B1

I hope that they have something to do with your Wärmerückgewinnung.
Check the values and tell me:
1) new names for s0A03AE s0A03AF s0A03B0 s0A03B1 (something like sRecoverxxxx)
2) do we need a normalization (time 10, or time 100, or time 128....)
3) tell me the unit for the parameters.

p.s. Tom you are mixing up: p49 + p50 is not connected directly with pumpcycles. There are another parameters for the pumpcycles. Please let Markus confirm my hypothesis
   
if outside_tempFiltered > p49SummerModeTemp + p50SummerModeHysteresis ---> Summermode
if outside_tempFiltered < p49SummerModeTemp - p50SummerModeHysteresis ---> Wintermode


enjoy
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 April 2014, 22:17:14
hey imm :)
thats awesome! thanks a lot! i wonder what the dualModePoint is   ???
will check the new values this weekend.

just finished updating the wiki. i have now changed to the "new" parameter and value names.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 April 2014, 00:26:22
immi,

you are fast! Can't wait to see the update with the Bivalenzpunkt and WRG values - You are right about pump cycle temps. They are different from summer mode..at least that's what the manual says

markus: thanks for the Wiki update and the tip with the THZ update error. Ended up deleting the file.
             As far as I understand the system...even though it is summer there is at least one cycle per day where the water in the heating circuits is moved around. It is ever turn off, even in DWHmode and sumer mode. In winter mode the system goes back to the max. number of pump cycles per day (i think 52)

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 April 2014, 01:24:03
Hi Tom
If you plot it, it is clear.
--in black the pump cycles,
--blue if in wintermode
gind enclosed a gplot example
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 April 2014, 08:40:48
different behavior of pump cycles in winter mode and summer mode can be seen in attached screen dump, visualized by flow and return temperatures (pink and brown curves). As you can see: as long as outside_temp_filtered (blue curve) is low enough there are lots of pump cycles (e.g. between 5:00 and 8:00 am); as soon as  outside_temp_filtered gets higher the cycles are interrupted (after 10:00 am).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 April 2014, 09:27:31
hi immi,

thanks for the new values, unfortunately i cannot identify them. they do not fit on any of the values i'm looking for.
i was studying the englisch manual for the heating and found a better wording for the things i'm searching.
you can find them under "Actual Values" on the bottom. in englisch they are named like "Heat M Recovery Day", Heat M Recovery TTL, Heat M Boost, ... there are 8 "Heat M ..." values which shows you the heat recovery.

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 April 2014, 12:20:23
Hi immi,

Can you provide a few more decimals after the comma for AF and B1 values?
I think AF is WM WRG Tag in kWh and B1 is WM WRG Sum in MWh.

For the other 2... No clue yet.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 April 2014, 12:26:28
Zitat von: houseowner123 am 25 April 2014, 12:20:23
I think AF is WM WRG Tag in kWh and B1 is WM WRG Sum in MWh.
would fit to my setup, too
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 April 2014, 12:45:26
Zitat von: micomat am 25 April 2014, 12:26:28
would fit to my setup, too

Cool! 8)

This would be "heat quantity recovered per day" and "heat quantity covered total" ?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 April 2014, 13:45:11
this would be too easy,
I expect something more "confusing" from the creative heatpump developer

something like
heat quantity recovered per day = s0A03AE + 1000 * s0A03AF in Wh
or the opposite

heat quantity recovered total = s0A03B0 +1000 * s0A03B1 in kWh
or the opposite

p.s. use your mind, but do not search for something logical :)
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 April 2014, 15:02:05
oh my god is it really so strange???
i checked the 4 new values but they didn't change the whole day while the values in "actual values" so i guess there are decimal points missing or these are some different information ;)

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 April 2014, 20:12:03
Zitat von: micomat am 25 April 2014, 15:02:05
oh my god is it really so strange???
i checked the 4 new values but they didn't change the whole day while the values in "actual values" so i guess there are decimal points missing or these are some different information ;)

markus
Hi Markus,

Follwing immi's explaination for weird clues: Is it possible that AE and B0 are the decimals after the comma? Can you check this with your actual WRG readings since I am not home until tomorrow. So, WRG Total would be B1 before the comma, B0 after the comma.
Not sure why WRG Day won't change at all but on the other hand of the heat pump for the circuits is off, then no produced heat is recycled.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 25 April 2014, 22:18:11
Hi Tom,

can check on Sunday ;) But i cannot remember that the read values fit to any of my values in the THZ.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 27 April 2014, 10:08:05
Hi, since the last update where the reading names have changed, I still see the old values !!! How can I remove them?

For example "allFB" is now "sGlobal" which is fine and works, however I still see the reading "allFB" with old data.

shutdown restart does not help
rereadcfg does not help
deleting fhem.save does not help
replacing fhem.save with a empty file does not help

What can I do to get really allFB away?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 April 2014, 10:21:45
hi heiner,

just use "deletreading Mythz allFB" and similar for all old readings :)
u can also use "deletereading Mythz *" to delete all actual readings.

cheers,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 April 2014, 10:54:46
Zitat von: Heiner am 27 April 2014, 10:08:05
deleting fhem.save does not help
Hi Heiner
deleting fhem.save does not help if fhem is running.
You have to stop it, delete fhem.save and start it.

I explain you what happens: When fhem is shutting down, it saves all readings in fhem.save for next time you start up.

Nevertheless "deletereading Mythz *" is much more confortable.

Hi Markus
thanks for updating the wikis
immi



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 27 April 2014, 15:04:39
Zitat von: micomat am 25 April 2014, 22:18:11
Hi Tom,

can check on Sunday ;) But i cannot remember that the read values fit to any of my values in the THZ.

Markus

Hi Markus,

the values of the new parameters only change upon server restart. While s0A03AF and s0A03B1 are unchanged (maybe the suspected summary values), the other two parameters do change. s0A03B0 is higher then on Friday (170--->177) but the other one went down (297-->116)
I can't make any sense out of them and I think it need combined observations of some users to get behind these miracle readings.

I don't know if this is old news to everyone but I made some sense out of the rvu-release reading in sGlobal. It refers to the dictated power-off time of the local energy supplier (Sperrzeiten). To get a disc out on your price/kWh I signed a contract where our grid owner Vattenfall can remove the power for up to 4 hours. Most of the time it is no problem but if there are back-to-back shower activities...the water is ice-cold. With this reading you already know before you stand in the shower why you can expect! ;)
Here is the screen shot:

(http://www.fotos-hochladen.net/uploads/screenshot201h35qv0ofsk.png) (http://www.fotos-hochladen.net)

Question: Instead of showing the "non-Sperrzeiten" I would like to display the reverse: the real Sperrzeiten, when rvu release value is 0 and not the default 1. How can change the scale of reading? Any idea anyone?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 April 2014, 17:47:59
Hi Tom
in gplot, you have something like this, I suppose

#FileLog 51:Mythz.sGlobal\x3a::
plot "<IN>" using 1:2 axes x1y2 title 'rvuRelease' ls l0 lw 2 with lines


where "FileLog 51" is the word position 51 in logfile.
if you want "not rvuRelease" use "1-$fld[50]"


#FileLog 51:Mythz.sGlobal\x3a::1-$fld[50]
plot "<IN>" using 1:2 axes x1y2 title 'rvuRelease' ls l0 lw 2 with lines


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 April 2014, 22:28:13
Dear all
I uploaded v 0.092
changelog
--> implemented sHeatRecoveredDay and sHeatRecoveredTotal (incl. interval)
as explained
http://forum.fhem.de/index.php/topic,13132.msg162483.html#msg162483 (http://forum.fhem.de/index.php/topic,13132.msg162483.html#msg162483)
I returned home this night and confirmed the hypothesis; for me is working
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 April 2014, 22:38:44
Great :) thanks again!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 28 April 2014, 00:25:57
Awesome, Immi  8)
The plot now works as desired. :)
Excited to check out the new version with the WRGs. Where you found those parameters, there should be more like actual heat produced for the circuits and the water, also per day and as total. Would be great to have those. Won't recover that much more heat because of the "Sommerkassette" which I will put in this week.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 April 2014, 06:35:34
sounds like i have to test this new parameter today :)

EDIT:
working like a charm :)
thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 April 2014, 19:04:41
I am starting to collect lots of data from THZ.pm
I am trying to understand better the heatpump: therefore I looked at the relation between HCx_heat-set_temp as f(Outside_tempFiltered).
I made some fitting and came to the following preliminary results.
Negletcting the FLOW-Proportion parameter and RoomInfluence parameter

HCx_heat-set_temp: =  a  + b * Outside_tempFiltered +  c * Outside_tempFiltered^2
where
a=1,5 + wantedRoomTemperature * 1,3
b=-10 * p13GradientHC1 / wantedRoomTemperature
c=-0,01


please feel free to contribute to the discussion.
find enclosed the fitted data
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 April 2014, 20:14:48
okay, i'm not completely sure what you're targeting. more efficiency? energy saving? or just something to play around? :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 April 2014, 20:31:41
Zitat von: micomat am 29 April 2014, 20:14:48
okay, i'm not completely sure what you're targeting. more efficiency? energy saving? or just something to play around? :)
I cannot tell you now ... I want the big picture
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 April 2014, 20:37:50
okay :) i can wait
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 April 2014, 21:57:19
There's an additive offset in heatSetTemp when THZ switches between winter and summer mode.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 April 2014, 10:50:51
Hi Willi
thanks for the hint:
can you see it from logfiles the offset SOmmer/Winter ?

p.s. nice plot

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 April 2014, 10:53:06
added 0.091 info to wiki
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 April 2014, 15:19:51
Zitat von: immi am 30 April 2014, 10:50:51
Hi Willi
thanks for the hint:
can you see it from logfiles the offset SOmmer/Winter ?

p.s. nice plot

immi
Don't understand the question. All values shown in the plots are comming out of Mythz.log. So if the plot shows a bump, this bump is also avl. in the logged data of course.

I'm not aware of a THZ parameter defining a bump of xy°C when switching between summer and winter mode.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 30 April 2014, 16:38:18
Zitat von: immi am 29 April 2014, 19:04:41
I am starting to collect lots of data from THZ.pm
I am trying to understand better the heatpump: therefore I looked at the relation between HCx_heat-set_temp as f(Outside_tempFiltered).
I made some fitting and came to the following preliminary results.
Negletcting the FLOW-Proportion parameter and RoomInfluence parameter

HCx_heat-set_temp: =  a  + b * Outside_tempFiltered +  c * Outside_tempFiltered^2
where
a=1,5 + wantedRoomTemperature * 1,3
b=-10 * p13GradientHC1 / wantedRoomTemperature
c=-0,01


please feel free to contribute to the discussion.
find enclosed the fitted data
immi

Hi immi,

1. I find it useful to understand how LWZ/THZ works. The more we know, the better we recognize when something is out of the ordenary.
2. I misss in your equation the foot point. I am assuming it is the 1,5 value which defines a
3. Room influence could look like this (wanted_roomtemp/measured_roomtemp). This factor would come as additional parameter into b and c
4. What does "Fireplace" Kamin do? Temperature- or only ventilation-related?
5. Suggestion: Heating curve settings change dramatically between 0-10°C and -10°-0°C outside temp range. With parameters we already have, only could implement 2 different heatcurves, based on these ranges?
6. Is there another way to get actual room temperature feedback into mythz from another module? I don't want to by FEZ. But I use my fireplace quite often during winter time and I hate to see the THZ working hard at night, when it is already 25°C in house.

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 April 2014, 17:07:23
Zitat von: willybauss am 30 April 2014, 15:19:51
Don't understand the question. All values shown in the plots are comming out of Mythz.log. So if the plot shows a bump, this bump is also avl. in the logged data of course.
I'm not aware of a THZ parameter defining a bump of xy°C when switching between summer and winter mode.
I wanted to know if you could estimate the bump: 5°K 10°K.... I am always in summermode
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 April 2014, 17:34:10
Hi Tom
Zitat2. I misss in your equation the foot point. I am assuming it is the 1,5 value which defines a
1.5 is not foot point; it came from the interpolation of the 3 curves; at the time, my footpoit is 0; For footpoint, I assume a vertical offset; but not tested.
Zitat3. Room influence could look like this (wanted_roomtemp/measured_roomtemp). This factor would come as additional parameter into b and c
I neglected it, in order to reduce the unknons. If you have time, take your logged data and fit some curves. It would be helpfull.
Zitat4. What does "Fireplace" Kamin do? Temperature- or only ventilation-related?
I have no idea, I expect only vent.
5. Suggestion: Heating curve settings change dramatically between 0-10°C and -10°-0°C outside temp range. With parameters we already have, only could implement 2 different heatcurves, based on these ranges?
I try to use a simple model with no anomaly (discontinuity); otherwise further optimization will need numerical methods hard to use.
Zitat6. Is there another way to get actual room temperature feedback into mythz from another module? I don't want to by FEZ. But I use my fireplace quite often during winter time and I hate to see the THZ working hard at night, when it is already 25°C in house.
Sure: I have enocean thermostate in each room; you can use other sensors supported by fhem.
At the beginning I used  "Notify" on a threshold of the thermostate read by FHEM.
Then I disabled it, because when the thermostate detects the temp-increase (ca 20 min after fireplace heating), it is too late.
I want to change the  pXX-values 2 hours before settig fire to the fireplace.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 April 2014, 18:38:05
Thermostat? what Thermostat do you use?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 April 2014, 20:09:04
Hi Markus
one ThermokonSR04 per room
http://www.thermokon.de/EN/easysens-31/sr04--room-sensors-and-operating-units-temperature.html

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 April 2014, 22:18:03
and you can read them with fhem?
i'm thinking about the new homematic thermostat in combination with an actuator instead of my "dumb" thermostats.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 April 2014, 22:50:08
Zitat von: houseowner123 am 30 April 2014, 16:38:18
6. Is there another way to get actual room temperature feedback into mythz from another module? I don't want to by FEZ. But I use my fireplace quite often during winter time and I hate to see the THZ working hard at night, when it is already 25°C in house.
Simply check the installation manual  (can be downloaded from tecalor) on how to install an external sensor. See attached screen dump. Order a cheap PT1000 and some cable, install it, use it.


Using this one instead of fhem driven thermo sensors will keep the THZ's reliability even in case of server defects, SW issues etc. as already stated a few days ago.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 April 2014, 22:58:51
Zitat von: immi am 30 April 2014, 17:07:23
I wanted to know if you could estimate the bump: 5°K 10°K.... I am always in summermode
immi
bump is not always same, but always in the range of 1.2 ... 1.5°C.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 April 2014, 23:44:03
Zitat von: micomat am 30 April 2014, 22:18:03
and you can read them with fhem?
i'm thinking about the new homematic thermostat in combination with an actuator instead of my "dumb" thermostats.
I use the enocean thermostates to control the temperature in each room, without FHEM and THZ; I have additional actuators for each room.

Enocean is supported in fhem
In parallel, I read all my thermostates for monitoring in FHEM, as you see in pdf attached in my previous post « Antwort #399 am: Heute um 20:09:04 »

If FHEM crashes nothing happens; It just stops monitoring.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Mai 2014, 00:30:09
Zitat von: willybauss am 30 April 2014, 22:58:51
bump is not always same, but always in the range of 1.2 ... 1.5°C.
strange I expected more

one more thing...
I uploaded V0.093 tomorrow you can update..
changelog:

I added a plot of the quadratic curve neglecting summer/winter, FLOW-Proportion parameter and RoomInfluence parameter.
Using your settings of HC1, it computes the curve. The actual value is shown in red.
Look at the picture below.
you can test the plot like this:


define wl_hr2 weblink htmlCode <div class="SVGplot"><embed src="/fhem/THZ_PrintcurveSVG/" type="image/svg+xml"  name="wl_hr2"/></div> <a href="/fhem?detail=wl_hr2">wl_hr2</a><br>
attr wl_hr2 room heatpump


p.s. please Markus do not document in the wik this versioni; I do not know if I will leave the plot in  future version.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 01 Mai 2014, 09:37:34
intresting :) will test this during the weekend.
thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Mai 2014, 10:41:35
Zitat von: immi am 30 April 2014, 23:44:03
If FHEM crashes nothing happens; It just stops monitoring.
of course. But that was not the question, where my answer relates to. The question was
Zitat von: houseowner123 am 30 April 2014, 16:38:18
6. Is there another way to get actual room temperature feedback into mythz from another module? I don't want to by FEZ. But I use my fireplace quite often during winter time and I hate to see the THZ working hard at night, when it is already 25°C in house.
Getting feedback into the THZ without the risk of crashing FHEM is just possible with direct connection of room temperature sensor to the THZ, without any connection to fhem.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Mai 2014, 10:46:15
Zitat von: immi am 01 Mai 2014, 00:30:09
strange I expected more


you can check yourself. e.g.

set  p49SummerModeTemp 0
is your friend.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Mai 2014, 11:43:51
Zitat von: willybauss am 01 Mai 2014, 10:46:15
you can check yourself. e.g.
set  p49SummerModeTemp 0
is your friend.
Hi Willy
just tried
in order to swithch from sommer to winter mode now
set  Mythz p49SummerModeTemp 23
in order to swithch back from winter to sommer mode mode now
set  Mythz p49SummerModeTemp 13
the offset is actually very small 0.6° now for my settings and current outside temp.. You got 1.2°.
This means that it is not a simple linear vertical offset, but is depending on may other parameters.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Mai 2014, 20:40:47
what I do not understand at all is an obvious relation between heatSetTemp and inside humidity, see attachment. I observe such bumps in the heatSetTemp curve frequently.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Mai 2014, 22:29:20
Hi Willy
I do not have a hum-sensor directly on the heatpump, therefore I cannot reproduce it.
There shouln'd be a link between the two parameters.
Therefore I suggest to check in the logfiles, if something strange happens at this very time.
Morever look that your .gplot is parsing the right parameter at this particular time, and not something similar which matches the regular expression you defined.
Are the bump periodical or random? If periodical search for something which is triggered with the same freq.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Mai 2014, 23:13:15
Zitat von: immi am 01 Mai 2014, 22:29:20
Hi Willy
I do not have a hum-sensor directly on the heatpump, therefore I cannot reproduce it.
There shouln'd be a link between the two parameters.
Therefore I suggest to check in the logfiles, if something strange happens at this very time.
Morever look that your .gplot is parsing the right parameter at this particular time, and not something similar which matches the regular expression you defined.
Are the bump periodical or random? If periodical search for something which is triggered with the same freq.
immi
I agree, there shouldn't be a link between them, but anyway it is. Nothing strange observed. .gplot checked, right values parsed. Bumps are not periodical, but always fit to bumps in the humidity curve, which are usually caused by e.g. cooking. Neither outside_temp_filtered nor inside_temp (the expected contributors for heating curve calculation) show such bumps at the same point in time, therefore I don't see another reason but humidity bump as root cause of the bump in heatSetTemp.

Might be a bug in the THZ firmware.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Mai 2014, 06:25:52
you can try to reproduce it :) just breath upon the sensor. for me a link between those parameter is senseless.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 07:18:08
Zitat von: willybauss am 30 April 2014, 22:50:08
Simply check the installation manual  (can be downloaded from tecalor) on how to install an external sensor. See attached screen dump. Order a cheap PT1000 and some cable, install it, use it.


Using this one instead of fhem driven thermo sensors will keep the THZ's reliability even in case of server defects, SW issues etc. as already stated a few days ago.

Thanks, willybaus! PT1000 is ordered and will be connected this weekend if time permits. I think it is great idea. I was not aware that a separate external sensor could be connected. I wonder why Stiebel Eltron does no offer this option as a default (e.g. if you want a reference room).

Thinking further: is is possble to use integrated sensor for this input which itself receives thermal input from the two levels of the house?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 07:29:22
Zitat von: immi am 30 April 2014, 17:34:10
I try to use a simple model with no anomaly (discontinuity); otherwise further optimization will need numerical methods hard to use.Sure: I have enocean thermostate in each room; you can use other sensors supported by fhem.
At the beginning I used  "Notify" on a threshold of the thermostate read by FHEM.
Then I disabled it, because when the thermostate detects the temp-increase (ca 20 min after fireplace heating), it is too late.
I want to change the  pXX-values 2 hours before settig fire to the fireplace.

immi

Couldn't you set the HC1 desired temp to so lower bogus temp (as manual setting) to prevent heat activity. The only drawback that I have observed in the past: every time I temper with the heat curve for the first day, the used energy is higher than before. The seond day usually looks better. But that was before fhem monitoring. ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 Mai 2014, 09:31:03
Zitat von: houseowner123 am 02 Mai 2014, 07:18:08
Thinking further: is is possble to use integrated sensor for this input which itself receives thermal input from the two levels of the house?
Sorry, don't understand what you mean. Did you check the related section of the THZ installation manual?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Mai 2014, 09:52:15
You know Willy, what I find strange looking at your plot: it is not only a bump.

As you see there is an increase (in the humidity) and a very very rapid decrease (down).
look in the picture.
And I know humidity sensor can go up up fast (example shower or cooking) but never saw one going down so dramatically fast, reaching a point even lower than average before.
You can achieve such an effect only opening all windows in winter with -20°C super dry outside.
Something is wrong here

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Mai 2014, 11:19:24
that looks like a heartbeat on a cardiogram  ;D
willi, did you connect your ECG(EKG) to the heatpump?

SCNR  ;D
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 Mai 2014, 11:33:15
I'll do some additional testing by forcing humidity changes.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 11:49:18
Zitat von: willybauss am 02 Mai 2014, 09:31:03
Sorry, don't understand what you mean. Did you check the related section of the THZ installation manual?

Yes, I read the section. What you mean, is that you regulate how strong sensor influences the heating curve (strength of room influence). That takes care that. Thanks for the hint.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 12:30:21
Immi,

I noticed an issue with the heat recovery reading. I suspect the connect/disconnect issue drops the reading of everything except for sGlobal in the log files. I notice this because the plot is empty. I restart and from this moment on the logging returns to normal and the e.g. heat recovery is logged and correctly displayed..until the next disconnect. Any idea?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 Mai 2014, 12:34:43
 
Zitat von: houseowner123 am 02 Mai 2014, 11:49:18
Yes, I read the section. What you mean, is that you regulate how strong sensor influences the heating curve (strength of room influence). That takes care that. Thanks for the hint.
That's right. Initially I set the influence of inside sensor to 30%, but by checking the fhem graphs it turned out that often it is like you described: the heatpump heats up the house, though it is still too warm, caused by other effects (in my case it's mostly the sun shining through big windows on south side). After having changed the room influence to 50% such issues are very limited meanwhile.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Mai 2014, 13:45:46
Zitat von: houseowner123 am 02 Mai 2014, 12:30:21
Immi,
I noticed an issue with the heat recovery reading. I suspect the connect/disconnect issue drops the reading of everything except for sGlobal in the log files. I notice this because the plot is empty. I restart and from this moment on the logging returns to normal and the e.g. heat recovery is logged and correctly displayed..until the next disconnect. Any idea?
Thanks, Tom
Hi Tom
For what you experience, there could be 100 reasons.
All problems come from my inexperience in programming  ;D

I try to explain you what happens in background.
THZ has some routine to get  (THZ_get) values from the heatpump and to set them (THZ_set)
This part, to my opinion is very robust!! 8)

The problems comes from the intervals: periodic calls to THZ_get without blocking.
There is a central FHEM function to do this (without to fork) called InternalTimer.
InternalTimer has some limitations: normally each module need only one interval. THZ has many parameters which need different intervals.
Therefore I wrote a workaround THZ_GetRefresh.

sub THZ_GetRefresh($) {
my ($par)=@_;
my $hash=$par->{hash};
my $command=$par->{command};
my $interval = AttrVal($hash->{NAME}, ("interval_".$command), 0);
my $replyc = "";
if (!($hash->{STATE} eq "disconnected")) {
  if ($interval) {
      $interval = 60 if ($interval < 60); #do not allow intervall <60 sec
      InternalTimer(gettimeofday()+ $interval, "THZ_GetRefresh", $par, 1) ;
  }
  $replyc = THZ_Get($hash, $hash->{NAME}, $command);
}
return ($replyc);
}


The error handling in  THZ_GetRefresh with InternalTimer is really poor.
To make it short: if you lose once the call to one interval, it will not be called anymore. So if you have once a problem with sGlobal, there will be no refresh of sGlobal until restart.

Basic rule: if you see something strange (or change some config or update),  restart FHEM.
I also suggest to restart FHEM periodically, to be sure (e.g at 23:59)
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Mai 2014, 13:49:47
yep, i also expierienced a crash of my fhem yesterday which was solved with a powercycle late at night ;)
there was no time for error research...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 17:36:08
Zitat von: immi am 02 Mai 2014, 13:45:46

The error handling in  THZ_GetRefresh with InternalTimer is really poor.
To make it short: if you lose once the call to one interval, it will not be called anymore. So if you have once a problem with sGlobal, there will be no refresh of sGlobal until restart.

Basic rule: if you see something strange (or change some config or update),  restart FHEM.
I also suggest to restart FHEM periodically, to be sure (e.g at 23:59)
immi

Pushing the 60min off Button caused the issue again:
2014.05.02 11:31:00 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.05.02 11:31:00 3: define at_D_60minOff at +00:59:00 set Mythz p07FanStageDay 1;set Mythz p07FanStageDay 0; setstate FanSelectorDay 60minOff : 0180FC0A056C00001003---InterfaceNotRespondig
2014.05.02 11:31:00 3: Notify_p07FanStageDay return value: 0180FC0A056C00001003---InterfaceNotRespondig
2014.05.02 11:31:00 3: Setting Mythz baudrate to 115200
2014.05.02 11:31:00 1: /dev/ttyUSB0 reappeared (Mythz)
2014.05.02 12:30:00 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.05.02 12:30:00 3: at_D_60minOff: 0180FD0A056C00011003---InterfaceNotRespondig
2014.05.02 12:30:01 3: Setting Mythz baudrate to 115200
2014.05.02 12:30:01 1: /dev/ttyUSB0 reappeared (Mythz)


Heat recovery monitoring stopped at 12:30. So would an automatic shutdown-restart help here?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 17:56:31
Zitat von: immi am 01 Mai 2014, 00:30:09
strange I expected more

one more thing...
I uploaded V0.093 tomorrow you can update..
changelog:

I added a plot of the quadratic curve neglecting summer/winter, FLOW-Proportion parameter and RoomInfluence parameter.
Using your settings of HC1, it computes the curve. The actual value is shown in red.
Look at the picture below.
you can test the plot like this:


define wl_hr2 weblink htmlCode <div class="SVGplot"><embed src="/fhem/THZ_PrintcurveSVG/" type="image/svg+xml"  name="wl_hr2"/></div> <a href="/fhem?detail=wl_hr2">wl_hr2</a><br>
attr wl_hr2 room heatpump


p.s. please Markus do not document in the wik this versioni; I do not know if I will leave the plot in  future version.

immi

Heating curve does not work for me. :(

(http://www.fotos-hochladen.net/uploads/screenshot2011n0jtksq9f.png) (http://www.fotos-hochladen.net)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Mai 2014, 19:32:43
Hi Tom
the Heating curve does work for you. You are out of range, and I did not implement an autoscale.
Look at the green line, it has a vertical offset.
Try to put the fusspunkt ($p14LowEnDHC1) to 0.

Your other problem is more interesting for me.
please post more log and the full config

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Mai 2014, 20:36:40
Hi immi,

thanks to the THZ module, I was able to set the low end to 0 K. The SE guy who did the setup locked it at 0.7 K which always bugged me. Finally, freedom here! :) What does the actual heating point mean? on the curve: heating occurs ; below the curve: heating needed; about the curve: too hot?

The logs are not more revealing; the connect/reconnect issue appears several time/day; I do not use serial mode:
2014.05.01 00:27:17 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.05.01 00:27:17 3: at_N_60minOff: 0180FE0A056D00011003---InterfaceNotRespondig
2014.05.01 00:27:17 3: Setting Mythz baudrate to 115200
2014.05.01 00:27:17 1: /dev/ttyUSB0 reappeared (Mythz)
2014.05.01 13:33:03 0: Server started with 33 defined entities (version $Id: fhem.pl 5663 2014-04-26 09:13:54Z rudolfkoenig $, os linux, user fhem, pid 6126)
2014.05.01 13:33:04 3: [MyDashboard V2.11] Using an outdated no longer used Attribute or Value. This has been corrected. Don't forget to save config. [dashboard_lockstate]
2014.05.01 19:15:23 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.05.01 19:15:28 3: Setting Mythz baudrate to 115200
2014.05.01 19:15:28 1: /dev/ttyUSB0 reappeared (Mythz)
2014.05.02 20:00:01 3: set Mythz pOpMode manual : manual
2014.05.02 20:00:01 3: reheat_start: manual
2014.05.02 20:04:37 1: /dev/ttyUSB0 disconnected, waiting to reappear
2014.05.02 20:04:37 3: Setting Mythz baudrate to 115200
2014.05.02 20:04:37 1: /dev/ttyUSB0 reappeared (Mythz)



basic config (without reading and plots):

define Mythz THZ /dev/ttyUSB0@115200
attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz room THZ
define FileLog_Mythz FileLog ./log/Mythz-%Y-%m.log Mythz

define reheat_start at *20:00:00 IF ([Mythz:WWTemp]<44.5) (set Mythz pOpMode manual)
define reheat_end at *21:00:00 IF ([Mythz:pOpMode] eq "manual") (set Mythz pOpMode DHWmode)

define MyDashboard Dashboard
attr MyDashboard dashboard_lockstate lock
attr MyDashboard dashboard_row top-center
attr MyDashboard dashboard_showhelper 0
attr MyDashboard dashboard_showtooglebuttons 0
attr MyDashboard dashboard_tab1groups THZ
attr MyDashboard dashboard_tab1name Momentanwerte
attr MyDashboard dashboard_tab1sorting t0c100,THZ,true,340,258:
attr MyDashboard dashboard_tabcount 1
attr MyDashboard dashboard_webfrontendfilter WEB
define MyDashboard_weblink weblink htmlCode {DashboardAsHtml("MyDashboard")}
attr MyDashboard_weblink room DashboardRoom

define FanSelectorDay dummy
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3@blue
attr FanSelectorDay group THZ
attr FanSelectorDay room Luefter
attr FanSelectorDay setList 0 1 2 3 60minOff
attr FanSelectorDay webCmd 0:1:2:3:60minOff
define Notify_p07FanStageDay notify FanSelectorDay  IF ([FanSelectorDay] eq "60minOff") (define at_D_60minOff at +00:59:00 set Mythz p07FanStageDay [Mythz:p07FanStageDay],set Mythz p07FanStageDay 0, setstate FanSelectorDay 60minOff) ELSE (set Mythz p07FanStageDay $EVENT)
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1

define FanSelectorNight dummy
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
attr FanSelectorNight group THZ
attr FanSelectorNight room Luefter
attr FanSelectorNight setList 0 1 2 3 60minOff
attr FanSelectorNight webCmd 0:1:2:3:60minOff
define Notify_p08FanStageNight notify FanSelectorNight IF ([FanSelectorNight] eq "60minOff") (define at_N_60minOff at +00:59:00 set Mythz p08FanStageNight [Mythz:p08FanStageNight],set Mythz p08FanStageNight 0, setstate FanSelectorNight 60minOff) ELSE (set Mythz p08FanStageNight $EVENT)
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1


What is that dashboard message all about? Never goes away.
Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Mai 2014, 23:48:49
Dear all
I uploaded v 0.094.
-> small bug fixed in $p14LowEnDHC1
-> some delay added for Tom, who has an older firmware
-> heating curve simulation updated.

@Tom
>> What does the actual heating point mean? 
The actual heating point is the status of your heatpump; The heat curve is my simulation, which is far from perfect.
>> What is that dashboard message all about?
delete following obsolete line from config "attr MyDashboard dashboard_lockstate lock"


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 03 Mai 2014, 13:03:10
Zitat von: immi am 02 Mai 2014, 23:48:49
Dear all
I uploaded v 0.094.
-> small bug fixed in $p14LowEnDHC1
-> some delay added for Tom, who has an older firmware
-> heating curve simulation updated.

@Tom
>> What does the actual heating point mean? 
The actual heating point is the status of your heatpump; The heat curve is my simulation, which is far from perfect.
>> What is that dashboard message all about?
delete following obsolete line from config "attr MyDashboard dashboard_lockstate lock"

immi

Thanks immi! :)

Is this THZ_GetRefresh already included in the new version or is that code meant for the config file?
Thanks also for the hint with the obsolete line!

EDIT Readings dropped to sGlobal only yesterday at 22:22 without any hints in them or myths log files. Had to do restart to get all readings and logs back again. Will test v0.94 and report back.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 Mai 2014, 13:19:22
Hi Tom
THZ_GetRefresh  is there from 3 weeks, otherwise you would not have interval attributes.

Is it better with 0.094?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 03 Mai 2014, 22:09:59
Hi Willybaus,

I connected the PT1000 as in the manual. Can't see any changes in the reading. The reading in 00_THZ.pm would be under sGlobal--> inside temp, right? There is a blue and black cable. Is it possible that I need to switch these?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Mai 2014, 00:11:25
Hi Tom,
sGlobal--> inside temp is correct. Maybe you need to restart the THZ. And you should try setting

INBETRIEBNAHME - RT.ERFASSUNG HK  ==> set to HK1

I don't believe that you need to change black/blue. Polarity shouldn't be an issue.

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Mai 2014, 00:40:19
Tom,
you can measure if there's really a resistance of approx. 1078 Ohm (= PT1000 @ 20°C) at the THZ side's end of the sensor cable. If not => check cable, sensor, soldering, ... Or (for debugging only) replace the cable incl. PT1000 by a resistor (or series of resistors) having approx. 1078 Ohm in total. So the reported value should be approx. 20°C.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 04 Mai 2014, 01:16:06
Thanks willibaus for all your input.
I do not have such a setting under Inbetriebnahme. Room temp however, is displayed in HK1 but it does not change at all, even in my hand.  I googled that the The thz needs same indoor sensor as the outside sensor: kty 81-210.  The PT1000 with its current resistance is right to read -60 degrees by the fhem module.
If I would place the sensor I boiling water it should read -20.
I found this in the newer version of the lwz manual. Or is the hot water test a bad idea? I can measure resistance too.

Thanks,
  Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 Mai 2014, 09:05:13
measuring the resistance is a better idea than try boiling hot water ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Mai 2014, 09:50:30
Zitat von: houseowner123 am 04 Mai 2014, 01:16:06
Thanks willibaus for all your input.
I do not have such a setting under Inbetriebnahme. Room temp however, is displayed in HK1 but it does not change at all, even in my hand.  I googled that the The thz needs same indoor sensor as the outside sensor: kty 81-210.  The PT1000 with its current resistance is right to read -60 degrees by the fhem module.
If I would place the sensor I boiling water it should read -20.
I found this in the newer version of the lwz manual. Or is the hot water test a bad idea? I can measure resistance too.

Thanks,
  Tom
Looks like things changed a bit within last 4 years. Putting the sensor into water might end up in measuring the resistance of the hot water itself. But since the sensor is the wrong one anyway you can't damage anything. -60°C sounds like the default value, which is being displayed  if no sensor is connected.

Wait until afternoon, when outside temperature is higher, then measure the resistance of the outside_temp sensor (after having it disconnected of course). ATTENTION: You will get an error message by doing so. To avoid that you should switch off the THZ completely before disconnecting the outside temp sensor.

As soon as you know the approx. right resistance from above mentioned measurement you can boil your PT1000 and measure the resistance too. So you know which value you can expect from the THZ display. Just judge if it can make sense or not. Alternatively (or for sure ?) you need to order the  kty 81-210 as well.

Sorry for having given you the wrong ordering info. From reading the THZ installation manual I've been sure it's a PT1000.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 04 Mai 2014, 13:01:39
No sweat, willybaus. I ordered the sensor from Amazon. So I just send it back. Will measure offline resistance later tonight. Ideally I would like to order the sensor element alone because I have all the cables. Question: Can solder this thing into copper wire or will this damage the sensor?

Thanks,
  Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Mai 2014, 19:10:08
as far as I remember I soldered it also. Datasheet says max. ambient operating temperature is 150°C, so if you're used to solder electronic components you might be unable to destroy it by soldering. If you're unsure just pick the wire with a pair of tongs close to the housing, so that just a short end is visible. The  pair of tongs will work as a heat sink during soldering, avoiding the heat to reach the silicon.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 04 Mai 2014, 19:31:21
OK, willybaus. I will try that with the tongues.

Immi,
Version 0.94 does make things worse. Nothing is read except for sGlobal. No errors. Only restart makes one reading of all 40 parameters.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Mai 2014, 20:33:01
In the "humidity vs. heatSetTemp" topic I again observed a relation between both. The midnight spike was blowing breath into the humidity sensor. In the afternoon we simply opened the windows in living room, so that fresh air from the outside reduced inside humidity - resulting in an inverse reaction of  heatSetTemp value.
Next I'll try to blow hot air from a hair dryer into the exhaust ventilation, assuming that there are more, undocumented, sensors in the THZ.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 05 Mai 2014, 20:55:19
Hi, i try to use the Outside temp to do other things outside oft the heatpump.
So i split out this Form sGlobal reading and i know how to reduce decimal places however one Problem remain.

As sGlobal has always changes, my split outsideTemp get updates frequently even the value stay the same. exactly this isthe Problem. If i usw filelog for example i get endless times a updates Entry with no value change.

Usually I would set "event-on-change" but this cannot work here. What else can i do?

Thanks again for and help.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Mai 2014, 23:29:28
Zitat von: Heiner am 05 Mai 2014, 20:55:19
Usually I would set "event-on-change" but this cannot work here.
Not true, event-on-change works. I try to explain it once more.


attr Mythz event-on-change-reading .*
attr Mythz event-on-update-reading s.*

The first line tells FHEM : "I want a notify/log-entry only if a reading changes; consider all readings"
The second line tells FHEM: "I want all readings starting with "s" to be treated normally, please override event-on-change-reading"

now let us define 2 userreadings:one starting with "s" and one not (AussenTemp and sAussenTemp)

attr Mythz userReadings AussenTemp:sGlobal { sprintf('%1.f ',   ((split ' ',ReadingsVal("Mythz","sGlobal",0))[1]) ) }, sAussenTemp:sGlobal { sprintf('%1.f ',   ((split ' ',ReadingsVal("Mythz","sGlobal",0))[1]) ) }


and now the log result

2014-05-05_23:08:59 Mythz sGlobal: outsideTemp: 12.9 flowTemp: 32.1 returnTemp: 31.6 hotGasTemp: 31 dhwTemp: 43.8 flowTempHC2: -60 evaporatorTemp: 25.7 condenserTemp: 32.5 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 14.8 relHumidity: 0 dewPoint: 759 P_Nd: 7.59 P_Hd: 13.39 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-05-05_23:08:59 Mythz sAussenTemp: 13
2014-05-05_23:08:59 Mythz AussenTemp: 13
2014-05-05_23:09:08 Mythz sFirmware: version: 4.39
2014-05-05_23:09:27 Mythz sGlobal: outsideTemp: 12.8 flowTemp: 32 returnTemp: 31.6 hotGasTemp: 30.8 dhwTemp: 43.8 flowTempHC2: -60 evaporatorTemp: 25.6 condenserTemp: 32.3 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 14.8 relHumidity: 0 dewPoint: 761 P_Nd: 7.61 P_Hd: 13.39 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-05-05_23:09:27 Mythz sAussenTemp: 13
2014-05-05_23:10:27 Mythz sHeatRecoveredTotal: 2114 kWh
2014-05-05_23:10:27 Mythz sGlobal: outsideTemp: 12.8 flowTemp: 32 returnTemp: 31.4 hotGasTemp: 30.6 dhwTemp: 43.9 flowTempHC2: -60 evaporatorTemp: 25.6 condenserTemp: 32.3 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 14.8 relHumidity: 0 dewPoint: 761 P_Nd: 7.61 P_Hd: 13.35 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-05-05_23:10:27 Mythz sAussenTemp: 13
2014-05-05_23:10:31 Mythz sHC1: outsideTemp: 12.7 x08: 37.8 returnTemp: 31.4 integralHeat: 0 flowTemp: 32 heatSetTemp: 23.9 heatTemp: 31.5 seasonMode: summer integralSwitch: 100 opMode: setback roomSetTemp: 21
......................
2014-05-05_23:15:39 Mythz sGlobal: outsideTemp: 12.5 flowTemp: 32 returnTemp: 32.1 hotGasTemp: 30.4 dhwTemp: 43.6 flowTempHC2: -60 evaporatorTemp: 25.6 condenserTemp: 32.4 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 14.6 relHumidity: 0 dewPoint: 761 P_Nd: 7.61 P_Hd: 13.35 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-05-05_23:15:39 Mythz sAussenTemp: 12
2014-05-05_23:15:39 Mythz AussenTemp: 12
2014-05-05_23:17:11 Mythz sHC1: outsideTemp: 12.6 x08: 37.8 returnTemp: 32.1 integralHeat: 0 flowTemp: 32.2 heatSetTemp: 24 heatTemp: 32 seasonMode: summer integralSwitch: 100 opMode: setback roomSetTemp: 21
2014-05-05_23:17:58 Mythz sDHW: dhw_temp: 43.5 outside_temp: 12.6 dhw_set_temp: 43.6 comp_block_time: 0 x20: 0 heat_block_time: 0 x28: 2 x32: 2 x36: 15755 x40: 0
2014-05-05_23:22:19 Mythz sGlobal: outsideTemp: 12.5 flowTemp: 31.9 returnTemp: 31.5 hotGasTemp: 30.1 dhwTemp: 43.4 flowTempHC2: -60 evaporatorTemp: 25.6 condenserTemp: 32 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 14.4 relHumidity: 0 dewPoint: 763 P_Nd: 7.63 P_Hd: 13.22 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-05-05_23:22:19 Mythz sAussenTemp: 12


As you see all reading starting with "s" are always logged.
AussenTemp is only logged on change.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 06 Mai 2014, 20:48:29
Hi there!

First of all I wanted to say hello and give you all a big thank you for your work on this fhem-extension!  8)
I'm a new LWZ303i (V 4.09) owner and I was looking for a way to monitor and switch the parameters from the couch without having to walk downstairs  ;)
Hopefully I can also contribute something  :-[

I'm running FHEM on a raspberry Pi and get the readings over USB.

And of course I also have a question  ::) :P
I am very happy with all the actual given posibilliies. Hence I would find it charming if it was possible to read also the values on power-consumption, that can be found in the "Fachmann-Menü (=> Laufzeiten)".
I was reading a lot - and hopefully didn't overread it - and found no hint on getting this data. There was an answer in Robert Penz's blog about this, and also some hint was given via mail. So maybe it would be possible? The data should be in the sHistory register?


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 Mai 2014, 20:52:39
hi lwzler,

welcome to the group :) nice to read that your installation is working.
for now there are only some heat-recovery values read from the heatpump. maybe immi can check if he can find the requested values in the system.

did you use the fhemwiki installation instruction? did you expierience any problems? i ask to improve the wiki maybe :)

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 Mai 2014, 21:12:25
Hi lwzler
very happy it worked for you,
If you managed the full installation alone (without asking in the forum) , means that Markus wiki is excellent.
Please test further and tell us if you can also write back to the heatpump.
Zitat von: lwzler am 06 Mai 2014, 20:48:29
Hence I would find it charming if it was possible to read also the values on power-consumption, that can be found in the "Fachmann-Menü (=> Laufzeiten)".
I was reading a lot - and hopefully didn't overread it - and found no hint on getting this data. There was an answer in Robert Penz's blog about this, and also some hint was given via mail. So maybe it would be possible? The data should be in the sHistory register?
Yes in sHistory you have exactly the first 6 values of  "Fachmann-Menü (=> Laufzeiten)".
sHistory compressorHeating: 1364 compressorCooling: 0 compressorDHW: 921 boosterDHW: 1 boosterHeating: 205
The others have to be found and interpreted; please share all information you have.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 06 Mai 2014, 21:17:47
Zitat von: micomat am 06 Mai 2014, 20:52:39
did you use the fhemwiki installation instruction? did you expierience any problems? i ask to improve the wiki maybe :)

I did not experience any problems during installation. From the beginning (with raspbian including lots of updates) until the system was running and the LWZ sent me the first "hello world"  :P it took not an hour at all.

I used the info from the wiki page to get mythz started. But I also had read the thread here before...but in my opinion the wiki is great and has no lack of needed information!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 Mai 2014, 21:27:16
thanks for the feedback ;)
did the sHistory reading contain the values you need?

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 06 Mai 2014, 21:59:23
Zitat von: immi am 06 Mai 2014, 21:12:25
Yes in sHistory you have exactly the first 6 values of  "Fachmann-Menü (=> Laufzeiten)".
sHistory compressorHeating: 1364 compressorCooling: 0 compressorDHW: 921 boosterDHW: 1 boosterHeating: 205
The others have to be found and interpreted; please share all information you have.

Until now I've tried to get the values with an altered 00_THZ.pm. Unfortunetaly they seem not be in direct order with the known first 6 values, as I always get back a zero value when I try to read at another position.

Is there an easy way to get all "09" values as raw data from my LWZ?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 06 Mai 2014, 22:28:35
can you Provide the names of the values youre looking for?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 Mai 2014, 22:56:35
Zitat von: lwzler am 06 Mai 2014, 21:59:23
Until now I've tried to get the values with an altered 00_THZ.pm. Unfortunetaly they seem not be in direct order with the known first 6 values, as I always get back a zero value when I try to read at another position.
Is there an easy way to get all "09" values as raw data from my LWZ?
yes you go to sub THZ_Parse($)
there are lots of "when" at about line 1000
you search for

when ("09")    {                     #operating history
    $message =    "compressorHeating: " . hex(substr($message, 4,4))    . " " .
                  "compressorCooling: " . hex(substr($message, 8,4))    . " " .
                  "compressorDHW: " . hex(substr($message, 12,4))    . " " .
                  "boosterDHW: " . hex(substr($message, 16,4))    . " " .
                  "boosterHeating: " . hex(substr($message, 20,4))   ;
  }


and replace with

when ("09")    {                     #operating history
    $message =  $message . " " .
                "compressorHeating: " . hex(substr($message, 4,4))    . " " .
                  "compressorCooling: " . hex(substr($message, 8,4))    . " " .
                  "compressorDHW: " . hex(substr($message, 12,4))    . " " .
                  "boosterDHW: " . hex(substr($message, 16,4))    . " " .
                  "boosterHeating: " . hex(substr($message, 20,4))   ;
  }

and then you get sHistory

If you have time and you are able to help reverse.eng., I find very intriguing E8.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 06 Mai 2014, 23:40:32
Zitat von: micomat am 06 Mai 2014, 22:28:35
can you Provide the names of the values youre looking for?

For example "E Warmwasser Tag" (E(nergy) DHW Day [Wh or kWh]) which is the electric enery the LWZ used.

@immi
Thanks. Just checked the other registers but I havenot found the values I was looking for - even not in other registers. But I'm gonna find this! As my LWZ has no etxra energy meter I am very interested in the ability to differ which amount of used energy was fopr the LWZ or the other consumers...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 00:29:24
dear all
I just uploaded v 0.095. Tomorrow you can update thz.
changelog
- readings sHeatDHWDay and  sHeatDHWTotal  added

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 07 Mai 2014, 01:23:32
Wow! Amazing...so it wasn't hiding in one of the known registers?

...I'm really awkward to ask, if you also know where to find sHeatDay/Total...the consumptions for heating  :-[

I've tried to read all paramameters possible and searched the results for the data in HEX-mode.
So if have gonna missed some parameters...  :(
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 06:27:11
hey lwzler,

don't worry. immi is soaking up all requests for new values ;D

update info added to wiki.


markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 07 Mai 2014, 08:45:28
Zitat von: immi am 07 Mai 2014, 00:29:24
readings sHeatDHWDay and  sHeatDHWTotal  added

sHeatDHW Day / Total are the heat quantities (? Wärmemenge), just to be sure. But nevertheless those values are interesting as they can be used to calculate the "Arbeitszahl" of the heat pump  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 09:40:07
immi,

another request from my side :)
do you see any change to read the "clean filter" state? it's displayed in the display once the filter reached it's lifetime or is too messy.

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 10:06:37
Dear lwzler
>>sHeatDHW Day / Total are the heat quantities (? Wärmemenge),
I read the word "quantity" in the manual. I do not like it... or I do not understand it.
Physics tell you that Heat (Wärme) is an energy transfer Q. It is in Joule normally.
I expect Tecalor uses kWh and Wh, which are still energy but are more confortable.

If sHeatDHW Day / Total are Q.... I am not sure.
I found it yesterday evening and I wrote the code with almost closed eyes :)
I expect that everyone helps checking.

Hi Markus
the increase in the numer of parameters going really fast,
the code is getting a mess. and we have a FHEM major release in one week.
Let us try to clean up and stabilize.
All other parameters will come. What could be done is to list the wished parameters/features in the wiki.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 10:25:28
okay so don't stress yourselfe. it was just a thought while cleaning the filters last weekend.

if you need help finding some errors, maybe i can do some kind of code review?

by the way there is a spelling error in P14
p14LowEnDHC1 i guess it should be p14LowEndHC1

:)
try to get some sleep before you clean up the code.


@ll please report your parameter and function whishes to me, i will collect and wiki them.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 07 Mai 2014, 14:29:12
@immi

Thanks for your efforts!  :D

Zitat von: immi am 07 Mai 2014, 10:06:37
If sHeatDHW Day / Total are Q.... I am not sure.

Given the data shown at my LWZ's display, yeah. sHeatDHW is the value shown in the "Istwerte" menu.

In the "Fachmann" area there is the submenu "Laufzeiten" in which you can find the values that are available in the shistory but also a lot more values e.g. the electric power consumed by the lwz for heating and hot water including the electrical power consumed by the aux heater.

While sHeatDHW is the amount of energy that was transferred in the system to heat water the value sxxxxxDHW in the "Laufzeiten"-submenu gives you the "real" electrical energy the LWZ had to expend for the evaporator etc..
With those two values it is possible to calculate the energy conversion efficenicy  (η; Arbeitszahl) which should be at least around 2 for heat pumps afair.

So now worries  :)

@wishlist
For me the values
"E Heizung Tag [(k)Wh]"
"E Heizung Summe [M/k Wh]"
"E WW Tag [(k)Wh]"
"E WW Summe [M/k Wh]"
"E Heizen NE Summe  [M/k Wh]"
"E WW NE Summe [M/k Wh]"

would be very interesting.

I'm going to try to get a whole reading of ALL the LWZ vales and going to search those values with a hex editor...and hopefully find them  ;)

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 15:00:18
I want to go back to the quadratic curve which I also updated in 0.095.
you cal plot the curve adding in the config following code

define wl_hr2 weblink htmlCode <div class="SVGplot"><embed src="/fhem/THZ_PrintcurveSVG/" type="image/svg+xml"  name="wl_hr2"/></div> <a href="/fhem?detail=wl_hr2">wl_hr2</a><br>
attr wl_hr2 room heatpump

Now why it is so important? If we do not understand it, how can we change parameters in our heatpump like gradient, LowEndHC1...?
Another important reason is that I see nothing on the small display from the heatpump.
My best fit is now following this equation: Simul_heatSetTemp(outside_tempFiltered)

a= 1 + (roomSetTemp * (1 + p13GradientHC1 * 0.87)) + p14LowEndHC1
b= -14 * p13GradientHC1 / roomSetTemp
c= -1 * p13GradientHC1 /75
Simul_heatSetTemp = c * outside_tempFiltered^2  + b * outside_tempFiltered  + a


As you can see, the gradient is both in the quadratic and in the linear part.
I am still neglecting from the curve winter/sommer FLOW-Proportion, RoomInfluence.. but it is not so bad

Please tell me how far is the red point (for your setup) to the simulated quadratic curve.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Mai 2014, 16:34:52
Zitat von: lwzler am 07 Mai 2014, 14:29:12


@wishlist
For me the values
"E Heizung Tag [(k)Wh]"
"E Heizung Summe [M/k Wh]"
"E WW Tag [(k)Wh]"
"E WW Summe [M/k Wh]"
"E Heizen NE Summe  [M/k Wh]"
"E WW NE Summe [M/k Wh]"

would be very interesting.

I'm going to try to get a whole reading of ALL the LWZ vales and going to search those values with a hex editor...and hopefully find them  ;)

E WW Tag = sHeatRecoveryDay
E WW Summe = SHeatRecovery..total or Sum

So these are already part of the current readings that you should be able to see.
Regarding the Arbeitszahl...The values that the LWZ give you you have to put into relation to the energy that was needed to produce (from your separate reading (Stromzähler). Since the heat recovered is part of this system I also add this factor in to energy that was "produced". So over an entire year (2013) I ended up with an Arbeitszahl of 3.76. In my mind, it does not make sense to judge it day-by-day. For instance: The lowest numbers for Arbeitszahl, mean the least efficient, the LWZ is during summer. Why? Because there is no heat produced that can be recovered. All energy (even though it is very little) goes into the production of WW.

@immi: as far as wish list for parameters I agree with LWZlers list. PLUS: Is is possible to give sHistory parameters another decimal. Just one ofter the comma would be great. :)

regarding heating curve: The red point does not show up for me at all anymore. I am not sure why? Maybe because I have now DHWmode permanently set?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 16:56:28
Zitat von: houseowner123 am 07 Mai 2014, 16:34:52
E WW Tag = sHeatRecoveryDay
E WW Summe = SHeatRecovery..total or Sum

sorry thats incorrect

WM WRG Tag = heat recovery day
WM WRG Summe = heat recovery total

they are display under actual avlues not in "fachmann"
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 17:54:13
Hi Tom
you do not see the red point, because the plot is up to 21°C , outside is warmer
if you updated FHEM (and restarted) you should see in the legend (below-left) the actual value of the red point.
please try this night and early in the morning

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 18:37:08
i See the red Point :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 19:34:12
Hi Markus
is it on the line more or less?
if not post your plot and all your relevant pXX
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 19:35:05
doesn't fit at all, see attachment. Reason is most probably a factor of 10 in reading P14, which is 1.5°C, but the graph says 15°C. The offset btw. red dot and green curve fits to the difference.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 19:45:51
it's perfectly on the line all the time :)
sometimes a liiiiittle below but who cares?

thanks :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 19:46:08
after correctiion of factor 10 in source code it fits much better, but still not good. Reason might be that I use  the inside temp sensor additionally, influencing the heat curve by 50%. Current room temperature is 23.5°C, while inside temp set is 21.5°C.

I don't expect you to work on this, since I'm obviously the only one having this setup, and since it's not really beneficial for me.

edit:

After a look on the graphical heat curve in the THZ display I can confirm that your green curve fits very well to it - since this curve doesn't consider inside temp as well. 

Additionally I'd like to take this chance to vote for installing an inside temp sensor. As you can see, without an  inside temp sensor the heatpump would start to heat up soon, not considering that the inside temp is still much too high. The red dot shows clearly that the inside temp sensor cares about this fact and pulls the curve down by almost 5 degrees. This definitely saves a lot of energy with very limited effort ... ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 20:07:44
and here is the result when I set the room influence to 0% - fits the curve almost perfect
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 20:46:04
my room Influence is always 0%
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 07 Mai 2014, 20:49:23
Zitat von: micomat am 07 Mai 2014, 19:45:51
it's perfectly on the line all the time :)
sometimes a liiiiittle below but who cares?

Same for me  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 20:52:55
Dear all thanks for the feedback

Hi Willy
>>> after correctiion of factor 10 in source code it ..
Where have you corrected it; you have probably an older version version, please check
I fixed p14LowEndHC1 one or two version ago.
Just checked and works fine 8)
update and don't forget to restart.

My target (and I think yours) is to save energy in winter and keep an avarage of 21.5 degree in livingroom.
In order to save energy, I want to try to keep the HCheatSetTemp as low as possible (Carnot theorem rules) for having maximum theoretical efficiency.

I find also interesting that you are using 0.26 as gradient.
The guy installing the system has set 0.4 for me.
I never changed it, because I have never understood really what it did.
I expect that only knowing how the system reacts to external-temp, I can chose a better value for next winter.

Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 21:11:31
i use gradient of 0.2 and 3k low end? interesting :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 22:14:17
##############################################
# 00_THZ
# $Id: 00_THZ.pm 5772 2014-05-06 22:27:21Z immiimmi $
# by immi 05/2014
# v. 0.095
#

... row 1256:
my $p14LowEnDHC1 =0.1 * (split ' ',ReadingsVal("Mythz","p14LowEnDHC1",0))[0];



You're partially right:  p14LowEnDHC1 reports 1.5K, but nevertheless the value inside the heating curve was 15 before I corrected it, see attached screen shot in my answer Antwort #466 am: Heute um 19:35:05 .

Should I make the red arrow even bigger?  ???
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 22:29:31
Zitat von: immi am 07 Mai 2014, 20:52:55
My target (and I think yours) is to save energy in winter and keep an avarage of 21.5 degree in livingroom.
In order to save energy, I want to try to keep the HCheatSetTemp as low as possible (Carnot theorem rules) for having maximum theoretical efficiency.

I find also interesting that you are using 0.26 as gradient.
The guy installing the system has set 0.4 for me.
I never changed it, because I have never understood really what it did.
I expect that only knowing how the system reacts to external-temp, I can chose a better value for next winter.

Immi
So you take a huge effort in fhem but obviously missed the basic rule for energy saving, which should have been the first step. You should make a hydraulic adjustment of your whole heating system, fixing the throughput of all pipes to really necessary values. And before that you have to obsolete all your room thermostats, so that the heat flow is no more restricted anywhere. So finally the heat pump just produces the heat which is *really* needed. By having a heating curve set by accident and fix it with room thermostats you loose up to 40% of energy. I did so too in first winter, ending up in approx. 3800kWh per year and 130 hours of booster usage. Second winter - after first iteration of above mentioned changes - I endet up in 3000kWh and 5 hours booster, in last winter (which was not so cold) it tends to 2500kWh without booster at all. All values without any solar collectors on my roof.

I simply bought a ton of cheap digital thermometers, distributed them all over the house, opened all heating circles (remove thermostat heads or set them to 30°C) and then adjusted the flow values of all circles so that all rooms had same temperature. Since this temperature was much too high of course I began reducing the heat curve and its offset, until all rooms had 21.5°C without using room thermostats at all. Adjusting the 0.26 value of the heating curve simply ensures that your 21.5°C are kept always, no matter how warm or cold it'soutside. It basically reflects the heat loss of your building. The better the isolation, the lowe the value.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Mai 2014, 22:31:50
my booster was Never used. Not even at -15C.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Mai 2014, 22:33:47
@ immi: even after update there is no red dot.  :( Because 8 °C is below the scale. Other than that, love the new readings! Thanks so much :)

(http://img5.fotos-hochladen.net/uploads/screenshot201e2u6ixvgzd.png) (http://www.fotos-hochladen.net)

@ willybaus: the new inside temp probe arrive today and I installed it and ..it works. So the PT1000 is really just for the solar collector for the inside you need KTY 81-210 cable.
The reading is not 100% correct but as for the outside sensor, there is an option to correct the reading. Thanks again for the suggestion. Just need to rewire and extended the cable from the basement to the kitchen/living room but this should not be a problem. FHEM THZ reading under sGlobal works nicely.  8)

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 22:41:20
Zitat von: houseowner123 am 07 Mai 2014, 22:33:47
The reading is not 100% correct but as for the outside sensor, there is an option to correct the reading.
Hi Tom,


if you don't succeed with the correction in this way (like it was im my case because of additional display in living room) let me know. I had to correct it by a user reading
inside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[81]) - 0.6 }



Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 22:43:31
Zitat von: micomat am 07 Mai 2014, 22:31:50
my booster was Never used. Not even at -15C.
that sounds reasonable, since you have a heating curve value of just 0.2. Let me know about the outside wall isolation (cross section of your walls) please.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Mai 2014, 23:09:38
@immi:
something went wrong with the shutdown + restart. After another restart the value of 1.5° was correct even in the heating curve graph, and even without my factor of 0.1. But it cannot be related to an outdated version. My previous version was 0.090 which didn't have the heating curve graph at all. Maybe I opened the heating curve too early after restart, when p14 had not yet been read by 0.094, so the wrong old value of 0.090 was still there.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Mai 2014, 23:25:48
Hi willy
plausible explanation
thanks for helping to debug
immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Mai 2014, 00:16:31
Zitat von: immi am 07 Mai 2014, 23:25:48
Hi willy
plausible explanation
thanks for helping to debug

one more question:p15RoomInfluenceHC1 is from 0 to 10 like in datasheet or there is a typo?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 Mai 2014, 06:31:22
Zitat von: willybauss am 07 Mai 2014, 22:43:31
that sounds reasonable, since you have a heating curve value of just 0.2. Let me know about the outside wall isolation (cross section of your walls) please.

i have a low energy house (and a always freezing wife) ;)
we have a 15cm outside insulation on the walls. in my eyes the booster is first allowed to work after a few days of very low temperature with the danger of the house is chilling out too much. i live in southern of bavaria (about 40km from fuessen) so we HAVE winter here ;)

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 08:12:02
Zitat von: immi am 08 Mai 2014, 00:16:31
one more question:p15RoomInfluenceHC1 is from 0 to 10 like in datasheet or there is a typo?
looks like a typo. I can change it from 0till 100%.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Mai 2014, 11:33:50
Zitat von: willybauss am 08 Mai 2014, 08:12:02
looks like a typo. I can change it from 0till 100%.
Hi Willy
In Both the engl. and german datasheet  is wrong 1..10. otherwise it makes no sense.
I do not use the parameter (at the time ), but I am starting to consider it for next winter.
Could you please explain in one sentence, what the parameter does, so that Markus documents  the wiki?
Maybe an example could be usefull, considering what happens with 0% and and what happens with your current setting.
Shall I modify the code in 00_THZ.pm from 0..10  to 0...100%?
Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Mai 2014, 12:24:59
Zitat von: willybauss am 07 Mai 2014, 22:41:20
Hi Tom,


if you don't succeed with the correction in this way (like it was im my case because of additional display in living room) let me know. I had to correct it by a user reading
inside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[81]) - 0.6 }



Willy

Thanks, Willy! That is exactly what I had to do.  :) Correction was -2.6. Regarding usage: We live in an low energy house (KfW 55) too, built in late 2011. The first two years we used 2800 kWh. I then looked closer into options of saving. Most effective so far are the timer programs for day and night. I simply accept that it is little bit colder in the morning and start the day setting at 4 pm. Also the difference between day and night should not be more than 2 K. Because of the warm winter my goal is less than 2000 kWh this year.

Regarding booster: Booster usage does only depend on either bimodal point or the total time delay set for normal mode before booster sets in.  I have the bimodal point set at -10°C and only use booster stage I (if needed)  because most people agree that these setting are safe. But the bigger question: Is it really most efficient? With the help of FHEM THZ monitoring I would like to determine the outside temp where booster usage is more efficient than having the heat pump working endlessly.

@immi: Would room influence as 0-10 scale. It could be that the FEZ extra display translates this into percent but on the LWZ/THZ display it is a 0...10 scale, at least for my version. I think it is a smart idea to use room temp influence at setting 5 (50%) as a starting point. The heat production is then balanced between in-and outside temp. However I see the danger that it also could lead to unnecessary heating. It needs testing. In the end it depends how well your house is insulated and air-tightly packed.
Four things can acutely raise the room temp:
- use of fireplace
- use of kitchen oven
- low sun through big windows
- pure presence of people (2-3) in one room 
Under these circumstances room influence should slow down pump activity. Is there anybody else out there but Willy who has a room temp sensor installed?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Mai 2014, 13:56:17
Hi Tom
>>  Would room influence as 0-10 scale. It could be that the FEZ extra display translates this into percent but on the LWZ/THZ display it is a 0...10 scale, at least for my version. I think it is a smart idea to use room temp influence at setting 5 (50%) as a starting point.

In the heatpump firmware there is a number from 0 to 100. In the display of my heatpump there is  0 to 100.
In the manual there is 0...10.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Mai 2014, 14:00:35
Zitat von: immi am 08 Mai 2014, 13:56:17
Hi Tom
>>  Would room influence as 0-10 scale. It could be that the FEZ extra display translates this into percent but on the LWZ/THZ display it is a 0...10 scale, at least for my version. I think it is a smart idea to use room temp influence at setting 5 (50%) as a starting point.

In the heatpump firmware there is a number from 0 to 100. In the display of my heatpump there is  0 to 100.
In the manual there is 0...10.

immi

I guess then diffferent firmware versions have different scales here. Can you set the influence to something like 56% or only in decades?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Mai 2014, 14:49:20
you can try 56%
--
set Mythz p15RoomInfluenceHC1 5.6

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 15:00:58
Zitat von: immi am 08 Mai 2014, 13:56:17
In the heatpump firmware there is a number from 0 to 100. In the display of my heatpump there is  0 to 100.
In the manual there is 0...10.

immi
same at my side
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 15:05:00
Zitat von: immi am 08 Mai 2014, 11:33:50
Hi Willy
Could you please explain in one sentence, what the parameter does, so that Markus documents  the wiki?
Maybe an example could be usefull, considering what happens with 0% and and what happens with your current setting.
Shall I modify the code in 00_THZ.pm from 0..10  to 0...100%?
Immi
@ markus:
p15RoomInfluenceHC1 defines influence of room temperature on heating curve.
0 => heat curve follows outside temp only
30 => 30% influence of inside temp, 70% outside temp
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Mai 2014, 15:15:43
Zitat von: willybauss am 08 Mai 2014, 15:05:00
@ markus:
p15RoomInfluenceHC1 defines influence of room temperature on heating curve.
0 => heat curve follows outside temp only
30 => 30% influence of inside temp, 70% outside temp
Willy,
Since you have the most experience with this. So the THZ/LWZ calculates then internally 2 heating curves, one only based on outside temp, the other only on inside temp and then weights the results based you chosen influence setting to come up with a resulting HeatSollTemp?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 15:35:44
@ houseowner123

I wonder how a KFW55 house can cool down by 2° over night? If I would switch the heat pump off in the evening I would not at all see any difference on the inside room temperature for lots of hours, since the stone floor (approx. 30 tons) keeps lots of energy.

When in the evening do you start night mode? I assume you switch to day setting at 4 am, not pm, right? Or is the house in night mode from last evening until afternoon? That would be the explanation for the big savings by using day/night mode.

Do you have additional solar cells on the roof? I don't - so far.

ZitatWith the help of FHEM THZ monitoring I would like to determine the outside temp where booster usage is more efficient than having the heat pump working endlessly.

How will you do that? Can you share your thoughts about finding the right decision? Basically I believe that the heat pump's heat creation is more efficient that the booster always. Even in coldest winter nights it has at least a factor of 3x, while the booster is always on 1x. Limiting the booster to stage 1 is a good solution to avoid stopping the heat pump to work, just because the booster did its work too fast.

The setting of room influence is also related to the physical characteristics of your house, e.g. phase shift (=time delay between a temperature change happening outside and the point in time when it arrives on the room side). If your house is built from heavy stones you should keep the room influence low. Otherwise it can take too long to heat up, when the room sensor detects under temperature. Stones have a big heat storage capacity, needing lots of energy to heat them up - and the THZ has just 6kW ...

Another thing causing higher room temperatures is reading newspaper at night :-) My lamp uses up to 150W, visible on the thermometer within 15 minutes.

Often forgotten influences:
- hydraulic adjustment (as I described above)
- use of room thermostats instead of open heating circles
- wrong spread of heat circle temperatures (=difference between flow temp and return temp); should be approx. 5° when using a underfloor heating
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 15:43:36
Zitat von: houseowner123 am 08 Mai 2014, 15:15:43
Willy,
Since you have the most experience with this. So the THZ/LWZ calculates then internally 2 heating curves, one only based on outside temp, the other only on inside temp and then weights the results based you chosen influence setting to come up with a resulting HeatSollTemp?
Sorry, don't know how the calculation is really done in detail. Up to approx. February I used 30%, but when I started with the monitoring I saw that there's still heat pump activity during night, even if room temperature is too high. After switching to 50% this is just happening rarely.
You can check the heating curve screen dumps I posted yesterday. One of them is with 0%, the other one with 50%. The difference is ~4.8° in heatSetTemp.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Mai 2014, 17:05:09
Zitat von: willybauss am 08 Mai 2014, 15:35:44
@ houseowner123

I wonder how a KFW55 house can cool down by 2° over night? If I would switch the heat pump off in the evening I would not at all see any difference on the inside room temperature for lots of hours, since the stone floor (approx. 30 tons) keeps lots of energy.

There are the differencse: No stones in my house, it is wooden based house (Fingerhaus) with multilayered thin insulation. Because of that, the ceiling is rather thin. Second, I have basement in which the temp is always much lower and I assume (though the basement is well insulated against the internal staircase) it works a bit like a heat sink.
Presence or absence is a room of 2 people accounts for 1K difference. If there are 6 people present in the house, I generally need no oven in the winter. Having overnight guest has therefore special (saving) benefits.

Zitat von: willybauss am 08 Mai 2014, 15:35:44
When in the evening do you start night mode? I assume you switch to day setting at 4 am, not pm, right? Or is the house in night mode from last evening until afternoon? That would be the explanation for the big savings by using day/night mode.

Sorry, 4 pm the day mode starts

Zitat von: willybauss am 08 Mai 2014, 15:35:44
Do you have additional solar cells on the roof? I don't - so far.

No, they will never amortize.

Zitat von: willybauss am 08 Mai 2014, 15:35:44
How will you do that? Can you share your thoughts about finding the right decision? Basically I believe that the heat pump's heat creation is more efficient that the booster always.

That is what I believed until this winter during which we had three days with average temps of -10°C. The heat pump was struggling to even raise the temp if the heating circuit by 0.1K. I was watching it for 45 min. On the contrary, WW heating worked well. When I olwered bimodal point from -10°C to -6°C the daily usage dropped by 5 or 6 kWh. Even though the booster runs with 6 kWh, usage was lower. Well, maybe my LWZ needs mainainance but I believe there is an out side temp for which counts: 6 kWh * time x < 1.5 kWh * time y. That's what I would like to determine.


Zitat von: willybauss am 08 Mai 2014, 15:35:44
The setting of room influence is also related to the physical characteristics of your house, e.g. phase shift (=time delay between a temperature change happening outside and the point in time when it arrives on the room side). If your house is built from heavy stones you should keep the room influence low. Otherwise it can take too long to heat up, when the room sensor detects under temperature. Stones have a big heat storage capacity, needing lots of energy to heat them up - and the THZ has just 6kW ...

Since our both houses have completely different physical characteristics, the ideal settings might differ too. I do not have a "stone buffer".

Zitat von: willybauss am 08 Mai 2014, 15:35:44
Another thing causing higher room temperatures is reading newspaper at night :-) My lamp uses up to 150W, visible on the thermometer within 15 minutes.

And I thought you're the king of energy efficiency here... ;)

Zitat von: willybauss am 08 Mai 2014, 15:35:44
Often forgotten influences:
- hydraulic adjustment (as I described above)
- use of room thermostats instead of open heating circles
- wrong spread of heat circle temperatures (=difference between flow temp and return temp); should be approx. 5° when using a underfloor heating

Not sure how to influence the spread. Mine is definitely lower. more like 3-4°.
Completely agree about the thermostats
hydraulic adjustment...For now I trust the setting the builder has provided me with. I also do not want the same temps in every room of the house. Bed rooms therefore have low flow rates, bath room and 3 living room circuits have how rates of flow.

thanks for the useful discussion, even though it is a bit off the forum topic.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Mai 2014, 17:43:55
Hi Tom
>> thanks for the useful discussion, even though it is a bit off the forum topic.
I also like the discussion and I do not care if it is a little off topic.
Go on, share your experience and config setting.
The module development 00_THZ is running really fast also because I am learning more on the heatpump from you.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 08 Mai 2014, 20:01:01
Zitat von: immi am 08 Mai 2014, 17:43:55
Hi Tom
>> thanks for the useful discussion, even though it is a bit off the forum topic.
I also like the discussion and I do not care if it is a little off topic.

Thanks for letting the discussion go on.

I also have a house with a balloon framing structure and a basement (Fingerhaus too ;) ). As I didn't want to spent ~6k € extra  - which would never have amortized  - I "only" reached KfW62...
But I wouldn't count to much on those KfW rankings.

As the last winter wasn't really a winter, the heat pump didn't use the booster at al. So I have a lack of experience on this poitn. But what is driving me - besides of laziness  ;) - in monitoring the heat pump, is to find a way to use my self-made solar energy in the best way for the heat pump.

About the booster and the compresser bivalent point.
For me it is plausible that the booster can work more efficient at certain levels higher than the given bivalency point. With the bosster you easliy can raise room temperatures 1-2K whereas the compressor has to struggle to get enough enery out of the air to manage to produce 0.1 - 0.5 K.
So this is also a point wehre it is usefull to know about the energy consumption of the heat pump, to be able to decide at which temperatures what form of energy production works most efficient.



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 20:53:15
Zitat von: houseowner123 am 08 Mai 2014, 17:05:09
There are the differencse: No stones in my house, it is wooden based house (Fingerhaus) with multilayered thin insulation.
Basically same construction than mine, beside my 6cm thick stone floor where the underfloor heating is built in.
Zitat
No, they will never amortize.
I thought so too and therefore filled the roof with PV cells. But meanwhile I see from the logged data that I coud save ~150€ p.a. with solar cells (warm water plus heating support). And meanwhile the government supports installation with up to 1500€, so the calculation might look different now.
Zitat
When I olwered bimodal point from -10°C to -6°C the daily usage dropped by 5 or 6 kWh. Even though the booster runs with 6 kWh, usage was lower. Well, maybe my LWZ needs mainainance but I believe there is an out side temp for which counts: 6 kWh * time x < 1.5 kWh * time y. That's what I would like to determine.
sounds very interresting indeed
Zitat
Not sure how to influence the spread. Mine is definitely lower. more like 3-4°.
Simply reduce power of the heat circuit pump - which additionally saves energy. To do so you need to remove the left front housing of the THZ. Then you will see the regulators on the water pumps. To ease it up I drilled a small hole into the housing, so I do no more need to remove it, to just turn the regulator.
And when the housing is removed anyway you can add some more isolation around the DHW container. This reduced the energy loss of the DHW container by 30 ... 40%. Water needs to heat up just once per day if nothing is used.
Zitat
hydraulic adjustment...For now I trust the setting the builder has provided me with.
You will see as soon as you stop using the thermostats.
Zitat
I also do not want the same temps in every room of the house.
Basically no problem to reduce a room's temperature, just reduce the flow. What not really works is a significantly higher temperature in e.g. bath room. With my setup its just possible to have it approx. 1° higher than the other rooms.


An additional very cheap solution to save energy: simply remove the outside temp sensor from north side of the house and mount it at the north eastern corner, so that sunshine can heat it up early in the morning. So you can tell the THZ that the sun will do the job for the rest of the day (if you have big windows on south and east side, like me). Check blue and black curves in attached screen shot. As soon as the sun shines on the sensor the heatSetTemp goes dow. Nevertheless the inside temp goes up during the day. On cloudy on foggy days it works as before.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 Mai 2014, 20:57:16
for me, additional price for 5,2m² solar cells on the roof was 3000EUR after a hard negotiation...
AND i love it to see also on cloudy days (even in december) the DHW temp is climing on 50-60°C without having the DHW compressor working ;)
we've got 5000EUR from the government for having the energy consumption reduced to KFW40 level
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 21:13:06
Zitat von: micomat am 08 Mai 2014, 20:57:16
AND i love it to see also on cloudy days (even in december) the DHW temp is climing on 50-60°C without having the DHW compressor working ;)
flat panel or vaccum tube cells?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 08 Mai 2014, 21:30:48
flat Panel. here are some hail Storms Every Summer ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 08 Mai 2014, 21:37:22
Zitat von: micomat am 08 Mai 2014, 20:57:16
for me, additional price for 5,2m² solar cells on the roof was 3000EUR after a hard negotiation...
Including the upgrade for the THZ to al SOL version?

Zitat von: micomat am 08 Mai 2014, 20:57:16
AND i love it to see also on cloudy days (even in december) the DHW temp is climing on 50-60°C without having the DHW compressor working ;)
On those days my PV produces al least ~10 kWh, that can be used for the compressor...so there has to be some maths whichs comes out cheaper after all.
Acutally I don't know...

Maybe for some of you this users-maintenance-manual which I found in a blog might be interesting:
http://hausnummer17.blogspot.de/2014/01/durchfuhrung-der-wartungsarbeiten-fur.html
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Mai 2014, 21:54:02
Zitat von: micomat am 08 Mai 2014, 20:57:16
for me, additional price for 5,2m² solar cells on the roof was 3000EUR after a hard negotiation...
AND i love it to see also on cloudy days (even in december) the DHW temp is climing on 50-60°C without having the DHW compressor working ;)
we've got 5000EUR from the government for having the energy consumption reduced to KFW40 level

Impressive! I did not think the panels would work on cloudy days. Nevertheless, at the time the Sol option was too pricy. The panels were 4000 and the Sol version was 2000 € more. We already had the kfw55 benefit of 4000 with 303i and since we were heavily penalized for having a basement, I am not sure if we would have even reached kfw40 levels to get the extra 1000 € bonus. But I am glad it worked out for you. Good negotiation skills!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Mai 2014, 23:32:47
I don't have solar cells, but I have the THZ with solar option (303 SOL), since it has different advantages too. So I plan to add solar panels to the southern wall sooner or later.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Mai 2014, 00:45:51
Dear all
I was very diligent:
I uploaded v0.096 //////// tomorrow update and restart
changelog:
1) RoomInfluenceHC1 from 0 to 100%
2) lots of new energy parameters (I did not go downstairs to check them)

have fun
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 Mai 2014, 06:28:20
Zitat von: lwzler am 08 Mai 2014, 21:37:22
Including the upgrade for the THZ to al SOL version?
On those days my PV produces al least ~10 kWh, that can be used for the compressor...so there has to be some maths whichs comes out cheaper after all.
Acutally I don't know...

yep, with all upgrades and so. btw, we also have 5kW solar power on the roof :D so i love sunny days.
and we also have a basement. a house without a basement is not a real house :D

immi, thanks a lot. will test and update the wiki today.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 09 Mai 2014, 10:43:58
Thanks, immi!  :)

Coming back to the modul..I have three questions:
Question 1: I am a little frustrated that the new heating parameters are never updated unless I do restart. Here is my config:

attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sHeatRecoveredDay 28800
attr Mythz interval_sHeatDHWDay 28800
attr Mythz event-on-change-reading .*


What I am doing wrong?

Second: Is there a way to count or better to add up the times of the activity for the pumps. So, when they active they are attributed the value 1; when inactive they get a zero. I would like to sum up per day the time of activity for heating circuit and the DWH pump (0:00-24:00). Why? sHistory rounds to the full hour which is great if you want to judge things over the course of a month. For the determination, when a booster beats the pump in energy consumption, this kind of finer time resolution is essential.

Third: How do you fill the headers of the diagrams (e.g. the heat curve) with all these nice reading. Willy has it too. What is the code for that?

Thank you so much!
Tom!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Mai 2014, 11:04:36
Hi Tom
First: easy--> you get a periodic update for a reading only if you set in your config an interval or a AT. How shal THZ know how often you want to refresh?
Second: not a easy task
Third: easy --> read the wiki: http://www.fhemwiki.de/wiki/Plots_erzeugen

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 09 Mai 2014, 13:04:49
Zitat von: immi am 09 Mai 2014, 11:04:36
First: easy--> you get a periodic update for a reading only if you set in your config an interval or a AT. How shal THZ know how often you want to refresh?

I am confused. The code line says there is an interval of 28800 seconds for both parameters. Why aren't they updated then at all. I don't understand.

Zitat von: immi am 09 Mai 2014, 11:04:36
Third: easy --> read the wiki: http://www.fhemwiki.de/wiki/Plots_erzeugen
I read this. The parameter is <TL>. That's all the instruction says. But how do get an actual reading in the title? Can you please provide just one plain example out of a gplot log? I figure out the rest.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 09 Mai 2014, 13:35:02
@immi

Thanks a lot for that impressive update!  ;D

All values are set correctly - according to my LWZ's display.

Just the value "sboostHCtotal" always gives me an error, when I'd like to check => " msg2  new error code"

@all
If some of you have a extra power meter (heat pump energy for example), would it be possible to check if the values the THZ delivers on consumption are almost ok?

Zitat von: houseowner123 am 09 Mai 2014, 10:43:58
attr Mythz interval_sGlobal 300
attr Mythz interval_sHeatRecoveredDay 28800
attr Mythz interval_sHeatDHWDay 28800


What I am doing wrong?

Your interval is set to 28800 seconds = 8 hours
So the update is gonna work, but you'll only update those values 3 times a day

€dit:
Zitat von: houseowner123 am 09 Mai 2014, 13:04:49
I am confused. The code line says there is an interval of 28800 seconds for both parameters. Why aren't they updated then at all. I don't understand.

They are firstly read from the THZ, when FHEM starts up, then the second reading is 8 hours later.
Did you check the logfile, when the first reading after startup was made? As the update for those values is from today maybe your 8 hours are not over yet?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Mai 2014, 14:27:58
Zitat von: houseowner123 am 09 Mai 2014, 13:04:49
I read this. The parameter is <TL>. That's all the instruction says. But how do get an actual reading in the title? Can you please provide just one plain example out of a gplot log? I figure out the rest.
You have found the right place; do not stop
Variable    <TL>
Nutzung in gplot-File set title '<TL>'       
Füllung mit inhalt in fhem.cfg  attr weblink title "Dies füllt den Platzhalter"

e.g.
define MyNICEPlot SVG ....................
attr MyNICEPlot  title "THIS IS THE TITLE"

immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 Mai 2014, 18:51:08
new readinga are perfect :) wiki update will follow soon.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Mai 2014, 19:22:56
Zitat von: lwzler am 09 Mai 2014, 13:35:02
Just the value "sboostHCtotal" always gives me an error, when I'd like to check => " msg2  new error code"

fixed in v 0.097, just uploaded
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 09 Mai 2014, 21:11:10
@Immi: one word - WOW! All I ever wanted from the The readings. Answers my question nr. 2 completely.  8)

@lwzler: thanks for the hint with the 8 hrs. All is working. I was just too impatient. I habe an extra power Meter and will report about tzhe lwz accuracy.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Mai 2014, 23:06:30
Zitat von: lwzler am 08 Mai 2014, 20:01:01
About the booster and the compresser bivalent point.
For me it is plausible that the booster can work more efficient at certain levels higher than the given bivalency point. With the bosster you easliy can raise room temperatures 1-2K whereas the compressor has to struggle to get enough enery out of the air to manage to produce 0.1 - 0.5 K.
I  do not agree.
Let us avoid using the word "efficiency", bad word (used otherwise in thermodinamic).
Let us define performance:
Performance = heat_transferred_inside_house/electrical_energy_taken_from_the_grid
The booster has "per definition" a performance of 1; It is a simple resistance.
The heat pump has "per definition" a performance higher than 1.

You have a booster, not because it has a better performance (as defined above), but because the heat pump "struggles" (as you said) as its performance approaches one.
This struggling has 2 consequences: your heatpump is not able to deliver enough energy to keep an nice temp inside and/or your heatpump  could wear out.

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 Mai 2014, 20:02:27
wiki updated :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 13 Mai 2014, 10:58:31
Hi,

again Immi great work.

Just for clarification what exactly is the meaning of the values?

ElectrHCDay - Is it the Electric Power needed for Heating for a Day ( excluding water heating)?
HeatHCDay  - Is this the effective energy needed, means due to the THZ performance of >1 this is eefectivly the ElctrHCDay*performance on that day ?

BoostHC Total - Is then the additional Electrical Energy when the Heatpump used the Booster as well ( usually if it is too cold outside)

HeatRecoveredDay - Is the gained Energy only from the Fan ?  or
                                  is this the difference between Electr... and Heat for both HC and DHW?

                                 In case it is the Fan how does it work? If the Fan is running, fresh air from outside get heated based on the "old inside Air which gets blown out, however you will never reach more heat on the inside than the heat you have blowing out, so you may reach a efficiency of 80% or 90% or 95% but if you switch off the Fan you loose even less heat. Does now Heat Revcoverd meassure somehow for the period where the fan is "on" the DeltaTempreature "outside" to "filtered outside" to calculate the energy gained?

Thaks for explanation. (May be something which could be captured on the WIKI as well)

Thanks for clarification.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 Mai 2014, 11:21:53
Yes it makes sense to describe properly all sXX values
please help Markus to find a nice wording for them
immi

"sSol"   => {cmd2=>"16"},
"sDHW"   => {cmd2=>"F3"},
"sHC1"   => {cmd2=>"F4"},
"sHC2"   => {cmd2=>"F5"},
"sHistory"   => {cmd2=>"09"},
"sLast10errors"   => {cmd2=>"D1"},
"sGlobal"   => {cmd2=>"FB"}, #allFB
"sTimedate" => {cmd2=>"FC"},
"sFirmware" => {cmd2=>"FD"},
"sBoostDHWTotal" => {cmd2=>"0A0924", cmd3=>"0A0925", unit =>"kWh"},
"sBoostHCTotal"   => {cmd2=>"0A0928", cmd3=>"0A0929", unit =>"kWh"},
"sHeatRecoveredDay" => {cmd2=>"0A03AE", cmd3=>"0A03AF", unit =>"Wh"},
"sHeatRecoveredTotal" => {cmd2=>"0A03B0", cmd3=>"0A03B1", unit =>"kWh"},
"sHeatDHWDay" => {cmd2=>"0A092A", cmd3=>"0A092B", unit =>"Wh"},
"sHeatDHWTotal" => {cmd2=>"0A092C", cmd3=>"0A092D", unit =>"kWh"},
"sHeatHCDay" => {cmd2=>"0A092E", cmd3=>"0A092F", unit =>"Wh"},
"sHeatHCTotal"   => {cmd2=>"0A0930", cmd3=>"0A0931", unit =>"kWh"},
"sElectrDHWDay" => {cmd2=>"0A091A", cmd3=>"0A091B", unit =>"Wh"},
"sElectrDHWTotal" => {cmd2=>"0A091C", cmd3=>"0A091D", unit =>"kWh"},
"sElectrHCDay" => {cmd2=>"0A091E", cmd3=>"0A091F", unit =>"Wh"},
"sElectrHCTotal"

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 13 Mai 2014, 13:47:24
I can't say for sure but it seems like ElectrHCDay and HeatHCDay overcalculate the primary energy that used. Is the energy of the fan activity and controling somewhere in there? Anyway my meter reading (2-2,3 kWh/d) so far is always lower than HeatHCDay+HeatHCDay. Especially when I consider that 1 kWh alone is attributed to LWZ controling and stage 1 air (equals 40 W *24 hrs=960 W/day). What are your experiences?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 Mai 2014, 13:55:00
well tom

I would consider to compare your electricity meeter with
sBoostHCTotal +sBoostDHWTotal + sElectrDHWTotal + sElectrHCTotal.

just make a reading today and in 2 weeks.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 13 Mai 2014, 13:57:54
Hi immi,

I will do so and right down the numbers and wait a week or two and then report back.
The booster is never used and doesn't change, that's why I didn't include it in the equation.
Is there any way to get one decimal point after the comma from the sHistory readings?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 Mai 2014, 14:04:14
Zitat von: houseowner123 am 13 Mai 2014, 13:57:54
Is there any way to get one decimal point after the comma from the sHistory readings?
Not to my knolwdge.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 13 Mai 2014, 15:39:45
hey all,

i will add the descriptions to the wiki. but i will just copy and paste the official descriptions from the installation manual. i don't see any benefit in finding own words for the values.

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Mai 2014, 22:42:33
Zitat von: houseowner123 am 09 Mai 2014, 13:04:49
... The parameter is <TL>. That's all the instruction says. But how do get an actual reading in the title? Can you please provide just one plain example out of a gplot log? I figure out the rest.
I'm going to provide you with my config file and plot files here in the forum soon, since I've been asked for such details more than once within last days. It might be a good idea to share our plot and/or dashboard solutions in order to give the others some hints for own improvements.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 14 Mai 2014, 08:31:47
Hi ,
@ Immi,  « Antwort #442 am: 05 Mai 2014, 23:29:28 » worked perfectly, Thanks.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 14 Mai 2014, 14:10:25
Hi together,

I've searched for a solution for basement ventilation and got caught by fhem. And as I also have a Stiebel Eltron LWZ 303 integral, I've found your thread and your wiki. First of all, thank you for all your work, great job!

A year or two ago, I've tried the heatpumpmonitor with my Raspberry Pi from Robert Penz without any luck. It was never connecting with the LWZ. As I had no time for any error searching, I stopped with the heatpumpmonitor. Today I found the reason in your thread, the reason was the wrong baudrate within the USB connection. Maybe Markus can add such a information in the wiki (Connection via USB, the Baudrate can be 115200 or 57600).

After I found your thread and all the informations regarding fhem, I've started with my Raspi from scretch. Put a new image on the sd card, installed fhem, updated everything to the latest version and finally installed (set) everything in the fhem.cfg for the THZ. As mentioned above, first the baudrate was not ok, after I switched to 57600 the connection was working and the data of my LWZ were fetched.

And now comes the "But": But, the THZ module is getting data for a view minutes, at some point, FHEM crashes. So I put the verbose level to 5 and tried it several times. Always when the module tries to get some 'programFan_.....' (not always the same) it crashes.
Then I've checked the Raspberry Pi, as I found the information in the Net, there could be a problem with the power of the USB-port. So I've changed to a powered USB-Hub. -> Same problem.
As I use a USB-cabel-extender, I now just use a 3 meter USB-cabel plugged in to the 'self-powered-USB Hub'. -> Still the same problem.  :-\

I'm just using a 4GB class 6 SD-Card, maybe the card is to slow?? I've ordered a high speed 8gb class 10 card yesterday, which should be delivered today, so I also can eliminate that problem this evening. But as the Raspberry Pi is still running, I can't imagine, that this will fix my problem.

I also do not have any further senders/receivers set up in the FHEM. Just a fresh installation with just the THZ/LWZ module...

So, that's why I ask you! Had anybody a similar problem or do you have any idea, what could be the problem?

Thank you for your help!
Best regards
Jakl

Here the last entries of my THZ and FHEM log files with verbose 5.
Zitat
2014-05-14_13:40:34 Mythz programFan_Sa-So_0: 00:00--24:00
2014-05-14_13:40:34 Mythz pHolidayEndMonth: 1
2014-05-14_13:40:35 Mythz p01RoomTempDayHC2: 20.5 °C
2014-05-14_13:40:35 Mythz p37Fanstage1AirflowInlet: 80 m3/h
2014-05-14_13:40:36 Mythz programDHW_We_2: n.a.--n.a.
2014-05-14_13:40:36 Mythz programFan_Mo-Fr_1: 00:00--24:00

Zitat
2014.05.14 13:40:36 5: Triggering Mythz (1 changes)
2014.05.14 13:40:36 5: Notify loop for Mythz programFan_Mo-Fr_1: 00:00--24:00
2014.05.14 13:40:36 4: eventTypes: THZ Mythz programFan_Mo-Fr_1: 00:00--24:00 -> programFan_Mo-Fr_1: .*:.*--.*:.*
2014.05.14 13:40:36 5: Mythz sending 02
2014.05.14 13:40:36 5: SW: 02
2014.05.14 13:40:37 5: Mythz sending 0100FCFB1003
2014.05.14 13:40:37 5: SW: 0100FCFB1003
2014.05.14 13:40:37 5: Mythz sending 10
2014.05.14 13:40:37 5: SW: 10
2014.05.14 13:40:37 5: Mythz sending 10
2014.05.14 13:40:37 5: SW: 10
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 Mai 2014, 14:39:21
Hi Jakl,

welcome aboard :)
I just added the information to the wiki with the 57600baud rate. Thanks.

Can you post your fhem.cfg? So maybe we can find the error somewhere there? And also interesting would be if your THZ module version is up2date. So when did you load the version or did you try an "update" of fhem?

The loop message looks very strange to me...

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 14 Mai 2014, 15:06:16
Hi Markus,

at the end you will find my fhem.cfg, I've just deleted the security-sections from the web, webphone and webtablet definitions.

I've updated the linux distribution of my raspberry pi to the latest releases. And I've updated FHEM after installation to the latest packages via the update command in FHEM!
The software version of my LWZ 303 is 3.19.

Thank you and best regards,
Jakl


attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global motd SecurityCheck:\
\
WEB,WEBphone,WEBtablet has no basicAuth attribute.\
telnetPort has no password/globalpassword attribute.\
\
Restart fhem for a new check if the problem is fixed,\
or set the global attribute motd to none to supress this message.\

attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global userattr devStateIcon devStateStyle icon sortby webCmd
attr global verbose 5

define telnetPort telnet 7072 global
attr telnetPort password 2gr84u2

define WEB FHEMWEB 8083 global
attr WEB stylesheetPrefix ios7

define WEBphone FHEMWEB 8084 global
attr WEBphone stylesheetPrefix smallscreen

define WEBtablet FHEMWEB 8085 global
attr WEBtablet stylesheetPrefix touchpad

# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog

define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log

define eventTypes eventTypes ./log/eventTypes.txt

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create


define Mythz THZ /dev/ttyUSB0@57600 # oder (/dev/ttyXXX)
attr Mythz interval_sGlobal 300 # Internes Polling Intervall 5min
attr Mythz interval_sHistory 28800 # Internes Polling Intervall 8h
attr Mythz interval_sLast10errors 120 # Internes Polling Fehlerspeicher
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 14 Mai 2014, 15:11:58
Zitat von: willybauss am 13 Mai 2014, 22:42:33
I'm going to provide you with my config file and plot files here in the forum soon, since I've been asked for such details more than once within last days. It might be a good idea to share our plot and/or dashboard solutions in order to give the others some hints for own improvements.

Hi Willy,

that would greatly appreciated from every newbie. I have the largest problems creating the plots I want. I can only get so much from the wiki sites. It helps me to read a code, see it's effects and then I understand the language much better.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Mai 2014, 16:32:57
Zitat von: Jakl am 14 Mai 2014, 15:06:16
The software version of my LWZ 303 is 3.19.
3.19 could be interesting :)

I do not think it has something to do with cables or speed of the rasPi.

Start deleting  autocreate and  initialUsbCheck from config-file.
Now we want to disable the automatic refresh at FHEM start. Edit the code of 00_THZ.pm like this: Comment out lines 268 to 273: add # at the beginning of the line


sub THZ_Refresh_all_gets($) {
  my ($hash) = @_;
  RemoveInternalTimer($hash);
  my $timedelay= 5; #strart after 5 seconds
  #  foreach my $cmdhash (keys %gets) {
  #  my %par = ( command => $cmdhash, hash => $hash );
  #  RemoveInternalTimer(\%par);
  #  InternalTimer(gettimeofday() + ($timedelay++) , "THZ_GetRefresh", \%par, 0);
  #   $timedelay += 0.3;
  #  }
}


then restart fhem: it should not crash anymore.
Now test one reading after the other manually
e.g. get Mythz pOpMode

one or more of them should crash the FHEM
I  have to understand which one, and disable it for you

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 14 Mai 2014, 17:07:19
@Jakl, if you need German support for doing this, just send me a PN so i can help you ;)
as far as i know, you are the first one trying to connect with a firmware bevore 4.09

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 14 Mai 2014, 22:17:42
As promised here are my config files and a few screen shots showing how it looks like finally.
Would be nice to see yours as well.

Plot3_Fans.jpg shows the result of a filter replacement at approx. 17:30. It might be a good idea to trigger a reminder for filter replacement using these values (e.g. THZ sends you an email as soon as a defined power level of fans is reached) instead of the icon on the THZ's display. Drawback of the THZ's own solution is that the "filter is ok" value gets a reset on every power cycle. So if you need to switch off your heatpump fequently for any reason you will never get reminded for filter change.

Restart.sh is a small shell script, which is called by a cron job  in order to stop and restart fhem once per day. This improves  system stability a lot and works even in case of a "hanging" fhem process.

Willy

PS:
I need to mention that Plot2 is a 1:1 copy of immi's plot, not originated by me.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 15 Mai 2014, 09:59:58
@Markus: Thank you, but my english is not that bad! :-)

@immi:
As expected, the SD card was not the problem. Also after deleting autocreate and  initialUsbCheck the system still crashed.
I will do your recommended modifications in THZ_Refresh_all_gets and retrieve the readings manually. And I will try to enter some error and exception handling in the code. I'm software engineer, but I'm more familiar in the Windows C# world and this are my first steps with Pearl. Maybe I can help you a little bit to improve the code.

It will take some time to get this done.  :-\

Regards,
Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Mai 2014, 10:08:38
Hi Willy
this looks great

Hi Jakl
Excellent, I will shame for my coding :)
I am not a software guy, and I learned perl while writing this module.
I made some simulations in Fortran and C, 100 years ago.
Going to Perl, was a shock. All this freedom looked like anarchy :)

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 10:12:06
@ Jakl:
My experience prior to fhem and even prior to heatpumpMonitor (which I used for months successfully) is that the heatpump needs some delay between the send/receive communications. I checked it out by using a macro capable terminal software, which had the possibility to add delays inside the communication strings. Later on I confirmed stable communication by using a bash script to get the sGlobal values into a file. As far as I remember the delays in my case (THZ 303 SOL, ver. 4.19) have to be between 10ms and 500ms. Possibly the 10ms is not enough in your case.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 15 Mai 2014, 10:56:41
Zitat von: micomat am 13 Mai 2014, 15:39:45
but i will just copy and paste the official descriptions from the installation manual.

Is there a manual with the items "sElectrDHWDay" etc. descriped? Untill now I didn't find them in any manual  :-[

For this values I had asked the Stiebel Eltron service technician who did the initial setup for my LWZ. He statet that those vlaues should be accurate as the LWZ should have an internal power meter.
But another technician told me the oposite...

An information on USB connection to the LWZ:
I am using (a) 10m USB Cable (5m USB Cable + 5m extension; unpowered; unamplified) to connect the LWZ with my RasPi. The connection works stable without any signs of porblems.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 12:16:16
As far as I know Markus uses the english version of the THZ manual and takes the namings from the P-parameter description table - slightly modified by e.g. prefix s or p of course.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 15 Mai 2014, 12:28:45
Zitat von: lwzler am 15 Mai 2014, 10:56:41
Is there a manual with the items "sElectrDHWDay" etc. descriped? Untill now I didn't find them in any manual  :-[

For this values I had asked the Stiebel Eltron service technician who did the initial setup for my LWZ. He statet that those vlaues should be accurate as the LWZ should have an internal power meter.
But another technician told me the oposite...


Currently all sElectr..values point to inaccuracy. But I will wait 4 more days as immi suggested to determine how bad the diviation from the real meter readings is.

@willy: Thanks so much for codes and graphs.  :) It has already helped me tremendously. One question reagarding passive cooling: In order for this to be efficient (in-house-circulation) I need to turn off the normal ventilation, right?

@lwzler: I have version 4.09 which is the second oldest tested here and it required a delay of 100-200 ms. I use a 3 m long USB cable. If nothing helps with the crashs you might, for test purposes, try a shorter USB cable.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 Mai 2014, 12:40:54
Zitat von: willybauss am 15 Mai 2014, 12:16:16
As far as I know Markus uses the english version of the THZ manual and takes the namings from the P-parameter description table - slightly modified by e.g. prefix s or p of course.

yep, when i have some time for that project ;) but i didn't forget it

ZitatI am using (a) 10m USB Cable (5m USB Cable + 5m extension; unpowered; unamplified) to connect the LWZ with my RasPi. The connection works stable without any signs of porblems.

in my point of view that "could" cause a problem but must not. the quality of the cable is a big point in this case. when there are interferences on a long cable it can cause problems.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 15 Mai 2014, 13:32:17
Zitat von: houseowner123 am 15 Mai 2014, 12:28:45
@lwzler: I have version 4.09 which is the second oldest tested here and it required a delay of 100-200 ms. I use a 3 m long USB cable. If nothing helps with the crashs you might, for test purposes, try a shorter USB cable.

Maybe something got mixed up here. I am not running into any problems with this configuration. For me everything works very nicely with no crashes at all.
I postet my config as for "Jakl" the USB connection was discussed as a pssible problem.

For me the LWZ<->Raspi combination seems to be very robust against USB problems, as my configuration is way out of the norm (max. 3m length for USB cables).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 14:29:37
Zitat von: houseowner123 am 15 Mai 2014, 12:28:45
One question reagarding passive cooling: In order for this to be efficient (in-house-circulation) I need to turn off the normal ventilation, right?
No, not at all. First of all you should have a look into the installation manual, where it's described in deep detail.
Basically as soon as you switch the passive cooling to anything <> 0 one of both ventilation fans is switched off, the other one runs at increased power level. Now you should open at least one window, so that in- or output ventilation can happen through the open window. This works as a bypass for the heat exchanger, so that you can really get cool air into the house at night, which is no more heated up while passing through the heat exchanger.
Advantage against the "Sommerkassette" (which replaces the heat exchanger by a simple bypass) is, that you're still able to ventilate the house during day time (when it's hot outside), and the heat exchanger keeps the cold inside. Using a "Sommerkassette" instead would mean you have to switch off the ventilation completely during hot day time, to avoid heating up the inside.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 15 Mai 2014, 14:40:24
Hi,

never heard of sommerkasette. You mean when it is hot I just chnage the Programm times for the Fan, from some day hours into night hours, correct?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Mai 2014, 14:53:21
Dear all
it is right, we have to find a nice concept for summer.

I was thinking to the following:
Leave window open (tilted) in the basement and

30 minutes drawing the air from the 2 bathrooms and kitchen: this cools down fast 70% of the house (exeption of the bedrooms).
30 minutes blowing the air to the bedrooms.

this can be achieved easily without programming: just switch "p75passiveCooling" from 1 to 2 every 30 min....
theoretically.

maybe you have better suggestions.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 15 Mai 2014, 15:14:44
12.1.1 Passivkühlung
Die Passivkühlungwird freigegeben, wenn die Außentemperatur mindestens 2 Stunden lang 3 K über der Raumsolltemperatur liegt. Sinkt dann die Außentemperatur um 3 K unter die Raumsolltemperatur wird die Passivkühlung aktiviert: Steht ,,PASSIVKÜHUNG"auf
1, wird der Zuluftlüfter abgeschaltet und die Leistung des Abluftlüfters um 20 %erhöht. Dadurch wird über die geöffneten Fenster kühle Außenluft in Wohnung gesaugt.
Bekommt,,PASSIVKÜHLUNG" den Wert 2, wird der Abluftlüfter ab - geschaltet und die Leistung des Zuluftlüfters um 20 % erhöht. Hier müssen Sie die Fenster nicht öffnen. Diese Variante ist allerdings weniger effektiv und funktioniert nicht bei sehr dichten Häusern (d.h. wenn beim Blower-Door-Test die Luftaustauschzahl n50 <= 1 ist. Spätestens um 10 Uhr morgens wird die Passivkühlung beendet.
12.1.2 Passivkühlung über Fortluft
Bei der ,,PASSIVKÜHLUNG ÜBER FORTLUFT" [MENÜ/LÜFTUNG] wird die Luft über ein Klappensystem direkt aus dem Keller gesogen. Die
Klappen können über den Ausgang x 18-2 (,,Lüftung Nacht") angesteuert werden. Die Freigabekriterien sind dieselben wie bei der
Passivkühlung.


This is straight from the manual. Thanks, willy! ;)
So Passive cooling stage 2 is no option for most of us because of our BDT values. So, what immu suggests as alternative is Passikühlung über Fortluft? What is the advantage of passive cooling stage 1? The difference between Abluft and Fortluft is not clear to me. It seems that passive cooling is already temperature- and time regulated. Wouldn't FHEM then just mess with those LWZ/THZ internals?

I have a Sommerkassette, it can be ordered from Tecalor, cost about 80 €. In terms of cooling the house down at night I do not find it effective. Only after a 5 K difference between in- and outside temp you get a 1K lower temp in the morning. In tropical nights (min temp 20°C) it not effective anymore and you open all your windows anyway and move into the cool but moist basement. ;)

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 15 Mai 2014, 15:15:46
Did anybody install http://www.tecalor.de/dam/downloads/produkte/lueftungssysteme/THZ-303-403-SOL/172090-37758-8875_THZ_303-403_de/bedienung---installation-luftungsgerat-thz-303-403-sol.pdf (http://www.tecalor.de/dam/downloads/produkte/lueftungssysteme/THZ-303-403-SOL/172090-37758-8875_THZ_303-403_de/bedienung---installation-luftungsgerat-thz-303-403-sol.pdf) "15.2.4 Anschluss Außenluft Wohnungslüftung optional" on page 61?
Or can anyone explain the funktion.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 15 Mai 2014, 15:27:47
Zitat von: Gassi am 15 Mai 2014, 15:15:46
Did anybody install http://www.tecalor.de/dam/downloads/produkte/lueftungssysteme/THZ-303-403-SOL/172090-37758-8875_THZ_303-403_de/bedienung---installation-luftungsgerat-thz-303-403-sol.pdf (http://www.tecalor.de/dam/downloads/produkte/lueftungssysteme/THZ-303-403-SOL/172090-37758-8875_THZ_303-403_de/bedienung---installation-luftungsgerat-thz-303-403-sol.pdf) "15.2.4 Anschluss Außenluft Wohnungslüftung optional" on page 61?
Or can anyone explain the funktion.

Interesting. Never seen this before. Either if you do not want use the ventilation system at all or to provide a spacial alternative to the main inlet.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 15:44:33
Zitat von: Heiner am 15 Mai 2014, 14:40:24
Hi,

never heard of sommerkasette. You mean when it is hot I just chnage the Programm times for the Fan, from some day hours into night hours, correct?
no, not at all. Please check the manual first.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 15:48:05
Zitat von: immi am 15 Mai 2014, 14:53:21
this can be achieved easily without programming: just switch "p75passiveCooling" from 1 to 2 every 30 min....
theoretically.
My experience shows that 30 minutes is MUCH too less to have any effect, even in a wooden house. In a house made from stone it's even worse. We should talk about multiple hours instead.
Using mode 2 you can open the windows as well of course. But in this case the fresh air goes through the whole ventilation pipe system before it comes into the target room, and during this - possibly long - travel it already heats up a lot.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 15:55:38
Zitat von: houseowner123 am 15 Mai 2014, 15:14:44
What is the advantage of passive cooling stage 1?
fresh air comes directly from the outside, without any detour through the piping system, which would heat the fresh air up before it reaches the room.
Zitat von: houseowner123 am 15 Mai 2014, 15:14:44
The difference between Abluft and Fortluft is not clear to me.
Forget about the "Fortluft" alternative. I discussed it with a support gui. It's not worth to be mentioned at all. Mode 1 and 2 are the only useable options.
Zitat von: houseowner123 am 15 Mai 2014, 15:14:44
It seems that passive cooling is already temperature- and time regulated. Wouldn't FHEM then just mess with those LWZ/THZ internals?

Exactly. The THZ's own logic will prohibit any "misuse". To work around it you would need to switch the fans manually (or by "low level" fhem switching commands) on/off and to specifig power levels. Sounds dangerous: as soon as fhem gets out of order you're lost.
Zitat von: houseowner123 am 15 Mai 2014, 15:14:44
I have a Sommerkassette, it can be ordered from Tecalor, cost about 80 €. In terms of cooling the house down at night I do not find it effective. Only after a 5 K difference between in- and outside temp you get a 1K lower temp in the morning. In tropical nights (min temp 20°C) it not effective anymore and you open all your windows anyway and move into the cool but moist basement. ;)
That's what I expected, and the reason to not install it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Mai 2014, 16:22:56
Zitat von: willybauss am 15 Mai 2014, 15:48:05
My experience shows that 30 minutes is MUCH too less to have any effect, even in a wooden house. In a house made from stone it's even worse. We should talk about multiple hours instead.
Using mode 2 you can open the windows as well of course. But in this case the fresh air goes through the whole ventilation pipe system before it comes into the target room, and during this - possibly long - travel it already heats up a lot.
I think we have a comunication problem Willy: my suggestion was to toggle from mode 1 to mode 2 every 30 min.
this means during the night you have 4hours  mode 1 and 4hours mode 2
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 15 Mai 2014, 16:34:40
Immi,

But in passive mode 2, in high efficency houses like ours, that are wrapped in PVC (our BDT is 0.8...), you would reach a steady-state pretty fast and no air would move in. You would only wear out the ventilators.
Can somebody enlighten me what the Passivkühlung with Fortluft actually does and does it have to do with a basement as described in the manual?
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Mai 2014, 17:31:51
Hi Tom
as written before
Leave window open (tilted) in the basement and
30 minutes drawing the air from the 2 bathrooms and kitchen: this cools down fast 70% of the house (exeption of the bedrooms).
30 minutes blowing the air to the bedrooms.

toggle from mode 1 to mode 2 every 30 min.
this means during the night you have 4hours  mode 1 and 4hours mode 2
The duty cycle could be optimized.

With mode 1 you cool down through the window tilted in the basement and get fresh air from the basement.
with mode 2 you mix up air in all room wich are not in the path.

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 Mai 2014, 18:58:03
next week the weather forecast is up to 28°C so i will test the first time the passive cooling :)
thanks to immi who made it possible to switch it from the iPhone  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Mai 2014, 22:39:10
Zitat von: immi am 15 Mai 2014, 16:22:56
I think we have a comunication problem Willy: my suggestion was to toggle from mode 1 to mode 2 every 30 min.
this means during the night you have 4hours  mode 1 and 4hours mode 2
immi
You're right. Last summer I used mode 1 the whole night. The open windows were in bedroom and living room, so (since almost the whole ground floor is one great room consisting of living room, dining room and kitchen) almost the whole house got fresh air directly from the outside through the open windows. I believe that's more efficient than togggeling between mod 1 and 2, since the flow doesn't need to be turned into other direction frequently.

Drawback of my solution is: as soon as I need to close the window in bedroom (since it's too loud outside for any reason) there's no more any fresh air in bedroom at all. I would need to switch to mode 2 manually when closing the window. Therefore my next big project in FHEM will be to check all my window sensors (I installed hidden ones, made from reed contacts and magnets during the construction phase of the house) by fhem and switch between mode 1 and 2 automatically based on the result.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 18 Mai 2014, 01:07:14
Weeks ago I wrote
Zitatwhat I do not understand at all is an obvious relation between heatSetTemp and inside humidity, see attachment. I observe such bumps in the heatSetTemp curve frequently.

Meanwhile I know the answer, which is pretty easy: As soon as I take the external display into my hand the measured humidity as well as the measured inside temp. is influenced by my body. The heating curve (roomSetTemp) reacts on the rising inside temp. That's all.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 Mai 2014, 14:33:52
That tiny little dent in the beginningbis a rise in inside temp? Why is the risE in humidity then so sharp? Must be a supersenisitiv sensor, whereas the inside temp sensor is quite the opposite. Thanks for solving that mystery.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 Mai 2014, 16:38:05
hi immi,

as i can see there were two code chances recently. could you please provide change information?

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Mai 2014, 17:57:40
Hi Markus
you notice everything:)

v0.099
- room-influence has been included in the simulation curve plot.
- Willi noticed an incosistency in the plot: to make it short:
in wintermode roomSetTemp (from  sHC1) is given from p01RoomTempDayHC1  and  p02RoomTempNightHC1   
in summermode roomSetTemp (from  sHC1) is given from  p01RoomTempDayHC1SummerMode and  p02RoomTempNightHC1SummerMode

The last 2 parameters are not documented in the manuals. Their behaviour has been confirmed empirically.
The same is valid for HC2.
It is very important to document it in the wiki.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 Mai 2014, 21:25:27
Hi immi,


thanks for the update. Since you uncovered more no more settings than present in the manual and given the stability of the program across different software version, wouldn't with the next update be the perfect opportunity to switch to version 1.0?

Also, who of FHEM THZ users owns a summer cassette?

I did my maintenance cleaning today and uses brush to clean of the ventilators which were pretty dirty after 3 years. I also cleaned out the muddy copper pan? Does anybody have an idea where this mud comes from?

back the ventilator: I noticed a dramatic drop in ventilator speed now: Input: 23-->15  and Output: 25-->17.  Could this be the result of too harsh cleaning efforts or is the speed lower with the summer cassette in place? Fan power is unchanged. Any experiences out there?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 Mai 2014, 21:58:15
Tom, 0.099 will be followed by 0.100 ;)

immi, docu will be updated tomorrow.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 Mai 2014, 22:09:06
Why keep the 0.x? This is a stable release by my standards..but ok! ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Mai 2014, 22:20:57
Hi Tom
thanks for the compliment.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 18 Mai 2014, 22:44:20
Zitat von: immi am 18 Mai 2014, 17:57:40
Hi Markus
you notice everything:)

v0.099
- room-influence has been included in the simulation curve plot.
- Willi noticed an incosistency in the plot: to make it short:
in wintermode roomSetTemp (from  sHC1) is given from p01RoomTempDayHC1  and  p02RoomTempNightHC1   
in summermode roomSetTemp (from  sHC1) is given from  p01RoomTempDayHC1SummerMode and  p02RoomTempNightHC1SummerMode

The last 2 parameters are not documented in the manuals. Their behaviour has been confirmed empirically.
The same is valid for HC2.
It is very important to document it in the wiki.

immi
Additionally I can say that these parameters cannot be changed by the THZ's user interface obviously. At least I coudn't find a way to change them. They are just visible in the ISTWERTE menu: in winter mode p01RoomTempDayHC1  is shown, in summer mode p01RoomTempDayHC1SummerMode  is shown there.
The only way to change them might be the set command of fhem.

This could get important in summer, when the question comes up which reference temperature for the inside temperature is being used by THZ's control to decide if passive cooling will be activated or not. I assume that p01RoomTempDayHC1SummerModep02RoomTempNightHC1SummerMode  is used, but that's just an assumption. T.b. confirmed experimentally in summer.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 Mai 2014, 22:57:46
by the Way... the mud is a mix of dust and condensed water  :o
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 19 Mai 2014, 00:03:26
Zitat von: immi am 15 Mai 2014, 17:31:51
Hi Tom
as written before
Leave window open (tilted) in the basement and
30 minutes drawing the air from the 2 bathrooms and kitchen: this cools down fast 70% of the house (exeption of the bedrooms).
30 minutes blowing the air to the bedrooms.

toggle from mode 1 to mode 2 every 30 min.
this means during the night you have 4hours  mode 1 and 4hours mode 2
The duty cycle could be optimized.

With mode 1 you cool down through the window tilted in the basement and get fresh air from the basement.
with mode 2 you mix up air in all room wich are not in the path.

immi

Since heat wave is coming our way, what is a good way to implement this? Would this work?


Define pass_cooling at *22:00:00 set Mythz p75passiveCooling 1,Mythz p75passiveCooling 2 on-for-timer 1800
Define pass_cooling at *08:00:00 set Mythz p75passiveCooling 0


Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 19 Mai 2014, 00:25:57
where can I get v0.099? I tried
update force
but without success; I'm still on v0.098 afterwards.


edit:
next morning it worked; I'm on 0.099 now
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 Mai 2014, 09:19:00
Zitat von: houseowner123 am 19 Mai 2014, 00:03:26
Since heat wave is coming our way, what is a good way to implement this? Would this work?

Define pass_cooling at *22:00:00 set Mythz p75passiveCooling 1,Mythz p75passiveCooling 2 on-for-timer 1800
Define pass_cooling at *08:00:00 set Mythz p75passiveCooling 0

Hi Tom It will not work
1) onfortimer works only for on-off devices; of course many tricks are possible; this evening I will test something. you can try something like this with a duty-cycle of 1to5 and a period of 1h

define at_start_cooling1 at *21:00:00 define at_repeat_cooling1 at +*{7}01:00:00 set Mythz p75passiveCooling 1
define at_start_cooling2 at *21:50:00 define at_repeat_cooling2 at +*{6}01:00:00 set Mythz p75passiveCooling 2


2) If you read carefully the manual, you will see that you do not need "set Mythz p75passiveCooling 0"; the heatpump disables automagically the cooling mode when it is again hot or at 10AM.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 20 Mai 2014, 07:41:19
Thanks so much immi. I definitely will check it out. Tonight I will checked the calculated energy values against meter readings and provide real time power usage for different stages. A bit strange: Heat recovery is still measured even though I installed the bypass. Therefore, it seems sHeatRecovered values are not measured but somehow calculated.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 20 Mai 2014, 09:39:13
Zitat von: houseowner123 am 20 Mai 2014, 07:41:19
A bit strange: Heat recovery is still measured even though I installed the bypass. Therefore, it seems sHeatRecovered values are not measured but somehow calculated.
Of course. How should the THZ know about replacing the heat exchanger against the bypass?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 20 Mai 2014, 12:16:35
Zitat von: willybauss am 20 Mai 2014, 09:39:13
Of course. How should the THZ know about replacing the heat exchanger against the bypass?

I have a theory that I still need to test. If true, the thz could know whether the by-pass is in place. But probably the engineers didn't care because the average use would never want to know about this anyway.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 20 Mai 2014, 12:53:52
exactly. What we do here is at least 120% above the THZ developers' expectations  :) .
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 20 Mai 2014, 13:17:00
@ houseowner123:
Can you confirm meanwhile that the heating curve is influenced by the inside temp. sensor? To test it you can simply heat up the sensor using e.g. a hair dryer, and then watch the heatSetTemp value. It should decrease.

I'm asking because I observed a strange behavior: I do not just have an inside temp. sensor, but additionaly a second display in living room, which has a built in inside temp. sensor as well. So now the question was, which of both is being used by the THZ control. The answer is: both.To get rid of this curious situation I tried to obsolete the inside temp sensor, but without success. As soon as I removed it, the sGlobal:insideTemp value was -60°C always, though I had expected it to be filled by the second display's sensor value instead.

@immi:

Looks like there is another hidden value to be read from the THZ, representing the inside temp. value of the second display. Do you have an idea where it might be located?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Mai 2014, 15:09:40
Hi Willy
no idea because I do not have the hardware to test it
have a look in register E8; just uncomment line 273.
Heat up your living room display and read again E8

or maybe someone can lend you an oscilloscope and you can look at the can-bus of the display
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 20 Mai 2014, 21:20:53
The results are in after exactly 7 days of measuring: actual Meter reading: 15 kWh
sElectr.DHW change: 9 kWh, sElectr HC change: 0 kWh
Ventilation stage 1 for 24/7 + powering the: 36 W.    36 W x 24 hr x 7 d= 6 kWh
Sum: selector.DWH change+ventilation+powering= 15 kWh
Q.e.d.   THZ module measures are correct sElectrical values! 8)

Remarks: I can measure real time power usage, so here are some values for the ones that are interested (303i):
Powering and controlling: 12 W
Air vent stage 1- winter cassette: 24 W
Air vent stage 1 - summer cassette: 13 W
Air vent stage 2 - summer cassette: 25 W
Air vent stage 3 - summer cassette: 45 W
HC Compressor:  54 W
DHW pump: 1500 W

The heat produced - sHeatDWh was 27 kWh - as predicted 1:3 efficiency
sHistory reported: 5 hours of DWH compressor activity. I think there must be a rounding error here because it should be 6 hrs according to all available data.

In addition I hypothesize that the summer cassette decreases the fan speeds due to lack of forced heat exchange. The flow, if I could only measure it, should be the same no matter which cassette is in there because the flow rates are set. So the summer module saves 11 W. So within the THZ lifetime it will eventually amortize. ;)

Does anyone else have actual metering on the Thz? I envision that if we could somehow determine actual activity time across 24 he's of compressor, vent stages, heat pump and booster activity, that this module can give you exact meter reading ( actual total system usage) of energy for any given day.

@willy: the sensor is still in the cool basement. Need to extend the chord. Will check the heating set point change and report back.

Tom

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Mai 2014, 21:29:28
nice overview tom!!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 21 Mai 2014, 00:38:21
@houseowner123

Thank's a lot for your work and the impressive values.
Especially the section on the power consumption summer cassette <-> winter cassette was very interesting!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 21 Mai 2014, 13:40:46
Hi,

I already got this module up and running with my LWZ 303i. But now I've got some questions, maybe you can answer me.

1. How do you get the inside temperature? I do not have any inside control or temperature sensor from stiebel inside my house.
2. And how do you get the humidity? Is that also a sensor in the house or is it an internal sensor of the THZ/LWZ?
3. Do you all have power and heating measurement within your LWZ/THZ? Can that be installed additonally?
4. What is the last firmware version for an LWZ 303i?

@houseowner123:
You wrote:
ZitatI can measure real time power usage,

Can you tell me/us, how you do that? I'm planing to do the same, but at the moment I have several ways in mind and can't decide the best (low cost, high output). And I would like to know, how much energy kWh you need with your 303i over a year. You can write me an PM, if that's fine with you.  :)

Best regards,
Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Mai 2014, 13:46:08
Zitat von: Jakl am 21 Mai 2014, 13:40:46
1. How do you get the inside temperature? I do not have any inside control or temperature sensor from stiebel inside my house.
2. And how do you get the humidity? Is that also a sensor in the house or is it an internal sensor of the THZ/LWZ?
both sensors are inside the control panel which you don't have. me not either, so i installes the HMS100TF using a CUL868 for this measurings.
Zitat
3. Do you all have power and heating measurement within your LWZ/THZ? Can that be installed additonally?
yep, they are coming from the system itself.
Zitat
4. What is the last firmware version for an LWZ 303i?
for the 303 i guess 4.39
for the 403 i already saw a 5.39

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Mai 2014, 16:30:39
cheapest way for measuring inside temp with THZ (!) is an external sensor, connected via a 2 wire cable. Advantage of measuring it with THZ is that you can select to influence the heating curve in this case. Of course that's not possible with different inside temp measuring methods since the THZ doesn't know about it. Humidity needs a secondary display in living room and it can measure inside temp as well.


power and heating measurement is built in into THZ/LWZ. See "ISTWERTE" and "FACHMANN - LAUFZEITEN" menu for available values.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Mai 2014, 18:23:50
Willy, why Not? you can change the Set temps depending on the measurement of the hms100tf
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Mai 2014, 19:17:03
Zitat von: micomat am 21 Mai 2014, 18:23:50
Willy, why Not? you can change the Set temps depending on the measurement of the hms100tf
http://fhem.de/commandref_DE.html#THRESHOLD could help you
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Mai 2014, 19:41:03
Not what i meant but Never mind ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Mai 2014, 20:14:11
Zitat von: immi am 21 Mai 2014, 19:17:03
http://fhem.de/commandref_DE.html#THRESHOLD could help you
Hi Markus
My understanding is that you want to change the Set temps in the heatpump depending on the measurements of hms100tf.
I would't do a linear feedback (continuous set of values)
I suggested you threshold, because it could help you with a quantized feedback (relatively small discrete set).

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Mai 2014, 20:17:23
and i suggested the HMS to jakl :)
but the idea with threshold is good.

thanks
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Mai 2014, 22:34:49
Zitat von: micomat am 21 Mai 2014, 18:23:50
Willy, why Not? you can change the Set temps depending on the measurement of the hms100tf
As I already statet weeks ago I'll never ever implement a solution which needs to rely on a series of low budget items instead of the double digit mtbf of the THZ's own control:
ZitatAnd finally I'd like to let you know why I don't want to rely on fhem to do things instead of Tecalor's THZ control. Reason is simply reliability. I'll never ever replace the THZ control with it's double digit year MTBF against a sequence of cheap consumer parts like raspberryPi (using flash card as mass storage), low budget chinese power supply, LAN switch (again with  low budget chinese power supply), PowerLAN-adapters, USB-RS232-adapter etc. My goal is to minimize risk. If I can influence what the THZ does by still relying on its own control I'll do it. But I don't e.g. use fhem switch to manual mode for a while in order to heat up water. If during this period of time one of the affected components dies, or a fhem command of a different unit hangs up for any reason, the THZ will never go back into automatic mode. Worst case I'm on vacation far away from home and can't do anything beside checking how it goes wrong.
Second goal is that the solution doesn't need to rely on myself. If I'm not at home and anything goes wrong it must be enough for my wife to simply remove the RS232 cable from the THZ and the THZ goes on working as if there would never have been a cable. So a service technician can do his job without any problems, no matter if I'm accessible or not.


As soon as fhem hangs for any reason your solution will stop working - no matter if you're at home or thousands of kilometers away.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Mai 2014, 22:43:39
Zitat von: immi am 20 Mai 2014, 15:09:40
Hi Willy
no idea because I do not have the hardware to test it
have a look in register E8; just uncomment line 273.
Heat up your living room display and read again E8

or maybe someone can lend you an oscilloscope and you can look at the can-bus of the display
immi
No success with sAllE8  :( . I can't find a relation between inside temp and the values. But there seems to be a relation between some of the read parameters and passive cooling mode. The last reading in the list is with passive cooling type 1 active, the other ones not.


24,7°C - 2014-05-21_15:18:06 Mythz sAllE8: 77E8020001F73E0001914E00021ACB0001B39200000000000000000E101F19005100651B2200 x04: 512 x08: 503 x12: 15872 x16: 401 x20: 19968 x24: 538 x28: -13568 x32: 435 x36: -28160 x40: 0 x44: 0 x48: 0 x52: 14 x52: 4127 x60d: 6400 x64: 20736 x68: 25883 x72: 8704
25,7°C - 2014-05-21_15:22:29 Mythz sAllE8: 76E8020001F73E0001914E00021ACB0001B39200000000000000000E101E19005100651B2200 x04: 512 x08: 503 x12: 15872 x16: 401 x20: 19968 x24: 538 x28: -13568 x32: 435 x36: -28160 x40: 0 x44: 0 x48: 0 x52: 14 x52: 4126 x60d: 6400 x64: 20736 x68: 25883 x72: 8704
24,2°C - 2014-05-21_21:10:47 Mythz sAllE8: 75E8020001F73E0001914E00021ACB0001B39200000000000000000E101D19005100651B2200 x04: 512 x08: 503 x12: 15872 x16: 401 x20: 19968 x24: 538 x28: -13568 x32: 435 x36: -28160 x40: 0 x44: 0 x48: 0 x52: 14 x52: 4125 x60d: 6400 x64: 20736 x68: 25883 x72: 8704
24,6°C - 2014-05-21_21:17:40 Mythz sAllE8: 08E8020001F73E0001914E00021ACB0001B39200000000000000000E10002100000065003600 x04: 512 x08: 503 x12: 15872 x16: 401 x20: 19968 x24: 538 x28: -13568 x32: 435 x36: -28160 x40: 0 x44: 0 x48: 0 x52: 14 x52: 4096 x60d: 8448 x64: 0 x68: 25856 x72: 13824
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Mai 2014, 23:08:26
hi willi
allE8 looks like some vent speed.
you have to spy the can-bus if you want to understand more
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Mai 2014, 23:53:31
thanks for the hint. Can bus spying wouldn't be a problem. I could borrow any kind of oszilloscop from my company, but that's too much effort for such a detail as long as an easy workaround exists (use the inside temp value from sGlobal, measured with external sensor). I'll spend my free time differently in more efficient way.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 22 Mai 2014, 10:59:11
Zitat von: willybauss am 21 Mai 2014, 16:30:39
cheapest way for measuring inside temp with THZ (!) is an external sensor, connected via a 2 wire cable.
Zitat von: micomat am 21 Mai 2014, 13:46:08
both sensors are inside the control panel which you don't have. me not either, so i installes the HMS100TF using a CUL868 for this measurings.yep, they are coming from the system itself.for the 303 i guess

Thank you Markus, thank you willybauss, I think I will go with the external sensor connected with the LWZ/THZ directly. So I can use the advantage (and event if it is just a little advantage) of the influence of the heating curve. I think I already have one external sensor from stiebel eltron in my basement, but it was not installed with the heat-pump.

Zitat von: willybauss am 21 Mai 2014, 22:34:49
As I already statet weeks ago I'll never ever implement a solution which needs to rely on a series of low budget items instead of the double digit mtbf of the THZ's own control:

As soon as fhem hangs for any reason your solution will stop working - no matter if you're at home or thousands of kilometers away.

@willybauss: I agree. But from my point of view, the weak point is FHEM. Not the used devices.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 Mai 2014, 13:29:59
Zitat von: Jakl am 22 Mai 2014, 10:59:11
So I can use the advantage (and event if it is just a little advantage) of the influence of the heating curve. I think I already have one external sensor from stiebel eltron in my basement, but it was not installed with the heat-pump.
In my case it's a big advantage. After having made a perfect hydraulic adjustment I do no more have any inefficient room thermostats. So I can save lots of unnecessary heating costs by telling the THZ that the inside temp is already reached, thus no heating necessary. This is especially the case at nights after sunny days, when the sun heated up the house through my bis southern oriented windows. Without inside temp sensor the THZ would heat up the underfloor heating anyway, just based on the assumption that cold outside temp requires inside heating as well.

Zitat von: Jakl am 22 Mai 2014, 10:59:11
@willybauss: I agree. But from my point of view, the weak point is FHEM. Not the used devices.
I agree. The more features you add to your fhem config, the higher the risk that anything blocks the rest. Since fhem is single threaded there's not really a way out.
But nevertheless: in my long live I saw lots of dead hard disks, power supplies, ... Since it's a long chain of such devices, the risk is much higher than having just one single THZ control.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Mai 2014, 13:54:00
hey immi,

when setting the system from automatic to DHW-Mode, do i have to enter the digit for DHW-Mode or the text DHW-Mode? If it is the digit, could we implement some kind of translation from digit to text and vice versa in the set-list?

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 22 Mai 2014, 14:58:56
Hi markus,

you have to enter the word: DHWmode

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Mai 2014, 15:01:37
ok needed this info for the Wiki :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Mai 2014, 22:26:57
Zitat von: immi am 18 Mai 2014, 17:57:40
v0.099
- room-influence has been included in the simulation curve plot.
- Willi noticed an incosistency in the plot: to make it short:
in wintermode roomSetTemp (from  sHC1) is given from p01RoomTempDayHC1  and  p02RoomTempNightHC1   
in summermode roomSetTemp (from  sHC1) is given from  p01RoomTempDayHC1SummerMode and  p02RoomTempNightHC1SummerMode

The last 2 parameters are not documented in the manuals. Their behaviour has been confirmed empirically.
The same is valid for HC2.
After some days of observation, I can add something which in the manual it was not so clear fo me.

Passive cooling mode is activated if  p75passiveCooling>=1 and if the outside temperature is 3 K above the set-room-temperature for at least two hours and if the outside temperature then drops 3K below the set-room-temperature.   

My question was  what is set-room-temp?
p01RoomTempDayHC1  and  p02RoomTempNightHC1 are the one connected to the activation of cooling mode.

this is only valid if no inside room temperature sensor is installed.

if confirmed by someone, info is wiki relevant
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 Mai 2014, 23:45:17
Zitat von: immi am 22 April 2014, 23:34:33
I was aware of it; therefore I did not advertize too much on it. I am fighting on this and on Partytime.
UnschedVent and maybe Partytime are a combination of a flag somewhere and the registers I found.
I have an idea; but quite risky, because I am debugging from VPN. In 2 weeks I will have a look.
p.s. there are many more eggs to find.

Any news on this topic?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 23 Mai 2014, 09:26:34
Hi,

I have a problem with the reading of inside temp and the rel_humitidy.
from the the logs I see, that it's not read.
"5-23_08:25:02 Mythz sGlobal: outsideTemp: 11.7 flowTemp: 29.5 returnTemp: 24.6 hotGasTemp: 38.4 dhwTemp: 47.1 flowTempHC2: 21.1 evaporatorTemp: 23.5 condenserTemp: 25.2 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 40 inputVentilatorPower: 43 mainVentilatorPower: 0 outputVentilatorSpeed: 32 inputVentilatorSpeed: 36 mainVentilatorSpeed: 0 outside_tempFiltered: 16.5 relHumidity: 0 dewPoint: 883 P_Nd: 8.83 P_Hd: 8.95 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-0"

On the THZ display under "ISTWERTE->HK2 Raumtemperatur und HK2 Luftfeuchtigkeit there are the right values!
How can I read these values?

Micha
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Mai 2014, 10:05:06
Do you have an external sensor for inside temperature and/or a second display connected via CAN bus to the heatpump? Otherwise it's impossible.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 23 Mai 2014, 16:29:51
I have a second display in the living room, which is to HC2 assigned.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Mai 2014, 19:43:16
For debugging purposes please try to assign the 2nd display to HC1. I would expect valid humidity values to be available in sGlobal afterwards. I don't know how you can read HC2 based values. Might be that immi can give you a hint on how to find it out yourself by reading new parameters.

I'm unsure if you'll get valid inside temperature values from the second display, even if assigned to HC1. As I stated above (anytime this week)  - at least in my case -  the  inside temperature value of sGlobal is read from the separate external temperature sensor only.

Please report the result of this experiment here, no matter if it ends successfully or not. At least I am very interrested in such results, since up to now I've been the only one here having a second display and an external sensor.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 23 Mai 2014, 20:04:13
Hi,

I have a question regarding heating circles. I have a LWZ 303 i, what are the different heating circles for? HC1 for the floor heating? HC2??
That's a general question, I hope somebody can answer this. Do you have the same settings for the heating curve for HC1 and HC2??

Best regards,
Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Mai 2014, 20:11:12
I noticed that the passive cooling mode lasts longer than the max. 8 hours mentioned in the manual. I had one night with 12 hours, last night it was 13 hours. Looks like the starting point is indeed when outside temp is 3° lower than inside temp.

But for the end point there are obviously different rules.
Today it ended at 10:00 at
Yesterday it ended at 08:12 at
So I believe that endpoint criteria is
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Mai 2014, 20:17:48
Zitat von: Jakl am 23 Mai 2014, 20:04:13
Hi,

I have a question regarding heating circles. I have a LWZ 303 i, what are the different heating circles for? HC1 for the floor heating? HC2??
That's a general question, I hope somebody can answer this. Do you have the same settings for the heating curve for HC1 and HC2??

Best regards,
Jakl
Depends on what the planner of your heating thought. You should know/ask him if you have one single HC, or two HCs. With a second circle you can drive two different heatSetTemps, e.g. if you have a house with two apartments (both families might need different temperature profiles based on their preferences), or a part of the house has radiators instead of underfloor heating (radiators need much higher temperatures). If you have two HCs the heating curves might be different, but not necessarily. Depends on details.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 Mai 2014, 20:29:54
Zitat von: willybauss am 23 Mai 2014, 20:11:12
(10:00 reached)
Willi it is also written in the manual
"Passive cooling ends no later than at 10:00 h."

For your other question. I haven't found any other parameter. I am not really inspired.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 Mai 2014, 20:56:09
Zitat von: Jakl am 23 Mai 2014, 20:04:13
Hi,

I have a question regarding heating circles. I have a LWZ 303 i, what are the different heating circles for? HC1 for the floor heating? HC2??
That's a general question, I hope somebody can answer this. Do you have the same settings for the heating curve for HC1 and HC2??

Best regards,
Jakl

the 303 can use two circles. i have also a 303 with only HC1 active for the floor heating. the HC2 is displayed but not activated in the system.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Mai 2014, 23:05:37
@immi:
since a few days I can no more see a heating curve (but the red dot is still visible). Is the curve deactivated in summer mode, or is it related to latest update, or what else could be the root cause?
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 Mai 2014, 23:40:10
Zitat von: willybauss am 23 Mai 2014, 23:05:37
@immi:
since a few days I can no more see a heating curve (but the red dot is still visible). Is the curve deactivated in summer mode, or is it related to latest update, or what else could be the root cause?
Willy
no idea, I see it perfectly, please post sGlobal and sHC1.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 24 Mai 2014, 10:01:09
Hi,

when I assign the second display to HC1, humutidy is correct, but inside temp is still at -60 degree.

outsideTemp: 12.3 flowTemp: 26.7 returnTemp: 25 hotGasTemp: 30.2 dhwTemp: 44.5 flowTempHC2: 20.4 evaporatorTemp: 25.2 condenserTemp: 22.7 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 25 inputVentilatorPower: 27 mainVentilatorPower: 0 outputVentilatorSpeed: 22 inputVentilatorSpeed: 27 mainVentilatorSpeed: 0 outside_tempFiltered: 13.8 relHumidity: 35.7 dewPoint: 885 P_Nd: 8.85 P_Hd: 8.95 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Mai 2014, 10:22:30
Zitat von: immi am 23 Mai 2014, 23:40:10
no idea, I see it perfectly, please post sGlobal and sHC1.
immiere you ar
here you are
2014-05-24_10:13:36 Mythz sHC1: outsideTemp: 13 x08: -49.1 returnTemp: 22.2 integralHeat: 0 flowTemp: 24.4 heatSetTemp: 21.3 heatTemp: 22.8 seasonMode: summer integralSwitch: 100 opMode: setback roomSetTemp: 21
2014-05-24_10:16:56 Mythz sGlobal: outsideTemp: 13 flowTemp: 24.4 returnTemp: 22.2 hotGasTemp: 21.5 dhwTemp: 42.3 flowTempHC2: -60 evaporatorTemp: 20.8 condenserTemp: 23.1 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 34 inputVentilatorPower: 27 mainVentilatorPower: 0 outputVentilatorSpeed: 24 inputVentilatorSpeed: 28 mainVentilatorSpeed: 0 outside_tempFiltered: 13.1 relHumidity: 37.6 dewPoint: 957 P_Nd: 9.57 P_Hd: 9.43 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: 24.6
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Mai 2014, 10:33:18
Zitat von: michaelk68 am 24 Mai 2014, 10:01:09
Hi,


when I assign the second display to HC1, humutidy is correct, but inside temp is still at -60 degree.
So it's as I expected: => To solve your issues completely you need to Alternatively you can use an inside temperature measurement of a different hardware, e.g. Homematic etc. But in this case there's no (automatic) feedback to the THZ's control, thus no influence of inside temperature on the heating curve. Markus (micomat) suggested to work around this issue (here in this thread approx. 1 week ago) by setting THZ parameters based on such external measurements. But I'm not a friend of such proceedings due to reliability reasons: as soon as fhem stops working for any reason, your heatpump's parameters can be in an unexpected state, where the THZ is no more able to work correctly in a sensible way without this external influence.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 Mai 2014, 11:10:23
uploaded v0.100 (you can update this evening or tomorrow)
changelog

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 Mai 2014, 18:46:24
Zitat von: immi am 24 Mai 2014, 11:10:23
I wanted to change the parameters, and was too lazy to go downstair[/li][/list]
lol
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Mai 2014, 22:42:51
Zitat von: immi am 24 Mai 2014, 11:10:23
fix for the Willy's heating curve
So the issue was related to inside temperature measurement and it's influence on the heating curve?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 Mai 2014, 06:58:00
Zitat von: willybauss am 24 Mai 2014, 22:42:51
So the issue was related to inside temperature measurement and it's influence on the heating curve?
bad modeling of your data. fitting is still not perfect,,, but improving.
Anyhow, the heating curve should only give an idea of what the heatpump does inside.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 26 Mai 2014, 08:11:52
heating curve is visible again after update to 0.100. Red dot fits curve perfectly - at least with currently warm outside temps.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 26 Mai 2014, 14:36:35
Who have also an inside temperature sensor installed, not the inside controller? Or does anybody know, which low cost sensor I can install? Link?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 26 Mai 2014, 15:33:42
Not sure what you mean with controler. But I order and successfully installed this one.

http://www.sensorshop24.de/Sonderposten/Kabelfuehler-mit-verschiedenen-Sensoren/Kabelfuehler-mit-KTY/Kabelfuehler-mit-Knickschutzfeder-6x30-KTY-81-210-2-5-Meter-PVC.html?listtype=search&searchparam=SO617

It doesn't get much cheaper unless you want to solder the sensor yourself onto a cable.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 26 Mai 2014, 16:17:33
Zitat von: willybauss am 26 Mai 2014, 08:11:52
heating curve is visible again after update to 0.100. Red dot fits curve perfectly - at least with currently warm outside temps.

I never see the red dot. The red dot point seems to fixed for me at 8°C. Since it is not heating time rihgt now, I am not worried about it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Mai 2014, 22:55:52
Dear all

v0.101 has been uploaded, you can download tomorrow.
- no new features
- lots of clean up
- logs in verbose 5 implemented.
- buffer overflow (caused by sGlobal for LWZ 303 firmware 3.19). has been fixed.

Lots of code has been improved, based on the precious feedback from Jakl.
Please test all feature that you can.

If I get positive feeback, more upgrade are on the pipeline.
Jakl has suggested some more changes, which will make 00_THZ more reliable and efficient.
thanks again for helping.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Mai 2014, 10:56:42
just updated the wiki.
unfortunately there is less time at the moment, so i just added info from 0.099 to 0.101

thanks for the work @ll
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Mai 2014, 20:04:13
Dear all
I noticed that Tom installed a inside room temperature sensor.
With this sensor makes very sense to use the P15 different from 0.
Willy uses P15 = 50%.

Now both Tom and I have P19  at 30%, ( normal setting with thermostates)
What happens if we set both P19 and P15 to a value different from 0.
Apocalypse,  frogs falling from the sky?
;D
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Mai 2014, 20:20:15
Zitat von: immi am 27 Mai 2014, 20:04:13
Apocalypse,  frogs falling from the sky?
;D
immi

Tell me if so :) Sounds like great Fun!
by the Way i miss the Parameter to Set the Solar temp (60° default). any Chance to find it?

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 Mai 2014, 21:27:16
I have P19  at 30% as well. Don't know if it makes sense to change it. Setting it to 30% means that 70% of the heatTemp calculation are influenced by return temperature, 30% by flow temperature. I believe that the return temp is a better indicator for the *real* temperature of the stone floor than flow temp. Therefore the 30% setting makes sense.

@ immi:

Setting P15 to anything different from 0 doesn'tmake sense as long as there's no inside temp measurement available. Worst case the calculation takes the default value (-60°C) into account ...  :P
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Mai 2014, 22:10:14
Zitat von: willybauss am 27 Mai 2014, 21:27:16
Setting P15 to anything different from 0 doesn'tmake sense as long as there's no inside temp measurement available. Worst case the calculation takes the default value (-60°C) into account ...  :P
I know, I did not mention that I am going to buy a temp sensor this winter.

p.s. have you tried v0.101? do you see anything strange?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 Mai 2014, 22:12:38
Zitat von: immi am 27 Mai 2014, 22:10:14
p.s. have you tried v0.101? do you see anything strange?
Sorry, I didn't update yet. Will try within next few days.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 28 Mai 2014, 13:30:20
Zitat von: houseowner123 am 26 Mai 2014, 15:33:42
Not sure what you mean with controler. But I order and successfully installed this one.

http://www.sensorshop24.de/Sonderposten/Kabelfuehler-mit-verschiedenen-Sensoren/Kabelfuehler-mit-KTY/Kabelfuehler-mit-Knickschutzfeder-6x30-KTY-81-210-2-5-Meter-PVC.html?listtype=search&searchparam=SO617

It doesn't get much cheaper unless you want to solder the sensor yourself onto a cable.

Tom
Hi Tom,

must it be a KTY sensor? Can I find this information anywhere in the documentation of the THZ/LWZ?
I think to use one of these:
http://www.fuehlersysteme.de/raumtemperaturfuhler.html (http://www.fuehlersysteme.de/raumtemperaturfuhler.html)
or
http://www.fuehlersysteme.de/unterputz-raumtemperaturfuhler.html

Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Mai 2014, 14:09:35
0.101 installed, runs without any problems :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Mai 2014, 15:45:32
Zitat von: Jakl am 28 Mai 2014, 13:30:20
Hi Tom,

must it be a KTY sensor? Can I find this information anywhere in the documentation of the THZ/LWZ?
I think to use one of these:
http://www.fuehlersysteme.de/raumtemperaturfuhler.html (http://www.fuehlersysteme.de/raumtemperaturfuhler.html)
or
http://www.fuehlersysteme.de/unterputz-raumtemperaturfuhler.html (http://www.fuehlersysteme.de/unterputz-raumtemperaturfuhler.html)

Jakl
No matter what you use mechanically, BUT electrically it has to have the same characteristics (= resistance vs. temperature diagram) than the one mentioned by Tom (KTY 81- 210). Otherwise the measured temperatures are wrong.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 28 Mai 2014, 16:12:07
Zitat von: willybauss am 28 Mai 2014, 15:45:32
No matter what you use mechanically, BUT electrically it has to have the same characteristics (= resistance vs. temperature diagram) than the one mentioned by Tom (KTY 81- 210). Otherwise the measured temperatures are wrong.

Hi willybauss, hi Tom,

I asked Stiebel Eltron and they told me, I should connect a PT1000. But the PT1000 have different resistance then a KTY 81-210. So when Tom uses a KTY 81-210 and it works, should I order a KTY 81-210?
Do I also need to take care off the cabels or is it ok if I use a simple 2-wire cable like that: http://www.sensorshop24.de/Kabel-Leitungen/PVC-Leitung-2-Leiter-35-C-bis-105-C.html (http://www.sensorshop24.de/Kabel-Leitungen/PVC-Leitung-2-Leiter-35-C-bis-105-C.html)
Best regards,
Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 28 Mai 2014, 16:26:36
Zitat von: Jakl am 28 Mai 2014, 16:12:07
Hi willybauss, hi Tom,

I asked Stiebel Eltron and they told me, I should connect a PT1000. But the PT1000 have different resistance then a KTY 81-210. So when Tom uses a KTY 81-210 and it works, should I order a KTY 81-210?
Do I also need to take care off the cabels or is it ok if I use a simple 2-wire cable like that: http://www.sensorshop24.de/Kabel-Leitungen/PVC-Leitung-2-Leiter-35-C-bis-105-C.html (http://www.sensorshop24.de/Kabel-Leitungen/PVC-Leitung-2-Leiter-35-C-bis-105-C.html)
Best regards,
Jakl

Just wondering why I documented all the sensor steps here and it is still not clear?
PT1000 is a collector sensor.  Look at page 36: http://www.stiebel-eltron.de/imperia/md/content/STIEBELELTRON/de/Fachpartner/Fachinformationen/Downloads/Gebrauchs-und-Montageanweisungen/04_lueftung/15_zentralsysteme/166459-35726-8545_lwz_303-403_de.pdf
PTC is the same as Aussenfühler=inner sensor. Then I looked in the table on that page and comapred the different resistance scale with existing literature and the ONLY scale it measures up to KTY81-210.
And that's what I wrote a couple of weeks ago after PT1000 did not work (which I also wrote about).
If you want to go ahead with what SE tells you...do it...but don't complain..because I told you so! ;)

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Mai 2014, 18:58:42
immi, could you add an version information to the module internals? i saw this in the dashboard module and found it very helpful when supporting somebody
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 28 Mai 2014, 20:23:04
Zitat von: houseowner123 am 28 Mai 2014, 16:26:36
Just wondering why I documented all the sensor steps here and it is still not clear?
PT1000 is a collector sensor.  Look at page 36: http://www.stiebel-eltron.de/imperia/md/content/STIEBELELTRON/de/Fachpartner/Fachinformationen/Downloads/Gebrauchs-und-Montageanweisungen/04_lueftung/15_zentralsysteme/166459-35726-8545_lwz_303-403_de.pdf
PTC is the same as Aussenfühler=inner sensor. Then I looked in the table on that page and comapred the different resistance scale with existing literature and the ONLY scale it measures up to KTY81-210.
And that's what I wrote a couple of weeks ago after PT1000 did not work (which I also wrote about).
If you want to go ahead with what SE tells you...do it...but don't complain..because I told you so! ;)

Tom

Sorry Tom, I thought that I had read the whole thread. I don't know how it could happend, that I missed your story about the pt1000 sensor. And google also have not found any answer, even not within this thread.
Thank you for your help!  ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Mai 2014, 20:25:18
Zitat von: micomat am 28 Mai 2014, 18:58:42
immi, could you add an version information to the module internals? i saw this in the dashboard module and found it very helpful when supporting somebody
module internals???
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Mai 2014, 20:40:55
here's an screenshot =)

next suggestion... i'm not sure if it would make sense to exclude the "program" values from the standard log? my logfile from 1 month is about 15MBytes, that makes generating plots including 2-3monthts very slow. may it more helpful to have those information only on a higher verbose level? i don't need to see same program values all the time in the log. whats your opinion?

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Mai 2014, 22:51:33
INTERNAL version is a good idea, I will see what can I do
Zitat von: micomat am 28 Mai 2014, 20:40:55
next suggestion... i'm not sure if it would make sense to exclude the "program" values from the standard log? my logfile from 1 month is about 15MBytes, that makes generating plots including 2-3monthts very slow. may it more helpful to have those information only on a higher verbose level? i don't need to see same program values all the time in the log. whats your opinion?
this solves your problem

attr Mythz event-on-update-reading p\d.*
attr Mythz event-on-change-reading .*


the last line is: all parameter will be updated only on change
the first line is: forget the last line for parameters starting with p+number.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Mai 2014, 22:55:23
Great :) thank You so much!
will test and update the Wiki soon


markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 29 Mai 2014, 10:40:23
Zitat von: Jakl am 28 Mai 2014, 20:23:04
Sorry Tom, I thought that I had read the whole thread. I don't know how it could happend, that I missed your story about the pt1000 sensor. And google also have not found any answer, even not within this thread.
Thank you for your help!  ;)

No problem, Jakl! :)
@immi and Markus: would it be worth adding the Sensor information to the wiki. As a hardware extension section and the provide information where in the module the relevant measures appear. It is pretty tedious to go through all the pages. If you want I can come up with a German/English draft.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Mai 2014, 10:59:41
if you send me the exact details of the sensor, sure i can add the info to the wiki :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 29 Mai 2014, 12:46:01
Hello,

I have yesterday installed FHEM on an raspberry Pi with youre thz.pm. Workshop Great. Connection over USB on a Thz 304 Firmware 5.19.
Does anybody have pictures from ISG Web. I like to rebuild some Features...

304 have a rel huminity Fan correction, Can u bring the Parameter in thz.pm?

I think we Need a better log Rotation. The perform with the raspberry on the Plots sucks...




Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Mai 2014, 13:05:58
Zitat von: belu am 29 Mai 2014, 12:46:01
Connection over USB on a Thz 304 Firmware 5.19.
Interresting and good news that it works on 304 as well. Am I right that 304 is the successor of 303?
Zitat von: belu am 29 Mai 2014, 12:46:01Does anybody have pictures from ISG Web.
You didn't try using google yet, right?  ;) 
Zitat von: belu am 29 Mai 2014, 12:46:01304 have a rel huminity Fan correction, Can u bring the Parameter in thz.pm?
What does this correction do in detail?
Zitat von: belu am 29 Mai 2014, 12:46:01I think we Need a better log Rotation. The perform with the raspberry on the Plots sucks...
Your suggestions are welcome. Code is freeware - just take and improve ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Mai 2014, 14:24:08
Zitat von: willybauss am 29 Mai 2014, 13:05:58
Code is freeware - just take and improve ...
willy
small errata. code is open source as defined by GLP.
but my message is the same.

Zitat von: belu
I think we Need a better log Rotation. The perform with the raspberry on the Plots sucks...
Hi belu
happy that you got it running.
Logs, plot and raspberry are treated in other section of this forum. You can address to the specialist of each module.
There are so many solutions to this problem....
1) use the raspi only as repeater (keywords ser2net or fhem2fhem). You save the data and make the plot on better hardware (i do it with a qnap nas).
2) tailor what you save in the logs: not too often, not everything, only on change...
3) use dblog instead of filelog
4) cache the plots: generate them every 5 minutes, not every time you refresh the webpage. 

immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Mai 2014, 15:13:58
Zitat von: immi am 28 Mai 2014, 22:51:33

attr Mythz event-on-update-reading p\d.*
attr Mythz event-on-change-reading .*


the last line is: all parameter will be updated only on change
the first line is: forget the last line for parameters starting with p+number.

immi

just implemented it but it seems not to affect the p-readings. i still have them in the log.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Mai 2014, 16:49:06
Zitat von: micomat am 29 Mai 2014, 15:13:58
just implemented it but it seems not to affect the p-readings. i still have them in the log.

The setting does not remove all pxxxx from log. It does something else, as I wrote
p+number like P01 will be logged as before.
all other parameters will be logged only if they change.

if you want to log only sXXXXX, use this code

define FileLog_Mythz FileLog /opt/fhem/log/Mythz-%Y-%m.log Mythz:s.*
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 Mai 2014, 08:59:22
thanks :) will try and come back to you
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Mai 2014, 21:46:21
v0.103, tomorrow you can update
- added  version as internal
- major change in comunication (speed improvement: 10x faster get-procedure and set-procedure)

please give me feedback:  some more changes inspired by jakl are in the pipeline.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Mai 2014, 22:25:24
Zitat von: immi am 30 Mai 2014, 21:46:21
speed improvement: 10x faster get-procedure and set-procedure)
ups - I have just a GBit LAN. Is it enough or do I need to update it as well  :)  ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 31 Mai 2014, 08:31:41
guys, you're awesome :D
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Mai 2014, 09:11:28
looks like a bug in v.103:
after having updated I got no more readings. A manually forced get Mythz sGlobal results in
01000BFBFDA800DE010300E4013F01D9FDA800E500D800F00000110154010E00 msg2 3Acrc_error in answer


edit:
basically same result with
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Mai 2014, 09:32:04
I removed lots of delay

increase the delay: go to line 652
change it from
select(undef,undef,undef,0.001);

to
select(undef,undef,undef,0.01);


and please stop fhem and restart it
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Mai 2014, 10:34:17
works again, thanks  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Mai 2014, 11:14:47
v0.104 uploaded
- 10ms delay added for willy... v0.104 is still 5x faster than v0.101
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Mai 2014, 17:07:47
Hi,

this my first version to change the operation mode of the thz.


##Operation Mode an changing

define OperationModeTHZ dummy
attr OperationModeTHZ alias Operation Mode
attr OperationModeTHZ group THZ
attr OperationModeTHZ room Heizung
attr OperationModeTHZ setList Standby Automatic Daymode Setback DHWmode Manual Emergency
attr OperationModeTHZ webCmd standby:automatic:DAYmode:setback:DHWmode:manual:emergency

define Notify_pOpMode notify OperationModeTHZ set Mythz pOpMode $EVENT
define Notify_OperationModeTHZ notify (Mythz.pOpMode.*) setstate OperationModeTHZ $EVTPART1


Works... but, i like a drop down menu...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Mai 2014, 22:17:29
Zitat von: belu am 31 Mai 2014, 17:07:47
Works... but, i like a drop down menu...
well done belu
If you want a drop-down menu

attr OperationModeTHZ setList state:automatic,standby,DAYmode,setback,DHWmode,manual,emergency
attr OperationModeTHZ webCmd state

I do not like them because in some browser look and behave strange
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Juni 2014, 00:46:15
thx ImmI

works great...

my idea for DHW

## Domestic hot water

define DHWTHZ readingsGroup Mythz:<%sani_boiler_temp@red>,<Hot_Water>,dhw_temp
attr DHWTHZ alias Hot Water
attr DHWTHZ group DHW
attr DHWTHZ room Heizung
attr DHWTHZ valueFormat { dhw_temp => '%0.1f °C' }

#Day
define Hot_Water_Day dummy
attr Hot_Water_Day alias Hot Water Day
attr Hot_Water_Day group DHW
attr Hot_Water_Day room Heizung
attr Hot_Water_Day setList state:slider,10,1,70
attr Hot_Water_Day webCmd state
define Notify_p04DHWsetDay notify Hot_Water_Day set Mythz p04DHWsetDay $EVENT
define Notify_Hot_Water_Day  notify (Mythz.p04DHWsetDay.*) setstate Hot_Water_Day $EVTPART1

#Night
define Hot_Water_Night dummy
attr Hot_Water_Night alias Hot Water Night
attr Hot_Water_Night group DHW
attr Hot_Water_Night room Heizung
attr Hot_Water_Night setList state:slider,10,1,70
attr Hot_Water_Night webCmd state
define Notify_p05DHWsetNight notify Hot_Water_Night set Mythz p05DHWsetNight $EVENT
define Notify_Hot_Water_Night   notify (Mythz.p05DHWsetNight.*) setstate Hot_Water_Night $EVTPART1


Who can i get the DHW_Temp without Userreadings from sGlobal? I dont like the rows...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Juni 2014, 01:06:19
belu
it is nice your example of frontend.
I repeat: I do not like drop-down-menu because in some browser look and behave strangly.
If you have no problem in all your used browsers (incl. smartphone), make sure that these easy shortcut are out of reach of children,  drunk relatives ...... :)
Unwanted changing of the ventilation from 1 to 2 is not so bad, changing opmode to emergency or hotwater temp..... could be annoing.

I have configured more frontends (FHEMWEB): one for me at port 8083  and one for my family 8084 with the parameter "hiddenroom"
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Juni 2014, 09:54:10
Hello Immi,

my FHEM ist Password protected,  i used it only for my thz. the home automation runs on loxone.
i understand ure security reasons, id like to change the structure...
drop down menu for op mode works great with all browsers i used.

define OperationModeTHZ dummy
attr OperationModeTHZ alias Operation Mode
attr OperationModeTHZ group Operation Mode
attr OperationModeTHZ room Heizung
##with dropdown
attr OperationModeTHZ setList state:automatic,standby,DAYmode,setback,DHWmode,manual,emergency
attr OperationModeTHZ webCmd state
## without dropdown
#attr OperationModeTHZ setList Standby Automatic Daymode Setback DHWmode Manual Emergency
#attr OperationModeTHZ webCmd standby:automatic:DAYmode:setback:DHWmode:manual:emergency
define Notify_pOpMode notify OperationModeTHZ set Mythz pOpMode $EVENT
define Notify_OperationModeTHZ notify (Mythz.pOpMode.*) setstate OperationModeTHZ $EVTPART1


In my opinion the user can change...

the reason why i used a dropdown or a slider... i have problems to create a input field with a min and max range.
in the dropdown u can set fix points to change. In a slider u can set max and min.

The best way is a defined range to input field and a save button to transmit.

id like to rebuild a setup screen for thz... 

sorry immi, i dont wont disgust you.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Juni 2014, 09:59:06
Zitat von: immi am 01 Juni 2014, 01:06:19
Unwanted changing of the ventilation from 1 to 2 is not so bad, changing opmode to emergency or hotwater temp..... could be annoing.

additionally I need to rise the question what might happen if fhem stops working unexpectedly (due to bug, hw defect, ...) while THZ is in a mode different from automatic and/or where parameters are set to anything else than the"normal" ones. Worst case this happens when you're far away from home ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Juni 2014, 10:11:51
Hello Willi,

Zitat von: willybauss am 01 Juni 2014, 09:59:06
additionally I need to rise the question what might happen if fhem stops working unexpectedly (due to bug, hw defect, ...) while THZ is in a mode different from automatic and/or where parameters are set to anything else than the"normal" ones. Worst case this happens when you're far away from home ...

This is only a heatpump with a boiler, the highest risk is the boiler compound with the booster. if the system doesnt works correkt there is now flow and the booster all on. the boiler can heat over 100 degree and explode. there is a hardware shutdown named STB ( Sicherheits Temperatur Begrenzer ) ( Safety tempreture limiter ). I think the risk with one user is ok...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Juni 2014, 10:22:10
Belu, no critic in your direction.
Everyone should decide how far you want to go.
My children (2y and 4y) play with FHEM, if they find a smartphone somewhere: they open the shutters, switch on lights. Therefore, critical stuff is out of reach, but no need for password protection.
loxone interesting: please share your impression.

Willy
To your question there must be only one answer
if FHEM crashes, nothing bad should happen.
as Belu noticed, definition of BAD is subjective.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Juni 2014, 10:37:18
Zitat von: immi am 01 Juni 2014, 10:22:10
Belu, no critic in your direction.
Everyone should decide how far you want to go.
My children (2y and 4y) play with FHEM, if they find a smartphone somewhere: they open the shutters, switch on lights. Therefore, critical stuff is out of reach, but no need for password protection.
loxone interesting: please share your impression.


Hi Immi,

loxone is a cheap homeserver. 400 Euro with 12 inputs 24 v dc, 8  x 230 v 6 A Outputs, 4 Analog Inputs 0 - 10 V and 4 Analog outputs and KNX compatibility.
I Used it for webinterface / Browser / Ipad / Smartphone to manage the House. Combined with a Loxone OneWire Modul i cant collective all tempreture and rel humidity.
All buttons and switches in my house are KNX based and get to the loxone. The outputs going to a Wago PLC with a KNX Module, 72 Outputs 24 v DC with relais and 5 x 4 0 - 10 v analog out to the heating servo motors.
works realy nice and stable together.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Juni 2014, 10:48:24
@ Willi

Risk; what happend when:

Heatpump runs without flow and no shutdown. >> Heatpump is reaching the max compressing and shutdown with error 8
All Booster runs without flow and no shutdown 10 KWh >> Safety temperature limiter reached max, hardware shutdown with error 2 and manual quit on the STB ( Sicherheitstemperatur Begrenzer )
Colling funktion THZ X04 under the dew point >> Danger can destroy building stock
Passivcooling without a window connect and a oven >> Danger no Shutdown, thick smoke and monoxid!!!! Dangerous to life!!!

I think the most critical function are passivcooling with a oven....

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Juni 2014, 20:16:53
Zitat von: belu am 01 Juni 2014, 10:11:51
Hello Willi,

This is only a heatpump with a boiler, the highest risk is the boiler compound with the booster. if the system doesnt works correkt there is now flow and the booster all on. the boiler can heat over 100 degree and explode. there is a hardware shutdown named STB ( Sicherheits Temperatur Begrenzer ) ( Safety tempreture limiter ). I think the risk with one user is ok...
If the risk of having a cold house and cold DHW in December is acceptable for you, you can go on raping your THZ control in any way you like.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 01 Juni 2014, 20:37:22
i agree with belu. fireplace and passivecooling is the highest risk. i can live in a cold house but i cannot survive in smoke and carbon monoxide.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Juni 2014, 08:06:03
@immi: Sorry, I was not around for testing. Love the speed changes. Works great for me!  8)

Belu is right at one point: If anyone in the family that is less experienced should use fronted to change settings, a predefined selection set is preferred. However, it SHALL NOT contain all setting option, like the op mode. Just use the safe and most common ones. If you want really want to select something like standby and emergency, then only at the LWZ/THZ display, or if you only want to use the dashboard, then have basic and (locked) expert settings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 02 Juni 2014, 15:31:58
@all

I did not start a fundamental discussion here. I wanted to advance the development. I find just the intervention harmless in such investments. I have a lot to do with industrial plant and do it professionally. Which plugin is used here or not everyone can weigh yourself.
I protect my FHEM area and there have also just me access. If someone is using these plugins and actively writes in the heating he must know what he's doing.

My first endeavor is to first gathering all possible information as it also makes the ISG Web. Then, the write functions that I consider to intigrieren useful.

My current problem is that the parameters of my heating so only partially equal to the parameters of the 303/403 are. I've a THZ 304 ..
How can I or we insert the fehlenen parameter in the THZ module?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Juni 2014, 16:29:10
Zitat von: belu am 02 Juni 2014, 15:31:58
My current problem is that the parameters of my heating so only partially equal to the parameters of the 303/403 are. I've a THZ 304 ..
How can I or we insert the fehlenen parameter in the THZ module?
Easy: tell me which missing parameter you are searching for and tell me the corresponding register, where it is stored in the heatpump and the corresponding format.
I will try to implement it in the THZ module.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Juni 2014, 17:07:02
immi, may i remind you in the solar set temp also? =) that is a parameter i miss. manual tells me it's P83.

thanks,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Juni 2014, 23:14:49
v0.105 uploaded, tomorrow you can update.
changelog
- even faster setting and getting (setting from 1.3s of v0100 to <0.1s)
- 2x faster refresh at the beginning
- thz attributes can be changed without restarting, on the fly
- fix in the interval routine
- p83 added
- added suffix temp to the  names of parameters p04 p05 p06 p11....: e.g. p04DHWsetDay is now p04DHWsetDayTemp.......  pay attention if you automated the DHW in the frontend.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Juni 2014, 07:27:55
yeeeehaw! :D
thanks a lot. update in wiki follows tomorrow.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 03 Juni 2014, 16:41:50
Zitat von: immi am 02 Juni 2014, 23:14:49
v0.105 uploaded, tomorrow you can update.
changelog
- even faster setting and getting (setting from 1.3s of v0100 to <0.1s)
- 2x faster refresh at the beginning
- thz attributes can be changed without restarting, on the fly
- fix in the interval routine
- p83 added
- added suffix temp to the  names of parameters p04 p05 p06 p11....: e.g. p04DHWsetDay is now p04DHWsetDayTemp.......  pay attention if you automated the DHW in the frontend.

immi

@immi great work,

I am also behind why the system increased which parameters such as means.
Unfortunately I only have the German manual. If someone comes to the English of the THZ 303 and 304 there? Did Google found nothing.
Immi, you do not mind if I look at myself again paramater accurate and something in the structure would alter it as it is in the user manual? would give more insight because it is equal to the structure menu.

Can you give me maybe explain how I come to the cmd2?

"p01RoomTempDayHC1" => {cmd2 => "0B0005", argmin => "13", argmax => "28"},

THX
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Juni 2014, 17:30:16
belu, you can find the englisch manual on the stiebel eltron page. tecalor doesn't have one i think.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 Juni 2014, 17:52:44
Zitat von: belu am 03 Juni 2014, 16:41:50
Can you give me maybe explain how I come to the cmd2?
"p01RoomTempDayHC1" => {cmd2 => "0B0005", argmin => "13", argmax => "28"},
German/eng I do not care
what I need is the register (cmd2) and the format (where the info is in the answer and how it is encoded)

You can get register and format in 3 ways
1) reverse eng. a working interface (software or hardware): man in the middle
2) log all registers, change only what you want manually, log all registers and see among all what has changed, what could be interesting.
3) ask  stiebeleltron for a complete documentation of all registers. The protocoll is now well-known.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Juni 2014, 18:58:28
wiki updated
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 03 Juni 2014, 20:21:07
Ok, i have registered as a professional on stiebel eltron. try the easy way to get the parameter...

i cant connect with a terminal programm to the usb port...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Juni 2014, 20:31:51
did you try to connect with different speeds? 115200/57600 are most common for USB. but there may some different speeds.

you need to connect with a special software like hterm which can send the needed information in a hex format to the heating. i don't think a standard terminal will ever get an answer from the THZ.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 Juni 2014, 20:42:35
belu
Markus is right
you have to send and receive hex

to read all regiseter, I wrote the debung function in thz line 1243
you can activate it with
get Mythz debug_read_raw_register_slow
and then play around

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 Juni 2014, 22:42:19
To see how the communication basically works you can have a look into the attached shell script. That was my starting point to THZ communication months ago. The important parts are the "sleep" rows. Sleep time must be between 10ms and 500ms (in my case), otherwise you won't get an answer from the heatpump.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Juni 2014, 21:46:04
Today it was too hot outside, so I decided to do some homework.
If you like to get informed in case of trouble you can use the following code as an axample.
define Mythz.alarm_failure notify Mythz { if (((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]) > ReadingsVal("Mythz","number_of_faults_old","ERROR")) { DebianMail('EMAILADDRESS@t-online.de','Tecalor Mythz Alarm - ERROR','Fehlermeldung: '. $EVENT);; fhem("setreading Mythz number_of_faults_old ". ((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]));; } }
attr Mythz.alarm_failure room Heizung

define Mythz.alarm_boosterDHW notify Mythz { if (((split ' ',ReadingsVal("Mythz","sHistory","ERROR"))[7]) > ReadingsVal("Mythz", "boosterDHW_old", "ERROR")) { DebianMail('EMAILADDRESS@t-online.de','Tecalor Mythz Alarm - boosterDHW','Zusatzheizung wurde fuer Warmwasser benutzt: '. $EVENT);; fhem("setreading Mythz boosterDHW_old ". ((split ' ',ReadingsVal("Mythz","sHistory","ERROR"))[7]));; } }
attr Mythz.alarm_boosterDHW room Heizung

define Mythz.alarm_boosterHeating notify Mythz { if (((split ' ',ReadingsVal("Mythz","sHistory","ERROR"))[9]) > ReadingsVal("Mythz", "boosterHeating_old", "ERROR")) { DebianMail('EMAILADDRESS@t-online.de','Tecalor Mythz Alarm - boosterHeating','Zusatzheizung wurde zum heizen benutzt: '. $EVENT);; fhem("setreading Mythz boosterHeating_old ". ((split ' ',ReadingsVal("Mythz","sHistory","ERROR"))[9]));; } }
attr Mythz.alarm_boosterHeating room Heizung


Since the values are saved in the ..._old readings you'll get just one email for any change of values. I decided to save the values in "dummy" readings instead of perl variables, to ensure that they're still available, even after reboot.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Juni 2014, 13:43:11
I have the phone today with some people from Stiebel Eltron order to get the parameter.
Did not get canceled, I should an email letter, this will then be reviewed and submitted to the Executive Board.
We enter halt into direct competition with the ISG Web.
So let's wait and see.
A direct access to the open source community does not form a heater manufacturers. I am thinking here of the market could be larger. Better at the end of heaters sold more than a few ISG Web.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juni 2014, 13:56:13
Zitat von: belu am 10 Juni 2014, 13:43:11
I have the phone today with some people from Stiebel Eltron order to get the parameter...

Balu: For a better understanding: Can you post this in German? Thanks!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 14:06:51
@ immi:
I'm pretty sure to have found two bugs.

1st issue:
I tried to program a night time interval for programFan_Mo-So from 22:00 till 09:00. As mentioned in the THz manual I need to split it into two partsBut the first part isn't possible using fhem, since argMax is set to "23:59" instead of "24:00".

Trying to use what's maximal possible ends up in a programmed time range of 22:00--23:45, since the THZ isn't capable of managing single minute ranges. So finally the range of 23:45 till 24:00 is programmed wrongly.

I'd like to know if there was really a need of setting argMax to "23:59" instead of "24:00", or if that's just a mistake? Currently I'm not at home, but tonight I can try to modify the code in order to check how it behaves using 24:00. I'll let you know the answer.

2nd issue:
My settings are No matter if I set (using fhem) the programmed time to 09:00--22:00 or to 22:00--09:00 (in two steps as mentioned above) the real fan speed always keeps same. So it looks like the same behavior, we already observed with the UnschedVent settings: they're set but not activated, when programming is being done with fhem instead of using the THZ display.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juni 2014, 14:13:54
And I thought I was the only one. I believe I also found a bug: programFan_Mo-So_0  I have it set to end at 8 am but instead it turns off at 6 am every day.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 14:51:38
Zitat von: houseowner123 am 10 Juni 2014, 14:13:54
And I thought I was the only one. I believe I also found a bug: programFan_Mo-So_0  I have it set to end at 8 am but instead it turns off at 6 am every day.

Tom
Could you try to make same setting again, but using the THZ display instead of fhem? I assume that it will work then, as described above "... set but not activated, when programming is being done with fhem instead of using the THZ display".
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juni 2014, 15:17:05
will do and report back!  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Juni 2014, 15:32:02
@houseowner123

Also hier mal etwas ausführlicher und auf deutsch,

Ich habe heute Vormittag mit Stiebel Eltron Telefoniert. Wurde 5 mal weitergeleitet bis mir da jemand qualitativ aussagen treffen konnte. Das war dann der Fachleiter für die Schulungen des ISG WEB. Mit ihm hatte ich dann ein ausführliches Gespräch.
Habe ihm dann erklärt das ich Teil einer Community bin die für die LWZ / THZ ein Modul auf Basis der GNU Public Privacy mit Linux entwickelt. Das wir die Anlage auslesen und teilweise auch steuern könnten.
Das der Code der 303 / 403 schon zu 90 % entschlüsselt ist. Nach einer Grundsatzdiskussion das es nicht illegal ist und das es mein Gerät ist und ich ihm es mit einem Auto verglichen habe das eine OSB Schnittstelle hat...
Naja nach etwas Aufklärung und Sinn des Projektes war er recht begeistert. Hab ihm erklärt das es auf dieser Basis kein anderer Heizungshersteller anbietet und das man sicherlich die ein oder andere Heizung an einen Technik Freak der ein Niedriegenergie Haus bauen möchte mehr verkaufen kann als die Konkurrenz.
Sein haken ist halt das sie sicherlich weniger ISG WEB verkaufen werden und das er das nicht entscheiden kann.
Leider ist der Entwickler der THZ / LWZ im Urlaub. Aber es müsste eh Grundsätzlich abgeklärt werden ob die Geschäftsleitung es möchte das die Parameter öffentlich genutzt werden. Ich meinte halt das es nur eine Arbeitserleichterung und mehr Sicherheit gibt wenn sie uns dabei helfen.
Es ist also eine WIN WIN Situation für beide.

Vielleicht hat ja jemand lust mit mir diese Mail zu verfassen. Es würde uns schon ziemlich helfen wenn seitens Stiebel Eltron die Schnittstelle geöffnet wird.

Achja ich hab mir gerade mit 5,86 Euro eine Sommerkassette gebaut...

LG

Belu
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Juni 2014, 15:56:41
Willy, I am just back from swimming. Life is hard... on holiday  ;D
I will look at your points in the next days.

Belu
nice job. I agree that it would be a win-win solution.
Be stubborn, keep on pushing.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 16:06:03
Zitat von: belu am 10 Juni 2014, 15:32:02
Das der Code der 303 / 403 schon zu 90 % entschlüsselt ist. Nach einer Grundsatzdiskussion das es nicht illegal ist und das es mein Gerät ist und ich ihm es mit einem Auto verglichen habe das eine OSB Schnittstelle hat...
Naja nach etwas Aufklärung und Sinn des Projektes war er recht begeistert. Hab ihm erklärt das es auf dieser Basis kein anderer Heizungshersteller anbietet und das man sicherlich die ein oder andere Heizung an einen Technik Freak der ein Niedriegenergie Haus bauen möchte mehr verkaufen kann als die Konkurrenz.
Was er mit Sicherheit gedacht, aber natürlich nicht gesagt hat, ist, dass sie in Zukunft sehr genau hin sehen werden, wenn Jemand innerhalb der Garantiezeit mit einem "komisch" aussehenden Fehler daher kommt. Ich kann nur Jedem raten, den Begriff fhem aus dem Gedächtnis zu streichen und das Kabel zu entfernen, wenn ein Servicetechniker naht, zumindest solange die Garantiezeit noch nicht rum ist. Man kann z.B. den Kompressor plus Booster starten und manuell die Pumpe ausschalten, dann überhitzt das Teil ruck zuck. Und wenn Stiebel Eltron dann zur Vermeidung hoher Garantiekosten behauptet, deine selbst gestrickte Software sei schuld, dann wird es eng - unabhängig davon, ob das THZ-Modul von fhem das aktuell hergibt oder nicht.

Ein OSB (http://www.wissenwiki.de/OSB)-Auto - cool  ;) . Meins hat nicht mal USB ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 16:07:57
Zitat von: belu am 10 Juni 2014, 15:32:02
Achja ich hab mir gerade mit 5,86 Euro eine Sommerkassette gebaut...
Dann solltest du halt tagsüber die Lüftung ganz ausschalten, sonst wirds ordentlich warm in der Bude - der Nachteil der Sommerkassette.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Juni 2014, 16:09:27
Zitat von: willybauss am 10 Juni 2014, 16:06:03
Was er mit Sicherheit gedacht, aber natürlich nicht gesagt hat, ist, dass sie in Zukunft sehr genau hin sehen werden, wenn Jemand innerhalb der Garantiezeit mit einem "komisch" aussehenden Fehler daher kommt. Ich kann nur Jedem raten, den Begriff fhem aus dem Gedächtnis zu streichen und das Kabel zu entfernen, wenn ein Servicetechniker naht, zumindest solange die Garantiezeit noch nicht rum ist. Man kann z.B. den Kompressor plus Booster starten und manuell die Pumpe ausschalten, dann überhitzt das Teil ruck zuck. Und wenn Stiebel Eltron dann zur Vermeidung hoher Garantiekosten behauptet, deine selbst gestrickte Software sei schuld, dann wird es eng - unabhängig davon, ob das THZ-Modul von fhem das aktuell hergibt oder nicht.

Ein OSB-Auto - cool  ;) . Meins hat nicht mal USB ...

Nenn es wie du möchtest... EOBD OBDII OBD 2 Ist auch egal...  OBD
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juni 2014, 16:20:22
Zitat von: willybauss am 10 Juni 2014, 16:06:03
Was er mit Sicherheit gedacht, aber natürlich nicht gesagt hat, ist, dass sie in Zukunft sehr genau hin sehen werden, wenn Jemand innerhalb der Garantiezeit mit einem "komisch" aussehenden Fehler daher kommt. Ich kann nur Jedem raten, den Begriff fhem aus dem Gedächtnis zu streichen und das Kabel zu entfernen, wenn ein Servicetechniker naht, zumindest solange die Garantiezeit noch nicht rum ist.

While still under warranty, this should be a no brainer to pull the USB cable..
Thanks for pushing this with SE, balu. I am less optimistic, however. Their sales department will veto this because of ISG Web with its outragous price. Second their lawyers will not like it either because the software control in the wrong hands could mean trouble as willybaus described. Also, by opening the code to the public, you can also run into prorietary issues, like giving away secrets to the competition or have somebody in China copy your product 1:1. And that is a hard thing to argue. The only chance I see that they will give it away when the current THZ that can be controlled by the module is outdated.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Juni 2014, 16:33:18
Zitat von: houseowner123 am 10 Juni 2014, 16:20:22
Thanks for pushing this with SE, balu. I am less optimistic, however. Their sales department will veto this because of ISG Web with its outragous price. Second their lawyers will not like it either because the software control in the wrong hands could mean trouble as willybaus described. Also, by opening the code to the public, you can also run into prorietary issues, like giving away secrets to the competition or have somebody in China copy your product 1:1. And that is a hard thing to argue. The only chance I see that they will give it away when the current THZ that can be controlled by the module is outdated.

hi tom
I have never read a summary so narrow-minded and fuddy-duddy.
But you are right, because lots of enginnering endeavor are just bocked by people playing with the fear and making terror. What could happen if ...? have you made an FMEA? Have you asked your legal department?
I go back in the water.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 17:05:21
Zitat von: immi am 10 Juni 2014, 16:33:18
hi tom
I have never read a summary so narrow-minded and fuddy-duddy.
But you are right, because lots of enginnering endeavor are just bocked by people playing with the fear and making terror. What could happen if ...? have you made an FMEA? Have you asked your legal department?
I go back in the water.
immi
I don't name it  narrow-minded nor  fuddy-duddy, since I believe it's not tom's opinion but just the (rightly assumed) thinking of the addresees. They're of course related to their responisibilities and much less (if at all) to our hobby project. That's simply a fact, no matter if we like it or not. But I'd like to see that I'm wrong, so let's hope and wait for the answer.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 10 Juni 2014, 18:15:10
i remember car manufacutrers have made similar statements to people who connect open source or third party OBD systems to their cars. some courts judged that this is no problem as long as the parameters change are not out of the specs given by the manufacturer. and i guess that we do nothing out of specs. we are just changing values remote instead of at the panel. same with a computer... just changing the hardware (memory, CPU, ...) does not affect the guarantee of the rest of the system at all as long as you are following the manuals.
so i guess thats all more or less big blahblah... :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juni 2014, 21:24:09
Fuddy-duddy is the term of the day, I guess. ;)
I currently work at the intersection between academia and big industry. I learnt to there are always two sides of the coin and in the end you gotta sell it to your partner to secure the deal. Since I focused on the negative side before here, comes the plus side: Heat pumps, especially air heat pumps have become a tough sell, especial since the EEG Umlage is already by 6 cents now and will rise in the future. Federal regulators have also realized they are not efficient (greeting to immi!) as they can be and withdrew federal loan support for the 303/304 model. Look here: http://www.bafa.de/bafa/de/energie/erneuerbare_energien/publikationen/energie_ee_waermepumpe_liste_ab_2013.pdf
SE therefore will present a new model this fall: http://www.stiebel-eltron.de/erneuerbare-energien/produkte/lueftung/integralgeraete-mit-zentraler-zuluft/lwz-504/

However, since amazon.com, every seller knows how important ratings and customer satisfaction are. The programming brains of this group (definitely not me) have realized the potential that is still in almost outdated models, to improve handling, customizing to specific needs, monitoring and most important to ingrate the the/lwz into general house automatization (which is without a doubt the future). We as group are faster as an SE engineers group to come up with ideas (email alerts, temperature information, heating programs, etc) that make the lwz/thz more attractable to customers.
Permanent monitoring and alerting can help reduce customers cost. Most LWZ are badly setup and neglected and waste energy which in turn give it a bad reputation. FHEM THZ module can change that and if the engineers want they can integrate some of our customization into their software. They can only benefit from this group because we are dedicated customers which provide open feedback they can use for their own development.

Not to forget there is also a Viesmann FHEM and soon any heating system will be part of this. So, by endorsing this, SE could be front runners. We are their Fan base! :)

OK, the only downside: We are not a legal group. So accountability is a problem. What if somebody creates a virus and writes it in here. Maybe Rudof König could help us out in this sense, that somehow the code is protected from any misuse or so. If somebody knows of a lawyer, that could provide legal advice...that would be great.

Again just my two cents. Balu, if I can help you, drop me a PM.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 21:31:21
 
Zitat von: micomat am 10 Juni 2014, 18:15:10
... i guess that we do nothing out of specs. we are just changing values remote instead of at the panel...
I spent the last two hours to proof that this assumption is wrong: we're changing values, yes. But with a different result than changing them via the panel. Therefore the argument would be (rightly) that we don't know/understand what we're doing.

@immi:
I meanwhile can confirm that my assumption regarding to the 2nd issue (see my posting of today 14:06:51) is right. Changing timing settings of fan programs is possible, the result of these changes is visible on the THZ display, BUT the changed settings are never activated. Fan speed doesn't change at all, no matter if I try to define a day or night mode using any one of the time definitions. The only way I found to activate the changed settings is, to open the setting in the THZ display and change it again. Just opening and confirming the existing settings doesn't work; it definitely needs to be changed again using the THZ display.

That's exactly the same behavior I already reported months ago for the pXXUnschedVentY settings and for party-time. I strongly believe it's the same for all DHW, HC1, HC2 and holiday timing settings.

Summarizing these results I have to say that approx. 130 set parameters are not in working condition.


Regarding to the 1st issue  (see my posting of today 14:06:51) I can confirm that changing time values works correctly, when argMax is being changed from "23:59" to "24:00". But since 2nd issue is not (yet) fixed that doesn't help in any way currently.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 21:40:18
@ Tom
I'd like to read the linked documents, but unfortunately the links seem to be broken. Could you please repair them or send them to me via PN?
Thanks
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Juni 2014, 22:17:24
Hi,

tomorrow will write something for Stiebel Eltron considering all the arguments. Dangers I'll talk small and emphasize the benefits.

Oh I was thinking something about the No Bypass ...
I currently have a simple KG 125 tube in it, built as a summer cassette air sealing in the exhaust duct.
Operate it now with passive cooling mode 4, works great so far.

I find the approach with a ground heat exchanger is not bad, I have only to consider the fresh air and the drain.
In summer the works so wonderful with a siphon and 2% gradient. Since I'm only afraid of mold and bacteria.
In winter, it can dry out the siphon and then I draw the air out of the sewers.

Those are actually both no good stuff.
For the summer, I've already looked at me it would really make sense, a bypass to the fresh air to attach suction.

Covered because of such a thing. http://intelmann.net/index.php/cat/c41_Bypassklappen-Bypassklappen.html

The idea is. in the summer to pull in operation with the summer cassette air from the basement to the air quality and to improve the temperature.
I have a passive house. So air change is <= 0.6 N5 which means it is partly really stuffy after 12 hours with no ventilation.
Had it today simply tested times in which I have the fresh air pipe settled and closed.
Works really well, the air from the basement has 18 degrees and then flows into the rooms with 25 ..
Somehow I got to the heat exchanger, the heat can not be dissipated get the last days. Therefore, today the idea of ​​the summer cassette.

What do you think?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 10 Juni 2014, 22:23:05
@willy

At least I can support you with the link to the LWZ504 (which is a really nice HP with inverter)
http://www.stiebel-eltron.de/erneuerbare-energien/produkte/lueftung/integralgeraete-mit-zentraler-zuluft/lwz-504/ (http://www.stiebel-eltron.de/erneuerbare-energien/produkte/lueftung/integralgeraete-mit-zentraler-zuluft/lwz-504/)

@Topic

Call me pessimistic. But I wouldn't be surprised if newer upcoming firmware releases for THZ/LWZ would need a hardware dongle, that secures the communication with the LWZ/THZ and therefor ist restricted to authorizes service personal or users that pay for ISG Web etc.
Hopefully this is only pessimistic, as also the development of this would cost extra money and SE maybe comes to the point, that the FHEM community is rather small. But on the other side those big companies won't get taken the butter from their breads  ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 10 Juni 2014, 22:26:53
Zitat von: houseowner123 am 10 Juni 2014, 21:24:09

OK, the only downside: We are not a legal group. So accountability is a problem. What if somebody creates a virus and writes it in here. Maybe Rudof König could help us out in this sense, that somehow the code is protected from any misuse or so. If somebody knows of a lawyer, that could provide legal advice...that would be great.

Again just my two cents. Balu, if I can help you, drop me a PM.

Tom

Not a Problem i think. could Happen to any Open Source Software. GPL/GNU or whatever fhem is licensed to will Take care of this legal issue.

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 10 Juni 2014, 22:29:48
Zitat von: lwzler am 10 Juni 2014, 22:23:05
@Topic

Call me pessimistic. But I wouldn't be surprised if newer upcoming firmware releases for THZ/LWZ would need a hardware dongle, that secures the communication with the LWZ/THZ and therefor ist restricted to authorizes service personal or users that pay for ISG Web etc.
Hopefully this is only pessimistic, as also the development of this would cost extra money and SE maybe comes to the point, that the FHEM community is rather small. But on the other side those big companies won't get taken the butter from their breads  ;)
no way. Nobody would Pay for. also in Case of a Problem with such a dongle the Wohle Heating can fail. Never Seen such lockouts then in license environments.

stiebel woulndt be so stupid ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Juni 2014, 22:55:03
Hi Markus
>>i remember car manufacutrers have made similar statements to people ......
you were reading my mind.

Zitat von: houseowner123 am 10 Juni 2014, 21:24:09
What if somebody creates a virus and writes it in here. Maybe Rudof König could help us out in this sense, that somehow the code is protected from any misuse or so. If somebody knows of a lawyer, that could provide legal advice
Hi Tom
It would be great, if you support Belu with the comunication with Stiebel Eltron.

You are right. I could put a trojan  in the code, like each of the 30 people with write access to  sourceforge repository. But the nice thing behind an open source project, is that each of you will see what each developer did to each fhem modules.  I think this model is safer than each compiled propietary software you are using every day.

Rudolf could lead FHEM in a over-safe direction. I really hope we will not do it.

p.s. We need lawyers, if they are ready to learn perl. If Stiebel Eltron shares some documentation (at very high engineering level), they are not responsible of the misuse of the information, because it can only be read by an expert. Product liability (produkthaftung) (at least in europe) takes  care of  protecting the weak side.


Hi Willy
I am definitelly not in the mood of looking at the code.
Thanks for testing carefully before reporting a bug.
Could you make one more check?

Instead of changing only with FHEM programFan_Mo-So_0, could you change also programFan_Mo_0 programFan_Tu_0 ......
I am not checking in 00_THZ, if  there is a conflict between the whole week and each day.
I think the display takes care of fixing such a conflict.

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Juni 2014, 23:16:53
Zitat von: immi am 10 Juni 2014, 22:55:03
Could you make one more check?

Instead of changing only with FHEM programFan_Mo-So_0, could you change also programFan_Mo_0 programFan_Tu_0 ......
I am not checking in 00_THZ, if  there is a conflict between the whole week and each day.
I think the display takes care of fixing such a conflict.

Hi immi,

of course I could do it, but it would be a waste of time. Before I started testing I ensured all other fan related values to be in "n.a.--n.a." state. I did it twice - first with fhem and then additionally by crawling through all the menu items in the THZ display. So there's definitely no conflict. Additionally, as I already said, the result fits the previous observations of party-time and unschedVent. In these values there's no possibility of a conflict at all.

Just enjoy your vacation and come back recovered. We can wait some time. Since we know about the issue it's an easy workaround to not change these values via fhem for a while.

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Juni 2014, 10:52:23
Zitat von: willybauss am 10 Juni 2014, 14:51:38
Could you try to make same setting again, but using the THZ display instead of fhem? I assume that it will work then, as described above "... set but not activated, when programming is being done with fhem instead of using the THZ display".

I did it and it is fixed now. I don't think that FHEM is to blame (maybe). The problem was that I had entries for the individual work days and Mo-So. It is not problem if you never change the air settings for day/night like during winter. But during the summer...the control is confused. So I eliminated individual day entries and now it is working fine.

To all: How did you make through the heat wave? Which settings worked best (times and temperatures). Maybe we can compare setting and can come up with a good "cooling config paragraph".
I only did normal Sommerkassette cooling level 2 from 9:30 pm to 8 am. In house temps increased 1,5°C per day. Upper floor humidity (bed rooms) is biggest problem. How do get the cold basement air up there? And since the basement air (18°) has 70% humidity, aren't you making problems worse by pushing it upwards?

Tom

PS: links in my previous post are fixed now.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 Juni 2014, 11:15:19
Zitat von: houseowner123 am 11 Juni 2014, 10:52:23
I did it and it is fixed now.
happy

[/quote]
... How do get the cold basement air up there? And since the basement air (18°) has 70% humidity, aren't you making problems worse by pushing it upwards?
[/quote]
I have not computed it but just by feeling. As soon as you 18°C 70% will go upstairs (if you find a solution for it), they will be heated to 24°C or more with 55% hum, which ould be acceptable
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 11 Juni 2014, 14:12:26
i close all my shutters in the morning and set passive cooling to 1.
opend a window in ground floor and first floor and opened also the door to the basement.
doesn't help too much but a little is better than nothing.

ground floor about 25°C/50%, 1st floor 27°C/55%

i would love to soak up the basement air also but i have no idea how that could work without the special "fortluftklappen passivkühlung" described in the manual.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Juni 2014, 17:47:26
Zitat von: micomat am 11 Juni 2014, 14:12:26
i close all my shutters in the morning and set passive cooling to 1.
That's ok.
Zitat von: micomat am 11 Juni 2014, 14:12:26
opend a window in ground floor and first floor and opened also the door to the basement.

doesn't help too much but a little is better than nothing.
That's not ok, if it's also being done in the morning. Passive cooling just works during night time, when outside temperature is less than inside temp. As soon as outside temp rises in the morning the passive cooling mode is being switched off automatically, going back to normal fan operation. Therefore you need to activate passive cooling in the evening and open the windows over night.

Since I decided to not install a summer cassette I set the lowest fan levels (1 or even 0) during daytime; the more fresh air, the more heat comes into the house, since the efficiency factor of the heat exchanger is < 100%. During night time I proceeded as described above: fan level 3 + passive cooling type 1, some windows opened (just in "air input" rooms, not in exhaust rooms!

Passive cooling doesn't make sense if you have a summer cassette. Passive cooling is just a workaround in order to bypass the heat exchanger, what's not necessary in case of a summer cassette.

Does it really make sense to bring the cool air from basement up into the upper floors? This will result in warm air to flow from upper floors into basement, to avoid a vacuum there. Sooner or later the basement will be heated up as well by this air flow ... And: as long as it's warm outside you should NOT open the windows in basement to avoid vacuum. Otherwise the warm air flows through the windows into basement, cools down and the humidity rises due to cooling down. This is a frequent error, causing mould problems sooner or later.

When I planned my house I also thought about distributing heat through the ventilation system. But it turned out quickly that the energy content of air is much too less to be really efficient. That's the reason why you can cool down your houses a whole night long using highest ventilation speed without big effect. The ideal house would have perfectly isolated wooden outside walls ("Holzständerbauweise"), but heavy stone made walls inside, which have a very high storage capacity for heat (in winter) or cold (in summer).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Juni 2014, 20:10:17
Nice and correct summary, willy!

One more thing comes to mind to accelerate the air exchange: Increase p39 and p42 Airflow settings. Mine are currently set at 220 m^3/hr with a heated house volume 452 m^3. One complete air volume change would take 2 hrs. How is the setting in your houses and are their recommendations or guidelines how high one can go with the exchange rate?

I also thought to use the IF command to set p08FanStageNight= 3, when the filtered outside temp is lower than the filtered inside temp and return to p08FanStageNight=0 when the ratio is reversed or has a 1 degree difference.  So, you don't accidentally warm up the house.

I mentioned before that the heat recovered counting continues despite floor heating off and a Sommerkassette in place. I believe the reason for that is, that the inlet air temp is measured by the the and together with the flow rate, the heat amount is simply calculated. If air flow is set to zero - recovered heat remains zero.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 11 Juni 2014, 22:14:54
willy, of course only in the night time.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Juni 2014, 23:14:51
Zitat von: houseowner123 am 11 Juni 2014, 20:10:17
One more thing comes to mind to accelerate the air exchange: Increase p39 and p42 Airflow settings. Mine are currently set at 220 m^3/hr with a heated house volume 452 m^3. One complete air volume change would take 2 hrs. How is the setting in your houses and are their recommendations or guidelines how high one can go with the exchange rate?
I forgot to mention that I did exactly this already in last summer.
p39: 240m³
p42: 284m³
The different settings are intended: airflow measurements showed that these settings are necessary to ensure almost identical in- and putput flows. I say "almost identical" since I wanted to force a very slight under-inflation to surely avoid over-inflation, which can cause damages to the building in winter time.

Zitat von: houseowner123 am 11 Juni 2014, 20:10:17I also thought to use the IF command to set p08FanStageNight= 3, when the filtered outside temp is lower than the filtered inside temp and return to p08FanStageNight=0 when the ratio is reversed or has a 1 degree difference.  So, you don't accidentally warm up the house.
I don't think that's necessary if you use passive cooling mode: in this mode THZ itself checks for useful temperature ranges and switches back to "normal" operation if passive cooling mode isn't sensible. If you have a summer cassette installed it might be useful of course.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 12 Juni 2014, 21:30:02
Immi: from config file:
2014.06.12 19:34:23 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe timeout to slow?
and
Use of uninitialized value in concatenation (.) or string at ./FHEM/00_THZ.pm line 1006.

in other news: air ventilation timing settings are out of control, even when I set them on the the/lwz display. Just free running on current setting 24/7. Restart did not help. Any ideas?

Thanks,
Tom

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 Juni 2014, 21:42:38
passive qooling thought-chain...

when using passive cooling set to 1, the incoming air fan is disabled, the exhaust air fan is increased.
fresh and cool air is soaken up from e.g. open windows or basement and will flow via the exhausts through the flat.

when using setting 2 the manual tells me not to open the windows. i have a very airthight house. so i think i wont have an advantage with overpressure only. so maybe i will try it to open a windows also to blow out the warm air as the inlet air wont be heated through the heat exchanger when the exhaust fan is disabled.


hm.... :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 Juni 2014, 23:02:31
Zitat von: houseowner123 am 12 Juni 2014, 21:30:02
Immi: from config file:
2014.06.12 19:34:23 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe timeout to slow?
and
Use of uninitialized value in concatenation (.) or string at ./FHEM/00_THZ.pm line 1006.

in other news: air ventilation timing settings are out of control, even when I set them on the the/lwz display. Just free running on current setting 24/7. Restart did not help. Any ideas?

Thanks,
Tom
What did you restart - fhem or THZ? In case of trouble I suggest you to unplug the cable to fhem-server and press the THZ's reset button for at lease 20 ... 30 seconds. Then check carefully all fan program settings for single days, for Mo-Fr, Sa-So and Mo-So. Correct any possible inconsistenciesand possibly try another reset afterwards.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 Juni 2014, 23:05:48
Zitat von: micomat am 12 Juni 2014, 21:42:38
when using setting 2 the manual tells me not to open the windows.
My version of the manual doesn't forbit to open the windows, it just says you do not need to open windows. Of couse with open windows the efficiency is much better.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 12 Juni 2014, 23:20:05
Telling not to do so is not a forbiddance :)
will try it
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 Juni 2014, 09:50:47
Zitat von: houseowner123 am 12 Juni 2014, 21:30:02
Immi: from config file:
2014.06.12 19:34:23 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe timeout to slow?
and
Use of uninitialized value in concatenation (.) or string at ./FHEM/00_THZ.pm line 1006.
in other news: air ventilation timing settings are out of control, even when I set them on the the/lwz display. Just free running on current setting 24/7. Restart did not help. Any ideas?
Hi Tom
"Maybe timeout to slow?" is coming each time the comunication is faulty. Nothing bad, you are just dropping a request, which should be repeated. The second warning is related to the first.
If you have too much of these logs, we have to dig deaper.

For the timing setting, I need to be home for verifying also what Willy wrote. Please share your progress.

I still have not understood how the firmware interpretes conflicts: and there are lots of combination possible.
My Hypothesis (never checked) looks like this:
1) daygroups (x_Mo-Fr_x , x_Mo-So_x and x_Sa-So_x) are only relevant for the display
2) Single days (x_Mo_x, x_Tu_x, x_We_x ...) are used by the firmware to control the heatpump.
3) when you change in the display daygroups, also sigle days are accordingly changed.

I never implemented any rule between sigle days and daygropus in 00_THZ, because I am not sure of the above, which could be too easy. I expect something more creative:)

As you see, it would be great to have a complete documentation of the firmware. We could concentrate on new features or stability, instead of reverse eng. the heatpump.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Juni 2014, 23:35:30
I made a small test for the program times. I used HC2 for it, which is unused in my case, so I don't risk breaking my working setup. I believe the system works same for e.g. fan or DHW programming.Summarizing it looks like always the last entry wins, but just in case of same value id (Mo_1, Mo_2, Mo_3).


Further tests with different ids show that "last entry wins" is limited to values of same id. Discrepencies with different ids are not solved, nor overwritten, e.g.Tue and Wed have finally two entries with overlapping timesTherefore it's very easy to ensure having all programs removed: set Mo-So_1,  Mo-So_2 and  Mo-So_3 to any value and afterwards reset  them to --:-- - --:--. This removes all other settings for single days etc. as well.

I did all of these tests using the THZ display. I intentionally avoided using fhem to set values, since we know (see my posting of a few days before) that this would set, but never activate values, which would result in nothing else but confusion.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 16 Juni 2014, 10:26:56
@willy: I was thinking of you, wehn I read this. May be worth checking out this winter as it comes directly from Stiebel-Eltron:

Some settings for advanced fine tuning of heat pumps

Beyond these more commonly adjusted controls are a number of additional refinements to consider:

1.Kelvin Minutes
This setting governs how hard a heat pump works. It looks at the temperature of the water in your heating system and compares the set temperature (decided by the heat curve and outside temperature) with the actual water temperature. If the temperature is close to the set temperature it waits a relatively long time before recalculating and turning the pump up to speed heat up or down if the set temperature has been reached (to see how little effort is required to maintain the set temperature). If the differential is large it waits a short time before recalculating and adjusting the effort up or down. So for example if the temperature of the water is rising 2 degrees every minute, the controller might add 2 minutes to the time before recalculating the effort required. As the water comes closer to the set point the intervals between recalculations get longer and longer. There is a manual setting from 0-500 that allows you to influence the intervals between recalculations – so if we take our earlier example we might slow the response so that the system adds 4 minutes instead of 2 to its thinking time when the temperature is rising at 2 degree every minute Slowing the response like this will have a beneficial effect on efficiency as the heat pump will work less hard – but of course this can be at the expense of response time. This is where buildings with a large thermal mass (think those with thick solid stone walls) can benefit. Because they have a high thermal mass they will cool down relatively slowly and you can afford to be more conservative about how responsive you are to fluctuations in outside temperature, without risking sudden drops in the internal temperature. For example, these buildings may well manage to retain heat during a short cloudy or showery spell , compared to a lightweight timber-framed construction in which the temperature drop may be felt as unacceptable.

source: http://www.stiebel-eltron.co.uk/business-partners/news/technical-expert-blog/fine-tuning-heat-pumps/ (http://www.stiebel-eltron.co.uk/business-partners/news/technical-expert-blog/fine-tuning-heat-pumps/)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Juni 2014, 16:35:14
Hi tom,


thanks for the hint. I've been aware of this parameter and already thought about how to use it in a sensible way. I have to read the blog again to really understand how it could impact on my thoughts.

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Juni 2014, 23:13:54
Hi Tom
as far as I understand integralComponent should be a good friend of kelvin :)

v0106
changelog
-P30integralComponent added
-major change in parsing function. Parse (for the get function) is now more readable and customizable.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 Juni 2014, 00:19:19
You're awesome! :)

Gesendet von meinem Nexus 7 mit Tapatalk

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 19 Juni 2014, 09:44:19
0.106 installed and found to be great :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 19 Juni 2014, 14:45:39
If you have implemented an alarm notify sending you an email in case of trouble, you can also force it to add an attachment containing the list of failures, as mentioned in the installation manual. The text file is attached here.

The notify needs to be modified a bit, in order to add the path to the attachment:

define Mythz.alarm_failure notify Mythz { if (((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]) > ReadingsVal("Mythz","number_of_faults_old","ERROR")) { DebianMail('YOUREMAILADDRESS@t-online.de','Tecalor Mythz Alarm - ERROR','Fehlermeldung: '. $EVENT,'/mnt/fhem/Tecalor-Fehlermeldungen.txt');; fhem("setreading Mythz number_of_faults_old ". ((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]));; } }
attr Mythz.alarm_failure room Heizung


In above code    /mnt/fhem/Tecalor-Fehlermeldungen.txt   is the path to the attachment, which has to be adjusted to your needs.

Additionally you need to modify the function DebianMail in your 99_myUtils.pm, so that it can support attachments:

package main;
use strict;
use warnings;
use POSIX;
sub
myUtils_Initialize($$)
{
my ($hash) = @_;
}
######## DebianMail  Mail auf dem RPi versenden - incl. Attachment ############
sub
DebianMail
{
my $rcpt = shift;
my $subject = shift;
my $text = shift;
my $attach = shift;
my $ret = "";
my $sender = "YOUREMAILADDRESS\@t-online.de";
my $konto = "kontoname\@account.de";
my $passwrd = "YOURPASSWORD";
my $provider = "securesmtp.t-online.de";
Log 1, "sendEmail RCP: $rcpt";
Log 1, "sendEmail Subject: $subject";
Log 1, "sendEmail Text: $text";
Log 1, "sendEmail Attachment: $attach";

$ret .= qx(sendEmail -f '$sender' -t '$rcpt' -u '$subject' -m '$text' -a '$attach' -s '$provider' -xu '$konto' -xp '$passwrd' -o tls=auto);
$ret =~ s,[\r\n]*,,g;    # remove CR from return-string
Log 1, "sendEmail returned: $ret";
}
1;


And finally - since DebianMail got an additional argument -  you need to add an additional empty argument to every one of your already existing DebianMail calls: directly after the text argument you need to add


,''


e.g. it could finally look like


define Mythz.alarm_insideTempLow notify Mythz { if (ReadingsVal("Mythz","inside_temp","ERROR") < 19 ) { DebianMail('YOUREMAILADDRESS@t-online.de','Tecalor Mythz Alarm - insideTemp','Innentemperatur zu niedrig','');;;; } }


Afterwards everything should work as before, but you get hints for root cause of failure additionally as soon as THZ informs you about any trouble.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 21 Juni 2014, 09:46:30
Since the last update the Main fan power in sGlobal is always zero. Does anybody else have the same issue?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Juni 2014, 10:40:02
Hi Tom
For me it is working.

2014-06-21_02:10:59 Mythz sGlobal: outsideTemp: 12.8 flowTemp: 50.6 returnTemp: 47.7 hotGasTemp: 87.5 dhwTemp: 45.8 flowTempHC2: -60 evaporatorTemp: 4.7 condenserTemp: 49.4 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 1 heatingCircuitPump: 0 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 30 inputVentilatorPower: 30 mainVentilatorPower: 70 outputVentilatorSpeed: 21 inputVentilatorSpeed: 28 mainVentilatorSpeed: 20 outside_tempFiltered: 14.2 relHumidity: 0 dewPoint: 0 P_Nd: 4.38 P_Hd: 23.12 actualPower_Qc: 4491 actualPower_Pel: 5243 collectorTemp: -60 insideTemp: -60

Search for "compressor: 1" in the logfile. It is hot, therefore mainVentilatorPower should remain 0 mostly all the time.
The last update was critical in parsing, keep me informed.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Juni 2014, 18:45:16
immi is right. main vent is only working when the compressor is running :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 21 Juni 2014, 20:06:20
For whatever the reason, all is normal now again. :) Hope it stays that way.  But thanks for the confirmation, immi and Markus!

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 22 Juni 2014, 14:56:12
I updated to latest version an now it seems that the example configuration from the wiki is not working witht the FanSelectors.
I always get

FanSelectorDay: unknown attribute webCmd. Type 'attr FanSelectorDay ?' for a detailed list. FanSelectorDay: unknown attribute devStateIcon. Type 'attr FanSelectorDay ?' for a detailed list. FanSelectorNight: unknown attribute webCmd. Type 'attr FanSelectorNight ?' for a detailed list. FanSelectorNight: unknown attribute devStateIcon. Type 'attr FanSelectorNight ?' for a detailed list. FanSelectorDay: unknown attribute webCmd. Type 'attr FanSelectorDay ?' for a detailed list. FanSelectorDay: unknown attribute devStateIcon. Type 'attr FanSelectorDay ?' for a detailed list.

The attr's are instantaneously removed from config.

What am I doing wrong here?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Juni 2014, 15:38:13
please post your Config. it should work

markus
via iphone
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 22 Juni 2014, 19:39:50
This is my config:



attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global verbose 3

# define telnetPort telnet 7072 global

define WEB FHEMWEB 8083 global
attr WEB hiddenroom DashboardRoom

define WEBphone FHEMWEB 8084 global
attr WEBphone hiddenroom DashboardRoom
attr WEBphone stylesheetPrefix smallscreen

define WEBtablet FHEMWEB 8085 global
attr WEBtablet hiddenroom DashboardRoom
attr WEBtablet stylesheetPrefix touchpad

# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog

define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log

define eventTypes eventTypes ./log/eventTypes.txt

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create

# #########################################################################
# THZ 404 Sol Waermepumpe
# #########################################################################
define Mythz THZ /dev/ttyUSB0@57600

# interval Defintionen
attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 120

# userReadings
attr Mythz userReadings AussenTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[1]}, VorlaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[3]}, RuecklaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[5]}, WWTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[9]}, KollektorTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[79]}

# Definition von file-log und den SVG-Plots einiger Daten
define FileLog_Mythz FileLog ./log/Mythz-%Y-%m.log Mythz
define wal_0 SVG FileLog_Mythz:thz:CURRENT
attr wal_0 room Heizung
define wal_1 SVG FileLog_Mythz:thz1:CURRENT
attr wal_1 room Heizung
define wal_2 SVG FileLog_Mythz:thz2:CURRENT
attr wal_2 room Heizung
define wal_3 SVG FileLog_Mythz:thz3:CURRENT
attr wal_3 room Heizung
define wal_4 SVG FileLog_Mythz:thz4:CURRENT
attr wal_4 room Heizung

# readingsGroup
define rg_thz readingsGroup Mythz:<%temp_outside>,<Aussen>,AussenTemp Mythz:<%sani_supply_temp@red>,<Vorlauf>,VorlaufTemp Mythz:<%sani_return_temp@blue>,<Rücklauf>,RuecklaufTemp Mythz:<%sani_boiler_temp@BD7800>,<Wasser>,WWTemp Mythz:<%sani_solar_temp>,<Kollektor>,KollektorTemp
attr rg_thz alias Heizung Temperaturen
attr rg_thz group THZ
attr rg_thz room Sysintern
attr rg_thz valueFormat { AussenTemp => '%1.f °C', VorlaufTemp => '%1.f °C', AussenTemp=> '%1.f °C', RuecklaufTemp=> '%1.f °C', WWTemp=> '%1.f °C', KollektorTemp=> '%1.f °C' }

# Dashboard
define MyDashboard Dashboard
attr MyDashboard dashboard_row top-center
attr MyDashboard dashboard_showtooglebuttons 0
attr MyDashboard dashboard_tab1groups THZ
attr MyDashboard dashboard_tab1name micofhem
attr MyDashboard dashboard_tab1sorting t0c100,THZ,true,170,253
attr MyDashboard dashboard_tabcount 1
attr MyDashboard dashboard_webfrontendfilter WEB
define MyDashboard_weblink weblink htmlCode {DashboardAsHtml("MyDashboard")}
attr MyDashboard_weblink room DashboardRoom

# FanSelector für die Lueftungssteuerung
define FanSelectorDay dummy
attr FanSelectorDay group THZ
attr FanSelectorDay setList 0 1 2 3 offFor60min
attr FanSelectorDay webCmd 0:1:2:3:offFor60min
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageDay notify FanSelectorDay IF ([FanSelectorDay] eq "offFor60min") (define at_D_offFor60min at +00:59:00 set Mythz p07FanStageDay [Mythz:p07FanStageDay],set Mythz p07FanStageDay 0, setstate FanSelectorDay offFor60min) ELSE (set Mythz p07FanStageDay $EVENT)
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1
attr FanSelectorDay room heatpump
define FanSelectorNight dummy
attr FanSelectorNight group THZ
attr FanSelectorNight setList 0 1 2 3 offFor60min
attr FanSelectorNight webCmd 0:1:2:3:offFor60min
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p08FanStageNight notify FanSelectorNight IF ([FanSelectorNight] eq "offFor60min") (define at_N_offFor60min at +00:59:00 set Mythz p08FanStageNight [Mythz:p08FanStageNight],set Mythz p08FanStageNight 0, setstate FanSelectorNight offFor60min) ELSE (set Mythz p08FanStageNight $EVENT)
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1
attr FanSelectorNight room heatpump
attr FanSelectorDay webCmd 0:1:2:3:offFor60min
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
# #########################################################################


Somehow after multiple "shutdown restart" it displays the icon but the error when saving the config stays the same.

Frank
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Juni 2014, 20:31:25
okay, that all looks quite normal.

please enter "list FanSelectorDay" and "list FanSelectorNight" in the command line of fhem and post the output.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 22 Juni 2014, 21:58:21

Internals:
   NAME       FanSelectorDay
   NR         48
   STATE      0
   TYPE       dummy
   Readings:
     2014-06-22 15:07:07   state           0
Attributes:
   group      THZ
   room       heatpump
   setList    0 1 2 3 offFor60min


Internals:
   NAME       FanSelectorNight
   NR         51
   STATE      1
   TYPE       dummy
Attributes:
   group      THZ
   room       heatpump
   setList    0 1 2 3 offFor60min
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Juni 2014, 22:16:22
Zitat von: maximalz am 22 Juni 2014, 19:39:50
This is my config:


attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global verbose 3

# define telnetPort telnet 7072 global

define WEB FHEMWEB 8083 global
attr WEB hiddenroom DashboardRoom

define WEBphone FHEMWEB 8084 global
attr WEBphone hiddenroom DashboardRoom
attr WEBphone stylesheetPrefix smallscreen

define WEBtablet FHEMWEB 8085 global
attr WEBtablet hiddenroom DashboardRoom
attr WEBtablet stylesheetPrefix touchpad

# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog

define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log

define eventTypes eventTypes ./log/eventTypes.txt

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create

# #########################################################################
# THZ 404 Sol Waermepumpe
# #########################################################################
define Mythz THZ /dev/ttyUSB0@57600

# interval Defintionen
attr Mythz interval_sGlobal 300
attr Mythz interval_sHistory 28800
attr Mythz interval_sLast10errors 120

# userReadings
attr Mythz userReadings AussenTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[1]}, VorlaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[3]}, RuecklaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[5]}, WWTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[9]}, KollektorTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[79]}

# Definition von file-log und den SVG-Plots einiger Daten
define FileLog_Mythz FileLog ./log/Mythz-%Y-%m.log Mythz
define wal_0 SVG FileLog_Mythz:thz:CURRENT
attr wal_0 room Heizung
define wal_1 SVG FileLog_Mythz:thz1:CURRENT
attr wal_1 room Heizung
define wal_2 SVG FileLog_Mythz:thz2:CURRENT
attr wal_2 room Heizung
define wal_3 SVG FileLog_Mythz:thz3:CURRENT
attr wal_3 room Heizung
define wal_4 SVG FileLog_Mythz:thz4:CURRENT
attr wal_4 room Heizung

# readingsGroup
define rg_thz readingsGroup Mythz:<%temp_outside>,<Aussen>,AussenTemp Mythz:<%sani_supply_temp@red>,<Vorlauf>,VorlaufTemp Mythz:<%sani_return_temp@blue>,<Rücklauf>,RuecklaufTemp Mythz:<%sani_boiler_temp@BD7800>,<Wasser>,WWTemp Mythz:<%sani_solar_temp>,<Kollektor>,KollektorTemp
attr rg_thz alias Heizung Temperaturen
attr rg_thz group THZ
attr rg_thz room Sysintern
attr rg_thz valueFormat { AussenTemp => '%1.f °C', VorlaufTemp => '%1.f °C', AussenTemp=> '%1.f °C', RuecklaufTemp=> '%1.f °C', WWTemp=> '%1.f °C', KollektorTemp=> '%1.f °C' }

# Dashboard
define MyDashboard Dashboard
attr MyDashboard dashboard_row top-center
attr MyDashboard dashboard_showtooglebuttons 0
attr MyDashboard dashboard_tab1groups THZ
attr MyDashboard dashboard_tab1name micofhem
attr MyDashboard dashboard_tab1sorting t0c100,THZ,true,170,253
attr MyDashboard dashboard_tabcount 1
attr MyDashboard dashboard_webfrontendfilter WEB
define MyDashboard_weblink weblink htmlCode {DashboardAsHtml("MyDashboard")}
attr MyDashboard_weblink room DashboardRoom

# FanSelector für die Lueftungssteuerung
define FanSelectorDay dummy
attr FanSelectorDay group THZ
attr FanSelectorDay setList 0 1 2 3 offFor60min
attr FanSelectorDay webCmd 0:1:2:3:offFor60min
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p07FanStageDay notify FanSelectorDay IF ([FanSelectorDay] eq "offFor60min") (define at_D_offFor60min at +00:59:00 set Mythz p07FanStageDay [Mythz:p07FanStageDay],set Mythz p07FanStageDay 0, setstate FanSelectorDay offFor60min) ELSE (set Mythz p07FanStageDay $EVENT)
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1
attr FanSelectorDay room heatpump
define FanSelectorNight dummy
attr FanSelectorNight group THZ
attr FanSelectorNight setList 0 1 2 3 offFor60min
attr FanSelectorNight webCmd 0:1:2:3:offFor60min
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
define Notify_p08FanStageNight notify FanSelectorNight IF ([FanSelectorNight] eq "offFor60min") (define at_N_offFor60min at +00:59:00 set Mythz p08FanStageNight [Mythz:p08FanStageNight],set Mythz p08FanStageNight 0, setstate FanSelectorNight offFor60min) ELSE (set Mythz p08FanStageNight $EVENT)
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1
attr FanSelectorNight room heatpump
attr FanSelectorDay webCmd 0:1:2:3:offFor60min
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3
# #########################################################################


Somehow after multiple "shutdown restart" it displays the icon but the error when saving the config stays the same.

Frank

Hi Frank

avoid automatic stuff, unless you have a new device to be configures
--> comment out autocreate.

try to clean up
--> you have 2 times: attr FanSelectorDay webCmd  //and/// attr FanSelectorDay devStateIcon

immi



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 Juni 2014, 10:06:51
Zitat von: immi am 22 Juni 2014, 22:16:22
try to clean up
--> you have 2 times: attr FanSelectorDay webCmd  //and/// attr FanSelectorDay devStateIcon

oh shame on me, how can i have overlooked that... :o
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 23 Juni 2014, 21:02:58
Thank you! I did not notice the double specification of the two attributes. Now the warning is gone.
Another question: Is there a better forum to discuss THZ-specific questions (not FHEM-related)? Because as I can see there are a lot of people around here who know much better how to set the parameters of the THZ than me.

Frank
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 Juni 2014, 21:05:55
you could try haustechnikdialog.de but in my eyes, the settings must fit to your house and needs. there is not a really "best" default setting.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 23 Juni 2014, 21:13:19
That's clear, but in this case it's some basic understanding what and why.
For example, although I'm usin warm-water mode (don't know the english word) my floor heating circulation pump is switched on many times the day.
But thanks for the hint, I'll try haustechnikdialog.de.

Frank
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 23 Juni 2014, 21:21:30
you could also try to call the stiebel eltron / tecalor support.
they are very helpful in my eyes :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Biting am 23 Juni 2014, 23:03:13
Hi,
is there a possibiltity to configure the energy consumption of the heating?
I want to detect the energy I currently have as overproduction by my PV system.  Assumed it is 500W I would like to allow the heating to use 500W to heat up the water. In case I do not have an overproduction of PV energy I want to stop the heating up to a defined Minimum. In case the Minimum water temperature is reached I would allow to use energy I have to buy to keep the Minimum.
Thank you
Biting
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Juni 2014, 23:05:23
haustechnikdialog.de is really a good choice - more qualified answers than e.g. bauexpertenforum.de, which seems to be an accumulation of sarcastic oriented faultfinders. But as in every forum even  haustechnikdialog.de isn't free of such...
If you have a specific question you can send me a PN. I have a bit of experience with some of the parameters and made good progress in reducing my heating costs during last winter seasons.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Juni 2014, 23:14:02
Zitat von: maximalz am 23 Juni 2014, 21:13:19
That's clear, but in this case it's some basic understanding what and why.
For example, although I'm usin warm-water mode (don't know the english word) my floor heating circulation pump is switched on many times the day.
But thanks for the hint, I'll try haustechnikdialog.de.

Frank
For this issue you should take care about Both should be just a bit higher than For more details about these parameters please have a look into the installation manual before asking more questions.

Values depend on isolation quality (Heizlast) of your house and some more parameters. My values (wooden house, big, southern oriented windows, Heizlast of approx. 6kW) areAs you can see in the attachment the pump is mainly switched off, just during a few night hours is goes to high frequency in order to check the stone floor temperature for possibly heating it up. You can even reduce the number of pump cycles by reducing
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Juni 2014, 23:21:06
Zitat von: Biting am 23 Juni 2014, 23:03:13
Hi,
is there a possibiltity to configure the energy consumption of the heating?
I want to detect the energy I currently have as overproduction by my PV system.  Assumed it is 500W I would like to allow the heating to use 500W to heat up the water. In case I do not have an overproduction of PV energy I want to stop the heating up to a defined Minimum. In case the Minimum water temperature is reached I would allow to use energy I have to buy to keep the Minimum.
Thank you
Biting
You can of course modify the set values of DHW ("Brauchwasser"), in order to force heating or to avoid heating. You can do so e.g. based on programmed perl logic, based on whatever parameters you can imagine. To do so you need of course additionally a possibility to check your PV energy creation via fhem.
But you should have in mind that this bears the risk of getting totally lost, e.g. if your fhem server stops working for any reason, and short before it set the DHW value to e.g. "cold". You'll need to have a cold shower the next morning  ;)

And of course this can only work if you can use your PV energy for feeding the heatpump. In my case I have separate electricity meters for heating and household. Just one of them can be fed by the PV energy.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 Juni 2014, 01:16:25
Zitat von: willybauss am 23 Juni 2014, 23:14:02

Values depend on isolation quality (Heizlast) of your house and some more parameters. My values (wooden house, big, southern oriented windows, Heizlast of approx. 6kW) are

       
  • p49SummerModeTemp 11.5 °C
  • p56OutTempMaxPumpCycles -- °C
  • p57OutTempMinPumpCycles --°
As you can see in the attachment the pump is mainly switched off, just during a few night hours is goes to high frequency in order to check the stone floor temperature for possibly heating it up. You can even reduce the number of pump cycles by reducing

HI Willy
why have you p56>p57?
In the manual, it is for me clear that p56<p57.... look at the ranges and the default values.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Juni 2014, 08:10:47
You're right, that's a bug. I'll exchange them. But I'll use the THZ display to do so, since I'm not confident in fhem to change values correctly. Do you have any update on this topic?
Looks like a bug in the 00_THZ module. In the display the values are correct, the fhem readings are reversed. Could you check please?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 Juni 2014, 09:12:16
Zitat von: willybauss am 24 Juni 2014, 08:10:47
You're right, that's a bug. I'll exchange them. But I'll use the THZ display to do so, since I'm not confident in fhem to change values correctly. Do you have any update on this topic?
Looks like a bug in the 00_THZ module. In the display the values are correct, the fhem readings are reversed. Could you check please?
please explain better:
1) do you agree that p56 should be lower than p57?
2) you expect that I exchanged the registers names in FHEM, Don´t you? I can only check tomorrow.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Juni 2014, 11:28:11
Zitat von: immi am 24 Juni 2014, 09:12:16
1) do you agree that p56 should be lower than p57?
I agree. What I observed is:

fhem readings are:manual readings from THZ display showSo the fhem readings are mixed up compared to real THZ settings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Biting am 24 Juni 2014, 18:47:38
Hi,
thanks for the info. Getting the actual energy overproduction is necessary, of course. In my case it will be allowed to connect the PV to the heating. Anyway just Setting the temperature does not completely fulfill my requirement. I want to use only the energy I have and not more. I do not know if the heating uses 1kw to increase the temperature for 1hour or 500w for 2 hours to get to a certain value. I just want to set "please heat up and only use 500W as Long as the Maximum temperature is reached". Therefor turning off the heating by Setting an already reached temperature is clear but turning it on to only set a Maximum energy consumption is my demand. The idea is to use every single watt of energy overproduction to heat up the water without buying energy.
Biting
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Juni 2014, 21:42:06
Zitat von: Biting am 24 Juni 2014, 18:47:38
... I just want to set "please heat up and only use 500W ...
That can't work using a heat pump. The compressor needs a defined amount of power which is approx. 1.5kW. So you can decide to use it or not, thus taking 1.5kW or nothing.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 Juni 2014, 12:11:12
Willy is absolutely right in this. Only if your PV is able to provide a steady current that equals 1500 W, you could do this but setting this as a threshold, and then you you provide this energy to the compressor and do whatever you want. If you want to use subthreshold energy there is only the fan for air circulation. But even at the highest level this is less than 90 W and if it is really hot outside you want the air circulation off anyway. All you're left with is a battery buffer solution which in my mind will never make economically  any sense, unless a kWh cost you 50 cents.

The combination heat pump and PV as in the current settings are not made in heaven! ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 Juni 2014, 20:07:46
v 0.107 uploaded, tomorrow, you can update
p56 and p57 exchanged and fixed


willy please fix
« Antwort #739 am: 23 Juni 2014, 23:14:02 »
we do not want that someone copies the exchanged values

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 Juni 2014, 21:26:52
done


btw: did you have time to look into this issue?:
Zitat von: willybauss am 10 Juni 2014, 21:31:21
... we're changing values, yes. But with a different result than changing them via the panel. ...

@immi:
I meanwhile can confirm that my assumption regarding to the 2nd issue (see my posting of today 14:06:51) is right. Changing timing settings of fan programs is possible, the result of these changes is visible on the THZ display, BUT the changed settings are never activated. Fan speed doesn't change at all, no matter if I try to define a day or night mode using any one of the time definitions. The only way I found to activate the changed settings is, to open the setting in the THZ display and change it again. Just opening and confirming the existing settings doesn't work; it definitely needs to be changed again using the THZ display.

That's exactly the same behavior I already reported months ago for the pXXUnschedVentY settings and for party-time. I strongly believe it's the same for all DHW, HC1, HC2 and holiday timing settings.

Summarizing these results I have to say that approx. 130 set parameters are not in working condition.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 Juni 2014, 10:50:41
I noticed a possibly dangerous default setting of THZ. As soon as you activate the vacation mode the THZ will operate in standby mode for the defined vacation duration, thus it will use the standby temperatures as expected values. BUT the default value of standby inside temp (P03) is 10°C. So if you plan for a vacation in winter time you might come back from vacation and notice that all your plants are dead, your cat found another place to live, etc.

I suggest you to change all P03 related settings to e.g. 18...20°C. These are at least

p03RoomTempStandbyHC1
p03RoomTempStandbyHC1SummerMode
p03RoomTempStandbyHC2
p03RoomTempStandbyHC2SummerMode

Currently it might or might not be useful to change the values via fhem. Reason can be found in my post directly above this one.

Via THZ display you might be unable to change the winter mode ones (1st and 3rd row) currently; you might need to bring THZ into winter mode first.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Juni 2014, 18:50:57
Zitat von: willybauss am 10 Juni 2014, 21:31:21
I meanwhile can confirm that my assumption regarding to the 2nd issue (see my posting of today 14:06:51) is right. Changing timing settings of fan programs is possible, the result of these changes is visible on the THZ display, BUT the changed settings are never activated. Fan speed doesn't change at all, no matter if I try to define a day or night mode using any one of the time definitions. The only way I found to activate the changed settings is, to open the setting in the THZ display and change it again. Just opening and confirming the existing settings doesn't work; it definitely needs to be changed again using the THZ display.
That's exactly the same behavior I already reported months ago for the pXXUnschedVentY settings and for party-time. I strongly believe it's the same for all DHW, HC1, HC2 and holiday timing settings.
Hi Willy
pXXUnschedVentY and the programschedule are completely different.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Juni 2014, 12:56:04
Zitat von: immi am 27 Juni 2014, 18:50:57

       
  • Your activation hypothesis is not correct for holiday, which for me is working well from fhem.
Maybe; as I wrote: I didn't test it since the program_xxx topic was not yet clear/fixed


Zitat von: immi am 27 Juni 2014, 18:50:57

       
  • Your activation hypothesis is not correct for program_sigleday, which for me is working well from fhem.
works on my side as well - as you wrote: just for single day settings


Zitat von: immi am 27 Juni 2014, 18:50:57

       
  • I did not test completely program_group_of_days, which is still not clear for me; my hypothesis was here.
    http://forum.fhem.de/index.php/topic,13132.msg176385.html#msg176385 (http://forum.fhem.de/index.php/topic,13132.msg176385.html#msg176385)
Can't confirm that it's not clear. The answer is here:
http://forum.fhem.de/index.php/topic,13132.msg176569.html#msg176569

Additional tests today confirmed this answer:Therefore the fix is quite easy: Changing values of a group_of_days setting via fhem has to be translated into additionally changing the related single day settings in the communication btw. fhem and THZ.

Example:
fhem user interface: has to be translated into fhem communication to THZ:Based on the (already confirmed) "last entry wins" hypotheses there's no plausibility check needed at all.

So I'd like you to either change it in this way or alternatively remove the group_of_day settings completely from the user interface, since they're not working in current state.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Juni 2014, 13:51:33
 again I observed lots of argMax =>  "23:59"

inside the code of thzversion 0.107, while I expected them to be replace by
argMax =>  "24:00"

already, see here (1st issue):
http://forum.fhem.de/index.php/topic,13132.msg175611.html#msg175611 (http://forum.fhem.de/index.php/topic,13132.msg175611.html#msg175611)

currently trying to set an interval until 24:00 ends up in

ZitatArgument does not match the allowed inerval Min 00:00 ...... Max 23:59
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Juni 2014, 15:19:58
HI
I will see what can be done for grouping the days

for Min 00:00 ...... Max 23:59, there was a reason, I did it intentionally,   in an older version was 24:00, but I do not remember. ops  getting old
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Juni 2014, 16:41:48
with Max 23:59 it's impossible to define a nightly range of e.g. 22:00--06:00. Is has to be split into 22:00--23:45 and 00:00--06:00, thus having an interrupt btw. 23:45 and 24:00.
THZ manual explicitely describes to set it as 22:00-24:00 plus 00:00-06:00 in order to get a complete range without interrupt.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Juni 2014, 19:27:05
willy
i do not discuss if we need it or not.
I do not remember why I changed it.
I will put it back in the next release.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Juni 2014, 13:51:06
v0108
-major change in setting, taking care of group fo days.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Juni 2014, 17:01:23
which Setting? :)
sorry i dont understand all of this massive textings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Juni 2014, 18:24:22
simply read second half of my

Antwort #752 am: 28 Juni 2014, 12:56:04

That should answer your question.


@immi:  thanks a lot  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Juni 2014, 08:24:17
Zitat von: immi am 29 Juni 2014, 13:51:06
v0108
-major change in setting, taking care of group fo days.

immi
1st testing shows that it works - thanks again
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Juni 2014, 09:31:18
Dear all
Markus is taking care of the wiki in an excellent way.
I am a little slower with the command ref.
http://fhem.de/commandref.html#THZ
Command-ref should provide a short summary of how to use the module (like man in unix).
Expecially to the newcomers, could you please suggest what are you missing? what should be deleted?
Just take the actual text (in german or in engl.) and post the differences
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 Juni 2014, 10:55:32
Same to me. If you need any more information just let me know. Will update the Wiki with it.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Juni 2014, 13:39:32
@ immi:
in ver 0.108 I do no more see "party-time" in the list of set parameters, but just in the get parameter list. Has this been done intentionally?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Juni 2014, 13:51:20
yes
partytime has never worked. I cannot set the value.
partytime can be read; therefore it is a get-parameter untill someone tells me how to set it.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Juli 2014, 10:13:08
wiki updated
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Juli 2014, 10:46:04
Hi Markus, Dear all
in the wiki there is still a hint on the connect-disconnect problem.
I do not see it anymore, so much has been done to fix it.
Actually my system is running so stable that I do not need to periodically restart.
I would like a short feedback on stability and on possible strange events that you find in logfile.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 Juli 2014, 10:53:16
I still see it frequently in the logs and I do not use the serial but the straight forward USB connection. Could this be a voltage issue of the THZ circuit board that the powering has small hickups and goes below 5 V for a second or so?

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Juli 2014, 10:57:32
i saw it until i updated today to 0.180. will keep you informed if 0.180 fixed it for me.
yesterday i've had some disconnect entrys.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 02 Juli 2014, 15:08:31
I saw it just once: yesterday - 1 day after having updated to 0.108.
Couldn't find it in log file of whole June. But I don't use ser2net, I use a USB2RS232 adapter instead.

I do also not see any further THZ related strange messages in any logs.

I check fhem's status (and restart fhem if necessary) on hourly base via a cronjob plus shell script. I avoid intentionally to do so inside fhem, since this automatism should fix issues like crashed or hanging processes. Therefore it doesn't make sense to execute the healing process inside the crashed one ... Works perfect so far. As soon as I manage to kill fhem from remote I have to wait maximum an hour until it works again.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Juli 2014, 17:57:36
Dear all
when you update, you have to restart FHEM ASAP.

Dear Tom
in a direct connection to the heatpump, everything could happen.
EMC (EMV in german) is a very bad beast.
Maybe can you correlate the hour of the event and a booster or compressor activation...
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 03 Juli 2014, 07:57:56
I am able to graphically display when the disappear occurs.
Problems: I have no idea what is measured. And whether it is correlative or causative.
But the overlay is striking and I believe that everybody else can test it.
Measure is called: mythz.*    then select column 4 , plotstyle lines. These lines are pretty regular and line up somehow with daily wrg energy. However, exactly when disappear occurs, this parameter shoots over the wrg line.

If this is too little, tell me what else is needed. I will post details later tonight. I am in a hurry.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 Juli 2014, 09:33:52
Zitat von: houseowner123 am 03 Juli 2014, 07:57:56
I am able to graphically display when the disappear occurs.
Problems: I have no idea what is measured. And whether it is correlative or causative.
But the overlay is striking and I believe that everybody else can test it.
Measure is called: mythz.*    then select column 4 , plotstyle lines. These lines are pretty regular and line up somehow with daily wrg energy. However, exactly when disappear occurs, this parameter shoots over the wrg line.

If this is too little, tell me what else is needed. I will post details later tonight. I am in a hurry.

Tom

Try to behave like a Geologist o a big-data-expert, for whom a correletion is enough to prove a deterministic demonstration :)
joke at a side
pay attention with what you see: mythz.* colum 4 will give you several parameters in one plot.
you have to better filter out... I suggested to filter  compressor on or booster on... but could be something else .. e.g. a valve which is switching.
I cannot reproduce your test because my fhem is running 10 meters away: it is connected with a long serial cable and I forward it with ser2net.
I do not have a connect-disconnet from more than 50 days.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Juli 2014, 17:58:17
just found:
2014.07.03 03:50:35 1: 192.168.178.50:2003 disconnected, waiting to reappear (Mythz)
2014.07.03 03:50:35 1: 192.168.178.50:2003 reappeared (Mythz)
2014.07.03 03:50:36 1: 192.168.178.50:2003 disconnected, waiting to reappear (Mythz)
2014.07.03 03:50:36 1: 192.168.178.50:2003 reappeared (Mythz)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 03 Juli 2014, 23:39:04
Hi Immi,

I did what you suggested and looked deeper into correlating events. I can find three categories. The disconnect is associated with
1. turning off the heat pump after WW activity (account for 60%)
2. return of power (my energy supplier turns the power off for 2 hours every day) (account for 30%)
3. nothing I can find. (account for 10%)

I conclude from this that it is an electrical or better shielding problem. Whenever the power turns off or on it may induce a small current in the USB cable/connector which makes FHEM believe the connection is lost. This also would explain that connection is almost immediately restored.

I am still fascinated that I graphically display this all, I just have no idea what it is. However the disappearing events look to me like a strange current. I still want to say that the occurrence i still random and not coupled to anything. I had 17 events in June; 2 already in July.

Here are some screen shots, each representing the above mentioned events in that order.

1) (http://img5.fotos-hochladen.net/uploads/heatpumpendspje1w8vtb.jpg) (http://www.fotos-hochladen.net)


2) (http://img5.fotos-hochladen.net/uploads/generalpowero8idbznutow.jpg) (http://www.fotos-hochladen.net)


3) (http://img5.fotos-hochladen.net/uploads/unrelateda7trb3cwpy.jpg) (http://www.fotos-hochladen.net)

I'd be happy if someone could tell me what the green mythz.* parameter is that is so nice an regular.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Juli 2014, 08:53:14
did you ever try to use a different power outlet for your fhem server's power supply, being far away from the heatpump? You might need to use a extension cable to try this.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 Juli 2014, 10:04:27
mine is placed upon the heatpump but i also tried to move around the power supply. didn't work.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 04 Juli 2014, 10:10:15
I can confirm this. The power lines are completely separate but of course in the same room. EDIT: Sorry for the big images, I make them smaller next time.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Juli 2014, 13:13:45
I'd like you to share the code for the diagrams. Some of them look interresting.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 Juli 2014, 13:22:50
why using code for the diagrams? you can choos the values of the diagrams in the plot-gui. thats easier.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Juli 2014, 14:07:52
Zitat von: micomat am 04 Juli 2014, 13:22:50
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Juli 2014, 14:49:43
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Juli 2014, 14:57:18
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 Juli 2014, 15:46:38
i use a 3000mA power supply. so thats Not the Problem ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Juli 2014, 15:51:39
Zitat von: micomat am 04 Juli 2014, 15:46:38
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 05 Juli 2014, 01:29:21
@willy: Here is the code for the plot:

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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Juli 2014, 01:46:04
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 05 Juli 2014, 11:27:12
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Juli 2014, 15:34:24
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Juli 2014, 22:39:52
dear all
I am using the statistics module frome some days.


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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 Juli 2014, 22:49:29
will try it :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Juli 2014, 23:58:44
don't understand why some initial values directly after having started the statistics are unequal to zero:
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Juli 2014, 00:02:54
Zitat von: willybauss am 07 Juli 2014, 23:58:44
don't understand why some initial values directly after having started the statistics are unequal to zero:
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 Juli 2014, 10:55:59
quite different here:
min/max/avg stats are working. deltaReadings not as expected?

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


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Juli 2014, 13:08:44
Zitat von: micomat am 09 Juli 2014, 10:55:59
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 Juli 2014, 13:20:15
i thought i could see the hour-stats already...
but i will wait :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Juli 2014, 14:36:03
Hi Markus
I am still not sure of "statistics" behavior, but i find the module interesting.
It has lots of potential, expecially for the people who do not go in database direction.
It strongly depends on

1) how often you have an update of the parameter.
e.g. You probably read sGlobal every 5 minutes and  sBoostDHWTotal every 24h.

2) how often the parameter changes in the heatpump.
e.g. sBoostDHWTotal will change only when you take a shower;
e.g. SElectrDHWTotal will change only in winter when you take a bath.

of course an hourly statistics for SElectrDHWTotal makes no sense.
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 09 Juli 2014, 14:51:52
thankt for that information. will keep an eye on it :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 10 Juli 2014, 15:04:37
@willy: room temp sensor is now in its final place. :) I used two unused wires from a 5-pol cable that ended in the kitchen/living room area. Sensor comes sideways out of a wall socket. Works fine. Looking forward to colder days to test the room influence parameter. With your stone walls you should have a greater temperature buffer once heating is off. If anyone else who reads this have an external room sensor in place or plans to have one, please speak up and share your experience.

@ immi: what does not work is the heat curve calculation in wl_hr. It does not take account the correction of the inside temp. Instead it takes the sGlobal value which is uncorrected. If possible for you, look for that paramter (room temp correction HC1) in the code somewhere? It is not a Pxx in the manual unfortunately. Alternatively, is it possible to inform the thz module about the room temp correction, such that the heat curve is correctly displayed/calculated?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Juli 2014, 13:43:43
Zitat von: belu am 10 Juni 2014, 13:43:11
I have the phone today with some people from Stiebel Eltron order to get the parameter.
Did not get canceled, I should an email letter, this will then be reviewed and submitted to the Executive Board.
We enter halt into direct competition with the ISG Web.
So let's wait and see.
A direct access to the open source community does not form a heater manufacturers. I am thinking here of the market could be larger. Better at the end of heaters sold more than a few ISG Web.

Does anyone know about current state of this topic?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Juli 2014, 13:46:28
Belu has not contacted me about it. Looking at the IGS Web and how they market it...I find it unlikely that SE will be open to this idea.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Juli 2014, 14:00:49
Zitat von: houseowner123 am 10 Juli 2014, 15:04:37
@willy: room temp sensor is now in its final place. :) I used two unused wires from a 5-pol cable that ended in the kitchen/living room area. Sensor comes sideways out of a wall socket. Works fine. Looking forward to colder days to test the room influence parameter. With your stone walls you should have a greater temperature buffer once heating is off. If anyone else who reads this have an external room sensor in place or plans to have one, please speak up and share your experience.
small misunderstanding: I don' have stone walls at all, but a wooden house ("Holzständerbauweise"). But what I have is a massive heated stone floor (Fußbodenheizung), having more than 30 tons of heating storage capacity. That's much more than the usual 600 liter water buffer.

Zitat von: houseowner123 am 10 Juli 2014, 15:04:37
@ immi: what does not work is the heat curve calculation in wl_hr. It does not take account the correction of the inside temp. Instead it takes the sGlobal value which is uncorrected. If possible for you, look for that paramter (room temp correction HC1) in the code somewhere? It is not a Pxx in the manual unfortunately. Alternatively, is it possible to inform the thz module about the room temp correction, such that the heat curve is correctly displayed/calculated?

Thanks,
Tom
In my case I don't have this issue, the red dot is always exactly on the heating curve. But my setup is a bit different: I have the inside temp sensor just for visualisation of the value (part of sGlobal). The inside temp value for heating curve calculation is inside the external display, which I have additionally (connected to THZ via CAN bus). And this display has it's own offset value entry, so I assume the value to be corrected before it's being sent to the THZ.

In my case the drawback is, that the offset calculation for the sGlobal value doesn't work any more. Therefore I have to correct it by

attr Mythz userReadings dhw_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[9])}, Rel_humidity:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[67]) + 11.5}, flow_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[3])}, return_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[5])}, inside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[81]) - 0.6 }, outside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[1])}
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 21 Juli 2014, 15:39:30
Hi there,

I have asked but so far no response. I think there is nothing more to come.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Juli 2014, 21:55:44
belu,
do not stop asking,
do not work alone: more people, like Tom wanted to fight with you.

in parallel I would suggest we keep on working
which parameter are you missing?
maybe we find them out the old way.

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 26 Juli 2014, 16:44:15
Hi,

we have in the THZ the paramter for the Electrical Energy used yesterday for Heating and DWH.

But regarding the airfans ther is only a Parameter for the actual value, nothing for the consumption in total from the day before, correct?

Is it possible via the statistics module to define the yesterdays consumption? ( for main+input+output fan)

Thanks for ketting me know how to do it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mvb am 26 Juli 2014, 18:43:56
Hallo,

ich komm nicht weiter: Folgende Aufgabe:
Ziel: Raumlüftung soll aus sein, wenn Aussentemp > 22°C und wieder an, wenn < 20°C (z.B.)

Hardware: Fritzbox 7390 mit FHEM aus AVM-Labor,
FHEM: update am 24.7.14 durchgeführt
Stiebel Eltron LWZ 303 SOL, FW 4.19 über delock usb2serial - RS232 angebunden: Werte auslesen funktioniert perfekt. Plots anzeigen auch. Toll!!!

Code aus fhem.cfg: (um Lüftung zu steuern)
define AussenTemp dummy
setreading AussenTemp {(split ' ',ReadingsVal("LWZ","sGlobal",0))[1]}
define Lueftung THRESHOLD AussenTemp:2:22 |set LWZ p07FanStageDay 0|set LWZ p07FanStageDay 1|0
set Lueftung external



Fehlermeldung FHEM bei save config:
"Lueftung: no target_sensor defined"

Was mache ich falsch bzw. wie löse ich das Problem?

Danke
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Juli 2014, 21:07:54
Zitat von: Heiner am 26 Juli 2014, 16:44:15
Hi,
we have in the THZ the paramter for the Electrical Energy used yesterday for Heating and DWH.
But regarding the airfans ther is only a Parameter for the actual value, nothing for the consumption in total from the day before, correct?
Is it possible via the statistics module to define the yesterdays consumption? ( for main+input+output fan)
Thanks for ketting me know how to do it.

HI Heiner
we have no value of main+input+output fan consumption.
We have rotation speed and something linked to the given power.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Juli 2014, 21:26:06
Zitat von: mvb am 26 Juli 2014, 18:43:56
Hallo,
ich komm nicht weiter: Folgende Aufgabe:
Ziel: Raumlüftung soll aus sein, wenn Aussentemp > 22°C und wieder an, wenn < 20°C (z.B.)

Hardware: Fritzbox 7390 mit FHEM aus AVM-Labor,
FHEM: update am 24.7.14 durchgeführt
Stiebel Eltron LWZ 303 SOL, FW 4.19 über delock usb2serial - RS232 angebunden: Werte auslesen funktioniert perfekt. Plots anzeigen auch. Toll!!!

Code aus fhem.cfg: (um Lüftung zu steuern)
define AussenTemp dummy
setreading AussenTemp {(split ' ',ReadingsVal("LWZ","sGlobal",0))[1]}
define Lueftung THRESHOLD AussenTemp:2:22 |set LWZ p07FanStageDay 0|set LWZ p07FanStageDay 1|0
set Lueftung external


Fehlermeldung FHEM bei save config:
"Lueftung: no target_sensor defined"
Was mache ich falsch bzw. wie löse ich das Problem?
Danke

Hi mvb
happy that you got fhem working.
one question is "set LWZ p07FanStageDay 0" working for you?

I am not really familiar with THRESHOLD.
I would write something like this (not tested) without the dummy device.


attr LWZ userReadings AussenTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[1]}, VorlaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[3]}, RuecklaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[5]}, WWTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[9]}

define Lueftung THRESHOLD LWZ:AussenTemp:2:22 |set LWZ p07FanStageDay 0|set LWZ p07FanStageDay 1|0


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mvb am 27 Juli 2014, 11:28:35
Hi immi,

thanks for your answer. Now I tested:

attr LWZ userReadings AussenTemp {(split ' ',ReadingsVal("LWZ","sGlobal",0))[1]}
define Lueftung THRESHOLD LWZ:AussenTemp:2:22 |set LWZ p07FanStageDay 0|set LWZ p07FanStageDay 1|0
attr Lueftung number_format %.1f
attr Lueftung state_format _m _dv

And it is working! Great!
You excuse me that I left the other temperature readings as they are hopefully not needed for this control task.
The problem was the "set Lueftung external". Once deleted it worked. But then I don't understand the Commandref for THRESHOLD: "Set: .... Set the desired value. If no desired value is set, the module is not active. "

What I dislike now is that AussenTemp is updated every second. I was looking for a solution with less "RS232-traffic".

"set LWZ p07FanStageDay 0" is obviously working as I copied the THZ-code example for the manual setting of the ventilation level into my fhem.cfg, tested it and checked the setting directly at the LWZ.

Thanks, Bye, Martin
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Juli 2014, 14:02:10
right Martin
I just tested it. "External" makes only sense if you want to use a variable (or a reading) for storing the desired temperature.
For you it is fixed, therefore it makes no sense.

I think I will also use this vent control but maybe with desired temp at 28°C, not 22
It could also be interesting in winter during the night to stop the vent if temperature is below -10°C.

I think you can skip the following in your definition, I get it automagically
attr Lueftung number_format %.1f
attr Lueftung state_format _m _dv

immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: maximalz am 27 Juli 2014, 20:05:17
Hi Martin,
this is a very useful application imho. Did you manage it to get the AussenTemp queried less often?

Frank
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Juli 2014, 21:57:36
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

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mvb am 28 Juli 2014, 20:05:08
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Juli 2014, 20:18:54
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 31 Juli 2014, 13:41:16
...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?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 31 Juli 2014, 14:18:24
yep, it's called the perpetuum-mobile ;D

same here, awesome work, awesome function. i love it!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 August 2014, 11:12:16
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Floru am 01 August 2014, 15:20:09
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 August 2014, 20:04:14
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

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 August 2014, 07:09:02
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 August 2014, 09:11:45
Mine is for Heating:
9033/2353 =3.83

for DHW
1090/353 = 3.09
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 August 2014, 09:12:42
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 August 2014, 09:19:17
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 02 August 2014, 09:42:28
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.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 03 August 2014, 19:25:05
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
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 August 2014, 21:24:00
hi
which Version of 00_thz.pm do you use?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 03 August 2014, 22:09:02
Hi

i am using version: 0.108

Since the last post i have hundreds of new errors. i found some more:

2014.08.03 22:01:08 2: LWZ403/RAW: 000000000000001003
Use of uninitialized value $message in concatenation (.) or string at ./FHEM/00_THZ.pm line 1052.
Use of uninitialized value $length in concatenation (.) or string at ./FHEM/00_THZ.pm line 1054.
Use of uninitialized value $message in substr at ./FHEM/00_THZ.pm line 1055.
substr outside of string at ./FHEM/00_THZ.pm line 1055.
Use of uninitialized value $parsingcmd in pattern match (m//) at ./FHEM/00_THZ.pm line 1056.
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 1062.
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 last logfile (07.14) has no entrys about this. the new one (08.14) start directly with all these errors...

maybe this helps for investigation

thx

kai
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 August 2014, 23:36:35
What's always ignored  in such calculations (even for heating systems based on oil or gas) is the energy used for waterpump, electronic control unit, fans for ventilation etc. They cannot be taken into account easily, since these circuits are not giong through the heatpump's electricity meter but through the 'normal' household electricity meter. The heatpump's values ( sHeatHCTotal, sElectrHCTotal, ...) don't cover is as well. Knowing about this topic I installed separate meters for these circuits (see for L1 and L2 in the installation manual). I'll post my values with and without them:

sHeatHCTotal 22568 kWh / sElectrHCTotal 6113 kWh = 3.69

incl. L1+L2:  sHeatHCTotal 22568 kWh / (sElectrHCTotal 6113 kWh + 1008 kWh +357 kWh) = 3.02 

sHeatDHWTotal 6025 kWh / sElectrDHWTotal 2119 kWh = 2.84
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 August 2014, 00:41:52
Hi firebal301
it is several weeks, that I do not change the code (v0.108)

2014.08.03 22:01:08 2: LWZ403/RAW: 000000000000001003
.

Are you using a serial cable (no usb direct) like me willy and Floru?
I prepared for Floru a small improvement (candidate v0.109), for which I got no feedback.
If you are using serial cable, give me a PM, you can also test it.


Hi Tom
I agree I oversimplified the "performance" index..... fortunatelly my boss ( my wife) is not digging in this KPI :)

Hi Willy
It is amazing how much current the heatpump getting  through the normal household  meter
in your case 1.36MWh wuaoh
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 August 2014, 08:28:41
Zitat von: immi am 04 August 2014, 00:41:52
It is amazing how much current the heatpump getting  through the normal household  meter
in your case 1.36MWh wuaoh
immi
Exactly. And as soon as we try to take the heat recovery of ventilation system into account we also need to take the electric energy used for it into account.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Floru am 04 August 2014, 08:40:59
Hi immi,

many thanks for this test release. This solution seems to work fine also. I tested it for about 20 hours and got no error messages and regular readings every 5 minutes.
With v0.108 befor I had error s like described from firebal301 about every 20-30 minutes. I will have a look to the error log for the next days and will post, if I see any communication error.

by the way, my performance values:
for HC: 6428/2008 = 3.20
for DHW: 4987/1763 = 2.83

Florian
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 04 August 2014, 09:38:06
gad to read :)
i sometimes saw such errors in different modules also some times.
in most cases a restart of the raspi solved the problem.

best,
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 August 2014, 15:18:26
I have 2 minutes: I Try to explain you where the error comes.
2014.08.03 22:01:08 2: LWZ403/RAW: 000000000000001003

In several FHEM module you have 2 function to read the interface: in my case:

The first takes care of reading a messages during a conversation (polling -You ask someting, the heatpump answer, you ask somethingelse..).

The second reads messages, without a conversation. Just in case the heatpump sends something without a precise request.
This second case should never happen with the THZ.
But. If a peace of the message in the first case comes too late .... the last part of the message remains in the serial interface... and sub THZ_Read is activated causing a warning or an error.

The old solution (ca v. <0.104) was to wait a lot before reading. This is unefficient, because in 90% of the case, the wait time is useless.
Each long message ends with 1003; The elegant solution is to repeat the first case untill 1003 comes.


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 04 August 2014, 17:34:18
Hi immi

thanks for the explanation. You are right. I Am using the serial cable at the front connector.

i am only suprised, that this error happend exactly at 00:00:00 month-change...  :o

i will test your 'beta' v.0.109. PM comes seperately :-)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 05 August 2014, 15:40:57
after 24 hours of testing v.109 no error appears. great work immi thanks  8)

other question:

how often you can overwrite the flash in the heatpump. i am not sure that the control is designed for register-changing several times a day.

maybe this will effect the flash in 10 years or later; maybe in one... :(

does anyone know how often you can overwrite such memory ?

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 August 2014, 17:16:42
depends on the part type, from few thousands till some 10 thousand times. If one can remove the board from his THZ and tell me the exact part name I can dig deeper  ;) .

But you're right: changing the values frequently, possibly multiple times per day, may wear out the memory parts earlier as expected.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 August 2014, 21:10:54
uploaded v.0109
changeloge: bug fix for long messages in combination with serial cable connection


Considering the reliability, I really hope tecalor used some kind of smart memory management.
Over 10..15 years, also without stress like rewriting the memory, data retention is a lottery.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: lwzler am 06 August 2014, 21:40:06
@Topic HC Temp > Room Temp in summer

Well what made me wondering was the fact, that even in colder periods, when we had outsidetemps between 8 to 17°C in a week in June, the HC temp never fell below ~24°C (with no heating activity). But

Zitat von: willybauss am 01 August 2014, 11:12:16
As long as the heating circle pump is switched off (what's the case for almost 100% of the time in summer mode)

that's for sure ok, if the heatcircle pump doesn't work at all. I had something in mind, that the heatcircle pump works at least x times a day or so.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 August 2014, 23:07:22
Zitat von: lwzler am 06 August 2014, 21:40:06
that's for sure ok, if the heatcircle pump doesn't work at all. I had something in mind, that the heatcircle pump works at least x times a day or so.

just plot it,
find an example of the gplot below

# Created by FHEM/98_SVG.pm, 2014-04-25 01:10:11
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 '<TL>'
set ytics
set y2tics
set grid
set ylabel ""
set y2label ""
set yrange [0:1]
set y2range [0:2]

#FileLog 35:Mythz.sGlobal\x3a:0:
#FileLog 37:Mythz.sGlobal\x3a:0:
#FileLog 39:Mythz.sGlobal\x3a:0:
#FileLog 41:Mythz.sGlobal\x3a:0:
#FileLog 31:Mythz.sGlobal\x3a:0:
#FileLog 19:Mythz.sHC1\x3a::$fld[18]=~"summer"?0:1

plot "<IN>" using 1:2 axes x1y1 title 'Compressor' ls l1fill lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage3' ls l0 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage2' ls l4 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage1' ls l3 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'HeatingCircuit_Pump' ls l5 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'winterMode' ls l2fill lw 0.5 with lines
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 07 August 2014, 05:24:53
Zitat von: immi am 05 August 2014, 21:10:54
uploaded v.0109

updated wiki

best regards from China :)

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 August 2014, 08:10:21
I set my pump cycles toAnd I'm pretty sure that the measured HC temp is influenced by the DHW container which is located close to the flow temp sensor inside the THZ. That might be the reason why the flow temp and return temp show bumps as soon as the pump starts, see attached screen dump between 4 and 8 o'clock, when it switched to winter mode due to low outside temp. As soon as the pump works the sensor sees the 'real' flow/return temp inside the stone floor. When the pump is switched off the temps are manipulated by waste heat of other components inside the THZ. And just that is the reason why the THZ needs the pump to be  switched on frequently, in order to know about the 'real' temperatures => decide if heating is necessary or not.

btw: the gplot files of both graphics had been added to one of my posts approx. 6 ... 8 weeks ago.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 August 2014, 17:46:13
Zitat von: willybauss am 07 August 2014, 08:10:21
I set my pump cycles to

       
  • p54MinPumpCycles = 1 ==> once per day in summer mode
  • p55MaxPumpCycles = 48 ==> once every 30 minutes in winter mode
And I'm

I know that you know it Willy
but just to be sure that the point is clear for everyone.
Pumpcycle is not related to summer and wintermode which are determined by "p49SummerModeTemp" "p50SummerModeHysteresis"   

Pumpcycle is  related to"p54MinPumpCycles" "p55MaxPumpCycles" "p56OutTempMaxPumpCycles" "p57OutTempMinPumpCycles"

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 August 2014, 12:40:39
Exactly. As you can see in my plots:The additional heating pump activity at 9:00 am has nothing to do with this topic. It's just caused by heating up DHW. I assume at end of this task the unnecessary heat has to be brought out of the THZ (in order to cool the system down) by moving the hot water into the stone floor (just a very limited volume, thus not realy heating up rooms).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 28 August 2014, 13:20:49
slightly off topic: smart homes do not pay off...except for smart metering your heating installation. Just some food for though if someone calls you crazy:
http://www.heise.de/newsticker/meldung/Smart-Homes-sparen-zu-wenig-2303371.html?wt_mc=sm.feed.tw.ho
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Lutz123 am 22 September 2014, 19:23:46
Hallo Forum,

die Frage nach der außerplanmässigen Lüftung bzw. "unscheduled ventilation" ist schon gestellt worden,  ich wollte es mal so probieren:
(Firmware 3.39)
Die Anfrage "F6" an die THZ liefert neben einem unbekannten Wert die ausserplanmäßige Lüftungsstufe sowie dafür einen Countdown in Minuten.
Eine einfache Umwandlung der Antwort in einen Schreibbefehl, indem ich "80" einsetze und den CRC anpasse, funktioniert nicht.
Ich habe keinen "Sniffer", der das Protokoll abfangen könnte.
Meine Frage: Kann ich von "F6" Rückschlüsse auf Adressen bekommen, mit denen ein Schreibbefehl erfolgreich ist?

Danke von Lutz.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 September 2014, 19:47:38
as our main Developer is Not German You may ask this also in englisch.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 September 2014, 08:24:41
Der Versuch, die Werte über die serielle Schnittstelle an dieselbe Adresse zu schreiben, aus der sie auch gelesen werden, schlug bereits fehl, sh. etliche Seiten weiter vorne in diesem Forenthema. Die Adresse solltest Du aus dem Sourcecode des THZ- Moduls bekommen.

Man wird wohl das CAN-Bus-Protokoll abhören müssen.  Die Vermutung ist aktuell, dass beim Setzen der außerplanmäßigen Lüftung übers Display auch gleich ein Flag zur Aktivierung gesetzt wird. Dieses Flag  (oder was immer der Auslöser sein mag)  ist noch nicht gefunden.

Gruß
Willy

PS:
Immi spricht auch durchaus deutsch, auch wenn englisch für ihn bequemer ist. Aber halt nur für ihn  ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 September 2014, 15:50:57
Hi Lutz123
as far as I know, F6 is a status register, which among otherts, includes "unscheduled ventilation" information.
I understood only 50% of  both "unscheduled ventilation" and "party time".
The 2 parameters need a double action, some kind of activation.
Your idea to hack f6 was not bad, but if you cannot write F6, it means, it is read-only.

I agree with Willy: Man wird wohl das CAN-Bus-Protokoll abhören müssen.
I can live very well without these features, because the buttons in fhem can mimic them quite well; look at the end of the wiki.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Lutz123 am 24 September 2014, 10:41:12
Hello Forum,

Thanks for answering,
my thz is connected to a BeagleBlackBone using the serial interface.
If the winter will becomes long, dark and cold, I could connect it the other way, because my BBB can CAN ... HAhahuhaha.... Sorry, only a joke. It makes me thinking of Suzi Quatro's "can the can" ... Hahah ... Sorry again, only another joke.
If I'm successful in sniffing "F6" I will post my results here. --->

Greetings from Lutz, NSA novice.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 29 September 2014, 18:36:29
Hallo zusammen,


Ich habe fhem auf einem Ubuntu Host (13.10) installiert, modpath mit '/opt/fhem' gefüttert und fhem mit 'update' aktualisiert. Unter '/opt/fhem/FHEM' finde ich nun auch '00_THZ.pm'. Wenn ich es aber mit 'reload 00_THZ' neu laden will, kommt folgende Fehlermeldung (auch im Log):


reload: Error:Modul 00_THZ deactivated:
Global symbol "%intAt" requires explicit package name at /opt/fhem//FHEM/00_THZ.pm line 1247.
Global symbol "%intAt" requires explicit package name at /opt/fhem//FHEM/00_THZ.pm line 1248.
Global symbol "%intAt" requires explicit package name at /opt/fhem//FHEM/00_THZ.pm line 1248.



Was mache ich falsch? Die o.g. Zeilennummern in der pm-Datei helfen mir nicht wirklich weiter. Werden auskommentierte Zeilennummern bei Fehlermeldungen mitgezählt oder nicht? Wie finde ich die betroffenen Zeilen am besten, ohne besondere Klimmzüge machen zu müssen. Danke für Eure Hilfe.


Viele Grüße,
kabelsurfer
___________
Tecalor THZ 303 SOL @Linksys NSLU2 @ser2net @Ubuntu 13.10 64-bit Host w/ fhem-5.5.deb
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 September 2014, 19:05:14
shutdown restart schon versucht?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 29 September 2014, 22:40:17
Vom Host?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 September 2014, 06:46:21
von fhem :)
sorry, einfach oben in der eingabezeile "shutdown restart" eingeben.
vielleicht hast du einfach zu viel upgedated und nachgeladen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 September 2014, 21:00:12
hi kabelsurfer
as Marcus suggested
1) make a complete update of fhem --> update
2) restart --> shutdown restart
3) check  all  modules version --> version

if problem persists, provide complete logfiles and configfiles

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 30 September 2014, 23:01:16
Thanks to both of you! That is what I did, and now it works, i.e. I can define my THZ.  :)  For the curious, here is the message with the versions:


# $Id: fhem.pl 6623 2014-09-26 17:55:17Z rudolfkoenig $
# $Id: 01_FHEMWEB.pm 6611 2014-09-24 07:48:32Z rudolfkoenig $
# $Id: 92_FileLog.pm 6571 2014-09-19 16:05:56Z rudolfkoenig $
# $Id: 99_SUNRISE_EL.pm 5851 2014-05-13 19:39:03Z rudolfkoenig $
# $Id: 99_Utils.pm 6574 2014-09-19 17:32:48Z rudolfkoenig $
# $Id: 98_autocreate.pm 6505 2014-09-06 12:24:48Z rudolfkoenig $
# $Id: 91_eventTypes.pm 6428 2014-08-20 11:51:27Z rudolfkoenig $
# $Id: 91_notify.pm 6371 2014-08-07 05:33:37Z rudolfkoenig $
# $Id: 98_telnet.pm 6611 2014-09-24 07:48:32Z rudolfkoenig $


Why are only these shown? Is it only the FHEMWEB plus the modules starting with IDs of 9 that are displayed with 'version'? Anyway, now my journey continues...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 01 Oktober 2014, 06:17:54
maybe you've configured a wrong verbose level in your config?
but anyway, if it's working now, have fun :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Oktober 2014, 08:10:50
Zitat von: kabelsurfer am 30 September 2014, 23:01:16


# $Id: fhem.pl 6623 2014-09-26 17:55:17Z rudolfkoenig $
# $Id: 01_FHEMWEB.pm 6611 2014-09-24 07:48:32Z rudolfkoenig $
# $Id: 92_FileLog.pm 6571 2014-09-19 16:05:56Z rudolfkoenig $
# $Id: 99_SUNRISE_EL.pm 5851 2014-05-13 19:39:03Z rudolfkoenig $
# $Id: 99_Utils.pm 6574 2014-09-19 17:32:48Z rudolfkoenig $
# $Id: 98_autocreate.pm 6505 2014-09-06 12:24:48Z rudolfkoenig $
# $Id: 91_eventTypes.pm 6428 2014-08-20 11:51:27Z rudolfkoenig $
# $Id: 91_notify.pm 6371 2014-08-07 05:33:37Z rudolfkoenig $
# $Id: 98_telnet.pm 6611 2014-09-24 07:48:32Z rudolfkoenig $


Why are only these shown? Is it only the FHEMWEB plus the modules starting with IDs of 9 that are displayed with 'version'?

"version" command should list all currently loaded modules:
havn't you said that you have defined thz?
something like this is missing
# $Id: 00_THZ.pm 6363 2014-08-05 19:03:32Z immiimmi $

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 01 Oktober 2014, 10:14:39
Immi,

i just updated my fhem and now i see a strange error message in the log while starting:


2014.10.01 10:13:09 3: Mythz device opened
False [] range "\w-" in regex; marked by <-- HERE in m/^(\s*([\w- <-- HERE \.]+)(:\S*)?\s+((\w+)\s+)?({.*?})\s*)(,\s*(.*))*$/ at fhem.pl line 2240, <$fh> line 129.
2014.10.01 10:13:10 3: Opening FritzBox device 192.168.178.1:1012


not sure if it's a problem of Mythz module? Anyway everything is working fine :)

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Oktober 2014, 21:42:00
Markus
Same problem. but do not know if connected with THZ.

root cause is a fix from Rudolf in usrreadings in order to allow points.......
http://forum.fhem.de/index.php/topic,27442.0.html
https://github.com/mhop/fhem-mirror/commit/1e2f6bf54160be8a78f6c6c63383696f72e6c333

untill 03.10 I cannot play around
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 01 Oktober 2014, 21:50:03
dont hurry. seems Not to be critical :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 08:08:55
Zitat von: immi am 01 Oktober 2014, 08:10:50
"version" command should list all currently loaded modules:
havn't you said that you have defined thz?
something like this is missing
# $Id: 00_THZ.pm 6363 2014-08-05 19:03:32Z immiimmi $

immi
Yes, good point, but I do not know why there are only so view entries. Any hints are welcome.

My THZ (from 2008) has the software/firmware version 2.16. Does anybody know how I can make the fhem THZ module work for this old version? I am willing to contribute to testing, i.e. reading values etc.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Oktober 2014, 09:01:01
i guess it will work once it's working ;)

try the following:
update force
update 00_THZ.pm
shutdown restart

list Mythz (or however you defined the name of your THZ)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 17:41:23

Thanks, I have done all that. After the 'shutdown restart' I got this despite that I had defined Mythz (define Mythz THZ 192.168.178.3:2020) already:
Error messages while initializing FHEM:
statefile: Please define Mythz first



Since the above message appears every time after 'shutdown restart', I assume that I need to define Mythz every time after that, right?


After defining it (anew), 'list Mythz' gives me this output:

Internals:
   CFGFN
   DEF        192.168.178.3:2020
   DeviceName 192.168.178.3:2020
   FD         13
   NAME       Mythz
   NR         31
   PARTIAL
   STATE      opened
   TYPE       THZ
   VERSION    0.109
Attributes:


Should 'Attributes' above show something? As you see, it does not.

The IP is the one of my NSLU2 (a small and old NAS from Linksys) to which I have connected the THZ 303 SOL via 2 wires and RS232-USB adapter and ser2net (2020:telnet:600:/dev/ttyUSB0:9600 8DATABITS NONE 1STOPBIT) - proven to be working outside fhem.


Still, 'version' does only show the stuff I quoted above, i.e. no 00_THZ.pm among them.


The Log says that there is something wrong with my connection:

2014.10.02 17:25:30 0: Server shutdown
2014.10.02 17:25:30 1: Including fhem.cfg
2014.10.02 17:25:30 3: telnetPort: port 7072 opened
2014.10.02 17:25:30 3: WEB: port 8083 opened
2014.10.02 17:25:30 3: WEBphone: port 8084 opened
2014.10.02 17:25:30 3: WEBtablet: port 8085 opened
2014.10.02 17:25:30 2: eventTypes: loaded 2 events from ./log/eventTypes.txt
2014.10.02 17:25:30 1: Including ./log/fhem.save
2014.10.02 17:25:30 1: statefile: Please define Mythz first
2014.10.02 17:25:30 1: usb create starting
2014.10.02 17:25:31 1: usb create end
2014.10.02 17:25:31 2: Error messages while initializing FHEM: statefile: Please define Mythz first
2014.10.02 17:25:31 0: Server started with 9 defined entities (version $Id: fhem.pl 6633 2014-09-29 20:05:48Z rudolfkoenig $, os linux, user fhem, pid 9335)
2014.10.02 17:25:32 1: Including fhem.cfg
2014.10.02 17:25:32 1: telnetPort: Can't open server port at 7072: Address already in use. Exiting.
2014.10.02 17:37:06 3: Opening Mythz device 192.168.178.3:2020
2014.10.02 17:37:06 3: Mythz device opened
2014.10.02 17:37:06 2: Mythz/RAW: FFFB03FFFB01FFFE01FFFD00
2014.10.02 17:37:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.02 17:37:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
...


Since the baudrate is already set to only 9600 in ser2net.conf, I guess that there is not a speed but some other problem.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Oktober 2014, 18:10:13
2014.10.02 17:37:06 2: Mythz/RAW: FFFB03FFFB01FFFE01FFFD00
2014.10.02 17:37:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

This is a typical timeout problem, Which can be due to the 9k/s or to a command which you old firmware does not understand.

let us start with some homework:
1) each time you modify something: stop fhem, modify start fhem

2) deactivate the autorefresh
comment out line 413 of thz
# $replyc = THZ_Get($hash, $hash->{NAME}, $command);

3) verbose to max in config file -- > 
attr global verbose 5

4) ask for firmwareversion
get Mythz sFirmware

5) post complete config file and log

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 18:20:56
Zitat von: immi am 02 Oktober 2014, 18:10:13
1) each time you modify something: stop fhem, modify start fhem

I assume that with "stop fhem" you mean 'shutdown' and with "start fhem" you mean 'restart'?

Zitat von: immi am 02 Oktober 2014, 18:10:13
2) deactivate the autorefresh
comment out line 413 of thz
# $replyc = THZ_Get($hash, $hash->{NAME}, $command);

I have done that.

Zitat von: immi am 02 Oktober 2014, 18:10:13
3) verbose to max in config file -- > 
attr global verbose 5

I have done that as well.

Zitat von: immi am 02 Oktober 2014, 18:10:13
4) ask for firmwareversion
get Mythz sFirmware

However, I cannot do 'get Mythz sFirmware' without again defining Mythz, which gets lost everytime I do a shutdown/restart. Is this normal?
A 'msg2 InterfaceNotRespondig' gives me this:
msg2 InterfaceNotRespondig




Zitat von: immi am 02 Oktober 2014, 18:10:13
5) post complete config file and log

Config and log are attached.


Edit:
Hm, I now realise that fhem.cfg shows a verbose mode of 3, despite I had set it to 5. Very strange... I now submitted another 'attr global verbose 5' with [enter], but when I check fhem.cfg via the menu (Edit files > config file > fhem.cfg) it again shows a verbosity level of 3, i.e. in one line 'attr global verbose 3'. So does manually entering 'attr global verbose 5' not get reflected in fhem.cfg? Am I missing a point here? -- Well, at least it stays 5 via the menu method, i.e. then clicking on "Save fhem.cfg". Since my USB adaptor does not change, I commented out the line 'define initialUsbCheck notify global:INITIALIZED usb create' in fhem.cfg. I have replaced the previously attached fhem.cfg and also fhem.log with the updated ones, i.e. verbosity now set to 5. When trying to get the FW version, the Log shows 'Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead'. I will recheck my cable tomorrow...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Oktober 2014, 20:10:03
for stopping fhem "shutdown" command is fine
for starting fhem you start it from command line: perl fhem.pl fhem.cfg

edit the config when fhem is not running

in your config file you have to define Mythz otherwise how can fhem know about it?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Oktober 2014, 20:13:46
by the way... some versions needs to be configured to 115200 or 57600 baud to work.
not sure if yours is one of that.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 20:18:18

Thanks to both of you. Most likely you have not yet seen my edit and updated cfg und log above?


When I do just 'shutdown', how comes that the web GUI of fhem is still available without issuing 'perl fhem.pl fhem.cfg'? (thanks for the hint to start it like that, I was not aware of it)


I had entered 'define Mythz THZ 192.168.178.3:2020' in the command field and had hit [enter] which does not seem to work for a permanent save. Sorry that I was under this wrong impression. I will also try increasing the baudrate, first to 19200.


Here is my again update fhem.cfg:

attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath /opt/fhem/
attr global motd none
attr global room Unsorted
attr global sendStatistics manually
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global userattr devStateIcon devStateStyle icon sortby webCmd
attr global verbose 5


define telnetPort telnet 7072 global


define WEB FHEMWEB 8083 global


define WEBphone FHEMWEB 8084 global
attr WEBphone stylesheetPrefix smallscreen


define WEBtablet FHEMWEB 8085 global
attr WEBtablet stylesheetPrefix touchpad


# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog


define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log


define eventTypes eventTypes ./log/eventTypes.txt


# Disable this to avoid looking for new USB devices on startup
#define initialUsbCheck notify global:INITIALIZED usb create


define Mythz THZ 192.168.178.3:2020
attr Mythz interval_sGlobal 300 # Internes Polling Intervall 5min
attr Mythz interval_sHistory 28800 # Internes Polling Intervall 8h
attr Mythz interval_sLast10errors 120 # Internes Polling Fehlerspeicher
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Oktober 2014, 20:23:50
could you please provide information about how the heating is connected to your computer. is it a raspberry? is it connected via USB-Serial-Converter or do you use a second computer via ser2net?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 20:30:14
The IP 192.168.178.3 in Mythz is the IP of my NSLU2 (a small and old NAS from Linksys) to which I have connected the THZ 303 SOL via 2 wires and RS232-USB adapter (pl2303 or ftdi - cannot remember right now) and ser2net (2020:telnet:600:/dev/ttyUSB0:9600 8DATABITS NONE 1STOPBIT) - proven to be working outside fhem with 9600 baud. As I wrote above, I will recheck my cable and also try increasing the baud rate to 19200 and higher - tomorrow, though, so please bear with me. My THZ (from 2008, i.e. before the "iPod" wheel was introduced) has a software (or you call it firmware) version 2.16, i.e. it is pretty "old". Thanks for your great help!

Edit: Fhem runs on a PC with Ubuntu 13.10 64bit.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Oktober 2014, 20:48:49
okay, all of that looks okay.
the 2.16 is definitively supported as robert penz also could connect with the heatpumpmonitor python program.
i found this information here: https://answers.launchpad.net/heatpumpmonitor/+question/160527
so stay tuned ;) never give up, we'll get it running sooner or later.

if you're a little bit firm with linux, you could try heatpumpmonitor or a serial communicator like hterm (windows) to test if there is a general comm way to the heating.
don't worry, as far as i know, you cannot break it with these tests.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Oktober 2014, 21:07:22
Zitat von: kabelsurfer am 02 Oktober 2014, 20:18:18
Thanks to both of you. Most likely you have not yet seen my edit and updated cfg und log above?


When I do just 'shutdown', how comes that the web GUI of fhem is still available without issuing 'perl fhem.pl fhem.cfg'? (thanks for the hint to start it like that, I was not aware of it)


I had entered 'define Mythz THZ 192.168.178.3:2020' in the command field and had hit [enter] which does not seem to work for a permanent save. Sorry that I was under this wrong impression. I will also try increasing the baudrate, first to 19200.


Here is my again update fhem.cfg:

attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath /opt/fhem/
attr global motd none
attr global room Unsorted
attr global sendStatistics manually
attr global statefile ./log/fhem.save
attr global updateInBackground 1
attr global userattr devStateIcon devStateStyle icon sortby webCmd
attr global verbose 5


define telnetPort telnet 7072 global


define WEB FHEMWEB 8083 global


define WEBphone FHEMWEB 8084 global
attr WEBphone stylesheetPrefix smallscreen


define WEBtablet FHEMWEB 8085 global
attr WEBtablet stylesheetPrefix touchpad


# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log fakelog


define autocreate autocreate
attr autocreate filelog ./log/%NAME-%Y.log


define eventTypes eventTypes ./log/eventTypes.txt


# Disable this to avoid looking for new USB devices on startup
#define initialUsbCheck notify global:INITIALIZED usb create


define Mythz THZ 192.168.178.3:2020
attr Mythz interval_sGlobal 300 # Internes Polling Intervall 5min
attr Mythz interval_sHistory 28800 # Internes Polling Intervall 8h
attr Mythz interval_sLast10errors 120 # Internes Polling Fehlerspeicher
define FileLog_Mythz FileLog ./log/Mythz-%Y.log Mythz

Hi kabelsurfer
I do not like to hear that you have gui available after shutdown. You have to kill fhem, modify fhem.cfg, start it.
There are lots of manuals on google how to kill a process or to check it (ps -ef)

Stay with the 9600baud/s if you already tested it with other software. Old firmware could require it.

In your config remove all intervalls and autocreate: you do not need them now.

1) start fhem
2) get Mythz sFirmware
if you do not get the right answer post the logfile.
if you get 2.16 first milestone is set

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: kabelsurfer am 02 Oktober 2014, 22:39:52
Zitat von: micomat am 02 Oktober 2014, 20:48:49
the 2.16 is definitively supported as robert penz also could connect with the heatpumpmonitor python program.
Yes, I know. I am running heatpumpmonitor on my NSLU2, but want to migrate to fhem. ;)  As written above, fhem currently sits on an Ubuntu host, but the plan is to have it on my Synology DS214se. But testing fhem on the NSLU2 via ser2net to Ubuntu is currently easier.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 03 Oktober 2014, 08:00:39
okay, if the heatpumpmonitor works, the THZ module maybe just not knows how to talk to the 2.16 firmware ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Oktober 2014, 09:13:33
Zitat von: micomat am 01 Oktober 2014, 10:14:39
Immi,

i just updated my fhem and now i see a strange error message in the log while starting:


2014.10.01 10:13:09 3: Mythz device opened
False [] range "\w-" in regex; marked by <-- HERE in m/^(\s*([\w- <-- HERE \.]+)(:\S*)?\s+((\w+)\s+)?({.*?})\s*)(,\s*(.*))*$/ at fhem.pl line 2240, <$fh> line 129.
2014.10.01 10:13:10 3: Opening FritzBox device 192.168.178.1:1012



Hi Markus
FYI Rudolf fixed the bug in fhem.pl
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 05 Oktober 2014, 13:05:08
thanks immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 15 Oktober 2014, 01:12:04
Hello immi,
I migrated FHEM from Fritzbox 7270 to RaspberyyPI B+.
The LWZ303sol is connected via serial cable through FTDI serial/USB converter to the RaspberryPI (dev/ttyUSB1@57600)
FHEM is on the latest level incl 00_THZ 0.109.
On the Fritzbox I never had issues but to my surprise now with Raspberry I get tons of Perl warnings.
E.g. PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.

Unfortunately it seems the fix mentioned in this thread does not work in my specific scenario.
Is there something I can do to solve this?

Thanks and regards
xyz_fhem
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 15 Oktober 2014, 06:37:23
i also use raspi to connect. no issues. did you try "update force" on the raspi setup and then "shutdown restart"?

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Jakl am 15 Oktober 2014, 10:33:08
Hi everybody,

I try to build up a Dashboard which is structured like the menu in my LWZ 303. I've got everything in place what I want, except the "Istwerte".
Now I got the problem, that I'm not 100% sure, which value fits to which 'Istwert'. I've attached an excel file, with my 'Istwerte' and the values I think belong to them. Some are missing, maybe some are wrong. Maybe you can help me with this?

Thank you and best regards,
Jakl
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 15 Oktober 2014, 10:52:06
@micomat: Yes, I did an update force and shutdown restart and also a restart of the RPI.
But still tons of entries in the fhem log.

Any idea?

Thanks
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Oktober 2014, 14:14:15
Hi xyz_fhem
I also left freezbox last year: really too slow.
please post logfile.

It is usefull that you increase before the loglevel: set verbose to 5.
immi

Hi JAckal
excellent idea
share your code. People can test it and help you improve it much better than an xls file.

>>Now I got the problem, that I'm not 100% sure,..
nobody is really 100% sure; to my opinion, it is more importnant to describe the parameter, than to translate it.
Markus started in the wiki. But this is a huge amount of work.

p.s. you have the same parameter double e.g. sHC1_roomSetTemp
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 16 Oktober 2014, 22:04:14
@immi: The strange Thing first:
When I set verbose Level to 5 no Perl error happens.
When I set it back to Level 3 the following floods the log file:

only a small extract:
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $message in concatenation (.) or string at ./FHEM/00_THZ.pm line 1076.
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $length in concatenation (.) or string at ./FHEM/00_THZ.pm line 1078.
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $message in substr at ./FHEM/00_THZ.pm line 1079.
2014.10.16 21:43:57 1: PERL WARNING: substr outside of string at ./FHEM/00_THZ.pm line 1079.
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $parsingcmd in pattern match (m//) at ./FHEM/00_THZ.pm line 1080.
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:57 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1091.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 1: PERL WARNING: Use of uninitialized value $parsingcmd in string eq at ./FHEM/00_THZ.pm line 1086.
2014.10.16 21:43:58 2: LWZ/RAW: 0000000000000000000000000000000000001003


Any idea why that happens?

Thanks and regards
xyz_fhem
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Oktober 2014, 00:19:29
you have a serial cable; no direct usb connection?
if yes, your raspi is running too fast for your serial comunication; you go out of sync.

2014.10.16 21:43:58 2: LWZ/RAW: 0000000000000000000000000000000000001003

should be easy to fix. Tomorrow I will send you something.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 17 Oktober 2014, 00:31:16
yes, i started with the heatpumpmonitor and still use the same serial cable with mate-n-lok at one end and a sub-d9 at the other. The communciation gets converted via FTDI USB/serial converter. I thought about exchanging the serial cable with an USB-A-B cable, mainly due to faster communication, but ... just have not done it. Actually .... would it improve the Situation so dramatically?

Thanks and regards
xyz_fhem
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 Oktober 2014, 07:08:38
immi, i still have the problem, that sometimes the mythz module reports "opened" but there is no data collected.
so is it possible to count the number of errors in the logfile (mythz disappeared... or so) until the next data communication was established. so i could fetch this count and if it's higher then maybe 50 or so, i'll just restart the Pi connected to the heatpump?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Oktober 2014, 10:58:51
Hi xyz_fhem
do not change to direct USB connection.  I also stay with long serial cable.
I will fix your issue easily this evening, then you can test.
--
Direct USB connection suffers for the problem just described by Markus.
Root cause: not sure, we were speculating on EMC/EMV.

Hi Markus
until I have a better idea,  in unix combine "tail" + "grep"
Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 17 Oktober 2014, 16:02:15
hello,
I get the following error.
Can you help me?

Logfile:
2014.10.17 15:52:34 5: THZ_Get: Try to get 'pHolidayBeginMonth'
2014.10.17 15:52:34 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:34 5: Mythz sending 02
2014.10.17 15:52:34 5: SW: 02
2014.10.17 15:52:34 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:35 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:35 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:35 5: THZ_Get: Try to get 'pHolidayEndTime'
2014.10.17 15:52:35 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:35 5: Mythz sending 02
2014.10.17 15:52:35 5: SW: 02
2014.10.17 15:52:35 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:36 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:36 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:36 5: THZ_Get: Try to get 'programHC2_So_2'
2014.10.17 15:52:36 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:36 5: Mythz sending 02
2014.10.17 15:52:36 5: SW: 02
2014.10.17 15:52:36 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:37 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:37 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:37 5: THZ_Get: Try to get 'p01RoomTempDayHC1SummerMode'
2014.10.17 15:52:37 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:37 5: Mythz sending 02
2014.10.17 15:52:37 5: SW: 02
2014.10.17 15:52:37 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:38 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:38 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:38 5: THZ_Get: Try to get 'programDHW_Sa_1'
2014.10.17 15:52:38 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:38 5: Mythz sending 02
2014.10.17 15:52:38 5: SW: 02
2014.10.17 15:52:38 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:38 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:38 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:38 5: THZ_Get: Try to get 'programHC2_Sa-So_2'
2014.10.17 15:52:38 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:38 5: Mythz sending 02
2014.10.17 15:52:38 5: SW: 02
2014.10.17 15:52:38 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:39 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:39 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:39 5: THZ_Get: Try to get 'programHC2_Mo_1'
2014.10.17 15:52:39 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:39 5: Mythz sending 02
2014.10.17 15:52:39 5: SW: 02
2014.10.17 15:52:39 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:40 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:40 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:40 5: THZ_Get: Try to get 'p38Fanstage2AirflowInlet'
2014.10.17 15:52:40 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:40 5: Mythz sending 02
2014.10.17 15:52:40 5: SW: 02
2014.10.17 15:52:40 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:41 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:41 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:41 5: THZ_Get: Try to get 'programFan_Mo_1'
2014.10.17 15:52:41 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:41 5: Mythz sending 02
2014.10.17 15:52:41 5: SW: 02
2014.10.17 15:52:41 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:42 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:42 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:42 5: THZ_Get: Try to get 'p99FanStageParty'
2014.10.17 15:52:42 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:42 5: Mythz sending 02
2014.10.17 15:52:42 5: SW: 02
2014.10.17 15:52:42 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:42 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:42 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:42 4: HMLAN_ack: timeout - clear queue
2014.10.17 15:52:42 5: THZ_Get: Try to get 'pHolidayEndYear'
2014.10.17 15:52:42 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:42 5: Mythz sending 02
2014.10.17 15:52:42 5: SW: 02
2014.10.17 15:52:42 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:43 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:43 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:43 5: THZ_Get: Try to get 'programFan_We_0'
2014.10.17 15:52:43 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:43 5: Mythz sending 02
2014.10.17 15:52:43 5: SW: 02
2014.10.17 15:52:43 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:44 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:44 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:44 5: THZ_Get: Try to get 'p08FanStageNight'
2014.10.17 15:52:44 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:44 5: Mythz sending 02
2014.10.17 15:52:44 5: SW: 02
2014.10.17 15:52:44 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:45 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:45 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:45 5: THZ_Get: Try to get 'programDHW_So_2'
2014.10.17 15:52:45 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:45 5: Mythz sending 02
2014.10.17 15:52:45 5: SW: 02
2014.10.17 15:52:45 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:46 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:46 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:46 5: THZ_Get: Try to get 'programHC2_Fr_0'
2014.10.17 15:52:46 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:46 5: Mythz sending 02
2014.10.17 15:52:46 5: SW: 02
2014.10.17 15:52:46 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:46 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:46 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:46 5: THZ_Get: Try to get 'programHC2_Th_1'
2014.10.17 15:52:46 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:46 5: Mythz sending 02
2014.10.17 15:52:46 5: SW: 02
2014.10.17 15:52:46 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:47 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:47 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:47 5: THZ_Get: Try to get 'p16GradientHC2'
2014.10.17 15:52:47 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:47 5: Mythz sending 02
2014.10.17 15:52:47 5: SW: 02
2014.10.17 15:52:47 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:48 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:48 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:48 5: THZ_Get: Try to get 'programDHW_Th_2'
2014.10.17 15:52:48 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:48 5: Mythz sending 02
2014.10.17 15:52:48 5: SW: 02
2014.10.17 15:52:48 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:49 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:49 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:49 5: THZ_Get: Try to get 'programFan_Mo-Fr_1'
2014.10.17 15:52:49 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:49 5: Mythz sending 02
2014.10.17 15:52:49 5: SW: 02
2014.10.17 15:52:49 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:50 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:50 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:50 5: THZ_Get: Try to get 'p56OutTempMaxPumpCycles'
2014.10.17 15:52:50 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:50 5: Mythz sending 02
2014.10.17 15:52:50 5: SW: 02
2014.10.17 15:52:50 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:50 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:50 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:50 5: THZ_Get: Try to get 'p55MaxPumpCycles'
2014.10.17 15:52:50 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:50 5: Mythz sending 02
2014.10.17 15:52:50 5: SW: 02
2014.10.17 15:52:50 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:51 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:51 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:51 5: THZ_Get: Try to get 'programDHW_Fr_1'
2014.10.17 15:52:51 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:51 5: Mythz sending 02
2014.10.17 15:52:51 5: SW: 02
2014.10.17 15:52:51 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:52 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:52 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:52 5: THZ_Get: Try to get 'p18RoomInfluenceHC2'
2014.10.17 15:52:52 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:52 5: Mythz sending 02
2014.10.17 15:52:52 5: SW: 02
2014.10.17 15:52:52 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:53 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:53 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:53 5: THZ_Get: Try to get 'p02RoomTempNightHC1SummerMode'
2014.10.17 15:52:53 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:53 5: Mythz sending 02
2014.10.17 15:52:53 5: SW: 02
2014.10.17 15:52:53 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:54 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:54 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:54 5: THZ_Get: Try to get 'programDHW_Mo-So_0'
2014.10.17 15:52:54 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:54 5: Mythz sending 02
2014.10.17 15:52:54 5: SW: 02
2014.10.17 15:52:54 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:54 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:54 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:54 5: THZ_Get: Try to get 'programHC2_Mo-Fr_1'
2014.10.17 15:52:54 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:54 5: Mythz sending 02
2014.10.17 15:52:54 5: SW: 02
2014.10.17 15:52:54 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:55 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:55 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:55 5: THZ_Get: Try to get 'programDHW_We_0'
2014.10.17 15:52:55 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:55 5: Mythz sending 02
2014.10.17 15:52:55 5: SW: 02
2014.10.17 15:52:55 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:56 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:56 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:56 5: THZ_Get: Try to get 'sHeatRecoveredTotal'
2014.10.17 15:52:56 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:56 5: Mythz sending 02
2014.10.17 15:52:56 5: SW: 02
2014.10.17 15:52:56 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:57 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:57 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:57 5: THZ_Get: Try to get 'p03RoomTempStandbyHC1SummerMode'
2014.10.17 15:52:57 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:57 5: Mythz sending 02
2014.10.17 15:52:57 5: SW: 02
2014.10.17 15:52:57 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:58 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:58 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:58 5: THZ_Get: Try to get 'programHC1_Fr_0'
2014.10.17 15:52:58 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:58 5: Mythz sending 02
2014.10.17 15:52:58 5: SW: 02
2014.10.17 15:52:58 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:59 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:59 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:59 5: THZ_Get: Try to get 'programHC1_Fr_2'
2014.10.17 15:52:59 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:59 5: Mythz sending 02
2014.10.17 15:52:59 5: SW: 02
2014.10.17 15:52:59 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:52:59 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:52:59 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:52:59 5: THZ_Get: Try to get 'p01RoomTempDayHC2SummerMode'
2014.10.17 15:52:59 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:52:59 5: Mythz sending 02
2014.10.17 15:52:59 5: SW: 02
2014.10.17 15:52:59 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:00 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:00 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:00 5: THZ_Get: Try to get 'sHC1'
2014.10.17 15:53:00 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:00 5: Mythz sending 02
2014.10.17 15:53:00 5: SW: 02
2014.10.17 15:53:00 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:01 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:01 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:01 5: THZ_Get: Try to get 'p05DHWsetNightTemp'
2014.10.17 15:53:01 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:01 5: Mythz sending 02
2014.10.17 15:53:01 5: SW: 02
2014.10.17 15:53:01 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:02 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:02 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:02 5: THZ_Get: Try to get 'pHolidayEndMonth'
2014.10.17 15:53:02 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:02 5: Mythz sending 02
2014.10.17 15:53:02 5: SW: 02
2014.10.17 15:53:02 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:03 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:03 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:03 5: THZ_Get: Try to get 'programHC2_Mo-Fr_2'
2014.10.17 15:53:03 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:03 5: Mythz sending 02
2014.10.17 15:53:03 5: SW: 02
2014.10.17 15:53:03 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:03 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:03 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:03 5: HMLAN_Send:  HMLAN1 I:K
2014.10.17 15:53:03 5: THZ_Get: Try to get 'p02RoomTempNightHC2SummerMode'
2014.10.17 15:53:03 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:03 5: Mythz sending 02
2014.10.17 15:53:03 5: SW: 02
2014.10.17 15:53:03 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:04 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:04 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:04 5: THZ_Get: Try to get 'pHolidayEndDay'
2014.10.17 15:53:04 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:04 5: Mythz sending 02
2014.10.17 15:53:04 5: SW: 02
2014.10.17 15:53:04 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:05 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:05 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:05 5: THZ_Get: Try to get 'pHolidayBeginDay'
2014.10.17 15:53:05 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:05 5: Mythz sending 02
2014.10.17 15:53:05 5: SW: 02
2014.10.17 15:53:05 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:06 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:06 5: THZ_Get: Try to get 'p40Fanstage1AirflowOutlet'
2014.10.17 15:53:06 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:06 5: Mythz sending 02
2014.10.17 15:53:06 5: SW: 02
2014.10.17 15:53:06 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:07 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:07 5: THZ_Get: Try to get 'programFan_We_1'
2014.10.17 15:53:07 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:07 5: Mythz sending 02
2014.10.17 15:53:07 5: SW: 02
2014.10.17 15:53:07 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:07 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 15:53:07 5: THZ_Get: Try to get 'programFan_Mo_0'
2014.10.17 15:53:07 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 15:53:07 5: Mythz sending 02
2014.10.17 15:53:07 5: SW: 02
2014.10.17 15:53:07 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 15:53:08 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 15:53:08 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'


Mythz Logfile:

2014-10-16_21:43:56 Mythz DISCONNECTED
2014-10-16_21:44:02 Mythz CONNECTED
2014-10-16_21:44:04 Mythz DISCONNECTED
2014-10-16_21:44:04 Mythz CONNECTED
2014-10-16_21:44:04 Mythz DISCONNECTED
2014-10-16_21:44:04 Mythz CONNECTED
2014-10-16_21:44:04 Mythz DISCONNECTED
2014-10-16_21:44:04 Mythz CONNECTED
2014-10-16_21:44:04 Mythz DISCONNECTED
2014-10-16_21:44:05 Mythz CONNECTED
2014-10-16_21:44:05 Mythz DISCONNECTED
2014-10-16_21:48:12 Mythz CONNECTED
2014-10-16_21:48:20 Mythz DISCONNECTED
2014-10-16_21:48:20 Mythz CONNECTED
2014-10-16_21:48:20 Mythz DISCONNECTED
2014-10-16_21:48:20 Mythz CONNECTED
2014-10-16_21:55:20 Mythz DISCONNECTED
2014-10-16_21:55:23 Mythz CONNECTED
2014-10-16_22:13:26 Mythz DISCONNECTED
2014-10-16_22:13:32 Mythz CONNECTED
2014-10-16_22:14:13 Mythz DISCONNECTED
2014-10-16_22:14:44 Mythz CONNECTED
2014-10-16_22:14:44 Mythz DISCONNECTED
2014-10-16_22:14:44 Mythz CONNECTED


thanks.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 Oktober 2014, 16:46:35
will try to shield the raspi... maybe it helps.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 17 Oktober 2014, 16:50:48
FHEM is loaded onto a MacMini.
What should I do?

Thank you
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Oktober 2014, 17:06:36
Hi Koppl
please give us further informations:
software version of your heatpump?

how do you connect: direct usb or usb2ser+ serial cable?

post config and full-log as file

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 17 Oktober 2014, 17:52:47
The software of the heat pump is 4.19.
I connect the heat pump via USB.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Oktober 2014, 19:01:22
Koppl
I am sorry that I have to make you stupid questions but we have to start somewhere
1) did the interface respond something?
2) are you sure that the name of the interface (/dev/ttys000) is correct?
http://pbxbook.com/other/mac-tty.html
3) are you sure the frequency is correct?

immi     
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 17 Oktober 2014, 19:25:02
Zitat von: immi am 17 Oktober 2014, 19:01:22
Koppl
I am sorry that I have to make you stupid questions but we have to start somewhere
1) did the interface respond something?
2) are you sure that the name of the interface (/dev/ttys000) is correct?
http://pbxbook.com/other/mac-tty.html
3) are you sure the frequency is correct?

immi   

that's ok. thanks for the help

1) yes the interface respond
2) yes that is correct. with / dev / ttyUSB0 I get no connection
3) yes the frequency is 115200
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Oktober 2014, 20:02:37
Zitat von: Koppl am 17 Oktober 2014, 19:25:02
1) yes the interface respond
2) yes that is correct. with / dev / ttyUSB0 I get no connection
3) yes the frequency is 115200
Hi Koppl,
sorry if I insist.
I do not see from your logfile that the interface responds, how do you know that /dev/ttys000 is correct?
I would have expected something like /dev/cu.usbserial-FTG99I4O
Have a look here http://www.fhemwiki.de/wiki/Fhem_on_OS_X

Hi Markus
do you know which driver is needed in linux for the direct usb connection to the heatpump?
In the heatpump  there is a Serial-to-USB. but I do not know which one: FTDI  or PL230?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 17 Oktober 2014, 20:27:54
should be ftdi. will Check on my System.

EDIT:
It's a CP210x UART Bridge. Should work with system drivers
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 17 Oktober 2014, 22:30:05
Hello immi,

Zitat von: immi am 17 Oktober 2014, 20:02:37
Hi Koppl,
sorry if I insist.
I do not see from your logfile that the interface responds, how do you know that /dev/ttys000 is correct?
I would have expected something like /dev/cu.usbserial-FTG99I4O
Have a look here http://www.fhemwiki.de/wiki/Fhem_on_OS_X

immi

somehow I do not come on.
I get the device / dev / ttyUSB0 no connection.
Have now found out that the interface is not responding.
I have attached a photo from Mythz.

Following the log after rebooting:

2014.10.17 22:22:46 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:47 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:47 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:47 5: THZ_Get: Try to get 'sHeatRecoveredTotal'
2014.10.17 22:22:47 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:47 5: Mythz sending 02
2014.10.17 22:22:47 5: SW: 02
2014.10.17 22:22:47 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:48 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:48 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:48 5: THZ_Get: Try to get 'p03RoomTempStandbyHC1SummerMode'
2014.10.17 22:22:48 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:48 5: Mythz sending 02
2014.10.17 22:22:48 5: SW: 02
2014.10.17 22:22:48 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:49 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:49 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:49 5: THZ_Get: Try to get 'programHC1_Fr_0'
2014.10.17 22:22:49 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:49 5: Mythz sending 02
2014.10.17 22:22:49 5: SW: 02
2014.10.17 22:22:49 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:50 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:50 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:50 5: THZ_Get: Try to get 'programHC1_Fr_2'
2014.10.17 22:22:50 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:50 5: Mythz sending 02
2014.10.17 22:22:50 5: SW: 02
2014.10.17 22:22:50 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:51 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:51 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:51 5: THZ_Get: Try to get 'p01RoomTempDayHC2SummerMode'
2014.10.17 22:22:51 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:51 5: Mythz sending 02
2014.10.17 22:22:51 5: SW: 02
2014.10.17 22:22:51 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:51 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:51 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:51 5: THZ_Get: Try to get 'sHC1'
2014.10.17 22:22:51 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:51 5: Mythz sending 02
2014.10.17 22:22:51 5: SW: 02
2014.10.17 22:22:51 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:52 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:52 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:52 5: THZ_Get: Try to get 'p05DHWsetNightTemp'
2014.10.17 22:22:52 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:52 5: Mythz sending 02
2014.10.17 22:22:52 5: SW: 02
2014.10.17 22:22:52 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:53 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:53 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:53 5: THZ_Get: Try to get 'pHolidayEndMonth'
2014.10.17 22:22:53 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:53 5: Mythz sending 02
2014.10.17 22:22:53 5: SW: 02
2014.10.17 22:22:53 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:54 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:54 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:54 5: THZ_Get: Try to get 'programHC2_Mo-Fr_2'
2014.10.17 22:22:54 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:54 5: Mythz sending 02
2014.10.17 22:22:54 5: SW: 02
2014.10.17 22:22:54 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:55 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:55 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:55 5: THZ_Get: Try to get 'p02RoomTempNightHC2SummerMode'
2014.10.17 22:22:55 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:55 5: Mythz sending 02
2014.10.17 22:22:55 5: SW: 02
2014.10.17 22:22:55 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:55 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:55 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:55 5: THZ_Get: Try to get 'pHolidayEndDay'
2014.10.17 22:22:55 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:55 5: Mythz sending 02
2014.10.17 22:22:55 5: SW: 02
2014.10.17 22:22:55 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:56 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:56 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:56 5: THZ_Get: Try to get 'pHolidayBeginDay'
2014.10.17 22:22:56 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:56 5: Mythz sending 02
2014.10.17 22:22:56 5: SW: 02
2014.10.17 22:22:56 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:57 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:57 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:57 5: THZ_Get: Try to get 'p40Fanstage1AirflowOutlet'
2014.10.17 22:22:57 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:57 5: Mythz sending 02
2014.10.17 22:22:57 5: SW: 02
2014.10.17 22:22:57 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:58 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:58 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:58 5: THZ_Get: Try to get 'programFan_We_1'
2014.10.17 22:22:58 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:58 5: Mythz sending 02
2014.10.17 22:22:58 5: SW: 02
2014.10.17 22:22:58 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:59 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:59 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:59 5: HMLAN_Send:  HMLAN1 I:K
2014.10.17 22:22:59 5: THZ_Get: Try to get 'programFan_Mo_0'
2014.10.17 22:22:59 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:59 5: Mythz sending 02
2014.10.17 22:22:59 5: SW: 02
2014.10.17 22:22:59 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:22:59 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:22:59 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:22:59 5: THZ_Get: Try to get 'programHC1_Sa_2'
2014.10.17 22:22:59 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:22:59 5: Mythz sending 02
2014.10.17 22:22:59 5: SW: 02
2014.10.17 22:22:59 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:00 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:00 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:00 5: THZ_Get: Try to get 'programHC2_Mo-So_0'
2014.10.17 22:23:00 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:00 5: Mythz sending 02
2014.10.17 22:23:00 5: SW: 02
2014.10.17 22:23:00 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:01 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:01 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:01 5: THZ_Get: Try to get 'programFan_Mo_2'
2014.10.17 22:23:01 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:01 5: Mythz sending 02
2014.10.17 22:23:01 5: SW: 02
2014.10.17 22:23:01 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:02 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:02 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:02 5: THZ_Get: Try to get 'programFan_Mo-Fr_2'
2014.10.17 22:23:02 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:02 5: Mythz sending 02
2014.10.17 22:23:02 5: SW: 02
2014.10.17 22:23:02 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:03 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:03 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:03 5: THZ_Get: Try to get 'programFan_So_1'
2014.10.17 22:23:03 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:03 5: Mythz sending 02
2014.10.17 22:23:03 5: SW: 02
2014.10.17 22:23:03 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:03 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:03 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:03 5: THZ_Get: Try to get 'p17LowEndHC2'
2014.10.17 22:23:03 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:03 5: Mythz sending 02
2014.10.17 22:23:03 5: SW: 02
2014.10.17 22:23:03 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:04 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:04 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:04 5: THZ_Get: Try to get 'p11DHWsetManualTemp'
2014.10.17 22:23:04 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:04 5: Mythz sending 02
2014.10.17 22:23:04 5: SW: 02
2014.10.17 22:23:04 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:05 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:05 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:05 5: THZ_Get: Try to get 'programHC1_Mo_1'
2014.10.17 22:23:05 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:05 5: Mythz sending 02
2014.10.17 22:23:05 5: SW: 02
2014.10.17 22:23:05 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:06 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:06 5: THZ_Get: Try to get 'sHistory'
2014.10.17 22:23:06 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:06 5: Mythz sending 02
2014.10.17 22:23:06 5: SW: 02
2014.10.17 22:23:06 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:07 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:07 5: THZ_Get: Try to get 'programFan_Th_0'
2014.10.17 22:23:07 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:07 5: Mythz sending 02
2014.10.17 22:23:07 5: SW: 02
2014.10.17 22:23:07 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:07 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:07 5: THZ_Get: Try to get 'programHC1_Th_1'
2014.10.17 22:23:07 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:07 5: Mythz sending 02
2014.10.17 22:23:07 5: SW: 02
2014.10.17 22:23:07 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:08 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:08 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:08 5: THZ_Get: Try to get 'p44UnschedVent2'
2014.10.17 22:23:08 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:08 5: Mythz sending 02
2014.10.17 22:23:08 5: SW: 02
2014.10.17 22:23:08 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:09 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:09 5: THZ_Get: Try to get 'sElectrDHWTotal'
2014.10.17 22:23:09 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:09 5: Mythz sending 02
2014.10.17 22:23:09 5: SW: 02
2014.10.17 22:23:09 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:10 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:10 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:10 5: THZ_Get: Try to get 'programHC2_Sa-So_0'
2014.10.17 22:23:10 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:10 5: Mythz sending 02
2014.10.17 22:23:10 5: SW: 02
2014.10.17 22:23:10 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:11 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:11 5: THZ_Get: Try to get 'p03RoomTempStandbyHC2'
2014.10.17 22:23:11 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:11 5: Mythz sending 02
2014.10.17 22:23:11 5: SW: 02
2014.10.17 22:23:11 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:11 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:11 5: THZ_Get: Try to get 'programFan_Sa_1'
2014.10.17 22:23:11 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:11 5: Mythz sending 02
2014.10.17 22:23:11 5: SW: 02
2014.10.17 22:23:11 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:12 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:12 5: CUL_HM tr_steckdose_TROCKNER protEvent:CMDs_pending pending:1
2014.10.17 22:23:12 3: CUL_HM set tr_steckdose_TROCKNER statusRequest
2014.10.17 22:23:12 5: HMLAN_Send:  HMLAN1 S:+257DB6,00,01,00
2014.10.17 22:23:12 5: HMLAN_Send:  HMLAN1 S:S1FC743A3 stat:  00 t:00000000 d:01 r:1FC743A3 m:0A A001 010101 257DB6 010E
2014.10.17 22:23:12 5: CUL_HM tr_steckdose_TROCKNER protEvent:CMDs_processing... pending:0
2014.10.17 22:23:12 5: THZ_Get: Try to get 'programHC2_Fr_2'
2014.10.17 22:23:12 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:12 5: Mythz sending 02
2014.10.17 22:23:12 5: SW: 02
2014.10.17 22:23:12 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:13 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:13 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:13 5: THZ_Get: Try to get 'programHC2_So_1'
2014.10.17 22:23:13 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:13 5: Mythz sending 02
2014.10.17 22:23:13 5: SW: 02
2014.10.17 22:23:13 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:14 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:14 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:14 5: THZ_Get: Try to get 'pHolidayBeginTime'
2014.10.17 22:23:14 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:14 5: Mythz sending 02
2014.10.17 22:23:14 5: SW: 02
2014.10.17 22:23:14 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:15 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:15 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:15 5: THZ_Get: Try to get 'programDHW_We_1'
2014.10.17 22:23:15 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:15 5: Mythz sending 02
2014.10.17 22:23:15 5: SW: 02
2014.10.17 22:23:15 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:15 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:15 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:15 5: THZ_Get: Try to get 'programDHW_Mo_0'
2014.10.17 22:23:15 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:15 5: Mythz sending 02
2014.10.17 22:23:15 5: SW: 02
2014.10.17 22:23:15 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:16 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:16 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:16 5: THZ_Get: Try to get 'programDHW_Sa_2'
2014.10.17 22:23:16 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:16 5: Mythz sending 02
2014.10.17 22:23:16 5: SW: 02
2014.10.17 22:23:16 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:17 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:17 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:17 5: THZ_Get: Try to get 'programDHW_Th_0'
2014.10.17 22:23:17 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:17 5: Mythz sending 02
2014.10.17 22:23:17 5: SW: 02
2014.10.17 22:23:17 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:18 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:18 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:18 5: THZ_Get: Try to get 'programHC2_Sa-So_1'
2014.10.17 22:23:18 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:18 5: Mythz sending 02
2014.10.17 22:23:18 5: SW: 02
2014.10.17 22:23:18 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:19 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:19 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:19 5: THZ_Get: Try to get 'programDHW_Mo-So_1'
2014.10.17 22:23:19 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:19 5: Mythz sending 02
2014.10.17 22:23:19 5: SW: 02
2014.10.17 22:23:19 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:19 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:19 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:19 5: THZ_Get: Try to get 'sBoostHCTotal'
2014.10.17 22:23:19 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:19 5: Mythz sending 02
2014.10.17 22:23:19 5: SW: 02
2014.10.17 22:23:19 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:20 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:20 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:20 5: THZ_Get: Try to get 'programDHW_Mo-Fr_1'
2014.10.17 22:23:20 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:20 5: Mythz sending 02
2014.10.17 22:23:20 5: SW: 02
2014.10.17 22:23:20 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:21 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:21 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:21 5: THZ_Get: Try to get 'programHC2_We_1'
2014.10.17 22:23:21 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:21 5: Mythz sending 02
2014.10.17 22:23:21 5: SW: 02
2014.10.17 22:23:21 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:22 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:22 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:22 5: THZ_Get: Try to get 'sDHW'
2014.10.17 22:23:22 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:22 5: Mythz sending 02
2014.10.17 22:23:22 5: SW: 02
2014.10.17 22:23:22 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:23 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:23 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:23 5: THZ_Get: Try to get 'programHC1_Tu_2'
2014.10.17 22:23:23 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:23 5: Mythz sending 02
2014.10.17 22:23:23 5: SW: 02
2014.10.17 22:23:23 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:23 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:23 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:23 5: THZ_Get: Try to get 'programDHW_Sa-So_2'
2014.10.17 22:23:23 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:23 5: Mythz sending 02
2014.10.17 22:23:23 5: SW: 02
2014.10.17 22:23:23 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:24 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:24 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:24 4: HMLAN_ack: timeout - clear queue
2014.10.17 22:23:24 5: THZ_Get: Try to get 'programFan_Tu_1'
2014.10.17 22:23:24 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:24 5: Mythz sending 02
2014.10.17 22:23:24 5: SW: 02
2014.10.17 22:23:24 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:25 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:25 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:25 5: THZ_Get: Try to get 'programFan_Mo-Fr_0'
2014.10.17 22:23:25 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:25 5: Mythz sending 02
2014.10.17 22:23:25 5: SW: 02
2014.10.17 22:23:25 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:26 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:26 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:26 5: THZ_Get: Try to get 'programHC1_Sa-So_1'
2014.10.17 22:23:26 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:26 5: Mythz sending 02
2014.10.17 22:23:26 5: SW: 02
2014.10.17 22:23:26 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:27 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:27 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:27 5: THZ_Get: Try to get 'programHC1_Th_0'
2014.10.17 22:23:27 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:27 5: Mythz sending 02
2014.10.17 22:23:27 5: SW: 02
2014.10.17 22:23:27 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:28 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:28 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:28 5: THZ_Get: Try to get 'p01RoomTempDayHC2'
2014.10.17 22:23:28 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:28 5: Mythz sending 02
2014.10.17 22:23:28 5: SW: 02
2014.10.17 22:23:28 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:28 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:28 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:28 5: THZ_Get: Try to get 'programHC1_So_1'
2014.10.17 22:23:28 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:28 5: Mythz sending 02
2014.10.17 22:23:28 5: SW: 02
2014.10.17 22:23:28 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:29 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:29 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2014.10.17 22:23:29 5: THZ_Get: Try to get 'programHC2_Tu_1'
2014.10.17 22:23:29 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2014.10.17 22:23:29 5: Mythz sending 02
2014.10.17 22:23:29 5: SW: 02
2014.10.17 22:23:29 5: Mythz start Funktion THZ_ReadAnswer
2014.10.17 22:23:30 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.10.17 22:23:30 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: xyz_fhem am 17 Oktober 2014, 23:25:15
immi, the Version you sent me via pm seem to work fine.
My Graphs look much better now, values get loged correctly as far as i can see.

Please find attached the verbose=5 log for THZ

How does it look from a developers Point of view?

Thanks and regards
xyz_fhem
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Oktober 2014, 06:53:01
HI xyz_fhem
log is fine, as far as I see.
I can commit it, v0.110 uploaded.
chanhelog: 00_THZ: bugfix for interface (with serial cable) trunkating messages (forum 209294)
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Oktober 2014, 07:11:07
Zitat von: Koppl am 17 Oktober 2014, 22:30:05
Hello immi,
somehow I do not come on.
I get the device / dev / ttyUSB0 no connection.

Hi Koppl
you need the serial interface name.
I cannot tell you which serial interface to use, because I do not have your hardware and connection type.
What I can tell and repeat:
1) forget  /dev/ttyUSB0 on macos. It is not a RasPI.
2) read the wiki http://www.fhemwiki.de/wiki/Fhem_on_OS_X
most important

$ls /dev/cu.*
/dev/cu.usbserial-xxxxxxxx
$ls /dev/tty.*
/dev/tty.usbserial-xxxxxxxx

I have  /dev/cu.usbserial-FTG99I4O but with different hardware.
3) Markus was very nice to identify your hardware type: CP210x
Probably you need to install the serial driver for macos http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 18 Oktober 2014, 09:26:05
Hello immi,

have now installed the driver.
with /dev/tty.SLAB_USBtoUART@115200 it works now

Thank you
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Oktober 2014, 10:05:14
Hi Koppl
happy you did it,
would you be so nice to improove http://www.fhemwiki.de/wiki/Fhem_on_OS_X with your usercase?
just write down a proposal and give it to a wiki admin to upload
we do not want all this info to get lost. some other users could need it.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 18 Oktober 2014, 10:09:22
you can send a proposal to me, i can add it to the wiki.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Koppl am 19 Oktober 2014, 10:17:24
hello,

yes I write a proposal and send it micomat.

One problem I have.
I like described in the wiki added to the FanSelector for ventilation control.
The ventilation is not around.
How often FHEM reads the data from the heating and sends it back?

The readings will be properly time when I compare.

Thank you
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 Oktober 2014, 15:32:56
Zitat von: Koppl am 19 Oktober 2014, 10:17:24

How often FHEM reads the data from the heating and sends it back?

I do not understand your question.  There are parameters for thelling fhem how often to read.
Have a look at this example: start simple and when you understand better fhem, let your config grow.


define Mythz THZ fritz3270:2003
attr Mythz DbLogExclude .*:600
attr Mythz event-min-interval s.*:4800
attr Mythz event-on-change-reading .*
attr Mythz interval_sDHW 400
attr Mythz interval_sElectrDHWDay 2400
attr Mythz interval_sElectrDHWTotal 43200
attr Mythz interval_sGlobal 400
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 interval_sHistory 86400
attr Mythz interval_sLast10errors 86400
attr Mythz room pompa
attr Mythz userReadings AussenTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[1]}, VorlaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[3]}, RuecklaufTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[5]}, WWTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[9]}
#attr Mythz event-on-update-reading p\d.*
#attr Mythz interval_sHC2 400
define FileLog_Mythz FileLog /opt/fhem/log/Mythz-%Y-%m.log Mythz:.*
attr FileLog_Mythz logtype thz:plot,text
attr FileLog_Mythz room pompa


define FanSelectorDay dummy
attr FanSelectorDay devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3@blue
attr FanSelectorDay group THZ
attr FanSelectorDay room pompa
attr FanSelectorDay setList 0 1 2 3 60minOff
attr FanSelectorDay webCmd 0:1:2:3:60minOff
define Notify_p07FanStageDay notify FanSelectorDay  IF ([FanSelectorDay] eq "60minOff") (define at_D_60minOff at +00:59:00 set Mythz p07FanStageDay [Mythz:p07FanStageDay],set Mythz p07FanStageDay 0, setstate FanSelectorDay 60minOff) ELSE (set Mythz p07FanStageDay $EVENT)
define Notify_FanselectorDay notify (Mythz.p07FanStageDay.*) setstate FanSelectorDay $EVTPART1


define FanSelectorNight dummy
attr FanSelectorNight devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2 3:vent_ventilation_level_3@blue
attr FanSelectorNight group THZ
attr FanSelectorNight room pompa
attr FanSelectorNight setList 0 1 2 3 60minOff
attr FanSelectorNight webCmd 0:1:2:3:60minOff
define Notify_p08FanStageNight notify FanSelectorNight IF ([FanSelectorNight] eq "60minOff") (define at_N_60minOff at +00:59:00 set Mythz p08FanStageNight [Mythz:p08FanStageNight],set Mythz p08FanStageNight 0, setstate FanSelectorNight 60minOff) ELSE (set Mythz p08FanStageNight $EVENT)
define Notify_FanselectorNight notify (Mythz.p08FanStageNight.*) setstate FanSelectorNight $EVTPART1

define FanPassiveCooling dummy
attr FanPassiveCooling group THZ
attr FanPassiveCooling room pompa
attr FanPassiveCooling setList 0 1 2
attr FanPassiveCooling webCmd 0:1:2
#attr FanPassiveCooling devStateIcon 0:vent_ventilation_level_0 1:vent_ventilation_level_1 2:vent_ventilation_level_2
define Notify_p75passiveCooling notify FanPassiveCooling set Mythz p75passiveCooling $EVENT
define Notify_PassiveCooling notify (Mythz.p75passiveCooling.*) setstate FanPassiveCooling $EVTPART1

define rg_thz readingsGroup Mythz:<%temp_outside>,<Aussen>,AussenTemp Mythz:<%sani_supply_temp@red>,<Vorlauf>,VorlaufTemp Mythz:<%sani_return_temp@blue>,<Rücklauf>,RuecklaufTemp Mythz:<%sani_boiler_temp@BD7800>,<Wasser>,WWTemp
attr rg_thz group THZ
attr rg_thz room pompa
attr rg_thz valueFormat { AussenTemp => '%.1f °C', VorlaufTemp => '%.1f °C', AussenTemp=> '%.1f °C', RuecklaufTemp=> '%.1f °C', WWTemp=> '%.1f °C' }



Willy, Markus, Tom ... have much better, fancy configuration. Maybe they will show you the real potential of FHEM.

Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 19 Oktober 2014, 16:43:05
Zitat
Willy, Markus, Tom ... have much better, fancy configuration. Maybe they will show you the real potential of FHEM.

I posted my whole configuration including screen dumps inside this thread, approx.April time frame. Nothing changed meanwhile, still works.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 19 Oktober 2014, 16:52:49
here we go (http://forum.fhem.de/index.php/topic,13132.msg168721.html#msg168721)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 Oktober 2014, 17:06:46
nice effect of switching off daylight savings (see attached jpg)  :)

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Oktober 2014, 22:01:11
a timeloop  8)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 27 Oktober 2014, 23:47:46
yep :) back to the past!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: gerry.s am 29 Oktober 2014, 18:07:37
Hallo,

ich habe leider ständig:

2014-10-29 17:58:12 THZ Mythz CONNECTED
2014-10-29 17:58:12 THZ Mythz DISCONNECTED
2014-10-29 17:58:13 THZ Mythz CONNECTED
2014-10-29 17:58:13 THZ Mythz DISCONNECTED
2014-10-29 17:58:13 THZ Mythz CONNECTED
2014-10-29 17:58:14 THZ Mythz DISCONNECTED
2014-10-29 17:58:14 THZ Mythz CONNECTED
2014-10-29 17:58:15 THZ Mythz DISCONNECTED
2014-10-29 17:58:16 THZ Mythz CONNECTED

im "Event Monitor".
Liegt das vielleicht am BananaPi oder muss ich da was in der fhem.cfg
eintragen? Hab das zwar über die Suche an verschiedenen Stellen gefunden,
aber leider keine Lösung.

Gerry
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Oktober 2014, 22:55:10
hi Gerry
is the Connection down or do you just dont want to See this messages?
i See then also but Connection is Fine. do you use serial or USB?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: gerry.s am 29 Oktober 2014, 23:45:00
Hi Micromat,
Connection is fine, but my web interface is very slow and I thought that's because of the log traffic. I use direct USB connection.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 30 Oktober 2014, 20:47:31
okay we See this issue on USB. Mine is also not sooo fast but this may also depend in the number of data read from the thz. this error may occur to electrical interferences.
should be no Big Thing.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Oktober 2014, 09:44:37
Zitat von: gerry.s am 29 Oktober 2014, 18:07:37
Hallo,
ich habe leider ständig:
2014-10-29 17:58:12 THZ Mythz CONNECTED
2014-10-29 17:58:13 THZ Mythz DISCONNECTED
2014-10-29 17:58:13 THZ Mythz CONNECTED
2014-10-29 17:58:14 THZ Mythz DISCONNECTED

im "Event Monitor".
Liegt das vielleicht am BananaPi oder muss ich da was in der fhem.cfg
eintragen? Hab das zwar über die Suche an verschiedenen Stellen gefunden,
aber leider keine Lösung.
Gerry
If your system is normally working and  you get such a log sporadically, like Markus, I expect an interference problem.
Someone correlated problem with some events in the heatpump.
I do not have your configuration, therefore I cannot go systematically to the root cause.
I would try to stabilize the current supply and in parallel build some kind of emc-filter or magnetic shield.

If your system is reacting slowly, it could be related to the huge ammount of data you can generate in FHEM.
Post more information as attachment: config file, plot files, logs... maybe someone can help you.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 14 November 2014, 21:05:32
I am wondering how to interpret the physical meaning of the parameter sHeatRecoveredDay with respect to the calculation of the COP. Is it already included in sHeatHCDay (sHeatHCDay = sHeatRecoveredDay + <energy transferred from outside air>)? Considering the logged values it would be my guess. Today's values are as follows:
sHeatHCDay = 38858 Wh
sHeatRecoveredDay = 12227 Wh
sElectrHCDay = 10313 Wh
(no boost)

Though, the sum of the electrical values (incl. boost) does not match the metered values. The THZ reports approx. 200 kWh less than the meter.

Cheers!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 November 2014, 10:44:34
godmorgon
happy that you joined the group.
I think, I am not sure, that sHeatRecovered is for the ventilation. You can test it is you disable ventilation for one day, it should not change much.

if you have no boost (very normal with this wheather), the cop should be sHeatHCDay/sElectrHCDay = 38858 /10313 = circa 3.7

p.s. the cop makes not so much sense if you have sunncollectors.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 November 2014, 20:57:19
Did you check the installation manual (http://www.tecalor.de/dam/jcr:8c31554d-ecb0-4e05-a951-4a6bbea4e9e1/bedienung---installation-luftungsgerat-thz-303-403-sol.pdf) for these questions? As far as I remember there is a chapter describing such details.
edit:
I've been wrong. There's no such chapter in the manual.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 17 November 2014, 22:56:54
I gave it another thought and came to the conclusion that sHeatRecoveredDay is what its name says - heat amount recovered from the ventilation. It is a kind of energy loss prevention/compensation due to ventilation - if there is no ventilation then there is no associated loss. So sHeatRecoveredDay cannot be an additional gain. And therefore, it is neither part of sHeatHCDay nor it should be added to it. So the heat pump COP should not be influenced by this value. Only the overall performance of the house as a system benefits from this recovered energy.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 18 November 2014, 07:45:07
I do not fully agree when you say "if there is no ventilation then there is no associated loss". If there's no forced, THZ based ventilation the user has to replace it by manual ventilation, means opening the windows frequently. So the value of  sHeatRecoveredDay shows the amount of avoided energy loss of manual ventilation. This indeed has nothing to do with COP, but anyway it is a benefit coming from the THZ based system, which otherwise couldn't be reached.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 November 2014, 09:29:56
I think the truth is inbetween. I think the energy from sHeatRecovery is produced by the energy of the ventilation. I posted earlier the energy the different steps require, at least for my ventilation settings. So one could take these into account and assume that this energy is actually "produced". ONow the counter argument:  If I increase the ventilation from level 1 to level 3 more air is turned over per time unit. Therefore sHeatRecovery will increase but this is a wrong assumption and can only be compared to ventilation status without HeatRecovery. Has anybody tested this realtionship between ventilation levels and sHeatReoveryDay?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 18 November 2014, 21:30:11
@willybass
I did not refer to an absolute lack of ventilation. So we mean the same.

@houseowner123
I have the impression that heat recovery is done with a simple heat exchanger. Because the diagrams show a continuous increase of the recovered energy which is fully unrelated to the heat pump timing. If this is true the value of sHeatRecovery is probably estimated from the exchanged air volume and the temperature differerence.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 November 2014, 10:23:31
Zitat von: godmorgon am 18 November 2014, 21:30:11
If this is true the value of sHeatRecovery is probably estimated from the exchanged air volume and the temperature differerence.

Also my expectation.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 19 November 2014, 19:49:06
The THZ display provides the current HC pressure. Though, the manual does not show parameter name/number for it. Is there a way to read the HC pressure value via the maintenance interface ot CAN bus?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 November 2014, 20:55:19
If you mean P_nd and P_hd , they are already in sGlobal.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 19 November 2014, 22:10:32
Nope, I mean the hydraulic pressure in the heating circuit. It is the second last value in the list with "actual values" - "PRESSURE HTG CIRC".
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 November 2014, 23:27:06
Zitat von: godmorgon am 19 November 2014, 22:10:32
Nope, I mean the hydraulic pressure in the heating circuit. It is the second last value in the list with "actual values" - "PRESSURE HTG CIRC".
sorry
I have no idea where to find it ( the register, the position in the register) and how it is encoded.
Do you have a clue?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 20 November 2014, 14:14:54
ZitatDo you have a clue?
I have not started hacking yet.

FYI: Today Stiebel technicians performed commissioning of my heat pump. They told me that the software version shown in the display (5.39) is the software version of the display module and NOT of the main board. The current SW version of a THZ 404 SOL is 3.15 (dated May 14, 2014).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 22 November 2014, 00:14:58
Immi
Can you send the Parameter P29 into the THZ?
Because the THZ has a bug. I have set the parameter P29=4.
When I now change P29 parameter to 2 and make a restart.
After Reboot the parameter P29 = 4.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 November 2014, 06:41:46
Zitat von: Gassi am 22 November 2014, 00:14:58
Immi
Can you send the Parameter P29 into the THZ?
Hi GAssi
I think it should be possible.
v0.111 --> P21,22,23,24,25,29 added and uploaded
please test tomorrow

Hi godmorgon
so you see any improvements/change after the upgrade from Stiebel

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 23 November 2014, 20:00:10
I have not noticed any changes because I currently do not test anything. If there is a list of known bugs/issues?

There is a typo in 00_THZ.pm - the entry "interval_sBoostDHWTotal" is present twice (lines 342 and 343 in ver 0.111). I guess the second entry should read "interval_sBoostHCTotal".
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 November 2014, 21:34:35
Zitat von: godmorgon am 23 November 2014, 20:00:10
I have not noticed any changes because I currently do not test anything. If there is a list of known bugs/issues?
not to my knowledge
Zitat
There is a typo in 00_THZ.pm - the entry "interval_sBoostDHWTotal" is present twice (lines 342 and 343 in ver 0.111). I guess the second entry should read "interval_sBoostHCTotal".
thanks, next time I commit it will be fixed

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 24 November 2014, 00:10:21
Not sure if this is related but last night I ran an update. At 10 am (on events listed) Mythz disconnected. The only correlating event at the time is the mystic disconnect-reappear.

2014.11.23 09:42:48 1: /dev/ttyUSB0 disconnected, waiting to reappear (Mythz)
2014.11.23 09:42:53 3: Setting Mythz baudrate to 115200
2014.11.23 09:42:53 1: /dev/ttyUSB0 reappeared (Mythz)


Tonight I restarted the FHEM, RasPi , restart the LWZ, nothing helped.
The log after restart claims that mythz is opened, but it isn't. Any suggestions anyone?  :-\ Thanks!

2014.11.24 00:03:17 0: Server shutdown
2014.11.24 00:03:21 1: Including fhem.cfg
2014.11.24 00:03:21 3: telnetPort: port 7072 opened
2014.11.24 00:03:22 3: WEB: port 8083 opened
2014.11.24 00:03:22 3: WEBphone: port 8084 opened
2014.11.24 00:03:22 3: WEBtablet: port 8085 opened
2014.11.24 00:03:22 2: eventTypes: loaded 450 events from ./log/eventTypes.txt
2014.11.24 00:03:23 3: Opening Mythz device /dev/ttyUSB0
2014.11.24 00:03:23 3: Setting Mythz baudrate to 115200
2014.11.24 00:03:23 3: Mythz device opened
2014.11.24 00:03:27 3: Opening CUL_0 device /dev/ttyACM0
2014.11.24 00:03:27 3: Setting CUL_0 baudrate to 9600
2014.11.24 00:03:27 3: CUL_0 device opened
2014.11.24 00:03:27 3: CUL_0: Possible commands: BCFiAZEGMKURTVWXefmltux
2014.11.24 00:03:27 1: Including ./log/fhem.save
2014.11.24 00:03:28 1: usb create starting
2014.11.24 00:03:30 3: Probing CUL device /dev/ttyAMA0
2014.11.24 00:03:30 3: Probing TCM_ESP3 device /dev/ttyAMA0
2014.11.24 00:03:30 3: Probing FRM device /dev/ttyAMA0
2014.11.24 00:03:36 1: usb create end
2014.11.24 00:03:36 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.11.24 00:03:36 0: Server started with 55 defined entities (version $Id: fhem.pl 6913 2014-11-08 10:32:44Z rudolfkoenig $, os linux, user fhem, pid 2212)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 24 November 2014, 08:33:38
HI,

same happened to me after upgrading fhem and the thz module. Mythz seams to be opened, but it isn't.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 November 2014, 08:54:19
If you want to revert to v0110 manually, download it from here
https://github.com/mhop/fhem-mirror/blob/9e3218d56713c291d42f5562c3455bf2160588dd/fhem/FHEM/00_THZ.pm

other stuff you can do is to force a full update.
or to look in  the log-file after enabling verbose 5

I do expect the problem is related to something else. more this night.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 24 November 2014, 17:44:43
Hi immi,

even after downgrading to version 0.110 I cant see the THZ:

2014.11.24 17:33:40 3: Opening Mythz device /dev/ttyUSB0
2014.11.24 17:33:40 3: Setting Mythz baudrate to 115200
2014.11.24 17:33:40 3: Mythz device opened
2014.11.24 17:33:49 1: Including ./log/fhem.save
2014.11.24 17:33:49 1: usb create starting
2014.11.24 17:33:51 3: Probing CUL device /dev/ttyAMA0
2014.11.24 17:33:51 3: Probing TCM_ESP3 device /dev/ttyAMA0
2014.11.24 17:33:51 3: Probing FRM device /dev/ttyAMA0
2014.11.24 17:33:57 3: Probing TCM_ESP3 device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing TCM_ESP2 device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing FHZ device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing TRX device /dev/ttyUSB1
2014.11.24 17:33:58 3: Probing ZWDongle device /dev/ttyUSB1
2014.11.24 17:33:58 3: Probing FRM device /dev/ttyUSB1
2014.11.24 17:34:03 1: usb create end
2014.11.24 17:34:03 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.11.24 17:34:04 0: Server started with 33 defined entities (version $Id: fhem.pl 6913 2014-11-08 10:32:44Z rudolfkoenig $, os linux, user fhem, pid 2746)
2014.11.24 17:34:04 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:05 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEB. Don't forget to save config.
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEBphone. Don't forget to save config.
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEBtablet. Don't forget to save config.
2014.11.24 17:34:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:08 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:10 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:13 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:13 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 November 2014, 18:59:50
I was quite sure that it was not related to THZ v0111.
Another module causes you some problems in combination with thz.

have you tried reverting everything to an old status?
you should find it in   /fhem/restoreDir/-datum-

than if the old status is working we have to look which fhem-modules have changed in the meanwhile, and one by one analyze them.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 24 November 2014, 19:20:18
immi: what is the command for restoring a status. Can it be done from within the FHEM web interface?

Thanks!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 November 2014, 20:06:20
Zitat von: houseowner123 am 24 November 2014, 19:20:18
immi: what is the command for restoring a status. Can it be done from within the FHEM web interface?
Thanks!

I suggest that you go to command line and with trial and error copy the files:
the stucture is simple

[/opt/fhem/restoreDir] # ls
2014-11-09/ 2014-11-22/ 2014-11-24/

I have updated 3 times , I select the last one and copy them to the original path

[/opt/fhem/restoreDir] # cd 2014-11-24/
[/opt/fhem/restoreDir/2014-11-24] # ls
CHANGED  FHEM/    docs/
[/opt/fhem/restoreDir/2014-11-24] # cd FHEM
[/opt/fhem/restoreDir/2014-11-24/FHEM] # ls
00_THZ.pm             98_HourCounter.pm     HttpUtils.pm
10_CUL_HM.pm          98_WOL.pm             TcpServerUtils.pm
33_readingsGroup.pm   98_logProxy.pm        controls_fhem.txt
98_CustomReadings.pm  98_structure.pm       firmware/
98_HMinfo.pm          HMConfig.pm
[/opt/fhem/restoreDir/2014-11-24/FHEM] # cp * /opt/fhem/FHEM/


immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 November 2014, 22:06:21
I made a full update in the night from 21st to 22nd of November, a few hours before the new 00_THZ version was accessible. It works, so currently I resist any thought of doing another update ...
But I need to mention that I also had some trouble in that night: I also couldn't access the THZ. I couldn't repair it by rebooting the Raspberry Pi, but it worked again after a power cycle of RasPi.
Initially the update didn't work at all since the restoreDir directory had a wrong owner, thus no sub directory under restoreDir could be created. After a while it turned out that there had been some changes in the update code by Rudolf Koenig recently. Changing access rights using chown (change owner) and chgrp change group) solved the issue.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 November 2014, 22:22:35
Currently I deal with p30integralComponent. Does anyone know how to visualize or calculate the actually summed up value of kmin (KelvinMinutes) since last compressor action?
Reason for that it that I frequently noticed unnecessary start of the compressor, even if the room temperature is still too high, e.g. caused by sun shining through southern windows. I could avoid that by increasing P30 from 100Kmin (default) to currently 300Kmin.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 07:56:51
Meanwhile I have the same issue: Mythz says "connected" but it isn't. Last entries in Mythz.log look like
2014-11-24_19:28:31 Mythz DISCONNECTED
2014-11-24_19:28:37 Mythz CONNECTED
2014-11-24_19:28:41 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:28:19 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:35:14 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:40:36 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:53:08 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:56:32 Mythz programDHW_So_1: n.a.--n.a.
2014-11-25_06:40:31 Mythz programDHW_So_1: n.a.--n.a.
2014-11-25_07:00:20 Mythz programDHW_So_1: n.a.--n.a.

Every row shows either a shutdown-restart of fhem, a reboot of RasPi or a power cycle of RasPi.
The issue began exactly in the point in time when I had to reboot my Fritz.Box for a different reason.
Trying to get values from the THZ by "get <parameter>" results in the fhem UI showing "msg2 closed connection".

I need to mention that I'm still on 00_THZ version 0.110.
I already tried to shutdown fhem + copy whole contents of backup directory (.../restoreDir/<Date>/*) + power cycle RasPi, but it didn't help either. Therefore it looks like the issue is outside fhem. But I didn't force any Linux updates since weeks.

After having switched to verbose level 5 I found an entry in the fhem.log file showing
2014.11.25 07:48:37 5: Cmd: >setstate Mythz disconnected<
2014.11.25 07:48:37 5: Cmd: >setstate Mythz 2014-11-22 00:27:53 HC1_average Error evaluating Mythz userReading HC1_average: Bareword "HC1_avg" not allowed while "strict subs" in use at (eval 856191) line 1.<

But this code does no more exist in my configuration since a couple of days. I don't know where it comes from. Any idea?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 10:51:12
I do not make any substantial change to THZ since 6 weeks. V0111 is definitely not responsible
I do not see any failure with NAS, fritzbox, MACOS; with direct serial connection or with ser2net.

1) Try to look what you have in common: e.g. servertype

2) Try to disable all connected hardware: e.g. remove all CUL usb (I do not have any CUL)

3) there was a change to the CUL and DEVIO 10 days ago
https://github.com/mhop/fhem-mirror/commit/6cae87be663ce0486375b510dca69de619c6a52b
@Willy here you can try the following? stop fhem,  remove line 391 from FHEM/DevIo.pm,  delete fhem.save, start fhem

4) please post the log text file with verbose 5

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 12:11:38
@ immi:
Since I'm still on V0110 I also believe it has nothing to do with the THZ module. I'll try the suggested steps tonight.

@ michaelk68 and houseowner123:
Should we try to find out common things in our configurations?
My config consists of (unsorted list as it came to my mind)
If we share same parts of config these might be on suspicion.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 25 November 2014, 13:23:23
I restored my config before the fhem update. It's still not working. So I think it's depends on a linux update.
I have a Raspi with linux wheezy, which is running fhem.
Connected is the THZ over USB, some 1wire temperature sensors, and an USB IR reader for smart metering.
I did install linux updates on the weekend!

Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 14:06:41
so up to now Raspi / Linux seems to be the only correlation. Hopefully houseowner123's data will confirm that.

@ immi:
on which platform does your fhem work? Didn't you use a Raspi too? In that case I wonder why you do not (yet?) see the issue.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 14:20:44
Zitat von: willybauss am 25 November 2014, 14:06:41
@ immi:
on which platform does your fhem work? Didn't you use a Raspi too? In that case I wonder why you do not (yet?) see the issue.
please read « Antwort #941 am: Heute um 10:51:12 »
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 November 2014, 15:14:20
Confirmed. I use Raspi too.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 17:33:52
Zitat von: immi am 25 November 2014, 14:20:44
please read « Antwort #941 am: Heute um 10:51:12 »
I already did so. After having read again I need to repeat the question - for you in more precise manner:

does your fhem run on NAS or on fritzbox - assuming that MACOS can be sorted out. There are indeed users having in installed on e.g. synology diskstation. Therefore  « Antwort #941 am: Heute um 10:51:12 » is not self explanatory.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 18:08:31
Hi Willy
My FHEM runs normally on QNAP with a ser2net in cascade to a usb2serial converter.
I also tested yesterday v0111 on my macos with ser2net in cascade to a usb2serial converter.
I also tested yesterday  v0111 on my fritzbox without ser2net (direct usb2serial converter).
immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 25 November 2014, 18:15:44
Hi immi,

line 391 in devio.pm is empty, is it correct? I deleted it and restarted fhem, but without success.

Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 20:15:11
Zitat von: michaelk68 am 25 November 2014, 18:15:44
Hi immi,

line 391 in devio.pm is empty, is it correct? I deleted it and restarted fhem, but without success.

Hi Michael
line 391 is not empty in the last version of  devio.pm, look here
https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/DevIo.pm
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 20:37:33
I think I can simulate the issue with the command:

setreading Mythz state disconnected


the fhem remain locked also after restart

I can fix it with

setreading Mythz state opened



I do not know where it is coming.
I have to simulate it because my connecction is always stable, never disconnected

have a try
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 25 November 2014, 21:05:07
immi: In my eyes you're a genius! :D Big thank you! Mythz back in full gear! :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 21:51:08
sounds perfect. Nevertheless I took the chance to do as immi suggested, hoping that we can find the root cause instead of just fixing the issue without knowing where it came from.

After having commented out row 391 from DevIo.pm  fhem reports "Mythz opened" and indeed it works  :) .

I'll send the fhem log file as well as Mythz log file (verbose level 5) to immi by email, since I don't have time to check if there is any contents which I don't want to show to the rest of the world.

edit:
row 391 looked like (before I commented it out):  "setReadingsVal($hash, "state", "disconnected", TimeNow());"
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 25 November 2014, 21:55:11
Untill I find a patch (week-end),
1) keep the fhem updated
2) repeat the command setreading Mythz state opened every hour with at
define cerotto at +*00:59:00 setreading Mythz state opened

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 22:29:12
I still wonder why rolling back to the state before last update didn't solve the issue. DevIo.pm had been part of the backup in ...\restoreDir\... folder. Since nothing solved the issue I finally rolled back all the files including  DevIo.pm. But that didn't solve it either.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 25 November 2014, 23:24:02
Zitat von: immi am 25 November 2014, 21:55:11
Untill I find a patch (week-end),
1) keep the fhem updated
2) repeat the command setreading Mythz state opened every hour with at
define cerotto at +*00:59:00 setreading Mythz state opened

immi
It looks like there's another alternative: since Mythz works again meanwhile (thanks again to immi!) I copied the old version of DevIo.pm from backup to the active .../FHEM directory. It doesn't contain the    ...setReadingsVal($hash, "state", "disconnected", ... code at all.
As long as I don't force further updates I expect it to work.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: michaelk68 am 26 November 2014, 17:35:54
Hi immi,

I need to run:

setreading Mythz state opened

only once. It's running since yesterday night without problems!

Thx
Michael
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 26 November 2014, 19:25:24
I tried to establish a separate communication channel with the THZ according to the protocol "specification". But something goes wrong. On receiving 0x02 the THZ replies with 0x10. Any other requests (e.g. from the original heatpump monitor homepage) remain unanswered - no reply at all. Only if I send 0x02 0x10 0x03 the THZ replies with 0x10 0x02. But after acknowledging it with 0x10 there is no additional data provided. The serial port setup is as used by 00_THZ.pm (115200 bps, 8N1). Any ideas?

EDIT
I do not quite understand how it is possible that the original code by Robert uses link speed of 57600 and the fhem implementation runs at 115200. Is it related to newer firmware versions?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 November 2014, 20:14:58
godmorgon
Where do you have a protocol "specification"?
I do not fully understand your question: do you want to hack the device? 
Edit or use the sub THZ_debugread($); I used it to test ranges of registers and save the answer in a files;
You can call it with "get Mythz debug_read_raw_register_slow"
It is selfexplaining.

If you want to start from 0, here you have an example

get Mythz sHistory --> register 09


FHEM               <->      LWZ304
02                    ->                                # I  want to speak
                       <-          10                  # ok I hear you
01000A091003        ->                                # tell me about register 09 please
                     <-          10                  # ok I understood what you want
------delay depending on the firmware -----
                     <-          02                  # I want to speak
10                  ->                               # ok I hear you
                     <-    0100D9090554000003A5000100CD1003       
10                 ->                                # thanks I understood


explanation of  the answer
0100              D9    09               0554000003A5000100CD       1003
readheader     crc    register        data                                      footer

It is oversimplified. The protocol in some cases is much more interesting :)
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 26 November 2014, 21:09:12
Zitat von: godmorgon am 26 November 2014, 19:25:24
I tried to establish a separate communication channel with the THZ according to the protocol "specification". But something goes wrong. On receiving 0x02 the THZ replies with 0x10. Any other requests (e.g. from the original heatpump monitor homepage) remain unanswered - no reply at all. Only if I send 0x02 0x10 0x03 the THZ replies with 0x10 0x02. But after acknowledging it with 0x10 there is no additional data provided. The serial port setup is as used by 00_THZ.pm (115200 bps, 8N1). Any ideas?

EDIT
I do not quite understand how it is possible that the original code by Robert uses link speed of 57600 and the fhem implementation runs at 115200. Is it related to newer firmware versions?
Some firmware versions use 57600, others 115200.

What the heatpump monitor page doesn't say: there's a timing window on 10ms ... 500ms. Within this time frame after having received the answer from THZ you have to send the next command, otherwise it will be rejected.

If you really want to play on this low level I'll add a shell script for RaspberryPi, which was my own starting point for communication to THZ. Just open a terminal window, e.g. using Putty, copy the script to anywhere on RasPi and execute it. You should find result data in the log file, which is defined in the script. And initially you may need to adjust the script a bit, e.g. baud rate. The result data is in hex of course, as mentioned by Robert Penz on his heatpumpMonitor page.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 26 November 2014, 21:31:26
I just wanted to try an alternative implementation. I already figured out that the timing is very important.

The protocol "specification" I referred to is the fhem code and Robert's findings. This is why I used quotes. ;-)

There is an interesting overview of CAN bus codes here (http://juerg5524.ch/data/ElsterTable.inc). Some of the codes are identical to the RS232/USB some of them aren't.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 27 November 2014, 01:03:37
Mythz was disconnected at the change from night to day settings. Had to perform setreading Mythz state opened for it to record again.
I like the new hystereses settings. Nothing I would change very often but play with it. Is it possible to get a decimal number for this? My hysteresis 1 setting is: 2.8 but it is displayed as 3
I also increased the asymmetry from 2 to 3 in the hope that when it gets really cold the LWZ would start early enough to heat to avoid the use of the booster. Thanks again immi for unlocking this for us!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 November 2014, 11:52:53
Zitat von: houseowner123 am 27 November 2014, 01:03:37
Mythz was disconnected at the change from night to day settings. Had to perform setreading Mythz state opened for it to record again.
I like the new hystereses settings. Nothing I would change very often but play with it. Is it possible to get a decimal number for this? My hysteresis 1 setting is: 2.8 but it is displayed as 3
I also increased the asymmetry from 2 to 3 in the hope that when it gets really cold the LWZ would start early enough to heat to avoid the use of the booster. Thanks again immi for unlocking this for us!

Yeaterday night, I couldn´t sleep... getting old or to much stress from work.
I wrote a fix for the devio.pm issue... I will upload this night

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 November 2014, 12:33:14
Zitat von: immi am 27 November 2014, 11:52:53
Yeaterday night, I couldn´t sleep... getting old or to much stress from work.
I wrote a fix for the devio.pm issue... I will upload this night

immi
Sounds like you meanwhile understand the root cause. Up to now I expected it to be an issue to be fixed in devio.pm. Or is it an expected behavior of devio.pm which you didn't know up to now, and therefore it hadn't been covered in 00_THZ.pm?

Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 November 2014, 12:36:30
Zitat von: houseowner123 am 27 November 2014, 01:03:37
My hysteresis 1 setting is: 2.8 but it is displayed as 3
I formatted some values for silimar reasons:
attr rg_thz valueFormat { inside_temp => '%0.1f °C', outside_temp => '%0.1f °C', Rel_humidity => '%0.1f %%', flow_temp => '%0.1f °C', return_temp => '%0.1f °C', dhw_temp => '%0.1f °C' }


Might work similarly in your case.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 November 2014, 13:03:23
Zitat von: willybauss am 27 November 2014, 12:33:14
Sounds like you meanwhile understand the root cause. Up to now I expected it to be an issue to be fixed in devio.pm. Or is it an expected behavior of devio.pm which you didn't know up to now, and therefore it hadn't been covered in 00_THZ.pm?
Willy
Expected behaviour... you can expect something only if the the depending modules are well documented...:)
I think I understand the issue which (very likely) is connected with the devio.pm.
But I am not 100% sure because I am only simulating it.
When you test the new version (if I decide to upload it this night) we will see.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 November 2014, 15:06:11
Zitat von: immi am 27 November 2014, 13:03:23
Expected behaviour... you can expect something only if the the depending modules are well documented... :)
that's right of course. In case of being caused by devio.pm the issue could also affect other modules. But since I have a pretty small configuration I didn't hear anything about such problems.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 November 2014, 20:02:00
Zitat von: houseowner123 am 27 November 2014, 01:03:37
Nothing I would change very often but play with it. Is it possible to get a decimal number for this? My hysteresis 1 setting is: 2.8 but it is displayed as 3....
v 0112 uploaded tomorrow you can upgrade
00_THZ.pm: bugfix for error caused by DevIo.pm 6980 status disconnected msg223569

I do not see your problem
I can change p21Hist1 also to 3.4 K and I visualize it correctly

-werbung-
one more thing non related to thz, justme1968 updated SVG.
http://forum.fhem.de/index.php?action=pm#msg30057
http://forum.fhem.de/index.php/topic,29233.msg223435.html#msg223435
I really like the flexibility e.g. I like the spiderchart.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 28 November 2014, 01:18:15
Thanks immi and willy. All it needed was a restart and the decimal number appeared in the hysteresis. Need to be more patient. ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 November 2014, 10:14:18
Zitat von: immi am 27 November 2014, 20:02:00
-werbung-
one more thing non related to thz, justme1968 updated SVG.
http://forum.fhem.de/index.php?action=pm#msg30057 (http://forum.fhem.de/index.php?action=pm#msg30057)
I really like the flexibility e.g. I like the spiderchart.
immi
Sorry, don't understand. The link shows me my personal impartation folder - but no new entries there  :-\ .
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 November 2014, 11:44:13
Zitat von: willybauss am 28 November 2014, 10:14:18
Sorry, don't understand. The link shows me my personal impartation folder - but no new entries there  :-\ .
editiert
http://forum.fhem.de/index.php/topic,29233.msg223435.html#msg223435
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 November 2014, 14:44:32
looks indeed interresting; not as a replacement for existing plots, but may be useful for different kind of plots I never thought about up to now  :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 November 2014, 20:49:10
hey guys,

sorry being absent in the last time... unfortunately there is absolutely no time for play'n round with fhem right now =(
i'm reading the discussion with greath delight to see what's growin out of the module :)

i'm trying to add all the news and updates within the, hopefully, stressless time around christmas.
if somebody wants to write an update for the wiki, just send it to me

markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 November 2014, 23:17:40
does anyone of you have trouble with sending emails out of fhem linux after last weekend's issue? for me the Debian sendEmail feature doesn't work anymore, even if started in terminal outside fhem. After having done lots of updates and installed possibly missing related packages the failure meanwhile ends up in
Nov 30 23:12:57 raspberrypi sendEmail[10901]: ERROR => TLS setup failed: SSL Version SSLv2 not supported error:00000000:lib(0):func(0):reason(0)

The command itself looks like
sendEmail -f '[SENDER]@t-online.de' -t '[ADDRESSEE]@t-online.de' -u 'Testsubject' -m 'Testtext' -s 'securesmtp.t-online.de' -xu '[LOGIN]@t-online.de' -xp '[PASSWORD]' -o tls=auto -vv


edit:
issue fixed by http://forum.fhem.de/index.php/topic,28612.msg223493.html#msg223493 (http://forum.fhem.de/index.php/topic,28612.msg223493.html#msg223493)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mlb am 02 Dezember 2014, 19:21:58
First of all - thank you for this great thread. I have been user of Stiebel LWZ403 (+Solar), for 3rd year now. Until now
I've been using excellent heatpumpMonitor from Robert, then I found FHEM and I really liked the idea. I installed a template configuration from Willy and it was rather  easy to get it working (Wille - thank you!  :) ). However - I found two issues with FHEM where heatpumpMonitor still is better at:

1. Charts generation speed. Yes I know Robert generated pictures  in the background and so they could be displayed instantly, but also Robert used database to store measurements - while in FHEM as I understand, each time a log file is being parsed and that makes it working really slow, even with a decent CPU. So my question would be - have you tried to solve this already? I have seen DB option for FHEM, but frankly I am too new to this subject to try it without having examples, and my German is rather poor to use other threads at this forum...

2. Display of negative values (like temperatures when chart is expected to display a filled area: the shaded part is always from the bottom of the chart, not from zero axis... and so it looks rather strange and confusing.

--
greetings to all,
Marek
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 02 Dezember 2014, 20:17:13
Hi Marek
happy that you like thz. The idea behing fhemTHZis not to make a better monitoring, but to actively integrate the heatpump in a complete home automatization like fhem.
I have several hints for you.

The first hint is the most efficient: with less money you achieve a better result investing no time.
With the other suggestions, you spend lot's of time, but you learn something or use your mind, which is a nice side-effect.
My preferred way, is to keep logfiles as small I can, storing only what I need.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 02 Dezember 2014, 20:41:05
Overclocking the RasPi to 1000MHz brought some more comfort to my system =)
Since Overclocking is no longer killing your guarantee on the RasPi it could be worth a try.

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mlb am 02 Dezember 2014, 21:52:58
Zitat von: immi am 02 Dezember 2014, 20:17:13


  • use a more powerfull fhem-server than a raspi
  • help to improve the SVG module; actually if you update to the last version you should find some improvents: rudolf and    justme1968 are very active on the module, which has potential 
  • keep logfiles small; store in logfile only what you need, not so frequently, and only if you have a variable has a change   
  • test the dblog 
  • generate periodically a plot as batch-job, look in the wiki, there was an example


Hi immi, thanks a lot for response and explanation.

Actually for my FHEM test instance I already use a regular server (this is my home server Ubuntu 14.10 with 4 disks as RAID , Asterisk, and couple of other services), having Intel CPU, (Haswell G1820,2*2.7 GHz, a nice processor). I planned to move FHMI to raspi after initial tests (as I already use raspi for other purposes) - but yes, I will try other hints you suggested and will let you know.

Before I found FHEM- I tried to use software from openremote.org, but Java is somehow too heavy for my purposes, and FHEM is just a direction I like better :)  I am not a developer, still - I can do simple things in Linux environment and from that perspective FHEM is more user-friendly.

Just as a question about my second point and drawing of negative temperature values - have you seen this before? Or maybe there might be  something wrong with my setup? I will try to attach a screenshot:

(http://i58.tinypic.com/o6d9c3.jpg)

... so the blue area that represents negative outside temperature - should rather be between 0 and temperature value, and not between the value and -10 :D
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 03 Dezember 2014, 10:22:13
Hi Marek,

Welcome to the forum! A few comments based on my experience: For me it looks like the bigger part of execution time is related to number of graphs shown in your charts. In the last few months I accidentally created THZ log files having >25MB per month. After having fixed the issue it is down to less than 10MB, but the time needed to create the charts doesn't decrease a lot. "Logging only if a variable has changed" might or might not work. If you log sGlobal only, you're logging lots of values in 1 single variable. So the chance that none of them changed is limited...

I've tested dblog months ago based on the assumption that getting the data out of a database should be faster than reading tons of log files. In fact it is not really faster. Additionally there where hurdles to overcome with the way 00_THZ represents the reading results: e.g. sGlobal shows multiple values in one single reading; so it doesn't make sense to put it into one single database entry, but you need to split them into single readings before logging them to the db.

If you succeed in "generate periodically a plot as batch-job" please let me/us know. I'm really interrested it it. It's not always necessary to have the last 5 minutes in the graphs, but a fast plot every hour could be sufficient in most cases.

For the negative values the solution could be to replace the Y axis from °C to Kelvin  ;) ... For me this never had been an issue, so I didn't even notive it up to now.

I assume you got my configuration example from a file I attached to a post months ago. In this case please check your fhem.log file. I assume there are tons of error messages caused by the failure notifies, e.g.

define Mythz.alarm_failure notify Mythz { if (((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]) > ReadingsVal("Mythz","number_of_faults_old","ERROR")) { DebianMail('MYEMAILADDRESS@t-online.de','Tecalor Mythz Alarm - ERROR','Fehlermeldung: '. $EVENT,'/mnt/fhem/Tecalor-Fehlermeldungen.txt');; fhem("setreading Mythz number_of_faults_old ". ((split ' ',ReadingsVal("Mythz","sLast10errors","ERROR"))[1]));; } }
attr Mythz.alarm_failure room Heizung


In my case the log file increased to >19MB within one day due to this topic. You need to replace all of the "ERROR" entries by 0, since fhem no more accepts them after one of the latest updates. So it should look like

define Mythz.alarm_failure notify Mythz { if (((split ' ',ReadingsVal("Mythz","sLast10errors",0))[1]) > ReadingsVal("Mythz","number_of_faults_old",0)) { DebianMail('MYEMAILADDRESS@t-online.de','Tecalor Mythz Alarm - ERROR','Fehlermeldung: '. $EVENT,'/mnt/fhem/Tecalor-Fehlermeldungen.txt');; fhem("setreading Mythz number_of_faults_old ". ((split ' ',ReadingsVal("Mythz","sLast10errors",0))[1]));; } }
attr Mythz.alarm_failure room Heizung


(same for all the other failure notifies of course)

Do you still know when I posted this configuration file? I'd like to update it there in order to not create trouble to new users.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: mlb am 03 Dezember 2014, 22:54:30
Thanks Willie, I will make necessary adjustments.

I downloaded your configuration from post you published on May 14: http://forum.fhem.de/index.php/topic,13132.msg168721.html#msg168721 (http://forum.fhem.de/index.php/topic,13132.msg168721.html#msg168721)

It was not working initially due to missing global definitions, but once I copied them from default fhem.cfg - it started working :) I had small issue with remote control for Samsung TV and also your Weather tab gives errors, but I have not investigated reasons for it yet, most likely I will just remove it.

I'm glad to inform my graphs are working blazing fast now! I simply removed all existing log files, applied your advice to log only changed values - and it is so much better now - a big thank you :D

I will look at background plots generation in a couple of days, after I have more data available in logs.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Dezember 2014, 22:00:20
In the last few days I dealed with the charting frontend (http://www.fhemwiki.de/wiki/Neues_Charting_Frontend) which looks pretty nice. Meanwhile it can handle file logs as well, so you can simply use it additionally to the "classic" web frontend without the need of additional db logging.

Advantages:Disadvantages:
I decided to stay with the "normal" UI normally, but use the charting frontend for deeper analysis occasionally. Since it doesn't need additional effort/data (beside the userReading) this seems to be a valuable solution.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 13 Dezember 2014, 19:36:02
Hallo an alle FHEM Nutzer,

seit ca. 1 Monat versuche ich die Anbindung meiner LWZ303i Wärmepumpe an FHEM bzw. an Heatpumpmonitor einzurichten.
Mein Problem ist die alte Firmware meiner LWZ (V2.06). Und soweit ich das im Fhemwiki gelesen habe, ist dieser Firmwarestand nicht mit der Konfiguration "00_THZ.pm" kompatibel. Mit meiner LWZ sieht der ausgelesene Datensatz wie folgt aus (hinter einigen Hex-Zahlen habe ich die Dezimalwerte angegeben):

001BFB Wahrscheinlich Header
00C5 Kollektor 19,7°C
0016 Aussen 2,2°C
0142 Vorlauf 32,2°C
0115 Rücklauf27,7°C
02D4 Heissgas 72,4°C
0162 Warmwasser 35,4°C
0000 Temp. Heizkreis 2 (nicht vorhanden)
00E5 Kompressor 22,9°C
FFC9 Verdampfer -5,5°C
0142 Verflüssiger 32,2°C
19
1C
00
00
99
CE
00
00
11 Drehzahl Fortlüfter 17
00
0014 ?Aussentemp. gedämpft 2,0°C
00
00
00
00
00
00
00
01
00
1003 footer

Hat den vielleicht schon jemand eine ältere LWZ/THZ mit V2.06 mit FHEM im Betrieb?
Es wäre für mich kein Problem, wenn jemand lieber in Englisch antworten möchte.
Vielen Dank.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Dezember 2014, 21:29:22
Du solltest die ganze Antwort der LWZ hier einstellen. Idealerweise hängst Du das Mythz.log File an einen Beitrag an.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 13 Dezember 2014, 23:27:41
Hier ein Beispiel aus der LOG-Datei:

2014.12.05 15:09:43 2: Mythz/RAW: 1003
2014.12.05 15:11:37 2: Mythz/RAW: 0073FB00C5
2014.12.05 15:11:37 2: Mythz/RAW: 001F0102
2014.12.05 15:11:37 2: Mythz/RAW: 010401
2014.12.05 15:11:37 2: Mythz/RAW: 2D01C100
2014.12.05 15:11:37 2: Mythz/RAW: 0000E300
2014.12.05 15:11:37 2: Mythz/RAW: B400FD
2014.12.05 15:11:37 2: Mythz/RAW: 091C00
2014.12.05 15:11:37 2: Mythz/RAW: 0000C8
2014.12.05 15:11:37 2: Mythz/RAW: 000000
2014.12.05 15:11:37 2: Mythz/RAW: 00001A
2014.12.05 15:11:37 2: Mythz/RAW: 000000
2014.12.05 15:11:37 2: Mythz/RAW: 000000
2014.12.05 15:11:37 2: Mythz/RAW: 000000
2014.12.05 15:11:37 2: Mythz/RAW: 1003
2014.12.05 15:12:25 2: Mythz/RAW: 00FAF4001EFE
2014.12.05 15:12:25 2: Mythz/RAW: 3F0104FFFF
2014.12.05 15:12:25 2: Mythz/RAW: EA010201
2014.12.05 15:12:25 2: Mythz/RAW: 1B010300
2014.12.05 15:12:25 2: Mythz/RAW: 010001
2014.12.05 15:12:25 2: Mythz/RAW: 011C00
2014.12.05 15:12:25 2: Mythz/RAW: 640100
2014.12.05 15:12:25 2: Mythz/RAW: 000000DC01
2014.12.05 15:12:25 2: Mythz/RAW: 670000
2014.12.05 15:12:25 2: Mythz/RAW: 00DD0000
2014.12.05 15:12:25 2: Mythz/RAW: 0000F41003
2014.12.05 15:14:43 2: Mythz/RAW: 0063FB00C5001E01
2014.12.05 15:14:43 2: Mythz/RAW: 020103012A
2014.12.05 15:14:43 2: Mythz/RAW: 01C000
2014.12.05 15:14:43 2: Mythz/RAW: 0000E300
2014.12.05 15:14:43 2: Mythz/RAW: B400FC
2014.12.05 15:14:43 2: Mythz/RAW: 001C00
2014.12.05 15:14:43 2: Mythz/RAW: 0000C800
2014.12.05 15:14:43 2: Mythz/RAW: 000000
2014.12.05 15:14:43 2: Mythz/RAW: 001A000000
2014.12.05 15:14:43 2: Mythz/RAW: 00000000
2014.12.05 15:14:43 2: Mythz/RAW: 000010
2014.12.05 15:14:43 2: Mythz/RAW: 03
2014.12.05 15:16:37 2: Mythz/RAW: 006AFB00
2014.12.05 15:16:37 2: Mythz/RAW: C5001E0102
2014.12.05 15:16:37 2: Mythz/RAW: 0101012A
2014.12.05 15:16:37 2: Mythz/RAW: 01C000
2014.12.05 15:16:37 2: Mythz/RAW: 0000E300
2014.12.05 15:16:37 2: Mythz/RAW: B500FB08
2014.12.05 15:16:37 2: Mythz/RAW: 1C000000
2014.12.05 15:16:37 2: Mythz/RAW: C80000
2014.12.05 15:16:37 2: Mythz/RAW: 0000001B
2014.12.05 15:16:37 2: Mythz/RAW: 000000
2014.12.05 15:16:37 2: Mythz/RAW: 0000000000
2014.12.05 15:16:37 2: Mythz/RAW: 001003

Um 15:11:37 wird ein Datensatz ausgelesen (14 Zeilen). Die einzelnen Datensätze kann man daran erkennen, dass ein Datensatz immer mit "1003" endet. Nach genau 5 Minuten (Um 15:16:37) wird gemäß eingestelltem Zyklus der nächste Datensatz eingelesen. Und die Inhalte der Datensätze passen soweit auch zu den Anzeigen meiner LWZ (also sind es wohl keine fehlerhaften Daten).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Dezember 2014, 10:02:47
Peter
it is a good news. It works very well with your very old firmware.
Nevertheless some small (or big) fix has to be done to the THZ module in order to support yuour old firmware.
please use verbose 5.
In this way, all debug info will be logged.
Then post the logfile as file, because it will be huge.
best regards
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 14 Dezember 2014, 11:58:48
Hallo.
So wie ich das verstehe, muss schon einiges im THZ-Modul geändert werden, da zum Einen der Datensatz eine andere Länge hat und zum Anderen der Aufbau des Datensatzes sich komplett unterscheidet. Im HeatpumpMonitor von Robert Penz gibt es deswegen auch verschiede Module.
Im Anhang findet ihr den aktuellen Auszug aus der LOG-Datei nach der Umschaltung auf "verbose 5".
Vielen Dank im Voraus.
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Dezember 2014, 12:29:47
Hi Peter
there are several things to do
at first I want to get rid of
2014.12.14 11:43:08 2: Mythz/RAW: 0000000000
2014.12.14 11:43:08 5: Mythz/RAW: 16000000
2014.12.14 11:43:08 2: Mythz/RAW: 16000000
2014.12.14 11:43:08 5: Mythz/RAW: 000000
2014.12.14 11:43:08 2: Mythz/RAW: 000000

these are comunication problems because your interface is very slow

try to uncomment line 679 from
#select(undef,undef,undef,0.010);
to
select(undef,undef,undef,0.010);

and restart fhem, then test and post again the logfile as file

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 14 Dezember 2014, 17:46:43
Hallo Immi,

habe sofort deinen Tipp mit "select(undef,undef,undef,0.010);" ausprobiert.
Nach dem "update 00_THZ.pm" und "shutdown restart" im FHEM habe ich mit Erstaunen festgestellt,
dass zum ersten Mal die Temperaturwerte meiner LWZ angezeigt wurden.
WOW! Dachte ich zuerst. Nach einer längeren Zeit hat sich dann herausgestellt, dass diese Werte nicht mehr aktualisiert werden.
Ein Reboot meines Rasppi hat auch keine Besserung gebracht.
Dann habe ich die Kommunikation im FHEM von Serial2Net auf /dev/ttyUSB0 umgestellt. Man muss hier noch dazu sagen, dass meine alte LWZ nur mit 9600kBps kommuniziert. Im THZ-Modul habe ich deswegen überall die Baudrate auf 9600 geändert.
Den aktuellen Auszug der LOG-Datei und noch zwei Bilder aus FHEM habe ich im Anhang beigefügt.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 14 Dezember 2014, 18:11:59
Probiere mal, was sich tut, wenn Du im ersten Bild bei FanSelectorDay auf eine der Zahlen tippst. Eigentlich sollte dann die Anzahl der ausgemalten Flügel im Symbol sich ändern, und die Lüfterdrehzahl ebenfalls. Wenn das klappt, hast Du eine bidirektionale Verbindung, die prinzipiell funktioniert.

Lass mich raten: Du hast kein 2. Display im Wohnzimmer? Deshalb meldet die Anlage 0% Luftfeuchtigkeit (das Display in der Anlage hat keinen Feuchtesensor eingebaut), die über das UserReading auf 11,5% korrigiert werden. Mit der Innentemperatur dürfte es sich ähnlich verhalten.

Die restlichen Werte im 1. Bild sehen vernünftig aus, bis auf FanSelectorPassiveCooling. Den liefert die Anlage vermutlich nicht mit.

Bei näherer Betrachtung des Logfiles frage ich mich allerdings, woher fhem die angezeigten Werte überhaupt nimmt. Und die Kommunikation scheint auch noch instabil zu sein. Dazu muss immi sich äußern. Er ist der Spezialist für sowas.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 14 Dezember 2014, 19:14:42
Habe jetzt die verschiedenen FanSelector-Stufen angeklickt. Die angezeigte Anzahl der Blätter ändert sich auch. An der LWZ passiert aber nichts.
Ich habe noch die alte LWZ mit Tasten-Bedienteil (kein Drehrad). Meine LWZ hat soweit ich weiß keine Feuchtigkeitsmessung. Die Innentemperatur ist über einen Fühler im Wohnzimmer angeschlossen und der Wert schein zu stimmen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Dezember 2014, 20:05:31
as I see from logfile you are one step further but still far from endline.
increase the delay and change line 679 to
select(undef,undef,undef,0.050);


one more question: do you have some "at" in your config like at command atMythzGlobal as +*00:05:00 {fhem "get Mythz sGlobal","1";return()}

please remove all of  them and use instead the interval attribute:
attr Mythz interval_sGlobal 300

then restart, and post the logfile
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 14 Dezember 2014, 21:13:40
Ich habe soweit alles wie von dir empfohlen umgesetzt. Auf den ersten Blick ist leider keine Besserung zu sehen.
Im Anhang wie immer ein aktueller Auszug der LOG-Datei.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Dezember 2014, 23:27:25
Hi Peter
the communication is still an issue. I want to read sGlobal without issues. 
test this version
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 15 Dezember 2014, 08:23:36
Zitat von: peter456 am 14 Dezember 2014, 19:14:42
Die Innentemperatur ist über einen Fühler im Wohnzimmer angeschlossen und der Wert schein zu stimmen.
Das erklärt den vernünftig aussehenden Wert für die Innentemperatur. In der Konfiguration gibt es ein userReading für insideTemp, bei dem ein Offset von 0.6° gemacht wird, weil bei mir der Innentemperaturfühler ungenau ist. Hier kannst Du Deinen Innentemperaturfühler-Messwert justieren.

Das userReading für die Luftfeuchtigkeit (ebenfalls mit Offset-Korrektur) kannst Du komplett löschen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 15 Dezember 2014, 19:08:25
Hallo Immi,

nachdem ich dein neues THZ-Modul übertragen hatte und "update 00_THZ.pm" sowie "shutdown restart" durchgeführt hatte, waren die Temperaturwerte meiner LWZ wieder aktualisiert worden. Leider bleibt es wieder bei der einmaligen Aktualisierung. Die Werte ändern sich auch nicht wenn ich meinen Rasppi oder FHEM neu starte.
Den aktuellen Auszug der LOG-Datei und noch ein Bilder aus FHEM habe ich im Anhang beigefügt.

vielen Dank für diene Hilfe
Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Dezember 2014, 19:20:40
Zitat von: peter456 am 15 Dezember 2014, 19:08:25
übertragen hatte und "update 00_THZ.pm" sowie "shutdown restart" durchgeführt hatte, waren die Temperaturwerte meiner LWZ
Hi Peter
I have not told you to use "update 00_THZ.pm" (version 0.112), but the version attached yesterday at 23:27:25 (version v.0.113)
you can check if you type version.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 15 Dezember 2014, 19:50:59
Hallo immi,

ich dachte man muss "update 00_THZ.pm" bei jeder Aktualisierung des THZ-Moduls ausführen.
Soll ich nur deine neue Datei von Gestern  23:27:25 (version v.0.113) nach "/home/pi/fhem/FHEM" übertragen und ein Reboot von FHEM durchführen. Ich bin noch Anfänger was Linux und FHEM betrifft.
Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Dezember 2014, 19:53:21
Zitat von: peter456 am 15 Dezember 2014, 19:50:59

Soll ich nur deine neue Datei von Gestern  23:27:25 (version v.0.113) nach "/home/pi/fhem/FHEM" übertragen und ein Reboot von FHEM durchführen. Ich bin noch Anfänger was Linux und FHEM betrifft.
Gruß
Peter
genau
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 15 Dezember 2014, 20:14:16
Habe soweit alles neu gemacht. Jetzt habe ich keinen Zugriff auf FHEM. Der Browser zeigt "Die Seite kann nicht angezeigt werden". Ein Reboot des Rasppi hat auch nichts gebracht. Jetzt weiß ich auch nicht weiter.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Dezember 2014, 20:26:39
Peter
version 0.113 should not block fhem, I tested it.
restore your system and try again

I will upload v0.113 to the repository now
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 15 Dezember 2014, 20:41:54
Ich habe bis jetzt keine Sicherungen erstellt. Das könnte jetzt etwas dauern bis es wieder läuft.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Dezember 2014, 00:05:46
Zitat von: peter456 am 15 Dezember 2014, 20:41:54
Ich habe bis jetzt keine Sicherungen erstellt. Das könnte jetzt etwas dauern bis es wieder läuft.
Wenn man eine Datei ungewissen Inhalts zum testen bekommt, dann überschreibt man nicht einfach die bekannt gute Datei mit etwas fragwürdigem, sondern man kopiert sie erst woanders hin, oder man benennt sie um. Man kann doch nicht den Ast absägen, auf dem man sitzt.  :-X
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 Dezember 2014, 07:58:32
Aller Anfang ist schwer :)
Aber wenn Du ein "Update" gemacht hast sollte sich das backup unter /opt/fhem/backups befinden...
daraus koenntest Du die alte Version zurueck holen.

Gruß
Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Dezember 2014, 08:10:05
Update machen, wenn FHEM gar nicht startet? Ich würde erst mal versuchen, die kaputte (?) Datei aus dem FHEM Verzeichnis zu entfernen - das heißt woanders hin verschieben, nicht löschen!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 16 Dezember 2014, 09:13:37
Manchmal muss man durch Fehler dazu lernen. :(
Aber ich glaube mein FHEM hat ein allgemeines Problem.
Beim manuellen Starten von FHEM hat mein Rasppi gestern angezeigt,
dass die Datei fhem.cfg nicht vorhanden wäre.
Ich muss heute Abend meine Fehlersuche fortsetzen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 16 Dezember 2014, 19:42:02
Hallo Immi,

mein FHEM läuft wieder. Aus irgendeinem Grund war die Datei fhem.cfg nicht im Verzeichnis /opt/fhem sondern im Verzeichnis /opt.
Danach habe ich das ältere THZ-Modul (V0.112) wieder eingespielt und später die neue Version (V0.113) nach /home/pi/fhem übertragen. Ich hoffe ich habe alles richtig gemacht. Die Temperaturwerte meiner LWZ wieder nicht aktualisiert.
Den aktuellen Auszug der LOG-Datei aus FHEM habe ich im Anhang beigefügt.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 Dezember 2014, 19:59:17
Peter
the log you have snt me is with v113? are you sure?
you can check it like in the image

if it is still v0112 then make a fhem update: I uploaded the last version in the meanwhile.

if it is v0113 then try
get Mythz sFirmware


and
get Mythz sGlobal
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 16 Dezember 2014, 20:38:57
Hallo Immi,

tut mir leid, du hattest recht. Die Version war noch bei V0.112. Jetzt muss aber alles stimmen (siehe Bild).
Auf die Anfrage Firmware bekomme ich "version: 2.06".
Auf die Anfrage sGlobal bekomme ich "010016FB00C5001901070103012101A2000000E3008A00FE001C000000C900000000001B00
msg2 WInterface max repeat limited to 15"

Den aktuellen Auszug der LOG-Datei aus FHEM habe ich im Anhang beigefügt.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 16 Dezember 2014, 20:46:38
Zitat von: peter456 am 16 Dezember 2014, 20:38:57
Auf die Anfrage sGlobal bekomme ich "010016FB00C5001901070103012101A2000000E3008A00FE001C000000C900000000001B00
msg2 WInterface max repeat limited to 15"

excellent!!
I will prepare another version for tomorrow, I know what to do now
edit17.12: you can update to v0.114

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 16 Dezember 2014, 20:47:54
Vielen Dank. :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 16 Dezember 2014, 21:12:14
good job :)
gonna update the wiki as soon as possible.

best
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Dezember 2014, 17:51:10
Hi Peter
did you have time to test v0114?

I would like to see the logfile.
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 19:15:14
Hallo immi, ich wußte nicht dass die Datei schon fertig ist. Wo kann ich diese downloaden?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Dezember 2014, 19:42:26
i uploaded 2 days ago
just update
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 20:24:18
Hallo Immi,

Das update hat funktioniert. V0.114 wird im FHEM angezeigt.
Auf die Anfrage Firmware bekomme ich "version: 2.06".
Auf die Anfrage sGlobal bekomme ich "outsideTemp: 10.2 flowTemp: 26.5 returnTemp: 23 hotGasTemp: 28.7 dhwTemp: 43.4 flowTempHC2: 0 evaporatorTemp: 16.2 condenserTemp: 24.6 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 1 boosterStage3: 1 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 1 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 0 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 5273.6 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 25088 mainVentilatorSpeed: 0 outside_tempFiltered: 0 relHumidity: 0 dewPoint: 0 P_Nd: 0 P_Hd: 0 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: 19.7 insideTemp: 23"
Den aktuellen Auszug der LOG-Datei aus FHEM habe ich im Anhang beigefügt.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Dezember 2014, 20:51:20
the communication looks very well, not perfect, but ok.
Now we have to work on the functionality.
I strongly suggest not to try to write back to the heatpump. The registers in your old firmware could be different.

The first thing to be fixed is the interpretation of sGlobal: Look at line 992 to 1012: here there is the interpretation of the register for newer firmware.
It would be great if you could tell me how your old firmware sGlobal is organized.
e.g. from your logfile  0100A5FB00C50067010700DC011101B2000000E700AD00F3001C000000CE0000000000630000000000000000001003
Then I can implement it, and we loot at another status register... sHC1, sHC2, sDHW, sSol...
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 18 Dezember 2014, 21:04:28
10.2°C outside temperature and booster stage 3 is on? Can this be true? Only for unsanierter Altbau or there is something really wrong with the settings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 21:11:04
Hallo immi,

ich werde versuchen die Daten aus sGlobal zu interpretieren.
Momentan stimmen die ausgelesenen Werte noch nicht ganz. Natürlich ist auch der Heizstab aus. Momentan ist die LWZ aus.
Aber das macht mich schon mal glücklich dass die Kommunikation funktioniert.
Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 21:51:21
Hallo immi,

hier sind die aktuellen Werte aus sGlobal:

0100C3FB Header
00C5 collector_temp, Kollektortemp. (19,7°C)
0069 outside_temp, Außentemp. (10,5°C)
00EB flow_temp, Vorlauftemp. (23,5°C)
00DD return_temp, Rücklauftemp. (22.1°C)
00F5 hot_gas_temp, Heißgastemp. (24.5°C)
01AF dhw_temp, Speichertemp. (43.1°C)
0000 flow_temp_hc2, Vorlauftemp.-HK2 (0°C)
00E9 compressor_temp (23,3°C)
00B4 evaporator_temp, Verdampfertemp. (18.0°C)
00E7 condensor_temp, Verflüssigertemp. (23.1°C)
0004 ?
37 extr_speed_set, Drehzahl Ablüfter Soll (55)
3A vent_speed_set, Drehzahl Zulüfter Soll (58)
00 expel_speed_set, Drehzahl Fortlüfter Soll (0)
CE ?
00 extr_speed_actual, Drehzahl Ablüfter Ist (0)
00 vent_speed_actual, Drehzahl Zulüfter Ist (0)
00 expel_speed_actual, Drehzahl Fortlüfter Ist (0)
00 ? rel_humidity, Rel. Feuchte,
0065 outside_temp_filtered, Außentemp. gefiltert (10,1°C)
000000000000000000 ?
1003 footer

Reicht das so aus?
Es wäre zwar schön wenn ich auch die Werte zur LWZ schreiben könnte, ist aber für mich nicht ganz wichtig. Wichtiger wäre die Anzeige und die Aufzeichnung der aktuellen Werte.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Dezember 2014, 22:11:37
Zitat von: peter456 am 18 Dezember 2014, 21:51:21
Es wäre zwar schön wenn ich auch die Werte zur LWZ schreiben könnte, ist aber für mich nicht ganz wichtig. Wichtiger wäre die Anzeige und die Aufzeichnung der aktuellen Werte.

Geduld Peter

>>hier sind die aktuellen Werte aus sGlobal:
this means that up to "00E7 condensor_temp" old and new firmware are the same.... then start the difference.

and I think your explanation has a problem
extr_speed_set=55 and extr_speed_actual=0
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 22:16:35
Bezüglich der Werte "extr_speed_set=55 and extr_speed_actual=0" bin ich mir auch unsicher.
Das sind auch teilweise Informationen dabei, die ich aus dem Internet habe.  Die Messwerte habe ich aber mit meiner LWZ verglichen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 18 Dezember 2014, 22:21:20
Vielleicht helfen dir die Informationen aus dem Modul des HeatpumpMonitors von Robert Penz.
Dieses Modul (siehe Anhang) extra für die alte Firmware 2.06 erstellt worden.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Dezember 2014, 23:08:04
Peter
do not change approach: go on like you did « Antwort #1019 am: Heute um 21:51:21 »

get sGlobal
look in the logfile and search for the raw-data
go in the basement and look in the heatpump for the 6 ventilation values (3xSoll und 3xIst)

post what you found out.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 Dezember 2014, 19:10:40
Hi Peter
In the meanwhile that you try to decode register sGlobal for the old firmware, i uploaded v0115

I implemented the "Informationen aus dem Modul des HeatpumpMonitors von Robert Penz". All non identified parts will receive value "n.a."

you can activate the function for the old firmwareby
1) updating THZ-fhem to v0115
2) adding to confing file following new attribute
attr Mythz firmware 2.06

without the attribute the module behaves as usual
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 19 Dezember 2014, 21:31:26
Hi Immi,

ich habe nochmals versucht die Parameter "extr_speed_set=55 and extr_speed_actual=0" nachzuvollziehen.
Die Anzeigen der Lüfter stimmen mit den Anzeigen meiner LWZ überein.
Hier meine Ergebnisse:
0100C3FB Header
00C5 collector_temp, Kollektortemp. (19,7°C)
0069 outside_temp, Außentemp. (10,5°C)
00EB flow_temp, Vorlauftemp. (23,5°C)
00DD return_temp, Rücklauftemp. (22.1°C)
00F5 hot_gas_temp, Heißgastemp. (24.5°C)
01AF dhw_temp, Speichertemp. (43.1°C)
0000 flow_temp_hc2, Vorlauftemp.-HK2 (0°C)
00E9 compressor_temp (23,3°C)
00B4 evaporator_temp, Verdampfertemp. (18.0°C)
00E7 condensor_temp, Verflüssigertemp. (23.1°C)
0004 ?
37 extr_speed_set, Drehzahl Ablüfter Soll (55%) (LWZ-Anzeige A11 Steuerprozente Zulüfter)
3A vent_speed_set, Drehzahl Zulüfter Soll (58%) (LWZ-Anzeige A12 Steuerprozente Ablüfter)
00 expel_speed_set, Drehzahl Fortlüfter Soll (0%) (LWZ-Anzeige A13 Steuerprozente Fortlüfter)
CE ?
1F extr_speed_actual, Drehzahl Ablüfter Ist (31) (LWZ-Anzeige A14 Drehzahl Zulüfter)
1D vent_speed_actual, Drehzahl Zulüfter Ist (29) (LWZ-Anzeige A15 Drehzahl Ablüfter)
00 expel_speed_actual, Drehzahl Fortlüfter Ist (0) (LWZ-Anzeige A16 Drehzahl Fortlüfter)
00 ?
0065 outside_temp_filtered, Außentemp. gefiltert (10,1°C)
000000000000000000
1003 footer

Mehr Informationen kann ich momentan nicht liefen.

Dein Update auf V0.115 habe ich durchgeführt. Leiter wird auch nach dem "shutdown restart" die Version V0.114 im FHEM angezeigt.
Das Attribut  "attr Mythz firmware 2.06" habe ich eingefügt, aber solange die Version 0.115 nicht angezeigt wird, bringt das wahrscheinlich nichts.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 19 Dezember 2014, 23:28:58
Zitat von: peter456 am 19 Dezember 2014, 21:31:26

Dein Update auf V0.115 habe ich durchgeführt. Leiter wird auch nach dem "shutdown restart" die Version V0.114 im FHEM angezeigt.
Das Attribut  "attr Mythz firmware 2.06" habe ich eingefügt, aber solange die Version 0.115 nicht angezeigt wird, bringt das wahrscheinlich nichts.

I just uploaded v0.116 with your last information.
It takes several hours before you can update. you can try to update tomorrow.

In the meanwhile you can give me feedback on other registers:
get Mythz sHC1
get Mythz sHC2
get Mythz sDHW
get Mythz sSol
get Mythz sLast10errors
get Mythz sHistory

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 20 Dezember 2014, 11:12:52
Hallo,

das Update auf V0.116 hat heute funktioniert.
Hier die gewünschten Werte:

get Mythz sHC1 => outsideTemp: 3.2 x08: 51.4 returnTemp: 26.6 integralHeat: -58 flowTemp: 31.4 heatSetTemp: 27.5 heatTemp: 28 seasonMode: winter integralSwitch: 100 opMode: normal roomSetTemp: 22

get Mythz sHC2 => outsideTemp: 3.2 returnTemp: 26.6 vorlaufTemp: 0 heatSetTemp: 29.8 heatTemp: 26.6 stellgroesse: -100 seasonMode: winter opMode: normal

get Mythz sDHW => dhw_temp: 39.9 outside_temp: 3.2 dhw_set_temp: 36 comp_block_time: 0 x20: 4376 heat_block_time: 2728 x28: 2 x32: 2 x36: 31499

get Mythz sSol => 01031A161003  msg2 command not known  (meine LWZ hat kein Solar)

get Mythz sLast10errors => number_of_faults: 1 fault0CODE: 0 fault0TIME: 120:39 fault0DATE: 87.07 fault1CODE: 0 fault1TIME: 0 fault1DATE: 0 fault2CODE: 0 fault2TIME: 0 fault2DATE: 0 fault3CODE: 0 fault3TIME: 0 fault3DATE: 0

get Mythz sHistory => compressorHeating: 897 compressorCooling: 897 compressorDHW: 10159 boosterDHW: 3536 boosterHeating: 0  (ich denke nicht das diese Werte stimmen)


Den aktuellen Auszug der LOG-Datei aus FHEM habe ich im Anhang beigefügt.
Mein provisorisch eingerichteter Plot der Außentemperatur funktioniert schon seit gestern. :)

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Dezember 2014, 18:31:31
Hi Peter
It does not look bad, you have done 50% of the work for the old firmware 2.06
If you want to modify the decoding  of sHC1, sHC2, sDHW or sSol...you have to tell me exactly how it should look like. Same game as sGlobal.
If you are happy, we can go on with all other registers, like
get Mythz p01RoomTempDayHC1   
get Mythz p07FanStageDay
get Mythz pOpMode

p.s. Pay attention to sLast10errors. Your heatpump saved something, maybe an error. Find out on the heatpump which error it is.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 20 Dezember 2014, 20:52:37
Hallo Immi,

ich bin jetzt schon begeistert und zufrieden mit dem was hier im Forum innerhalb weniger Tage erreicht wurde.
Vielen herzlichen Dank an dich und alle anderen hier.
Ich kann jetzt schon alle für mich wichtigen Daten der Wärmepumpe überwachen (siehe Anhang).
Wenn du Lust an der Weiterennwicklung dieser alten Firmware hast, bin ich auch bereit dir die notwendigen Daten zu liefern.

Hier weitere Daten:
get Mythz p01RoomTempDayHC1  => 380B0852033E7F01033E034D7F01 °C
get Mythz p07FanStageDay => 6A0A010046000000A00078
get Mythz Popmode => 6A0A010046000000A00078

Im Speicher der Wärmepumpe ist aktuell 1 Fehler gespeichert: Fehlernummer 23, Uhrzeit Fehler 18:39, Datum Fehler 802.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 20 Dezember 2014, 22:48:33
Sieht schon mal ganz gut aus. Die Warmwasserkurve ist etwas merkwürdig, das wird wohl an der Regelung der alten Firmware liegen. Mehr sieht man, wenn Daten mehrerer Tage vorhanden sind.

Datum Fehler 802 klingt komisch ==> Februar 2008, oder 8. Februar  ???

Ich habe mal eine Datei mit Fehlerinformationen angehängt, die ich dem Installationsmanual entnommen habe.

@immi:
Would it make sense to have this list of error codes accessible via fhem UI? I don't know how this could be realized, but I could be the sponsor for the text. If it's needed in English language I could try to download an English version of the installation manual and grab the text from there. But I believe most of the users would prefer the German version.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 20 Dezember 2014, 23:31:18
Zitat von: willybauss am 20 Dezember 2014, 22:48:33
@immi:
Would it make sense to have this list of error codes accessible via fhem UI?
hi wily
Do you mean errorcode name
ZitatFehler 23: Fehler Verfluessigertemperaturfuehler
or errorcode text/explanation?
ZitatDer Verdichter wird abgeschaltet. Pruefen Sie den Kondensatablauf. Eventuell hat der Schwimmerschalter
am Boden des Kaelteaggregats geschaltet.

I do not know what it makes sense: some ideas
For sure both can be documented in  the fhemwiki. If you give engl. and german to Markus, he can upload.
I could also easily implement in fhem some kind of conversion of errorcodename, like I do for weekdays line 295....
Or I could link a chapter in the wiki....
or??

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 21 Dezember 2014, 09:21:07
Zitat von: immi am 20 Dezember 2014, 23:31:18
If you give engl. and german to Markus, he can upload.
I could also easily implement in fhem some kind of conversion of errorcodename, like I do for weekdays line 295....

Conversion of errorcodename would be the most satisfying for users i think.
Sure i can add to the wiki :)

Markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 21 Dezember 2014, 10:45:07
Hi

when you talk about errors, i missed an errorcode for the air filter. there is an icon on the display to change the filter, but FHEM (THZ) didn't tell me something about this issue.

It would be great to trigger to this event with a push notification :-)

Has anyone an idea???

THX

Kai
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Dezember 2014, 10:53:01
I agree with Markus. So I'll try to get the English version of the installation manual and extract the error descriptions soon.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Dezember 2014, 11:05:08
Zitat von: firebal301 am 21 Dezember 2014, 10:45:07
Hi

when you talk about errors, i missed an errorcode for the air filter. there is an icon on the display to change the filter, but FHEM (THZ) didn't tell me something about this issue.

It would be great to trigger to this event with a push notification :-)

Has anyone an idea???

THX

Kai
This icon shows up sometimes, sometimes not. The THZ simply checks for the needed RPM's of the fans when it powers up (e.g. after having changed the filters); later on the icon shows up as soon as the RPM values increased by a specific percentage. So if you had to switch off your THZ for any other reason beside filter change, the initial value is lost. Therefore I do not rely on this icon any more. I simply have a reminder in my smartphone to change/clean the filters every 3 months. Additionally I have small filters in the rooms at the airflow outlets. These filters are black, the frame is white. As soon as the filters turn to light grey I know that there's a lot of dirt on them.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 21 Dezember 2014, 11:35:40
btw: owners of the SOL version might need to take care about an additional filter:
if the fresh air for the ventilation enters your THZ via the separate tube at the THZ's back side (the mostly used, cheaper solution is getting the fresh air together with the air for the compressor through the big oval air input on back top side of the THZ) you have to face the fact, that there's an additional heat exchanger directly after the pipe's connection to the THZ's air inlet. This heat exchanger is intended to warm up the fresh air in order to prevent glaciation of the "Kreuz-Gegenstrom-Wärmeaustauscher". And in older models of the THZ...SOL version there's no filter before that heat exchanger. Even the installation manual (2009-version) doesn't mention this fact. The 2014 version of the installation manual describes clearly (chapter 14.2) , that there is an additional filter behind the "Kreuz-Gegenstrom-Wärmeaustauscher" for that reason, see attached screen shot from the manual.

In my THZ I can see that not just the 2009's manual, but even the whole 2009's heatpump itself is missing this filter. The attached picture shows you a look at the input side of this heat exchanger when I removed the pipe for the first time, approx. 1 1/2 years after start using the THZ. My solution was, to add another filter at the other end of this pipe (where the fresh air enters the pipe outside of the house).

edit:
Meanwhile I noticed that the 2014 version of the installation manual now requests an external filter box in the imput pipe, see screenshot_2.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Dezember 2014, 11:56:44
Zitat von: willybauss am 21 Dezember 2014, 11:05:08
This icon shows up sometimes, sometimes not. The THZ simply checks for the needed RPM's of the fans when it powers up (e.g. after having changed the filters); later on the icon shows up as soon as the RPM values increased by a specific percentage. So if you had to switch off your THZ for any other reason beside filter change, the initial value is lost. Therefore I do not rely on this icon any more. I simply have a reminder in my smartphone to change/clean the filters every 3 months. Additionally I have small filters in the rooms at the airflow outlets. These filters are black, the frame is white. As soon as the filters turn to light grey I know that there's a lot of dirt on them.
Hi Kay
I agree with Willy, do not use the filter change warning, which is unereliable.
You can build up a reminder every 1/2 year, or monitor VentilatorPower/VentilatorSpeed of sGlobal.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 21 Dezember 2014, 19:59:57
Question: How can one put in "like in the Dashboard" a button that is pushed and from there a counter is counting backwards 6 months and then presents a message "chang filter" until this button is pushed again? I agree with immi that the LWZ counter is totally flawed and FHEM would be more reliable in that sense. Does anyone an idea how to implement that codewise, a 182 day counter?

@willy: A month ago I change the room influence setting to 80:20 and I see remarkable improvements when there are sudden temperature changes. The heating is totally off now when the fireplace is on until noon the next day. Energy consumption is a lot better for me than on 50:50 setting. What is your experience?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 21 Dezember 2014, 20:51:48
Zitat von: houseowner123 am 21 Dezember 2014, 19:59:57
Question: How can one put in "like in the Dashboard" a button that is pushed and from there a counter is counting backwards 6 months and then presents a message "chang filter" until this button is pushed again? I agree with immi that the LWZ counter is totally flawed and FHEM would be more reliable in that sense. Does anyone an idea how to implement that codewise, a 182 day counter?
I use google calendar, which I connected to the fhem with the calendar module.
I am not a great frontend guy, I would suggest  that you post the question in the frontend or automatization (depending on how you formulate the question) as stad-alone-3d.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 21 Dezember 2014, 22:18:01
Hi there,

Is there a description for the various values in sGlobal (e.g. rvuRelease, mixerOpen, mixerClosed, signalAnode, STB)? I would like to understand how those names were created and what is their physical meaning.

Cheers!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 00:27:44
Zitat von: peter456 am 20 Dezember 2014, 20:52:37
Hier weitere Daten:
get Mythz p01RoomTempDayHC1  => 380B0852033E7F01033E034D7F01 °C
get Mythz p07FanStageDay => 6A0A010046000000A00078
get Mythz Popmode => 6A0A010046000000A00078

Im Speicher der Wärmepumpe ist aktuell 1 Fehler gespeichert: Fehlernummer 23, Uhrzeit Fehler 18:39, Datum Fehler 802.

Peter
you should really do not try to write back (set) to the heatpump.
the answer you posted shows the register are really different.
I am considering to disable write back for old firmwares.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 00:42:16
Zitat von: godmorgon am 21 Dezember 2014, 22:18:01

Is there a description for the various values in sGlobal (e.g. rvuRelease, mixerOpen, mixerClosed, signalAnode, STB)? I would like to understand how those names were created and what is their physical meaning.
Hi godmorgon
bad news for you: you have bought a heatpump with non documented protocols. You can ask SE or Tecalor to provide you documentation on the registers stored in the heatpump.
We tried in the last 70 pages to understand. When we find something relevant Marcus  documents it  in the wiki.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 22 Dezember 2014, 09:26:31
Zitat von: immi am 22 Dezember 2014, 00:27:44
Peter
you should really do not try to write back (set) to the heatpump.
the answer you posted shows the register are really different.
I am considering to disable write back for old firmwares.
immi

Alles klar immi.
Es ist eine gute Idee das Schreiben zu alten Wärmepumpen zu deaktivieren.
Ich habe das zwar bis jetzt auch nicht versucht, aber man könnte vielleicht irgendwann aus versehen sowas auslösen.
Mir ist wichtig dass das Gerät zuverlässig die Daten aufzeichnet.
Wie stabil ist die Kommunikation bei neueren Wärmepumpen?
Habt Ihr unterbrechungen in der Kommunikation oder Aufzeichnung?
Bei mir sieht es nach 2 Tagen nocht gut aus.  :)
Macht es vielleicht Sinn, den FHEM-Server z.B. Nachts um 0Uhr immer neu zu sparten (restart)?

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 10:38:37
Zitat von: immi am 22 Dezember 2014, 00:42:16
We tried in the last 70 pages to understand. When we find something relevant Marcus  documents it  in the wiki.
I have read the last 70 pages. I fully understand that the available data is a result of reverse engineering. Somebody gave names to the variables. Some things are obvious. The others aren't. Therefore, I asked for an explanation how you guys came up with the names you are using and how they are related to the parts and processes of the THZ.
Two examples:
- Whenever my heat pump is heating rvuRelease is set to 1. What does it mean? Can I tell from a bit whether the heat pump is heating or warming the water?
- I never saw mixerOpen, mixerClosed or the valve bits set to 1 (sampling rate - 1 min). Is something wrong with my heat pump? Does it encode the values in a different way?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 11:31:03
Zitat von: godmorgon am 22 Dezember 2014, 10:38:37
rvuRelease is set to 1.
rvuRelease is a typo it should be evuRelease; i will fix it in the next version.

It should change only if your circuit is connected as in the image below.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 22 Dezember 2014, 12:02:01
That is correct, immi. Our energy supplier put such a release timer in. Thanks to the THZ-FHEM module I can see that this switch has detrimental effects to the warmwater. If the heating is triggered just before the "off time" sets in the whole warmwater tank is replaced fresh cold water, meaning in that one hour were no heating is triggered, the water temp goes from 38°C to 25°C. It cleary shows that this switch actually cost money. Pretty stupid thing. Even changing the supplier on the free market does not change this.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Dezember 2014, 15:36:10
AFAIK this switch provides the EVU (Energieversorgungsunternehmen/Power Provider) the possibility to kick off high-load-systems in peal-load time ranges. This is mostly also covered within the power delivery contract. But they usually can tell you the "blocking-hours".
Not only heatpumps are using this EVU-Release-Switch...

My power company talk about this possibility of blocking the contract, but they never did it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 16:09:15
One minor addition from my findings:
cmd = 0a024b returns the software ID as displayed at the commissioning level. Though, I do not know the difference between the software version (5.39) and the software ID (7278).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 16:23:20
Zitat von: godmorgon am 22 Dezember 2014, 16:09:15
One minor addition from my findings:
cmd = 0a024b returns the software ID as displayed at the commissioning level. Though, I do not know the difference between the software version (5.39) and the software ID (7278).
Not in my heatpump
0A024B-0100580A024B1003-01045C0A024B1003-UNKNOWN REQUEST
are you sure about  0a024b?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 16:35:46
Tx: 01 00 58 0a 02 4b
Rx: 01 00 e2 0a 02 4b 1c 6e => 7278
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 16:39:09
One more thing:
Does yours respond to cmd = 0xfe?

Rx: 01 00 c7 fe 03 b1 83 f5 01 00 00 04 32 c9 00 06 67 71 03 0f 4d 61 72 20 31 34 20 32 30 31 34 20
(b'\x03\xb1\x83\xf5\x01\x00\x00\x042\xc9\x00\x06gq\x03\x0fMar 14 2014 ')
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 16:50:47
Zitat von: godmorgon am 22 Dezember 2014, 16:39:09
One more thing:
Does yours respond to cmd = 0xfe?

Rx: 01 00 c7 fe 03 b1 83 f5 01 00 00 04 32 c9 00 06 67 71 03 0f 4d 61 72 20 31 34 20 32 30 31 34 20
(b'\x03\xb1\x83\xf5\x01\x00\x00\x042\xc9\x00\x06gq\x03\x0fMar 14 2014 ')

Yes "FE" is an old friend, never changing from 2 years.
68FE03B183910001000000000006674A02084D6172202039203230313120
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 16:51:21
v 0117 uploaded; you can update tomorrow.
changelog:
- errata of evuRelease
- enabling of read-only mode for old firmware
- sHistory decoding fixed for old firmware
- engl. command ref updated.


@Markus: when do you have time...
would you be so nice to translate the command ref in german and send me back by email?
would you be so nice to update the wiki for old firmwares; incl. a big disclaimer?

@Willy: when do you have time...
if you give me a mapping like weekdays, I can implement the fault name
example how could it look like.
my %weekday = ( "0" =>"Monday", "1" => "Tuesday", "2" =>"Wednesday", "3" => "Thursday", "4" => "Friday", "5" =>"Saturday", "6" => "Sunday" );
my %faultmap = ( "0" =>"n.a.", "1" => "F01_Anode_fault", "2" =>"F02_XXX_XX_X",
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 16:59:55
So it looks like your heat pump or some parts of it have "Mar 9 2011" as manufacturing date.
There seems to be an alternative command for the software ID: 0a0341. It also returns 7278 (1c6e).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 22 Dezember 2014, 17:27:17
0A0341-01004F0A03411003-0104530A03411003-UNKNOWN REQUEST
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 22 Dezember 2014, 17:46:37
This is weird.

Would it make sense to compare register/command responses for 0x0a0000-0xcffff?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 Dezember 2014, 21:44:11
Zitat von: immi am 22 Dezember 2014, 16:51:21
@Willy: when do you have time...
if you give me a mapping like weekdays, I can implement the fault name
example how could it look like.
my %weekday = ( "0" =>"Monday", "1" => "Tuesday", "2" =>"Wednesday", "3" => "Thursday", "4" => "Friday", "5" =>"Saturday", "6" => "Sunday" );
my %faultmap = ( "0" =>"n.a.", "1" => "F01_Anode_fault", "2" =>"F02_XXX_XX_X",
ok, I'll do my very best  ;) . Unfortunately there's no English version of the installation manual available at all; so I need to translate myself. Feel free to correct it if I'm wrong.

my %faultmap = ( "0" =>"n.a.", "1" => "F01_Anode_fault", "2" => "F02_SafetyTemp_Delimiter_actuated", "3" => "F03_High_Preasure_Guard_fault", "4" => "F04_Low_Preasure _Guard _fault", "5" => "F05_Outlet_Fan_fault", "6" => "F06_Input_Fan_fault", "7" => "F07_Main_Output_Fan_fault", "11" => "F11_Low_Preasure_Sensor_fault", "12"=> "F12_High_Preasure_Sensor_fault", "15" => "F15_DHW_Temperature_fault",  "17" => "F17_Defrosting_Duration_exceeded", "20" => "F20_Solar_Sensor_fault", "21" => "F21_Outside_Temperature_Sensor_fault", "22" => "F22_Hot_Gas_Temperature_fault", "23" => "F23_Condensor_Temperature_Sensor_fault", "24" => "F24_Evaporator_Temperature_Sensor_fault", "26" => "F26_Return_Temperature_Sensor_fault", "28" => "F28_Flow_Temperature_Sensor_fault", "29" => "F29_DHW_Temperature_Sensor_fault", "30" => "F30_Software_Version_fault" );

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 22 Dezember 2014, 21:45:24
Zitat von: immi am 22 Dezember 2014, 16:51:21

@Markus: when do you have time...
would you be so nice to translate the command ref in german and send me back by email?
would you be so nice to update the wiki for old firmwares; incl. a big disclaimer?


i'll try tomorrow :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 22 Dezember 2014, 23:12:02
Zitat von: houseowner123 am 21 Dezember 2014, 19:59:57
@willy: A month ago I change the room influence setting to 80:20 and I see remarkable improvements when there are sudden temperature changes. The heating is totally off now when the fireplace is on until noon the next day. Energy consumption is a lot better for me than on 50:50 setting. What is your experience?
Hi all,
if you cannot  understand my following sentences in German language please let me know, but basically I believe that all of us gut genug deutsch verstehen. Das Thema wird mir zu komplex, um es ohne Gefahr von Missverständnissen in englisch rüber zu bringen.


Klar, plötzliche Änderungen der Innentemperatur (Sonneneinstrahlung, Holzofen, viele Personen im Haus, ...) werden mit 80:20 (Innen:Außen) besser berücksichtigt als mit 50:50 oder gar 20:80. Dafür ist das Setting ja da. Aber man muss beachten, warum überhaupt die Außentemperatur in die Rechnung eingeht. Der Grund ist, dass bei einem plötzlichen Kälteeinbruch (außen) frühzeitig vorgeheizt werden muss. Wenn erst der Innenfühler merkt, dass es innen kalt wird, dann ist es viel zu spät zum heizen. Die schwache Wärmepumpe  braucht einige Stunden, um den Estrich und die Wohnräume aufzuheizen. Deshalb darf es gar nicht so weit kommen, dass die Innentemperatur wegen eines Kälteeinbruchs absinkt. Die Heizung bekommt deshalb über den Außentemperatursensor die Info, dass demnächst die Wände auskühlen werden, und dass deshalb ein höherer Heizbedarf anliegt.

Die spannende Frage dabei ist die Abstimmung aller beteiligten Faktoren. Das ist von Haus zu Haus unterschiedlich:
Das Heizverhalten der Bewohner ist ebenfalls unterschiedlich. Ich z.B. habe gar keine Nachtabsenkung, weil ich über Nacht praktisch keine Temperaturänderung feststelle, wenn ich abends die Heizung ausschalte. Und das 1/2 Grad, das über Nacht verloren ging, muss dann morgens aufgeheizt werden, wenn die Zuluft der Wärmepumpe am kältesten ist ...  :-\

Je nach Haustyp und Wetterverhältnissen kann es bei 80:20 evtl. auch mal kalt werden.

Weitere interessante Faktoren sind:
Nun zur Frage nach meinen Erfahrungen: Ich habe zwar keinen Holzofen, aber große Fenster auf der Südseite. Und bei meinem sehr gut gedämmten Haus genügt auch die Esszimmerlampe (150Watt Halogen), um die Raumtemperatur zu erhöhen. Zu Beginn hatte ich keinen Innentemperaturfühler. Jeder noch so kleine Einflussfaktor, vor allem Sonne, bewirkte eine Temperaturerhöhung, die sich über Stunden hielt, weil der Heizung eben die zu hohe Raumtemperatur unbekannt war.
Ich begann dann mit 20:80 ... 30:70, weil mir im HaustechnikDialog-Forum von zu großen Werten abgeraten worden war. Ich bin nun dennoch bei 50:50 und sehe keine Nachteile. Wenn es über Nacht plötzlich kalt wird (so richtig kalt hatten wir diesen Winter ja noch gar nicht), dann fällt die Innentemperatur um ca. 0,5° ab. Die Ursache dafür habe ich noch nicht analysiert. Ich weiß also noch nicht, ob ich dennoch weiter gehen sollte.

Trotz aller Faktorenschieberei bringt etwas ganz anderes den wirklichen Durchbruch bei den Heizkosten: alle Raumthermostate ganz öffnen, die Durchflussmengen hydraulisch abgleichen, bis alle Räume gleich warm werden, die Heizkurve P13 und Fußpunkt P15 so weit runter drehen, bis die Innentemperaturen stimmen, und die Pumpendrehzahl so einstellen, dass die Spreizung (Differenz zwischen Vor- und Rücklauftemperatur) bei ca. 5° liegt. Das war eine 6 Wochen lange Arbeit mit täglich mehrfacher Temperaturmessung in allen Räumen, dauerndes abgleichen der Durchflussmengen und nachjustieren der Parameter. Aber jetzt produziert die Wärmepumpe nur noch exakt die Wärmemenge, die auch tatsächlich gebraucht wird, kein Stück mehr.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 23 Dezember 2014, 08:57:12
Zitat von: willybauss am 22 Dezember 2014, 21:44:11
ok, I'll do my very best  ;) . Unfortunately there's no English version of the installation manual available at all; so I need to translate myself. Feel free to correct it if I'm wrong.

v0118 uploaded, you can probably update tomorrow or this afternoon, ask sourceforge:)
-faultcode implemented.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 23 Dezember 2014, 12:48:15
Zu Willys Kommentar ein paar Anmerkungen:
1. So weit stimmt alles, was Du sagst. Vergiss aber das Haustechnik-Dialog Forum als verlässliche Quelle. Was verstehst Du unter sehr gut gedämmt? Gib mal Deinen Jahresbedarf an. Meiner ist theoretisch mit 19 kWh/m2 per anno berechnet worden  (inkl. Warmwasser). Dank des milden Winters werden es so 16-17 kWh/m2 sein. d.h. Heizkosten imcl WW von 40 €/Monat im 4 Personenhaushalt.
2. Hydraulischer Abgleich ist wichtig, normalerweise sollte die Heizungsfirma das genau berechnen und die Durchflussraten entsprechend einstellen; ich würde a da nur dranrummstellen, wenn es absolut notwenig ist. Wie Du bereits festgestellt hast. Allein die Präsenz einer oder 2 Personen in einem mittelgroßen ändert die Raumtemperatur beträchtlich. Um diesen Abgleich wirklich ordentlich durchzuführen brauchst Du für jedes Zimmer einen Thermometer, viel Zeit und kein zusätzlichen Wärmequellen (auch Personen), die das Ergebnis beeinflussen. Der Aufwand ist beträchtlich und praktisch für die meisten, die schon im Haus leben kaum durchführbar. Die Ausstattung der Zimmer ist auch nicht zu unterschätzen. Ein leeres Zimmer heizt sich erst mal schneller auf und kühlt sich schneller ab. Sich Übergardinen, Möbel, Teppiche vorhanden verlängern sich diese Zeiten. Idealerweise wird solch ein Abgleich in einem leeren Haus durchgeführt. Als letztes noch: Der Wunsch der meisten sind nie gleiche Temp. überall, sondern kältere Schlafzimmer und wärmerer Wohnzimmer und Bäder. D.h. nach dem Abgleich müsste ich weitermachen und Schlafzimmer runterregeln, um andere Wunschräume hochzuregeln, was den Aufwand erheblich vergrößert. Oder täusche ich mich da?
3. Die Nachtabsenkung bringt schon was, wenn man es richtig macht und nicht übertreibt, zumindest für das Holzständerhaus. Meine Nachtabsenkung geht von 21 Uhr bis 13 Uhr.  D.h. 11 Uhr springt die Heizung wieder an, wenn und das ist meist die Zeit, bei der die Tagestemp. am höchsten ist.
4. Fenster auch große Fronten bringen von Nov-Feb. m.E. nichts, da die Sonneneinsrahlung zu niedrig ist. Gerade 3-fach verglaste Fenster. In der Übergangszeit sieht das schon wieder anders aus.
5. Keiner sagt, daß die 80:20 in Stein gemeißelt sind. Die Einstellung ist nur vom Verbrauch her deutlich besser als 50:50, wenn die Aussentemp so zwischen 6 und 0 Grad liegen. Das kann schon mit der Holzständerbauweise zusammenhängen, weil die Kinetik des Aufheizend und Auskühlens anders ist, als bei Steinbauweise. Der Effekt zusätzlicher Wärmequellen (Geschirrspüler, Kamin und Ofen) auf die Raumtemp ist beträchtlich. Wenn ich 2 Personen mehr im Haus (Besuch) habe, wäre das letzte was ich machen würde, den Kamin anzuwerfen, weil es unerträglich warm werden würde.
6. Frage: Wie erreichst Du eine Spreizung von 5°C und wie misst Du die? Stiebel Eltron und die auch die Heizungsfirma haben von den Einsteckthermometern abgeraten.

Freue mich über den konstruktiven Austausch. :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 23 Dezember 2014, 12:56:24
Zitat von: willybauss am 22 Dezember 2014, 23:12:02
Hi all,
if you cannot  understand my following sentences in German language please let me know, but basically I believe that all of us gut genug deutsch verstehen. Das Thema wird mir zu komplex, um es ohne Gefahr von Missverständnissen in englisch rüber zu bringen.


Hallo willybauss,

ich bin ja momentan noch ganz am Anfang mit der Auswertung meiner Daten, da ich erst seit wenigen Tagen ein funktionierendes FHEM habe.
Eins ist mir aber sofort aufgefallen. Aufgrund meiner Nachtabsenkung läuft meine LWZ ab ca. 9 Uhr mehrere Stunden durch, obwohl die Aussentemperaturen noch recht niedrig sind.
Eventuell muss ich die Nachtabsenkung noch überdenken. Ich könnte mir aber auch vorstellen dass die Däpfung der Aussentemperatur z.B. 12Stunden hier noch helfen könnte.
Mein Ziehl wäre dann, dass die LWZ möglichts nur dann heizt wenn die Aussentemperatur höher (als z.B. in der Nacht) ist.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Dezember 2014, 18:28:01
Zitat von: houseowner123 am 23 Dezember 2014, 12:48:15
Zu Willys Kommentar ein paar Anmerkungen:
...
Im HDT Forum gibt es 2 - 3 Leute mit Verständnis, der Rest ist ...

Mein Haus soll angeblich 45kWh/m² brauchen; ich (2-Personen-Haushalt) komme aber wie Du auf ca.500€ pro Jahr bei 120m² beheizter Fläche - und habe weder thermische Solarzellen auf dem Dach noch einen Holzofen, aber einen beheizten Kellerraum und das Warmwasser für die Spülmaschine geht ebenfalls über die LWZ, und incl. des Stromverbrauchs für die Lüftungsanlage, die ja auch im Sommer läuft.

Normalerweise gibt man ja den THERMISCHEN Energiebedarf an.

40€/Monat => 480€/Jahr => ca. 2100kWh elektrische Energie => ca. 7300kWh thermische Energie

Bei 17kWh/m² wäre das eine beheizte Wohnfläche von ca. 430m², wenn ich mich nicht irgendwo gründlich verhauen habe. Das würde die LWZ/THZ gar nicht schaffen, also muss Deine Angabe der ELEKTRISCHE Energiebedarf sein. Das wiederum entspräche bei einem COP von ca. 3,5 einem THERMISCHEN Energiebedarf von 18*3,5 = 63kWh/m². Kommen die Hausverkäufer jetzt auf die Idee, die Zahlen zu schönen, indem sie thermisch und elektrisch "verwechseln"?

Eine hübsche Vergleichsgröße wäre der Bivalenzpunkt,d.h. bei welcher Außentemperatur schafft es die LWZ grade noch, das Haus zu beheizen, ohne den Heizstab zu Hilfe zu nehmen. Bei mir sind das -7,5°C.

Hydraulischer Abgleich: Deine Aufwandsabschätzung passt ganz gut. Ich hatte ca. 10 Thermometer im ganzen Haus verteilt, dann aber festgestellt, dass sie um bis zu +/-0,5° voneinander abweichen. Dann muss man halt rechnerisch (additive Korrektur) eingreifen, um vergleichen zu können. Bin dann aber auf ein Infrarotthermometer umgestiegen. Abgleich ist im bewohnten bzw. bewohnbar eingerichteten Zustand besser, weil das dann die spätere Realität besser abbildet als ein leeres Haus. Berechnung ist eine Sache, die Praxis leider etwas anderes. Die Wahrheit sieht man erst, wenn man dem Wasser freien Lauf gibt, d.h. die Thermostate ganz öffnet. Die würgen ja letztlich das ab, was die LWZ grade erwärmt hat. Ich hatte das "Glück", nach einem Bandscheibenvorfall weder sitzen noch liegen zu können. Dann bin ich wochenlang nachts durchs Haus gegangen und habe gemessen und justiert. Wer weiß, ob ich mich das ohne die Drogen (Schmerzmittel) getraut hätte :-) ... Schlafzimmer ist bei mir ganz einfach: es hat überhaupt keine Heizung. Wenn ich es dort warm haben will genügt es, die Tür zum Flur 1 Stunde offen zu lassen. Wärmeres Bad und wärmere Ankleide ist schwierig. Ich schaffe dort grade mal 1° mehr als im Rest des Hauses. Beim nächsten Haus würde ich dort die Heizschlangen noch enger verlegen lassen (habe überall 10cm Raster).
Meine Temperaturen:
   Wohnräume + Flure 21,5 +/- 0,2°C
   Bad + Ankleide 1° mehr
   beheizter Kellerraum 20°C (Hobbywerkstatt, da genügt das so)
   
> Oder täusche ich mich da?
nein, das stimmt ganz gut.

Nachtabsenkung:Ich möchte morgens ab 6:30 ausgiebig frühstücken und Zeitung lesen ohne zu frieren. Deshalb nützt mir eine Absenkung bis 13 Uhr nichts. Wenn ich um 21 Uhr abschalte und um 4 Uhr wieder einschalten muss, kann ich es auch gleich konstant lassen. Wie weit geht denn bei Dir die Temperatur runter bis 11 Uhr? Bei mir würde man nicht viel Unterschied sehen.

Südfenster: Bei uns schien heute die Sonne, und schwups hatte ich 23,5° im Wohnzimmer, jetzt noch 22,5. Die Heizung hat um 9 Uhr zuletzt geheizt...

Evtl. musst Du im Lauf des Winters die 80:20 etwas verändern, vielleicht passt es ja bei Deinem Haus sogar.

Die Spreizung ist einfach: entweder die Enden der Heizschläuche im Verteiler mit dem Infrarotthermometer messen (vorher mit schwarzem Gewebeklebeband bekleben, um die Messgenauigkeit zu verbessern) oder einfach in FHEM sGlobal flowTemp und returnTemp voneinander abziehen. Einstellen tut man sie über die Justage der Pumpenleistung.  Höhere Leistung = größerer Durchfluss = weniger Zeit, um die Wärme an den Estrich abzugeben = höhere Rücklauftemperatur. Das Ganze geht natürlich nur während des Heizvorganges.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 23 Dezember 2014, 18:32:21
Zitat von: peter456 am 23 Dezember 2014, 12:56:24
Hallo willybauss,

ich bin ja momentan noch ganz am Anfang mit der Auswertung meiner Daten, da ich erst seit wenigen Tagen ein funktionierendes FHEM habe.
Eins ist mir aber sofort aufgefallen. Aufgrund meiner Nachtabsenkung läuft meine LWZ ab ca. 9 Uhr mehrere Stunden durch, obwohl die Aussentemperaturen noch recht niedrig sind.
Eventuell muss ich die Nachtabsenkung noch überdenken. Ich könnte mir aber auch vorstellen dass die Däpfung der Aussentemperatur z.B. 12Stunden hier noch helfen könnte.
Mein Ziehl wäre dann, dass die LWZ möglichts nur dann heizt wenn die Aussentemperatur höher (als z.B. in der Nacht) ist.
Ja, so ähnlich war auch meine Überlegung. Aber ich will es morgens schon warm haben, deshalb lässt sich heizen in der Nacht manchmal nicht vermeiden.

Generell ist es bei Wärmepumpen wie beim Auto: Kurzstreckenbetrieb schadet dem Material und erhöht den Verbrauch. Durch diverse Einstellungen (vor allem Hysteresen und Integralanteil P30) ist es mir gelungen, dass die WP nur noch 2 - 3 mal am Tag anspringt, dann aber mehrere Stunden am Stück heizt. Dennoch bleibt die Raumtemperatur sehr konstant.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 24 Dezember 2014, 09:19:38
buon natale a tutti
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Dezember 2014, 11:40:24
Zitat von: immi am 24 Dezember 2014, 09:19:38
buon natale a tutti
mille grazie
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 27 Dezember 2014, 19:22:13
Hallo Immi,

ich habe jetzt bei meinem FHEM zuletzt einige Einstellungen geändert und teilweite noch Kommunikationsprobleme festgestellt.
Z.B. wenn ich "attr global verbose" von 5 auf 3 verändere dann bekomme ich bei sGlobal folgende Antwort  "010023FB00C5FFED013F0119030D01B6000000E0FFA30142111C000099CA0000
msg2 WInterface max repeat limited to 24 ". Und meine Aufzeichnung funktioniert nicht mehr.  Wenn ich "attr global verbose" zurück auf 5 einstelle funktioniert alles wieder. Des Weiteren wenn ich den Pfad der LOG-Dateien von "./log" auf meinem USB-Stick "/media/usbstick" verändere bekomme bei sGlobal die gleiche Antwort wie vorhin.
Im Anhang ein Auszug aus der LOG-Datei bei verändertem Pfad auf USB-Stick.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Dezember 2014, 23:37:12
Hi Peter
I will fix it tomorrow, easy
In the meanwhile, can you post a txt-file (no image) with all your readings?
I expect most of them are not working on your firmware and I want to deactivate them for you
e.g

register        value         timestamp
p01RoomTempDayHC1     21.8 °C      2014-12-27 23:20:12
p01RoomTempDayHC1SummerMode 21 °C 2014-12-27 23:21:01
...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 28 Dezember 2014, 12:00:22
Hallo immi,

danke für die schnelle Hilfe.
Im Anhang meine Readings.

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 28 Dezember 2014, 14:13:20
immi,

Looking at the loop in THZ_ReadAnswer I would say that the data arrives more slowly than expected. Logging adds some latency to the loop which improves the results. To understand the timing you would need to timetag every group of received bytes.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Dezember 2014, 19:10:52
uploaded v0119, tomorrow you can update
changelog:
- the firmware parameter 2.06 increases the countmax of the repetition of DevIo_SimpleReadWithTimeout from 24 to 50
- decrease of the DevIo_SimpleReadWithTimeout from 0.06 to 0.02
- the firmware parameter 2.06 removes registers not supported from older hetpumps

@ Peter, now you can remove "verbose 5", please test tomorrow

@ godmorgon: Makes sense what you say. But, latency alone is not the problem.
I cannot wait too much for each read, otherwise I block fhem. I prefer to read faster and several times, untill I get 1003.
This makes the reading function very fast for short messages. For longer messages, I iterate up to 50 times (not to block fhem). If 50 is not enough,  I will increase. Willy had the same issue (one order of magnitude less), some monthes ago.



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 28 Dezember 2014, 19:26:54
Why don't you introduce a separate thread doing all the low-level work (e.g. collecting the message bytes between 02 and 1003, stripping the escape bytes)?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Dezember 2014, 20:29:48
Zitat von: godmorgon am 28 Dezember 2014, 19:26:54
Why don't you introduce a separate thread doing all the low-level work (e.g. collecting the message bytes between 02 and 1003, stripping the escape bytes)?
Multithreading is complicated to implement: you have to make sure that 2 threads are not colliding, the serial interface is serial:)
Moreover fhem is not really supporting parallelism.
There is an attempt from Rudolf with nonblocking calls. If you want to try.

At the time thz-fhem is running very stable with my heatpump, and I am very optimistic that also old heatpumps can be tamed without nuclear weapons
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 28 Dezember 2014, 22:16:07
Zitat von: immi am 28 Dezember 2014, 20:29:48
At the time thz-fhem is running very stable with my heatpump, and I am very optimistic that also old heatpumps can be tamed without nuclear weapons

without? oh  :( i've already prepared some...
just kidding ;)
yes, it's running like a charm. i'm loving it!!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Dezember 2014, 22:36:11
I can confirm the smoothly working THZ module as well. Since months we're in a state of stability which is SOOO good that I wouldn't like to set this result on risk by major changes, as long as the result can also be reached by "conservative" add ons.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 29 Dezember 2014, 01:33:02
I can attest to the smoothness of the THZ module, except for that minor setback a couple weeks ago where the connection just did not work anymore. But thanks to willy and immi, that was minor. One thing that bothers me and I am not sure what the cause is that certain LWZ settings do not work anymore, for instance. I just tried to set things to "Absenkbetrieb" since I was gone for 2 days. Looking at the monitoring, the mode was selected but ultimately never executed. It kept running in "automatic". The other weird think is the ventilation: Only night settings work. Also for the day. I can never have no a change is setting for that. Whatever I select for night, runs 24/7. That was definitely different before.
So I wonder why this happens. Bugs in the LWZ firmware? Or does the THZ-FHEM modulation (not the monitoring) create these issues? So, keep your eyes open and report here if you see something as strange. Thanks!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Dezember 2014, 07:23:26
Zitat von: houseowner123 am 29 Dezember 2014, 01:33:02
... except for that minor setback a couple weeks ago where the connection just did not work anymore.
Your're right. I'd already forgot it.

Zitat von: houseowner123 am 29 Dezember 2014, 01:33:02
... certain LWZ settings do not work anymore, for instance. I just tried to set things to "Absenkbetrieb" since I was gone for 2 days. Looking at the monitoring, the mode was selected but ultimately never executed. It kept running in "automatic".
Did it really work before? I'm pretty sure I had the same issue last summer during vacation absence. Sounds like same issue as with p43---p46 UnschedVent*. These also can be set via FHEM, but the trigger flag for activation is still unknown. This flag obviously is being set automatically by the THZ's display after having changed the setting. Since none of us has a CAN bus monitoring, we still don't know how to activate it via fhem.

Zitat von: houseowner123 am 29 Dezember 2014, 01:33:02
The other weird think is the ventilation: Only night settings work. Also for the day. I can never have no a change is setting for that. Whatever I select for night, runs 24/7. That was definitely different before.

I can't confirm, since day and night settings are same in my case. Are you really sure that the hourglass symbol is visible on the THZ's display during day time? Otherwise your THZ might be outside of automatic mode.

edit:
Since tonight I know that my THZ can hold the inside temp. at 21.5°C, even at outside temperature of -14°C, and with just stage 1 of booster activated  :) .
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Dezember 2014, 10:23:07
Zitat von: houseowner123 am 29 Dezember 2014, 01:33:02
I just tried to set things to "Absenkbetrieb" since I was gone for 2 days. Looking at the monitoring, the mode was selected but ultimately never executed. It kept running in "automatic". The other weird think is the ventilation: Only night settings work. Also for the day. I can never have no a change is setting for that. Whatever I select for night, runs 24/7. That was definitely different before.
Hi Tom
I try to explain pOpMode:
I change pOpMode to standby (Bereitschaftbetrieb) when I am on holyday more days.
setback (Absenkbetrieb) is for discriminating different phases of one day (e.g. day and night);
I never use setback.
The opposite of setback is DAYmode

In automatic it toggles between setback and DAYmode according programXXX_YY

So if you are in setback it is normal that  "Whatever I select for night, runs 24/7".
To my opinion, your pOpMode is in setback or you have an issue with programXXX_YY: I would try to set them all again.
I just uploaded v0120 in which I set some delays between the programming of  programXXX_YY.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Dezember 2014, 11:59:51
Hi Peter
how does it look loke v0119
are your issues gone without verbose 5?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 29 Dezember 2014, 12:07:33
Zitat von: immi am 28 Dezember 2014, 19:10:52
uploaded v0119, tomorrow you can update
changelog:
- the firmware parameter 2.06 increases the countmax of the repetition of DevIo_SimpleReadWithTimeout from 24 to 50
- decrease of the DevIo_SimpleReadWithTimeout from 0.06 to 0.02
- the firmware parameter 2.06 removes registers not supported from older hetpumps

@ Peter, now you can remove "verbose 5", please test tomorrow

Hallo Immi,

Mit V0.119 funktionier alles super. Vielen Dank.
Wenn du das nächste Mal was änderst, könntest du bitte noch einige Register aus "get Mythz" entfernen.
Einige Register liefern zwar Werte, aber diese Werte sind nicht plausibel.
Es könnte folgende Register bleiben:
- sDHW
- sFirmware
- sGlobal
- sHC1
- sHC2
- sHistory
- sLast10errors

Ich habe noch eine Frage. Kann ich zu den aufgezeichneten Werten im Plot einen Korrekturfaktor (z.B. 0,5°C für Innentemperatur) einstellen?

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Dezember 2014, 13:27:02
Zitat von: peter456 am 29 Dezember 2014, 12:07:33
Ich habe noch eine Frage. Kann ich zu den aufgezeichneten Werten im Plot einen Korrekturfaktor (z.B. 0,5°C für Innentemperatur) einstellen?

Ich habe dafür userReadings genommen:
Rel_humidity:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[67]) + 11.5}, flow_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[3])}, outside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[1])}, dhw_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[9])}, inside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[81]) - 0.6 }

Lösche einfach raus, was Du nicht brauchst und füge den Rest Deiner Konfiguration hinzu. Das letzte in der Liste ist die inside_temp mit Korrekturwert -0,6°.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Dezember 2014, 14:30:51
Zitat von: peter456 am 29 Dezember 2014, 12:07:33
Einige Register liefern zwar Werte, aber diese Werte sind nicht plausibel.
Hi Peter
It should be already implemented in v0119. I leave for your firmware all readonly registers. One or 2 will deliver strange stuff (like partytime) but you can live with it.
Probably, you have lots of old stuff, which needs to be deleted.
try:
deletereading Mythz *

and restart
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 29 Dezember 2014, 16:42:44
thank immi I will try v0120. Even though to be sure that THZ module is not the issue I changed the Op settings on the LWZ display. Anyway, I will try it.
@willy impressive that you can get as low with minimal booster settings. We should compare Vor-und Rücklaufkurven. I have the feeling that I have a lot of air in my system. What pressure is your FBH set at? 1.8 bar or lower and what is your DG pressure?
I used the Kamin all day yesterday which shut off the FBH but then I get 19°C upstairs. Which is fine for me at night. Daily use inkl Lüftung: 8-10 kWh.
How do I eliminate irrelevant readings like s0A03AE, s0A03AF, s0A03B0 and s0A03B1 ?

@micomat: My ELV thermometers in the house do not work anymore. Do you have any idea why? Here is the log file code.

2014.12.28 20:18:47 3: Opening CUL_0 device /dev/ttyACM0
2014.12.28 20:18:47 3: Setting CUL_0 baudrate to 9600
2014.12.28 20:18:47 3: CUL_0 device opened
2014.12.28 20:18:56 1: Cannot init /dev/ttyACM0, ignoring it (CUL_0)


Thanks,
  Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Dezember 2014, 17:19:12
 
Zitat von: houseowner123 am 29 Dezember 2014, 16:42:44
2014.12.28 20:18:56 1: Cannot init /dev/ttyACM0, ignoring it (CUL_0)
Tonight my Raspi had a similar issue: at 6:44am the THZ monitoring stopped. Checking the log files I noticed that the EnOcean CUL stopped as well. Restarting FHEM nor Raspi didn't help. Issue solved by a power cycle of Raspi. Obviously the Raspi lost its support for serial (or USB) ports accidentally.
Zitat von: houseowner123 am 29 Dezember 2014, 16:42:44
We should compare Vor-und Rücklaufkurven. I have the feeling that I have a lot of air in my system. What pressure is your FBH set at? 1.8 bar or lower and what is your DG pressure?


Das wird Dir nicht helfen. Luft bekommst Du nur durch entlüften (lassen) raus. Höherer Druck verkleinert die Luftblasen  nur und erhöht das Risiko, dass Verschraubungen undicht werden - vielleicht auch erst langfristig. Worauf es wirklich ankommt habe ich ja bereits kurz vor Weihnachten beschrieben.
Wie ist das denn jetzt mit Deinem Bivalenzpunkt und mit dem thermischen Energieverbrauchs Deines Hauses? Der Energiepass nennt 2 Werte:
Endenergieverbrauch => Strom (bei mir 14,3kWh/m²a) 
Primärenergieverbrauch => thermischer Wärmebedarf (bei mir 47,2 kWh/m²a)
Der Unterschied (Faktor 3,3) erklärt sich durch den COP der Wärmepumpe.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 29 Dezember 2014, 17:46:58
Zitat von: willybauss am 29 Dezember 2014, 13:27:02
Ich habe dafür userReadings genommen:
Rel_humidity:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[67]) + 11.5}, flow_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[3])}, outside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[1])}, dhw_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[9])}, inside_temp:sGlobal {((split ' ',ReadingsVal("Mythz","sGlobal",0))[81]) - 0.6 }

Lösche einfach raus, was Du nicht brauchst und füge den Rest Deiner Konfiguration hinzu. Das letzte in der Liste ist die inside_temp mit Korrekturwert -0,6°.
Hallo willybauss,
ich habe gerade nach deinem Beispiel einen Korrekturfaktor bei der Innentemperatur eingegeben. Bei der Anzeige meiner Temperaturen hat sich der Wert auch soweit geändert. Aber in der Trendkurve wird immer noch der Wert ohne Korrekturfaktor aufgezeichnet.
Meine Konfiguration der Trenddarstellung sieht so aus:

define FileLog_Mythz FileLog /media/usbstick/log/Mythz-%Y-%m.log Mythz
define Plot1_Temp SVG FileLog_Mythz:thz1:CURRENT

Bei "CURRENT" werden ja die aktuellen Werte geschrieben. Sollte hier vielleicht was geändert werden?

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Dezember 2014, 20:01:14
Zitat von: peter456 am 29 Dezember 2014, 17:46:58
Meine Konfiguration der Trenddarstellung sieht so aus:

define FileLog_Mythz FileLog /media/usbstick/log/Mythz-%Y-%m.log Mythz
define Plot1_Temp SVG FileLog_Mythz:thz1:CURRENT

Bei "CURRENT" werden ja die aktuellen Werte geschrieben. Sollte hier vielleicht was geändert werden?

Gruß
Peter
CURRENT kenne ich nicht, aber ich habe den Eindruck, dass Du direkt in der fhem.cfg herum editierst. Das soll man nicht machen !!! Und das, was Du ändern musst, steht dort gar nicht drin, sondern in der .gplot Datei im Verzeichnis /opt/fhem/www/gplot. Aber da solltest Du ebenfalls nicht manuell drin herum editieren ...
Links unter dem Plot ist ein Link, der Dich in den Konfigurationseditor Deines Plots bringt. Dort musst Du definieren, woher die Daten genommen werden. Dort musst Du Mythz.sGlobal.insideTemp (der Wert von insideTemp wird repräsentiert durch seine Spaltennummer innerhalb von sGlobal) ersetzen durch das soeben erstellte userReading Mythz.inside_temp  (der Wert von inside _ temp wird repräsentiert durch die Spaltennummer 4 innerhalb  von  inside_temp).

Ich hätte gerne einen Screen Dump angehängt, wie das bei mir aussieht, aber der Server für Uploads scheint grade voll zu sein.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 29 Dezember 2014, 20:12:09
Zitat von: houseowner123 am 29 Dezember 2014, 16:42:44
@micomat: My ELV thermometers in the house do not work anymore. Do you have any idea why? Here is the log file code.

2014.12.28 20:18:47 3: Opening CUL_0 device /dev/ttyACM0
2014.12.28 20:18:47 3: Setting CUL_0 baudrate to 9600
2014.12.28 20:18:47 3: CUL_0 device opened
2014.12.28 20:18:56 1: Cannot init /dev/ttyACM0, ignoring it (CUL_0)


as willy already mentioned, looks like a problem of your CUL. Restarting may solve the problem.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 29 Dezember 2014, 20:26:33
Im FHEM-Wiki zur THZ steht das so beschrieben:
"In der fhem.cfg legen wir das Plot an:
define Plot_Temp SVG FileLog_Mythz:thz:CURRENT
attr Plot_Temp room Heizung".

Was mache ich falsch?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Dezember 2014, 21:55:52
Zitat von: peter456 am 29 Dezember 2014, 20:26:33
Im FHEM-Wiki zur THZ steht das so beschrieben:
"In der fhem.cfg legen wir das Plot an:
define Plot_Temp SVG FileLog_Mythz:thz:CURRENT
attr Plot_Temp room Heizung".

Was mache ich falsch?
@Peter:
Hast Du auch den Rest des betreffenden Absatzes gelesen? Steht im wiki irgendwas davon, dass Du ein userReading anstatt eines "normalen" Werts anzeigen willst? Dort wird nur sGlobal erwähnt - und damit wird der Wert ohne Korrekturfaktor angezeigt. Hast Du den (auch im wiki genannten) Link schon mal angeklickt und dann versucht zu machen, was ich Dir geschrieben hatte?

@Markus:
Wenn das so wörtlich im wiki steht, dann ist die Versuchung groß, mit dem Editor drin rum  zu basteln. Das kann man sicher auch so formulieren, dass der Editor-Gedanke außen vor bleibt.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 30 Dezember 2014, 08:29:16
Hallo willybauss,

dein Vorschlag hat funktioniert. Ich habe von Anfang an schon probiert die Userreadings im Plot einzutragen. Ich war aber zu doof die Input-Nummer richtig einzutragen. Bei einzelnen Variablen ist es wohl meistens die Nummer 4.
Vielen Dank.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Dezember 2014, 10:41:29
Zitat von: peter456 am 30 Dezember 2014, 08:29:16
Hallo willybauss,

dein Vorschlag hat funktioniert. Ich habe von Anfang an schon probiert die Userreadings im Plot einzutragen. Ich war aber zu doof die Input-Nummer richtig einzutragen. Bei einzelnen Variablen ist es wohl meistens die Nummer 4.
Vielen Dank.
Ja, die Bedienung ist manchmal etwas merkwürdig, und nicht konsistent über alle Anwendungsfälle hinweg. Mal muss man beim Datum anfangen zu zählen (Plots), mal beim ersten Datenwert (userReadings). Das führt leicht zu Verwirrung. Aber wenn man sich die bestehenden und funktionierenden Einträge des Plots anschaut kann man mit etwas Überlegung Rückschlüsse ziehen. Wichtig ist halt, erst zu Ende zu lesen, mit dem tatsächlichen Anwendungsfall in Beziehung zu setzen und das anzunehmen, was geraten wird  ;) .

Ja, es sollte dann i.d.R. immer die Nummer 4 sein:

1. TimeStamp
2. Modulname
3. Readingsname
4. Wert
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 30 Dezember 2014, 23:58:14
Thank you all for the hint with the CUL. Unplugging did the trick.
I noticed that flow and return temp are different in sGlobal and sHC1. Why is that? Which is the correct one?
Also the LWZ display shows a flow temp (average)? for both Vor and Rücklauf. Is that somewhere in sGlobal too?

Thanks,
Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Dezember 2014, 00:55:38
Zitat von: houseowner123 am 30 Dezember 2014, 23:58:14
Thank you all for the hint with the CUL. Unplugging did the trick.
I noticed that flow and return temp are different in sGlobal and sHC1. Why is that? Which is the correct one?
not for me; actually not now that I am on vacation.
Could be that you have different reading time? flowtemp is changing very fast.

sGlobal   
outsideTemp: 1.8 flowTemp: 12.7 returnTemp: 12.4 hotGasTemp: 13.8 dhwTemp: 18.9 flowTempHC2: -60 evaporatorTemp: 10.5 condenserTemp: 12.8 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 0 inputVentilatorPower: 0 mainVentilatorPower: 0 outputVentilatorSpeed: 0 inputVentilatorSpeed: 0 mainVentilatorSpeed: 0 outside_tempFiltered: 1.9 relHumidity: 0 dewPoint: 0 P_Nd: 6.15 P_Hd: 6.19 actualPower_Qc: 0 actualPower_Pel: 0 collectorTemp: -60 insideTemp: -60
2014-12-31 00:50:31

sHC1   
outsideTemp: 1.8 x08: -12.5 returnTemp: 12.4 integralHeat: -84 flowTemp: 12.7 heatSetTemp: 14.9 heatTemp: 12.4 seasonMode: winter integralSwitch: 101 opMode: standby roomSetTemp: 11
2014-12-31 00:50:28
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Dezember 2014, 11:50:53
Zitat von: houseowner123 am 30 Dezember 2014, 23:58:14
Thank you all for the hint with the CUL. Unplugging did the trick.
I noticed that flow and return temp are different in sGlobal and sHC1. Why is that? Which is the correct one?
Also the LWZ display shows a flow temp (average)? for both Vor and Rücklauf. Is that somewhere in sGlobal too?

Thanks,
Tom
I found a thread in fhem wiki (or forum?) mentioning such issues; they assume it most probably to be caused by instable voltage at USB ports, mixing of USB1.1 and 2.0 sticks, ... So if it happens frequently you can try to add an active USB hub having a separate power supply. But I have two of those (one on each USB port) and anyway I had the isssue... If you want to try it you need to select it  carefully, since especially Raspi doesn't work with all of them.

With the temperatures I strongly believe that it is like immi said. I checked my log file and saw such differences only in cases where the readings had a bigger difference than just a few seconds. You can force the readings by  "get Mythz sGlobal" and   "get Mythz sHC1"  within seconds. So you will  - if the assumption is true -  get identical values in both readings.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 31 Dezember 2014, 15:21:53
Hi willi,

I might look into this. Sometimes I have smaller outages, not longer than 1 hour. Other than that the HMS100 TF are pretty reliable and I am thinking of getting 2 more, to record temp. on KG, EG, DG, and attic. Crazy, I know.
Anyway you were right, 20 kwh is my Endenergiebedarf; Primärenergiebedarf is 51 kWh mit 145 qm beheizte Fläche. I terms of overall energiebedarf our houses a pretty comparable. The 19 kWh are: 6.5 kWh heating; 7 kwh WW; and 2.2  kwh booster. My endenergiebedarf for 2014 is 13.7 kWh. I am not completely happy though. I lose a little pressure every year and need to refill the FBH with about 0.5-1 L every year. Next year I plan to install an additional FBH in the basement (30 qm) with a Selfio Kit and I will connect this to HC1. This take a lot of adjustments. Thanks for explaining the integral-Anteil. Happy New year to all of you!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Dezember 2014, 19:02:56
Zitat von: houseowner123 am 31 Dezember 2014, 15:21:53
New year to all of you!
same from my side. I wish you all the best for next year.
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Januar 2015, 04:32:42
Hi tom
I read you have 1.8 bar and 4 floors (KG, EG, DG, and attic).
water 10 meter height -> 1 Bar
Atmosphere pressure --> 1 Bar
I would consider increasing to 2 Bars just to be sure. And I would check where the pressure loss is coming from.

Hi Willy
http://forum.fhem.de/index.php/topic,13132.msg234192.html#msg234192 is an interesting post.
I keep on reading that you are not a friend of room thermostates.
I do not understand the  physical nature of your empirical experience, which I trust, do not get me wrong.
Please assume the following oversimplified gedankenexperiment:
You have two identical houses just with two rooms.

In one case, room2 has a pulse wide modulation and in the other, an amplitude modulation.
Why one should be more efficient than the other?
At the end, the efficiency is only improved by minimizing the flow temperature.

Here I am really off-topic, ops..
I wish everyone a wonderfull 2015
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Januar 2015, 12:41:47
Zitat von: immi am 01 Januar 2015, 04:32:42
In both houses room1 the flow is completely open: temperature of room1 is just a function of the flow temperature e.g. 22°C.


In this (theoretical) case the benefit would be limited (but exist anyway), because this would represent an ideally adjusted heating curve. In room1 the thermostat would open the water flow by 100% of time, thus the thermostat1 could be skipped at all.

Advantage of thermostat in room2 is that you can easily adjust the target temperature to changing needs (as long as it is not higher than room1 temperature), what's not so easy without thermostats.

Drawback of regulating the temperature in room2 by thermostats would be, that the water flow (=> and temperature) in room1 would be impacted by switching the water flow in room2 on/off (because the HC pump will not follow the reduced flow value perfectly). In a real house it could happen that all thermostats in all rooms (or all rooms beside room1) are closed the same time, resulting in a high preasure failure 03. The flow value has to be at least 550 liters/h because otherwise the heat pump cannot deliver the produced heat to the house. These 550 l/h can't be realized by a flow through room1 only (in my case the whole house with all circles open has approx. 750 l/h). To avoid this situation there is normally a "Überströmventil" installed: in cases where too many thermostats are closed the same time the preasure increases above the adjusted limit in the Überströmventil, the Überströmventil opens and provides a short cut between flow and return pipe. This solution avoids the failure 03 of course, because it will immediately rise the return temperature, followed by switching off the heat generation. But a short cut between flow and return pipe definitely will prevent the generated heat from being used in your rooms => causing inefficiency. Without thermostats this situation can't happen,thus I decided to completely close the Überströmventil.

In practice it's usual to regulate the room temperature in ALL rooms by thermostats. That's what the heating mechanics can realize easily, fast and cheap - no time consuming investment on perfect hydraulic adjustment of water flow in all the rooms, no trouble with users wanting to adjust room temperatures easily by simply turning the wheel at the thermostat. So the solution for the mechanics is to adjust the heating curve higher than really needed, and limit the room temperatures by the thermostat settings in ALL rooms. So there is a difference between generated and really used flow temperature, which again causes inefficiency.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Januar 2015, 13:29:36
Zitat von: houseowner123 am 31 Dezember 2014, 15:21:53
Anyway you were right, 20 kwh is my Endenergiebedarf; Primärenergiebedarf is 51 kWh mit 145 qm beheizte Fläche. I terms of overall energiebedarf our houses a pretty comparable. The 19 kWh are: 6.5 kWh heating; 7 kwh WW; and 2.2  kwh booster. My endenergiebedarf for 2014 is 13.7 kWh. I am not completely happy though. I lose a little pressure every year and need to refill the FBH with about 0.5-1 L every year. Next year I plan to install an additional FBH in the basement (30 qm) with a Selfio Kit and I will connect this to HC1. This take a lot of adjustments. Thanks for explaining the integral-Anteil. Happy New year to all of you!

Please have in mind that the 51 kWh are per m². So your house has a calculated heat consumption of 51*145 = 7395 kWh/a. Mine is (mainly caused by being smaller) at 5664 kWh/a. When comparing our heat curves etc. you need to have in mind this difference of 30%. So your THZ works closer to it's limit than mine. In my house the booster usage was zero in last winter, yours was 2.2 kWh/m² => 319kWh in total.

You might be able to compensate that by your oven fire place, which I don't have. Do you have solar cells as well? I don't have them; I decided for PV cells on the whole south side of the roof.

Another interresting factor is the location. In my case the statistics says
- lowest average monthly temperature:  0.6°C
- average yearly temperature:  9.4°C
- highest average monthly temperature:  18.3°C

In your case (Berlin):
- lowest average monthly temperature:  1.1°C
- average yearly temperature:  8.8°C
- highest average monthly temperature:  17.2°C

So you might have an advantage in winter.

Meanwhile I have the 2014 values: 2184 kWh (electrical) in total => 18.2 kWh/m²
Compared to your 13,7 kWh/m² it looks like your oven (or solar cells?) help a lot.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 03 Januar 2015, 00:42:12
thanks willi; interesting point of view
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Januar 2015, 13:48:31
uploaded v 0121, tomorrow or this evening, you can update
changelog:

@ Peter: you should try : get Mythz sPxxxx
please post the reply of the register; please try to interprete it accordingly
look at the interpretation here http://www.haustechnikdialog.de/Forum/t/85548/Software-zum-Auslesen-der-Tecalor-THZ-303-SOL-ueber-RS232-o-a-Schnittstelle?page=9
maybe it works for you

Zitat
Hex________Dec________Wert________Parameter_______________________P
00D7_______215________21.5________Raumtemperatur Normalbetrieb_______P1
00DC_______220________22.0________Raumtemperatur Absenkbetrieb_______P2
0064_______100________10.0________Raumtemperatur Bereitschaft__________P3
01C2_______450________45.0________Brauchwassertemp. Normalbetrieb_____P4
01C2_______450________45.0________Brauchwassertemp. Absenkbetrieb_____P5
0064_______100________10.0________Brauchwassertemp. Bereitschaft_______P6
__02_________2_________2__________Lüfterstufe Normalbetrieb____________P7
__01_________1_________1__________Lüfterstufe Absenkbetrieb____________P8
__01_________1_________1__________Lüfterstufe Bereitschaft______________P9
015E_______350________35.0________Heizkreistemperatur Handbetrieb_______P10
01C2_______450________45.0________Brauchwassertemperatur Handbetrieb__P11
__02_________2_________2__________Lüfterstufe Handbetrieb_____________P12
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 04 Januar 2015, 14:18:22
Hallo,

klasse sache mit dem Auslesen der LWZ/THZ. Bin die tage darauf gestossen und habs mit nem übrigen Raspberry nachgebastelt. Vorhandene Hardware LWZ404SOL(BJ 2012) Vers. 5.39 mit zusätzlichem Display(LWZ) in der Küche/Esszimmer. Raspberry mit Fhem und Anschluss über USB-Kabel und Zugriff über Wlanstick(zum test jetzt mal).

Das Auslesen und plotten der Daten klappt soweit ganz gut.

Probleme hab ich mit dem Auslesen der Innentemperatur siehe Ausgelesene Global:

outsideTemp: 2 flowTemp: 49.9 returnTemp: 46.1 hotGasTemp: 103.2 dhwTemp: 43.4 flowTempHC2: -60 evaporatorTemp: -8.9 condenserTemp: 46.5 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 1 heatingCircuitPump: 0 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 rvuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 20 inputVentilatorPower: 20 mainVentilatorPower: 70 outputVentilatorSpeed: 57 inputVentilatorSpeed: 38 mainVentilatorSpeed: 22 outside_tempFiltered: 1.9 relHumidity: 28.4 dewPoint: 0 P_Nd: 2.54 P_Hd: 20.27 actualPower_Qc: 10885 actualPower_Pel: 17302 collectorTemp: -60 insideTemp: -60

In der Mythz sehe ich die Version 0.110. Leider bin ich zu doof ein Update durchzuführen. 
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Januar 2015, 14:27:26
Zitat von: glücksgriff am 04 Januar 2015, 14:18:22
In der Mythz sehe ich die Version 0.110. Leider bin ich zu doof ein Update durchzuführen.
updating is easy; just type update in the command line field and wait 2 min and restart the Raspberry.
for the temperature issue tom and willy will help you; i do not have zusätzlichem Display installed
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 04 Januar 2015, 14:37:48
Hi immi,

danke für die schnelle Antwort. Das mit Update habe ich auch schon getestet. Hab auch wie im Ebook beschrieben links Button für restart,update....... integriert.Restart und update-check funktioniert.

Bei update bekomme ich folgende Meldung:


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Januar 2015, 14:42:01
after update do not expect a feedback from fhem; it depends on too many things.
always refer to logfile

if you updated like I wrote, should be ok.
restart your raspi.
check which version of thz you have running

immi

p.s. I do not like the buttons for such important/critical things. I could click without wanting it.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 04 Januar 2015, 14:56:19
Hi immi,

Two more questions:
- Do you actually have a numeric software ID (not the software version) shown in the display?
- The values of actualPower_Qc and actualPower_Pel do not make any sense. Do you know for sure that such values are provided?

I also think that the decoding of the relative humidity is not quite right. The value just posted by glücksgriff is absolutely identical to the one posted by willybauss in a different thread. In my case it is always set to 0.

Cheers,
godmorgon
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 04 Januar 2015, 18:06:21
Hi,
hab meine himbeere 2 stunden in ruhe gelassen und vor einer stunde ein reset gemacht. Weder im eventmonitor noch im logfile stand was von dateiaktualisierungen. Lediglich die mythz daten wurden aktualisiert. Gibts eigentlich andere die auch probleme mit dem auslesen der innentemperatur haben.
2.display kann ich ja nicht falsch angeschlossen haben. Feuchtmessung ist ok und die raumtemp steht ja auch im display.
Was bedeutet "global only" als antwort für den befehl update.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Januar 2015, 18:20:01
Hi godmorgon
>> Do you actually have a numeric software ID (not the software version) shown in the display?
I do not know; I am still on vacation for the next 2 weeks (I cannot check now). It is a topic in which I want to dig further.
Please keep on sharing all your information.
>> The values of actualPower_Qc and actualPower_Pel do not make any sense. Do you know for sure that such values are provided?
no: most of the names in register FB come from here 02.12.2013 06:44:26 http://www.haustechnikdialog.de/Forum/t/85548/Software-zum-Auslesen-der-Tecalor-THZ-303-SOL-ueber-RS232-o-a-Schnittstelle?page=13
Papillon got the names from the tecalor service software; I translated some of them using the same words in the engl. manual (google may help you).

My interpretation, which I never checked:
actualPower_Qc --> differential in time of Heat_Qc 
actualPower_pEl --> differential in time of ElectricalEnergy (electrical power from the plug)
If you make an avarage of their ratio over time (weighted mean over time), you should get the CoefficientOfPerformance.
Last year, I thought to check their ratio and write me an allert email, if it goes behond a threshold ... then I forgot to dig further.


>> relative humidity
I do not have a humidity sensor ;(
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 04 Januar 2015, 18:35:58
Zitat von: glücksgriff am 04 Januar 2015, 18:06:21
Hi,
hab meine himbeere 2 stunden in ruhe gelassen und vor einer stunde ein reset gemacht. Weder im eventmonitor noch im logfile stand was von dateiaktualisierungen. Lediglich die mythz daten wurden aktualisiert. Gibts eigentlich andere die auch probleme mit dem auslesen der innentemperatur haben.
2.display kann ich ja nicht falsch angeschlossen haben. Feuchtmessung ist ok und die raumtemp steht ja auch im display.
Was bedeutet "global only" als antwort für den befehl update.

if you used the update like I told you, you should get following result


RMDIR: /opt/fhem/restoreDir/2014-12-25
UPD ./CHANGED
UPD FHEM/00_SONOS.pm
UPD FHEM/00_TCM.pm
UPD FHEM/10_CUL_HM.pm
UPD FHEM/10_EnOcean.pm
UPD FHEM/21_SONOSPLAYER.pm
UPD FHEM/23_LUXTRONIK2.pm
UPD FHEM/33_readingsGroup.pm
UPD FHEM/55_GDS.pm
UPD FHEM/59_PROPLANTA.pm
UPD FHEM/59_Twilight.pm
UPD FHEM/66_ECMD.pm
UPD FHEM/70_ENIGMA2.pm
UPD FHEM/70_JSONMETER.pm
UPD FHEM/70_PIONEERAVR.pm
UPD FHEM/72_FRITZBOX.pm
UPD FHEM/89_VCONTROL.pm
UPD FHEM/92_FileLog.pm
UPD FHEM/98_HMinfo.pm
UPD FHEM/98_RandomTimer.pm
UPD FHEM/98_SVG.pm
UPD FHEM/98_statistics.pm
UPD FHEM/Color.pm
UPD FHEM/HMConfig.pm
UPD FHEM/WMBus.pm
UPD FHEM/lib/UPnP/sonos_input_dock.jpg
UPD docs/commandref.html
UPD docs/commandref_DE.html
UPD www/jscolor/ct_background.svg
UPD www/jscolor/hue_background.svg

New entries in the CHANGED file:
  - fix: 66_ECMD: avoid reading from a closed connection in ECMD_READ
  - feature: 70_PIONEERAVR: readings for currentAlbum etc., more internals (network settings, moved some from readings to internals), new attributes volumeLimit & volumeLimitStraight

update finished, "shutdown restart" is needed to activate the changes.

in the log files, you find the same information
The answer to an update can also be "nothing to do... "
Do not make 2 update after another without rebooting

reset of the RASPI is bad; reboot is what you should do on a regular basis (weekly or dayly depending how stable is your system)

when you are more experienced (debugging yourself your problems), you can avoid rebooting and you can just resart fhem.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 04 Januar 2015, 20:20:49
nabend,
nach ausgiebiger recherge habe ich nun den erfolgreichen tip bekkommen und es mit " update force " geschafft das System zu aktualisieren. Auch Mythz ist nun auf 0.120 aktualisiert worden. Leider gibt mein Parameter  "insideTemp:" nach wie vor "-60" aus. Habt Ihr das Problem schon mal gehabt. 
Gruss
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Januar 2015, 20:51:23
@glücksgriff:
Erst mal herzlich willkommen im Forum. Die SEHR GUTE Nachricht ist, dass es mit der 404 auch funktioniert. Das hatten wir bislang nur vermutet, aber vor Dir hatte es niemand verifiziert. Das könnte uns bei der Argumentation gegenüber Stiebel Eltron helfen. Die haben ja nur Interesse an aktuellen Modellen.

Das insideTemp Thema ist etwas kompliziert. Die in sGlobal angezeigte Temperatur ist nicht die, die im externen Display angezeigt wird, sondern die, die die Anlage aus einem separat anzuschließenden Sensor ausliest. Bei der 303 wird dieser Sensor am Panel X5, Pin 5+6 (Bezeichnung "Raumfühler") angeschlossen. Schau mal in Deinem Installationsmanual nach, ob es das bei der 404 noch gibt.

Die Stelle, an der der Innentemperaturwert des externen Displays ausgelesen werden kann, hat noch Niemand gefunden (aber auch nicht wirklich Jemand danach gesucht).

Die in sGlobal angezeigte Luftfeuchtigkeit ist aber tatsächlich die aus dem externen Display. Bei mir weicht der gemessene Wert aber stark vom tatsächlichen ab. Ich habe das über einen linearen Offset nach dem auslesen korrigiert.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Januar 2015, 20:56:59
Zitat von: godmorgon am 04 Januar 2015, 14:56:19
I also think that the decoding of the relative humidity is not quite right. The value just posted by glücksgriff is absolutely identical to the one posted by willybauss in a different thread. In my case it is always set to 0.

In my case the values are definitely varying; comparing the values to situations in living room makes absolutely sense: having a lot of people inside gives higher values, cooking also shows increasing values.

But I always have a linear offset of approx. 11.5% between measured value and real one, e.g. if I see a measured value of 30% the real value in my living room is approx. 41.5%.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 04 Januar 2015, 20:59:12
@immi
Indeed 303x series don't seem to have humidity sensors. Since the humidity value is not provided on display I don't know what to search for in the binary values.

Some examples of my 0xfb messages (the bytes presumed to store Qc and Pel are marked):
01 00 54 fb fd a8 00 16 01 3d 01 08 02 69 01 e7 fd a8 fd a8 00 0d 01 2b 60 08 11 01 5e 01 5e 02 bc 00 00 00 00 00 15 00 19 00 00 00 00 01 2d 04 f2 45 d8 df 9f 3f c4 9b a6 07 c5 00 b1 01 6d 00 00 01 08 01 38 00 13 00 02 01 09 00 00 00 00 0f ff
01 00 69 fb fd a8 00 17 01 3d 01 08 02 78 01 e7 fd a8 fd a8 00 10 01 1d 60 08 11 01 5e 01 5e 02 bc 00 0e 00 18 00 14 00 19 00 00 00 00 01 3c 05 24 45 d7 6d 7d 3f cd 91 69 07 fa 00 b1 01 6f 00 00 01 07 01 3a 00 1d 00 0a 01 17 00 00 00 00 0f 23
01 00 ea fb fd a8 00 16 01 44 01 08 02 49 01 e6 fd a8 fd a8 00 1c 01 17 60 08 11 00 00 00 00 02 bc 00 00 00 00 00 14 00 19 00 00 00 00 01 4c 05 30 46 00 d5 8f 3f d4 7a e2 07 c5 00 b1 01 2a 00 00 01 06 01 44 ff f4 ff de 01 23 00 00 00 00 10 3e
I don't see how these huge values could possibly correspond to valid kWh.

I was able to decode the following THZ404SOL registers:
0a 033b - flow rate/Volumenstrom, 0.1 l/min
0a 064f - hum. masking time/Feuchte Maskierzeit, min
0a 0650 - hum. threshold value/Feuchte Schwellwert, %
0a 06a4 - output reduction/Leistungsreduktion, %
0a 06a5 - output increase/Leistungserhöhung, %
0a 09d1 - humidity protection/Feuchteschutz, bool
0a 09d2 - set humidity min/Feuchte Soll min, %
0a 09d3 - set humidity max/Feuchte Soll max, %

By the way, the 0x0c command seems to mirror the values of the 0x0b command.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Januar 2015, 21:11:06
humidity value can be evaluated from external display ONLY. If you don't have such a second display you can forget about this topic.
But I believe that all displays, even the built-in ones, have a humidity sensor and a temperature sensor installed. There's a short cut wire on display's back side, which identifies it as the built-in one, so that the firmware doesn't read out these values (because it doesn't make sense to deal with temperature and humidity values of heating room in basement).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Januar 2015, 21:14:44
a rough look on the actualPower_Pel values shows me values between approx. +18000 and -18000. 18kW power consumtion is far too much; and the negative values would mean that the heatpump generates electrical power, what I don't really believe ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 04 Januar 2015, 21:18:04
It is not mentioned in the manual of my THZ404SOL that I need any additional sensors to activate humidity protection. From the description I would expect that the humidity sensor is installed in the ventilation outlet. Why else should the heatpump activate ventilation after 24h with the humidity protection active and the fan set to stage 0? It sounds like it would test the air humidity.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 04 Januar 2015, 21:26:29
ok, you tell me news ... I never heard about humidity protection. The 303 doesn't have this feature.

But anyway the value in sGlobal shows the humidity measured by the external display. Having the  humidity protection feature in mind I believe that the 404 has another humidity sensor built in, which measures the exhaust air flow. This value must be read out in a different way.

PS:
Up to now I didn't realize that you have a 404. I thought glücksgriff is the first one here having a 404.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 04 Januar 2015, 22:52:16
Ok,
dann bin ich dann mal das Versuchskaninchen. Jetzt hab ich auch mal schnell im Installationsheft nachgesehen und volgende Zusatanschlüsse für Fühler gefunden.

TA                  Außentemperaturfühler  <------- ist ja besezt
TV                  Vorlauftemperaturfühler Mischerkreis   <---------- bei mir nicht angeschlossen
TR                  Raumtemperaturfühler <-------------------- hab ich eben mal einen Fühler angeschlossen und getestet. 18.6 C in meinem Keller. intime_temp ist der Zusatzfühler
TS                  Solartemperaturfühler <------------------------ bei mir nicht vorhanden

Einen Anschluss für den für einen externen Feuchtfühler konnte ich an der Heizung sowie im Installationsheft nicht finden, wobei es laut Stiebel Bedienungsanleitung eine LWZ Gültigkeit:17.01.2011 - 31.12.2013. und eine ab 01.01.2014 gibt.

Die Frage stelle ich mir jetzt nur was ich mit diesem zusätzlichen Fühler anstellen sollte. Raumeinfluss kann ich ja nur mit dem Zusatzdisplay realisieren, oder.

Gibt es eigentlich eine liste der Parameter aus der sGlobal ( möchte gerne die Heissgas und Kondensatortemperatur plotten ). Mit Parameter 7, und 8 kann er nichts finden
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Januar 2015, 00:47:34
Zitat von: godmorgon am 04 Januar 2015, 20:59:12
By the way, the 0x0c command seems to mirror the values of the 0x0b command.
not completely sometimes they seam to be equivalent, sometime not; if you look in my code

0Bxxx is for hc1
0Cxxx is for hc2
0Axxx is for fan and dhw...

but then there are exepetions in which the prefix  does not matter.
and then there are heatpumps versions in which it matters

I appreciate the creativity and the missing documentation of such a system :)
especially when one value is encoded in 2 registers like sBoostDHWTotal
or when time and date are encoded in 10 different ways in 10 different registers

Zitat von: glücksgriff am 04 Januar 2015, 22:52:16
Gibt es eigentlich eine liste der Parameter aus der sGlobal ( möchte gerne die Heissgas und Kondensatortemperatur plotten ). Mit Parameter 7, und 8 kann er nichts finden
I do not understand why you need a list for plotting hotgas from sGlobal

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Januar 2015, 08:34:40
Zitat von: glücksgriff am 04 Januar 2015, 22:52:16

Ok,
dann bin ich dann mal das Versuchskaninchen. Jetzt hab ich auch mal schnell im Installationsheft nachgesehen und volgende Zusatanschlüsse für Fühler gefunden.

TA                  Außentemperaturfühler  <------- ist ja besezt
TV                  Vorlauftemperaturfühler Mischerkreis   <---------- bei mir nicht angeschlossen
TR                  Raumtemperaturfühler <-------------------- hab ich eben mal einen Fühler angeschlossen und getestet. 18.6 C in meinem Keller. intime_temp ist der Zusatzfühler
TS                  Solartemperaturfühler <------------------------ bei mir nicht vorhanden

Einen Anschluss für den für einen externen Feuchtfühler konnte ich an der Heizung sowie im Installationsheft nicht finden, wobei es laut Stiebel Bedienungsanleitung eine LWZ Gültigkeit:17.01.2011 - 31.12.2013. und eine ab 01.01.2014 gibt.

Die Frage stelle ich mir jetzt nur was ich mit diesem zusätzlichen Fühler anstellen sollte. Raumeinfluss kann ich ja nur mit dem Zusatzdisplay realisieren, oder.

Gibt es eigentlich eine liste der Parameter aus der sGlobal ( möchte gerne die Heissgas und Kondensatortemperatur plotten ). Mit Parameter 7, und 8 kann er nichts finden
hotGasTemp und condenserTemp sind doch in sGlobal enthalten. Was brauchst Du mehr?

TR ist der richtige Anschluss. Kabel in den "Führungsraum" legen (meist nimmt man dafür das Wohnzimmer), Sensor dran, Raumeinfluss (p15RoomInfluenceHC1) einstellen, habe fertig. Evtl. noch eine Offsetkorrektur, weil die Sensoren plus Kabellänge nicht immer exakt die tatsächliche Raumtemperatur anzeigen.

Ein externer Feuchtefühler funktioniert nur mit dem externen Display. Das Ganze ist etwas  komisch aufgebaut. Für die LWZ/THZ 303 gilt:Für die 404 müsste nach meinem Verständnis zusätzlich gelten:
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Januar 2015, 08:46:59
Ich lese grade im Installationsmanual der 404:
Zitat5.8.9 Externes Bedienteil anschließen
Mit einem externen Bedienteil können Sie von Ihrer Wohnung
aus alle Funktionen des Geräts steuern und alle Einstellungen
vornehmen. Zusätzlich misst das externe Bedienteil die Raumtemperatur.
Falls gewünscht, nimmt dieser Wert Einfluss auf die
Heizkurve. Hiermit erreichen Sie, dass die Heizkurve abgesenkt
wird, wenn im Führungsraum, also dem Raum, in dem das Bedienteil
montiert ist, die Raumsolltemperatur überschritten wird
(z. B. durch Sonneneinstrahlung oder einen Holzofen).
Die Gewichtung des Raumeinflusses wird mit dem Parameter
Raume influss [MENÜ/He izen/He izkurve HK 1 oder per
Direktanwahl Parameter P15 und P18] eingestellt
Das klingt so, als ob das externe Display zwingend erforderlich wäre, um einen Raumeinfluss zu erreichen. Das glaube ich aber nicht. Ich denke eher, dass (wie bei der 303) dafür der Raumtemberaturfühler (Anschluss TR) ausreicht. Ein Anruf beim SE-Service sollte Klarheit bringen; oder einfach ausprobieren:Wenn sich bei diesen Tests die Heizkreis-Solltemperatur erwartungsgemäß beeinflussen lässt, dann brauchst Du für den Raumeinfluss kein externes Display.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 05 Januar 2015, 09:28:53
Zitat von: immi am 04 Januar 2015, 13:48:31
uploaded v 0121, tomorrow or this evening, you can update
changelog:

  • register interpretation from godmorgon implemented;
    http://forum.fhem.de/index.php/topic,13132.msg233992.html#msg233992
    for me it looks like "sFirmware-Id    Date: MAR 9 2011"
    if you know more about firmware-id or register FE, please share.
  • register 17 for old firmwares implemented; only Peter is affected

@ Peter: you should try : get Mythz sPxxxx
please post the reply of the register; please try to interprete it accordingly
look at the interpretation here http://www.haustechnikdialog.de/Forum/t/85548/Software-zum-Auslesen-der-Tecalor-THZ-303-SOL-ueber-RS232-o-a-Schnittstelle?page=9
maybe it works for you

Hallo immi,
das Update auf v0.121 hat funktioniert. Ich werde erst heute abend die Ergebnissen hier posten können.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 05 Januar 2015, 14:44:40
Zitat von: glücksgriff am 04 Januar 2015, 22:52:16
Ok,
dann bin ich dann mal das Versuchskaninchen. Jetzt hab ich auch mal schnell im Installationsheft nachgesehen und volgende Zusatanschlüsse für Fühler gefunden.

TA                  Außentemperaturfühler  <------- ist ja besezt
TV                  Vorlauftemperaturfühler Mischerkreis   <---------- bei mir nicht angeschlossen
TR                  Raumtemperaturfühler <-------------------- hab ich eben mal einen Fühler angeschlossen und getestet. 18.6 C in meinem Keller. intime_temp ist der Zusatzfühler
TS                  Solartemperaturfühler <------------------------ bei mir nicht vorhanden

Einen Anschluss für den für einen externen Feuchtfühler konnte ich an der Heizung sowie im Installationsheft nicht finden, wobei es laut Stiebel Bedienungsanleitung eine LWZ Gültigkeit:17.01.2011 - 31.12.2013. und eine ab 01.01.2014 gibt.

Die Frage stelle ich mir jetzt nur was ich mit diesem zusätzlichen Fühler anstellen sollte. Raumeinfluss kann ich ja nur mit dem Zusatzdisplay realisieren, oder.

Gibt es eigentlich eine liste der Parameter aus der sGlobal ( möchte gerne die Heissgas und Kondensatortemperatur plotten ). Mit Parameter 7, und 8 kann er nichts finden


Hallo,
Ich denk du hast einen falschen Senor angeschlossen.
Du hast bestimmt einen PT1000 Senor abgeklemmt. Es muss aber ein KTY 81-210 sein.

Klemme dein Sensor ab und Messe den Ohmischen Wert.
Schaue dann beim PT1000 und du wirst bei -60 Grad rauskommen.
http://www.ta.co.at/de/assets/Downloads/Datenblaetter/23Temperatursensoren/Datenblatt%20Temperatursensoren_1.1.pdf
Bitte beachte, dass die Brücke am Bedienteil (Heizung) noch entfernt werden muss.
Nach dem Reset kannst du im Bedienteil auswählen, wo der Sensor Einfluss haben soll.

Ich habe den wegen der größeren Masse verbaut:
http://www.pollin.de/shop/dt/NjY5OTE4OTk-/Bauelemente_Bauteile/Aktive_Bauelemente/Sensoren_Peltier_Elemente/Rohr_Anlegefuehler_mit_Sensor_KTY81_210_3_m.html

Viel Erfolg.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 05 Januar 2015, 14:57:51
Zitat von: willybauss am 04 Januar 2015, 21:26:29
ok, you tell me news ... I never heard about humidity protection. The 303 doesn't have this feature.

But anyway the value in sGlobal shows the humidity measured by the external display. Having the  humidity protection feature in mind I believe that the 404 has another humidity sensor built in, which measures the exhaust air flow. This value must be read out in a different way.

PS:
Up to now I didn't realize that you have a 404. I thought glücksgriff is the first one here having a 404.

As feature humity protection could also mean that water removal from the ventilated air is reduced or stopped if room humidity is too low. Alternatively it could be just a hygromter information that gives a display warning if humity or too high/low for health reasons. I use for this ELV MNS100TF and micromat too.

For the Raumfühler: Man muss ihn schon in das Wohnzimmer legen bzw. dort wo man sich am häufigsten aufhält. Der Aufbau ist simpel und ich hab mir das Teil über die 2 extraphase einer 5 poligen Steckdose, in den Wohnbezeich gelegt und der Fühle schaut seitlich aus einer Steckdose in der Ecke raus. Stellt man den Raumeinfluss hoch (so wie bei mir 80:20) ist das Wochnzimmer schön warm, weil exteren Heizquellen genutzt werden. Jedoch sind alle anderen Räume entsprechend kälter. Funktioniert gut bei Temp bis 0°C. Wird es merlklich kälter sollte man den Raumeinfluss runterschrauben, konnte ich aber noch nicht ausrteichend testen. Jede Veränderung braucht ein-zwei Tage Equilibrium-Zeit, in der der Verbrauch auch meist erhöht ist (wie bei Heizkurzenveränderungen).
Wie von willi merfach erwähnt muss die aus sGlobal ermittlete Temp noch korregiert werden (userreading) und zwar um genau den selben Korrekturwert, den man auch am LWZ Display einstellt. Aus Verbrauchssicht kann ich den Raumfühler empfehlen, wenn man viele externe Wärmequellen hat und einen Raum als Referenzraum nutzen will. Die Baufirma hat bei uns den Fühler nicht erwähnt bzw. verbaut.

edit: gassi hat recht! Richtigen Fühler anschliessen; der PT-1000 geht nicht. Misst nur -60°C
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Januar 2015, 16:30:23
Zitat von: Gassi am 05 Januar 2015, 14:44:40

Hallo,
Ich denk du hast einen falschen Senor angeschlossen.
Du hast bestimmt einen PT1000 Senor abgeklemmt. Es muss aber ein KTY 81-210 sein.

...
hä? Er schreibt doch, dass er nach Anschluss des Sensors 18,6° gemessen hat:
ZitatTR                  Raumtemperaturfühler <-------------------- hab ich eben mal einen Fühler angeschlossen und getestet. 18.6 C in meinem Keller. intime_temp ist der Zusatzfühler
Dann kann der Sensortyp nicht sooo falsch sein. Die -60!° waren, bevor er den Sensor angeschlossen hatte.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Januar 2015, 16:42:26
Zitat von: houseowner123 am 05 Januar 2015, 14:57:51
As feature humity protection could also mean that water removal from the ventilated air is reduced or stopped if room humidity is too low. Alternatively it could be just a hygromter information that gives a display warning if humity or too high/low for health reasons. I use for this ELV MNS100TF and micromat too.

Hier ein Auszug aus dem Manual der 404:
ZitatFeuchteschutzlüftung (Stufe 0)Das Gerät verfügt über eine Feuchteschutzregelung, die ihrGebäude vor Feuchteschäden schützen soll.Der Feuchteschutz sollte immer eingeschaltet werden. DerFeuchteschutz ist nur in der Lüfterstufe 0 wirksam. DerFeuchteschutz ist im Auslieferungszustand deaktiviert, d. h.der Parameter Fe uchteschutz hat den Wert 0 (AUS ). Für dasTrockenheizen muss der Parameter Fe uchteschutz den Wert0 (AUS) haben.Mit dem Parameter Fe uchteschutz schalten Sie die FeuchteschutzfunktionEin.Wenn die Lüftung ausgeschaltet wird (Stufe 0), wird dieFeuchteschutzlüftung aktiviert. In den ersten 24 Stundennach Abschalten der Lüftung sind die Lüfter ausgeschaltet.Danach prüft die Feuchteschutzschaltung in Intervallen voneiner Stunde, ob ein Lüften der Räume notwendig ist. Dazuwerden die Lüfter für die Dauer der Fe uchte Maskierzeit inder Stufe 1 betrieben. Überschreitet der gemessene Wert denFeuchtesollwert, werden beide Lüfter solange betrieben, bis derFeuchtesollwert um die Fe uchte Hysterese unterschritten wird.
Es handelt sich also eindeutig um den Schutz vor zu hoher Luftfeuchtigkeit.

Zitat von: houseowner123 am 05 Januar 2015, 14:57:51
Wie von willi merfach erwähnt muss die aus sGlobal ermittlete Temp noch korregiert werden (userreading) und zwar um genau den selben Korrekturwert, den man auch am internen LWZ Display einstellt.

Habe mal in rot noch etwas ergänzt. Das externe Display hat zwar auch einen Korrekturwert, der betrifft aber die Korrektur seines eigenen Sensors ... sorry, das ist ziemlich verwirrend, ich weiß ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 05 Januar 2015, 19:47:14
Hallo immi,

die Informationen vom Haustechnikdialog stimmen mit meinen Ergebnissen überein.
Hier die Antwort auf "get Mythz sPxxx"
E01700DA00D5006401A4019F0064020000006401A401


E017_______Dec________Wert________Header?_______________________
00DA_______218________21.8________Raumtemperatur Normalbetrieb_______P1
00D5_______213________21.3________Raumtemperatur Absenkbetrieb_______P2
0064_______100________10.0________Raumtemperatur Bereitschaft__________P3
01A4_______420________42.0________Brauchwassertemp. Normalbetrieb_____P4
019F_______415________41.5________Brauchwassertemp. Absenkbetrieb_____P5
0064_______100________10.0________Brauchwassertemp. Bereitschaft_______P6
__02_________2_________2__________Lüfterstufe Normalbetrieb____________P7
__00_________0_________0__________Lüfterstufe Absenkbetrieb____________P8
__00_________0_________0__________Lüfterstufe Bereitschaft______________P9
0064_______100________10.0________Heizkreistemperatur Handbetrieb_______P10
01A4_______420________42.0________Brauchwassertemperatur Handbetrieb__P11
__01_________1_________1__________Lüfterstufe Handbetrieb_____________P12


Was mir noch aufgefallen ist, dass bei "get Mythz sLast10errors" jetzt eine Fehlerinformation kommt.
"010046D101010017072F032200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
msg2 WInterface max repeat limited to 50".
Früher hat das problemlos funktioniert.
Get Mythz sGlobal funktioniert weiterhin ohne Probleme.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Januar 2015, 22:29:48
Hi Peter
I just uploaded v0122, you can update tomorrow
- pXX register for old firmware implemented (maybe you have a better name)
- max repeat increased limited to 60, before was 50
- actualPower_Qc: patched, there was a bufferoverflow, I took care of.
The value is still worng, but better. I do not understand completely how it is encoded. I will look tomorrow in it, if i find some time.

@Willy: the negative values are now gone
@godmorgon: it is not an energy (kWh) but a power kW or W or mW or uW, depending on the fancy encoding.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 05 Januar 2015, 22:52:36
Autor: willybauss
ZitathotGasTemp und condenserTemp sind doch in sGlobal enthalten. Was brauchst Du mehr?

das habe ich im sGlobal auch gelesen, leider stelle ich anscheinend zu doof an es im Plot-Editor einzupflegen.
Habe es mit versucht : "attr Mythz userReadings  evaporatorTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[7]}, condenserTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[8]}

Leider bekomme ich als Rückgabewert

condenserTemp                          dhwTemp:
hotGasTemp                               returnTemp:

wie müsste ich es im Plot-Editor einrichten.

Bezüglich dem "TR" Raumfühler. Es ist der orginale Fühler, und Temperaturen passen (zumindest mit 50 cm Leitung ). Werde die tage mal testen, was passiert wenn ich 2.Display und Raumfühler dran hab und Raumeinfluss einstelle.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 05 Januar 2015, 23:17:28
Zitat von: glücksgriff am 05 Januar 2015, 22:52:36
das habe ich im sGlobal auch gelesen, leider stelle ich anscheinend zu doof an es im Plot-Editor einzupflegen.
Habe es mit versucht : "attr Mythz userReadings  evaporatorTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[7]}, condenserTemp:sGlobal {(split ' ',ReadingsVal("Mythz","sGlobal",0))[8]}

Leider bekomme ich als Rückgabewert

Habe mir das userReading gar nicht angesehen, denn Du brauchst es nicht. Ein Wert, der in sGlobal enthalten ist, kann direkt aus sGlobal in den Plot verarbeitet werden. Einfach die entsprechende "Spaltennummer" innerhalb sGlobal im Plot-Editor eintragen. So ähnlich wie im angehängten ScreenDump (gelb markiert).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 05 Januar 2015, 23:40:13
Geniale Hilfe hier, auch für honkis wie mich. Ich habe es wie Du mir gerade beschrieben hast auch versucht leider ohne Erfolg.
Kannst du mir was du unter spaltennummer verstehst. Ich dachte die sGlobal von vorne duchzählen und bin deshalb auf 7 und 8 gekommen. Leider ohne erfolg, siehe bild.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 05 Januar 2015, 23:55:13
7 and 8 cannot be right: all value in sglobal are odd positions; the labels are in even

outsideTemp:  -1.5       flowTemp:   12.8    returnTemp: 12.9
pos4 .....         pos5     pos6            pos7   pos8            pos9
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: glücksgriff am 06 Januar 2015, 00:08:40
ok, genau das hat mir gefehlt. Vielen lieben dank
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 06 Januar 2015, 00:48:09
Zitat von: willybauss am 05 Januar 2015, 23:17:28
Habe mir das userReading gar nicht angesehen, denn Du brauchst es nicht. Ein Wert, der in sGlobal enthalten ist, kann direkt aus sGlobal in den Plot verarbeitet werden. Einfach die entsprechende "Spaltennummer" innerhalb sGlobal im Plot-Editor eintragen. So ähnlich wie im angehängten ScreenDump (gelb markiert).

Brauch ich schon, denn sGlobal korrigiert bei mir die Innentemperatur nicht. Die ist viel zu hoch. Also korrigier ich sie mit User readings. Oder ziehst Du Korrektur direkt im Plot-editor ab?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 Januar 2015, 02:07:44
Zitat von: houseowner123 am 06 Januar 2015, 00:48:09
Brauch ich schon, denn sGlobal korrigiert bei mir die Innentemperatur nicht. Die ist viel zu hoch. Also korrigier ich sie mit User readings. Oder ziehst Du Korrektur direkt im Plot-editor ab?
If you need it only for plotting, use the function field in the Ploteditor.
I prefer command line, because I like reproducibility:

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 '<TL>'
set ytics
set y2tics
set grid
set ylabel ""
set y2label ""
set yrange [0:1]
set y2range [0:2]

#FileLog 35:Mythz.sGlobal\x3a:0:
#FileLog 37:Mythz.sGlobal\x3a:0:
#FileLog 39:Mythz.sGlobal\x3a:0:
#FileLog 41:Mythz.sGlobal\x3a:0:
#FileLog 31:Mythz.sGlobal\x3a:0:
#FileLog 19:Mythz.sHC1\x3a::$fld[18]=~"summer"?0:1

plot "<IN>" using 1:2 axes x1y1 title 'Compressor' ls l1fill lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage3' ls l0 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage2' ls l4 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y1 title 'BoosterStage1' ls l3 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'HeatingCircuit_Pump' ls l5 lw 1 with lines,\
     "<IN>" using 1:2 axes x1y2 title 'winterMode' ls l2fill lw 0.5 with lines


As you see in the example, you can use  a perl function e.g. < $fld[18]=~"summer"?0:1" >.
The function can be simple or complex.
You just need something like
#FileLog 9:Mythz.sGlob*:0:$fld[8]+=50
Pay attention to the index in the perl function: I use 8 to indicate field 9.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 06 Januar 2015, 09:28:14
Zitat von: immi am 05 Januar 2015, 22:29:48
- max repeat increased limited to 60, before was 50
I appreciate your work very much but this is what I would call treatment of symptomps. Fhem had also truncated long messages when communicating with my 404. Until I set verbosity level to 5. I have never had this sort of issues with my test scripts scanning the THZ registers at the maximum possible rate.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 06 Januar 2015, 09:39:19
Zitat von: glücksgriff am 05 Januar 2015, 23:40:13
Geniale Hilfe hier, auch für honkis wie mich. Ich habe es wie Du mir gerade beschrieben hast auch versucht leider ohne Erfolg.
Kannst du mir was du unter spaltennummer verstehst. Ich dachte die sGlobal von vorne duchzählen und bin deshalb auf 7 und 8 gekommen. Leider ohne erfolg, siehe bild.
Ich mag honkis, die erst mal versuchen, sich selbst zu helfen, und die dann immer neue (bessere) Fragen stellen, anstatt die alten zu wiederholen  :) .
Hatte mir schon gedacht, dass dazu Rückfragen kommen; dummerweise ist mir dann der Rechner abgestürzt und ich konnte nicht mehr antworten. Als "Spalten" betrachte ich alles, was sich zwischen 2 Leerzeichen befindet. In Deinem Screenshot hattest Du für Warmwasser Spalte 8 angegeben; in meinem Screenshot war Brauchwasser (=Warmwasser) in Spalte 13. Am besten versucht man immer, anhand eines funktionierenden Beispiels (=meines) die notwendige Zählweise herauszufinden.

Dummerweise ist die Zählweise nicht immer einheitlich. Wenn ich es richtig in Erinnerung habe gilt:@houseowner123:
Beides ist möglich, wie immi bereits schreibt. Ich habe mich dennoch für die korrigierten Werte zu userReadings entschieden. Manchmal verwende ich auch das Charting Frontend; da wird es dann leichter, wenn die korrigierten Werte bereits im LogFile stehen.
Im Gegensatz zu immi bin ich aber kein Freund (mehr) davon, direkt in den config-Dateien zu editieren, egal ob fhem.cfg oder Plot-Config-Files. Das ist im Rest des FHEM-Forums ziemlich verpönt. Wozu gibt es schließlich die mehr oder weniger schicken UIs? Für Korrekturformeln gibt es im Plot-Editor die Spalte "Function". immis Beispiel sieht dann so aus wie im Screenshot (gelbe Markierung). Ich habe zusätzlich noch weitere Formeln (rote Pfeile), damit die Balken für Booster Stage 1 und Stage 2 nur 1/3 bzw. 2/3 Höhe haben. Sonst kann man die nicht unterscheiden. Das Ergebnis sehr ihr dann in Screenshot2. Hier hatte in der Nacht zum 29. Dezember der Booster in Stufe 1 beim heizen nachgeholfen. Bei der Warmwasserbereitung war er gelegentlich in Stufe 3 kurz aktiv.

Generell sollte man so wenig wie möglich userReaings haben. Ich hatte eine Zeit lang LogFiles von >25 MB pro Monat. Nach einer Aufräumaktion bin ich nun wieder bei ca.10 MB.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 06 Januar 2015, 09:43:54
Zitat von: godmorgon am 06 Januar 2015, 09:28:14
test scripts scanning the THZ registers at the maximum possible rate
sounds interresting ... can you share these scripts with us? Alternatively please send it as email attachment to me.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 06 Januar 2015, 12:03:18
Zitat von: godmorgon am 06 Januar 2015, 09:28:14
I appreciate your work very much but this is what I would call treatment of symptomps. Fhem had also truncated long messages when communicating with my 404. Until I set verbosity level to 5. I have never had this sort of issues with my test scripts scanning the THZ registers at the maximum possible rate.
Hi godmorgon
this is a philosophical/religius decision. You have a tradeof between stability and speed. I changed the decision 3 times. Since September I stick to the repeat solution.... but let me explain...

Root cause
There is a problem "trunkaded messages" coming from hardware.
The problem comes from a serial interface with only 2 cables connected, because there is no way to detect with hardware when a message is really finished.
Think to a message like 123000000123000000000004560000
Some USB-serial interfaces have better driver than other.... but in extreme conditions all have this problem.
If you direcly connect the heatpump with USB, this issue does not come. Nevertheless other problems appear.

100% Corrective action 1
Hardware flow control in addition to two-way data: the RTS and CTS lines are added in a 5-wire version.
This solution is not practicable for me.

99.9% Corrective action 2
you wait enough before reading. There are 9 different heat-pumps-types using THZ-FHEM.
This solution is not practicable because you should adapt the wait time to the different hardware.
Moreover you have always to take the worst-case wait-time. This means long wait-times also for short messages.
Your script (port to py) uses this approach.

99.9% Corrective action 3
I use insider information on the messages: I repeat endlessly the serial-reading as long as you get a certain pattern (e.g 1003).
It  is 100% reliable, and does not block fhem for long. Short messages are read very very very fast. Longer messages, this consumes slightly more cpu.
Why Peter had problems, if it were 100% reliable? easy, I never trust my software  ;D  I do not like endless loops. Therefore I limited the maximum repeat number. In the worst case the maximum repeat number is the number of bytes.
I will increase this number depending on user need.
Marcus and all directusb-users need 1 repeat
I never needed more than 5.
Willy needs 10
Peter needs 60+
This number cannot be longer than the message length.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 00:03:38
v 0123 uploaded
- actualPower_Qc and actualPower_pEl fixed

the encoding was tricky, they must be very important because are the only values which stieben eltron encodes with 32bits.

My interpretation:
actualPower_Qc [kW] --> differential in time of Heat_Qc
actualPower_pEl [kW] --> differential in time of ElectricalEnergy (electrical power from the plug)
If you make an avarage of their ratio over time (weighted mean over time), you should get the CoefficientOfPerformance.
Last year, I thought to check their ratio and write me an allert email, if it goes behond a threshold ... then I forgot to dig further.

feedback is welcome
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Januar 2015, 01:11:08
willy: Thanks for the explanation. your picture said more than 1000 words. Was everything I needed. No more slow graphs via user readings! :)

immi: thanks for the update looking forward to the corrected Arbeitszahl! Love it!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 07 Januar 2015, 09:07:32
Zitat von: immi am 05 Januar 2015, 22:29:48
Hi Peter
I just uploaded v0122, you can update tomorrow
- pXX register for old firmware implemented (maybe you have a better name)
- max repeat increased limited to 60, before was 50
- actualPower_Qc: patched, there was a bufferoverflow, I took care of.
The value is still worng, but better. I do not understand completely how it is encoded. I will look tomorrow in it, if i find some time.

@Willy: the negative values are now gone
@godmorgon: it is not an energy (kWh) but a power kW or W or mW or uW, depending on the fancy encoding.
Hallo immi,
mit der Version V0122 funktioniert mein Register "sLast10errors" wieder. Vielen Dank.
Das neue Register "pXX" könnte man z.B. "p1-12" nennen, da hier die Parameter 1-12 abgefragt werden.
Gruss
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 12:27:57
Zitat von: peter456 am 07 Januar 2015, 09:07:32
Das neue Register "pXX" könnte man z.B. "p1-12" nennen, da hier die Parameter 1-12 abgefragt werden.
p01-p12; deploy by next major change.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 13:06:10
Hallo,

ich wollte mich mal zurück melden, ist ja schon einiges passiert hier, hatte heute morgen wieder Stiebel Eltron im Hause, bei meiner Anlage ist ab und zu das Heizkreis und Warmwasser Ventil hängen geblieben. Dadurch hatte ich ab und zu 47 °C Vorlauf Temperatur in der Fußbodenheizung. Ventil getauscht und hoffen wir mal das es besser wird.

Was mir nun aber Gedanken macht ist die COP.
sHeatDHWTotal 3682 kWh /  sElectrDHWTotal 1598 kWh = DHW_COP= 2,301
sHeatHCTotal 6981 kWh / sElectrHCTotal 2514 kWh = Heat_COP = 2,777

Habe vorgestern ne Wartung gemacht und dabei ist mir das aufgefallen, die Werte stimmen auch überein mit dem was ich im Gerät auslese. Der Monteur meinte das es keine verlässliche Angabe ist. Die Gezählte Energie das würde nicht richtig laufen...

Der Plattenwärmetauscher war leicht vereist aber hab ihn halt mal richtig sauber gemacht aber das war alles im normalen Bereich nach einem Jahr.

Allein die aktuellen Werte.

von 0 Uhr bis jetzt 13 Uhr hatten wir min 0,7 °C bis aktuell 2,5 °C also im guten Arbeitsbereich der Wärmepumpe.

sHeatHCDay 8870 Wh / sElectrHCDay 2968 Wh = HeatDay_COP = 2,989

Das ist schon nicht gut....

Ich habe nun die aktuellste Softaware. 5.19.316

@IMMI gibt es die möglichkeit den Volumenstrom zu erfassen, bei mir ist er in den Istwerten aufgeführt.

Daruas könnte man ja die Wärmeenergie erfassen.

(http://upload.wikimedia.org/math/e/5/4/e542c3343daa526b9a3800c3d843d35e.png)
http://de.wikipedia.org/wiki/W%C3%A4rmez%C3%A4hler (http://de.wikipedia.org/wiki/W%C3%A4rmez%C3%A4hler)

Muss jetzt erstmal die COP in den griff bekommen, das ja echt grausam. Könnte es vielleicht sein das der Volumenstromsensor einen hat? Schon komisch.
Am meisten könnte ich mich aber aufregen über den Techniker der sagt ja das sind keine genauen Werte...



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 15:09:15
Zitat von: belu am 07 Januar 2015, 13:06:10
Was mir nun aber Gedanken macht ist die COP.
sHeatDHWTotal 3682 kWh /  sElectrDHWTotal 1598 kWh = DHW_COP= 2,301
sHeatHCTotal 6981 kWh / sElectrHCTotal 2514 kWh = Heat_COP = 2,777
Das Verhältnis zwischen DHW und Heat ist vernünftig. DHW hat wegen der höheren Solltemperatur generell schlechte Voraussetzungen für einen vernünftigen Wirkungsgrad (generell bei Wärmepumpen). Aber der COP ist tatsächlich sehr niedrig. Bei mir ist es ca. 3,7 (Heat). Hat denn evtl. der Heizstab mitgeheizt? Wie man die dafür notwendige Grafik baut habe ich grade gestern oder vorgestern hier als Screendump veröffentlicht.

Wie hoch ist denn die Spreizung (=Differenz zwischen Vor- und Rücklauftemperatur), gemessen während eines Heizzyklus? Die sollte schon bei ca. 5° sein, ist sehr oft viel zu gering.

Die Volumenstrommessung ist in die Software eingebaut, im Fachmannmenü zu erreichen. Wenn Du den dafür notwendigen Code brauchst => Email an mich.

Wenn die Spreizung zu gering ist kannst Du das über eine Reduzierung der Pumpenleistung erreichen. Dann aber zwingend anschließend die Volumenstrommessung machen, denn bei zu geringem Wert (550 Liter pro Minute bei der 303) geht die Anlage in einen Hochdruckfehlerzustand.

Weitere Möglichkeit für den schlechten COP: Du verwendest Raumthermostate, dadurch stimmt die Raumtemperatur, aber die Heizkurve ist evtl. viel höher eingestellt als notwendig. Dann taktet die Anlage unnötig oft => Kaltlaufverluste überwiegen, wie beim Auto im Kurzstreckenverkehr. Das kannst Du herausfinden, indem Du alle Thermostate voll aufdrehst. Wenn es dann (6 - 12 Stunden warten muss man schon auf ein vernünftiges Ergebnis) extrem warm in den Räumen wird, dann ist die Heizkurve viel zu hoch eingestellt. Bei diesem Test sollten die Räume eigentlich nur 1 - 2° wärmer werden als mit Thermostat.

Was noch sein kann: Dein Bau ist noch feucht (Bauaustrocknung). Aber dann wären nur die Heizkosten hoch, aber der COP würde stimmen.

Setze doch mal bitte mal einen Plot der Heizparameter hier rein. Ein sinnvolles gplot File dafür habe ich im April oder Mai hier veröffentlicht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 15:15:16
COP für DHW ist bei mir 2,85.

Was noch sein kann: bei den Total-Werten sind natürlich alle Heizzyklen seit Installation der Anlage enthalten. Grade in der Bauphase (Bauaustrocknung, Estrichtrocknung) schlägt der Heizstab überaus hoch rein. Auch das ist in diesen Werten reflektiert. Deshalb besser mal die Differenzwerte zwischen heute und z.B. Anfang Dezember als Rechenbasis nehmen. Die Werte findest du ja im Logfile.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Januar 2015, 15:27:49
willy: Das Thema hatten wir ja schon mal mit der Spreizung. Gibt es da nicht 2 Zirkulationspumpen, eine für den Vor- und ein für den Rücklauf? Eine steht auf 5 , die andere auf 9?
Ist diese hier auch bei Dir verbaut: http://www.dimplex.de/media/Montageanweisungen_SYS/5_Zubehoer/neutral_upe7025-12032_fd9206_de-gb-fr.pdf

Falls ja, wie sind denn Deine Einstellungen? Und noch mal zur Spreizung: Flow and Return machen ja so hyperbel-artige Kurven - sie nähern sich an (bis sie gleich sind) um sich dann wieder von einider zu entfernen? Jetzt meine Frage: Sind Deine 5°C Spreizung der Maximalwert, wie Vor-und Rücklauf ausanderenliegen? Falls ich mich unklar ausdrücke, schicke ich heute abend noch mal ein Bild der Graphen. Ich plotte immer auch heat Temp und setheat temp, was sehr schön den Raumeinfluss zeigt.

Tom
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 16:06:22
Hallo,

Bin gerade auf der Arbeit und hab die Werte nicht zur Verfügung, ist ganz flach eingestellt die Heizkurve 35 zu 20 Grad Steigung 0.25 damit wird auch alles warm. Bau ist trocken wird schon 2 Jahre beheizt. Estrich wurde mit einem anderem Gerät getrocknet um höhere Vorlauf Temperaturen zu bekommen.
Vorlauf zu Rücklauf sind so 5-6 Grad Differenz. 30 zu 24 28 zu 23 je nach dem...
Der Bivalenzpunkt ist bei mir bei -5 Grad und die Zusatzheizung nicht im Betrieb.

Ich denke da stimmt was nicht mit dem Volumenstromsensor. Aktuell benötige die bei 0 Grad so 10 bis 12 kW elektrisch im 140 qm auf 20 Grad zu heizen. Ist das zu viel?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 16:19:37
Zitat von: houseowner123 am 07 Januar 2015, 15:27:49
willy: Das Thema hatten wir ja schon mal mit der Spreizung.
Es gibt eine Pumpe fürs Warmwasser und eine für den Heizkreis. Separate Pumpen für Vor- und Rücklauf würden bei Flüssigkeiten (=nicht kompressibel) ja keinen Sinn machen. Bitte ggf. im Installationsmanual nachsehen. Die Einstellung der Warmwasserpumpe soll lt. Manual geschehen und nicht verändert werden. Die Heizkreispumpe dann halt lt. Spreizung anpassen. Werte anzugeben ist sinnlos, da sie von den örtlichen Gegebenheiten abhängen.

Die Messung der Spreizung mache ich eher im "flachen" Teil, also eher gegen Ende des Heizzyklus.

Die bei mir verbaute Pumpe sieht zumindest äußerlich gleich aus.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 16:48:18
Zitat von: belu am 07 Januar 2015, 16:06:22
... ist ganz flach eingestellt die Heizkurve 35 zu 20 Grad Steigung 0.25 damit wird auch alles warm.
So kann man da nichts dazu sagen. Steigung, Fußpunkt und Hysteresen sind das Mindeste, was Du angeben solltest. Dass es damit warm wird glaube ich sofort - fragt sich nur ob zu warm ... ==> Thermostattest wie oben beschrieben. Spreizung scheint zu passen.

Außerdem gibt es ==> Bitte gib mal die Bauweise an: Hier (http://nesa1.uni-siegen.de/index.htm?/softlab/casanova_3.htm) kann man auch die Daten seines Hauses eingeben und bekommt eine theoretische Berechnung der erforderlichen Heizenergie. Das Ergebnis dient aber nur zum Vergleich mit anderen, genauso berechneten Häusern. Echte Heizkosten kommen dabei nicht raus (bei mir lag der Wert um >50% daneben).

Ich hätte gerne einen Screenshot über 24 Stunden, ähnlich wie der angehängte. Das erforderliche gplot File habe ich angehängt. Evtl. musst Du etwas editieren, falls Du z.B. keinen Innentemperatursensor hast.

Meine Heizkosten fürs ganze letzte Jahr waren 2184 kWh. Diesen Wert solltest Du ja Anfang Januar sehr aktuell haben.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 17:33:53
Zitat von: willybauss am 07 Januar 2015, 16:48:18
Außerdem gibt es

       
  • gut und schlecht isolierte Häuser
  • Häuser ohne Blower Door Test  :-\
  • Leute, die permanent mit schräg gestelltem Fenster lüften
  • usw. zsw.
==> Bitte gib mal die Bauweise an:

       
  • Wandaufbau oder direkt den U-Wert (http://www.u-wert.net/ (http://www.u-wert.net/))
  • dito für Dach
  • Aufbau und U-Wert der Fenster und Außentüren
  • Ergebnis des Blower Door Tests
  • Stockwerke
  • Keller? wenn ja: Perimeterdämmung: Woraus und wie dick?
  • Dämmung unter der Bodenplatte? wenn ja: Perimeterdämmung: Woraus und wie dick?
  • thermische Solarzellen zusätzlich verbaut? wenn ja: Details (Größe, Typ)
  • Holzofen? wenn ja: Details (Größe, Luft oder mit Anschluß an die FB-Heizung)


@ Willi,

also es ist gut Isoliert, Neubau 2013 Enev 40 Energiesparhaus Blowerdoortest 0,5 also Passivhaus dicht.
Ist Holzständer durch die Aussage Enev 40 sollte der rest eigentlich ok sein. Ich hab irgendwas von dem Energieausweis von 8000 KW Primärenergiebedarf im kopf.


hier mal das Setup:

[/list]Readings
AussenTemp

0.3

2015-01-07 17:22:05
KollektorTemp

-60

2015-01-07 17:07:04
Rel_humidity

0

2015-01-03 15:26:28
RuecklaufTemp

25.4

2015-01-07 17:22:05
VorlaufTemp

31.3

2015-01-07 17:17:05
WWTemp

49.7

2015-01-07 17:22:05
dhw_temp

43.1

2015-01-03 15:26:28
flow_temp

43.4

2015-01-03 15:26:28
inside_temp

22.2

2015-01-03 15:26:28
outside_temp

1

2015-01-03 15:26:28
p01RoomTempDayHC1

21 °C

2015-01-07 14:06:44
p01RoomTempDayHC1SummerMode

25 °C

2015-01-07 14:07:34
p01RoomTempDayHC2

20 °C

2015-01-07 14:08:19
p01RoomTempDayHC2SummerMode

21 °C

2015-01-07 14:07:51
p02RoomTempNightHC1

21 °C

2015-01-07 14:07:23
p02RoomTempNightHC1SummerMode

25 °C

2015-01-07 14:07:47
p02RoomTempNightHC2

20 °C

2015-01-07 14:06:33
p02RoomTempNightHC2SummerMode

21 °C

2015-01-07 14:07:54
p03RoomTempStandbyHC1

16 °C

2015-01-07 14:06:43
p03RoomTempStandbyHC1SummerMode

30 °C

2015-01-07 14:07:50
p03RoomTempStandbyHC2

16 °C

2015-01-07 14:08:07
p03RoomTempStandbyHC2SummerMode

30 °C

2015-01-07 14:06:51
p04DHWsetDayTemp

47 °C

2015-01-07 14:06:21
p05DHWsetNightTemp

47 °C

2015-01-07 14:07:53
p06DHWsetStandbyTemp

10 °C

2015-01-07 14:07:11
p07FanStageDay

1

2015-01-07 14:06:35
p08FanStageNight

1

2015-01-07 14:07:40
p09FanStageStandby

0

2015-01-07 14:06:54
p11DHWsetManualTemp

10 °C

2015-01-07 14:08:01
p13GradientHC1

0.25

2015-01-07 14:07:29
p14LowEndHC1

2 K

2015-01-07 14:06:47
p15RoomInfluenceHC1

40 %

2015-01-07 14:06:50
p16GradientHC2

0.25

2015-01-07 14:07:42
p17LowEndHC2

2 K

2015-01-07 14:08:02
p18RoomInfluenceHC2

10240 %

2015-01-07 14:07:46
p19FlowProportionHC1

30 %

2015-01-07 14:07:22
p21Hist1

3 K

2015-01-07 14:06:20
p22Hist2

2 K

2015-01-07 14:06:55
p23Hist3

3 K

2015-01-07 14:06:17
p24Hist4

2 K

2015-01-07 14:06:25
p25Hist5

1 K

2015-01-07 14:07:44
p29HistAsymmetry

2

2015-01-07 14:07:19
p30integralComponent

100 Kmin

2015-01-07 14:06:30
p33BoosterTimeoutDHW

20 min

2015-01-07 14:06:57
p37Fanstage1AirflowInlet

120 m3/h

2015-01-07 14:07:17
p38Fanstage2AirflowInlet

170 m3/h

2015-01-07 14:07:37
p39Fanstage3AirflowInlet

281 m3/h

2015-01-07 14:06:42
p40Fanstage1AirflowOutlet

125 m3/h

2015-01-07 14:07:56
p41Fanstage2AirflowOutlet

174 m3/h

2015-01-07 14:06:29
p42Fanstage3AirflowOutlet

300 m3/h

2015-01-07 14:07:00
p43UnschedVent3

5 min

2015-01-07 14:07:09
p44UnschedVent2

5 min

2015-01-07 14:08:04
p45UnschedVent1

5 min

2015-01-07 14:07:05
p46UnschedVent0

5 min

2015-01-07 14:06:33
p49SummerModeTemp

17 °C

2015-01-07 14:06:41
p50SummerModeHysteresis

2 K

2015-01-07 14:06:19
p54MinPumpCycles

1

2015-01-07 14:06:56
p55MaxPumpCycles

50

2015-01-07 14:07:46
p56OutTempMaxPumpCycles

0 °C

2015-01-07 14:07:44
p57OutTempMinPumpCycles

20 °C

2015-01-07 14:06:27
p75passiveCooling

0

2015-01-07 14:06:35
p78DualModePoint

-5 °C

2015-01-07 14:06:39
p79BoosterTimeoutHC

60 min

2015-01-07 14:06:38
p83DHWsetSolarTemp

60 °C

2015-01-07 14:06:53
p99FanStageParty

3

2015-01-07 14:07:38
pHolidayBeginDay

1

2015-01-07 14:07:56
pHolidayBeginMonth

1

2015-01-07 14:07:32
pHolidayBeginTime

00:00

2015-01-07 14:08:09
pHolidayBeginYear

0

2015-01-07 14:06:54
pHolidayEndDay

14

2015-01-07 14:07:55
pHolidayEndMonth

3

2015-01-07 14:07:53
pHolidayEndTime

00:00

2015-01-07 14:07:33
pHolidayEndYear

13

2015-01-07 14:07:38
pOpMode

automatic

2015-01-07 14:07:17
party-time

00:00--00:00

2015-01-07 14:06:18
programDHW_Fr_0

00:00--24:00

2015-01-07 14:06:23
programDHW_Fr_1

n.a.--n.a.

2015-01-07 14:07:45
programDHW_Fr_2

n.a.--n.a.

2015-01-07 14:07:11
programDHW_Mo-Fr_0

00:00--24:00

2015-01-07 14:07:23
programDHW_Mo-Fr_1

n.a.--n.a.

2015-01-07 14:08:14
programDHW_Mo-Fr_2

n.a.--n.a.

2015-01-07 14:06:48
programDHW_Mo-So_0

00:00--24:00

2015-01-07 14:07:47
programDHW_Mo-So_1

n.a.--n.a.

2015-01-07 14:08:12
programDHW_Mo-So_2

n.a.--n.a.

2015-01-07 14:07:21
programDHW_Mo_0

00:00--24:00

2015-01-07 14:08:10
programDHW_Mo_1

n.a.--n.a.

2015-01-07 14:07:18
programDHW_Mo_2

n.a.--n.a.

2015-01-07 14:06:22
programDHW_Sa-So_0

00:00--24:00

2015-01-07 14:06:22
programDHW_Sa-So_1

n.a.--n.a.

2015-01-07 14:06:57
programDHW_Sa-So_2

n.a.--n.a.

2015-01-07 14:08:17
programDHW_Sa_0

00:00--24:00

2015-01-07 14:06:52
programDHW_Sa_1

n.a.--n.a.

2015-01-07 14:07:35
programDHW_Sa_2

n.a.--n.a.

2015-01-07 14:08:11
programDHW_So_0

00:00--24:00

2015-01-07 14:07:26
programDHW_So_1

n.a.--n.a.

2015-01-07 14:06:16
programDHW_So_2

n.a.--n.a.

2015-01-07 14:07:40
programDHW_Th_0

00:00--24:00

2015-01-07 14:08:12
programDHW_Th_1

n.a.--n.a.

2015-01-07 14:06:41
programDHW_Th_2

n.a.--n.a.

2015-01-07 14:07:43
programDHW_Tu_0

00:00--24:00

2015-01-07 14:06:32
programDHW_Tu_1

n.a.--n.a.

2015-01-07 14:07:27
programDHW_Tu_2

n.a.--n.a.

2015-01-07 14:07:06
programDHW_We_0

00:00--24:00

2015-01-07 14:07:49
programDHW_We_1

n.a.--n.a.

2015-01-07 14:08:10
programDHW_We_2

n.a.--n.a.

2015-01-07 14:07:24
programFan_Fr_0

09:00--21:00

2015-01-07 14:07:28
programFan_Fr_1

n.a.--n.a.

2015-01-07 14:06:31
programFan_Fr_2

n.a.--n.a.

2015-01-07 14:06:36
programFan_Mo-Fr_0

09:00--21:00

2015-01-07 14:08:16
programFan_Mo-Fr_1

n.a.--n.a.

2015-01-07 14:07:43
programFan_Mo-Fr_2

n.a.--n.a.

2015-01-07 14:07:59
programFan_Mo-So_0

09:00--21:00

2015-01-07 14:07:26
programFan_Mo-So_1

n.a.--n.a.

2015-01-07 14:06:28
programFan_Mo-So_2

n.a.--n.a.

2015-01-07 14:07:10
programFan_Mo_0

09:00--21:00

2015-01-07 14:07:58
programFan_Mo_1

n.a.--n.a.

2015-01-07 14:07:37
programFan_Mo_2

n.a.--n.a.

2015-01-07 14:07:59
programFan_Sa-So_0

09:00--21:00

2015-01-07 14:07:29
programFan_Sa-So_1

n.a.--n.a.

2015-01-07 14:06:42
programFan_Sa-So_2

n.a.--n.a.

2015-01-07 14:07:27
programFan_Sa_0

09:00--21:00

2015-01-07 14:06:30
programFan_Sa_1

n.a.--n.a.

2015-01-07 14:08:07
programFan_Sa_2

n.a.--n.a.

2015-01-07 14:07:08
programFan_So_0

09:00--21:00

2015-01-07 14:07:10
programFan_So_1

n.a.--n.a.

2015-01-07 14:08:01
programFan_So_2

n.a.--n.a.

2015-01-07 14:06:37
programFan_Th_0

09:00--21:00

2015-01-07 14:08:04
programFan_Th_1

n.a.--n.a.

2015-01-07 14:06:27
programFan_Th_2

n.a.--n.a.

2015-01-07 14:07:30
programFan_Tu_0

09:00--21:00

2015-01-07 14:07:04
programFan_Tu_1

n.a.--n.a.

2015-01-07 14:08:16
programFan_Tu_2

n.a.--n.a.

2015-01-07 14:07:20
programFan_We_0

09:00--21:00

2015-01-07 14:07:39
programFan_We_1

n.a.--n.a.

2015-01-07 14:07:57
programFan_We_2

n.a.--n.a.

2015-01-07 14:07:12
programHC1_Fr_0

00:00--24:00

2015-01-07 14:07:50
programHC1_Fr_1

n.a.--n.a.

2015-01-07 14:06:38
programHC1_Fr_2

n.a.--n.a.

2015-01-07 14:07:52
programHC1_Mo-Fr_0

00:00--24:00

2015-01-07 14:06:40
programHC1_Mo-Fr_1

n.a.--n.a.

2015-01-07 14:06:45
programHC1_Mo-Fr_2

n.a.--n.a.

2015-01-07 14:06:36
programHC1_Mo-So_0

00:00--24:00

2015-01-07 14:07:08
programHC1_Mo-So_1

n.a.--n.a.

2015-01-07 14:07:25
programHC1_Mo-So_2

n.a.--n.a.

2015-01-07 14:07:03
programHC1_Mo_0

00:00--24:00

2015-01-07 14:07:14
programHC1_Mo_1

n.a.--n.a.

2015-01-07 14:08:03
programHC1_Mo_2

n.a.--n.a.

2015-01-07 14:06:45
programHC1_Sa-So_0

00:00--24:00

2015-01-07 14:07:05
programHC1_Sa-So_1

n.a.--n.a.

2015-01-07 14:08:18
programHC1_Sa-So_2

n.a.--n.a.

2015-01-07 14:06:53
programHC1_Sa_0

00:00--24:00

2015-01-07 14:07:12
programHC1_Sa_1

n.a.--n.a.

2015-01-07 14:06:26
programHC1_Sa_2

n.a.--n.a.

2015-01-07 14:07:58
programHC1_So_0

00:00--24:00

2015-01-07 14:07:32
programHC1_So_1

n.a.--n.a.

2015-01-07 14:08:20
programHC1_So_2

n.a.--n.a.

2015-01-07 14:06:25
programHC1_Th_0

00:00--24:00

2015-01-07 14:08:19
programHC1_Th_1

n.a.--n.a.

2015-01-07 14:08:05
programHC1_Th_2

n.a.--n.a.

2015-01-07 14:07:04
programHC1_Tu_0

00:00--24:00

2015-01-07 14:07:30
programHC1_Tu_1

n.a.--n.a.

2015-01-07 14:06:59
programHC1_Tu_2

n.a.--n.a.

2015-01-07 14:08:18
programHC1_We_0

00:00--24:00

2015-01-07 14:07:15
programHC1_We_1

n.a.--n.a.

2015-01-07 14:06:34
programHC1_We_2

n.a.--n.a.

2015-01-07 14:07:31
programHC2_Fr_0

n.a.--n.a.

2015-01-07 14:07:41
programHC2_Fr_1

n.a.--n.a.

2015-01-07 14:07:14
programHC2_Fr_2

n.a.--n.a.

2015-01-07 14:08:08
programHC2_Mo-Fr_0

00:00--24:00

2015-01-07 14:06:39
programHC2_Mo-Fr_1

n.a.--n.a.

2015-01-07 14:07:48
programHC2_Mo-Fr_2

n.a.--n.a.

2015-01-07 14:07:55
programHC2_Mo-So_0

00:00--24:00

2015-01-07 14:08:00
programHC2_Mo-So_1

n.a.--n.a.

2015-01-07 14:07:07
programHC2_Mo-So_2

n.a.--n.a.

2015-01-07 14:06:49
programHC2_Mo_0

n.a.--n.a.

2015-01-07 14:06:24
programHC2_Mo_1

n.a.--n.a.

2015-01-07 14:07:36
programHC2_Mo_2

n.a.--n.a.

2015-01-07 14:06:44
programHC2_Sa-So_0

00:00--24:00

2015-01-07 14:08:06
programHC2_Sa-So_1

n.a.--n.a.

2015-01-07 14:08:13
programHC2_Sa-So_2

n.a.--n.a.

2015-01-07 14:07:35
programHC2_Sa_0

n.a.--n.a.

2015-01-07 14:07:16
programHC2_Sa_1

n.a.--n.a.

2015-01-07 14:06:29
programHC2_Sa_2

n.a.--n.a.

2015-01-07 14:07:02
programHC2_So_0

n.a.--n.a.

2015-01-07 14:07:21
programHC2_So_1

n.a.--n.a.

2015-01-07 14:08:09
programHC2_So_2

n.a.--n.a.

2015-01-07 14:07:34
programHC2_Th_0

n.a.--n.a.

2015-01-07 14:07:13
programHC2_Th_1

n.a.--n.a.

2015-01-07 14:07:41
programHC2_Th_2

n.a.--n.a.

2015-01-07 14:07:01
programHC2_Tu_0

n.a.--n.a.

2015-01-07 14:06:47
programHC2_Tu_1

n.a.--n.a.

2015-01-07 14:08:21
programHC2_Tu_2

n.a.--n.a.

2015-01-07 14:06:51
programHC2_We_0

n.a.--n.a.

2015-01-07 14:07:00
programHC2_We_1

n.a.--n.a.

2015-01-07 14:08:15
programHC2_We_2

n.a.--n.a.

2015-01-07 14:06:24
return_temp

39.6

2015-01-03 15:26:28
sBoostDHWTotal

547 kWh

2015-01-07 14:07:15
sBoostHCTotal

0 kWh

2015-01-07 14:08:13
sDHW

dhw_temp: 47.6 outside_temp: 1.3 dhw_set_temp: 50 comp_block_time: 1183 x20: 4104 heat_block_time: 1183 x28: 513 x32: 1 x36: 43202

2015-01-07 14:08:15
sElectrDHWDay

1379 Wh

2015-01-07 14:07:18
sElectrDHWTotal

1598 kWh

2015-01-07 14:08:06
sElectrHCDay

2893 Wh

2015-01-07 14:06:18
sElectrHCTotal

2514 kWh

2015-01-07 14:06:48
sFirmware

version: 5.19

2015-01-07 14:07:07
sFirmware-Id

Date: DEC 10 2014

2015-01-07 14:07:24
sGlobal

outsideTemp: 0.3 flowTemp: 31.3 returnTemp: 25.4 hotGasTemp: 69.8 dhwTemp: 49.7 flowTempHC2: -60 evaporatorTemp: -3.4 condenserTemp: 27.7 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 31 inputVentilatorPower: 30 mainVentilatorPower: 60 outputVentilatorSpeed: 24 inputVentilatorSpeed: 24 mainVentilatorSpeed: 17 outside_tempFiltered: 0.6 relHumidity: 0 dewPoint: 0 P_Nd: 3.68 P_Hd: 12.77 actualPower_Qc: 4949.592 actualPower_Pel: 1.743 collectorTemp: -60 insideTemp: 23.7

2015-01-07 17:22:05
sHC1

outsideTemp: 0.4 x08: -40.5 returnTemp: 25.3 integralHeat: -11 flowTemp: 31.2 heatSetTemp: 27.4 heatTemp: 27 seasonMode: winter integralSwitch: 100 opMode: normal roomSetTemp: 21

2015-01-07 17:17:54
sHC2

outsideTemp: 1.3 returnTemp: 23 vorlaufTemp: -60 heatSetTemp: 0 heatTemp: 0 stellgroesse: 0 seasonMode: winter opMode:

2015-01-07 14:06:21
sHeatDHWDay

1919 Wh

2015-01-07 14:07:20
sHeatDHWTotal

3682 kWh

2015-01-07 14:06:56
sHeatHCDay

8735 Wh

2015-01-07 14:06:50
sHeatHCTotal

6981 kWh

2015-01-07 14:06:46
sHeatRecoveredDay

1783 Wh

2015-01-07 14:06:58
sHeatRecoveredTotal

6243 kWh

2015-01-07 14:07:49
sHistory

compressorHeating: 1512 compressorCooling: 0 compressorDHW: 718 boosterDHW: 421 boosterHeating: 6

2015-01-07 14:08:03
sLast10errors

number_of_faults: 4 fault0CODE: fault0TIME: 7:2 fault0DATE: 28.11 fault1CODE: F02_SafetyTempDelimiterEngaged fault1TIME: 9:3 fault1DATE: 2.12 fault2CODE: fault2TIME: 11:23 fault2DATE: 6.01 fault3CODE: F07_MainOutputFanFault fault3TIME: 13:54 fault3DATE: 7.01

2015-01-07 17:06:32
sSol

collector_temp: -60 dhw_temp: 47.6 flow_temp: 24.3 ed_sol_pump_temp: 0 x20: 2560 x24: 15360 x28: 17 x32: 17

2015-01-07 14:06:19
sTimedate

Weekday: Monday Hour: 14 Min: 11 Sec: 18 Date: 2015/1/7

2015-01-07 14:06:59
state

opened

2015-01-07 14:06:11


hab mal 2 Plots eingefügt.



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 07 Januar 2015, 17:39:22
Zitat von: immi am 07 Januar 2015, 00:03:38
v 0123 uploaded
- actualPower_Qc and actualPower_pEl fixed
...
feedback is welcome
Using the values from my post (http://forum.fhem.de/index.php/topic,13132.msg240342.html#msg240342) I get the following single-precision floats:
6939.953, 1.536
6893.686, 1.606
8245.390, 1.660
So the first value might be a value in Watts. Though, the second value is probably not Pel (not even in kW).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 17:50:35
Zitat von: belu am 07 Januar 2015, 13:06:10
@IMMI gibt es die möglichkeit den Volumenstrom zu erfassen, bei mir ist er in den Istwerten aufgeführt.
For sure; if you tell me where to find it and how it is encoded :) sorry I already searched for it, without luck....
edit: I just tested also without success godmorgon hint 0A033B-0100490A033B1003-01044D0A033B1003-UNKNOWN REQUEST
Or if you convince the service guy to give you the new service software; I would be pleased to reverse-eng. it.
Or try to search in internet; many people are trying to implement an interface to the thz.
http://knx-user-forum.de/smarthome-py/39630-neues-plugin-thz-lwz-30x-40x.html
https://sourceforge.net/p/openautomation/code/HEAD/tree/wiregate/plugin/generic/StiebelEltron-LWZ-x04.pl#l302
Maybe someone has the address, and I can finally sit and copy :)

Zitat von: belu am 07 Januar 2015, 16:06:22
Bin gerade auf der Arbeit und hab die ...
ne-ne ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 18:19:56
Zitat von: godmorgon am 07 Januar 2015, 17:39:22
Using the values from my post (http://forum.fhem.de/index.php/topic,13132.msg240342.html#msg240342) I get the following single-precision floats:
6939.953, 1.536
6893.686, 1.606
8245.390, 1.660
So the first value might be a value in Watts. Though, the second value is probably not Pel (not even in kW).
I do not understand
have you used my v0123 or something else?
it is working well for me; I just tested again. My values are in kW.

with heating off and vent on
outsideTemp: 3 flowTemp: 12.5 returnTemp: 12.6 hotGasTemp: 12.4 dhwTemp: 16.6 flowTempHC2: -60 evaporatorTemp: 6.4 condenserTemp: 12.8 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 0 solarPump: 0 compressor: 0 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 29 inputVentilatorPower: 30 mainVentilatorPower: 0 outputVentilatorSpeed: 22 inputVentilatorSpeed: 23 mainVentilatorSpeed: 0 outside_tempFiltered: 4.2 relHumidity: 0 dewPoint: 0 P_Nd: 6.76 P_Hd: 6.62 actualPower_Qc: 0.000 actualPower_Pel: 0.000 collectorTemp: -60 insideTemp: -60



with heating on and vent on (I switched the heating on just for you :)
outsideTemp: 3 flowTemp: 16.3 returnTemp: 13.6 hotGasTemp: 23.3 dhwTemp: 16.6 flowTempHC2: -60 evaporatorTemp: -0.7 condenserTemp: 15.8 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 29 inputVentilatorPower: 30 mainVentilatorPower: 70 outputVentilatorSpeed: 15 inputVentilatorSpeed: 23 mainVentilatorSpeed: 20 outside_tempFiltered: 4.1 relHumidity: 0 dewPoint: 0 P_Nd: 2.9 P_Hd: 9.77 actualPower_Qc: 5.332 actualPower_Pel: 1.359 collectorTemp: -60 insideTemp: -60

can someone else check?
I am far from home and my internet connection is quite poor.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 18:40:51
@IMMI

2015-01-07 14:07:24
sGlobal

outsideTemp: 0.3 flowTemp: 31.3 returnTemp: 25.4 hotGasTemp: 69.8 dhwTemp: 49.7 flowTempHC2: -60 evaporatorTemp: -3.4 condenserTemp: 27.7 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 31 inputVentilatorPower: 30 mainVentilatorPower: 60 outputVentilatorSpeed: 24 inputVentilatorSpeed: 24 mainVentilatorSpeed: 17 outside_tempFiltered: 0.6 relHumidity: 0 dewPoint: 0 P_Nd: 3.68 P_Hd: 12.77 actualPower_Qc: 4949.592 actualPower_Pel: 1.743 collectorTemp: -60 insideTemp: 23.7


Wroks with  actualPower_Qc: 4949.592 actualPower_Pel: 1.743

But only a COP 2,83 :((((
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 07 Januar 2015, 18:45:28
Zitat von: immi am 06 Januar 2015, 12:03:18
this is a philosophical/religius decision.
Many things in our lives are philosophical or debatable. Some of them are related to the efficiency (in comparision to the effectiveness).

The serial link (hardware) is not the root cause of the problem because there is no real data loss. Data loss usually occurs when the read process is slower than the data arrival rate. What I observe with fhem is the opposite - if I slow down the read process I get all the data.

Of course some users might experience data loss due to wiring or EMC issues.

The messages have a specific formatting allowing us to detect the start and the end of a message. Futhertmore, there is a checksum providing an indicator for the data integrity (its quality is debatable). You don't need hadware flow control to cleanly segment the bytestream into individual messages and to check its integrity. So you should be able to rely on the message formatting. If something does not fit then all collected bytes are discarded.

Let's do the math first.
1 byte is encoded in 10 bits (1 start bit, 8 payload bits and 1 stop bit)
9600 bps would ideally transfer 960 bytes per second. That is, 1 byte needs less than 1ms. The longest THZ/LWZ message is shorter than 100 bytes. So it should arrive at the receiver within less than 100ms. But it obviously does not. I guess nobody has ever analyzed the transmission timing at the link level. Possibly the THZ/LWZ does not transmit bytes back-to-back which would increase the transmission duration. Therefore, it might be better no to rely on micro-timeouts but rather use a bigger timeout for the DLE+ETX reception.

A serial link running at 115200 bps is 12 times faster. Nevertheless, the fhem code seems to have a timing issue. I cannot tell you exacly what goes wrong in the long chain of data exchage. But something definetly goes wrong.

If I find time I will try to propose a solution. My approach would be to have a separate thread collecting all bytes belonging to one message.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 07 Januar 2015, 18:56:32
Zitat von: immi am 07 Januar 2015, 18:19:56
have you used my v0123 or something else?
I currently have no access to my heatpump either. So I did a quick command line test:
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('45d8df9f')))));"
6939.953
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('3fc49ba6')))));"
1.536
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('45d76d7d')))));"
6893.686
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('3fcd9169')))));"
1.606
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('4600d58f')))));"
8245.390
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('3fd47ae2')))));"
1.660

So even if I assumed the first value to be in W and the second in kW the COP would be not very credible: 4.29 - 4.97. I wish I had such a COP during the winter season. ;-)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 18:59:30
Zitat von: godmorgon am 07 Januar 2015, 18:45:28
If I find time I will try to propose a solution. My approach would be to have a separate thread collecting all bytes belonging to one message.
A separate process/thread for communication: It would be great. I would be happy to merge.

one more thing look at the length of your fb-response compared to mine

0100F9FBFDA8FFFC00B8009A021400A7FDA8FDA8FF8F00A82008110122012C02BC000F00160014000200000000010203CD40908DD33FA158111003
0100eafbfda8001601440108024901e6fda8fda8001c01176008110000000002bc000000000014001900000000014c05304600d58f3fd47ae207c500b1012a000001060144fff4ffde012300000000103e

immi




Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 07 Januar 2015, 19:06:42
Now you cannot say the size does not matter!  ;)
This is why I have more accesible registers in my heatpump.
However, I still have no clue where the values for humidity and hydralic pressure are hiding.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 07 Januar 2015, 19:20:29
There's something fishy.
Your 0xfb message in the last comparision had the following hex values:
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('3FA15811')))));"
1.261
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('40908DD3')))));"
4.517
The decoded values are represented rather differently:
actualPower_Qc: 4949.592 actualPower_Pel: 1.743
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Januar 2015, 20:00:55
Beheizte Fläche lt EnEV: 145 qm; 51 W/qm anno Primärenergiebedarf
Wandaufbau oder direkt den U-Wert: 0,147 W/qmK
dito für Dach: 0,178 w/qmK
Aufbau und U-Wert der Fenster und Außentüren: Alle Dreifachverglasung 0,7 w/qmK; eine Aussentür auch gedämmt Wert unbekannt.
Ergebnis des Blower Door Tests: 0.98 1/h
Stockwerke: 1, 5 Geschossig
Keller? wenn ja: Perimeterdämmung: Woraus und wie dick? Keller WU-Beton mit EPS 8cm; Treppenaugeninnenwände (innen und aussen) sind zusätzlich gedämmt mit 10 bzw 12 cm Glaswolle
Dämmung unter der Bodenplatte? wenn ja: Perimeterdämmung: Woraus und wie dick? 12 cm EPS nur Treppenauge
thermische Solarzellen zusätzlich verbaut? wenn ja: Details (Größe, Typ) nein
Holzofen? wenn ja: Details (Größe, Luft oder mit Anschluß an die FB-Heizung) Palena Olsberg 5 kW; kein Anschluss, nicht wasserführend
Ofen ist meist nur am WE an, oder wenn  Minusgrade draussen sind.

Hab kein so tolles Zusammenfassung-Bild wie ihr, alles einzeln: Meine Spreizung ist nur bei 2K.  :(
Steigung: 0,31 Fusspunkt: 1,5; Raumeinfluss: 80%; Flow Proportion: 30% Hyst 1: 2,8; Hyst 2: 2,4; Asymetrie: 3 K; Integral 100Kmin;  BoosterTimeoutHC:60 min; SummerMode Temp: 15°C; SummerModeHyst: 2K; BoosterTimeoutDWH:180 min; Bivalenz: -7°C

2014 Gesamtverbrauch inkl. Lüftung: 1975 kWh bei 4 Bewohnern.

(http://img5.fotos-hochladen.net/thumbnail/screenshot201cx671lvbw5_thumb.jpg) (http://www.fotos-hochladen.net/view/screenshot201cx671lvbw5.png)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 20:46:47
Zitat von: godmorgon am 07 Januar 2015, 19:20:29
There's something fishy.
Your 0xfb message in the last comparision had the following hex values:
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('3FA15811')))));"
1.261
$ perl -e "printf(\"%.3f\n\",unpack('f', pack( 'L',reverse(hex('40908DD3')))));"
4.517
The decoded values are represented rather differently:
actualPower_Qc: 4949.592 actualPower_Pel: 1.743

$message= "F9FBFDA8FFFC00B8009A021400A7FDA8FDA8FF8F00A82008110122012C02BC000F00160014000200000000010203CD40908DD33FA15811";

just add to line 1156 is decoded

outsideTemp: -0.4 flowTemp: 18.4 returnTemp: 15.4 hotGasTemp: 53.2 dhwTemp: 16.7 flowTempHC2: -60 evaporatorTemp: -11.3 condenserTemp: 16.8 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 29 inputVentilatorPower: 30 mainVentilatorPower: 70 outputVentilatorSpeed: 15 inputVentilatorSpeed: 22 mainVentilatorSpeed: 20 outside_tempFiltered: 0.2 relHumidity: 0 dewPoint: 0 P_Nd: 2.58 P_Hd: 9.73 actualPower_Qc: 4.517 actualPower_Pel: 1.261 collectorTemp: -60 insideTemp: -60
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Januar 2015, 21:10:15
I cannot make much sense out of the new energy parameters when I plot them. Why the neg values? The lines are almost on top of each other. I wold expect at least double AUC from the produced energy. Does anybody else has see this too, in their readings?

(http://img5.fotos-hochladen.net/thumbnail/screenshot201e806ygpzsx_thumb.jpg) (http://www.fotos-hochladen.net/view/screenshot201e806ygpzsx.png)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 21:14:25
tom
please post which version you have
you have to update to v0.123
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 07 Januar 2015, 21:53:37
yep, it is version 0.123
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 21:55:57
Zitat von: belu am 07 Januar 2015, 18:40:51
@IMMI

2015-01-07 14:07:24
sGlobal

outsideTemp: 0.3 flowTemp: 31.3 returnTemp: 25.4 hotGasTemp: 69.8 dhwTemp: 49.7 flowTempHC2: -60 evaporatorTemp: -3.4 condenserTemp: 27.7 mixerOpen: 0 mixerClosed: 0 heatPipeValve: 0 diverterValve: 0 dhwPump: 0 heatingCircuitPump: 1 solarPump: 0 compressor: 1 boosterStage3: 0 boosterStage2: 0 boosterStage1: 0 highPressureSensor: 0 lowPressureSensor: 1 evaporatorIceMonitor: 0 signalAnode: 0 evuRelease: 1 ovenFireplace: 0 STB: 0 outputVentilatorPower: 31 inputVentilatorPower: 30 mainVentilatorPower: 60 outputVentilatorSpeed: 24 inputVentilatorSpeed: 24 mainVentilatorSpeed: 17 outside_tempFiltered: 0.6 relHumidity: 0 dewPoint: 0 P_Nd: 3.68 P_Hd: 12.77 actualPower_Qc: 4949.592 actualPower_Pel: 1.743 collectorTemp: -60 insideTemp: 23.7


Wroks with  actualPower_Qc: 4949.592 actualPower_Pel: 1.743

But only a COP 2,83 :((((

HI Belu
actualPower_Pel: 1.743 is maybe ok but 4949.592 is not ok. 
you have probably a very new heatpump like godmorgon with different encoding of this parameters
Let us wait for feedback from more people...
I start to think that we have to fork like we did for Peter:
very old heapump like Peter -->firmware version 2.06
medium heatpump like me -->firmware version 4.39
very new heatpump like godmorgon --> firmware version 5.39 and ID 7278

let us see
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 21:57:36
Hi tom
can you post
get Mythz sGlobal


if you updated in the afternoon, you see only big values in the plot, which come from before the update

The  right values are much smaller like actualPower_Qc: 5.332 actualPower_Pel: 1.359

immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 22:02:03
@ MMI
have a thz 304 5.19 software version 316
The COP I have derived from the upper values are indeed identical values other. My COP is bad ..

2,8 COP...

ZitatWroks with  actualPower_Qc: 4949.592 actualPower_Pel: 1.743

But only a COP 2,83 :((((


or
2,8 COP...

ZitatsHeatHCDay 8870 Wh / sElectrHCDay 2968 Wh = HeatDay_COP = 2,989

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 07 Januar 2015, 22:17:04
Zitat von: belu am 07 Januar 2015, 22:02:03
@ MMI
have a thz 304 5.19 software version 316
The COP I have derived from the upper values are indeed identical values other. My COP is bad ..
Belu
you have a  problem in your actualPower_Qc: 4949.592 actualPower_Pel: 1.743
actualPower_Qc is 3 order of magnitude different from actualPower_Pel.

Can you see these value in your display?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 22:20:37
I will Test it tomorrow... I have 1,2 kW with Heating and 1,7 kw DHW
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 23:36:10
Zitat von: belu am 07 Januar 2015, 17:33:53
@ Willi,

also es ist gut Isoliert, Neubau 2013 Enev 40 Energiesparhaus Blowerdoortest 0,5 also Passivhaus dicht.
Ist Holzständer durch die Aussage Enev 40 sollte der rest eigentlich ok sein. Ich hab irgendwas von dem Energieausweis von 8000 KW Primärenergiebedarf im kopf.


hier mal das Setup:
...

Kaum wirds kalt, schon häufen sich die Beiträge so, dass man es schon gar nicht mehr schafft, alles zu lesen.



@belu:
An der Grafik sieht man überdeutlich, wie oft und für wie kurze Zeit Deine Anlage in den Heizmodus geht. Das ist das, was ich mit "takten" meinte. Wie ein Auto im Kurzstreckenverkehr: kaum ist der Motor warm und könnte effizient laufen, da macht man ihn wieder aus und wartet.Kaum ist er abgekühlt beginnt das Spiel von vorne. Das macht nicht nur den COP kaputt, sondern verschleißt auch die Anlage.

Die Werte des Hauses klingen nicht schlecht. Mein Haus hat lt. Energieausweis 47,2kWh/m², also bei 120m² beheizter Fläche ca. 5700kWh/Jahr.  In 2014 war der gesamte Stromverbrauch 2184kWh, die Jahre davor (kältere Winter, Anlage noch nicht so gut abgestimmt) ebenfalls unter 3000kWh. Dann sollte Dein Haus in der genannten Bauweise mit grob geschätzt 4-5000kWh/Jahr auskommen - vorausgesetzt Du wohnst in einer ähnlichen Klimazone wie ich (Großraum Stuttgart).

Deine Anlage hat mehrere Fehler gespeichert. Das solltest Du klären: am Display die Fehlercodes auslesen (Fachmann-Menü) und im Installationsmanual nachsehen, was sie bedeuten ==> hat evtl. mit dem Problem zu tun.

Die Hysteresen P21-P25 sind recht gering: 3 - 2 - 3 - 2 - 1k  Ich habe da 4 - 3 - 3 - 2 - 1K. Je größer die Werte, desto länger läuft die Anlage am Stück, und die Pausen sind dafür auch länger ==> weniger Kaltlaufzeitanteile. Ich hoffe, Du hast einen "richtigen" gegossenen Estrich (Zement- oder Anhydritestrich) mit einer fetten Wärmespeicherkapazität. Dann kannst Du die Hysteresen auch so einstellen. Bei Leichtbauestrich führt das aber zu Temperaturschwankungen im Haus.

Ich glaube nach wie vor, dass die Heizkurve für dein Haus zu hoch eingestellt ist ==> alle Thermostate komplett öffnen ==> wird es extrem warm im Haus, dann ist die Heizkurve zu hoch eingestellt; es sollte nur 1 - 2° wärmer werden.

Es stellt sich auch die Frage, wozu man mitten in der Nacht eine Raumtemperatur von 26,9°C braucht ... siehe Titelzeile Deiner 1. Grafik. Ist da zusätzlich ein Holzofen im Spiel? Generell ist die Innenraumtemperatur weit über den 20°, die Du genannt hattest. Auch kann ich mir nicht erklären, wie um 3:30 und 14:45 Uhr die Heizkreistemperatur so schnell ansteigen kann, obwohl gar kein Heizbetrieb (=kein grüner Balken im 2. Diagramm) stattfindet. Oder war da der Heiztakt so kurz, dass er gar nicht aufgezeichnet wurde?

Die Spreizung sieht soweit ok aus.

Ansonsten:
p33BoosterTimeoutDHW = 20 min ==> d.h. Du gibst der Wärmepumpe (WP) nur 20 Minuten Zeit, um warmes Wasser zu machen. Wenn sie es bis dahin nicht geschafft hat hilft der Heizstab. Ab welcher Temperatur darf sie das denn? Das kannst du nur im Display ablesen: Warmwasser - Parameter - Temp.Freigabe NE Da sollte z.B. -5° drin stehen. Bei Dir steht da sicher ein höherer Wert, denn ...

Ich sehe: compressorDHW: 718 Stunden boosterDHW: 421 Stunden ==> der Booster hilft sehr oft bei der Warwasserbereitung mit. Siehe letzter Absatz p33... Man sieht das auch in der 2. Grafik um 6:55 und 16:40 Uhr: jeweils ein schmaler roter senkrechter Balken, der bei dieser Außentemperatur nicht sein müsste.

Ich lese: sElectrHCDay  2893 Wh   2015-01-07 14:06:18   
Das ergibt auf den ganzen Tag hochgerechnet ungefähr 5 - 6 kWh, und nicht 10 - 12 kWh, wie du genannt hattest. Die 5 - 6 kWh sind voll ok für dieses Haus. Du schreibst: Anhand der Zahlen sehe ich: Kannst Du den Widerspruch bitte aufklären?


==> Du hast kein Problem mit hohem Verbrauch. Der Verbrauch ist ganz ok. Lediglich der COP ist durch die Taktung sehr schlecht. Wenn Du die Heizkurve korrigierst wird der COP besser und der Verbrauch nochmal geringer.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 23:42:49
Zitat von: immi am 07 Januar 2015, 18:19:56
can someone else check?
actualPower_Qc: 4.032 actualPower_Pel: 1.163
(version 0.123 used)

==> looks ok
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 07 Januar 2015, 23:53:28
Zitat von: houseowner123 am 07 Januar 2015, 20:00:55
Beheizte Fläche lt EnEV: 145 qm; 51 W/qm anno Primärenergiebedarf
Wandaufbau oder direkt den U-Wert: 0,147 W/qmK
...
Hab kein so tolles Zusammenfassung-Bild wie ihr, alles einzeln: Meine Spreizung ist nur bei 2K.  :(
Steigung: 0,31 Fusspunkt: 1,5; Raumeinfluss: 80%; Flow Proportion: 30% Hyst 1: 2,8; Hyst 2: 2,4; Asymetrie: 3 K; Integral 100Kmin;  BoosterTimeoutHC:60 min; SummerMode Temp: 15°C; SummerModeHyst: 2K; BoosterTimeoutDWH:180 min; Bivalenz: -7°C

2014 Gesamtverbrauch inkl. Lüftung: 1975 kWh bei 4 Bewohnern.
Dein Verbrauch klingt - dank Holzofen - ok. Haus ist auch sehr gut, bis auf den BlowerDoor Test. Wie man die Spreizung erhöht hatte ich ja schon beschrieben: Volumenstrom reduzieren durch geringere Pumpenleistung. Bei 1 1/2 Stockwerken sollte das ja gehen, ohne dass das Warme Wasser im Keller versackt. Mit etwas größeren Hysteresewerten (sh. meine Antwort an belu heute abend) kommt noch etwas mehr Effizienz raus.
Dein Warmwasser kühlt relativ schnell aus. Aber da bin ich wohl eine Ausnahme: ich habe den Warmwasserbehälter zusätzlich gedämmt. Wenn nichts verbraucht wird muss nur ca. alle 24 Stunden 1 mal nachgeheizt werden.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 07 Januar 2015, 23:54:53
@ Willybaus,

also ich hatte die Sicherung der Zusatzheizung eigentlich immer draußen, keine ahung warum er es dann gezählt hat, habe sie nie wirklich drin...

Das war die Tagessumme von heute Mittag.
Aktuell von heute bei um die 0 Grad
sHeatHCDay 22910 Wh / sElectrHCDay 7825 Wh = Entspricht dann einem COP von 2,928

Deine Verbesserungen werde ich morgen mal einpflegen vielleicht hilft da ja schon.
Die Raumtemperatur stimmt nicht wirklich hab aktuell 20,1 °C er sagt es sind 23,7...

@Immi

actualPower_Pel: 1.671 in FHEM
Real Power with Fans only 1.224 kw with the EHZ

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 00:01:40
Zitat von: belu am 07 Januar 2015, 23:54:53
@ Willybaus,

also ich hatte die Sicherung der Zusatzheizung eigentlich immer draußen, keine ahung warum er es dann gezählt hat, habe sie nie wirklich drin...
...
Die Raumtemperatur stimmt nicht wirklich hab aktuell 20,1 °C er sagt es sind 23,7...

compressorDHW: 718 Stunden boosterDHW: 421 Stunden lässt sich nicht wegdiskutieren, sorry.
Wie man einen falsch messenden Raumfühler korrigiert steht ja auch in einem meiner früheren Beiträge ... userReading ...


Außerdem würde mich nach wie vor interessieren:
Du schreibst: Anhand der Zahlen sehe ich:
Kannst Du den Widerspruch bitte aufklären?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 00:13:58
@ Willybaus,

also ich  hab im Haus maximal 20 Grad, es ging da um Thema Vorlauf Themperaturen mit Spreizung, Ich hab doch die Raspberry seid paar Tagen erst wieder im Betrieb, wird noch etwas dauern bis alles richtig ist.

Ich mach mir morgen früh mal die Arbeit und Antworte ausführlich auf deine Fragen. War eben auf Spätschicht und hab da nicht die Zeit ausschweifend zu Antworten.
Mich belastet halt nur diese schlechte COP kann es nicht nachvollziehen. Ich mein Sicherlich der verschleiß ist höher wenn sie öfter pulst. Aber ob sie jetzt 3 mal 2 stunden am Tag läuft oder 6 mal 1 Stunde macht den Unterschied nicht aus.
Die Sicherung vom Heizstab war noch nie drin, also ich weis nicht was er da zählt..
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Januar 2015, 00:18:20
Zitat von: belu am 07 Januar 2015, 23:54:53
.@Immi

actualPower_Pel: 1.671 in FHEM
Real Power with Fans only 1.224 kw with the EHZ

Sorry that I ask you again
did you manage to measure / log both values at the same time?
You know that such a value changes very rapidly.
Thats for you; if you get some good measurements and some statistics, you can judge to trust this value or not

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 00:21:38
@Immi,

yes read both at the same time,  quick refresh vom sglobal und the actual data from my electronic counter.
both data realy stable.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Januar 2015, 01:21:22
Zitat von: willybauss am 07 Januar 2015, 23:53:28
Dein Verbrauch klingt - dank Holzofen - ok. Haus ist auch sehr gut, bis auf den BlowerDoor Test. Wie man die Spreizung erhöht hatte ich ja schon beschrieben: Volumenstrom reduzieren durch geringere Pumpenleistung. Bei 1 1/2 Stockwerken sollte das ja gehen, ohne dass das Warme Wasser im Keller versackt. Mit etwas größeren Hysteresewerten (sh. meine Antwort an belu heute abend) kommt noch etwas mehr Effizienz raus.
Dein Warmwasser kühlt relativ schnell aus. Aber da bin ich wohl eine Ausnahme: ich habe den Warmwasserbehälter zusätzlich gedämmt. Wenn nichts verbraucht wird muss nur ca. alle 24 Stunden 1 mal nachgeheizt werden.

Ich kann Dir mal das Zertifikat vom BDT schicken. Ich kenn keinen der bei unseren Haustyp merklich bessere Werte hat. Ist ja auch weit über dem geforderten Wert von 0,5. Beim Test waren ein paar grobe Leckagen um die Spitzbodentür (war verzogen), was ich mittlerweile abgedichtet hab.
Hysterese werd ich (dank Deines Tips) mal vorsichtig erhöhen. Hast Du die Asymmetrie dafür runtergeregelt auf 2 K?
Mit dem Wassertank bin ich mir nicht so sicher. Hast Du einen Vorher-Nachher-Test gemacht mit der Dämmung.Man liest ja überall daß das nichts bringen soll. Hast Du einfach Mineralwolle rumgemacht? Ich hätte da noch was rumliegen...
Könnte die FBH auch noch mal auffüllen, so um 0,2-0,3 bar. Hängt im Ruhestand bei 1,5 bar und hat so 6 m zu überbrücken. Mit mehr Wasservolumen müsste die pumpe ja mehr arbeiten, d.h. so könnte auch der Volumenstrom reduziert werden. Oder unterliege ich da einen Denkfehler?

Eine Frage noch: Bei sGlobal gibt es: P_Nd: 3.37 P_Hd: 12.38 Sind das die Druckwerte in den beiden Kreisläufen (HC1 und DHW)?

Danke für Deine personalisierten Tips! :)

@immi: It works, it always did. My mistake! Sorry. See screenshot. Thanks!  ;D

(http://img5.fotos-hochladen.net/thumbnail/screenshot201nawe729h0z_thumb.jpg) (http://www.fotos-hochladen.net/view/screenshot201nawe729h0z.png)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 07:45:49
Zitat von: belu

Die Raumtemperatur stimmt nicht wirklich hab aktuell 20,1 °C er sagt es sind 23,7...

also ich  hab im Haus maximal 20 Grad

es ging da um Thema Vorlauf Themperaturen mit Spreizung

ob sie jetzt 3 mal 2 stunden am Tag läuft oder 6 mal 1 Stunde macht den Unterschied nicht aus.
Die Sicherung vom Heizstab war noch nie drin, also ich weis nicht was er da zählt..


Du hast also einen Messfehler von  23,7 - 20,1 = 3,6° bei der Innentemperatur. Wenn das Diagramm im Tagesverlauf 24 - 26,9° anzeigt, dann passt das mit Deiner Angabe von max. 20° im Haus nicht zusammen.

Es ging auch um den angeblich hohen Verbrauch (10 - 12 kWh/Tag), der ebenfalls nicht mit den vorliegenden Zahlen zusammen passt.

Wie genau stimmen denn die weiteren Angaben, z.B. die Außentemperatur, mit den tatsächlichen Werten überein?

Die WP läuft aber bei Dir nicht 6 mal 1 Stunde. Das 2. Diagramm zeigt 12 Einschaltvorgänge pro Tag, wovon die meisten unter 30 Minuten sind. Wenn ich die Höcker im 1. Diagramm dazu nehme, dann war sie sogar 15 mal am Tag in Betrieb, 3 mal davon so kurz, dass man es im 2. Diagramm gar nicht sieht. Kannst ja mal mit meinem Diagramm vergleichen.

Sorry, wenn ich das so klar sage: wenn Du so grobe Angaben machst, die offenbar mit der Realität wenig übereinstimmen, dann kann/werde ich Dir nicht weiter helfen.

Ich sehe in Deinem Log z.B. auch:  sElectrDHWDay  1379 Wh   2015-01-07 14:07:18
Wenn die Sicherung draußen ist, dann "glaubt" die Anlage, elektrisch geheizt zu haben, konnte es aber nicht. Die Anlage mit raus gedrehter Sicherung zu "überlisten" ist ein grobes Faul. Schließlich hat die Anlage für diesen Zweck jede Menge Möglichkeiten, um ungewollten Heizstabeinsatz mit Wissen der Anlage zu vermeiden, z.B. Warmwasser - Parameter - Temp.Freigabe NE.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 07:55:01
Zitat von: houseowner123 am 08 Januar 2015, 01:21:22
Ich kann Dir mal das Zertifikat vom BDT schicken. Ich kenn keinen der bei unseren Haustyp merklich bessere Werte hat. Ist ja auch weit über dem geforderten Wert von 0,5. Beim Test waren ein paar grobe Leckagen um die Spitzbodentür (war verzogen), was ich mittlerweile abgedichtet hab.
Hysterese werd ich (dank Deines Tips) mal vorsichtig erhöhen. Hast Du die Asymmetrie dafür runtergeregelt auf 2 K?
Mit dem Wassertank bin ich mir nicht so sicher. Hast Du einen Vorher-Nachher-Test gemacht mit der Dämmung.Man liest ja überall daß das nichts bringen soll. Hast Du einfach Mineralwolle rumgemacht? Ich hätte da noch was rumliegen...
Könnte die FBH auch noch mal auffüllen, so um 0,2-0,3 bar. Hängt im Ruhestand bei 1,5 bar und hat so 6 m zu überbrücken. Mit mehr Wasservolumen müsste die pumpe ja mehr arbeiten, d.h. so könnte auch der Volumenstrom reduziert werden. Oder unterliege ich da einen Denkfehler?

Eine Frage noch: Bei sGlobal gibt es: P_Nd: 3.37 P_Hd: 12.38 Sind das die Druckwerte in den beiden Kreisläufen (HC1 und DHW)?
...
Wir haben (Holzständerhaus) knapp über 0,5 beim BDT. Gefordert lt. Norm ist maximal 1,5. So gesehen liegst Du noch gut.
Ich habe die Asymetrie bei 1 (1, nicht 1K). Wenn Du auf 2 stellst, dann verringerst Du die max. Temperaturen, die die WP aufbringen muss (==> spart Strom), verringerst dabei aber auch den Temperaturhub. Wie man's macht isses verkehrt ...
Ich habe die Hohlräume rings um des Wasserbehälter mit Mineralwolle ausgestopft. Ich habe noch nirgendwo darüber was gelesen, lediglich 1 User im HTD Forum. Der war begeistert. Bei mir haben sich die Verluste halbiert: vorher 2 mal pro Tag erwärmen, jetzt 1 mal (jeweils gemessen im Sommer und ohne zwischnzeitige Wasserentnahme).
Mit auffüllen wirst Du das Wasservolumen kaum erhöhen. Wasser ist nicht komprimierbar. Du komprimierst lediglich das Gasvolumen im Ausgleichsbehälter (vorausgesetzt, Du hast keine Luftblasen im der FHH). Wenn Du nie nachfüllen musst (=> kein Leck) bringt höherer Druck wohl kaum was - außer Gefahr für die Rohrverbindungen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 08:42:40
Guten morgen,
also der Verdichter ist die Nacht 4 Stunden am Stück gelaufen 23 Uhr bis 3 Uhr. Danach jetzt nicht mehr.
Temperatur war von 23 Uhr 0,3 °C bis 3 Uhr 2,2 °C leicht steigend.

sElectrHCDay 5284 Wh / sHeatHCDay 14580 Wh = Heat_COP 2,76

Also bringt das mit dem lange laufen auch nicht wirklich was.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 09:35:59
Guten Morgen willybaus,

Es Handelt sich um einen Neubau von dez 2012. Freistehendes 1 1/2 geschössiges Einfamilienhaus, Es ist laut Energieausweis ein Enev 55 Haus, es hat einen Jahresenergiebedarf von 8235 kWh/a + Trinkwassererwärmung 2366.
Es Hat eine Nutzfläche von 190 qm wobei 140 qm beheitz sind.
Es hat laut Energieausweis 45,4 kWh /qm a

Ich habe vorher geschrieben das es ein Enev 40 Haus ist, ja weil ich die Perimeterdämmung im Keller selbst ausgeführt habe, in der Berechnung war die Kellerdecke Isoliert und nicht die Bodenplatte.
Desweiteren wurde die Kellerisolierung der Wände nicht in 8 CM ausgeführt sondern in 12 cm wie auch die Perimeter Dämmung der Bodenplatte. Material BASF XPS 12 CM WLG 035.

Es ist auch ein Enev 40 Haus, Problem ist nur das der Bauträger meine Perimeter Dämmung nicht akzeptiert, die Außenisolierung könnte ich in Eigenleistung machen aber die Perimeterdämmung würde nur vor Ort vom Bautrupp gemacht werden können. Ich habe damals mit dem Bautrupp zusammen die Dämmung ausgeführt. Ging auf kleinem Dienstweg und war ne kosten Nutzen abwägung. Die wollten dafür 6000 Euro, ich hätte aber nur wenig mehr Förderung bekommen. Material hat mich aber nur 1200 Euro gekostet.

Die UWerte stehen im Energieausweis, die wesentlichen Daten habe ich mal eingescannt.

Fenster sind immer geschlossen. Die Lüftungsanlage läuft immer mit 170 kubik die Stunde.

Ich hab keine Solaranlage.
Ich habe einen Ofen, den selben wie Houseowner Olsberg Palena Compact mit 5 KW

Heizung ist eine Tecalor THZ 304

@Houseowner

Blowerdoortest, das Geheimnis war einfach eine Vorwandinstallationsebene ein zu führen. Ich habe an allen Außenwänden ausser in den Bädern eine Installationsebene gemacht und den Wandaufbau verändert.

Holzständer mit Steinwolle, Dampfsperre ( Kontrolle mit Hochwertiger Wärmebildkamere der Isolierung und Dampfsperre und da war einiges nicht so wie man sich das wünscht.. ), Holz Lattung horizontal 6 x 2,5 CM Holz Lattung vertikal 6 x 2,5 CM.
Dadurch habe ich einen leeren Raum von 5 CM. Das war meine Installtionsebene für Elektrik und Wasser. Darauf dann Farmacell und Rigips selbst bei tiefen Einbaudosen die eine tiefe von 62 mm Haben komme ich nicht an die Dampfsperre. 2,5 + 2,5 + 1,2 + 1,2 = 7,4 cm Abstand als sicherheit.

Dadurch hab ich dieses Ergebnis geschaft. Der Prüfer hat den Test auch 3 mal gemacht und meinte das er das noch nie erlebt hat bei der DFH...

Bin soweit auch ziemlich zufrieden mit dem was jetzt ist, nur halt der COP ist nicht wie er soll, wobei ich denke das der Volumenstromsensor einen hat, anders kann ich mir das nicht erklären.
Wenn ich nur mal Pzu nehme also sElectrHCTotal 2522 kWh + sElectrDHWTotal 1600 kWh = 4122 KW für 2 Jahre geht ja eigentlich. Was dafür spricht ist das der Bau ja noch gewisser weise die ersten Jahre mehr benötigt. Was dagegen spricht war der letzte Winter.




Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 08 Januar 2015, 09:56:34
Zitat von: immi am 07 Januar 2015, 22:17:04
Belu
you have a  problem in your actualPower_Qc: 4949.592 actualPower_Pel: 1.743
actualPower_Qc is 3 order of magnitude different from actualPower_Pel.

Can you see these value in your display?
I don't think that current values are displayed. At least not in the case of 404SOL.

The interesting thing about Belu's values is that his heat pump seems to use a similar value encoding like mine. The Pel seems to have the same order of magnitude. However, the Qc is almost a half of mine Qc. He is not happy with his Qc. And I just cannot believe that my value is correct.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Januar 2015, 10:04:59
Zitat von: godmorgon am 08 Januar 2015, 09:56:34
I don't think that current values are displayed. At least not in the case of 404SOL.

The interesting thing about Belu's values is that his heat pump seems to use a similar value encoding like mine. The Pel seems to have the same order of magnitude. However, the Qc is almost a half of mine Qc. He is not happy with his Qc. And I just cannot believe that my value is correct.

Pel seems for me (303i) a little bit low. From the graph I see 1.1 kW but the meter usually read 1.5 kW. Will do a real life test tonight. Could it be that different firmwares and models present different values? Maybe an empirical correction factor is needed.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 10:22:52
hi,

current actualPower_Qc: 4676.042 actualPower_Pel: 2.453

DHW

Real Power on the meter 1,548 kw
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 08 Januar 2015, 11:46:30
In my experiments couple of days ago I had the following values:
v = 19.3 l/min = 1158 l/h = 0.326666666 l/s
dT = 6°K
With the specific thermal capacity cw = 4.182 kJ/(kg*K) and the approximate water density r = 1kg/l I get the following Qc:
Qc = v * cw * r * dT = 0.326666666 * 4.182 * 1 * 6 = 8.07126 kJ/s
This value seems to have the same order of magnitude which I saw in the 0xfb message.
The temperature difference seems to be about right (though, I haven't checked it yet). Since my COP values appear too high I would assume that the flow rate measurement is not correct.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 12:24:13
Zitat von: godmorgon am 08 Januar 2015, 11:46:30
In my experiments couple of days ago I had the following values:
v = 19.3 l/min = 1158 l/h = 0.326666666 l/s
dT = 6°K
With the specific thermal capacity cw = 4.182 kJ/(kg*K) and the approximate water density r = 1kg/l I get the following Qc:
Qc = v * cw * r * dT = 0.326666666 * 4.182 * 1 * 6 = 8.07126 kJ/s
This value seems to have the same order of magnitude which I saw in the 0xfb message.
The temperature difference seems to be about right (though, I haven't checked it yet). Since my COP values appear too high I would assume that the flow rate measurement is not correct.

I have testet v=  16,2 L / min = 972 l / h = 0,27 l / S
vl = 28,9 - rl 23.0 = dT 5,9 K


With the specific thermal capacity cw = 4.182 kJ/(kg*K) and the approximate water density r = 1kg/l I get the following Qc:
Qc = v * cw * r * dT = 0,27 * 4,182 * 1 * 5,9 = 6,6619 QC

Current  actualPower_Qc: 6515.391 at the same reading as the v & dT

current actualPower_Pel: 1.834
Real Power on the Meter 1,296

My COP Based on THZ Like  Current  actualPower_Qc: 6515.391 / current actualPower_Pel: 1834 = 3,55
Calculate on Temperture and Flow and the Real Power from the meter 6,6619 / 1296 = 5,139

i think both not correkt, i have a outside tempreture 4,2. in the power diagramm based thz 304 with 35 flow temp with fans 170 qm i can reach peak 5,1 kw qc...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 12:36:04
Zitat von: belu am 08 Januar 2015, 09:35:59
...
Bin soweit auch ziemlich zufrieden mit dem was jetzt ist, nur halt der COP ist nicht wie er soll, wobei ich denke das der Volumenstromsensor einen hat, anders kann ich mir das nicht erklären.

Wenn ich nur mal Pzu nehme also sElectrHCTotal 2522 kWh + sElectrDHWTotal 1600 kWh = 4122 KW für 2 Jahre geht ja eigentlich. Was dafür spricht ist das der Bau ja noch gewisser weise die ersten Jahre mehr benötigt. Was dagegen spricht war der letzte Winter.
Von den Werten her sieht das Haus sehr gut aus. Dach ist wie immer die Schwachstelle (U-Wert 0,18; Wände 0,125). Man vergisst immer, dass das Dach so eine große Fläche hat. Bei dem Verbrauch (bei dem sicher der Holzofen eine Rolle spielt) brauchst Du dich nicht wirklich zu beklagen; aber ich bin mit Kenntnis der Bauqualität noch mehr als vorher der Meinung, dass Deine Heizkurve für dieses Haus zu hoch ist, und dass deshalb die WP über die Thermostatventile zum takten gezwungen wird. Der durch bessere Abstimmung erreichbare Verbrauchsvorteil ist weniger Ausschlag gebend als die Tatsache, dass Du Dir langfristig die WP kaputt machst mit den vielen Kaltstarts. Nach einer Änderung der Einstellung sollte man immer (IMMER) 1 - 2 Tage warten, bis man sich zu abschließenden Aussagen verleiten lässt. Alles vorher ist nur ein Trend. Und dann bitte wieder mit der Ganztagesgrafik.

Warum die WP auch im Dauerbetrieb eine geringe Leistungszahl (der Begriff COP wird üblicherweise für das Jahresmittel verwendet, nicht für eine punktuelle Messung) hat, erschließt sich mir noch nicht. Ich meine, mich dunkel erinnern zu können, dass die 4er Serie die Leistung modulieren kann, d.h. bei geringem Wärmebedarf arbeitet sie in einer Art Teillastbetrieb (wenn's so stimmt). Ob das die Leistungszahl negativ beeinflusst weiß ich aber nicht. Evtl. mal beim telefonischen Support von SE anrufen und genau den heutigen Fall (4 Stunden Dauerlauf) schildern. Kannst ja sagen, Du hättest vorher und nachher die Werte vom Display abgelesen, um sie nicht direkt mit "da ist ein Bastler am Telefon und hat was kaputt gemacht" auf die falsche Fährte zu locken. ;)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 12:43:38
@ Willybaus,

ich bin schon Ausarbeitung am machen, habe alle Thermostate offen, lasse sie jetzt einfach brummen und werde mal schauen was die Raumtemperaturen so von sich geben, werde das erstmal entsprechend optimieren.
Hast sicherlich recht, ich bin noch nicht so tief im Thema und Frage deshalb gerne.
Ich denke auch das es irgendwas mit dem metering zu tun hat, ich kann mir irgendwie nicht vorstellen warum die Anlage so schlecht laufen sollte.
COP ist doch der Coeffizenz of Power / Aktualwert von QC abgegeben zu Pzu aufgenommen, das gibt dann eine Verhältniszahl.
Die Jz Jahresarbeitszahl ist der COP im Mittelwert..

Mit dem Dach hast schon recht, sind eigentlich überall 30 Isolierung an den Wänden und recht gute 3Fach isolierte Fenster mit einem U Wert von 0,6 aber Dach hat nur 24 cm... Wobei das schon Rockwoll 035 ist da kannst nichts besseres rein machen.


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 12:55:47
Zitat von: willybauss am 08 Januar 2015, 12:36:04
Ich meine, mich dunkel erinnern zu können, dass die 4er Serie die Leistung modulieren kann, d.h. bei geringem Wärmebedarf arbeitet sie in einer Art Teillastbetrieb (wenn's so stimmt). Ob das die Leistungszahl negativ beeinflusst weiß ich aber nicht. Evtl. mal beim telefonischen Support von SE anrufen und genau den heutigen Fall (4 Stunden Dauerlauf) schildern. Kannst ja sagen, Du hättest vorher und nachher die Werte vom Display abgelesen, um sie nicht direkt mit "da ist ein Bastler am Telefon und hat was kaputt gemacht" auf die falsche Fährte zu locken. ;)

Also ich hab ja schon viel getestet mit der Pumpe, ich habe ja auch ne Datenauswertung auf dem EHZ da sehe ich schon das sie im Heizungsbetrieb zwischen 1,15 kw nimmt und 1,35 kw. Es könnte sein das sie da schon etwas moduliert um eine optimale Spreizung hin zu bekommen.

Was ich mit Sicherheit aber sagen kann das sie im Warmwasserbetrieb so 1,7 kw nimmt. Denke das hängt mit der höheren Vorlauf Temperatur zusammen. Komischerweise ist es laut Leistungsdiagramm höher, aber das Leistungsdiagramm nimmt keinen Bezug zur aufgenommen Leistung, es sagt lediglich aus, bei dieser Temperatur mit Lüftung ohne Lüftung Vorlauf 35 oder Vorlauf 50 °C.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 13:38:12
Zitat von: belu am 08 Januar 2015, 12:43:38
Mit dem Dach hast schon recht, sind eigentlich überall 30 Isolierung an den Wänden und recht gute 3Fach isolierte Fenster mit einem U Wert von 0,6 aber Dach hat nur 24 cm... Wobei das schon Rockwoll 035 ist da kannst nichts besseres rein machen.
Ich habe aus diesem Grund nochmal auf der Innenseite eine Aufsparrendämmung mit weiteren 4cm, ebenfalls 035, drauf gemacht. Damit komme ich im Dach auf ca. 0,15 oder sowas.

Ich komme übrigens ohne zusätzliche Installationsebene in den Außenwänden ebenfalls auf ein BDT Ergebnis von 0,5. Das ist speziell bei der Verlegung von Kabeln ziemlich aufwändig (überall luftdichte Hohlwanddosen plus zusätzliche Abdichtung mit Silikon) und wird sicher nur dann ordentlich gemacht, wenn man die Elektrik selbst verlegt. Aber die vielen m² Wohnfläche wollte ich nicht spendieren.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 13:59:54
Jetzt ist schon wieder der Fehler 07 gekommen, Fortlüfter Drehzahl kleiner Nennwert, hab es nun mal untersucht....
Lüfter läuft garnicht an, mechanisch frei, was war es?
Nach dem Software Update stand die EVU Sperre auf 0, hab sie wieder auf 5 gestellt, er wollte Verdichter und Fortlüfter einschalter aber nur der Lüfter ist Drehzahlüberwacht, deshalb nur diese Störung.

Das wäre eigentlich wieder ein Grund für eine reklamation....
Wenn ich so Anlagen verlassen würde...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 08 Januar 2015, 14:52:59
Zitat von: belu am 08 Januar 2015, 13:59:54
Jetzt ist schon wieder der Fehler 07 gekommen, Fortlüfter Drehzahl kleiner Nennwert, hab es nun mal untersucht....
Lüfter läuft garnicht an, mechanisch frei, was war es?
Nach dem Software Update stand die EVU Sperre auf 0, hab sie wieder auf 5 gestellt, er wollte Verdichter und Fortlüfter einschalter aber nur der Lüfter ist Drehzahlüberwacht, deshalb nur diese Störung.

Das wäre eigentlich wieder ein Grund für eine reklamation....
Wenn ich so Anlagen verlassen würde...
Je mehr Du selbst dran reparierst, desto größer ist anschließend der Vorwurf, Du hättest es kaputt gemacht. Je nach Vertrag hast du auf Dein Haus 3 oder 5 Jahre Gewährleistung ...

Jedenfalls sind in diesem Zustand Überlegungen zum COP verfrüht ... Ich würde erst mal auf Gewährleistung die Anlage vom Werksservice checken lassen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 08 Januar 2015, 16:15:48
Also bei uns gehört die Heizung garantie-technisch nicht zum Haus; Vertrag war mit Stiebel, normalerweise 2 Jahre, nach deren Ersteinrichtung 3 Jahre.

slight-off topic: Hab eine Artikel gefunden der noch mal schön das Thema Zirkulationspumpe für Anfänger wie mich erklärt: http://www.ikz.de/uploads/media/839--Heizungstechnik.pdf

Weil es in der Postwut untergegangen ist: Can anybody explain what P nd and hd values in sGlobal mean? It is related to pump activity, that is all I noticed.

Thanks! :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 08 Januar 2015, 16:35:45
@Houseowner,

Pnd Phd sind Druckwächter die deinen Heiz / Kühlkreislauf überwachen.

Hochdruck Seite ist die mit dem Verdichter, Niederdruck Seite ist die hinter dem Expansionventil.

Das Kältemittel das drin ist wechselt ja den Aggregatzustand von Flüssig zu Gasförmig dadurch absorbiert es die Wärme die in der Umgebungsluft enthalten ist. Das macht es aber nur mit unterschiedlichen Atmosphären.

Die Werte Zeigen nur an das dein Verdichter läuft und Druck aufbaut und das Expansionsventil arbeitet und kontrolliert in den Verflüssiger Verdampft, kann dir da aber nicht sagen was gute oder schlechte werte sind.

Niederdruck heißt trotzdem Druck also nicht denken das das auf 0 sein muss, im Ruhezustand hat die Anlage so 3 Bar.

Aktuell bei mir P_Nd: 3.64 P_Hd: 12.53 Pumpe arbeitet im Heizbetrieb.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 08 Januar 2015, 20:08:50
Hallo immi,
ich hätte eine Bitte an dich.
Die Werte des Registers "sHistory" scheinen bei mir nicht zu stimmen. (compressorHeating: 1341 compressorCooling: 1346 compressorDHW: 10303 boosterDHW: 3578 boosterHeating: 1 ).
In der Software "Heatpumpmonitor" habe ich folgende Beschreibungen für die Register des Betriebszustandes für meine Firmware gefunden:

[HeatingValues]
comment = the heating values
request = \xf4
responseLength = 39
#            name              pos    type   size fixedDecimals
# -------------------------------------------------------------
value01 = inside_temp           32  fixedPoint  2   1

[CurrentTime]
comment = the current time of the heatpump
request = \xfc
responseLength = 9
value01 = hours                 2   fixedPoint  1   0
value02 = minutes               3   fixedPoint  1   0
value03 = seconds               4   fixedPoint  1   0
value04 = year                  5   fixedPoint  1   0
value05 = month                 7   fixedPoint  1   0
value06 = day                   8  fixedPoint  1   0

[OperatingCondition]
comment = the current operating condition (Betriebszustand)
request = \x09
responseLength = 13
value01 = operatingHours1   0   fixedPoint  2   0
value02 = operatingHours2   2   fixedPoint  2   0
value03 = heatingModeHours  4   fixedPoint  2   0
value04 = heatupWater       6   fixedPoint  2   0
value05 = coolingMode       8   fixedPoint  2   0



Könntest du bitte prüfen, ob im THZ-Modul die gleichen Register angegeben sind?
Vielen Dank.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 08 Januar 2015, 21:08:55
Zitat von: peter456 am 08 Januar 2015, 20:08:50
Hallo immi,
ich hätte eine Bitte an dich.
Die Werte des Registers "sHistory" scheinen bei mir nicht zu stimmen. (compressorHeating: 1341 compressorCooling: 1346 compressorDHW: 10303 boosterDHW: 3578 boosterHeating: 1 ).
one register at time:
Please do not change the names too much, I would like similar look and feel in thz-fhem
please decode this example from your logfile 20dec2014
C5090381038127AF0DD000000000001003'
then I can try up implement

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 08 Januar 2015, 22:52:16
Hallo immi,

ich habe mit der Software von Striebel Eltron die Betriebsstunden meiner LWZ ausgelesen (siehe Anhang).
Der Wert "C5090381038127AF0DD000000000001003" ist wie folgt aufgebaut:
C509
0381 => 897 Betriebsstunden LWZ
0381 => 897 Betriebsstunden LWZ
27AF => 10159 Betriebsstunden Heizmodus
0DD0 => 3536 Betriebsstunden Warmwassermodus
0000000000 => keine Funktion
1003

Die "Betriebsstunden LWZ" sind wahrscheinlich deswegen so niedrig, weil der Hex-Wert nur 4-stellig ist. Maximaler Wert FFFF = 65535 Stunden = 7 Jahre. Meine LWZ ist ca. 7,3 Jahre alt. Der aktuelle Wert würde also bedeuten 7 Jahre + 897 Stunden.
Die im FHEM ausgelesenen Werte "compressorHeating: 1341 compressorCooling: 1346 compressorDHW: 10303 boosterDHW: 3578 boosterHeating: 1" sind noch anscheint falsch zugeordnet. Bei compressorDHW müsste z.B. stehen 3578. Bei compressorHeating müsste stehen 10303.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Januar 2015, 08:29:24
Hi Peter
your interpretation and the image is quite contradictory
Nevertheless, let us do what you say

C509
0381 => 897 Betriebsstunden LWZ  --> operatingHours1
0381 => 897 Betriebsstunden LWZ  --> operatingHours2
27AF => 10159 Betriebsstunden Heizmodus  -->  heatingHours
0DD0 => 3536 Betriebsstunden Warmwassermodus --> DHWhours
0000  => 0 --> coolingHours

do you agree with this decoding?

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 09 Januar 2015, 09:11:05
Hallo immi,

ja das stimmt so.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 09 Januar 2015, 11:47:17
done
v124 uploaded
history register pathed for peter
please test tomorrow
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 09 Januar 2015, 14:28:41
Vielen Dank immi,
ich werde morgen berichten.
Es wundert mich, dass ich bis jetzt wohl der Einzige mit der alten Firmware bin.
Im Haustechnikdialog-Forum gab es Nutzer mit noch älteren LWZ/THZ Geräten.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 15:04:37
Zitat von: peter456 am 09 Januar 2015, 14:28:41
Vielen Dank immi,
ich werde morgen berichten.
Es wundert mich, dass ich bis jetzt wohl der Einzige mit der alten Firmware bin.
Im Haustechnikdialog-Forum gab es Nutzer mit noch älteren LWZ/THZ Geräten.
Dann mach dort bitte etwas Werbung für uns, sobald Du das Gefühl hast, dass man es anbieten kann. Das hilft uns bei der Argumentation gegenüber SE, dass Interesse besteht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 16:34:45
@Willibaus,

ich habe nun mal ne gescheitene Auswertung von Gestern, bin ja aktuell am Hydralischen Abgleich dran, habe die Berechnungen vom Heizungsbauer angefragt und versuche es aber momentan einfach nach gefühl und den Temperaturen die das alles zu harmonisieren in dem ich den Durchfluss in den Räumen erhöhe oder senke.

Das Haus hat momentan alles beheizt. 21 °C +-05 °C

Das schon mal gut, aber er hat auch dafür auf dem Zähler 15,1 KW aufgenommen. Kann man aber nachvollziehen da der Verdichter ja so 10 Stunden gelaufen ist. Ist jetzt nicht so toll...

Was sagst du dazu? Habe die Verbesserungen die du vorgeschlagen hast alle umgesetzt.


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 17:53:14
Zitat von: belu am 09 Januar 2015, 16:34:45
Was sagst du dazu? Habe die Verbesserungen die du vorgeschlagen hast alle umgesetzt.
Hi belu,

Hydr. Abgleich ist super - wenns gut klappt. Aber halt auch super aufwendig.

Das Diagramm sieht jetzt WESENTLICH besser aus in Bezug auf die Anzahl der Starts, also weniger Starts und dafür längere Laufzeiten. Die 15,1kWh würde ich mal als einzelnen Datenpunkt nicht soooo ernst nehmen, nur wenn das in ein paar Tagen immer noch so ist. So ein träges System muss bei Änderungen erst mal einschwingen. Und momentan kühlt der heftige Wind die Außenwände ab. Das ist nicht zu vernachlässigen.

Der kurze Start um ca. 8:05 Uhr wundert mich. Warum hat die WP da so schnell wieder abgeschaltet? Man sieht es im Plot2 nicht genau, aber könnte es sein, dass da geheizt wurde, ohne dass die Heizkreispumpe lief?  Kannst Du mal rein zoomen oder im Logfile nachsehen? Oder waren da womöglich alle Thermostatventile zu, und deshalb konnte die Wärme nicht abgegeben werden?

Warum erfolgte dieser Start überhaupt, wenn es doch recht warm war? Evtl. hat da der Integralanteil zugeschlagen. Evtl. würde es helfen, p30integralComponent zu erhöhen, um diese prophylaktischen Starts zu reduzieren. Sieh mal im Logfile nach, ob der tatsächliche Integralanteil zu dieser Uhrzeit den in P30 eingestellten Wert erreicht hatte.

Den Offset der Innentemperatur hast Du offenbar auch korrigiert - top! Ich verstehe aber noch nicht ganz, warum bei Dir zwischen 4 und 8 Uhr nachts die Innentemperatur am höchsten ist. Machst Du abends den Holzofen an, oder gibt es nachts eine andere Wärmequelle?

Warum reduziert sich die HC1 Soll tagsüber nicht, obwohl es draußen recht warm war? Der größte Teil der Heizkosten war zwischen 12 und 19 Uhr bei Außentemperaturen bis zu fast 10° - sehr ungewöhnlich. Bei mir ist die HC1 Soll ein inverses Abbild der Außentemperatur. Wie hoch hast Du denn p15RoomInfluenceHC1 eingestellt?

Auch die Abnahme der Innentemperatur tagsüber finde ich ungewöhnlich. Hast Du da eine Absenkung drin?

Bei evuLockout musst Du mir auf die Sprünge helfen. Schaltet da der Energieversorger mehrfach täglich die Stromzufuhr zur Wärmepumpe ab? Das würde den kleinen Aussetzer der Vorlauftemperatur zwischen 17:30 und 18 Uhr erklären.

Die negativen Zacken auf 10° bei HC1 Soll verstehe ich auch nicht. Zwei davon sind während der evuLockout ZEiten, der dritte aber nicht.

Und dein Warmwasserbehälter scheint besser isoliert zu sein als bei der 303. So eine geringe Auskühlund habe ich erst, seit ichihn zusätzlich isoliert habe.

Gruß
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 18:45:54
Noch was: im Plot4 sehe ich Leistungsaufnahmen von 2 bis 2,5kW. Wenn ich mich richtig erinnere hast Du die LWZ 304. Die hat lt. Datenblatt eine maximale Leistungsaufnahme von 1,44kW. Dann können die 2,5kW gar nicht stimmen. Wie misst Du denn die in Plot 4 angezeigte Leistung? Hast Du das schon mal mit den tatsächlichen Zahlen am Stromzähler abgeglichen?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 19:12:59
Zitat von: willybauss am 09 Januar 2015, 17:53:14
Der kurze Start um ca. 8:05 Uhr wundert mich. Warum hat die WP da so schnell wieder abgeschaltet? Man sieht es im Plot2 nicht genau, aber könnte es sein, dass da geheizt wurde, ohne dass die Heizkreispumpe lief?  Kannst Du mal rein zoomen oder im Logfile nachsehen? Oder waren da womöglich alle Thermostatventile zu, und deshalb konnte die Wärme nicht abgegeben werden?

Also ich hatte sie kurz von Hand eingeschaltet um zu schauen ob der Fortlüfter richtig läuft und die Abstände passen. Hatte dazu die Warmwasser Tagestemperatur auf 52 °C gestellt, dann springt die Wärmepumpe ja sofort an.

Zitat von: willybauss am 09 Januar 2015, 17:53:14
Den Offset der Innentemperatur hast Du offenbar auch korrigiert - top! Ich verstehe aber noch nicht ganz, warum bei Dir zwischen 4 und 8 Uhr nachts die Innentemperatur am höchsten ist. Machst Du abends den Holzofen an, oder gibt es nachts eine andere Wärmequelle?

Den Offset habe ich an der Heizung verstellt und genau angepasst und jetzt auch in dem Plot, Holzofen ist das nicht, es ist glaube ich einfach die trägheit der Fußbodenheizung es dauert ja 6 Stunden bis der raum wirklich warm wird. Es war kein Kamin an oder eine andere Wärmeuelle.

Zitat von: willybauss am 09 Januar 2015, 17:53:14
Warum reduziert sich die HC1 Soll tagsüber nicht, obwohl es draußen recht warm war? Der größte Teil der Heizkosten war zwischen 12 und 19 Uhr bei Außentemperaturen bis zu fast 10° - sehr ungewöhnlich. Bei mir ist die HC1 Soll ein inverses Abbild der Außentemperatur. Wie hoch hast Du denn p15RoomInfluenceHC1 eingestellt?

Ich habe ja im Wohnzimmer einen Ofen, da ist auch der Temperaturfühler den ich an TR angeschlossen habe, ich habe dann den Raumeinfluss von 30 % auf 40 % erhöht um besser auf den Ofen reagieren zu können um ein Überheizen zu vermeiden. Das könnte natürlich auch einene Einfluss auf die Heizkurve haben. Die Maximale Vorlauftemperatur habe ich auf 35 °C begrenzt. Aber du hast schon recht, die Frage ist warum geht die HC1 Soll nicht wesentlich runter. Die restlichen Parameter die wesentlich sind:

p13GradientHC1 0.25
p14LowEndHC1 2 K
p15RoomInfluenceHC1 40 %
p21Hist1 4 K
p22Hist2 3 K
p23Hist3 3 K
p24Hist4 2 K
p25Hist5 1 K
p29HistAsymmetry 2
p30integralComponent 100 Kmin

Ich glaube aber je flacher die Steigung ist desto weniger ist die Regeländerung, ich sollte evt den Fußpunkt etwas niedrieger setzen und dafür die Steigung etwas höher, dadurch müsste ich diesen effekt bekommen.


Zitat von: willybauss am 09 Januar 2015, 17:53:14
Auch die Abnahme der Innentemperatur tagsüber finde ich ungewöhnlich. Hast Du da eine Absenkung drin?

Nein habe keine Nachtabesenkung oder der gleichen drin, fahre 24/7 das gleiche Programm mit 21 °C Raumtemperatur HC1

Zitat von: willybauss am 09 Januar 2015, 17:53:14
Bei evuLockout musst Du mir auf die Sprünge helfen. Schaltet da der Energieversorger mehrfach täglich die Stromzufuhr zur Wärmepumpe ab? Das würde den kleinen Aussetzer der Vorlauftemperatur zwischen 17:30 und 18 Uhr erklären.
Die negativen Zacken auf 10° bei HC1 Soll verstehe ich auch nicht. Zwei davon sind während der evuLockout ZEiten, der dritte aber nicht.

Ich hatte doch erwähnt das der Monteur irgendwie die EVU Sperre raus gemacht hat, das die Drehzahl des Fortlüfters überwacht ist aber nicht der Verdichter an sich, das war der Fehler 07 Drehzahl Fortlüfter unterhalb der Grenze. Die Anlage geht dann auf Notbetrieb mit 10 °C das waren die Auswirkungen.
Mein Verteilernetzbetreiber schaltet mit einer Uhr meinen verbilligten Wärmepumpenstrom immer so 2 Stunden  zu Spitzenzeiten am Tag aus. Habe sie nun in den Plot eingefügt  weil die Daten vorliegen und es erklärt warum genau jetzt die Wärmepumpe nicht läuft.

Zitat von: willybauss am 09 Januar 2015, 17:53:14
Und dein Warmwasserbehälter scheint besser isoliert zu sein als bei der 303. So eine geringe Auskühlund habe ich erst, seit ichihn zusätzlich isoliert habe.

Das hoffe ich doch, das ist ja die THZ 304 sol die soll ja vom Design her besser sein was Lautstärke Isolierung angeht.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 19:15:00
Zitat von: willybauss am 09 Januar 2015, 18:45:54
Noch was: im Plot4 sehe ich Leistungsaufnahmen von 2 bis 2,5kW. Wenn ich mich richtig erinnere hast Du die LWZ 304. Die hat lt. Datenblatt eine maximale Leistungsaufnahme von 1,44kW. Dann können die 2,5kW gar nicht stimmen. Wie misst Du denn die in Plot 4 angezeigte Leistung? Hast Du das schon mal mit den tatsächlichen Zahlen am Stromzähler abgeglichen?

Ne ne, das ist das Pel und QC aus der MyTHZ sGlobal der Anlage, die Werte stimmen ja nicht überein mit dem was real ist, das ist noch expirimentell, ich hoffe das IMMI da noch was findet, ich war gerade dran mich in das THZ Modul ein zu lesen um ihn dabei etwas zu unterstützen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 19:37:15
@Willy

p13GradientHC1 0.25
p14LowEndHC1 2 K
p15RoomInfluenceHC1 40 %


Ich habe die Werte nun mal verändert.

p13GradientHC1 0.3
p14LowEndHC1 0 K
p15RoomInfluenceHC1 3 %

Ich habe einen Verdacht, denke das da in Parameter (  p15RoomInfluenceHC1 3 % )etwas nicht rund läuft.

Raumeinfluss hat laut Installtionsanleitung ein Wertebereich von 0 - 10, wenn ich da ne 40 reinschreibe gibt es kein min max Limitierung, er berechnet damit einfach den HC1 Soll... Das würe erklären warum er sich nur so wenig träge gegenüber der Außentemperatur ändert. Er hätte dann auch den 4 fachen Maximalwert.

@Immi,

in Line 77
"p15RoomInfluenceHC1"   => {cmd2=>"0B010F", argMin => "0", argMax => "100", type =>"0clean", unit =>" %"},

Do u have a devisor /10 inside after %? In the Manual THZ 304 P15 min value 0 and max 10.

Thx
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 20:34:15
@belu:
Wenn die Fußbodenheizung träge ist, dann sollte in so einem gut isolierten Haus sich die Temperatur gar nicht ändern - vorausgesetzt, es ist ein wirklich schwerer Estrich mit hoher Wärmekapazität. Bei mir sind es ca. 30 Tonnen Anhydritestrich, 6cm dick. Sieh mal meine Grafiken an. Die Innentemperatur ist total stabil, unabhängig von Heizzyklen. Nur bei Sonnenschein steigt die Innentemperatur an.

Die Steigung dürfte jetzt schon zu groß sein für Dein sehr gut gedämmtes Haus; wenn Du sie noch steiler machst, dann wirst Du bei tiefen Außentemperaturen wieder das Problem bekommen, dass die Anlage sich oft kurz einschaltet, weil sie zu viel heizt. Die Steigung ist dazu da, bei allen Außentemperaturen so viel Wärme bereit zu stellen wie das Haus braucht. Schlechtes Haus = große Steigung und umgekehrt. Wenn Du mit der Steigung andere Zwecke verfolgst, dann wirst Du Dich bei allen anderen Außentemperaturen über "komische" Effekte wundern - taktende WP, zu kalt, ... Lies das nochmal irgendwo nach und denke drüber nach, bevor Du rumstellst.

EVU Sperre, Fortlüfter, ... ok - verstanden.

Deine COP-Werte hattest Du doch auch aus diesen Zahlen ermittelt ... dann ist mir klar, warum da so schlechte Werte raus kommen.
Nimm Dir doch bitte mal die Zeit, die am Display angezeigten Tageswerte abzulesen und diese in der COP-Berechnung zu verwenden. Dann siehts wahrscheinlich besser aus. Die Werte des Displays stimmen bei mir recht genau mit den Werten des Stromzählers überein.

> Raumeinfluss hat laut Installtionsanleitung ein Wertebereich von 0 - 10
Bei der THZ303, für die das Mythz Modul ursprünglich geschrieben war, ist der Wertebereich 0 - 100%. Wenn Du 40 eingegeben hast und die Anlage das so akzeptierte, dann wird sie wohl ausschließlich nach Innentemperatur (400%) geregelt haben. Kein Wunder, dass sie erst mal stundenlang geheizt hat, um sich an die neue Situation anzupassen.

Deine jetzige Zahl 3 entspricht dann wohl nicht 3%, sondern 3 Deka-Prozent, also 30%. Da muss immi dann wohl was korrigieren.
==> Wir brauchen mal nen Freiwilligen, der die Wertebereiche der Parameter von 303 und 304 vergleicht. Womöglich liegt da noch mehr im Argen. Du solltest mal sicherheitshalber die Werte nur noch am Display ändern oder zumindest den gültigen Wertebereich gegenchecken.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 21:19:51
@Willybaus,

Also die COP hab ich berechnet anhand von Vorlauf Rücklauf und Durchfluss, Ich habe sie auch berechnet anhand der Werte die mir so gegen 24 Uhr vorlagen, Heizen Tag Summe / E Heizen Tag Summe.

Die Wertigkeiten stimmen aber nicht überein. Leider

Aktuell habe auf dem Zähler einen Tagesverbrauch von 11,9 kWh  2015-01-09 21:10:00
Frischer refresh der Daten ergibt:

sElectrHCDay 12781 Wh 2015-01-09 21:10:06
sElectrDHWDay 3392 Whn  2015-01-09 21:11:01

die beiden Werte stimmen auch mit den Daten in der THZ überein, der Zähler ist geeicht.... Dem Zähler glaube ich einfach mehr.  Das sind ja immerhin 4,2 KW mehr Leistung die er denkt das er sie verbraucht.
Meine erste Theorie war das wenn die Wärmepumpe über 0 Uhr läuft werden die Counter ja zurück gesetzt. Zur Sommer oder zur Winterzeit?

Ich muss den Intervall mal ändern, am Besten immer kurz vor 0 Uhr counten, dann sollte ich immer den Tagesverbrauch haben, vielleicht Zählt der interne Zähler der THZ
immer gleich falsch.

Wenn er denkt er nimmt fast immer 1 / 4 mehr Energie auf erklärt es auch meine schlechte COP von kleiner 3...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 21:32:27
Zitat von: belu am 09 Januar 2015, 21:19:51
Wenn er denkt er nimmt fast immer 1 / 4 mehr Energie auf erklärt es auch meine schlechte COP von kleiner 3...
Genau das meinte ich. Aber dann ist das auf jeden Fall ein Thema für den Stiebel Eltron Service - oder Tecalor (die das dann aber auch wieder an SE geben). Wahrscheinlich ist das ein Firmwareproblem, für das es sicher schon ein Update gibt.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 21:35:33
Zitat von: willybauss am 09 Januar 2015, 21:32:27
Genau das meinte ich. Aber dann ist das auf jeden Fall ein Thema für den Stiebel Eltron Service - oder Tecalor (die das dann aber auch wieder an SE geben). Wahrscheinlich ist das ein Firmwareproblem, für das es sicher schon ein Update gibt.

Leider nein, Am Dienstag war doch der Stiebel Eltron Monteur im Haus, der hat die aktuellste Software eingespielt, 10 Dez 2014. Das war vorher auch schon. Ich lese mich mal in die Pläne ein wie die ihre Energie zählen...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 09 Januar 2015, 22:04:11
Ok, es ist wirklich so ich konnte es jetzt an mehreren Stellen in der Log zum Echtzeit verbrauch beweisen es wird immer 1,4 mehr gezählt und angegeben als er auf dem Zähler hat...

Immer...
Da braucht man sich nicht zu wundern das man einen scheiss COP hat..
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 09 Januar 2015, 22:11:01
anrufen würde ich trotzdem. Vielleicht ist es ja ein Hardwareproblem.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 00:36:13
Ok, ich weis nun auch woher die Zahl kommt... War jetzt nach der Arbeit nochmal kurz an der Heizung. Je nach Leistung ist der Faktor 1,39 bis 1,41 höher, rund also 1,4...

Ist ne THZ 304, wenn ich mir die Leistungsdaten der THZ 404 anschaue ist die Wärmepumpe genau um diesen Faktor größer also in der elektrischen aufnahme...

Da ist echt schwer ein Bug drin. Mich würde ja mal intressieren wie sie die Leistung bestimmen. Es gibt keine Sensoren, hatte zuerst die Vermutung das da ein falscher Wandler drin ist.
War mutig und habe der Anlage gesagt sie ist ne THZ 404 ich mein ist ja baugleich bis auf den Verdichter.
Angemacht Warmwasser bereitet und siehe da... Noch mehr Leistung... nochmal um den Faktor 1,4 erhöht. Das erklärt so einiges.
Da ist ein Faktor auf dem Faktor...

Was mir noch aufgefallen ist wenn ich es auf THZ 404 sol stelle ist die Software 539 wie bei Peter.. Das heißt die Software ist identisch.
Man kann auch aus der THZ eine LWZ machen... Irgendwie schon komisch..
Ich werde mich am Montag mal bemühen in die Entwicklung durch zu kommen und hoffe das ich da irgendwen erreiche mit schlechtem Gewissen aus das sich dann Kapital für uns schlagen lässt...

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 08:25:06
Zitat von: belu am 10 Januar 2015, 00:36:13
... habe der Anlage gesagt sie ist ne THZ 404
... Man kann auch aus der THZ eine LWZ machen...

Interessant. Wie machst Du das?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 09:13:32
@willy, ich hab im Punkt Inbetriebnahme Modell drin. Das kann man verändern.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 10 Januar 2015, 12:19:06
Zitat von: immi am 09 Januar 2015, 11:47:17
done
v124 uploaded
history register pathed for peter
please test tomorrow
Hallo immi,
das update auf V0124 funktioniert.
Vielen Dank.
Die Werte stimmen mit meiner LWZ überein.
(operatingHours1: 1377 operatingHours2: 1385 heatingHours: 10309 DHWhours: 3581 coolingHours: 1 )

Bei meiner ist es ja möglich die Parameter P01-P12 auszulesen.
Kann man diese Parameter über FHEM auch verändern?
Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Januar 2015, 13:27:45
Zitat von: peter456 am 10 Januar 2015, 12:19:06
Kann man diese Parameter über FHEM auch verändern?
I am quite sure it is possible to change reg 17, but I would wait some weeks, untill when you are more familiar with fhem, and it is not so cold. I cannot debug it, before giving it to you. I would suggest that you remind me in 8 weeks.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 10 Januar 2015, 13:42:29
Alles klar.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 13:43:48
@ Immi , what do you think this can be the energy it wrong counting ? I just always 1.4 times more energy to electrical counters as on the calibrated meter . Even sglobal actualPower_Pel is always 1.4 times higher than the current performance on the calibrated meter .
This also explains why I always such a damn bad COP have ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Januar 2015, 15:59:06
belu
for me it is not clear, if I decode actualPower_Pel correctly for your new firmware.
In my firmware (4.39), I checked it against an old service software.
If also the service software from tecalor reads 1.4 more than your calibrated meeter, then also the energy count could be wrong.

The only way to be sure 100% is:
- to get the service software from tecalor/se (which I do not have for your new firmware)
or even better
- to get a full documentation of the registers from tecalor/se

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Januar 2015, 16:57:37
Zitat von: belu am 09 Januar 2015, 19:37:15
in Line 77
"p15RoomInfluenceHC1"   => {cmd2=>"0B010F", argMin => "0", argMax => "100", type =>"0clean", unit =>" %"},

Do u have a devisor /10 inside after %? In the Manual THZ 304 P15 min value 0 and max 10.
Willy, Belu
I remember an unfinished discussion on this parameter.
Do you prefer it in % (more readable, like flow-proportion,  like in the display) or from 1..10 (like in the manual)?
100% full-infl and 0% empty   -vs-  10 full-infl and 0 empty
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 10 Januar 2015, 17:52:33
Zitat von: belu am 10 Januar 2015, 13:43:48
@ Immi , what do you think this can be the energy it wrong counting ? I just always 1.4 times more energy to electrical counters as on the calibrated meter . Even sglobal actualPower_Pel is always 1.4 times higher than the current performance on the calibrated meter .
This also explains why I always such a damn bad COP have ...
The electrical energy values of my 404SOL match the values of the electrical meter pretty good. Though, I would say that the heat values exceed the expected values by approximately 40 %. From these values the COP would be 4.7-4.8. I would expect it somewhere in the area of 3.2-3.4 (for the temperature range of -2°C .. +2 °C). As far as I know the heat metering in the heat pump is based on discrete sensors (temperature, flow rate) which are not calibrated. Therefore, I think that the internal sensors provide messy data for the computation. Garbage in, garbage out.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 20:34:20
Zitat von: belu am 10 Januar 2015, 09:13:32
@willy, ich hab im Punkt Inbetriebnahme Modell drin. Das kann man verändern.
cool, habe ich nicht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 20:55:11
Zitat von: immi am 10 Januar 2015, 15:59:06
belu
for me it is not clear, if I decode actualPower_Pel correctly for your new firmware.
In my firmware (4.39), I checked it against an old service software.
If also the service software from tecalor reads 1.4 more than your calibrated meeter, then also the energy count could be wrong.

The only way to be sure 100% is:
- to get the service software from tecalor/se (which I do not have for your new firmware)
or even better
- to get a full documentation of the registers from tecalor/se
it's not that complicated. You should be able to do the following:

at 0:01 am (= 1 minute past midnight)  read and note
1. value of EVU energy meter for your heatpump (Stromzähler im Sicherungskasten)
2. value in FACHMANN - LAUFZEITEN - E.HEIZUNG TAG => should be close to zero
3. value in FHEM - Mythz.sGlobal.sElectrHCDay => should be close to zero

If values of 2. and 3. are not close to zero => wait another few minutes until daily reset happened.

at 11:59 pm (= 1 minute before next midnight, thus 23:58 hours later) read and note
4. value of EVU energy meter for your heatpump (Stromzähler im Sicherungskasten)
5. value in FACHMANN - LAUFZEITEN - E.HEIZUNG TAG
6. value in FHEM - Mythz.sGlobal.sElectrHCDay

Expected result: difference (value4 - value1) should be same as (value5 - value2) and same as (value6 - value3).

If the FHEM values (value6 - value3) differ from the THZ values (value5 - value2) ==> the decoding is wrong.

If the EVU values (value4 - value1) differ from the THZ values (value5 - value2) ==> the measurement inside the heatpump is wrong, thus decoding cannot fix that. The heatpump itself has a wrong measurement.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 21:27:48
Zitat von: immi am 10 Januar 2015, 16:57:37
Willy, Belu
I remember an unfinished discussion on this parameter.
Do you prefer it in % (more readable, like flow-proportion,  like in the display) or from 1..10 (like in the manual)?
100% full-infl and 0% empty   -vs-  10 full-infl and 0 empty
immi
After having checked both the manuals of 303 and 304 I noticed that in both manuals the allowed value range is same: 0 ... 10. So no change in  value range btw. 303 and 304(as I had expected before).For me it is unclear why SE doesn't have a clear logic, being same for all parameters. In the manual I see e.g.P15 range 0 ... 10P19 range 0 ... 100%It is a philosophic discussion if we use same values as SE (0 ... 10) or if we prefer the user friendly 0 ... 100% range. In case of the 0 ... 100% solution Mythz has to ensure that the division by 10 is done before the value is being transfered to the heatpump during set action (and multiplication by 10 in case of readings of course).

Now I checked which value range the display allows to be entered: it is 0 ... 100. So the value range of 0 ... 10 mentioned in the manual is simply a bug in the manual, which never had been fixed. The heatpump itself works with a 0 ... 100 range.

@belu:
Please check in your 304 which entries the display allows. I strongly believe that it is 0 ... 100 as well.

If that's the case the discussion can be stopped. In this case we do not need to change anything, since 0 ... 100 is used in the THZ as well as in FHEM.Mythz.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 21:31:33
THX@ Willy u understand me  ;)

Habe ich genau so gemacht, und leider ist E Heizen Tag 1,4 mal höher als der realer Verbrauch am EHZ
Und ja die Zähler sind alle um 0 Uhr auf 0, habe sogar die Uhrzeiten synchronisert.

Wie gesagt werde mich Montag nachmittag mal mit Stiebel Eltron in Verbindung setzen. Bin mal gespannt was sie da erklären werden.


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 21:35:01
Zitat von: willybauss am 10 Januar 2015, 21:27:48
@belu:
Please check in your 304 which entries the display allows. I strongly believe that it is 0 ... 100 as well.

If that's the case the discussion can be stopped. In this case we do not need to change anything, since 0 ... 100 is used in the THZ as well as in FHEM.Mythz.

Yes Willy, ure right, the same on thz 304 range 0 to 100.. i think its good..
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 10 Januar 2015, 22:27:09
Zitat von: immi am 10 Januar 2015, 16:57:37
Willy, Belu
I remember an unfinished discussion on this parameter.
Do you prefer it in % (more readable, like flow-proportion,  like in the display) or from 1..10 (like in the manual)?
100% full-infl and 0% empty   -vs-  10 full-infl and 0 empty
immi
Hi Markus
when you have time please fix it in the wiki. Otherwise I expect the same discussion again in 1/2year. Something like
"p15RoomInfluenceHC1 and flow-proportion go from 0% to 100% like in the display; the range 1..10 in the manual has to be considered a typo"
thanks a lot
Immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 22:42:06
@belu:
Ich komme nochmal zurück auf das Thema Steigung der Heizkurve. Ich habe 2 Kurven außergewöhnlicher Temperaturverläufe angehängt: Im Dezember wurde es plötzlich extrem kalt, heute das Gegenteil. Wenn die Steigung der Heizkurve gut zum Wärmebedarf des Hauses passt, dann kommt in beiden Fällen eine Innentemperatur heraus, die sehr stabil bleibt, trotz der extremen Veränderungen der Außentemperatur. Ich musste in beiden Fällen nicht eingreifen; die Regelung hat das selbst so gut hin bekommen.

Der Anstieg der Innentemperatur heute Nachmittag liegt an der Sonne, die durch die großen Südfenster mit geheizt hat. Die Wärmepumpe hat da ja nichts gemacht.

Nachtrag:
Es war auch nicht notwendig, die Sicherung des Heizstabs einzuschalten. Ich habe über die Parameter die WP so eingestellt, dass sie erst unterhalb von -7,5°C (Bivalenzpunkt) den Heizstab zum heizen benutzt - und dann braucht sie ihn ja auch. Den unnötigen Einsatz des Heizstabs fürs Warmwasser (2 mal im 1. Screenshot) habe ich durch vergrößern von p33 auf 90 Minuten jetzt auch unterbunden.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 10 Januar 2015, 22:45:53
Hallo,
seit einigen Wochen habe ich FHEM im Testbetrieb. Jetzt hab ich mich auch an das THZ-Modul gewagt. Ich hatte anfangs gezögert, weil ich eine sehr altes Modell habe und erst mal kein Risiko eingehen wollte. Meine THZ303SOL läuft noch mit der Firmware 2.14., ist ja schon seit dem Jahr 2003 im Einsatz. Mein Fazit: Das Modul 00_THZ läuft stabil, sehr gute Arbeit!!
Ich habe mich zunächst auf das Lesen der Statusregister fokussiert und die Werte in den Readings mit Werten im Serviceprogramm (LWZ303V405.exe) verglichen. Dabei habe ich das Attribut firmware="2.06" gesetzt.

1.  Die Register (Befehle) sLast10errors (D1) und sFirmware (FD) scheint es bei mir nicht zu geben.  Ich bekomme hier die Antwort "010301FD1003" bzw. 0103D5D11003 ( "msg2 command not known")

2. Die anderen Register 09, 16, FB, FC,  F3,  F4, F5 kann ich per FHEM auslesen. Das Register FB enthält auch bei Firmware 2.16  einige Status-Infos, die noch nicht im Reading sGlobal sind. Das würde ich gern noch anpassen. Ich habe die folgende Zuordung herausgefunden:

         [" boosterStage3: ",   44, 1, "bit3", 1],   [" solarPump: ",      44, 1, "bit2", 1],
         [" boosterStage1: ",   44, 1, "bit1", 1],   [" compressor: ",      44, 1, "bit0", 1],
         [" heatPipeValve: ",   45, 1, "bit3", 1],     [" diverterValve: ",      45, 1, "bit2", 1],
         [" dhwPump: ",      45, 1, "bit1", 1],     [" heatingCircuitPump: ",   45, 1, "bit0", 1],
           [" mixerOpen: ",      47, 1, "bit1", 1],
           [" mixerClosed: ",   47, 1, "bit0", 1],

Hat sonst noch jemand (mit Firmware 2.x)  Interesse an diesen Werten? Könnte das jemand testen/bestätigen?

Thanks,
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 10 Januar 2015, 23:01:27
Hi Andre,
willkommen im Forum und Glückwunsch zur selbständigen erfolgreichen Einrichtung des Mythz-Moduls. Der Einzige, der hier noch so einen Oldtimer hat, ist peter456. Ich nehme an, dass er sich auf Deine Frage meldet, andernfalls schreibe ihn einfach direkt an. Aber der hat keine SOL, wenn ich mich richtig erinnere, d.h. einen Teil der Parameter kann er nicht brauchen.

Ich habe die 303SOL Bj.2010, Inbetriebnahme 2011, FW Version 4.19. Mich würden Deine Langzeiterfahrungen interessieren bzgl. Ausfällen, Reparaturen etc. Damals wusste man ja auch noch nicht, dass die Rückschlagventile empfindlich auf Verkalkung reagieren. Stiebel Eltron hat ja im Lauf der Zeit die Vorschrift für die max. Wasserhärte immer weiter verschärft. Gibt es weitere Schwachstellen, auf die ich jetzt schon achten sollte?

Gruß
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 10 Januar 2015, 23:29:10
@ Willy,

schöne Plots, echt schön zu sehen, aber es waren ja auch rapide Änderungen an einem Tag 10 Grad in wenigen Stunden.

@ Andre,

Herzlich willkommen im Forum und direkt produktiv eingebracht, wunderbar!

Ich bin gerade dran das ich die ganzen Verbräuche mal triggern, aber das nicht so einfach.

Das erste was ich wollte ist die COP ableiten von Power QC und Power EL, so das man den aktuellen COP hat. Dann wollte ich den Verbrauch loggen, die investierte Heizenergie den Tages COP mit und ohne berücksichtigung der Rückgewinnung.

Scheitert aber schon das ich das mit dem Rechnen in den User Readings nicht hin bekomme, bzw monatlich plotten ist auch nicht so einfach...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 10 Januar 2015, 23:36:46
Hallo Willi,

ja wir haben einen echten Oldtimer, aber bisher keine Probleme gehabt. Wir hatten in all den Jahren nur einmal einen festen Lüfter, der dann getauscht werden musste. Zuluft- oder Abluft, ich müsste in den Akten wühlen, falls dich das genau interessiert.
Vor drei Wochen hatte ich dann eine Problem mit dem Kondenswaserabfluss, eine Schwachstelle bei den alten Modellen. Der Ablauf war verstopft, so dass das Wasser in den Boden gelaufen ist. Zum Glück habe ich es (hoffentlich) rechtzeitig gemerkt. Hier kann ich nur empfehlen einmal im Jahr den Abflussschlauch zu reinigen. Ich hatte das die letzten Jahre vernachlässigt. In einem anderen Forum habe ich gelesen, das jemand dadurch 140TEUR Folgeschaden hatte, weil Schimmel im Haus.  Ich werde mir jetzt sicherheitshalber gleich 2 Wassermelder in den Boden der THZ einbauen.
Zum Thema Wasserhärte habe ich mir noch gar keine Gedanken gemacht. Wir haben hier Wasserhärte jenseits von Gut und Böse (25 °dH), aber der WP hat es noch nicht geschadet.

Gruss
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Januar 2015, 00:22:10
@Willy: Ich hab es anfangs nicht glauben wollen, aber nach 2 Tagen Testung kann ich es nicht leugnen: Die Dämmung des Wassertanks zeigt Wirkung und welche!!!
Dabei gibt es m.E. folgendes zu bedenken. Die 7 cm (Perimeter)Dämmung ringsherum um den Tank sind nicht schlecht. Da passt auch nicht wirklich was an Dämmung noch rein. Die Schwachstelle (nach Abtasten und Abgreifen) liegt unter dem Tank. Dort ist fast gr nicht gedämmt. Normalerweise fällt das nicht ins Gewicht, wenn die LWZ im Haus auf gedämmter Bodenplatte steht. Doch wie bei Willy und mir steht die auf dem Rohkellerfussboden mit 4 cm Estrich drauf (nehme ich mal an). Ich habe dort auch keine Dämmung unter der Bodenplatte. Also hab ich alte kleine Mineralwollstücke (die ich entsorgen wolle) unten drunter richtig gut gestopft.
Nach 2 tagen Test (mit Wasserentnahme im 4 Personenhaushalt) kann ich abschätzen, daß sich die Auskühlungszeit um fast 50% verlangsamt hat. Wenn ich mal einen ganzen Tag keine Entnahme habe wegen Abwesenheit werd ich mal die echten Daten und Graphen durchgeben. Dadurch brauch ich nur noch 50% der Aufheizenergie für WW und beim Duschen hab ich seltener WW, das relativ kühl ist, weil kurz vor dem Aufheizen.
Danke für den phänomenalen Tip! :) Ich kann es nur jedem empfehlen!

Zur Spreizung: Hab die Durchflussrate von 6 auf 4,5 runtergestellt. Effekt ist aber klein: alt: 2,5°C neu: 3,2°C. Momentan kann ich nicht weiter testen, weil der Ofen läuft und es war genug draussen ist. Hab den Raumeinfluss auf 66% runtergestellt, damit das System flexibler auf Aussentemp. reagieren kann.


@AndreK: Willkommen im Forum. Hast Du Wartung immer selber gemacht oder eine Vertrag mit Stiebel. Ist ja gut zu wissen, daß es in 11 Jahren keine grossen Probleme gegeben hat. Ist die 303er Serie nicht sogar 2003 erst auf den Markt gekommen? Den Abflussschlauch vernachlässige ich auch immer, der setzt sich ganz schön zu. Man kommt aber auch so schlecht ran. Wer ich in die jährliche Wartung mit aufnehmen. Befreist Du die Lüfter vom Staub mit einem Pinsel?

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 Januar 2015, 09:51:49
Zitat von: andre.k am 10 Januar 2015, 22:45:53
Hallo,
seit einigen Wochen habe ich FHEM im Testbetrieb. Jetzt hab ich mich auch an das THZ-Modul gewagt. Ich hatte anfangs gezögert, weil ich eine sehr altes Modell habe und erst mal kein Risiko eingehen wollte. Meine THZ303SOL läuft noch mit der Firmware 2.14., ist ja schon seit dem Jahr 2003 im Einsatz. Mein Fazit: Das Modul 00_THZ läuft stabil, sehr gute Arbeit!!
Ich habe mich zunächst auf das Lesen der Statusregister fokussiert und die Werte in den Readings mit Werten im Serviceprogramm (LWZ303V405.exe) verglichen. Dabei habe ich das Attribut firmware="2.06" gesetzt.

1.  Die Register (Befehle) sLast10errors (D1) und sFirmware (FD) scheint es bei mir nicht zu geben.  Ich bekomme hier die Antwort "010301FD1003" bzw. 0103D5D11003 ( "msg2 command not known")

2. Die anderen Register 09, 16, FB, FC,  F3,  F4, F5 kann ich per FHEM auslesen. Das Register FB enthält auch bei Firmware 2.16  einige Status-Infos, die noch nicht im Reading sGlobal sind. Das würde ich gern noch anpassen. Ich habe die folgende Zuordung herausgefunden:

         [" boosterStage3: ",   44, 1, "bit3", 1],   [" solarPump: ",      44, 1, "bit2", 1],
         [" boosterStage1: ",   44, 1, "bit1", 1],   [" compressor: ",      44, 1, "bit0", 1],
         [" heatPipeValve: ",   45, 1, "bit3", 1],     [" diverterValve: ",      45, 1, "bit2", 1],
         [" dhwPump: ",      45, 1, "bit1", 1],     [" heatingCircuitPump: ",   45, 1, "bit0", 1],
           [" mixerOpen: ",      47, 1, "bit1", 1],
           [" mixerClosed: ",   47, 1, "bit0", 1],


Hi Andre
welcome to fhem.
I merged your hint with the info given by peter345.
I uploaded v0.125 with this change. Tomorrow you can upgrade fhem; please check for typos.
--
I find strange that you cannot read the FD register.
I would suggest that you try to read all register from 00 to FF:
I implemented a debug command for that:

get Mythz debug_read_raw_register_slow

It locks fhem for some minutes and at the end writes the results in logfile and in the filesystem "data.txt".
It makes very sense that you share all your register-outputs, uploading in the forum data.txt

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Januar 2015, 11:03:19
Zitat von: andre.k am 10 Januar 2015, 23:36:46
Hallo Willi,

ja wir haben einen echten Oldtimer, aber bisher keine Probleme gehabt. Wir hatten in all den Jahren nur einmal einen festen Lüfter, der dann getauscht werden musste. Zuluft- oder Abluft, ich müsste in den Akten wühlen, falls dich das genau interessiert.
Vor drei Wochen hatte ich dann eine Problem mit dem Kondenswaserabfluss, eine Schwachstelle bei den alten Modellen. Der Ablauf war verstopft, so dass das Wasser in den Boden gelaufen ist. Zum Glück habe ich es (hoffentlich) rechtzeitig gemerkt. Hier kann ich nur empfehlen einmal im Jahr den Abflussschlauch zu reinigen. Ich hatte das die letzten Jahre vernachlässigt. In einem anderen Forum habe ich gelesen, das jemand dadurch 140TEUR Folgeschaden hatte, weil Schimmel im Haus.  Ich werde mir jetzt sicherheitshalber gleich 2 Wassermelder in den Boden der THZ einbauen.
Zum Thema Wasserhärte habe ich mir noch gar keine Gedanken gemacht. Wir haben hier Wasserhärte jenseits von Gut und Böse (25 °dH), aber der WP hat es noch nicht geschadet.

Gruss
Andre
Hi Andre,
gut zu wissen, dass die Anlage solide läuft. Vermutlich wurde Dein Heizungswasser beim Befüllen aufbereitet. Bei Leuten, die das nicht machten, ist das HaustechnikDialog-Forum voll von Problemmeldungen wegen verkalkter Rückschlagventile und Heizsträngen mit Thrombose. Evtl. sollte ich mir innerhalb der Anlage auch nochmal einen Wassermelder einbauen. Bislang liegt nur unter der Kondensathebeanlage einer.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Januar 2015, 11:12:30
Zitat von: houseowner123 am 11 Januar 2015, 00:22:10
@Willy: Ich hab es anfangs nicht glauben wollen, aber nach 2 Tagen Testung kann ich es nicht leugnen: Die Dämmung des Wassertanks zeigt Wirkung und welche!!!
Ich muss ehrlich gestehen, dass ich vor dem Dämmen entgegen meiner Gewohnheit gar keine Temperaturmessung gemacht hatte. Insofern keine Ahnung, wo es am Wichtigsten ist. Bei mir steht die Anlage zwar abgekoppelt vom Estrich auf einem Podest auf dem Rohfußboden (=Schall-/Schwingungsentkopplung), aber auch das Podest besteht aus Dämmmaterial.

Wegen der Spreizung schlage ich vor, mal eine Durchflussmessung zu machen. Die findest Du im Fachmannmenü. Sie dauert ein paar Minuten; vor der Durchführung solltest Du Dir den entsprechenden Absatz im Installationsmanual durchlesen. Anschließend weisst Du, wie weit weg vom erlaubten Mindestdurchfluss (550 Liter pro Stunde bei der 303) Du bist. Während der Messung sollten aber alle Thermostatventile zu sein, so dass nur diejenigen Heizkreise in die Messung einfließen, die direkt angebunden, d.h. ständig offen sind. Sonst stellst Du einen zu geringen Wert ein und es kann passieren, dass in einer unglücklichen Situation der Mindestdurchfluss unterschritten wird.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 11 Januar 2015, 11:16:07
Zitat von: godmorgon am 04 Januar 2015, 20:59:12
@immi
Indeed 303x series don't seem to have humidity sensors. Since the humidity value is not provided on display I don't know what to search for in the binary values.

Some examples of my 0xfb messages (the bytes presumed to store Qc and Pel are marked):
01 00 54 fb fd a8 00 16 01 3d 01 08 02 69 01 e7 fd a8 fd a8 00 0d 01 2b 60 08 11 01 5e 01 5e 02 bc 00 00 00 00 00 15 00 19 00 00 00 00 01 2d 04 f2 45 d8 df 9f 3f c4 9b a6 07 c5 00 b1 01 6d 00 00 01 08 01 38 00 13 00 02 01 09 00 00 00 00 0f ff
01 00 69 fb fd a8 00 17 01 3d 01 08 02 78 01 e7 fd a8 fd a8 00 10 01 1d 60 08 11 01 5e 01 5e 02 bc 00 0e 00 18 00 14 00 19 00 00 00 00 01 3c 05 24 45 d7 6d 7d 3f cd 91 69 07 fa 00 b1 01 6f 00 00 01 07 01 3a 00 1d 00 0a 01 17 00 00 00 00 0f 23
01 00 ea fb fd a8 00 16 01 44 01 08 02 49 01 e6 fd a8 fd a8 00 1c 01 17 60 08 11 00 00 00 00 02 bc 00 00 00 00 00 14 00 19 00 00 00 00 01 4c 05 30 46 00 d5 8f 3f d4 7a e2 07 c5 00 b1 01 2a 00 00 01 06 01 44 ff f4 ff de 01 23 00 00 00 00 10 3e
I don't see how these huge values could possibly correspond to valid kWh.

I was able to decode the following THZ404SOL registers:
0a 033b - flow rate/Volumenstrom, 0.1 l/min
0a 064f - hum. masking time/Feuchte Maskierzeit, min
0a 0650 - hum. threshold value/Feuchte Schwellwert, %
0a 06a4 - output reduction/Leistungsreduktion, %
0a 06a5 - output increase/Leistungserhöhung, %
0a 09d1 - humidity protection/Feuchteschutz, bool
0a 09d2 - set humidity min/Feuchte Soll min, %
0a 09d3 - set humidity max/Feuchte Soll max, %

By the way, the 0x0c command seems to mirror the values of the 0x0b command.

@ Immi can u add the other lines

0a 033b - flow rate/Volumenstrom, 0.1 l/min
0a 064f - hum. masking time/Feuchte Maskierzeit, min
0a 0650 - hum. threshold value/Feuchte Schwellwert, %
0a 06a4 - output reduction/Leistungsreduktion, %
0a 06a5 - output increase/Leistungserhöhung, %
0a 09d1 - humidity protection/Feuchteschutz, bool
0a 09d2 - set humidity min/Feuchte Soll min, %
0a 09d3 - set humidity max/Feuchte Soll max, %


THX
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Januar 2015, 11:22:45
Zitat von: immi am 11 Januar 2015, 09:51:49
I would suggest that you try to read all register from 00 to FF:
I implemented a debug command for that:

get Mythz debug_read_raw_register_slow

It locks fhem for some minutes and at the end writes the results in logfile and in the filesystem "data.txt".
It makes very sense that you share all your register-outputs, uploading in the forum data.txt

immi
I tried to do so, but the command ended within a few seconds and logged  just a few registers:
FB-76FBFDA80029016A0168035B015DFDA800E0FFC901761008110168012202BC0015001D00140022011B000001800645408B367A3FAB74BC
01-D101FDA8002901
FB-56FBFDA80029016A01680360015DFDA800E0FFCA01761008110168012202BC0015001D00140022011B000001800649408AF78F3FABA68B
FE-12FE03B1839100010002806B0006674902084D6172202039203230313120
00-010001001003-010304001003-command not known
0A05D1-E10A05D10000
0A010D-0100190A010D1003-01041D0A010D1003-UNKNOWN REQUEST


What am I doing wrong?

Another question: wouldn't it make sense to write data.txt to the same location as Mythz.log, instead of  /opt/fhem/ ?   /opt/fhem/ is located on the SD card in case of a RaspberryPi, while the log directory is (in my case) on a mounted share on my NAS, in order to take care of the limited number of write cycles of the SD card.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 11 Januar 2015, 11:41:06
Zitat von: willybauss am 11 Januar 2015, 11:22:45
Another question: wouldn't it make sense to write data.txt to the same location as Mythz.log, instead of  /opt/fhem/ ?   /opt/fhem/ is located on the SD card in case of a RaspberryPi, while the log directory is (in my case) on a mounted share on my NAS, in order to take care of the limited number of write cycles of the SD card.

@ Willy, du aktivierst das ja nicht ständig, deswegen sollte es egal sein, wenn man es jetzt immer wieder diese Datei schreiben würde könnte man eine kleine Ramdisk erzeugen und es darin abspeichern, aber das ist halt Systemabhängig.
Mir macht es nichts aus wenn ich es ab und zu starte.

Habe es gerade mal gestartet...

get Mythz debug_read_raw_register_slow

FHEM: all raw registers read and saved

data.txt:

01-77010019FF5D00
02-010003021003-010306021003-command not known
03-010004031003-010307031003-command not known
04-010005041003-010308041003-command not known
05-010006051003-010309051003-command not known
06-010007061003-01030A061003-command not known
07-010008071003-01030B071003-command not known
08-010009081003-01030C081003-command not known
09-92090602000002D201A50006
0A-01000B0A1003-02-new unknown answer

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 Januar 2015, 12:33:43
Zitat von: willybauss am 11 Januar 2015, 11:22:45
I tried to do so, but the command ended within a few seconds and logged  just a few registers:
..
What am I doing wrong?
Hi Willy
Nothing wrong, you have an older version of thz-fhem. I use the sub THZ_debugread (line1241) for debugging and I change it very often. You can select some register manually  or select an intervall, just by uncommenting some lines.
I need to debug Andre´s old firmware.

Zitat von: belu am 11 Januar 2015, 11:16:07
@ Immi can u add the other lines
0a 033b - flow rate/Volumenstrom, 0.1 l/min
0a 064f - hum. masking time/Feuchte Maskierzeit, min
0a 0650 - hum. threshold value/Feuchte Schwellwert, %
0a 06a4 - output reduction/Leistungsreduktion, %
0a 06a5 - output increase/Leistungserhöhung, %
0a 09d1 - humidity protection/Feuchteschutz, bool
0a 09d2 - set humidity min/Feuchte Soll min, %
0a 09d3 - set humidity max/Feuchte Soll max, %

I cannot just add it, because they are not working for my firmware.
I have to think how to manage it, maybe with an attribute like for Peter.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 11 Januar 2015, 13:53:11
Hi immi,

thank you for your answer.

I'll check v0.125 tomorrow. In the meantime I tried to debug all registers from 1..FF, but I got only two entries in the logfile:
2015.01.11 13:21:51 3: 01  -  010002011003-02-new unknown answer
2015.01.11 13:21:52 3: 02  -  010003021003-1002-new unknown answer
2015.01.11 13:21:52 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.11 13:21:53 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

I changed the debug routine a little bit.
my @numbers = (9..256);


and I got the log:
2015.01.11 13:28:10 3: 09  -  5509015E015D870C35C60000000000
2015.01.11 13:28:10 3: 0A  -  01000B0A1003-02-new unknown answer
2015.01.11 13:28:11 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.11 13:28:12 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

It seems to be timing issue.

Andre

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 11 Januar 2015, 16:36:07
@Immi,

i have checked


Added in getsonly
"sFlowrate"                     => {cmd2=>"0A033B", cmd3=>"0A033B",     type =>"1clean", unit =>" cl/min"},

Outpud is Flowrate in Centiliter / min
THZ Display 19,1 Output lik 191 cl/min

i make a interval an test over time.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Januar 2015, 17:27:53
Zitat von: willybauss am 11 Januar 2015, 11:12:30
Während der Messung sollten aber alle Thermostatventile zu sein, so dass nur diejenigen Heizkreise in die Messung einfließen, die direkt angebunden, d.h. ständig offen sind. Sonst stellst Du einen zu geringen Wert ein und es kann passieren, dass in einer unglücklichen Situation der Mindestdurchfluss unterschritten wird.

Ich hab mir den Satz paar mal durchgelesen, verstehe ihn nicht. Wenn nicht geheizt wird sind noch per default alle Heizkreise zu über die Regler? Da ist keine ständig offen. Oder missverstehe ich da was?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 11 Januar 2015, 17:35:14
@ Houseownwer.

Die Anlage braucht einen Mindestdurchfluss von 550 l/h also mehr wie 9 l/m.

Wenn die nicht errei hat werden geht die Heizung am Störung. Wenn alle Heizkreise geschlossen sind hast ja theoretisch 0 durchfluss. Wenn die Heizung trotzdem heizt wegen niedrigen Außentemperaturen kommt dann eine Störung. Um das zu umgehen gibt es 2 Möglichkeiten die ich kenne. Einen Kreis immer offen lassen der als Bypass dient und über den die 9 l /m laufen. Oder eine Hadraulische weiche. Hab die heute Mittag eingestellt. Alle Kreise zu umwälzpumpe laufen lassen und dann auf etwas mehr wie 9 l eingestellt.

Es muss immer gewährleistet sein das durchfluss  da ist. Die anlag ist ja im default 30 / 70 Vorlauf Rücklauf gesteuert. Das heißt die Anlage muss umwälzen damit sie weis wie warm der Boden ist um dann die den hc 1 set Point zu erreichen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Januar 2015, 17:58:02
Zitat von: belu am 11 Januar 2015, 17:35:14
@ Houseownwer.

Die Anlage braucht einen Mindestdurchfluss von 550 l/h also mehr wie 9 l/m.

Wenn die nicht errei hat werden geht die Heizung am Störung. Wenn alle Heizkreise geschlossen sind hast ja theoretisch 0 durchfluss. Wenn die Heizung trotzdem heizt wegen niedrigen Außentemperaturen kommt dann eine Störung. Um das zu umgehen gibt es 2 Möglichkeiten die ich kenne. Einen Kreis immer offen lassen der als Bypass dient und über den die 9 l /m laufen. Oder eine Hadraulische weiche. Hab die heute Mittag eingestellt. Alle Kreise zu umwälzpumpe laufen lassen und dann auf etwas mehr wie 9 l eingestellt.

Es muss immer gewährleistet sein das durchfluss  da ist. Die anlag ist ja im default 30 / 70 Vorlauf Rücklauf gesteuert. Das heißt die Anlage muss umwälzen damit sie weis wie warm der Boden ist um dann die den hc 1 set Point zu erreichen.
Stimmt soweit. Bei mir wurde das so realisiert, dass es 2 Heizkreise gibt, die immer offen sind. Das sind die Flure in EG und OG. Die haben nur sehr wenige Heizschlangen, heizen deshalb nur wenig mit, aber sorgen eben für einen Mindestdurchfluss, wenn alle anderen Heizkreise zu sind.
Die hydraulisch Weiche gabs zusätzlich - sicherheitshalber. Aber die habe ich komplett zu gedreht. Nachdem ich die Thermostatventile wegrationalisiert hatte sind ja immer alle Heizkreise offen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 11 Januar 2015, 18:21:00
Danke für die Erklärung willy und belu.
Die Raumthermostate sind immer alle auf max. offen gestellt.
zu den Ventilen im Verteiler: Sind die stromlos dann immer offen? Also nur einen im EG und einen EG von den Ventilen abschrauben? Richtig?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 11 Januar 2015, 18:27:04
@Houseowner,

Ohne Ventil sind die Heizkreise offen. Die Ventile gibt's als NC normaly close oder NO normaly open. Würde es eher abziehen dann bist sicher. In der Regel NC verbaut. Stromlos geschlossen.

Ich hab echt Geld ausgegeben habe in meine sind Stetige Ventile 0-10 V ich muss mal schauen wie ich alles trotzdem hinbekomme das die THZ nicht taktet.
Hatte eigentlich nicht vor immer alle offen zu lassen. Mal schauen was mehr Energie spart. Evt Kompositionen aus beiden wenn die Heizkurve sehr knapp ist.

Wäre echt doof habe überall analoge Sensoren und fuzzy Logic regler für 0-10 v

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 11 Januar 2015, 18:51:54
Zitat von: belu am 11 Januar 2015, 18:27:04
Hatte eigentlich nicht vor immer alle offen zu lassen.
Kannst ja nach dem perfekten hydraulischen Abgleich wieder die Ventile in Betrieb nehmen und die Heizkurve um 1 - 2° parallel nach oben verschieben. Dann haben die Ventile eine Regelreserve und das Geld war nicht umsonst. So kann auch Jeder im seinem Zimmer die Temperatur etwas höher stellen, wenn er das möchte.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 Januar 2015, 19:10:04
Zitat von: andre.k am 11 Januar 2015, 13:53:11
Hi immi,

thank you for your answer.

I'll check v0.125 tomorrow. In the meantime I tried to debug all registers from 1..FF, but I got only two entries in the logfile:
2015.01.11 13:21:51 3: 01  -  010002011003-02-new unknown answer
2015.01.11 13:21:52 3: 02  -  010003021003-1002-new unknown answer
2015.01.11 13:21:52 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.11 13:21:53 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

I changed the debug routine a little bit.
my @numbers = (9..256);


and I got the log:
2015.01.11 13:28:10 3: 09  -  5509015E015D870C35C60000000000
2015.01.11 13:28:10 3: 0A  -  01000B0A1003-02-new unknown answer
2015.01.11 13:28:11 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.11 13:28:12 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

It seems to be timing issue.

Andre


Hi Andre
you are sending too many commands to the heatpump in a short time.
If you want you can change line 1283
select(undef, undef, undef, 3);
in this way it will wait 3 seconds between each command/register
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 11 Januar 2015, 21:41:17
Hi immo,

it's better with 3 sec. wait time, but I run still in a timeout.
I don't understand why we got the "02-new unknown answer". I would expect return code 0100 or 1003.

2015.01.11 21:19:49 3: 01  -  010002011003-02-new unknown answer
2015.01.11 21:19:53 3: 02  -  010003021003-02-new unknown answer
2015.01.11 21:19:56 3: 03  -  010004031003-02-new unknown answer
2015.01.11 21:19:59 3: 04  -  010005041003-02-new unknown answer
2015.01.11 21:20:02 3: 05  -  010006051003-02-new unknown answer
2015.01.11 21:20:05 3: 06  -  010007061003-02-new unknown answer
2015.01.11 21:20:08 3: 07  -  010008071003-0201002F07145A00281E0C006403001003-new unknown answer
2015.01.11 21:20:11 3: 08  -  010009081003-02-new unknown answer
2015.01.11 21:20:15 3: 09  -  01000A091003-02-new unknown answer
2015.01.11 21:20:18 3: 0A  -  A60A010064000000BE0078
2015.01.11 21:20:21 3: 0B  -  01000C0B1003-02-new unknown answer
2015.01.11 21:20:24 3: 0C  -  01000D0C1003-02-new unknown answer
2015.01.11 21:20:27 3: 0D  -  01000E0D1003-02-new unknown answer
2015.01.11 21:20:30 3: 0E  -  01000F0E1003-02-new unknown answer
2015.01.11 21:20:33 3: 0F  -  010010100F1003-02-new unknown answer
2015.01.11 21:20:37 3: 10  -  01001110101003-02-new unknown answer
2015.01.11 21:20:40 3: 11  -  010012111003-02-new unknown answer
2015.01.11 21:20:44 3: myWP THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 11 Januar 2015, 22:55:20
Hi Andre
this is the scan of my 00 to ff (how it should look like)

01-C4010100309100
02-010003021003-010306021003-command not known
03-010004031003-010307031003-command not known
04-010005041003-010308041003-command not known
05-010006051003-010309051003-command not known
06-010007061003-01030A061003-command not known
07-010008071003-01030B071003-command not known
08-010009081003-01030C081003-command not known
09-FE0905FB00000422000100CD
0A-01000B0A1003-01040F0A05FB1003-UNKNOWN REQUEST
0B-01000C0B1003-0104100B05FB1003-UNKNOWN REQUEST
0C-01000D0C1003-0104110C05FB1003-UNKNOWN REQUEST
0D-01000E0D1003-0103110D1003-command not known
0E-01000F0E1003-0103120E1003-command not known
0F-010010100F1003-0103130F1003-command not known
10-01001110101003-010314101003-command not known
11-010012111003-010315111003-command not known
12-010013121003-010316121003-command not known
13-010014131003-010317131003-command not known
14-010015141003-010318141003-command not known
15-010016151003-010319151003-command not known
16-1116FDA8011D00AF00000A003C20001111
17-010018171003-01031B171003-command not known
18-010019181003-01031C181003-command not known
19-01001A191003-01031D191003-command not known
1A-01001B1A1003-01031E1A1003-command not known
1B-01001C1B1003-01031F1B1003-command not known
1C-01001D1C1003-0103201C1003-command not known
1D-01001E1D1003-0103211D1003-command not known
1E-01001F1E1003-0103221E1003-command not known
1F-0100201F1003-0103231F1003-command not known
20-010021201003-010324201003-command not known
21-010022211003-010325211003-command not known
22-010023221003-010326221003-command not known
23-010024231003-010327231003-command not known
24-010025241003-010328241003-command not known
25-010026251003-010329251003-command not known
26-010027261003-01032A261003-command not known
27-010028271003-01032B271003-command not known
28-010029281003-01032C281003-command not known
29-01002A291003-01032D291003-command not known
2A-01002B182A1003-01032E2A1003-command not known
2B-01002C2B181003-01032F2B1003-command not known
2C-01002D2C1003-0103302C1003-command not known
2D-01002E2D1003-0103312D1003-command not known
2E-01002F2E1003-0103322E1003-command not known
2F-0100302F1003-0103332F1003-command not known
30-010031301003-010334301003-command not known
31-010032311003-010335311003-command not known
32-010033321003-010336321003-command not known
33-010034331003-010337331003-command not known
34-010035341003-010338341003-command not known
35-010036351003-010339351003-command not known
36-010037361003-01033A361003-command not known
37-010038371003-01033B371003-command not known
38-010039381003-01033C381003-command not known
39-01003A391003-01033D391003-command not known
3A-01003B3A1003-01033E3A1003-command not known
3B-01003C3B1003-01033F3B1003-command not known
3C-01003D3C1003-0103403C1003-command not known
3D-01003E3D1003-0103413D1003-command not known
3E-01003F3E1003-0103423E1003-command not known
3F-0100403F1003-0103433F1003-command not known
40-010041401003-010344401003-command not known
41-010042411003-010345411003-command not known
42-010043421003-010346421003-command not known
43-010044431003-010347431003-command not known
44-010045441003-010348441003-command not known
45-010046451003-010349451003-command not known
46-010047461003-01034A461003-command not known
47-010048471003-01034B471003-command not known
48-010049481003-01034C481003-command not known
49-01004A491003-01034D491003-command not known
4A-01004B4A1003-01034E4A1003-command not known
4B-01004C4B1003-01034F4B1003-command not known
4C-01004D4C1003-0103504C1003-command not known
4D-01004E4D1003-0103514D1003-command not known
4E-01004F4E1003-0103524E1003-command not known
4F-0100504F1003-0103534F1003-command not known
50-010051501003-010354501003-command not known
51-010052511003-010355511003-command not known
52-010053521003-010356521003-command not known
53-010054531003-010357531003-command not known
54-010055541003-010358541003-command not known
55-010056551003-010359551003-command not known
56-010057561003-01035A561003-command not known
57-010058571003-01035B571003-command not known
58-010059581003-01035C581003-command not known
59-01005A591003-01035D591003-command not known
5A-01005B5A1003-01035E5A1003-command not known
5B-01005C5B1003-01035F5B1003-command not known
5C-01005D5C1003-0103605C1003-command not known
5D-01005E5D1003-0103615D1003-command not known
5E-01005F5E1003-0103625E1003-command not known
5F-0100605F1003-0103635F1003-command not known
60-010061601003-010364601003-command not known
61-010062611003-010365611003-command not known
62-010063621003-010366621003-command not known
63-010064631003-010367631003-command not known
64-010065641003-010368641003-command not known
65-010066651003-010369651003-command not known
66-010067661003-01036A661003-command not known
67-010068671003-01036B671003-command not known
68-010069681003-01036C681003-command not known
69-01006A691003-01036D691003-command not known
6A-01006B6A1003-01036E6A1003-command not known
6B-01006C6B1003-01036F6B1003-command not known
6C-01006D6C1003-0103706C1003-command not known
6D-01006E6D1003-0103716D1003-command not known
6E-01006F6E1003-0103726E1003-command not known
6F-0100706F1003-0103736F1003-command not known
70-010071701003-010374701003-command not known
71-010072711003-010375711003-command not known
72-010073721003-010376721003-command not known
73-010074731003-010377731003-command not known
74-010075741003-010378741003-command not known
75-010076751003-010379751003-command not known
76-010077761003-01037A761003-command not known
77-010078771003-01037B771003-command not known
78-010079781003-01037C781003-command not known
79-01007A791003-01037D791003-command not known
7A-01007B7A1003-01037E7A1003-command not known
7B-01007C7B1003-01037F7B1003-command not known
7C-01007D7C1003-0103807C1003-command not known
7D-01007E7D1003-0103817D1003-command not known
7E-01007F7E1003-0103827E1003-command not known
7F-0100807F1003-0103837F1003-command not known
80-010081801003-010384801003-command not known
81-010082811003-010385811003-command not known
82-010083821003-010386821003-command not known
83-010084831003-010387831003-command not known
84-010085841003-010388841003-command not known
85-010086851003-010389851003-command not known
86-010087861003-01038A861003-command not known
87-010088871003-01038B871003-command not known
88-010089881003-01038C881003-command not known
89-01008A891003-01038D891003-command not known
8A-01008B8A1003-01038E8A1003-command not known
8B-01008C8B1003-01038F8B1003-command not known
8C-01008D8C1003-0103908C1003-command not known
8D-01008E8D1003-0103918D1003-command not known
8E-01008F8E1003-0103928E1003-command not known
8F-0100908F1003-0103938F1003-command not known
90-010091901003-010394901003-command not known
91-010092911003-010395911003-command not known
92-010093921003-010396921003-command not known
93-010094931003-010397931003-command not known
94-010095941003-010398941003-command not known
95-010096951003-010399951003-command not known
96-010097961003-01039A961003-command not known
97-010098971003-01039B971003-command not known
98-010099981003-01039C981003-command not known
99-01009A991003-01039D991003-command not known
9A-01009B9A1003-01039E9A1003-command not known
9B-01009C9B1003-01039F9B1003-command not known
9C-01009D9C1003-0103A09C1003-command not known
9D-01009E9D1003-0103A19D1003-command not known
9E-01009F9E1003-0103A29E1003-command not known
9F-0100A09F1003-0103A39F1003-command not known
A0-0100A1A01003-0103A4A01003-command not known
A1-0100A2A11003-0103A5A11003-command not known
A2-0100A3A21003-0103A6A21003-command not known
A3-0100A4A31003-0103A7A31003-command not known
A4-0100A5A41003-0103A8A41003-command not known
A5-0100A6A51003-0103A9A51003-command not known
A6-0100A7A61003-0103AAA61003-command not known
A7-0100A8A71003-0103ABA71003-command not known
A8-0100A9A81003-0103ACA81003-command not known
A9-0100AAA91003-0103ADA91003-command not known
AA-0100ABAA1003-0103AEAA1003-command not known
AB-0100ACAB1003-0103AFAB1003-command not known
AC-0100ADAC1003-0103B0AC1003-command not known
AD-0100AEAD1003-0103B1AD1003-command not known
AE-0100AFAE1003-0103B2AE1003-command not known
AF-0100B0AF1003-0103B3AF1003-command not known
B0-0100B1B01003-0103B4B01003-command not known
B1-0100B2B11003-0103B5B11003-command not known
B2-0100B3B21003-0103B6B21003-command not known
B3-0100B4B31003-0103B7B31003-command not known
B4-0100B5B41003-0103B8B41003-command not known
B5-0100B6B51003-0103B9B51003-command not known
B6-0100B7B61003-0103BAB61003-command not known
B7-0100B8B71003-0103BBB71003-command not known
B8-0100B9B81003-0103BCB81003-command not known
B9-0100BAB91003-0103BDB91003-command not known
BA-0100BBBA1003-0103BEBA1003-command not known
BB-0100BCBB1003-0103BFBB1003-command not known
BC-0100BDBC1003-0103C0BC1003-command not known
BD-0100BEBD1003-0103C1BD1003-command not known
BE-0100BFBE1003-0103C2BE1003-command not known
BF-0100C0BF1003-0103C3BF1003-command not known
C0-0100C1C01003-0103C4C01003-command not known
C1-0100C2C11003-0103C5C11003-command not known
C2-0100C3C21003-0103C6C21003-command not known
C3-0100C4C31003-0103C7C31003-command not known
C4-0100C5C41003-0103C8C41003-command not known
C5-0100C6C51003-0103C9C51003-command not known
C6-0100C7C61003-0103CAC61003-command not known
C7-0100C8C71003-0103CBC71003-command not known
C8-0100C9C81003-0103CCC81003-command not known
C9-0100CAC91003-0103CDC91003-command not known
CA-0100CBCA1003-0103CECA1003-command not known
CB-0100CCCB1003-0103CFCB1003-command not known
CC-0100CDCC1003-0103D0CC1003-command not known
CD-0100CECD1003-0103D1CD1003-command not known
CE-0100CFCE1003-0103D2CE1003-command not known
CF-0100D0CF1003-0103D3CF1003-command not known
D0-0100D1D01003-0103D4D01003-command not known
D1-D2D10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
D2-A6D28251
D3-0100D4D31003-0103D7D31003-command not known
D4-0100D5D41003-0103D8D41003-command not known
D5-0100D6D51003-0103D9D51003-command not known
D6-0100D7D61003-0103DAD61003-command not known
D7-0100D8D71003-0103DBD71003-command not known
D8-0100D9D81003-0103DCD81003-command not known
D9-0100DAD91003-0103DDD91003-command not known
DA-0100DBDA1003-0103DEDA1003-command not known
DB-0100DCDB1003-0103DFDB1003-command not known
DC-0100DDDC1003-0103E0DC1003-command not known
DD-0100DEDD1003-0103E1DD1003-command not known
DE-0100DFDE1003-0103E2DE1003-command not known
DF-0100E0DF1003-0103E3DF1003-command not known
E0-0100E1E01003-0103E4E01003-command not known
E1-0100E2E11003-0103E5E11003-command not known
E2-0100E3E21003-0103E6E21003-command not known
E3-0100E4E31003-0103E7E31003-command not known
E4-0100E5E41003-0103E8E41003-command not known
E5-0100E6E51003-0103E9E51003-command not known
E6-0100E7E61003-0103EAE61003-command not known
E7-0100E8E71003-0103EBE71003-command not known
E8-CAE8020001E3D60001EDBB0001C9120001E29E00000000000000000E10000000000000000001
E9-FAE900000000053A03C003E8000000000000001111000000000100
EA-0100EBEA1003-0103EEEA1003-command not known
EB-0100ECEB1003-0103EFEB1003-command not known
EC-0100EDEC1003-0103F0EC1003-command not known
ED-0100EEED1003-0103F1ED1003-command not known
EE-0100EFEE1003-0103F2EE1003-command not known
EF-0100F0EF1003-0103F3EF1003-command not known
F0-0100F1F01003-0103F4F01003-command not known
F1-0100F2F11003-0103F5F11003-command not known
F2-0DF205050000000000000000000001010E0000
F3-BBF3011B0033011800000000000000030003B3A6
F4-FFF40032FE2B00AFFFF200AF00CC00AE00010001000000650300000000A0010D160000A00200001600
F5-17F5003300B0FDA800CF00B0FC18000100000300000200000000
F6-07F600001000000000
F7-0100F8F71003-0103FBF71003-command not known
F8-0100F9F81003-0103FCF81003-command not known
F9-0100FAF91003-0103FDF91003-command not known
FA-0100FBFA1003-0103FEFA1003-command not known
FB-60FBFDA8003300AF00B000B6011EFDA8FDA8006400B20000110000000000000000000000000030000000000214039E0000000000000000
FC-51FC061614090F010B
FD-B6FD01B7
FE-68FE03B183910001000000000006674A02084D6172202039203230313120
FF-010000FF1003-010303FF1003-command not known

As explanation:
This week, I have not so much time to support, maybe I have a better idea next week, how to scan your registers.
I think at the moment, you can live quite well with the actual status.



Hi Belu
I just uploaded v0125, tomorrow you can update.
some of your new parameters have been implemented: use the attribute firmware.
changelog
Zitat
This module is starting to support (read-only experimental mode) older firmware 2.06; the following attribute adapts decoding and blocks any write back to the heatpump 
      attr Mythz firmware 2.06
This module is starting to support newer firmware 5.39; the following attribute adapts decoding
      attr Mythz firmware 5.39
If no attribute firmware is set, it is assumed your firmware is compatible with 4.39 (standard mode for everyone

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 12 Januar 2015, 00:28:47
@ Immi,

i tested the 0.125, works not with my firmware 5.19, the firmware is the same 5.39 only the heatpump is the diffrent.
can u add the line 5.19 or 5.39 for newer firmware?

big thx
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 12 Januar 2015, 01:07:30
Zitat von: belu am 12 Januar 2015, 00:28:47
i tested the 0.125, works not with my firmware 5.19, the firmware is the same 5.39 only the heatpump is the diffrent.
can u add the line 5.19 or 5.39 for newer firmware?
please be more precise, I do not understand.
What is not working?
have you set the attribute firmware to 5.39 in your config file < attr Mythz firmware 5.39 >?
what do you get if you type < get Mythz sFlowRate >?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 12 Januar 2015, 09:10:24
willy and others: the LWZ/THZ is full of surprises. I just noticed that when the HC heating is on, the cooling rate for DWH doubles. No warm water was taken at that time. Can somebody check this behavior on their heap pump too? It is bizarre!  :-[

(http://img5.fotos-hochladen.net/thumbnail/screenshot201qyrxw3e708_thumb.jpg) (http://www.fotos-hochladen.net/view/screenshot201qyrxw3e708.png)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 Januar 2015, 10:57:34
Zitat von: houseowner123 am 12 Januar 2015, 09:10:24
willy and others: the LWZ/THZ is full of surprises. I just noticed that when the HC heating is on, the cooling rate for DWH doubles. No warm water was taken at that time. Can somebody check this behavior on their heap pump too? It is bizarre!  :-[
I can't confirm, see screen dump of today. Sometimes I feel in similar way, but I couldn't confirm it so clearly as it is visible in your diagram. What I can confirm is, that the frquency of heating up DHW is less in winter time than in summer time.
You could show this diagram in the HaustechnikDialog forum in the hope that the user Lupo gives you an answer. My idea is that possibly the "Rückschlagklappe" stays open unexpectedly. Do you use specially prepared (decalcified) water in your heating circles? Otherwise the Rückschlagklappe scenario is most probably an issue. SE increased the requirements in every new release of the installation manuals. Meanwhile they request a maximum of 3°dH (Härtegrad).

PS:
Why don't you just add your pictures to the text (option is accessible inside "Erweiterte Optionen" directly under the editor window). There's no need to use a separate tool like www.fotos-hochladen.net (http://www.fotos-hochladen.net)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 12 Januar 2015, 13:27:45
Hallo zusammen, ich kann leider momentan nicht viel zu neuen Funktionen beitragen, da ich eine Woche im Urlaub bin.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 12 Januar 2015, 13:59:42
@Houseowner

Die Anlagen sollten ja ungefähr baugleich sein. Die Abwärme des Verdichterst wird ja in den Vorlauf gegeben. Der Vorlauf wird ja über das 2 Wege Ventil in der Multifunktionsgruppe geschaltet. Entweder Warmwasser oder Heizbetrieb.
Wenn das nicht sauber schließt hast du halt so einen Effekt. Der Rücklauf ist bei beiden verbunden mit dem gesamten Rücklauf ohne irgendwas. 
Wenn er in den Heizbetrieb geht und nur zu 95 % umschaltet hast genau diesen Effekt. Der Widerstand gegen die Heizkreisverteiler ist hoch aber durch den Wärmetaucher ist er eher gering. Die 5 % reichen damit kühleres Vorlauf Wasser für den Heibetrieb 30 Grad das Wasser abkühlen.
Hast ja sicher keine Garantie mehr. Würde es ausbauen und entkalken. Ggf neuen O Ringe drauf und wieder einbauen und es müsste wieder klappen.
Anders herum also das er beim Warmwasserbetrieb in den Vorlauf der Heizung pumpt weil er nicht sauber schließt halte ich eher für ausgeschlossen. Der geringe Widerstand der Wärmetauchers des für WW Bereitung und der Widerstand der Leckage sollten reichen das es nicht passiert.
Anders herum schon. Aber du solltest nie kälteres Wasser als die Temperatur im Vorlauf bekommen.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 12 Januar 2015, 14:57:08
@Immi ,

I just talked to Stiebel Eltron because of the wrong counting of energy. Then got him to say everything what I found out . He admits that it may be that the energy is counted wrong . The energy is the show there will be calculated. Dependencies pHD pND outside temperature. This means there is no real counter or transducer inside. Let's see if there might be coming to the parameter list when you successfully find their mistakes.

And because of the 5.19 / 5:39 was a misunderstanding , I thought you read the firmware . Then the mygets be automatically read correctly.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 12 Januar 2015, 18:44:48
@belu:
Ich kann nicht ganz folgen. Heißt das, Stiebel Eltron hält eine Messung mit 40% Fehler für normal, und Du hast Dich damit zufrieden gegeben? Da wird auch fhem nichts reparieren können. fhem kann ja auch nur das auslesen, was die Anlage gespeichert hat. Und wenn das falsch ist ...

Da Du offenbar der Einzige mit diesem Fehler bist wird es auch nicht sinnvoll sein, dass Mythz die ausgelesenen Werte irgendwie korrigiert. Du kannst das natürlich mit userReadings machen, ähnlich wie bei der Innentemperatur; aber der richtige Weg wäre, das eigentliche Messproblem in der Anlage zu lösen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 12 Januar 2015, 21:29:05
Zitat von: houseowner123 am 11 Januar 2015, 00:22:10
@AndreK: Willkommen im Forum. Hast Du Wartung immer selber gemacht oder eine Vertrag mit Stiebel. Ist ja gut zu wissen, daß es in 11 Jahren keine grossen Probleme gegeben hat. Ist die 303er Serie nicht sogar 2003 erst auf den Markt gekommen? Den Abflussschlauch vernachlässige ich auch immer, der setzt sich ganz schön zu. Man kommt aber auch so schlecht ran. Wer ich in die jährliche Wartung mit aufnehmen. Befreist Du die Lüfter vom Staub mit einem Pinsel?

Die ersten 3 Jahre hatten wir einen Techniker vom Hersteller zur Wartung beauftragt, dannach haben wir das selbst gemacht. Zum Reinigen der Lüfter und das Wärmetauschers benutzen wir Staubsauger mit Bürstenaufsatz. Es kann gut sein, dass die 303er 2003 neu auf dem Markt war. Wir waren damals erst der 2. Kunde, bei denen unsere Baufirma dieses Modell eingebaut hat.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 12 Januar 2015, 22:30:57
Zitat von: willybauss am 12 Januar 2015, 18:44:48
@belu:
Ich kann nicht ganz folgen. Heißt das, Stiebel Eltron hält eine Messung mit 40% Fehler für normal, und Du hast Dich damit zufrieden gegeben? Da wird auch fhem nichts reparieren können. fhem kann ja auch nur das auslesen, was die Anlage gespeichert hat. Und wenn das falsch ist ...

Da Du offenbar der Einzige mit diesem Fehler bist wird es auch nicht sinnvoll sein, dass Mythz die ausgelesenen Werte irgendwie korrigiert. Du kannst das natürlich mit userReadings machen, ähnlich wie bei der Innentemperatur; aber der richtige Weg wäre, das eigentliche Messproblem in der Anlage zu lösen.

Ich hab halt mit Stiebel Eltron telefoniert, die Infos ausgetauscht die ich habe, das meine Summe E Energie nicht stimmt. Das der COP deshalb immer schlecht ist. Das es nicht übereinstimmt mit dem geeichten Elektronischen Haushalts Zähler ( EHZ )
Er wollte dann noch wissen wie ich das denn nachvollziehen kann. Habe ihm dann erklärt jeden Tag 24 Uhr E Summe verglichen mit EHZ und THZ.

Hab es ihm dann geschildert das es immer typisch um den Faktor 1,4 höher ist.

War dann aber halt nett und räumt dann evt einen Fehler ein. Sie werden es prüfen. Habe noch paar Sachen mehr gesagt aber die gehören nicht ins Forum.

Wir helfen Stiebel Eltron ja ihre Geräte zu verbessern.

Was ich bisher genau raus finden konnte ist:

Das Energie Zählen findet nur in der Software statt. Verdichter Laufzeiten und Tabellen die hinterlegt sind. Heißt also die haben einen Verdichter Vermessen und die typische Stromaufnahme und die dann einfach hinterlegt.
Einluss auf die Stromaufnahme hat Außentemperatur, Hochdruck, Niederdruck, Vor und Rücklauf Temperatur und natürlich die Drezahl des Verdichters.

Die abgegebene Wärmeleistung wie aber Physisch berechnet anhand der Sensor Durchfluss Vor und Rücklauf x  Konstanten x Zeit. Also genau so wie Peter und ich das gerechnet haben...

Sie werden das prüfen und ich bekomme einen Rückruf, sie werden natürlich die Geräte updaten wenn es so sein sollte.
Wenn dem so ist versuche ich mal auf die Mithilfe der Community zu pochen und eine Hand wäscht die andere. Vielleicht kommt man so ja an ein paar Parameter.

Hoffen wir es... Ich halte euch auf dem laufenden


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Januar 2015, 08:22:27
ok, das klingt schon besser. Ich würde da hart bleiben; ist ja nachweislich ein Fehler. Aber mit den FHEM-Infos würde ich mich nicht aus dem Fenster lehnen, sonst sagen die womöglich, Du hättest die Anlage kaputt gebastelt.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 13 Januar 2015, 09:27:19
Zitat von: belu am 12 Januar 2015, 22:30:57
Das Energie Zählen findet nur in der Software statt. Verdichter Laufzeiten und Tabellen die hinterlegt sind. Heißt also die haben einen Verdichter Vermessen und die typische Stromaufnahme und die dann einfach hinterlegt.
Einluss auf die Stromaufnahme hat Außentemperatur, Hochdruck, Niederdruck, Vor und Rücklauf Temperatur und natürlich die Drezahl des Verdichters.
Very strange decision from the hardware designer. An electrical power meter is cheap and easy to integrate. Such a simulation is quite complicated, needs lots of time to be developed, and works badly.
Are you sure that you understood correctly

Zitat
Die abgegebene Wärmeleistung wie aber Physisch berechnet anhand der Sensor Durchfluss Vor und Rücklauf x  Konstanten x Zeit. Also genau so wie Peter und ich das gerechnet haben...
This makes sense. I would have also implemented it the same way.

Zitat
Vielleicht kommt man so ja an ein paar Parameter.
It would be great.

Zitat von: willybauss am 13 Januar 2015, 08:22:27
Aber mit den FHEM-Infos würde ich mich nicht aus dem Fenster lehnen, sonst sagen die womöglich, Du hättest die Anlage kaputt gebastelt.
5 years ago, I would have agreed 100% with Willy.
Now I start to think that companies start to care about social media because they know that lots of people read www.haustechnikdialog.de and forum.fhem.de
Such a reaction would be  very very bad for their reputation. 
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: houseowner123 am 13 Januar 2015, 19:17:27
Danke an Willy und belu für die Erklärungen mit dem Rückschlagventil. Macht totalen Sinn. Ein Grund, warum das Rückschlagventil nicht richtig schliesst, könnten die Ablagerungen durch hartes Berliner Wasser sein (14-17°dH) oder, daß die Rückschlagklappe ein wenig ausgenuddelt ist. Der Grund dafür könnte der evuRelease durch den Energieversorger sein. Wird die WW Aufbereitung durch das evu unterbrochen, kühlt sich das WW rapide ab. Der Grund dafür war mir nie klar. Wird kaltes Wasser einfach nachgefüllt? Oder könnte das auch mit der Rückschlagventil zu tun haben? (siehe Bild). Hab ein wenig Angst das Rückschlagventil (es gibt ja 2) rauszunehmen. Kommt einem da nicht das ganze Wasser entgegen und muss nicht nach Öffnung neu entlüftet werden etc? Ich werde das mal im Haustechnik-Dialog Forum posten. Aber wenn man so dort liest, haben ja andere ganz andere Probleme mit dem Rückschlgventil und müssen teilweise Brachialgewalt bemühen um diese manuell zu verschliessen.

back to FHEM: I also noticed that the ration PQc/Pel can't be right. If I devide PQc by 1,4 I am in about the right range. Pel might be a little lower than the meter says but it is not that much off.

Another thing I saw is that sElectrDHWDay and sElectrHCDay are way way too low. In the summer when immi uncovered the parameter, the value for sElectrDHWDay seem to reflect the real meter readings per day. But through the updates soemthing got lost. For instance in FHEM (+taking E Steuerung + E Lüftung into account) the resulting meter reading should be 2,3 kWh. In reality it is 7,7 kWh. Any idea where this discrepancy is coming from?

@willy: Danke für den Tip mit den erweiterten Optionen und den Anhängen! :)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Januar 2015, 22:32:27
@houseowner123
Bist Du sicher, dass da normales Wasser eingefüllt wurde, ohne Enthärtung? Wenn ich es richtig in Erinnerung habe hast Du doch eine ganz neue Anlage - 304? Die kann ja höchstens 3 Jahre alt sein - und schon Kalkpobleme? Ich würde mal eine Wasserprobe entnehmen (habe ich bereits beim befüllen im Rohbau gemacht) und den Härtegrad messen. Messflüssigkeit gibts im Aquarienzubehör für ca. 7 - 8€. Meine Frau sagt mir grade, dass es bei den Aquarien verschiedene Messmittel für Carbonathärte und Gesamthärte gibt. Sie sagt, Gesamthärte wäre in diesem Fall das richtige. Wenn da tatsächlich normales Wasser eingefüllt wurde, dann ist das ein Verstoß Deines Heizungsbauers gegen die Herstellervorschrift, die max. 3°dH vorschreibt. Dann kannst Du - falls noch keine 5 Jahre seit dem Bau rum sind - Nachbesserung incl. Reparatur der Rückschlagklappen und kompletter Spülung der Heizkreise verlangen. Ohne diese Maßnahme sind Langzeitprobleme vorprogrammiert.

Der evuRelease ist eigentlich bei der Konstruktion berücksichtigt; glaube nicht, dass der was dafür kann. Aber das Bild sieht sehr merkwürdig aus. Zum Ausbau der Rückschlagklappen kann ich Dir nichts sagen, aber anschließend entlüften wird sich vermutlich nicht vermeiden lassen.

Ich glaube, wir müssen die Genauigkeit der Verbrauchswerte Modell-abhängig betrachten. Bei mir (THZ303SOL, Firmware 4.19) stimmen die Zahlen von Stromzähler und THZ-interner Messung sehr gut überein. Die Ausreißer in der blauen Kurve sind Rundungsfehler, weil der Zähler in der THZ nur auf 0,1MWh genau anzeigt (nur 1 Nachkommastelle).

Postet einfach mal eure Ergebnisse incl. Modell und Firmwareversion. Ich fange mal eine Tabelle an, bitte erweitern. Evtl. schafft es ja sogar einer, das mit der Tabellenfunktion des Forums hübsch zu formatieren...

Besitzer   Modell    Firmware Abweichung-Stromzähler_el.-THZ-Zähler_el.
willybauss THZ303SOL 4.19     0%
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 13 Januar 2015, 22:49:14
@houseowner123
Stelle bitte den Link zu Deinem Beitrag im Haustechnikforum hier rein. Das Thema interessiert mich.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 14 Januar 2015, 17:38:28
Zitat von: immi am 11 Januar 2015, 22:55:20

This week, I have not so much time to support, maybe I have a better idea next week, how to scan your registers.
I think at the moment, you can live quite well with the actual status.


Hi immi,

your debug routine seems to be too fast for my communication. I inserted an additional read in line #1230 like in the THZ_Get_Comunication
   if ($msg eq "10") {
         ($err, $msg) = THZ_ReadAnswer($hash); # read 02
   }

Now I got the at least the correct THZ answers in the output file.

Here is the full logfile data.txt
01-4A015A8AC85A8AC8003C003C003C003C00
02-54020101052525
03-F3030096000A009600641441
04-E1045A0028005A
05-A50500040028000006000000001E006402260032015E0032
06-D806281E1414140000000200640302EE00AA0014000100280F
07-2F07145A00281E0C00640300
08-54080100325A0258000A0258
09-AE09017B017B872535CB0000000000
0A-A60A010064000000BE0078
0B-3A0B070801907F0103E803200000
0C-220C083402587F00
0D-660D073503207F0107D003207F00
0E-910E000000640000001E
0F-100F0000000000
10-D0100000FA019000020032
11-010012111003-010315111003-command not known
12-010013121003-010316121003-command not known
13-010014131003-010317131003-command not known
14-010015141003-010318141003-command not known
15-010016151003-010319151003-command not known
16-A316006101BB010500000A003C011D0500
17-2B1700C800BE009601C201900064020100015E01DA02
18-010019181003-01031C181003-command not known
19-01001A191003-01031D191003-command not known
1A-01001B1A1003-01031E1A1003-command not known
1B-01001C1B1003-01031F1B1003-command not known
1C-01001D1C1003-0103201C1003-command not known
1D-01001E1D1003-0103211D1003-command not known
1E-01001F1E1003-0103221E1003-command not known
1F-0100201F1003-0103231F1003-command not known
20-010021201003-010324201003-command not known
21-010022211003-010325211003-command not known
22-010023221003-010326221003-command not known
23-010024231003-010327231003-command not known
24-010025241003-010328241003-command not known
25-010026251003-010329251003-command not known
26-010027261003-01032A261003-command not known
27-010028271003-01032B271003-command not known
28-010029281003-01032C281003-command not known
29-01002A291003-01032D291003-command not known
2A-01002B182A1003-01032E2A1003-command not known
2B-01002C2B181003-01032F2B1003-command not known
2C-01002D2C1003-0103302C1003-command not known
2D-01002E2D1003-0103312D1003-command not known
2E-01002F2E1003-0103322E1003-command not known
2F-0100302F1003-0103332F1003-command not known
30-010031301003-010334301003-command not known
31-010032311003-010335311003-command not known
32-010033321003-010336321003-command not known
33-010034331003-010337331003-command not known
34-010035341003-010338341003-command not known
35-010036351003-010339351003-command not known
36-010037361003-01033A361003-command not known
37-010038371003-01033B371003-command not known
38-010039381003-01033C381003-command not known
39-01003A391003-01033D391003-command not known
3A-01003B3A1003-01033E3A1003-command not known
3B-01003C3B1003-01033F3B1003-command not known
3C-01003D3C1003-0103403C1003-command not known
3D-01003E3D1003-0103413D1003-command not known
3E-01003F3E1003-0103423E1003-command not known
3F-0100403F1003-0102413E1003-CRC error in request
40-010041401003-010344401003-command not known
41-010042411003-010345411003-command not known
42-010043421003-010346421003-command not known
43-010044431003-010347431003-command not known
44-010045441003-010348441003-command not known
45-010046451003-010349451003-command not known
46-010047461003-01034A461003-command not known
47-010048471003-01034B471003-command not known
48-010049481003-01034C481003-command not known
49-01004A491003-01034D491003-command not known
4A-01004B4A1003-01034E4A1003-command not known
4B-01004C4B1003-01034F4B1003-command not known
4C-01004D4C1003-0103504C1003-command not known
4D-01004E4D1003-0103514D1003-command not known
4E-01004F4E1003-0103524E1003-command not known
4F-0100504F1003-0103534F1003-command not known
50-010051501003-010354501003-command not known
51-010052511003-010355511003-command not known
52-010053521003-010356521003-command not known
53-010054531003-010357531003-command not known
54-010055541003-010358541003-command not known
55-010056551003-010359551003-command not known
56-010057561003-01035A561003-command not known
57-010058571003-01035B571003-command not known
58-010059581003-01035C581003-command not known
59-01005A591003-01035D591003-command not known
5A-01005B5A1003-01035E5A1003-command not known
5B-01005C5B1003-01035F5B1003-command not known
5C-01005D5C1003-0103605C1003-command not known
5D-01005E5D1003-0103615D1003-command not known
5E-01005F5E1003-0103625E1003-command not known
5F-0100605F1003-0103635F1003-command not known
60-010061601003-010364601003-command not known
61-010062611003-010365611003-command not known
62-010063621003-010366621003-command not known
63-010064631003-010367631003-command not known
64-010065641003-010368641003-command not known
65-010066651003-010369651003-command not known
66-010067661003-01036A661003-command not known
67-010068671003-01036B671003-command not known
68-010069681003-01036C681003-command not known
69-01006A691003-01036D691003-command not known
6A-01006B6A1003-01036E6A1003-command not known
6B-01006C6B1003-01036F6B1003-command not known
6C-01006D6C1003-0103706C1003-command not known
6D-01006E6D1003-0103716D1003-command not known
6E-01006F6E1003-0103726E1003-command not known
6F-0100706F1003-0103736F1003-command not known
70-010071701003-010374701003-command not known
71-010072711003-010375711003-command not known
72-010073721003-010376721003-command not known
73-010074731003-010377731003-command not known
74-010075741003-010378741003-command not known
75-010076751003-010379751003-command not known
76-010077761003-01037A761003-command not known
77-010078771003-01037B771003-command not known
78-010079781003-01037C781003-command not known
79-01007A791003-01037D791003-command not known
7A-01007B7A1003-01037E7A1003-command not known
7B-01007C7B1003-01037F7B1003-command not known
7C-01007D7C1003-0103807C1003-command not known
7D-01007E7D1003-0103817D1003-command not known
7E-01007F7E1003-0103827E1003-command not known
7F-0100807F1003-0103837F1003-command not known
80-010081801003-010384801003-command not known
81-010082811003-010385811003-command not known
82-010083821003-010386821003-command not known
83-010084831003-010387831003-command not known
84-010085841003-010388841003-command not known
85-010086851003-010389851003-command not known
86-010087861003-01038A861003-command not known
87-010088871003-01038B871003-command not known
88-010089881003-01038C881003-command not known
89-01008A891003-01038D891003-command not known
8A-01008B8A1003-01038E8A1003-command not known
8B-01008C8B1003-01038F8B1003-command not known
8C-01008D8C1003-0103908C1003-command not known
8D-01008E8D1003-0103918D1003-command not known
8E-01008F8E1003-0103928E1003-command not known
8F-0100908F1003-0103938F1003-command not known
90-010091901003-010394901003-command not known
91-010092911003-010395911003-command not known
92-010093921003-010396921003-command not known
93-010094931003-010397931003-command not known
94-010095941003-010398941003-command not known
95-010096951003-010399951003-command not known
96-010097961003-01039A961003-command not known
97-010098971003-01039B971003-command not known
98-010099981003-01039C981003-command not known
99-01009A991003-01039D991003-command not known
9A-01009B9A1003-01029C991003-CRC error in request
9B-01009C9B1003-01039F9B1003-command not known
9C-01009D9C1003-0103A09C1003-command not known
9D-01009E9D1003-0103A19D1003-command not known
9E-01009F9E1003-0103A29E1003-command not known
9F-0100A09F1003-0103A39F1003-command not known
A0-0100A1A01003-0103A4A01003-command not known
A1-0100A2A11003-0103A5A11003-command not known
A2-0100A3A21003-0103A6A21003-command not known
A3-0100A4A31003-0103A7A31003-command not known
A4-0100A5A41003-0103A8A41003-command not known
A5-0100A6A51003-0103A9A51003-command not known
A6-0100A7A61003-0103AAA61003-command not known
A7-0100A8A71003-0103ABA71003-command not known
A8-0100A9A81003-0103ACA81003-command not known
A9-0100AAA91003-0103ADA91003-command not known
AA-0100ABAA1003-0103AEAA1003-command not known
AB-0100ACAB1003-0103AFAB1003-command not known
AC-0100ADAC1003-0103B0AC1003-command not known
AD-0100AEAD1003-0103B1AD1003-command not known
AE-0100AFAE1003-0103B2AE1003-command not known
AF-0100B0AF1003-0103B3AF1003-command not known
B0-0100B1B01003-0103B4B01003-command not known
B1-0100B2B11003-0103B5B11003-command not known
B2-0100B3B21003-0103B6B21003-command not known
B3-0100B4B31003-0103B7B31003-command not known
B4-0100B5B41003-0103B8B41003-command not known
B5-0100B6B51003-0103B9B51003-command not known
B6-0100B7B61003-0103BAB61003-command not known
B7-0100B8B71003-0103BBB71003-command not known
B8-0100B9B81003-0103BCB81003-command not known
B9-0100BAB91003-0103BDB91003-command not known
BA-0100BBBA1003-0103BEBA1003-command not known
BB-0100BCBB1003-0103BFBB1003-command not known
BC-0100BDBC1003-0103C0BC1003-command not known
BC-0100BDBC1003-0103C0BC1003-command not known
BD-0100BEBD1003-0103C1BD1003-command not known
BE-0100BFBE1003-0103C2BE1003-command not known
BF-0100C0BF1003-0103C3BF1003-command not known
C0-0100C1C01003-0103C4C01003-command not known
C1-0100C2C11003-0103C5C11003-command not known
C2-0100C3C21003-0103C6C21003-command not known
C3-0100C4C31003-0103C7C31003-command not known
C4-0100C5C41003-0103C8C41003-command not known
C5-0100C6C51003-0103C9C51003-command not known
C6-0100C7C61003-0103CAC61003-command not known
C7-0100C8C71003-0103CBC71003-command not known
C8-52C8202020202020202020202020202020202020202020202020202020202020202020202020202020201B0C140E0E32000000000000

CA-0100CBCA1003-0103CECA1003-command not known
CB-0100CCCB1003-0103CFCB1003-command not known
CC-0100CDCC1003-0103D0CC1003-command not known
CD-0100CECD1003-0103D1CD1003-command not known
CE-0100CFCE1003-0103D2CE1003-command not known
CF-0100D0CF1003-0103D3CF1003-command not known
D0-0100D1D01003-0103D4D01003-command not known
D1-0100D2D11003-0103D5D11003-command not known
D2-0100D3D21003-0103D6D21003-command not known
D3-0100D4D31003-0103D7D31003-command not known
D4-0100D5D41003-0103D8D41003-command not known
D5-0100D6D51003-0103D9D51003-command not known
D6-0100D7D61003-0103DAD61003-command not known
D7-0100D8D71003-0103DBD71003-command not known
D8-0100D9D81003-0103DCD81003-command not known
D9-0100DAD91003-0103DDD91003-command not known
DA-0100DBDA1003-0103DEDA1003-command not known
DB-0100DCDB1003-0103DFDB1003-command not known
DC-0100DDDC1003-0103E0DC1003-command not known
DD-0100DEDD1003-0103E1DD1003-command not known
DE-0100DFDE1003-0103E2DE1003-command not known
DF-0100E0DF1003-0103E3DF1003-command not known
E0-0100E1E01003-0103E4E01003-command not known
E1-0100E2E11003-0103E5E11003-command not known
E2-0100E3E21003-0103E6E21003-command not known
E3-0100E4E31003-0103E7E31003-command not known
E4-0100E5E41003-0103E8E41003-command not known
E5-0100E6E51003-0103E9E51003-command not known
E6-0100E7E61003-0103EAE61003-command not known
E7-0100E8E71003-0103EBE71003-command not known
E8-7CE8000415F115754487445300340034005A005A0025002504670467038E037458010000
E9-FFE90E8809600E7E094F03DB0009AA2955011D0500
EA-0100EBEA1003-0103EEEA1003-command not known
EB-0100ECEB1003-0103EFEB1003-command not known
EC-2AEC01000066006B01060101016001B30000000000BE0104107B023232330004E906BE083A0831090D098C17CD17C3078C0836
ED-0100EEED1003-0103F1ED1003-command not known
EE-A8EE01050102010200005954000000000000000000
EF-BCEF050001000001E0046507800A050D200FA512C0154518601AE51E00208523A026252940FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF053D02
F0-1BF0050001FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF053D02
F1-F8F1050001000000F00438069009D80C300F7811D0151817701AB81D10205822B025F82850FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF053D01
F2-11F20202010001000000100105010100000000
F3-0CF301B3006B01C20000011D0000000100010214
F4-CEF4006BFF3A0101FFF10105010D010100010101011D00640200000000000000BE0000000000000002000000E6
F5-54F5006B0101000000F90101FC180101011D02000000000002000000BE
F6-08F600000000FF1000FFFF010000000300000000
F7-0100F8F71003-0103FBF71003-command not known
F8-0100F9F81003-0103FCF81003-command not known
F9-0100FAF91003-0103FDF91003-command not known
FA-0100FBFA1003-0103FEFA1003-command not known
FB-CEFB0066006B01050101015E01B20000000000C0010401052525000134350000006800000000
FC-8AFC0000142D300F00010C
FD-0100FEFD1003-010301FD1003-command not known
FE-0100FFFE1003-010302FE1003-command not known
FF-010000FF1003-010303FF1003-command not known


I compared the answers from FHEM with the answers which I've recorded from the the serial communication during a session of the configuration program. The following THX register I have found:
register type usage
01 parameter ventilation
03 parameter defrost evaporator
04 parameter defrost A/A exchanger
05 parameter heat1
06 parameter heat2
07 parameter DHW
08 parameter solar heat
09 status sHistory
0A parameter circulation pump
0B parameter heating programs
0C parameter DHW program
0D parameter fan programs
0E parameter restart time
0F parameter absence program
10 parameter dry heating
16 status sSolar
17 parameter set values
C9 parameter modem communication
E9 status sDefrost
EE status sProgram
F2 status sControl
F3 status sDHW
F4 status sHC1
F5 status sHC2
F6 status sSystem
FB status sGlobal
FC parameter sTime


In the next time I can provide you parsing rules for these registers I have found, but it takes a while. I'm not sure if this makes sense for every parameter register. I don't think that for example "dry heat" is not an real use case for FHEM. It would be also possible to write back the register of type parameter to the THZ. But as you already said, this is not so important at the moment.

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 14 Januar 2015, 19:04:45
Also bisher hat sich noch keiner wieder von Stiebel Eltron gemeldet.

@Willy, ich habe nun meinen hydraulischen Abgleich erfolgreich abgeschlossen, habe nun so + - 0,2 Grad differenz. War eigentlich garnicht so schwierieg, ging mehr um die kleinen Kreise, die voll auf zu machen und die andren so runter zu pegeln das es gleich ist.

Ich bin mal gespannt ob die Pumpe nun wieder so oft anfährt.

LG
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 14 Januar 2015, 19:21:40
Zitat von: belu am 14 Januar 2015, 19:04:45
Ich bin mal gespannt ob die Pumpe nun wieder so oft anfährt.
Spannend wird es immer dann, wenn viele/alle Thermostatventile gleichzeitig zu sind. Dann wird die Anlage die Wärme nicht los und schaltet schnell wieder ab. Schau'n mer mal ...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 14 Januar 2015, 20:10:39
Zitat von: andre.k am 14 Januar 2015, 17:38:28
Hi immi,

your debug routine seems to be too fast for my communication. I inserted an additional read in line #1230 like in the THZ_Get_Comunication
   if ($msg eq "10") {
         ($err, $msg) = THZ_ReadAnswer($hash); # read 02
   }


In the next time I can provide you parsing rules for these registers I have found, but it takes a while. I'm not sure if this makes sense for every parameter register. I don't think that for example "dry heat" is not an real use case for FHEM. It would be also possible to write back the register of type parameter to the THZ. But as you already said, this is not so important at the moment.

Andre

Hi Andre
you seam to read my mind  :)
In v0126 which I uploaded 2 days ago, there was the same solution.
Happy that you got there alone!! Happy to merge your new code.

FYI: You can get most of your reverse eng. with following configuration.
heatpump -- ser2net -- proxy.pl --- net2comport --- LWZ303-LWA403.exe
proxy.pl can be used to store/redirect the comminication of LWZ303-LWA403.exe
By uncommenting the "#if (length(...." you can use proxy.pl  to inject commands into LWZ303-LWA403.exe, in order to test what the single byte do
Pay attention to encoding rules when injecting:  crc and all rules like 10-->1010 and 2B-->2B18
In decoding: 2B18 --> 2B and 1010 -->10


[~] # cat proxy.pl
#!/usr/bin/perl
#

use warnings;
use strict;

use IO::Socket::INET;
use IO::Select;

my @allowed_ips = ('all', '10.10.10.5');
my $ioset = IO::Select->new;
my %socket_map;

my $debug = 1;

sub new_conn {
    my ($host, $port) = @_;
    return IO::Socket::INET->new(
        PeerAddr => $host,
        PeerPort => $port
    ) || die "Unable to connect to $host:$port: $!";
}

sub new_server {
    my ($host, $port) = @_;
    my $server = IO::Socket::INET->new(
        LocalAddr => $host,
        LocalPort => $port,
        ReuseAddr => 1,
        Listen => 100
    ) || die "Unable to listen on $host:$port: $!";
}

sub new_connection {
    my $server = shift;
    my $remote_host = shift;
    my $remote_port = shift;

    my $client = $server->accept;
    my $client_ip = client_ip($client);

    unless (client_allowed($client)) {
        print "Connection from $client_ip denied.\n" if $debug;
        $client->close;
        return;
    }
    print "Connection from $client_ip accepted.\n" if $debug;

    my $remote = new_conn($remote_host, $remote_port);
    $ioset->add($client);
    $ioset->add($remote);

    $socket_map{$client} = $remote;
    $socket_map{$remote} = $client;
}

sub close_connection {
    my $client = shift;
    my $client_ip = client_ip($client);
    my $remote = $socket_map{$client};
   
    $ioset->remove($client);
    $ioset->remove($remote);

    delete $socket_map{$client};
    delete $socket_map{$remote};

    $client->close;
    $remote->close;

    print "Connection from $client_ip closed.\n" if $debug;
}

sub client_ip {
    my $client = shift;
    return inet_ntoa($client->sockaddr);
}

sub client_allowed {
    my $client = shift;
    my $client_ip = client_ip($client);
    return grep { $_ eq $client_ip || $_ eq 'all' } @allowed_ips;
}

die "Usage: $0 <local port> <remote_host:remote_port>" unless @ARGV == 2;

my $local_port = shift;
my ($remote_host, $remote_port) = split ':', shift();


print "Starting a server on 0.0.0.0:$local_port\n";
my $server = new_server('0.0.0.0', $local_port);
$ioset->add($server);

while (1) {
    for my $socket ($ioset->can_read) {
        if ($socket == $server) {
            new_connection($server, $remote_host, $remote_port);
        }
        else {
            next unless exists $socket_map{$socket};
            my $remote = $socket_map{$socket};
            my $buffer;
            my $read = $socket->sysread($buffer, 4096);
            my $data =  uc(unpack('H*', $buffer));

##following line for injecting
#if (length($data) > 15 ) { $data="0100C5090381038127AF0DD000000000001003" } #

            open (MYFILE, '>>data.txt');
    print MYFILE ($data . "\n");
    close (MYFILE);
            $buffer=  pack('H*', $data);
            if ($read) {
                $remote->syswrite($buffer);
            }
            else {
                close_connection($socket);
            }
        }
    }
}




immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 15 Januar 2015, 17:37:19
Hi immi,

I found a difference in the parsing rule for FCtime. Here is an example of the response from THZ:
FC0000142D300F00010C
All values are shifted to right. In my FHEM the following parsing works perfect.

"FCtime" => [["Weekday: ", 7, 1,  "weekday", 1], [" Hour: ", 8, 2, "hex", 1],
      [" Min: ", 10, 2,  "hex", 1], [" Sec: ", 12, 2, "hex", 1],
      [" Date: ", 14, 2, "year", 1], ["/", 18, 2, "hex", 1],
      ["/", 20, 2, "hex", 1]


Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 15 Januar 2015, 22:56:16
Hallo,

wenn jemand zufällig die Softewar hat für die LWZ / THZ 304 / 404 würde mir das sehr helfen, bitte um Kontaktaufnahme.


Vielen Herzlichen Dank

LG

Belu
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 15 Januar 2015, 23:32:38
Hi Andre
v0.127 added with your hint.
tomorrow you can update

Hi Belu
sorry I do not have the service software for your firmware.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Januar 2015, 09:50:17
Zitat von: belu am 15 Januar 2015, 22:56:16
wenn jemand zufällig die Softewar hat für die LWZ / THZ 304 / 404 würde mir das sehr helfen ...
Angeblich soll das die Software (http://www.kromschroeder.de/Downloadbereich.4549.0.html) sein. ComSoft im Menü Downloads. Kannst es ja mal versuchen. Ich bin bislang noch nicht dazu gekommen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: firebal301 am 16 Januar 2015, 19:13:30
Zitat von: houseowner123 am 13 Januar 2015, 19:17:27
Danke an Willy und belu für die Erklärungen mit dem Rückschlagventil. Macht totalen Sinn. Ein Grund, warum das Rückschlagventil nicht richtig schliesst, könnten die Ablagerungen durch hartes Berliner Wasser sein (14-17°dH) oder, daß die Rückschlagklappe ein wenig ausgenuddelt ist. Der Grund dafür könnte der evuRelease durch den Energieversorger sein. Wird die WW Aufbereitung durch das evu unterbrochen, kühlt sich das WW rapide ab. Der Grund dafür war mir nie klar. Wird kaltes Wasser einfach nachgefüllt? Oder könnte das auch mit der Rückschlagventil zu tun haben? (siehe Bild). Hab ein wenig Angst das Rückschlagventil (es gibt ja 2) rauszunehmen. Kommt einem da nicht das ganze Wasser entgegen und muss nicht nach Öffnung neu entlüftet werden etc? Ich werde das mal im Haustechnik-Dialog Forum posten. Aber wenn man so dort liest, haben ja andere ganz andere Probleme mit dem Rückschlgventil und müssen teilweise Brachialgewalt bemühen um diese manuell zu verschliessen.

Ich hatte letzte Woche einen Techniker bei uns, da die Anlage (LWZ403) in Störung gegangen ist. Der Monteur erkläre mir unter anderem, dass die Rückschlagventile eine kleine Bohrung haben müssen, damit mögliche Luftblasen abgeführt werden und die darunterliegende Pumpe nicht trocken läuft. Durch diese kleine Bohrung findet leider auch immer ein kleiner Wärmeaustausch statt. Jedoch ist diese Wärme ja nicht verloren sondern geht ja dann ins andere System über (Heizung/Wasser). Dies nur mal als kleine Ergänzung...

Gruß
Kai
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: PhyTHZ am 16 Januar 2015, 23:03:56
Hi,

Some weeks ago I installed fhem/THZ on my Zyxel NAS NSA325 (no jokes about the name pls :-). Basically everything works, but the connection to my THZ403sol (4.39) seems to be unstable: There are several "Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?" messages in the log.
I already tried to use different USB/RS232 adapters (PL2303 and FT232) and a shorter cable. The RS232 signal looks fine on the oscilloscope. However, the timeout problems remain.

Frankly speaking I have no clue how to proceed. I attached a typical fhem log file. It would be great if someone could point me the right direction.

Thanks in advance,
Phy

Zu den Meibes Rückschlagkappen: Ich kann Kais Aussage bzw. die des Technikers bestätigen. Ich habe im letzten Jahr eine Klappe getauscht; die haben eine Luftschleuse. Bei WW-Bereitung erwärmt sich der Heizungsvorlauf daher leicht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Januar 2015, 23:16:37
@Phy
Herzlich willkommen im Club  :)

Zu den Verbindungsproblemen wird sich sicher immi bald äußern. Es gab auch auf den letzten 2 - 3 Seiten dieses Threads von ihm dazu Infos, aber ich will ihm da nicht vorgreifen.

Mich würde interessieren, wie Du die Rückschlagklappe ausgebaut hast. Geht das, ohne die Anlage zu entleeren? Und muss sie hinterher entlüftet werden?
Bei mir hat vor ein paar Wochen mal eine Klappe geklemmt. Wenn es ohne großen Aufwand geht würde ich die mal ausbauen und überprüfen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 16 Januar 2015, 23:21:25
Zitat von: PhyTHZ am 16 Januar 2015, 23:03:56
Some weeks ago I installed fhem/THZ ...
Hast Du schon mal ein Update gemacht? Welche Mythz-Version verwendest Du? Das steht in der Liste in den Internals.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Januar 2015, 10:22:31
Hi PhyTHZ
welcome on board; As willy asked, please keep THZ-fhem always to the last version (now v0.127)

Zitat von: PhyTHZ am 16 Januar 2015, 23:03:56
There are several "Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?" messages in the log.
I already tried to use different USB/RS232 adapters (PL2303 and FT232) and a shorter cable. The RS232 signal looks fine on the oscilloscope. However, the timeout problems remain.
Excellent problem description.
To my opinion, you do not have a timeout problem.
Your logfile is full with NAK. If you have an oscilloscope at home, for sure you know what is a NAK in a serial protocoll.
Forget it :)
My feeling is that, in your case, the heatpump  says "I am busy now, try later"
My heatpump (same version as yours) hasn´t done it in the last 10 months.

During the initialization phase, I send lots of commands in very short time.
Do you see the NAK only in the initialization phase or also later (timerange init+10min .. init+10h)?
Do you have a second display installed?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: PhyTHZ am 17 Januar 2015, 15:12:07
Zitat von: willybauss am 16 Januar 2015, 23:16:37
Bei mir hat vor ein paar Wochen mal eine Klappe geklemmt. Wenn es ohne großen Aufwand geht würde ich die mal ausbauen und überprüfen.
Zum Tausch muss der Heizkreis abgelassen werden. Das ging bei mir einfach, weil (leider) eine hydraulische Weiche mit Absperrhähnen verbaut ist. Aufgefüllt habe ich über einen Fillsoft Ionenaustauscher. Entlüften musste ich nur den Kreis mit der hydraulischen Weiche (Entlüften ist in der Anleitung beschrieben). Zum Öffnen der Verschraubung und zum Gegenhalten benötigt man zwei Rohrzangen/Schlüssel. Ich hatte prophylaktisch eine neue Klappe besorgt, von der ich dann aber nur die Dichtung benötigt habe. Ich könnte mir vorstellen, dass die Dichtung nicht so leicht zu bekommen ist: Fiberdichtung, Innen ca. 26 mm, Außen ca. 44.8, Dicke 1,5mm. Wenn die Klappe tatsächlich wegen Verschmutzungen hängt, muss aber wohl ohnehin die gesamte Anlage gespült werden – sonst hast Du das Problem gleich wieder. Wenn die Klappe jetzt wieder geht, wäre mir der Aufwand zu hoch – dank fhem erkennst Du ja schnell wenn die Klappe wieder hängt.


Zu Fhem:
I have currently installed thzversion = "0.126" Playing around with ,,select(undef, undef, undef, 0.1)" had no influence. However, I am no yet so deep into fhem/THZ.pm that I really understand what I am changing. NAK Messages are less frequently after init-phase; approx 1 time per hour (6 min interval for sGlobal). Sporadically I see these three problems in the log:

InterfaceNotRespondig:

2015.01.17 11:11:09 5: THZ_Get: Try to get 'sGlobal'
2015.01.17 11:11:09 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.01.17 11:11:09 5: Mythz sending 02
2015.01.17 11:11:09 5: SW: 02
2015.01.17 11:11:09 5: Mythz start Funktion THZ_ReadAnswer
2015.01.17 11:11:09 5: THZ_ReadAnswer: uc unpack: '10'
2015.01.17 11:11:09 5: Mythz sending 0100FCFB1003
2015.01.17 11:11:09 5: SW: 0100FCFB1003
2015.01.17 11:11:09 5: Mythz start Funktion THZ_ReadAnswer
2015.01.17 11:11:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.17 11:11:09 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'


NAK:

2015.01.17 12:46:09 5: THZ_Get: Try to get 'sGlobal'
2015.01.17 12:46:09 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.01.17 12:46:09 5: Mythz sending 02
2015.01.17 12:46:09 5: SW: 02
2015.01.17 12:46:09 5: Mythz start Funktion THZ_ReadAnswer
2015.01.17 12:46:09 5: THZ_ReadAnswer: uc unpack: '10'
2015.01.17 12:46:09 5: Mythz sending 0100FCFB1003
2015.01.17 12:46:09 5: SW: 0100FCFB1003
2015.01.17 12:46:09 5: Mythz start Funktion THZ_ReadAnswer
2015.01.17 12:46:09 5: THZ_ReadAnswer: uc unpack: '15'
2015.01.17 12:46:09 5: THZ_Get: Error msg2: 'NAK received from device'


and this one after init
2015.01.16 22:41:26 5: THZ_Get: Try to get 'sFirmware-Id'
2015.01.16 22:41:26 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.01.16 22:41:26 5: Mythz sending 02
2015.01.16 22:41:26 5: SW: 02
2015.01.16 22:41:26 5: Mythz start Funktion THZ_ReadAnswer
2015.01.16 22:41:26 5: THZ_ReadAnswer: uc unpack: '10'
2015.01.16 22:41:26 5: Mythz sending 0100FFFE1003
2015.01.16 22:41:26 5: SW: 0100FFFE1003
2015.01.16 22:41:26 5: Mythz start Funktion THZ_ReadAnswer
2015.01.16 22:41:26 5: THZ_ReadAnswer: uc unpack: '1002'
2015.01.16 22:41:26 5: Mythz sending 10
2015.01.16 22:41:26 5: SW: 10
2015.01.16 22:41:26 5: Mythz start Funktion THZ_ReadAnswer
2015.01.16 22:41:26 5: THZ_ReadAnswer: uc unpack: '01005FFE03B18391000100024D8A0006674A02051003'
2015.01.16 22:41:26 5: Mythz sending 10
2015.01.16 22:41:26 5: SW: 10
2015.01.16 22:41:26 5: Parse message: 5FFE03B18391000100024D8A0006674A0205
2015.01.16 22:41:26 5: Message length: 36
2015.01.16 22:41:26 3: THZ_Parsing: offset(36) + length(22) is longer then message : '5FFE03B18391000100024D8A0006674A0205'


Unfortunately there is not so much experience with my NAS and fhem. So I wonder whether it makes sense to install fhem on my windows laptop and give it a try.

Best wishes and thank you all for your help and support,

Phy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 17 Januar 2015, 16:38:40
Hi PhyTHZ
The third problem is because  register FE in your heatpump is 22 characters shorter that it should.
No comunication problem, just registers with different encoding.
my $buf = DevIo_SimpleReadWithTimeout($hash, 0.7);
Indeed your firmware-vs 4.39 is not like mine 4.39.
How old is your box?

InterfaceNotRespondig and NAK are, to my opinion, related.
For InterfaceNotRespondig, your heatpump waits more than 0.7s before responding.
For NAK, your heatpump says I am busy.
Therefore I asked you, if you have a second display for your heatpump in the living room.

Is there someone else with NAK issues?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 17 Januar 2015, 17:43:07
Zitat von: PhyTHZ am 17 Januar 2015, 15:12:07
Wenn die Klappe jetzt wieder geht, wäre mir der Aufwand zu hoch – dank fhem erkennst Du ja schnell wenn die Klappe wieder hängt.
Danke, genau so werde ich es machen.

@immi:
no NAK at all, ver 4.19 incl. 2nd display
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: PhyTHZ am 17 Januar 2015, 17:56:59
Hi immi,

My THZ403sol was manufactured / installed in 2010. Tecalor Service did the start-up. There was no software update since then (double-checked – it is really 4.39). Also, I read that you connect with 115200 baud, while I only get a connection with 57600 baud. It seems that my hardware is older.

ZitatTherefore I asked you, if you have a second display for your heatpump in the living room.

Sorry, overlooked your question. I don't have a second display.

Phy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 17 Januar 2015, 20:26:55
Zitat von: immi am 17 Januar 2015, 16:38:40
Indeed your firmware-vs 4.39 is not like mine 4.39.
This is why it is important to know the actual software ID. As far as I know the displayed software version (at least in the newer models) does not change when the motherboard software is updated but the software ID does.

I also noticed that there are some registers which change their contents depending on previous operations. The register for the software ID (0a 024b) in the THZ404 belongs to that kind. The first read after a previous command returns some data. But subsequent reads always return the software ID.

I also noticed that the d2 reads return data blocks varying every now and then. So I assumed that d2 requires an additional index. It is a one byte index. It seems that the d2 reads provide the entries stored by an internal data logger every 42 minutes (the first bytes contain a time stamp).

Last but not least - I never get NACKs of any type (0x15, 0x0101, 0x0102, 0x0103 or 0x04) for any known messages.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 17 Januar 2015, 21:58:37
Zitat von: PhyTHZ am 17 Januar 2015, 17:56:59
My THZ403sol was manufactured / installed in 2010. Tecalor Service did the start-up. There was no software update since then (double-checked – it is really 4.39). Also, I read that you connect with 115200 baud, while I only get a connection with 57600 baud. It seems that my hardware is older.
My 303SOL was installed in 2010 as well, ver. 4.19 and using 115200 baud. So it seems like in 2010 there was a hardware change as well as a firmware change, but not both the same point in time. But different connection speed does not necessarily mean different HW state as well.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Januar 2015, 01:23:34
Zitat von: godmorgon am 17 Januar 2015, 20:26:55
I also noticed that the d2 reads return data blocks varying every now and then. So I assumed that d2 requires an additional index. It is a one byte index. It seems that the d2 reads provide the entries stored by an internal data logger every 42 minutes (the first bytes contain a time stamp).
I do not see any use of d2, because I log in fhem.
It is important for the service tech. in order to see the last days of operation.
Find an example of D2 in attachment, if you are interested in it.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Januar 2015, 01:26:22
Zitat von: willybauss am 17 Januar 2015, 21:58:37
But different connection speed does not necessarily mean different HW state as well.
Agree completely. It would be so easy with some help from tecalor/SE.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 18 Januar 2015, 10:33:12
Today I could notice the first time how the THZ deals with a frozen heat exchanger. Obviously there's still some flow which prevents the exchanger from being deiced.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 18 Januar 2015, 10:56:13
Zitat von: immi am 18 Januar 2015, 01:23:34
I do not see any use of d2, because I log in fhem.
I do not see any use of it either. Just for completeness' sake.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Januar 2015, 11:25:51
Where do you find the firmware-id (e.g. 7278 from godmorgon) of my heatpump-display?
I looked in "Inbetriebnahme" and I find only the firmware-vs (softwarestand=4.39).

Second question: could someone familiar with other forum (like http://www.haustechnikdialog.de/) post a question about a changelog? It would be interesting what Tecalor/SE changed over the years.
I would like to understand if heatpumps with newer firmwares-id are also more efficient.
If this is the case, many people will try to upgrade to 7278 and I will foucus on it.

p.s. I serched and saw that in the past, the firmware-updates were with together with the service software. 
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 18 Januar 2015, 13:24:07
The software ID is the last entry in "Commissioning/Inbetriebnahme" of THZ404. This might be a recent addition. So you would have to update to a newer version if it is available for your heat pump. Possibly the software ID varies for different models. I guess that the software is released on a per model/family basis and not for all models at once. I will check for changes in the 0xfe message and the software ID after next update.

It will not be easy to find out the heat pump efficiency. You obviously cannot rely on the internal values because they are derived from uncalibrated/poorly calibrated sensors. So you have to use external heat meters under similar conditions before the update and thereafter.

Do you have an update history/logs?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 18 Januar 2015, 13:46:34
@belu
Does your display show anything like software ID? If yes, could you please try to read the register 0A024B.
Would you also post the contents of the FE response from your heat pump.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 18 Januar 2015, 15:16:43
Zitat von: godmorgon am 18 Januar 2015, 13:24:07
I will check for changes in the 0xfe message and the software ID after next update.
I also think that fe is a good place to look at.

FE03B1 83910001 00000000 0006674A 0208 4D6172202039203230313120    IMMI --> 4.39 ????
xXxXxX x-_-_-_- xXx-_-_- xXxXxX_- _-_- _M_a_r_____9___2_0_1_1__
FE03B1 83F50100 00000000 00066771 030f 4d6172203134203230313420      godmorgon --> 5.39 7278
xXxXxX x-_-_-_- xXx-_-_- xXxXxX_- _-_- _M_a_r___1_4___2_0_1_4__   
FE03B1 83910001 00000000 0006674A 0205                               PhyTHZ --> 4.39  ????


Some more examples would be usefull.

How often you get a visit ftom the heatpump technician? Why not to convince him to give you the actual service software.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: godmorgon am 18 Januar 2015, 15:56:27
Zitat von: immi am 18 Januar 2015, 15:16:43
How often you get a visit ftom the heatpump technician? Why not to convince him to give you the actual service software.
They still have to tune the air flows. So it is a good chance to ask for an update. Though, I somehow doubt that they have a software installer package.
I believe belu wrote somewhere that his software (5.19.316) is dated December 2014 which would be newer than mine. But newer is not always better. I am wondering where 316 comes from (display, register, verbal statement from technician).
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 18 Januar 2015, 18:39:57
@all

Bin gerade das Wochenende im Kurzurlaub.
Zur Software Version. Ich hab die 5.19. die Software wurde vom Techniker aktualisiert. Ich habe nach dem Update dann gefragt wo denn der Unterschied ist. Die Software wäre doch immer noch 5.19. darauf hat mir der Techniker im LWZ Programm den Eintrag gezeigt das es die 5.19.316 10 Dezember 2014 ist. Der Unterschied ist nur in der ID zu erkennen. Nächste Woche schaue ich mir die Register mal an und dann können wir da vielleicht das raus finden.

LG
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 21 Januar 2015, 10:31:54
Zitat von: andre.k am 10 Januar 2015, 22:45:53
Hallo,
seit einigen Wochen habe ich FHEM im Testbetrieb. Jetzt hab ich mich auch an das THZ-Modul gewagt. Ich hatte anfangs gezögert, weil ich eine sehr altes Modell habe und erst mal kein Risiko eingehen wollte. Meine THZ303SOL läuft noch mit der Firmware 2.14., ist ja schon seit dem Jahr 2003 im Einsatz. Mein Fazit: Das Modul 00_THZ läuft stabil, sehr gute Arbeit!!
Ich habe mich zunächst auf das Lesen der Statusregister fokussiert und die Werte in den Readings mit Werten im Serviceprogramm (LWZ303V405.exe) verglichen. Dabei habe ich das Attribut firmware="2.06" gesetzt.

1.  Die Register (Befehle) sLast10errors (D1) und sFirmware (FD) scheint es bei mir nicht zu geben.  Ich bekomme hier die Antwort "010301FD1003" bzw. 0103D5D11003 ( "msg2 command not known")

2. Die anderen Register 09, 16, FB, FC,  F3,  F4, F5 kann ich per FHEM auslesen. Das Register FB enthält auch bei Firmware 2.16  einige Status-Infos, die noch nicht im Reading sGlobal sind. Das würde ich gern noch anpassen. Ich habe die folgende Zuordung herausgefunden:

         [" boosterStage3: ",   44, 1, "bit3", 1],   [" solarPump: ",      44, 1, "bit2", 1],
         [" boosterStage1: ",   44, 1, "bit1", 1],   [" compressor: ",      44, 1, "bit0", 1],
         [" heatPipeValve: ",   45, 1, "bit3", 1],     [" diverterValve: ",      45, 1, "bit2", 1],
         [" dhwPump: ",      45, 1, "bit1", 1],     [" heatingCircuitPump: ",   45, 1, "bit0", 1],
           [" mixerOpen: ",      47, 1, "bit1", 1],
           [" mixerClosed: ",   47, 1, "bit0", 1],

Hat sonst noch jemand (mit Firmware 2.x)  Interesse an diesen Werten? Könnte das jemand testen/bestätigen?

Thanks,
Andre

Hallo andre.k,

ich habe eine LWZ303i aus dem Jahr 2007 mit Firmware V2.06. Die Register sLast10errors und sFirmware  funktionieren bei mir.
Hast du in deiner fhem.cfg Datei den Eintrag "attr Mythz firmware 2.06" eingetragen?

Gruß
Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 22 Januar 2015, 20:41:15
Zitat von: peter456 am 21 Januar 2015, 10:31:54
Hallo andre.k,

ich habe eine LWZ303i aus dem Jahr 2007 mit Firmware V2.06. Die Register sLast10errors und sFirmware  funktionieren bei mir.
Hast du in deiner fhem.cfg Datei den Eintrag "attr Mythz firmware 2.06" eingetragen?

Gruß
Peter

Hallo Peter,

ja, "attr Mythz firmware 2.06" habe ich eingetragen. Ich habe in der Zwischenzeit alle Register von 01...FF mit "debug_read_raw_register_slow" ausgelesen. Die beiden Register D1 und FD sind in meiner Firmware 2.14 tatsächlich nicht implementiert. Zurzeit bin ich noch dabei die Antworten der THZ zu analysieren.

Gruß
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 24 Januar 2015, 07:57:09
@Markus:
Ich sehe grade im Wiki, dass es dort Ergänzungsbedarf gibt. Vorschlag:

ZitatHier wird beschrieben wie man mit FHEM eine Tecalor THZ / Stieben Eltron LWZ 303/304/403/404 /SOL Wärmepumpe auslesen/steuern kann. Die 504 ist derzeit noch nicht getestet, könnte aber ebenfalls funktionieren.

Zum besseren Verständnis: Tecalor ist die Privatkundenmarke von Stieben Eltron. Die Geräte sind absolut baugleich.

Nachfolgend wird von der "THZ" gesprochen.

Getestet sind die Versionen 2.06, 4.09, 4.19, 4.39 und 5.39. Ältere Andere Versionen können funktionieren, das ist jedoch nicht garantiert.

Damit wäre auch die Funktion eventuell neuerer Versionen angesprochen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: micomat am 24 Januar 2015, 18:16:08
kommt in in kürze.
bin leider derzeit privat und beruflich zu sehr eingespannt.

Gruß
markus
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 25 Januar 2015, 21:50:48
Hi immi,

I re-engineered the register of my firmware. Could you please test and apply the patchfile.


--- 00_THZ.pm 2015-01-24 18:18:52.204114685 +0100
+++ /opt/fhem/FHEM/00_THZ.pm 2015-01-25 21:19:08.984477324 +0100
@@ -300,11 +300,27 @@
%getsonly539=(%getsonly539, %getsonly439);

my %getsonly206 = (
+ "pFan" => {cmd2=>"01", type =>"01pxx206", unit =>""},
+ "pExpert" => {cmd2=>"02", type =>"02pxx206", unit =>""},
+ "pDefrostEva" => {cmd2=>"03", type =>"03pxx206", unit =>""},
+ "pDefrostAA" => {cmd2=>"04", type =>"04pxx206", unit =>""},
+ "pHeat1" => {cmd2=>"05", type =>"05pxx206", unit =>""},
+ "pHeat2" => {cmd2=>"06", type =>"06pxx206", unit =>""},
+ "pDHW" => {cmd2=>"07", type =>"07pxx206", unit =>""},
+ "pSolar" => {cmd2=>"08", type =>"08pxx206", unit =>""},
+ "pCircPump" => {cmd2=>"0A", type =>"0Apxx206", unit =>""},
+ "pHeatProg" => {cmd2=>"0B", type =>"0Bpxx206", unit =>""},
+ "pDHWProg" => {cmd2=>"0C", type =>"0Cpxx206", unit =>""},
+ "pFanProg"    => {cmd2=>"0D", type =>"0Dpxx206", unit =>""},
+ "pRestart" => {cmd2=>"0E", type =>"0Epxx206", unit =>""},
+ "pAbsence" => {cmd2=>"0F", type =>"0Fpxx206", unit =>""},
+ "pDryHeat" => {cmd2=>"10", type =>"10pxx206", unit =>""},
"sSol" => {cmd2=>"16", type =>"16sol", unit =>""},
"p01-p12" => {cmd2=>"17", type =>"17pxx206", unit =>""},
"sDHW" => {cmd2=>"F3", type =>"F3dhw", unit =>""},
"sHC1" => {cmd2=>"F4", type =>"F4hc1", unit =>""},
"sHC2" => {cmd2=>"F5", type =>"F5hc2", unit =>""},
+ "sSystem" => {cmd2=>"F6", type =>"F6syst206", unit =>""},
"sHistory" => {cmd2=>"09", type =>"09his206", unit =>""},
"sLast10errors" => {cmd2=>"D1", type =>"D1last206", unit =>""},
         "sGlobal"       => {cmd2=>"FB", type =>"FBglob206", unit =>""},  #allFB
@@ -1014,10 +1030,88 @@
      [" x20: ", 20, 4, "hex2int", 1], [" x24: ", 24, 4, "hex2int", 1],
      [" x28: ", 28, 4, "hex2int", 1], [" x32: ", 32, 2, "hex2int", 1]
      ],
+  "01pxx206" => [
+ ["p37Fanstage1AirflowInlet: ", 4, 2, "hex", 1],
+ [" p38Fanstage2AirflowInlet: ", 6, 2, "hex", 1],
+ [" p39Fanstage3AirflowInlet: ", 8, 2, "hex", 1],
+ [" p40Fanstage1AirflowOutlet: ", 10, 2, "hex", 1],
+ [" p41Fanstage2AirflowOutlet: ", 12, 2, "hex", 1],
+ [" p42Fanstage3AirflowOutlet: ", 14, 2, "hex", 1],
+ [" p43UnschedVent3: ", 16, 4, "hex", 1],
+ [" p44UnschedVent2: ", 20, 4, "hex", 1],
+ [" p45UnschedVent1: ", 24, 4, "hex", 1],
+ [" p46UnschedVent0: ", 28, 4, "hex", 1],
+ [" p75PassiveCooling: ", 32, 2, "hex", 1]
+ ],
+  "05pxx206" => [
+ ["p13GradientHC1: ", 4, 4, "hex", 10],
+ [" p14LowEndHC1: ", 8, 4, "hex", 10],
+ [" p15RoomInfluenceHC1: ", 12, 2, "hex", 10],
+ [" p16GradientHC2: ", 14, 4, "hex", 10],
+ [" p17LowEndHC2: ", 18, 4, "hex", 10],
+ [" p18RoomInfluenceHC2: ", 22, 2, "hex", 10],
+ [" p19FlowProportionHC1: ", 24, 4, "hex", 10],
+ [" p20FlowProportionHC2: ", 28, 4, "hex", 10],
+ [" MaxSetHeatFlowTempHC1: ", 32, 4, "hex", 10],
+ [" MinSetHeatFlowTempHC1: ", 36, 4, "hex", 10],
+ [" MaxSetHeatFlowTempHC2: ", 40, 4, "hex", 10],
+ [" MinSetHeatFlowTempHC2: ", 44, 4, "hex", 10],
+ ],
+  "06pxx206" => [
+ ["p21Hist1: ", 4, 2, "hex", 10],
+ [" p22Hist2: ", 6, 2, "hex", 10],
+ [" p23Hist3: ", 8, 2, "hex", 10],
+ [" p24Hist4: ", 10, 2, "hex", 10],
+ [" p25Hist5: ", 12, 2, "hex", 10],
+ [" p26Hist6: ", 14, 2, "hex", 10],
+ [" p27Hist7: ", 16, 2, "hex", 10],
+ [" p28Hist8: ", 18, 2, "hex", 10],
+ [" p29HistAsymmetry: ", 20, 2, "hex", 1],
+ [" p30integralComponent: ", 22, 4, "hex", 1],
+ [" p31MaxBoostStages: ", 26, 2, "hex", 1],
+ [" MaxHeatFlowTemp: ", 28, 4, "hex", 10],
+ [" p49SummerModeTemp: ", 32, 4, "hex", 10],
+ [" p50SummerModeHysteresis: ", 36, 4, "hex", 10],
+ [" p77OutTempAdjust: ", 40, 4, "hex", 1],
+ [" p78DualModePoint: ", 44, 4, "hex", 10],
+ [" p79ReHeatingDelay: ", 48, 2, "hex", 1]
+ ],
+ "07pxx206" => [
+ ["p32HystDHW: ", 4, 2, "hex", 10],
+ [" p33BoosterTimeoutDHW: ", 6, 2, "hex", 1],
+ [" p34TempLimitBoostDHW: ", 8, 4, "hex", 10],
+ [" p35PasteurisationInterval: ", 12, 2, "hex", 1],
+ [" p36MaxDurationDHWLoad: ", 14, 2, "hex", 1],
+ [" PasteurisationTemp: ", 16, 4, "hex", 10],
+ [" MaxBoostStagesDHW: ", 20, 2, "hex", 1],
+ [" p84EnableDHWBuffer: ", 22, 2, "hex", 1]
+ ],
+  "08pxx206" => [
+ ["p80EnableSolar: ", 4, 2, "hex", 1],
+ [" p81DiffTempSolarLoading: ", 6, 4, "hex", 10],
+ [" p82DelayCompStartSolar: ", 10, 2, "hex", 1],
+ [" p84DHWTempSolarMode: ", 12, 4, "hex", 10],
+ [" HystDiffTempSolar: ", 16, 4, "hex", 1],
+ [" CollectLimitTempSolar: ", 20, 4, "hex", 10]
+ ],
+  "0Apxx206" => [
+ ["p54MinPumpCycles: ", 4, 2, "hex", 1],
+ [" p55MaxPumpCycles: ", 6, 4, "hex", 1],
+ [" p56OutTempMaxPumpCycles: ", 10, 4, "hex", 10],
+ [" p57OutTempMinPumpCycles: ", 14, 4, "hex", 10],
+ [" p58SuppressTempCaptPumpStart: ", 18, 4, "hex", 1]
+ ],
+  "10pxx206" => [
+ ["p70StartDryHeat: ", 4, 2, "hex", 1],
+ [" p71BaseTemp: ", 6, 4, "hex", 10],
+ [" p72PeakTemp: ", 10, 4, "hex", 10],
+ [" p73TempDuration: ", 14, 4, "hex", 1],
+ [" p74TempIncrease: ", 18, 4, "hex", 10]
+ ],
   "17pxx206" => [["p01RoomTempDay: ", 4, 4,  "hex",  10], [" p02RoomTempNight: ", 8,  4, "hex", 10],
      [" p03RoomTempStandby: ", 12, 4,  "hex", 10], [" p04DHWsetDayTemp: ", 16, 4,  "hex", 10],
      [" p05DHWsetNightTemp: ", 20, 4,  "hex", 10], [" p06DHWsetStandbyTemp: ", 24, 4,  "hex", 10],
-       [" p07FanStageDay: ", 28, 2,  "hex", 1], [" p08FanStageNight: ", 30, 4,  "hex", 1],
+       [" p07FanStageDay: ", 28, 2,  "hex", 1], [" p08FanStageNight: ", 30, 2,  "hex", 1],
      [" p09FanStageStandby: ", 32, 2,  "hex", 1], [" p10RoomTempManual: ", 34, 4,  "hex", 10],
      [" p11DHWsetManualTemp: ", 38, 4,  "hex", 10],  [" p12FanStageManual: ", 42, 2,  "hex", 1],
     ],
@@ -1033,11 +1127,11 @@
      [" fault2CODE: ", 32, 4, "faultmap", 1], [" fault2TIME: ", 36, 4, "hex2time", 1],  [" fault2DATE: ", 40, 4, "hexdate", 100],
      [" fault3CODE: ", 44, 4, "faultmap", 1], [" fault3TIME: ", 48, 4, "hex2time", 1],  [" fault3DATE: ", 52, 4, "hexdate", 100]
      ],
-  "F3dhw"  => [["dhw_temp: ", 4, 4, "hex2int", 10], [" outside_temp: ", 8, 4, "hex2int", 10],
+  "F3dhw"  => [["dhw_temp: ", 4, 4, "hex2int", 10], [" outside_temp: ", 8, 4, "hex2int", 10],
      [" dhw_set_temp: ", 12, 4, "hex2int", 10],  [" comp_block_time: ", 16, 4, "hex2int", 1],
-       [" x20: ", 20, 4, "hex2int", 1], [" heat_block_time: ", 24, 4, "hex2int", 1],
-       [" x28: ", 28, 4, "hex2int", 1], [" x32: ", 32, 4, "hex2int", 1],
-       [" x36: ", 36, 4, "hex", 1]
+       [" x20: ", 20, 4, "hex2int", 1], [" heat_block_time: ", 24, 4, "hex2int", 1],
+       [" BoosterStage: ", 28, 2, "hex", 1], [" x30: ", 30, 4, "hex", 1],
+       [" OpMode: ", 34, 2, "opmodehc", 1], [" x36: ", 36, 4, "hex", 1]
      ],
   "F4hc1"  => [["outsideTemp: ", 4, 4, "hex2int", 10], [" x08: ", 8, 4, "hex2int", 10],
      [" returnTemp: ", 12, 4, "hex2int", 10],  [" integralHeat: ", 16, 4, "hex2int", 1],
@@ -1053,6 +1147,8 @@
      [" heatTemp: ", 20, 4, "hex2int", 10], [" stellgroesse: ", 24, 4, "hex2int", 10],
      [" seasonMode: ", 30, 2, "somwinmode", 1],[" opMode: ", 36, 2, "opmodehc", 1]
     ],
+  "F6syst206" => [["LüfterstufeManuell: ", 30, 2, "hex", 1], [" RestlaufzeitLüfter: ", 36, 4, "hex", 1]
+ ],
   "FBglob" => [["outsideTemp: ", 8, 4, "hex2int", 10], [" flowTemp: ", 12, 4, "hex2int", 10],
      [" returnTemp: ", 16, 4, "hex2int", 10], [" hotGasTemp: ", 20, 4, "hex2int", 10],
      [" dhwTemp: ", 24, 4, "hex2int", 10], [" flowTempHC2: ", 28, 4, "hex2int", 10],
@@ -1090,9 +1186,9 @@
      [" outputVentilatorPower: ", 48, 2, "hex", 1],  [" inputVentilatorPower: ", 50, 2, "hex", 1], [" mainVentilatorPower: ", 52, 2, "hex", 1],
      [" outputVentilatorSpeed: ", 56, 2, "hex", 1], [" inputVentilatorSpeed: ", 58, 2, "hex", 1],  [" mainVentilatorSpeed: ", 60, 2, "hex", 1],
      [" outside_tempFiltered: ", 64, 4, "hex2int", 10], [" relHumidity: ", 70, 4, "n.a.", 1],
-       [" dewPoint: ", 82, 4, "n.a.", 1],
-       [" P_Nd: ", 86, 4, "n.a.", 1], [" P_Hd: ", 90, 4, "n.a.", 1],
-       [" actualPower_Qc: ", 94, 8, "n.a.", 1], [" actualPower_Pel: ", 102, 8, "n.a.", 1],
+       #[" dewPoint: ", 82, 4, "n.a.", 1],
+       #[" P_Nd: ", 86, 4, "n.a.", 1], [" P_Hd: ", 90, 4, "n.a.", 1],
+       #[" actualPower_Qc: ", 94, 8, "n.a.", 1], [" actualPower_Pel: ", 102, 8, "n.a.", 1],
      [" collectorTemp: ", 4,  4, "hex2int", 10], [" insideTemp: ", 32, 4, "hex2int", 10] #, [" x84: ", 84, 4, "donottouch", 1]
      ],
   "FCtime" => [["Weekday: ", 4, 1,  "weekday", 1], [" Hour: ", 6, 2, "hex", 1],


The response message for Register FB in my firmware is shorter. Therefore I commented out the parsing elements which are out of the message, otherwise I got error messages in the log file.

Thanks
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 09:24:02
Hi Andre
excellent patch!!
I will check it this evening carefully.
I do not want to change the order of FB, because I would like that people exchange their basic plot configuration.
The warning about message lenght will be fixed like this
[" actualPower_Qc: ",      50, 8, "n.a.", 1],   [" actualPower_Pel: ",      50, 8, "n.a.", 1],
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 26 Januar 2015, 16:25:44
Hello,
these are my first steps with FHEM.
I get the following error.


2015.01.26 16:11:40 5: THZ_Get: Try to get 'p03RoomTempStandbyHC2SummerMode'
2015.01.26 16:11:40 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.01.26 16:11:40 5: Mythz sending 02
2015.01.26 16:11:40 5: SW: 02
2015.01.26 16:11:40 5: Mythz start Funktion THZ_ReadAnswer
2015.01.26 16:11:40 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2015.01.26 16:11:40 5: THZ_Get: Error msg2: 'InterfaceNotRespondig'
2015.01.26 16:11:40 5: Mythz/RAW: 10
2015.01.26 16:11:40 2: Mythz/RAW: 10


Strawberry Fhem console:

given is experimental at ./FHEM/00_THZ.pm line 559, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 560, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 564, <$fh> line 7.
given is experimental at ./FHEM/00_THZ.pm line 575, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 576, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 577, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 578, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 579, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 580, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 581, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 582, <$fh> line 7.
given is experimental at ./FHEM/00_THZ.pm line 597, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 598, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 604, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 615, <$fh> line 7.
given is experimental at ./FHEM/00_THZ.pm line 1172, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1173, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1174, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1175, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1176, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1177, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1178, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1179, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1180, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1181, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1182, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1183, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1184, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1185, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1186, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1187, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1188, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1189, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1190, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1191, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1192, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1193, <$fh> line 7.
when is experimental at ./FHEM/00_THZ.pm line 1194, <$fh> line 7.


FHEM is loaded onto a Win8.1 64 bit, Strawberry Perl 5.20.1.1-32bit
I connect the heatpump (LWZ403) via usb2ser.
The software of the heatpump is 2.36.
Can you help me?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 16:47:52
Hi    brinkmicha
happy you want to join us

6 comments from my side:
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 26 Januar 2015, 17:36:07
Hi immi,
my Win8 is on a Zotac ID86 -> 10W. I use the system for the Stiebel and Solaredge Software.
There is no USB or LAN Port on my LWZ403sol from 2008. So I use the Serial Port like Robert Penz http://robert.penz.name/heat-pump-lwz/ (http://robert.penz.name/heat-pump-lwz/).
I use the THZ-FHEM version 0.127.
No, I have not used "attr Mythz firmware 2.06"  in config file...  where it must be entered?
Here is the config...

Thanks
brinkmicha
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 17:51:21
at the beginning
just after define Mythz THZ com4@9600


define Mythz THZ com4@9600
attr Mythz firmware 2.06


immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 26 Januar 2015, 20:08:40
Hi immi,

behave the same...   :(

more ideas? 

brinkmicha
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 20:18:30
Zitat von: brinkmicha am 26 Januar 2015, 20:08:40
Hi immi,
behave the same...   :(
if it is behaving the same (you have problem with p03RoomTempStandbyHC2SummerMode), it means you have not done what I said correctly --> "attr Mythz firmware 2.06"

if it is not behaving the same, post the logs
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 26 Januar 2015, 20:26:47
Zitat von: immi am 26 Januar 2015, 09:24:02
I do not want to change the order of FB, because I would like that people exchange their basic plot configuration.
The warning about message lenght will be fixed like this
[" actualPower_Qc: ",      50, 8, "n.a.", 1],   [" actualPower_Pel: ",      50, 8, "n.a.", 1],
immi
Hi immi,
I aggree with you, we should not change the order of values in the readings. I fix it in your way.
Another problem is line#1137
$parsingcmd = substr($message,2,6) if ($parsingcmd =~ m/(0A|0B|0C)/) ;
In Firmware 2.x the command is always 1 Byte. Could you add the condition like "firmware" ne "2.06"?
Thank You.
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 21:26:00
Hi Andre
I merged it, and tested it for my firmware
please check it again before I upload it.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 26 Januar 2015, 22:16:06
Hi immi,

great, it works perfect.
Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 26 Januar 2015, 22:30:14
uploaded v0.128 tomorrow you can update
-changelog: now most of parameters can be read from old firmwares

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 27 Januar 2015, 07:02:16
Zitat von: brinkmicha am 26 Januar 2015, 20:08:40
Hi immi,

behave the same... 

more ideas? 

brinkmicha


Du solltest zuerst wissen, ob überhaupt die Kommunikationsstrecke ok ist => eine Fehlerquelle ausschließen. Wenn Du den HeatpumpMonitor erwähnst, dann kennst Du ja den grundsätzlichen Ablauf der Kommunikation. Das kannst Du mit einer Terminalsoftware testen.  Was Robert Penz nicht erwähnt: zwischen Antwort der LWZ und dem nächsten Befehl muss ein Zeitfenster von min.10, max. 500ms eingehalten werden.

Unter Windows kannst Du dieses Terminal https://sites.google.com/site/terminalbpp/ (https://sites.google.com/site/terminalbpp/) verwenden, um direkt mit der LWZ zu "reden". Durch seine Makrofähigkeit kann man das Zeitfenster in Form von Delays berücksichtigen. Ein Makro, um sGlobal abzufragen, wäre dann

$02%DLY0010$01$00$FC$FB$10$03%DLY0010$10

Die Firmwareversion erhältst Du mit

$02%DLY0010$01$00$FE$FD$10$03%DLY0010$10

Wenn Du damit Antworten bekommst (im ersten Fall den größeren Datenblock, im zweiten Fall einen kürzeren, jeweils im Hex-Format), dann stimmt Deine Kommunikation zwischen PC und LWZ.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Januar 2015, 10:57:20
Hi brinkmicha

I think I understood where  the problem with Windows is
https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/DevIo.pm
# NOTE2: This works on Windows only for TCP connections
Sub DevIo_SimpleReadWithTimeout($$)
Sub DevIo_TimeoutRead($$)


I do not know if it can be fixed, but let´s try.
Please update to v0.128
Please change line 768 of 00_THZ.pm

my $buf = DevIo_SimpleReadWithTimeout($hash, 0.7);

with

select(undef, undef, undef, 0.025); # this is a delay of 25ms
my $buf = DevIo_DoSimpleRead($hash);



then start fhem with option "attr Mythz firmware 2.06"
after that post your complete log as file
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 27 Januar 2015, 16:00:58
Hi immi,

we're on the right way!  :)

Here my logs...

brinkmicha

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 27 Januar 2015, 16:12:38
Hallo willybauss,

danke für deine Antwort.
Habe die Kommunikation zwischen PC und LWZ wie beschrieben getestet - läuft!

Mal schauen was alles mit immis Anpassungen funktioniert.

Gruß brinkmicha

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Januar 2015, 16:53:13
Zitat von: brinkmicha am 27 Januar 2015, 16:00:58
Hi immi,
we're on the right way!  :)
brinkmicha

Jap the comunication is really terrible under windows.
you should also change following lines at abour line 778


while (( (length($data) == 1) or (($data =~ m/^01/) and ($data !~ m/1003$/m ))) and ($count <= $countmax))
{ my $buf1 = DevIo_SimpleReadWithTimeout($hash, 0.02);
Log3($hash->{NAME}, 5, "double read $count activated $data");


with


while (( (length($data) == 1) or (($data =~ m/^01/) and ($data !~ m/1003$/m ))) and ($count <= $countmax))
{ select(undef, undef, undef, 0.005); # this is a delay of 5ms
my $buf1 = DevIo_DoSimpleRead($hash);
Log3($hash->{NAME}, 5, "double read $count activated $data");


I strongly suggest not to use this fix in the unix world. This is only for windows.
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 27 Januar 2015, 17:16:25
Hi immi,

I've done...
Here are the logs...

Thanks
brinkmicha
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 27 Januar 2015, 19:22:48
Zitat von: brinkmicha am 27 Januar 2015, 17:16:25
I've done...
Here are the logs...
not bad, despite windows :)
you can live very well with the result.
Remove verbose 5.
Play with the system for some weeks, then....
You, Peter and Andre have an old heatpump.
You have to check the parameters that Peter and Andre helped to decode...
Some of them are not decoded correctly for your heatpump, like pDHWProg: CC0C000009377F00

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 27 Januar 2015, 20:02:42
Zitat von: immi am 27 Januar 2015, 19:22:48

Some of them are not decoded correctly for your heatpump, like pDHWProg: CC0C000009377F00

immi
That's because some registers (e.g. 0C) are still on my todo list;-)
andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: brinkmicha am 28 Januar 2015, 10:33:54
Hi immi and all,

I thank you very much!

brinkmicha

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 28 Januar 2015, 19:07:08
Zitat von: andre.k am 27 Januar 2015, 20:02:42
That's because some registers (e.g. 0C) are still on my todo list;-)
andre

Hallo andre.k,

bei meiner alten Firmware 2.06 habe ich in der FHEM-Version 0.128 noch folgende nicht dekodierte Antworten:
pDHWProg
E10C089804B07F01
pDefrostAA
BA043C0064001401
pDefrostEva
EE030096000A00960064143C
pAbsence
D80F00C8000000
pExpert
390201191C0000
pFanProg
8F0D064008987F01001E05787F01
pHeatProg
380B0852033E7F01033E034D7F01
pRestart
910E000000640000001E
sFirmware-Id
010302FE1003
msg2 command not known
sSol
01031A161003
msg2 command not known

Sind alle diese Register noch bei dir auf der TODO-Liste oder liegt das an meiner Firmware?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 28 Januar 2015, 19:45:10
Hallo zusammen,

ich wollte mich für die Infos hier und den Code bedanken. Dieser Thread und die Weiterentwicklung von Robert's "Entdeckungen" haben es mir ermöglicht, die Unterstützung für die WP in smarthome.pi umzusetzen.

Ich habe noch zwei Kleinigkeiten beizutragen:
Das Register 0x0A0176 enthält bei meiner WP (THZ 404 SOL, Ver. 5.39, SW ID 7278) Bits für die Display-Icons.
Ich habe bisher folgende Bits decodiert (Namen wie im Handbuch):
0x0001 - Schaltprogramm
0x0002 - Verdichter
0x0004 - Heizen
0x0010 - Warmwasserbereitung
0x0020 - elektrische Nachheizstufen
0x0100 - Filterwechsel oben und unten
0x0200 - Lüftungsstufe
0x0400 - Heizkreispumpe
0x0800 - Abtauen Verdamper
0x1000 - Filterwechsel oben
0x2000 - Filterwechsel unten

Des Weiteren findet man die Raumtemperatur der Fernbedienung in Bytes 32-33 der Payload der Message 0xF4. Ich glaube es würde in Perl folgendem entsprechen:
[" roomTempRC: ", 68, 4, "hex2int", 10]

Viele Grüße
toggle
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 28 Januar 2015, 20:40:29
Zitat von: peter456 am 28 Januar 2015, 19:07:08
Hallo andre.k,

bei meiner alten Firmware 2.06 habe ich in der FHEM-Version 0.128 noch folgende nicht dekodierte Antworten:
pDHWProg
E10C089804B07F01
pDefrostAA
BA043C0064001401
pDefrostEva
EE030096000A00960064143C
pAbsence
D80F00C8000000
pExpert
390201191C0000
pFanProg
8F0D064008987F01001E05787F01
pHeatProg
380B0852033E7F01033E034D7F01
pRestart
910E000000640000001E
sFirmware-Id
010302FE1003
msg2 command not known
sSol
01031A161003
msg2 command not known

Sind alle diese Register noch bei dir auf der TODO-Liste oder liegt das an meiner Firmware?

Hallo Peter,

ja, für alle Register, die bereits einen Namen haben, baue ich noch die Regeln für das Parsing. Ich hoffe ich bekomme das bis zum Wochenende hin.
Wenn die Meldung "msg2 command not known" kommt, ist der Befehl in der THZ nicht impelementiert. FE geht bei mir auch nicht. Wenn Du kein Solar hast, geht bei Dir offenbar auch kein Register 16.

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: peter456 am 28 Januar 2015, 20:55:55
alles klar Andre. Nur keine Hektik.

Gruß Peter
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Januar 2015, 22:04:48
Zitat von: toggle am 28 Januar 2015, 19:45:10
Das Register 0x0A0176 enthält bei meiner WP (THZ 404 SOL, Ver. 5.39, SW ID 7278) Bits für die Display-Icons.
Ich habe bisher folgende Bits decodiert (Namen wie im Handbuch):
0x0001 - Schaltprogramm
0x0002 - Verdichter
0x0004 - Heizen
0x0010 - Warmwasserbereitung
0x0020 - elektrische Nachheizstufen
0x0100 - Filterwechsel oben und unten
0x0200 - Lüftungsstufe
0x0400 - Heizkreispumpe
0x0800 - Abtauen Verdamper
0x1000 - Filterwechsel oben
0x2000 - Filterwechsel unten
Des Weiteren findet man die Raumtemperatur der Fernbedienung in Bytes 32-33 der Payload der Message 0xF4. Ich glaube es würde in Perl folgendem entsprechen:
[" roomTempRC: ", 68, 4, "hex2int", 10]
hi toggle/godmorgon
thanks for sharing, I will have a look.
All the best for your python port!!
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Januar 2015, 23:07:32
Zitat von: toggle am 28 Januar 2015, 19:45:10
Des Weiteren findet man die Raumtemperatur der Fernbedienung in Bytes 32-33 der Payload der Message 0xF4. Ich glaube es würde in Perl folgendem entsprechen:
[" roomTempRC: ", 68, 4, "hex2int", 10]
SUPER. Danach hatte ich selbst schon erfolglos gesucht.

@ immi: Could you implement it, please? It would really help me a lot!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 28 Januar 2015, 23:11:18
In einem anderen Forum habe ich grade eine wichtige Information über einen Firmwarebug der 303 gefunden. Keine Ahnung, ob andere Pumpen dasselbe Problem haben.
ZitatÄnderungen an der Einstellung der Asymmetrie der Heizkurve (P30) werden oft nicht übernommen.
Beispiel: Du änderst die Assy von 2 auf 3. Im Display steht auch 3 drin, aber die Anlage arbeitet weiter mit 2.
Erst wenn du den Reset drückst und dann wirklich nach dem Reset 3 drin steht, dann übernimmt er es auch.
Wenn ich die Assy bei meiner 303 ändere, brauche ich auch bis zu 3 Resets, bis diese endlich übernommen wird...

Das erklärt mir so manches komische Verhalten der Heizdiagramme.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 28 Januar 2015, 23:51:10
Zitat von: willybauss am 28 Januar 2015, 23:11:18
In einem anderen Forum habe ich grade eine wichtige Information über einen Firmwarebug der 303 gefunden. Keine Ahnung, ob andere Pumpen dasselbe Problem haben.
Das erklärt mir so manches komische Verhalten der Heizdiagramme.
Do they write if the Firmwarebug can be fixed with a firmware update?
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Januar 2015, 08:17:26
Zitat von: immi am 28 Januar 2015, 23:51:10
Do they write if the Firmwarebug can be fixed with a firmware update?
immi
yes, one wrote he got an update and it seems to work. But based on my own experience I doubt about the reliability of this user's answers ... But I'll ask again.

As far as I know it needs a Stiebel Eltron technician to update the firmware, right?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 11:14:20
Zitat von: willybauss am 29 Januar 2015, 08:17:26
As far as I know it needs a Stiebel Eltron technician to update the firmware, right?
the problem is where to get the firmwares and a compatibility list
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 29 Januar 2015, 20:01:42
Hallo,
Seit ein paar Tagen werden bei mir in den Plots nichts mehr angezeigt. Die Fenster sind da, aber leer (ohne Kennlinien). Ich habe nichts geändert. Der Raspi ist mit der THZ verbunden und die Werte sind bei sGlobal alle da (sichtbar).Nur werden die Plots nicht geschrieben. Softwarestand 0.127
Ich habe auch schon den Raspi neu gestartet.
Es ist jetzt alles ca. 4 Monate am Stück gelaufen.
Hat mir jemand einen Tipp?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 20:22:33
Zitat von: Gassi am 29 Januar 2015, 20:01:42
Hallo,
Seit ein paar Tagen werden bei mir in den Plots nichts mehr angezeigt. Die Fenster sind da, aber leer (ohne Kennlinien). Ich habe nichts geändert. Der Raspi ist mit der THZ verbunden und die Werte sind bei sGlobal alle da (sichtbar).Nur werden die Plots nicht geschrieben. Softwarestand 0.127
Ich habe auch schon den Raspi neu gestartet.
Es ist jetzt alles ca. 4 Monate am Stück gelaufen.
Hat mir jemand einen Tipp?
update or force update
thz didn´t change much; but major changes in fhem including plotting have been done in the last days
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Gassi am 29 Januar 2015, 20:45:14
Ich habe update Force ausgeführt und nun 0.128.

(http://www.bilder-upload.eu/thumb/9916d1-1422560894.jpg) (http://www.bilder-upload.eu/show.php?file=9916d1-1422560894.jpg)
(http://www.bilder-upload.eu/thumb/5714b7-1422561026.jpg) (http://www.bilder-upload.eu/show.php?file=5714b7-1422561026.jpg)
(http://www.bilder-upload.eu/thumb/6dcf7d-1422561457.jpg) (http://www.bilder-upload.eu/show.php?file=6dcf7d-1422561457.jpg)
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: PhyTHZ am 29 Januar 2015, 20:48:44
Hello all,

I continued to search for the reason for the numerous NAK/no response messages in my log and looked at the communication between my Zyxel NAS and the THZ403sol v. 4.39 with a "spy" cable. immi was completely right, the communication itself looks fine. If the problem occurs, the sequence is always

02 (THZ_PM)
10 (403sol)
Actual request (THZ_PM)
15 or "no response" (403sol)

Up to now I haven't found any correlation with the 403sol system state or the like.
So unless somebody has a better idea, the only thing I could think of is to implement a loop repeating failed requests.

Regarding the firmware version discussion: I had a look at the PCB and found a label in the center with "F.419" followed by a five digit number on it. Maybe this is a hint, that the PCB left the factory with firmware version 4.19. It is really a pity, that it's not possible to get the service software from Stiebel/Tecalor (or the description of the protocol).

However, despite these issues the monitoring already revealed some interesting things; e.g. my 403sol is affected from the "circulation pump runs always, if solar is active" bug. So either I need a new corrected firmware or control over "freigabe solar" in fhem :-)

Best wishes,

PhyTHZ
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 29 Januar 2015, 20:54:14
Hi immi,

the attached patch contains the missing parsing rules for the 2.x commands. I had some problems with the parsing type hex2time.
when ("hex2time") {$value= sprintf(join(':', split("\\.", hex(substr($value, 0,2) . substr($value, 2,2))/100))) ;}

The start/end time in the program registers are represented in hex:0735 -> decimal: 1845 -> time:18:45.
In my case i used the following line.
when ("hex2time") {$value= sprintf("%02u:%02u", hex($value)/100, hex($value)%100) ;}

Could you please check, if this works in all cases. Otherwise we need to use two different versions of hex2time.

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 20:57:26
Gassi
look at your logfiles. maybe empty or corrupted?

PhyTHZ
I would suggest that you do not loop in case of a NAK.
I inteprete a NAK as a strange status of your heatpump. If it is really busy, I wouldn´t increase the CPU-load.
I would just drop a reading every now and then.
I am still hoping we can (sooner or later) upgrade our firmware ourself.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 21:10:21
Hi Andre
can you explain me the difference?
my $value = "0735";
$value1= sprintf(join(':', split("\\.", hex(substr($value, 0,2) . substr($value, 2,2))/100))) ;
$value2= $value= sprintf("%02u:%02u", hex($value)/100, hex($value)%100) ;
print $value1;
print "\n";
print $value2;

I get the same result 18:45 in MACOS and QNAP.
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: PhyTHZ am 29 Januar 2015, 21:20:58
Hi immi,

I agree with you. A loop immediately resending each failed request wouldn't be very clever. However, I want to make sure, that parameters like sElectrDHWDay, sElectrDHWTotal, or the like are read at least once a day. Of course I could just decrease the polling interval, but that wouldn't be very elegant as well.

Best wishes,

PhyTHZ
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 29 Januar 2015, 21:28:08
Hi immi,

try another example "0320" and you see the difference.

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 21:39:17
Zitat von: PhyTHZ am 29 Januar 2015, 21:20:58
However, I want to make sure, that parameters like sElectrDHWDay, sElectrDHWTotal, or the like are read at least once a day.
Hi PhyTHZ
you are right not elegant: but I would read them 4 times a day and store them on change with a min of one time every 23h.

Zitat von: andre.k am 29 Januar 2015, 21:28:08
try another example "0320" and you see the difference.
Hi Andre,
I see. I use your fix.
immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 29 Januar 2015, 21:50:28
Hi Andre
please test
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 29 Januar 2015, 22:40:25
Zitat von: immi am 29 Januar 2015, 21:50:28
Hi Andre
please test
immi
Hi immi,
it works, verry good.
thank you
Andre



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 29 Januar 2015, 23:45:04
Zitat von: immi am 29 Januar 2015, 20:57:26
Gassi
look at your logfiles. maybe empty or corrupted?
@Gassi:
Am besten mal das Logfile umbenennen, so dass fhem es nicht mehr findet. Es sollte dann neu angelegt werden. Dann mal ne Weile laufen lassen und im File mit Texteditor nachschauen, ob wirklich alle paar Minuten die geloggten Daten drin ankommen.

Ich hatte mal versehentlich eine Textzeile eingefügt. Ab diesem Datum/Uhrzeit blieben meine Plots leer. Die Zeile aus dem Log gelöscht und alles war wieder gut.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 30 Januar 2015, 10:48:22
Zitat von: toggle am 28 Januar 2015, 19:45:10

Ich habe noch zwei Kleinigkeiten beizutragen:
Das Register 0x0A0176 enthält bei meiner WP (THZ 404 SOL, Ver. 5.39, SW ID 7278) Bits für die Display-Icons.
Ich habe bisher folgende Bits decodiert (Namen wie im Handbuch):
0x0001 - Schaltprogramm
0x0002 - Verdichter
0x0004 - Heizen
0x0010 - Warmwasserbereitung
0x0020 - elektrische Nachheizstufen
0x0100 - Filterwechsel oben und unten
0x0200 - Lüftungsstufe
0x0400 - Heizkreispumpe
0x0800 - Abtauen Verdamper
0x1000 - Filterwechsel oben
0x2000 - Filterwechsel unten

Des Weiteren findet man die Raumtemperatur der Fernbedienung in Bytes 32-33 der Payload der Message 0xF4. Ich glaube es würde in Perl folgendem entsprechen:
[" roomTempRC: ", 68, 4, "hex2int", 10]

@ Toggle, thx

Immi, can u add the lines for the thz 304 404 5.39 in sGlobal?

thx Immi

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2015, 13:18:42
Zitat von: belu am 18 Januar 2015, 18:39:57
Bin gerade das Wochenende im Kurzurlaub.
Zur Software Version. Ich hab die 5.19. die Software wurde vom Techniker aktualisiert. Ich habe nach dem Update dann gefragt wo denn der Unterschied ist. Die Software wäre doch immer noch 5.19. darauf hat mir der Techniker im LWZ Programm den Eintrag gezeigt das es die 5.19.316 10 Dezember 2014 ist. Der Unterschied ist nur in der ID zu erkennen. Nächste Woche schaue ich mir die Register mal an und dann können wir da vielleicht das raus finden.
Hi Belu
could you provide your FE register, I would like to have more examples?

FE03B1 83910001 00000000 0006674A 0208 4D6172202039203230313120    IMMI --> 4.39 ????
xXxXxX x-_-_-_- xXx-_-_- xXxXxX_- _-_- _M_a_r_____9___2_0_1_1__
FE03B1 83F50100 00000000 00066771 030f 4d6172203134203230313420      godmorgon --> 5.39 7278
xXxXxX x-_-_-_- xXx-_-_- xXxXxX_- _-_- _M_a_r___1_4___2_0_1_4__   
FE03B1 83910001 00000000 0006674A 0205                               PhyTHZ --> 4.39  ????


Zitat von: belu am 30 Januar 2015, 10:48:22
Immi, can u add the lines for the thz 304 404 5.39 in sGlobal?
Hi Belu
sGlobal is FB, Toggle spoke about F4

Hi Willy, Hi Belu
I implemented Toggle input some days ago.
you can test file attached to http://forum.fhem.de/index.php/topic,13132.msg253791.html#msg253791
I will wait before uploading to the repository for your feedback.
immi


Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Januar 2015, 21:05:49
In another forum I learned that the "firmware" version x.yz, e.g. 4.19 ist not really a firmware version, but most probably just represents a hardware state. That makes it understandable that users having same version 4.19, but anyway need to set different COM port speed.
I tried to get an overview about the different version we're meanwhile dealing with. Please help to complete the list by adding your one.

303i   2.06   peter456
303i   3.19   Jakl
303i   4.09   houseowner123, Iwzler
303SOL   4.19   willybauss, xyz_fhem
403SOL   2.36   brinkmicha
403SOL   4.39   PhyTHZ
      4.39   immi
            Heiner
            micomat
404SOL   4.39   maximalz   (really? I expect it to be either 403SOL or 5.39)
            THZ_Haus
            firebal301
404      5.39   michaelk68
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2015, 21:28:29
overview makes sense and please add register FE.
you can get it by setting verbose to 5 just before reading sFirmware-Id

immi 403SOL
sFirmware version  4.39
sFirmware-Id  FE03B1 83910001 00000000 0006674A 0208 4D6172202039203230313120 
speed 115200
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 30 Januar 2015, 22:01:51
303Sol   2.14
FE and FD not implemented
speed 9600

andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Januar 2015, 22:05:44
Zitat von: immi am 30 Januar 2015, 13:18:42
Hi Willy, Hi Belu
I implemented Toggle input some days ago.
you can test file attached to http://forum.fhem.de/index.php/topic,13132.msg253791.html#msg253791 (http://forum.fhem.de/index.php/topic,13132.msg253791.html#msg253791)
I will wait before uploading to the repository for your feedback.
immi
Hi immi,
seems to work as before. How can I access the new features - roomTempRC and the display icons ?
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2015, 22:45:19
Zitat von: willybauss am 30 Januar 2015, 22:05:44
Hi immi,
seems to work as before. How can I access the new features - roomTempRC and the display icons ?
Willy
look in
sDisplay and sHC1
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 30 Januar 2015, 22:49:02
Zitat von: immi am 28 Januar 2015, 22:04:48
hi toggle/godmorgon
Sorry to disappoint you. Even if there may be some coincidences this it not the case.

Two more FE responses from THZ 404 SOL (5.39):
03 b1 83 f5 00 01 00 ** ** ** 00 06 67 71 03 0b 4e 6f 76 20 20 39 20 32 30 31 31 20
03 b1 83 f5 01 00 00 ** ** ** 00 06 67 71 03 0f 4d 61 72 20 31 34 20 32 30 31 34 20

** - es handelt sich um die Seriennummer der Hauptplatine (sollte man vielleicht nicht posten)
Blau ist vermutlich die Hardware-Variante:
49 - THZ 303 SOL (willybauss)
4A - THZ 403 SOL (immi, PhyTHZ)
71 - THZ 404 SOL (toggle, godmorgon, *****)

Und in rot eine weitere Variante der SW-Versionsnummer:
02 05 => 2.05 (PhyTHZ)
02 08 => 2.08 (immi)
03 0b => 3.11 (*****)
03 0f => 3.15 (toggle, godmorgon)
03 10 => 3.16 (belu ?)
Und das ist der Grund, warum bei PhyTHZ manche Daten fehlen, obwohl er 4.39 wie immi hat.

Es wäre schon interessant zu wissen, wie der Softwarestand (2.06, 2.36, 3.19, 4.19, 4.39, 5.19, 5.39), die Software-ID und die SW-Versionsnummer mit Datum aus der FE-Message zusammenhängen. Jedenfalls kann der Softwarestand zumindest bei neueren Modellen verstellt werden, wie belu es hier (http://forum.fhem.de/index.php/topic,13132.msg243071.html#msg243071)  demonstrierte. Daher ist es kein Hardware-Attribut, sondern eher eine Protokoll-Version, die z.B. am CAN-Bus unterstützt wird.

Gruß
toggle
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Januar 2015, 22:55:46
sDisplay  switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0

But just two icons are shown in display: compressor and DHW


insideTempRC: 23.1  worksperfectly, thanks a lot!
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2015, 23:08:13
Zitat von: willybauss am 30 Januar 2015, 22:55:46
sDisplay  switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0

But just two icons are shown in display: compressor and DHW

could be that you have not refreshed  sDisplay?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 30 Januar 2015, 23:12:23
Zitat von: toggle am 30 Januar 2015, 22:49:02
03 10 => 3.16 (belu ?)
this is the question
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 30 Januar 2015, 23:36:46
Zitat von: immi am 30 Januar 2015, 23:08:13
could be that you have not refreshed  sDisplay?
no, refreshed the same time as I watched the display

tested again:

switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0

while just the HC pump icon is visible



Should we wait for belu's or other results?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 09:31:47
Guten morgen, ich würde gerne helfen aber ich komme irgendwie nicht an die Rohdaten. Bei mir läuft Mythz und das verbindet sich auch sauber, ich komme aber nicht über console drauf um die Antwort zu erhalten kann mir jemand da vielleicht helfen?
Kann mir einer erklären was ich falsch mache?

Ich hab die THZ angeschlossen per USB

pi@raspberrypi /opt/fhem $ ls -l /dev/ttyUSB*
crw-rw---T 1 root dialout 188, 0 Jan 31 09:23 /dev/ttyUSB0
pi@raspberrypi /opt/fhem $


Ist also da.

define Mythz THZ /dev/ttyUSB0@115200

damit läuft es.

Jetzt hatte ich fhem beendet und getty auf den port beendet und dachte mir machst es per screen auf.

screen /dev/ttyUSB0 115200

kommt nix, screen prozesse wieder beendet, nix greif darauf zu, kermit getestet komm nicht drauf, kermit deinstalliert, jetzt hab ich minicom installiert configuriert versuche drauf zu zu greifen ist aber immer offline.

Ich sehe es doch richtig wenn ich da drauf bin müsste es doch laufen wie bei der installation beim heatpump monitor, ich sende ich ne 02 und müsste ne 10 als antwort erhalten. aber wenn ich offline bin kann ich auch nichts senden.
Will ja das eine Register auslesen. Habe mir heute vormittag auch nichts anderes vorgenommen.

Vielen Dank, ich stehe gerade irgendwie auf dem Schlauch.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 31 Januar 2015, 09:57:18
Zitat von: willybauss am 30 Januar 2015, 22:55:46
sDisplay  switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0
I forgot to mention that I used big endian byte order: 04 07 => 0x0407 (switchingProg=1, compressor=1, heatingHC=1, pumpHC=1)
Zitat von: immi am 30 Januar 2015, 23:12:23
this is the question
this is my expectation because he mentioned 3.16.

@belu
Das Kommunikationstiming ist zeitkritisch - manuelle Operationen sind nicht schnell genug. FHEM hat eine eingebaute Funktion, um Rohdaten zu dumpen - THZ_debugread(). Um die FE-Message zu lesen, musst bloß verbose auf 5 setzen und "get sFirmware-Id" ausführen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 10:04:49
@immi:

After having updated to v.0.129 I see tons of entries in the fhem.log file:

2015.01.31 04:59:59 3: THZ_Parsing: offset(80) + length(4) is longer then message : 'BDF4FFFEFEA4011B0000010D011F011600010001200000C80200000000D70000160000D90000001600'



"tons" means every 5 minutes = once per reading cycle
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 10:12:25
Zitat von: belu am 31 Januar 2015, 09:31:47
Guten morgen, ich würde gerne helfen aber ich komme irgendwie nicht an die Rohdaten. Bei mir läuft Mythz und das verbindet sich auch sauber, ich komme aber nicht über console drauf um die Antwort zu erhalten kann mir jemand da vielleicht helfen?
Ich habe Dein Problem noch nicht ganz verstanden. Kommst Du auf das Webinterface von fhem?
Wenn ja: sieh mal im Logfile fhem-[timestamp].log  nach (entweder übers Webinterface oder mit einem Texteditor). Dort sollte nach dem Neustart von FHEM stehen
2015.01.30 21:48:01 3: Opening Mythz device /dev/ttyUSB0
2015.01.30 21:48:02 3: Setting Mythz baudrate to 115200
2015.01.30 21:48:02 3: Mythz device opened


Auf welcher Plattform läuft Dein FHEM? Beim RaspberryPi gibt es bei mir gelegentlich Situationen, dass der USB-Port den Dienst versagt. Da hilft kein Reboot des Betriebssystems, sondern nur noch ein harter PowerCycle, also Betriebsspannung für 15 Sekunden abklemmen und neu starten. Falls Du USB-Hubs mit Spannungsversorgung dran hast müssen die USB-Kabel auch raus, sonst bekommt der Raspi darüber Spannung und läuft trotz abgezogenem Stromkabel weiter.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 10:22:59
Zitat von: toggle am 30 Januar 2015, 22:49:02
Sorry to disappoint you. Even if there may be some coincidences this it not the case.

Two more FE responses from THZ 404 SOL (5.39):
03 b1 83 f5 00 01 00 ** ** ** 00 06 67 71 03 0b 4e 6f 76 20 20 39 20 32 30 31 31 20
03 b1 83 f5 01 00 00 ** ** ** 00 06 67 71 03 0f 4d 61 72 20 31 34 20 32 30 31 34 20

** - es handelt sich um die Seriennummer der Hauptplatine (sollte man vielleicht nicht posten)
Blau ist vermutlich die Hardware-Variante:
49 - THZ 303 SOL (willybauss)
4A - THZ 403 SOL (immi, PhyTHZ)
71 - THZ 404 SOL (toggle, godmorgon, *****)

Und in rot eine weitere Variante der SW-Versionsnummer:
02 05 => 2.05 (PhyTHZ)
02 08 => 2.08 (immi)
03 0b => 3.11 (*****)
03 0f => 3.15 (toggle, godmorgon)
03 10 => 3.16 (belu ?)
Und das ist der Grund, warum bei PhyTHZ manche Daten fehlen, obwohl er 4.39 wie immi hat.

Es wäre schon interessant zu wissen, wie der Softwarestand (2.06, 2.36, 3.19, 4.19, 4.39, 5.19, 5.39), die Software-ID und die SW-Versionsnummer mit Datum aus der FE-Message zusammenhängen. Jedenfalls kann der Softwarestand zumindest bei neueren Modellen verstellt werden, wie belu es hier (http://forum.fhem.de/index.php/topic,13132.msg243071.html#msg243071)  demonstrierte. Daher ist es kein Hardware-Attribut, sondern eher eine Protokoll-Version, die z.B. am CAN-Bus unterstützt wird.

Gruß
toggle

@ Toggle,

habe es nun verstanden und du hattest recht.

03B183F5000100 XX XX XX 000667710310104465632031302032303134201003

Antwort ist Date: DEC 10 2014

@Willy,

keine Ahnung, hab ne Raspberry aber per Mythz komm ich ja drauf, mit Verbose 5 komme ich ja auch so an die Daten. Ich war am überlegen mir ne BananaPI zu zu legen, hat mehr Power, bei gleichem Verbrauch. Denke dann ist das mit den Plots auch einfacher, was hälst davon?

LG

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 10:33:33
Zitat von: willybauss am 30 Januar 2015, 22:55:46
sDisplay  switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0

But just two icons are shown in display: compressor and DHW


insideTempRC: 23.1  worksperfectly, thanks a lot!

Also mein Feedback von sDisplay.

switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0

Heizung ist aus, das einzige was aktuell aktiv ist sollte diese Schaltprogramm aktiv diese Sanduhr oder 2 Dreiecke, also das klappt so nicht so ganz richtig.

LG
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 31 Januar 2015, 10:38:59
Meine Vermutung bzgl. der Modell-ID ist wohl nicht ganz richtig. Belu hat auch 0x71, aber eine 304 SOL. Vielleicht ist es der Hardwarestand der Hauptplatine.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 10:46:40
@Toggle,

also das einzige was wichtig ist das ist das Datum der Software, das hat mir auch der Stiebel Eltron Monteur gesagt, diese Firmware ID 5.19 5.39 hat nur grob etwas zu sagen, diese beiden Firmware versionen sind gleich nur je nach Modell ist das eine oder das andere aktiv. Die Anlagen unterscheiden sich ja nicht wirklich außer in der größe der Wärmepumpe, hatte meine Anlage mal umgestellt und ihr gesagt du bist eine THZ 404 SOL hatte dann direkt Softwarestand 5.39 als ich zurück gestellt hatte auf die THZ 304 SOL hatte ich die 5.19.

Ich denke wir werden genau die selbe Platine drin haben, die ist denke ich bei allen neueren Geräten gleich. Meine Anlage ist vom März 2012. Hatte letztens halt einen Monteur da der mir die letzte Firmwareversion drauf gemacht hat. Er meinte es wäre 5.19 316 Dez 10 2014, habe ich auch so in der Update Software gesehen.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 10:47:09
Zitat von: belu am 31 Januar 2015, 10:22:59
keine Ahnung, hab ne Raspberry aber per Mythz komm ich ja drauf, mit Verbose 5 komme ich ja auch so an die Daten. Ich war am überlegen mir ne BananaPI zu zu legen, hat mehr Power, bei gleichem Verbrauch. Denke dann ist das mit den Plots auch einfacher, was hälst davon?
Gibt es dann aktuell überhaupt noch ein Problem?

Bevor Du auf BananaPi umsteigst logge Dich erst mal auf den Raspi ein und starte im Terminal ein "top". Dann wirst du wahrscheinlich sehen, das der Prozessor nur minimal belastet ist. Bei mir dümpelt er bei weniger als 5% Last herum, davon 0,7% perl. Der Raspi ist zumindest bei mir kein Flaschenhals.

Wenn Du mehr Last siehst (läuft da sonst noch was größeres außer fhem?) finde heraus, wer dafür zuständig ist und versuche dort, das Problem zu beheben.

> ...  dann ist das mit den Plots auch einfacher ...
Was ist Dein Problem bei den Plots?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 31 Januar 2015, 10:49:42
Zitat von: belu am 31 Januar 2015, 10:33:33
switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0
Ein Auszug aus dem Logfile für "get sDisplay" mit verbose=5 wäre hilfreich.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 10:57:01
Zitat von: willybauss am 31 Januar 2015, 10:47:09
Gibt es dann aktuell überhaupt noch ein Problem?

Bevor Du auf BananaPi umsteigst logge Dich erst mal auf den Raspi ein und starte im Terminal ein "top". Dann wirst du wahrscheinlich sehen, das der Prozessor nur minimal belastet ist. Bei mir dümpelt er bei weniger als 5% Last herum, davon 0,7% perl. Der Raspi ist zumindest bei mir kein Flaschenhals.

Wenn Du mehr Last siehst (läuft da sonst noch was größeres außer fhem?) finde heraus, wer dafür zuständig ist und versuche dort, das Problem zu beheben.

> ...  dann ist das mit den Plots auch einfacher ...
Was ist Dein Problem bei den Plots?

@Willy

das war damals eine von den ersten 1000 RaspberryPI hab damals preorder gemacht und das ist halt die ganz alte kleine, die Schreddert immer am Limit, hab da eigentlich nur Mini Debian drauf ProFtpd FHEM Apache.

Wenn ich gegen abend die Logfiles aktualisiere dauert der aufruf der Plots sicherlich so 2 Minuten. In der Zeit habe ich aber auch ne Load von 2,5

Allein wenn ich nun das Loglevel auf Verbose 5 gemacht habe und mit Nano in diese Datei gehen um sie auszuwerten, weil die Output von tail leider zu gering ist bekomme ich graue Haare.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 11:02:13
@toggle

jaja spart euch manpages tail, habe schon :D
Hab es auf 30 Lines erweitert nun kann man mit arbeiten.


2015.01.31 10:59:27 4: HTTP FHEMWEB:192.168.1.136:51763 GET /fhem&room=Heizung_Plot&cmd=Get+Mythz+sDisplay
2015.01.31 10:59:27 5: Cmd: >Get Mythz sDisplay<
2015.01.31 10:59:27 5: THZ_Get: Try to get 'sDisplay'
2015.01.31 10:59:27 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.01.31 10:59:27 5: Mythz sending 02
2015.01.31 10:59:27 5: SW: 02
2015.01.31 10:59:27 5: Mythz start Funktion THZ_ReadAnswer
2015.01.31 10:59:27 5: THZ_ReadAnswer: uc unpack: '10'
2015.01.31 10:59:27 5: Mythz sending 0100820A01761003
2015.01.31 10:59:27 5: SW: 0100820A01761003
2015.01.31 10:59:27 5: Mythz start Funktion THZ_ReadAnswer
2015.01.31 10:59:27 5: THZ_ReadAnswer: uc unpack: '10'
2015.01.31 10:59:27 5: Mythz start Funktion THZ_ReadAnswer
2015.01.31 10:59:27 5: THZ_ReadAnswer: uc unpack: '02'
2015.01.31 10:59:27 5: Mythz sending 10
2015.01.31 10:59:27 5: SW: 10
2015.01.31 10:59:27 5: Mythz start Funktion THZ_ReadAnswer
2015.01.31 10:59:27 5: THZ_ReadAnswer: uc unpack: '0100830A017600011003'
2015.01.31 10:59:27 5: Mythz sending 10
2015.01.31 10:59:27 5: SW: 10
2015.01.31 10:59:27 5: Parse message: 830A01760001
2015.01.31 10:59:27 5: Message length: 12
2015.01.31 10:59:27 5: Triggering Mythz (0 changes)
2015.01.31 10:59:27 4: 14176:FHEMWEB:192.168.1.136:51763: /fhem&room=Heizung_Plot&cmd=Get+Mythz+sDisplay / RL:873 / text/html; charset=UTF-8 / Content-Encoding: gzip

es ist nur Schaltprogramm aktiv

Output switchingProg: 0 compressor: 1 heatingHC: 1 heatingDHW: 1 boosterHC: 1 filterBoth: 1 ventStage: 0 pumpHC: 0 defrost: 0 filterUp: 0 filterDown: 0
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 11:03:36
@belu:
dann würde ich erst mal nen Versuch mit dem Raspi B+ machen. Wie gesagt: keinerlei Lastprobleme bei mir (B-Version). Wohin schreibst Du denn die Daten? Die sollten auf jeden Fall außerhalb der SD-Karte liegen. Sonst hast du langfristig ein Problem, da die Karte nur eine begrenzte anzahl Schreibzyklem mitmacht.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: toggle am 31 Januar 2015, 11:09:52
@immi
The offset for sDisplay is not correct - it should be 8-11 instead of 4-7 (830A01760001).

Zitat"0A0176Dis" => [[" switchingProg: ",   11, 1, "bit0", 1],     [" compressor: ",   11, 1, "bit1", 1],
         [" heatingHC: ",      11, 1, "bit2", 1],     [" heatingDHW: ",   10, 1, "bit0", 1],
         [" boosterHC: ",      10, 1, "bit1", 1],     [" filterBoth: ",   9, 1, "bit0", 1],
         [" ventStage: ",      9, 1, "bit1", 1],     [" pumpHC: ",      9, 1, "bit2", 1],
         [" defrost: ",      9, 1, "bit3", 1],     [" filterUp: ",      8, 1, "bit0", 1],
         [" filterDown: ",   8, 1, "bit1", 1]
         ],
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 31 Januar 2015, 11:17:39
@Willy

also die Daten schreib ich nach /mnt/fhem/log/ das ist natürlich auf der SD Karte. Hatte zu anfang mal überlegt ob ich ne Ramdisk mache, aber das ding hat nur 256 mb und nunja die sind halt immer voll belegt. Ganz nebenbei sind sie halt weg wenn man sie Rebootet und es auf der Ramdisk war.
Die Lösung ist nicht ganz optimal, aktuell vom Januar hab ich 8,7mb Daten. Wenn ich einen Plott aufruf geht er die ja durch.
Also 256 mb der alte 700 mhz Singlecore.... Sprechen dafür sie einfach mal zu ersetzen.
Hab ihn jetzt einfach mal übertaktet, vielleicht bringt das was...
Der Ram ist ja geteilt für CPU und GPU hab mal GPU nur noch auf 16 mb gesetzt, ist ja eh kein Display und X drauf...



Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 11:29:51
Zur Abwechslung mal eine praktische Anwendung der ganzen Mythz-Datenloggerei: ich habe aus den geloggten Daten ein neues Diagramm erstellt, um die Ursachen für Beginn/Ende der Heiztakte zu ergründen. Man sieht im angehängten ScreenDump, dass geheizt wird, wenn die Hysterese (-4K, grüne Kurve) unterschritten wird. Das Ende des Heiztaktes wird durch den Integralwert veruracht (eingestellter Integralwert ist 200, rote Kurve). Das hilft mir beim einstellen der Hysteresen und Integralwerte.

Ein kleines Darstellungsproblem gibt es aber noch:

@immi:
Do you know how I can achieve sGlobal and sHC1 to be in sync, means they should always be read the same time (+/- a few seconds). Currently the upper plot shows end of heating cycle at ~8:50 while the lower plot shows a max. integral value at ~8:45. I assume that's caused by a time offset between reading sGlobal and sHC1. Of course this effect could be limited by reading the data more often, but I'm already at >10MB per month, using 5 minute reading intervals. This shouldn't increase to 50MB by reading every minute. Otherwise creating plots takes too much time.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 11:36:01
Zitat von: belu am 31 Januar 2015, 11:17:39
also die Daten schreib ich nach /mnt/fhem/log/ das ist natürlich auf der SD Karte.
Bei mir liegen die Daten auf /mnt/fhem/log. Das ist ein gemounteter Share meines NAS. Glücklicherweise habe ich bei meinen WD MybookLive /  WD MybookLiveDuo Zugriff auf die Linuxebene. Dadurch wird ein solcher Mount recht einfach. Aber man braucht halt einen Raspi mit LAN-Port dafür.
Der Zugriff auf die Logfiles von Windows aus geschieht dann einfach per Netzlaufwerk V:\fhem\log. Man sollte beim angucken der Logs halt nicht versehentlich speichern, weil inzwischen ja schon wieder neue Daten dazu geschrieben wurden.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 31 Januar 2015, 16:35:05
Zitat von: willybauss am 31 Januar 2015, 11:29:51
@immi:
Do you know how I can achieve sGlobal and sHC1 to be in sync, means they should always be read the same time (+/- a few seconds). Currently the upper plot shows end of heating cycle at ~8:50 while the lower plot shows a max. integral value at ~8:45. I assume that's caused by a time offset between reading sGlobal and sHC1. Of course this effect could be limited by reading the data more often, but I'm already at >10MB per month, using 5 minute reading intervals. This shouldn't increase to 50MB by reading every minute. Otherwise creating plots takes too much time.
Hi
Interesting plot,
The first thing is to have the same read interval. Then it should not drift more than 0.2s  for each read.
For data size, please consider that new methods have been (or are just going to be) released from Boris.
You can now filter very well the data before it is logged.
I am short on time this week. This is why v0129 has not been tested or uploaded to the repository.
Actually I am working on 0.130 with a new supported parameter (maybe monday)
sorry
immi


Hi Toggle
I will fix your suggestion.

Hi Belu
thanks for sharing your FE
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 16:39:11
Zitat von: immi am 31 Januar 2015, 16:35:05
Actually I am working on 0.130 with a new supported parameter (maybe monday)
Hi immi,
would it be possible to also have a fix for this issue (http://forum.fhem.de/index.php/topic,13132.msg254403.html#msg254403) in 0.130?
Willy
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 31 Januar 2015, 16:43:46
Zitat von: immi am 31 Januar 2015, 16:35:05
For data size, please consider that new methods have been (or are just going to be) released from Boris.
OK, let me see what happens. Do you have a link to the topic?


but: sGlobal and sHC1 are the ones needing most of the space, so it might be impossible to e.g. skip data sets consisting of identical values only. Since there are so many different values inside one reading, the chance of having identical rows is pretty small.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 16:57:01
Zitat von: willybauss am 31 Januar 2015, 16:43:46
but: sGlobal and sHC1 are the ones needing most of the space, so it might be impossible to e.g. skip data sets consisting of identical values only. Since there are so many different values inside one reading, the chance of having identical rows is pretty small.
actually not easy; you could split sGlobal and save often only what you need... or go for database, which is now better supported for plots.
Please keep on sharing your improvements in your plots. Many users make good use of it. We should also update the wiki.

Boris´s patch is not a final solution; but maybe helps
http://forum.fhem.de/index.php/topic,31856.0.html

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 17:00:23
v0.130 uploaded; tomorrow you can update
changelog:
- bugfix http://forum.fhem.de/index.php/topic,13132.msg254403.html#msg254403
- bugfix http://forum.fhem.de/index.php/topic,13132.msg254437.html#msg254437
- firmware-id  contains new features e.g. HW: 74 SW: 2.08 Date: MAR 9 2011
- new parameter p99RoomThermCorrection implemented
- THZ_PrintcurveSVG is now influenced by p99RoomThermCorrection, hope that fixing Rene´s problem, nobody else has a side-effect while plotting the heat-curve.

immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Februar 2015, 17:32:58
Super IMMI,

checkt, works great, i make a new addon for display the display status in browser...
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 18:31:10
Zitat von: belu am 01 Februar 2015, 17:32:58
Super IMMI,
checkt, works great, i make a new addon for display the display status in browser...
share it, screenshot and code for reuse.
Do not forget that it must be refreshed, otherwise it makes no sense.
Here it could be more interesing to refresh it from the webpage, instead of refreshing periodically with an interval...
de gustibus non disputandum est
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 18:41:12
 
Zitat von: immi am 01 Februar 2015, 16:57:01
actually not easy; you could split sGlobal and save often only what you need... or go for database, which is now better supported for plots.
Please keep on sharing your improvements in your plots. Many users make good use of it. We should also update the wiki.

Boris´s patch is not a final solution; but maybe helps
http://forum.fhem.de/index.php/topic,31856.0.html (http://forum.fhem.de/index.php/topic,31856.0.html)

immi


> "ein Event wird NUR bei Aenderung UND hoechstens alle X Sekunden erzeugt."

That would be my favorite. Currently eventOnChangeReading tends to increase the amount of data, since  "hoechstens alle X Sekunden" is missing.

"Split sGlobal and save often only what you need" doesn't help, since  What I currently prefer in tracking the data of my photovoltaic energy is, to modify the reading intervals based on a condition (here: day/night mode):

+*{sunrise_rel("REAL",-3600)} set PV_Zaehler INTERVAL 300
+*{sunset_rel("REAL",+1800)} set PV_Zaehler INTERVAL 3600


Resaon for having readings during night at all is, that it needs a reading to activate the change of interval.
It could be handled similarly in case of Mythz, e.g. log in shorter intervals as soon as integral value comes close to its limit. But it would make the logging logic rather complex.

A year ago I tried to use dblog instead of filelog. It turned out that it needs same amount of disk space but is much less user friendly: In case of a crash I simply need a text editor to check the log files. While debugging a not understood behavior of my THZ I simply can crawl through the data very easy.

> Please keep on sharing your improvements in your plots. Many users make good use of it. We should also update the wiki.
Looks like most users here are concentrating on logging more and more data in more detailed way. Is this really the goal? My goal is more in the range of understanding the THZ and get help to improve the parameters in order to save money and have better climate during whole year. Maybe we meed to open a different thread for that topic sooner or later, to not mix up both interrests.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 18:44:20
Zitat von: belu am 01 Februar 2015, 17:32:58
Super IMMI,

checkt, works great, i make a new addon for display the display status in browser...
Would be nice to show the same icons in THZ dashboard (http://www.fhemwiki.de/wiki/Datei:Dash.jpg) than the ones on the display.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 19:06:34
Zitat von: willybauss am 01 Februar 2015, 18:41:12
Looks like most users here are concentrating on logging more and more data in more detailed way. Is this really the goal? My goal is more in the range of understanding the THZ and get help to improve the parameters in order to save money and have better climate during whole year. Maybe we meed to open a different thread for that topic sooner or later, to not mix up both interrests.
My goal is that people lean the potential of fhem, and stop buying closed source "plug&play" cloud solution.
I find fhem a good logging tool. But I find that the superiority of FHEM comes from the integration and control of different devices.
But people are lazy and need some motivation at the beginning.
Zitat
Maybe we meed to open a different thread for that topic sooner or later, to not mix up both interrests.
Maybe we should close this topic in Codeschnipsel and start something in Heizungssteuerung/Raumklima.
Nevertheless it is important a clear Object/betreff.
Bundling all in one thread has a clear advantage for the newbie to find information and for me to stay updated without reading the whole forum.
If the question is only front-end related, it should be posted in front-end section, in which front-end expert can answer.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 19:15:40
Zitat von: immi am 01 Februar 2015, 19:06:34
Maybe we should close this topic in Codeschnipsel and start something in Heizungssteuerung/Raumklima.
Nevertheless it is important a clear Object/betreff.
I agree and will start an initial post with a summary of my current knowledge soon. Do you have a suggestion for the ideal Betreff?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Februar 2015, 19:27:38
@Willy

Ich finde die Idee das Logging in eine Datenbank zu packen wesentlich besser. Die Performence der Plots sollte das verdreifachen.
Das mit dem Display über werde ich die Woche mal angehen. Bin mir noch nicht sicher wie ich es realisiere. Einmal die aktuallisierung sollte gemacht werden mit einem Refresh der Seite.
Mal schauen.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 19:39:42
Zitat von: belu am 01 Februar 2015, 19:27:38
Die Performence der Plots sollte das verdreifachen.
Vermutest du das oder hast Du es getestet?
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 19:51:21
Zitat von: willybauss am 01 Februar 2015, 19:15:40
I agree and will start an initial post with a summary of my current knowledge soon. Do you have a suggestion for the ideal Betreff?
Hi Willy
thanks it would be great.
We could start with something like
THZ Tecalor (LWZ Stiebel Eltron) module support 
and
THZ Tecalor (LWZ Stiebel Eltron) heatpump optimization, experience exchange


Hi Heiner
can you close this 3D with as last post a link to the 3d of Willy?
thanks
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: belu am 01 Februar 2015, 19:51:38
Ich hatte früher mal mehr mit Datenbanken zu tun. Der Unterschied vom lesen einer CSV direkt oder von einer MySQL Datenbank ist das dreifache. MySQL ist da wirklich super schnell
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 20:02:00
Zitat von: belu am 01 Februar 2015, 19:51:38
Ich hatte früher mal mehr mit Datenbanken zu tun. Der Unterschied vom lesen einer CSV direkt oder von einer MySQL Datenbank ist das dreifache. MySQL ist da wirklich super schnell
So kenne ich das auch. Der Test in fhem hat mich ernüchtert.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: willybauss am 01 Februar 2015, 20:03:54
Zitat von: immi am 01 Februar 2015, 19:51:21
We could start with something like
THZ Tecalor (LWZ Stiebel Eltron) module support 
and
THZ Tecalor (LWZ Stiebel Eltron) heatpump optimization, experience exchange
Sounds good. I can clearly support the optimazation topic. Module support needs support from others (e.g. you) as well.
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: andre.k am 01 Februar 2015, 20:10:24
Zitat von: belu am 01 Februar 2015, 19:27:38

Das mit dem Display über werde ich die Woche mal angehen. Bin mir noch nicht sicher wie ich es realisiere. Einmal die aktuallisierung sollte gemacht werden mit einem Refresh der Seite.
Mal schauen.

Hallo,

ich habe mir auch gerade ein kleines Statusdisplay in Form einer readingsGroup gebaut. Vielleicht kann das als Anregung dienen. Alle Statusinfos kommen aus dem THZ-Reading sGlobal. Um die Werte einzeln verarbeiten zu können, habe ich die Zeichenkette wie folgt zerlegt:
attr myWP userReadings PumpeDHW:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[25]}, PumpeHC:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[27]}, PumpeSol:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[29]}, Compress:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[31]}, Boost3:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[33]}, Boost1:sGlobal {(split ' ',ReadingsVal("myWP","sGlobal",0))[37]}
Dann kann man die 5 Werte in einer readingsGroup einbinden:
define rg_thz_stat readingsGroup myWP:<Heizkreispumpe>,PumpeHC\
myWP:<Warmwasserpumpe>,PumpeDHW\
myWP:<Solarpumpe>,PumpeSol\
myWP:<Nacherwärmung_Stufe1>,Boost1\
myWP:<Nacherwärmung_Stufe3>,Boost3\
myWP:<Verdichter>,Compress
attr rg_thz_stat alias Status
attr rg_thz_stat group THZ-Status
attr rg_thz_stat nonames 1
attr rg_thz_stat valueIcon {'PumpeHC.1'=>'sani_pump@red','PumpeHC.0'=>'sani_pump', 'PumpeDHW.1'=>'sani_pump@red', 'PumpeDHW.0'=>'sani_pump', 'PumpeSol.1'=>'sani_pump@red','PumpeSol.0'=>'sani_pump', 'Compress.1'=>'sani_garden_pump@red','Compress.0'=>'sani_garden_pump', 'Boost1.1'=>'sani_heating_boost@red','Boost1.0'=>'sani_heating_boost', 'Boost3.1'=>'sani_heating_boost@red', 'Boost3.0'=>'sani_heating_boost'}

Die Icons habe ich mir aus dem FHEM-Standard zusammengesucht. Könnt Ihr nach eigenem Geschmack anpassen. Die Farbe der Icons ist grün bzw. weiss, je nach style und wird rot, wenn der Status den Wert 1 hat. Die Werte werden automatisch im Browser aktualisiert, wenn sGlobal neu gelesen wird. Die readingsGroup kann auch einfach in einem Dashboard benutzt werden. Und so sieht das aus wenn's fertig ist.

Andre
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: immi am 01 Februar 2015, 20:31:13
Zitat von: willybauss am 01 Februar 2015, 20:03:54
Sounds good. I can clearly support the optimazation topic. Module support needs support from others (e.g. you) as well.
I think we all can contribute in both as long as we find time for it.
immi
Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 01 Februar 2015, 20:40:19
Hi, das Thema wird nun hier geschlossen.

Willy wird in kurze im Bereich Heizungssteuerung ein neues Thema unter den Namen

THZ Tecalor (LWZ Stiebel Eltron) module support
Und
THZ Tecalor (LWZ Stiebel Eltron) heatpump optimization, experience exchange

Öffnen.

Titel: Antw:THZ / LWZ Tecalor Stiebel Eltron Heizung
Beitrag von: Heiner am 02 Februar 2015, 20:22:09
Und hier der exakte Link...

THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
http://forum.fhem.de/index.php/topic,33211.0.html