THZ / LWZ Tecalor Stiebel Eltron Heizung

[immi]

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

Code Auswählen Erweitern

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

[micomat]

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

[willybauss]

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:

   
• inside_temp > outside_temp AND inside_temp > p02RoomTempNightHC1 AND  window in sleeping room open => passive cooling = 1
• inside_temp > outside_temp AND inside_temp > p02RoomTempNightHC1 AND   window in sleeping room closed but different window open => passive cooling = 2
• else  passive cooling = 0

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.

[willybauss]

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

Code Auswählen Erweitern

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.

[willybauss]

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

Code Auswählen Erweitern


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

shouldn't it?

Markus

not really. Answer in this case

myDbLog: unknown attribute DbLogExclude. Type 'attr myDbLog ?' for a detailed list.

Commandref says

A 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?

[willybauss]

regarding to DbLog:


looks like an error in Commandref's example. Trying

Code Auswählen Erweitern

set Mythz DbLogExclude allFB,timedate,history
ends up in

Code Auswählen Erweitern

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.

[willybauss]

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

Code Auswählen Erweitern

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:

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


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)

[micomat]

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

[willybauss]

sounds like same issue as I had here:

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

Code Auswählen Erweitern


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

[micomat]

corrected the reading, will have an eye on it

thanks
markus

[immi]

Hi
I played around with dblog.
The standard installation of dblog restricts the reading to 32 char and event 512 char

Code Auswählen Erweitern

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

Code Auswählen Erweitern

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

Code Auswählen Erweitern

attr global userattr DbLogExclude devStateIcon devStateStyle fp_Pianoterra fp_Secondopiano fp_primopiano icon room_map sortby structexclude webCmd.....

immi

[willybauss]

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.

Concerning blacklisting in dblog, the right sysntax is

Code Auswählen Erweitern

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:

Code Auswählen Erweitern

define myDbLog DbLog /mnt/fhem/db.conf .*:.*(dhw_temp|Rel_humidity|flow_temp|return_temp|inside_temp|outside_temp).*

There is a trick which I did not find in any documentation; you have to add  DbLogExclude to the userattributes...

Code Auswählen Erweitern

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?

[willybauss]

forget my last sentence. I managed it meanwhile. fhem.cfg now looks like

Code Auswählen Erweitern

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!

[immi]

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

[willybauss]

ok, will do it this evening