THZ / LWZ Tecalor Stiebel Eltron Heizung

[willybauss]

2nd experiment result:
last10errors:

Code Auswählen Erweitern

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

[immi]

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

[willybauss]

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 

I 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 ...

[immi]

Hi willy
please test v0075, download it directly or update tomorrow.

immi

[willybauss]

using v0075 I tried

Code Auswählen Erweitern

attr Mythz interval_last10errors 120

without success:

Code Auswählen Erweitern

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?

[immi]

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

[willybauss]

... after update you restarted fhem

that's the topic I missed. Will try again this evening.

[micomat]

working here also
added v0.075 info to the wiki pages

[willybauss]

 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:

Code Auswählen Erweitern

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:

Code Auswählen Erweitern

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.

[immi]

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

[willybauss]

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:

Code Auswählen Erweitern

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.

[immi]

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

[micomat]

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

[immi]

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

Code Auswählen Erweitern

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

[micomat]

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

Code Auswählen Erweitern


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

Code Auswählen Erweitern


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