CUL + FHT80b

[Guest]

Originally posted by: <email address deleted>

Hi,

About a week ago, i switched back from Homematic, to 'good old' FS20 and
family. finally something i can write proper scripts in, and have cool
graphs:)
got myself a CUL, to receive the energy meters without having a 2nd device.

Before i received my CUL i used a upgraded FHZ1000 (to pro, to receive
the temperature thingys).

The FHZ1000 received the FHT80b data correctly: actuators when changed,
temperature every few minutes. Now with my CUL: it reports a
lime-protection every few minutes, and no temperature. actuator changes
are still reported.

What i get with log level 5:
2010.05.31 19:10:47 4: CUL: T2C5900AA00 -38
2010.05.31 19:10:47 5: CUL dispatch 810c04xx0909a0012c590000aa00
2010.05.31 19:10:47 4: FHT livingroom_heating actuator: lime-protection
2010.05.31 19:10:47 5: Triggering livingroom_heating (1 changes)

Does this make sense to any of you?

Remco

--
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-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Zrrronggg!]

                                                     

Could it be that this is the infamous "lime-protection-bug" somehow?

I have not encountered it myself so far but from what I read here in
the group
there is a problem that under certain circumstances after a lime
protection the real actuator states are not shown.

As far as I understood this is the problem:

If DURING lime-protection phase the desired-temp is LOWER then
measured-temp, the FHT sends lime-protection instead of actuator x%
even after the lime-protection is finshed. It does so  until the
desired temp gets higher then the measured temp.

(which in summer may take a while!)

It seems that this is a FHT firmwarebug. I have no idea why the
FHZ1000 (are we really talking about a FHZ1000? Or a FHZ1000PC?) gets
it right, maybe ELV put some workaround code in the FHZ.

A workaround with FHEM whould be, to set the desired temp right after
the lime protection to a high level for a short period and then back.
It seems that some have scripted that based on the known lime
protection times.

--
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-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.