THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.

[immi]

Hi immi , I just run the commands p08 and p09 . The appendix is the log file with verbose 5.

Peter, you do not have problem with writing; you have problems with every reading also.
Andre, I hope your logfile does not look the same.

I just uploaded v0136 with some waittimes for old firmwares.
immi

[andre.k]

immi, my logfile looks ok.

Code Auswählen Erweitern

2015.02.22 20:18:27 5: THZ_Get: Try to get 'p09FanStageStandby'
2015.02.22 20:18:27 5: THZ_Get: Try to get 'p01-p12'
2015.02.22 20:18:27 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.02.22 20:18:27 5: SW: 02
2015.02.22 20:18:27 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:18:27 5: THZ_ReadAnswer: uc unpack: '10'
2015.02.22 20:18:27 5: SW: 010018171003
2015.02.22 20:18:27 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:18:27 5: THZ_ReadAnswer: uc unpack: '10'
2015.02.22 20:18:27 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:18:27 5: THZ_ReadAnswer: uc unpack: '02'
2015.02.22 20:18:27 5: SW: 10
2015.02.22 20:18:27 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:18:27 5: double read 1 activated 01
2015.02.22 20:18:27 5: double read 1 result with buf1  0100
2015.02.22 20:18:27 5: double read 2 activated 0100
2015.02.22 20:18:27 5: double read 2 result with buf1  0100B8
2015.02.22 20:18:27 5: double read 3 activated 0100B8
2015.02.22 20:18:27 5: double read 3 result with buf1  0100B81700C8
2015.02.22 20:18:27 5: double read 4 activated 0100B81700C8
2015.02.22 20:18:27 5: double read 4 result with buf1  0100B81700C800BE
2015.02.22 20:18:27 5: double read 5 activated 0100B81700C800BE
2015.02.22 20:18:27 5: double read 5 result with buf1  0100B81700C800BE00
2015.02.22 20:18:27 5: double read 6 activated 0100B81700C800BE00
2015.02.22 20:18:27 5: double read 6 result with buf1  0100B81700C800BE00A001
2015.02.22 20:18:27 5: double read 7 activated 0100B81700C800BE00A001
2015.02.22 20:18:27 5: double read 7 result with buf1  0100B81700C800BE00A001C20190
2015.02.22 20:18:27 5: double read 8 activated 0100B81700C800BE00A001C20190
2015.02.22 20:18:27 5: double read 8 result with buf1  0100B81700C800BE00A001C201900064
2015.02.22 20:18:27 5: double read 9 activated 0100B81700C800BE00A001C201900064
2015.02.22 20:18:27 5: double read 9 result with buf1  0100B81700C800BE00A001C20190006402
2015.02.22 20:18:27 5: double read 10 activated 0100B81700C800BE00A001C20190006402
2015.02.22 20:18:27 5: double read 10 result with buf1  0100B81700C800BE00A001C20190006402010000
2015.02.22 20:18:27 5: double read 11 activated 0100B81700C800BE00A001C20190006402010000
2015.02.22 20:18:27 5: double read 11 result with buf1  0100B81700C800BE00A001C20190006402010000E601
2015.02.22 20:18:27 5: double read 12 activated 0100B81700C800BE00A001C20190006402010000E601
2015.02.22 20:18:27 5: double read 12 result with buf1  0100B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:18:27 5: double read 13 activated 0100B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:18:27 5: double read 13 result with buf1  0100B81700C800BE00A001C20190006402010000E601D6021003
2015.02.22 20:18:27 5: THZ_ReadAnswer: uc unpack: '0100B81700C800BE00A001C20190006402010000E601D6021003'
2015.02.22 20:18:27 5: SW: 10
2015.02.22 20:18:27 5: Parse message: B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:18:27 5: Message length: 44
2015.02.22 20:19:56 5: THZ_Get: Try to get 'p01RoomTempDay'
2015.02.22 20:19:56 5: THZ_Get: Try to get 'p01-p12'
2015.02.22 20:19:56 5: THZ_Get_Comunication: Check if port is open. State = '(opened)'
2015.02.22 20:19:56 5: SW: 02
2015.02.22 20:19:56 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:19:56 5: THZ_ReadAnswer: uc unpack: '10'
2015.02.22 20:19:56 5: SW: 010018171003
2015.02.22 20:19:56 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:19:56 5: THZ_ReadAnswer: uc unpack: '10'
2015.02.22 20:19:56 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:19:56 5: THZ_ReadAnswer: uc unpack: '02'
2015.02.22 20:19:56 5: SW: 10
2015.02.22 20:19:56 5: myWP start Funktion THZ_ReadAnswer
2015.02.22 20:19:56 5: double read 1 activated 01
2015.02.22 20:19:56 5: double read 1 result with buf1  0100
2015.02.22 20:19:56 5: double read 2 activated 0100
2015.02.22 20:19:56 5: double read 2 result with buf1  0100B817
2015.02.22 20:19:56 5: double read 3 activated 0100B817
2015.02.22 20:19:56 5: double read 3 result with buf1  0100B81700C800
2015.02.22 20:19:56 5: double read 4 activated 0100B81700C800
2015.02.22 20:19:56 5: double read 4 result with buf1  0100B81700C800BE00
2015.02.22 20:19:56 5: double read 5 activated 0100B81700C800BE00
2015.02.22 20:19:56 5: double read 5 result with buf1  0100B81700C800BE00A001C2
2015.02.22 20:19:56 5: double read 6 activated 0100B81700C800BE00A001C2
2015.02.22 20:19:56 5: double read 6 result with buf1  0100B81700C800BE00A001C20190
2015.02.22 20:19:56 5: double read 7 activated 0100B81700C800BE00A001C20190
2015.02.22 20:19:56 5: double read 7 result with buf1  0100B81700C800BE00A001C2019000
2015.02.22 20:19:56 5: double read 8 activated 0100B81700C800BE00A001C2019000
2015.02.22 20:19:56 5: double read 8 result with buf1  0100B81700C800BE00A001C2019000640201
2015.02.22 20:19:56 5: double read 9 activated 0100B81700C800BE00A001C2019000640201
2015.02.22 20:19:56 5: double read 9 result with buf1  0100B81700C800BE00A001C20190006402010000
2015.02.22 20:19:56 5: double read 10 activated 0100B81700C800BE00A001C20190006402010000
2015.02.22 20:19:56 5: double read 10 result with buf1  0100B81700C800BE00A001C20190006402010000E6
2015.02.22 20:19:56 5: double read 11 activated 0100B81700C800BE00A001C20190006402010000E6
2015.02.22 20:19:56 5: double read 11 result with buf1  0100B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:19:56 5: double read 12 activated 0100B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:19:56 5: double read 12 result with buf1  0100B81700C800BE00A001C20190006402010000E601D6021003
2015.02.22 20:19:56 5: THZ_ReadAnswer: uc unpack: '0100B81700C800BE00A001C20190006402010000E601D6021003'
2015.02.22 20:19:56 5: SW: 10
2015.02.22 20:19:56 5: Parse message: B81700C800BE00A001C20190006402010000E601D602
2015.02.22 20:19:56 5: Message length: 44

