THZ / LWZ Tecalor Stiebel Eltron Heizung

[micomat]

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

[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

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! 

[immi]

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

[micomat]

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

[immi]

INTERNAL version is a good idea, I will see what can I do

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

Code Auswählen Erweitern


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

[micomat]

Great thank You so much!
will test and update the Wiki soon


markus

[houseowner123]

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.

[micomat]

if you send me the exact details of the sensor, sure i can add the info to the wiki

[belu]

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

[willybauss]

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?

Does anybody have pictures from ISG Web.

You didn't try using google yet, right?   

304 have a rel huminity Fan correction, Can u bring the Parameter in thz.pm?

What does this correction do in detail?

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

[immi]

Code is freeware - just take and improve ...

willy
small errata. code is open source as defined by GLP.
but my message is the same.

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

[micomat]

Code Auswählen Erweitern


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.

[immi]

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

Code Auswählen Erweitern


define FileLog_Mythz FileLog /opt/fhem/log/Mythz-%Y-%m.log Mythz:s.*

[micomat]

thanks will try and come back to you

[immi]

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