Seit kurzem ständig Abends Pieps"orgien" der FHT80

[Holger]

Hallo,

ich weiss nicht mehr weiter.

Meine FHTs (über FHT1300PC-USB) an Linux PC mit UBuntu haben jetzt
lange ganz gut funktioniert, aber seit Kurzem bekomme ich fast täglich
Abends "PiepsOrgien".

Dann fangen nach einander die Regler (oder Raumregler) an zu piepsen,
Regler regelt auf (Heizung heizt dann direkt vor dem Schlafengehen
noch einmal alles auf gepflegt 23-25°C) und Morgens ist wieder alles
i.O ??

Keine Fehlermeldung bzgl. Batterie o.ä.

Hat das was mit der Lime Protection zu tun ?

Ich bin ratlos. Passiert wie gesagt seit Kurzem in verschiedenen
Räumen.

Anbei Fhem.cfg

attr global autoload_undefined_devices 1
attr global logfile /var/log/fhem/fhem-%Y-%m.log
attr global modpath /usr/share/fhem
attr global port 7072 global
attr global statefile /var/log/fhem/fhem.save
attr global verbose 3

define WEBS FHEMWEB 8084
attr WEBS smallscreen 1

define WEB FHEMWEB 8083 global

define autocreate autocreate
attr autocreate autosave 1
attr autocreate device_room %TYPE
attr autocreate filelog /var/log/fhem/%NAME-%Y.log
attr autocreate weblink 1
attr autocreate weblink_room Plots

define FHZ1 FHZ /dev/ttyUSB0
attr FHZ1 fhtsoftbuffer 0

define FHT_Bad_U FHT 0b0b
attr FHT_Bad_U retrycount 3
attr FHT_Bad_U room UG

define FileLog_FHT_Bad_U FileLog /var/log/fhem/FHT_Bad_U-%Y-%m.log
FHT_Bad_U
attr FileLog_FHT_Bad_U logtype fht:Temp/Act,text
attr FileLog_FHT_Bad_U room UG

define weblink_FHT_Bad_U weblink fileplot
FileLog_FHT_Bad_U:fht:CURRENT
attr weblink_FHT_Bad_U label "FHT_Bad_U Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_Bad_U room UG

define FHT_SchlafZ_U FHT 0b0c
attr FHT_SchlafZ_U retrycount 3
attr FHT_SchlafZ_U room UG

define FileLog_FHT_SchlafZ_U FileLog /var/log/fhem/FHT_SchlafZ_U-%Y-
%m.log FHT_SchlafZ_U
attr FileLog_FHT_SchlafZ_U logtype fht:Temp/Act,text
attr FileLog_FHT_SchlafZ_U room UG

define weblink_FHT_SchlafZ_U weblink fileplot
FileLog_FHT_SchlafZ_U:fht:CURRENT
attr weblink_FHT_SchlafZ_U label "FHT_SchlafZ_U Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_SchlafZ_U room UG

define FHT_Kueche FHT 0b0d
attr FHT_Kueche retrycount 3
attr FHT_Kueche room UG

define FileLog_FHT_Kueche FileLog /var/log/fhem/FHT_Kueche-%Y-%m.log
FHT_Kueche
attr FileLog_FHT_Kueche logtype fht:Temp/Act,text
attr FileLog_FHT_Kueche room UG

define weblink_FHT_Kueche weblink fileplot
FileLog_FHT_Kueche:fht:CURRENT
attr weblink_FHT_Kueche label "FHT_Kueche Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_Kueche room UG

define FHT_WohnZ FHT 0b0e
attr FHT_WohnZ retrycount 3
attr FHT_WohnZ room UG

define FileLog_FHT_WohnZ FileLog /var/log/fhem/FHT_WohnZ-%Y-%m.log
FHT_WohnZ
attr FileLog_FHT_WohnZ logtype fht:Temp/Act,text
attr FileLog_FHT_WohnZ room UG

define weblink_FHT_WohnZ weblink fileplot
FileLog_FHT_WohnZ:fht:CURRENT
attr weblink_FHT_WohnZ label "FHT_WohnZ Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_WohnZ room UG

