THZ / LWZ Tecalor Stiebel Eltron Heizung

[immi]

I have not noticed any changes because I currently do not test anything. If there is a list of known bugs/issues?

not to my knowledge

There is a typo in 00_THZ.pm - the entry "interval_sBoostDHWTotal" is present twice (lines 342 and 343 in ver 0.111). I guess the second entry should read "interval_sBoostHCTotal".

thanks, next time I commit it will be fixed

immi

[houseowner123]

Not sure if this is related but last night I ran an update. At 10 am (on events listed) Mythz disconnected. The only correlating event at the time is the mystic disconnect-reappear.

Code Auswählen Erweitern

2014.11.23 09:42:48 1: /dev/ttyUSB0 disconnected, waiting to reappear (Mythz)
2014.11.23 09:42:53 3: Setting Mythz baudrate to 115200
2014.11.23 09:42:53 1: /dev/ttyUSB0 reappeared (Mythz)

Tonight I restarted the FHEM, RasPi , restart the LWZ, nothing helped.
The log after restart claims that mythz is opened, but it isn't. Any suggestions anyone?  Thanks!

Code Auswählen Erweitern

2014.11.24 00:03:17 0: Server shutdown
2014.11.24 00:03:21 1: Including fhem.cfg
2014.11.24 00:03:21 3: telnetPort: port 7072 opened
2014.11.24 00:03:22 3: WEB: port 8083 opened
2014.11.24 00:03:22 3: WEBphone: port 8084 opened
2014.11.24 00:03:22 3: WEBtablet: port 8085 opened
2014.11.24 00:03:22 2: eventTypes: loaded 450 events from ./log/eventTypes.txt
2014.11.24 00:03:23 3: Opening Mythz device /dev/ttyUSB0
2014.11.24 00:03:23 3: Setting Mythz baudrate to 115200
2014.11.24 00:03:23 3: Mythz device opened
2014.11.24 00:03:27 3: Opening CUL_0 device /dev/ttyACM0
2014.11.24 00:03:27 3: Setting CUL_0 baudrate to 9600
2014.11.24 00:03:27 3: CUL_0 device opened
2014.11.24 00:03:27 3: CUL_0: Possible commands: BCFiAZEGMKURTVWXefmltux
2014.11.24 00:03:27 1: Including ./log/fhem.save
2014.11.24 00:03:28 1: usb create starting
2014.11.24 00:03:30 3: Probing CUL device /dev/ttyAMA0
2014.11.24 00:03:30 3: Probing TCM_ESP3 device /dev/ttyAMA0
2014.11.24 00:03:30 3: Probing FRM device /dev/ttyAMA0
2014.11.24 00:03:36 1: usb create end
2014.11.24 00:03:36 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.11.24 00:03:36 0: Server started with 55 defined entities (version $Id: fhem.pl 6913 2014-11-08 10:32:44Z rudolfkoenig $, os linux, user fhem, pid 2212)

[michaelk68]

HI,

same happened to me after upgrading fhem and the thz module. Mythz seams to be opened, but it isn't.

[immi]

If you want to revert to v0110 manually, download it from here
https://github.com/mhop/fhem-mirror/blob/9e3218d56713c291d42f5562c3455bf2160588dd/fhem/FHEM/00_THZ.pm

other stuff you can do is to force a full update.
or to look in  the log-file after enabling verbose 5

I do expect the problem is related to something else. more this night.
immi

[michaelk68]

Hi immi,

even after downgrading to version 0.110 I cant see the THZ:

2014.11.24 17:33:40 3: Opening Mythz device /dev/ttyUSB0
2014.11.24 17:33:40 3: Setting Mythz baudrate to 115200
2014.11.24 17:33:40 3: Mythz device opened
2014.11.24 17:33:49 1: Including ./log/fhem.save
2014.11.24 17:33:49 1: usb create starting
2014.11.24 17:33:51 3: Probing CUL device /dev/ttyAMA0
2014.11.24 17:33:51 3: Probing TCM_ESP3 device /dev/ttyAMA0
2014.11.24 17:33:51 3: Probing FRM device /dev/ttyAMA0
2014.11.24 17:33:57 3: Probing TCM_ESP3 device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing TCM_ESP2 device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing FHZ device /dev/ttyUSB1
2014.11.24 17:33:57 3: Probing TRX device /dev/ttyUSB1
2014.11.24 17:33:58 3: Probing ZWDongle device /dev/ttyUSB1
2014.11.24 17:33:58 3: Probing FRM device /dev/ttyUSB1
2014.11.24 17:34:03 1: usb create end
2014.11.24 17:34:03 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no basicAuth attribute. telnetPort has no password/globalpassword attribute.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2014.11.24 17:34:04 0: Server started with 33 defined entities (version $Id: fhem.pl 6913 2014-11-08 10:32:44Z rudolfkoenig $, os linux, user fhem, pid 2746)
2014.11.24 17:34:04 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:05 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEB. Don't forget to save config.
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEBphone. Don't forget to save config.
2014.11.24 17:34:06 3: [MyDashboard V2.13] Added hiddenroom 'DashboardRoom' to WEBtablet. Don't forget to save config.
2014.11.24 17:34:06 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:07 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:08 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:09 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:10 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:11 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:12 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:13 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?
2014.11.24 17:34:13 3: Mythz THZ_ReadAnswer got no answer from DevIo_SimpleRead. Maybe too slow?

[immi]

I was quite sure that it was not related to THZ v0111.
Another module causes you some problems in combination with thz.

have you tried reverting everything to an old status?
you should find it in   /fhem/restoreDir/-datum-

than if the old status is working we have to look which fhem-modules have changed in the meanwhile, and one by one analyze them.

[houseowner123]

immi: what is the command for restoring a status. Can it be done from within the FHEM web interface?

Thanks!

[immi]

immi: what is the command for restoring a status. Can it be done from within the FHEM web interface?
Thanks!

I suggest that you go to command line and with trial and error copy the files:
the stucture is simple

Code Auswählen Erweitern


[/opt/fhem/restoreDir] # ls
2014-11-09/ 2014-11-22/ 2014-11-24/

I have updated 3 times , I select the last one and copy them to the original path

Code Auswählen Erweitern


[/opt/fhem/restoreDir] # cd 2014-11-24/
[/opt/fhem/restoreDir/2014-11-24] # ls
CHANGED  FHEM/    docs/
[/opt/fhem/restoreDir/2014-11-24] # cd FHEM
[/opt/fhem/restoreDir/2014-11-24/FHEM] # ls
00_THZ.pm             98_HourCounter.pm     HttpUtils.pm
10_CUL_HM.pm          98_WOL.pm             TcpServerUtils.pm
33_readingsGroup.pm   98_logProxy.pm        controls_fhem.txt
98_CustomReadings.pm  98_structure.pm       firmware/
98_HMinfo.pm          HMConfig.pm
[/opt/fhem/restoreDir/2014-11-24/FHEM] # cp * /opt/fhem/FHEM/


immi

[willybauss]

I made a full update in the night from 21st to 22nd of November, a few hours before the new 00_THZ version was accessible. It works, so currently I resist any thought of doing another update ...
But I need to mention that I also had some trouble in that night: I also couldn't access the THZ. I couldn't repair it by rebooting the Raspberry Pi, but it worked again after a power cycle of RasPi.
Initially the update didn't work at all since the restoreDir directory had a wrong owner, thus no sub directory under restoreDir could be created. After a while it turned out that there had been some changes in the update code by Rudolf Koenig recently. Changing access rights using chown (change owner) and chgrp change group) solved the issue.

[willybauss]

Currently I deal with p30integralComponent. Does anyone know how to visualize or calculate the actually summed up value of kmin (KelvinMinutes) since last compressor action?
Reason for that it that I frequently noticed unnecessary start of the compressor, even if the room temperature is still too high, e.g. caused by sun shining through southern windows. I could avoid that by increasing P30 from 100Kmin (default) to currently 300Kmin.

