[FHZ] question on FS20 FHT-80B II

[Dr. Boris Neubert]

                                             

Am Sonntag, 7. Juni 2009 schrieb Rudolf Koenig:
> > an extension of the FHT.pm module: if a new attribute "lazy" ist set,
> > one of the commands
>
> [...]
>
> > will only be sent if it would actually change the setting.
> >
> > What do you think?
>
> Go ahead!

I just started to implement this when I saw that for nearly all of my FHTs
most readings are missing or have their initial values or they are from
2009-06-01, the last update of the fhem code from CVS.

list 1.wz.hzg
Internals:
   CODE       xxxx
   DEF        xxxx
   IODev      FHZ
   NAME       1.wz.hzg
   NR         39
   STATE      measured-temp: 23.3 (Celsius)
   TYPE       FHT
   Readings:
     2009-06-07 18:48:58   ack             0
     2009-06-07 18:48:56   actuator        6%
     2009-06-07 18:48:57   desired-temp    20.0
     2009-06-07 18:48:58   end-xmit        0
     2009-06-07 18:48:57   measured-high   0      <<<<
     2009-06-07 18:48:57   measured-low    233   <<<<
     2009-06-07 18:48:57   measured-temp   23.3 (Celsius)
     2009-06-07 18:48:58   warnings        none
   from/to-values are missing!            <<<<

=> only desired-temp, measured-temp and actuator have (meaningful) values.

Is this my personal problem or is there something wrong with previous week's
CVS version?

Boris


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> => only desired-temp, measured-temp and actuator have (meaningful) values.
>
> Is this my personal problem or is there something wrong with previous week's
> CVS version?

The last version removes all FHZ: elements from the STATE array (else
you would have each entry twice). I hope it does not brake something
else.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Rudolf Koenig wrote:
>> => only desired-temp, measured-temp and actuator have (meaningful) values.
>>
>> Is this my personal problem or is there something wrong with previous week's
>> CVS version?
>
> The last version removes all FHZ: elements from the STATE array (else
> you would have each entry twice). I hope it does not brake something
> else.

I revoke and state the contrary. I get all values, so it keeps on
working. It appears that my FHTs are not verbose enough - seems to
depend on the weather or so. An explicit refreshvalues makes the values
appear. No idea why it did not work yesterday...

Boris

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Am Sonntag, 7. Juni 2009 schrieb Rudolf Koenig:
> > I use 9 FHTs in my house and it is impossible to set the day/night
> > schedules in one go, even for one FHT at a time, some on/off-times are
> > missed by the FHT.
>
> > an extension of the FHT.pm module: if a new attribute "lazy" ist set,
> > one of the commands
>
> [...]
>
> > will only be sent if it would actually change the setting.
> >
> > What do you think?
>
> Go ahead!

changes made, tested, documentation updated, committed to CVS.

If the lazy attribute is set, FHEM won't send commands to the FHT if  the  
current reading and the value to be set are already identical. This may help
avoiding conflicts with the max-1%-time-on-air rule in large installations.
Not set per default.

Notabene: as opposed to the initial intention, lazy even applies to any FHT
command and not only to the *-from/-to commands.

Boris


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-