define FHT_KiZi FHT 0b0f
attr FHT_KiZi retrycount 3
attr FHT_KiZi room UG

define FileLog_FHT_KiZi FileLog /var/log/fhem/FHT_KiZi-%Y-%m.log
FHT_KiZi
attr FileLog_FHT_KiZi logtype fht:Temp/Act,text
attr FileLog_FHT_KiZi room UG

define weblink_FHT_KiZi weblink fileplot FileLog_FHT_KiZi:fht:CURRENT
attr weblink_FHT_KiZi label "FHT_KiZi Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_KiZi room UG

define FHT_Bad_O FHT 1b0b
attr FHT_Bad_O retrycount 3
attr FHT_Bad_O room OG

define FileLog_FHT_Bad_O FileLog /var/log/fhem/FHT_Bad_O-%Y-%m.log
FHT_Bad_O
attr FileLog_FHT_Bad_O logtype fht:Temp/Act,text
attr FileLog_FHT_Bad_O room OG

define weblink_FHT_Bad_O weblink fileplot
FileLog_FHT_Bad_O:fht:CURRENT
attr weblink_FHT_Bad_O label "FHT_Bad_O Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_Bad_O room OG

define FHT_SchlafZ_O FHT 1b0c
attr FHT_SchlafZ_O retrycount 3
attr FHT_SchlafZ_O room OG

define weblink_FHT_SchlafZ_O weblink fileplot
FileLog_FHT_SchlafZ_O:fht:CURRENT
attr weblink_FHT_SchlafZ_O label "FHT_SchlafZ_O Min $data{min1}, Max
$data{max1}, Last $data{currval1}"
attr weblink_FHT_SchlafZ_O room OG

define FileLog_FHT_SchlafZ_O FileLog /var/log/fhem/FHT_SchlafZ_O-%Y-
%m.log FHT_SchlafZ_O
attr FileLog_FHT_SchlafZ_O logtype fht:Temp/Act,text
attr FileLog_FHT_SchlafZ_O room OG

# FHT Entkalkungs-Workaround
define lime_reset notify .*lime-protection {\
my ($d, $m);;\
$d = $defs{'@'}{READINGS}{"desired-temp"}{VAL};;\
$m = $defs{'@'}{READINGS}{"measured-temp"}{VAL};;\
if($m gt $d) {\
fhem("attr @ lazy 0");;\
fhem("set @ desired-temp 29");;\
fhem("set @ desired-temp $d");;\
}\
}


define fhz_timer at +*00:01:00 set FHZ1 time

[Ernst Cozijnsen]

I have the same here and i would really like to now what it is

2011/3/18 Holger <holger.sch...@googlemail.com>

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-...@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+...@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Rudolf Koenig]

> Meine FHTs (�ber FHT1300PC-USB) an Linux PC mit UBuntu haben jetzt
> lange ganz gut funktioniert, aber seit Kurzem bekomme ich fast t�glich
> Abends "PiepsOrgien".

Dann waere es wichtig festzustellen:
- was piept
- wie piept es
- was steht im Handbuch zu diese Piep-Folge.
- was zeigen die logs (actuator/desired-temp/measured-temp)
- wie lange hat es denn "gut funktioniert" und was hat sich zuletzt geaendert

Fhem hat seit langem keine FHT/FHZ Aenderungen mehr erfahren, deswegen vermute
ich dass es ein FHT Problem ist...

Und solche Feinheiten, wie ueber irgendwelche Bits die Piep-Zeiten
freizuschalten kommt auch nicht in Frage (das kann fhem dem FHZ nicht sagen),
das koennte man hoechstens mit dem CUL.

[Holger]

Hello Rudolf,

thanks for the "trigger" to check the Basic FHT80 issues.

You are right its likely not an FHEM issue, but a lost connection
between radiator adapter and the room controller.

Signal is 5 beeps, heating goes to 30% and the antenna symbol in the
radiator adapter is not shown (like described in the FHT80 manual)