The reading p09FanStageStandby should be "0", but is not returned.
p01RoomTempDay works fine.

[immi]

Hi Andre
nice log, I feel better.
I just simulated B81700C800BE00A001C20190006402010000E601D602:
it is not a bug, it is a feature of fhem
p09FanStageStandby  is "0" and "0" is returned
   
p09FanStageStandby 0   2015-02-22 20:46:50

you just do not see it as answer in the frontend
this affects all versions and all gets which return "0".
immi

[andre.k]

Hi immi,
then I am reassured

Would it be helpful having an addidional Log3 message in THZ_Get(), if the get is from memory?

Andre

[immi]

Hi immi,
then I am reassured

Would it be helpful having an addidional Log3 message in THZ_Get(), if the get is from memory?

I added it 10 min before for debugging your message

[peter456]

Peter, you do not have problem with writing; you have problems with every reading also.
Andre, I hope your logfile does not look the same.

I just uploaded v0136 with some waittimes for old firmwares.
immi

Hi immi,
what can I do to eliminate the Problems with reading from LWZ?
In my opinion, the monitoring of my LWZ works quite well.

[immi]

I just uploaded v 0.137
changelog
heatcurve has been improved:
- 2 curves are now displayed: one with insideTemp influence (green), the other without(blue).
- heatcurve should support also old firmware (please Andre test it)