[willybauss]

Meanwhile I have the same issue: Mythz says "connected" but it isn't. Last entries in Mythz.log look like
2014-11-24_19:28:31 Mythz DISCONNECTED
2014-11-24_19:28:37 Mythz CONNECTED
2014-11-24_19:28:41 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:28:19 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:35:14 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:40:36 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:53:08 Mythz programDHW_So_1: n.a.--n.a.
2014-11-24_22:56:32 Mythz programDHW_So_1: n.a.--n.a.
2014-11-25_06:40:31 Mythz programDHW_So_1: n.a.--n.a.
2014-11-25_07:00:20 Mythz programDHW_So_1: n.a.--n.a.

Every row shows either a shutdown-restart of fhem, a reboot of RasPi or a power cycle of RasPi.
The issue began exactly in the point in time when I had to reboot my Fritz.Box for a different reason.
Trying to get values from the THZ by "get <parameter>" results in the fhem UI showing "msg2 closed connection".

I need to mention that I'm still on 00_THZ version 0.110.
I already tried to shutdown fhem + copy whole contents of backup directory (.../restoreDir/<Date>/*) + power cycle RasPi, but it didn't help either. Therefore it looks like the issue is outside fhem. But I didn't force any Linux updates since weeks.

After having switched to verbose level 5 I found an entry in the fhem.log file showing

Code Auswählen Erweitern

2014.11.25 07:48:37 5: Cmd: >setstate Mythz disconnected<
2014.11.25 07:48:37 5: Cmd: >setstate Mythz 2014-11-22 00:27:53 HC1_average Error evaluating Mythz userReading HC1_average: Bareword "HC1_avg" not allowed while "strict subs" in use at (eval 856191) line 1.<
But this code does no more exist in my configuration since a couple of days. I don't know where it comes from. Any idea?

[immi]

I do not make any substantial change to THZ since 6 weeks. V0111 is definitely not responsible
I do not see any failure with NAS, fritzbox, MACOS; with direct serial connection or with ser2net.

1) Try to look what you have in common: e.g. servertype

2) Try to disable all connected hardware: e.g. remove all CUL usb (I do not have any CUL)

3) there was a change to the CUL and DEVIO 10 days ago
https://github.com/mhop/fhem-mirror/commit/6cae87be663ce0486375b510dca69de619c6a52b
@Willy here you can try the following? stop fhem,  remove line 391 from FHEM/DevIo.pm,  delete fhem.save, start fhem

4) please post the log text file with verbose 5

immi

[willybauss]

@ immi:
Since I'm still on V0110 I also believe it has nothing to do with the THZ module. I'll try the suggested steps tonight.

@ michaelk68 and houseowner123:
Should we try to find out common things in our configurations?
My config consists of (unsorted list as it came to my mind)

   
• THZ module connected via USB hub and USB2Ser adapter
• CUL module connected via USB hub
• STV module for remote control of Samsung TV via LAN
• fhem on Raspberry Pi w/ Raspbian OS
• log file directory laying on a Western Digital NAS, mounted into the RasPi's directory tree (to avoid write actions on RasPi's SD card)
• Fritz box 7270 as dhcp server, WLAN- and DSL router
• FileLog
• different SVG plots
• WEBphone and WEBtablet for remote access
• dashboard
• small number of HomeMatic devices (power plug, 8 channel switch)

If we share same parts of config these might be on suspicion.

[michaelk68]

I restored my config before the fhem update. It's still not working. So I think it's depends on a linux update.
I have a Raspi with linux wheezy, which is running fhem.
Connected is the THZ over USB, some 1wire temperature sensors, and an USB IR reader for smart metering.
I did install linux updates on the weekend!

Michael

[willybauss]

so up to now Raspi / Linux seems to be the only correlation. Hopefully houseowner123's data will confirm that.

@ immi:
on which platform does your fhem work? Didn't you use a Raspi too? In that case I wonder why you do not (yet?) see the issue.