However, i changed all the batteries for new ones only 3 months
ago ... :-(. (from Aldi Sued .... best value for money following
Stiftung Warentest)

And if I measure the battteries with my battery tester they still have
> 1,4 Volt which should still be enough.

Which ones to change the room controller (no battery error message in
the log files btw) or the radiator adapter.

Does anyone has experience with these Lithium AA batteries ?
--> Yes, they are expensive, but last for about 10 times the amount of
photos as the cheapest alkaline batteries in a battery test for
cameras
--> I would give it a shot.

Nothing can be more anoying than the wifes voice telling you that "its
beeping again" .... ;-)

[Rudolf Koenig]

> You are right its likely not an FHEM issue, but a lost connection
> between radiator adapter and the room controller.

Cheap radio headphones or the like? Using a CUL in debug-mode (with screen,
not fhem!) with X80 or X08 might help localizing the problem. See also
http://www.koeniglich.de/culfw/commandref.html#cmd_X
Of course professional equipment is preferred if available.

[Holger]

Hi Rudolf,

no new wireless hardware (expect for an additional DECT phone and a
new laptop which usually runs with WLan)
--> should not interfear with the FHZ bandwidth, correct ?

I'll invested in some of these Lithium Batteries and will put them in
as soon as they are available.

I will post my experiences, then.

Strange is:
- Last week, it was a continues beeping in the evenings starting in
one room and then 15 minutes later another room and so on.
- Even I did nothing .... (I was too lazy to look for new
batteries) ... since 3 days, its quite again .... ?

[Dr. Boris Neubert]

Am 19.03.2011 08:23, schrieb Ernst Cozijnsen:
> I have the same here and i would really like to now what it is

Me too ;-)

It occurs from time to time but rare enough not to bother about the
reason, especially not a night when I am too lazy/sleepy to debug my
hardware. I suppose that the FHT8V looses its connection to the FHT80b
and starts complaining.

Regards,
Boris

[hifang]

I guess I have a similar problem. But no beeping. I did not even know
they can beep. Three FHT80b with one radiator each, running since
about 18 months.
OK, mostly I am not there (wanted to have that setup to be able to
control heating over the net in winter to have it warm when coming
home every two weeks or so),
so I could not hear it if it beeps. But once I experienced the
following problem "live", and there was no beeping.

In two of the three rooms (the two with the _newer_ batteries) the
temperature suddenly starts climbing for a short period. But in fhem,
actuator shows 0. Desired temp is below current temp, and only using
manual mode.
That one case I mentioned above, I saw the controller at the radiator
showed actuator >0, but on FHT the desired-temp was way below current
temp.

Anyone knows that kind of behaviour? Can it be that the controller
batteries are too weak to "close the valve"? But I saw no battery
warning sign anywhere.

Interested in any experiences to that topic.. Thanks!

[Thomas Böhne]

On 05/06/2011 12:18 AM, hifang wrote:
> In two of the three rooms (the two with the _newer_ batteries) the
> temperature suddenly starts climbing for a short period. But in fhem,
> actuator shows 0. Desired temp is below current temp, and only using
> manual mode.
> That one case I mentioned above, I saw the controller at the radiator
> showed actuator >0, but on FHT the desired-temp was way below current
> temp.
>
> Anyone knows that kind of behaviour? Can it be that the controller
> batteries are too weak to "close the valve"? But I saw no battery
> warning sign anywhere.

If the valve does not receive actuator messages for a certain time
(maybe due to other devices polluting the frequency), they open the
valve to 30%. You will not see that in fhem, because the main FHT80 unit
does not recognize the valve's reception problems. But what you see is
that the temperature rises.

If the valve receives actuator messages after some time, it goes back to
normal operation, stops beeping and sets the valve appropriately.

Note that the beeps occur seldomly; I would guess one short beep every
20 Minutes or so. Also note that battery empty beeps do not occur during
the night.

Thomas

[Rudolf Koenig]

> Anyone knows that kind of behaviour? Can it be that the controller
> batteries are too weak to "close the valve"? But I saw no battery
> warning sign anywhere.

If the valves cannot receive the FHT signal for a certain period, then they go
to their default opening position (30%?). They should then show a blinking
antenna symbol.

[hifang]

Thanks to both of you (early birds), good to know, that certainly
explains this.
Only question remains why this happens now from time to time, while it
never happened before for a long time. Probably the batteries then. Or
I put the FHT nearer to the receiver over the summer..