@Peter: I am happy if you are happy with the THZ module. Let Andre make the tests for your older firmware.

[mlb]

- 2 curves are now displayed: one with insideTemp influence (green), the other without(blue).

I think autoscaling does not work after adding second curve.

[immi]

I think autoscaling does not work after adding second curve.

fixed and uploaded

p.s are you sure you need such a high blue line. Don´t you think your p13GradientHC1 and p14LowEndHC1 are too high?
If I were you, I would slowly reduce to
p13GradientHC1           -->  0.35
p14LowEndHC1            --> 3 K
p15RoomInfluenceHC1 --> 60 %
maybe later you can reduce more: mine are much lower
please keep on the discussion in http://forum.fhem.de/index.php/topic,33452.0.html

[willybauss]

p.s are you sure you need such a high blue line. Don´t you think your p13GradientHC1 and p14LowEndHC1 are too high?

Unexpected but positive side effect of adding the second curve: now it helps to unmask wrong settings  .

[mlb]

Yes they are likely too high The reason is my main heating source is fireplace connected to house heating system and I have been using LWZ just for DHW and absences - and so I was really looking forward to analyze graphs from FHEM to understand if and how should I use LWZ for heating... That's why I have all these questions.  I'm also looking at electricity consumption, but so far I could not find a good method to analyse it for a period of time, especially when I have 2-tariff electricity meter (in my case I have cheaper energy for 13:00-15:00 and 22:00-06:00 hours).

@immi - thanks, I adjusted those values - let's see what happens

[willybauss]

I'm also looking at electricity consumption, but so far I could not find a good method to analyse it...

Youless LS110 is my suggestion. Easy installation, no need to change anything in the power cabling, direct LAN access, supported in FHEM. I use it sonce a few months to track my PV energy creation.
Just in case of bidirectional power meter it might get complicated. I'll need to investigate that soon.

[immi]

Yes they are likely too high The reason is my main heating source is fireplace connected to house heating system and I have been using LWZ just for DHW and absences - and so I was really looking forward to analyze graphs from FHEM to understand if and how should I use LWZ for heating... That's why I have all these questions.  I'm also looking at electricity consumption, but so far I could not find a good method to analyse it for a period of time, especially when I have 2-tariff electricity meter (in my case I have cheaper energy for 13:00-15:00 and 22:00-06:00 hours).

In parallel to monitoring, I would program the programHC1XX programDHWXX so that you have 1K more in the heating-set-temp and in the hotwater-set-temp between 13:00-15:00.
During this hours, your current is cheeper and normally in winter the air is hotter.
I wouldn´t do it between 22:00-06:00, because the current is cheeper but it is on avarage colder.
immi

[mlb]

In parallel to monitoring, I would program the programHC1XX programDHWXX so that you have 1K more in the heating-set-temp and in the hotwater-set-temp between 13:00-15:00.

Absolutely, I have done that already for some time, and have even 5K difference for DHW and a bit less for HC so I use energy more efficiently. Here I had a problem with setting P59 that caused the pump to start prematurely, so I set it to zero. It took several weeks before I understood what this setting does...

Still I was hoping to register values like sElectrDHWDay or sElectrHCDay on daily basis just to track usage in different months, just for some reason they are not shown on graphs reasonably.

Youless LS110 is my suggestion. Easy installation, no need to change anything in the power cabling, direct LAN access, supported in FHEM. I use it sonce a few months to track my PV energy creation.

Thanks - good itea, I will look at it. Just I noticed it needs the old type of meter with rotating plate, they are no longer used here... maybe I could find a used one.

[houseowner123]

Thanks - good itea, I will look at it. Just I noticed it needs the old type of meter with rotating plate, they are no longer used here... maybe I could find a used one.

The old meters are not a requirement. It works just fine with modern IR meters as I can report. Whether you want to upload your data to bidgely you need to decide.