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

Begonnen von immi, 02 Februar 2015, 11:42:16

Vorheriges Thema - Nächstes Thema

Heiner

Hi Immi,

after almost 12 hours I have a Feedback for you.

running 0.188 after update, no further update available
Attached the logfile which shows

342 problems @ step0 and 32 @step 2
The register impacted are ( and after the # the number of cases:
Zitat0B1460 -> #73
0A0925 -> #66
0A0611 -> #56
0B010E -> #46
D1     -> #34
0A05B8 -> #16
F3     -> #15
0A057E -> #13
0A05C4 -> #10
0A1DA1 -> #8
0A056C -> #7
0A05A2 -> #4
0A057D -> #4
0A05C2 -> #3
0B1462 -> #2
0B1461 -> #3
0A1780 -> #2
0A0924 -> #1
0A058C -> #1
0C1560 -> #1
0A0588 -> #2
0C0005 -> #1
0A1790 -> #1
FB -> #1

at 04:10 you see one special case resulting from the colling function
Zitat2020.08.25 04:10:00 3: THZ_Set: Error msg:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0  -- 0180700A05DD00031003 ->
2020.08.25 04:10:00 2: cooling: set Heizung p99startUnschedVent 3: 0180700A05DD00031003---THZ_Set: Error msg:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0  -- 0180700A05DD00031003 ->
2020.08.25 04:10:00 3: Setting Heizung serial parameters to 115200,8,N,1
2020.08.25 04:10:00 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 reappeared (Heizung)
2020.08.25 04:10:30 2: cooling: set Heizung p99startUnschedVent 3: 3
2020.08.25 04:11:42 1: /dev/serial/by-id/usb-ftdi_usb_serial_converter_ftBNKGX5-if00-port0 disconnected, waiting to reappear (Heizung)

I will change now to:
attr Mythz simpleReadTimeout 2


Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

hi heiner
thanks for the feedback
0.189 is available for update, nevertheless I also put it here
the simpleReadTimeout 2  needs 0.189


p.s. pay attention to attr Mythz or attr Heizung

Heiner

0.189 is found now by "update all" and installed, I keep you posted....
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

Heiner

no good. Same problem again.

Logfile of the last 2,5 hours attached. I count 66 step 0 problems and 14 step 2 problems

with 0.189 and shutdown restart afterwards
and with attr Heizung simpleReadTimeout 2



Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Hi Heiner
i focused in the timing of the comunication,
last idea: change line 1507 to
select(undef, undef, undef, 0.1);
you can change it from 0.002 to 0.5


maybe it is too hot or I am losing the big picture :)
The main problem is probably that your usbserial disconnects:
0) are you usung windows?
1) how well are soldered the cables?
check cable/cable connections /adapters/
2) When was the last time you made an update?
fhem makes a restore directory before an update.
you can see all vesioning https://github.com/fhem/fhem-mirror/tree/master/fhem/FHEM
here is the history of changes for https://github.com/fhem/fhem-mirror/commits/master/fhem/FHEM/00_THZ.pm
--> you can download older versions
DEVIO changed in the last 4 monthes a lot; I do not know if it has sideeffects to your system
https://github.com/fhem/fhem-mirror/commits/master/fhem/FHEM/DevIo.pm




Heiner

Hi Immi,

I changed it from 0.02 to 0.5 (no clue why it is not on 0.1 as you indicated)
then shutdown restart and.... the problem is a little different now not it is @ step1 !!!

0) fhem is running on a BananaPi with Armbian and Debian 10, and I built it relative new may be 1 month back
2) last update must have been only some weeks back. I think it was with THZ Version 0.184   
    I found a backup from 12th August and there that Version shows in the relevant row the value 0.025

thanks for the hint on where to find older Versions, I found the restore folder from fhem, it has 3 updates only 23-24-25 of August. 23 with no THZ.pm, 24 the THZ file is corrupt and full of NULL and 25th is already with Version 0.188 which caused some trouble for me.

I can try to get 0.184 again to work, but prefer that the actual Version works as well. I hope this move to step 1 rings any bell for you?

I will check soldering....
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Zitat von: Heiner am 25 August 2020, 16:35:24
then shutdown restart and.... the problem is a little different now not it is @ step1 !!!
this is a very good hint; I think I got it now; sorry it took so long
i uploaded 0.190

Heiner

Hi Immi,

perfect. Installed reboot, all values read by fhem no log entry. If it stays like it perfect.

shall I now remove the attr SimpleReadTimeout which is set to 2 still?

Really great that you made it.
Heiner
--------------------------------
fhem auf Pi3+
CUL 868MHz, Signalduino 434MHz, HM-CFG-USB
HM, THZ, Kostal, Somfy, Conbee, Pytonbinding, FritzBox, FTUI, MQTT2

immi

Zitat von: Heiner am 26 August 2020, 14:45:47
shall I now remove the attr SimpleReadTimeout which is set to 2 still?
yes remove it.
if you still see something strange in the next days, put it to 1; Two seconds  delay should never happen in your tecalor.
please give me a feedback about that in some days

börni

Hello @ll,

I've problems with fhem since my last update fhem and perl - I'm using loxberry.


2020.08.26 12:55:56 1: PERL WARNING: Use of uninitialized value $err in concatenation (.) or string at ./FHEM/00_THZ.pm line 1064.
2020.08.26 12:55:56 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/00_THZ.pm line 1064.


If I change some of the parameters - e.g. p04DHWsetTempDay -> I'm getting this error message:

msg THZ_Set: error reading register: 'THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0'


I'm not sure where the problem comes from - is that the right forum here for my problem?

Thanks
Fabian
Loxberry auf RPi3 mit FHEM / LWZ303i V.2.06 / Loxone / eisfair Server (LMS/NAS/cloud/et.) / Fronius WR mit 9,3 kwp

immi

hi fabian
can you please check if you have the last version 0.190?
the file is shared below;
it is automatically updated always 12h-24h  after my upload

börni

Hello Immi,

currently it's 0.189 - is that a issue which is solved in 0.190?

Thanks
Fabian
Loxberry auf RPi3 mit FHEM / LWZ303i V.2.06 / Loxone / eisfair Server (LMS/NAS/cloud/et.) / Fronius WR mit 9,3 kwp

immi


börni

This morning came the update to 0.190 - the problem changed and isn't solved unfortunately:


0180A517006400640064012C012C0064010000015E01C2001003---THZ_Set: Error msg:  THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step2 -- 0180A517006400640064012C012C0064010000015E01C2001003 ->


I'm wondering about the message because it looks like that the Interface isn't working properly - but it has worked before the updates ?! :(
Do you have an idea?

The readings are working - I see all the values. It seems if I'd change something by the parameters that this will not go through the line :(
My Version is 2.06

If I try to "set" the value two or three times after and after the failure message changes:

msg THZ_Set: error reading register: 'THZ_ReadAnswer: InterfaceNotRespondig. Maybe too slow THZ_Get_Com: error found at step0 '


and after the fourth or fifth try the value is transmitted. - I can find out if I use the get function.

Thanks
Fabian
Loxberry auf RPi3 mit FHEM / LWZ303i V.2.06 / Loxone / eisfair Server (LMS/NAS/cloud/et.) / Fronius WR mit 9,3 kwp

immi

Hi florian,
happy you see an improvement.
if you have the old 2.06, it makes sense

use
attr Mythz simpleReadTimeout 1


and if still happens

attr Mythz simpleReadTimeout 2


immi