CUL+FHTs weekplan

[Guest]

Originally posted by: <email address deleted>

Hi, what is the best way to periodicaly set a week plan (eg every day at
3am to make sure users dont make changes) to all my FHTs (now cca 5-6)
connected via CUL. The plan is mostly the same for the whole week eg from
05:00 till 08:00 and from 17:00 till 22:00. Every time I tried my CUL runs
out of buffer and goes to LOVF or EOB messages. Thanks a lot!

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

try to set just desired-temp with a sheduled "at"


On Fri, Nov 23, 2012 at 9:59 AM, Tomáš Hora wrote:

> Hi, what is the best way to periodicaly set a week plan (eg every day at
> 3am to make sure users dont make changes) to all my FHTs (now cca 5-6)
> connected via CUL. The plan is mostly the same for the whole week eg from
> 05:00 till 08:00 and from 17:00 till 22:00. Every time I tried my CUL runs
> out of buffer and goes to LOVF or EOB messages. Thanks a lot!
>
>  --
> To unsubscribe from this group, send email to
> fhem-users+unsubscribe@googlegroups.com
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

thats an option the weekplan is probably for me best solution since I every
eg 15 mins send all fhts mode manual/auto depending if someone is staying
at the room...

Dne pátek, 23. listopadu 2012 10:03:22 UTC+1 drdownload napsal(a):
>
> try to set just desired-temp with a sheduled "at"
>
>
> On Fri, Nov 23, 2012 at 9:59 AM, Tomáš Hora
> > wrote:
>
>> Hi, what is the best way to periodicaly set a week plan (eg every day at
>> 3am to make sure users dont make changes) to all my FHTs (now cca 5-6)
>> connected via CUL. The plan is mostly the same for the whole week eg from
>> 05:00 till 08:00 and from 17:00 till 22:00. Every time I tried my CUL runs
>> out of buffer and goes to LOVF or EOB messages. Thanks a lot!
>>
>>  --
>> To unsubscribe from this group, send email to
>> fhem-users+...@googlegroups.com
>>
>
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

you can also try to not set all weekplans at the same time. 1 fht at 2h30,
1 fht at 3h00 etc.


On Fri, Nov 23, 2012 at 10:24 AM, Tomáš Hora wrote:

> thats an option the weekplan is probably for me best solution since I
> every eg 15 mins send all fhts mode manual/auto depending if someone is
> staying at the room...
>
> Dne pátek, 23. listopadu 2012 10:03:22 UTC+1 drdownload napsal(a):
>>
>> try to set just desired-temp with a sheduled "at"
>>
>>
>> On Fri, Nov 23, 2012 at 9:59 AM, Tomáš Hora wrote:
>>
>>> Hi, what is the best way to periodicaly set a week plan (eg every day at
>>> 3am to make sure users dont make changes) to all my FHTs (now cca 5-6)
>>> connected via CUL. The plan is mostly the same for the whole week eg from
>>> 05:00 till 08:00 and from 17:00 till 22:00. Every time I tried my CUL runs
>>> out of buffer and goes to LOVF or EOB messages. Thanks a lot!
>>>
>>>  --
>>> To unsubscribe from this group, send email to
>>> fhem-users+...@**googlegroups.com
>>>
>>
>>  --
> To unsubscribe from this group, send email to
> fhem-users+unsubscribe@googlegroups.com
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Martin Fischer]

Am Freitag, 23. November 2012, 00:59:40 schrieb Tomáš Hora:
> Hi, what is the best way to periodicaly set a week plan (eg every day at
> 3am to make sure users dont make changes) to all my FHTs (now cca 5-6)
> connected via CUL. The plan is mostly the same for the whole week eg from
> 05:00 till 08:00 and from 17:00 till 22:00. Every time I tried my CUL runs
> out of buffer and goes to LOVF or EOB messages. Thanks a lot!

regarding to your LOVF problem, try also this on your FHTs:

Attributes:
lazy
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.

update the state of each device at different times, first. then set your week
plan, e.g.

00:15 FHT1 get state of device
00:45 FHT1 update week plan
01:15 FHT2 get state of device
01:45 FHT2 update week plan
...

avoids "flooding" the "air"

depending on your installation (and the numbers of devices), the time frames
could be shorter, e.g.

00:15 FHT1 get state of device
00:30 FHT2 get state of device
00:45 FHT3 get state of device
...
03:15 FHT1 update week plan
03:30 FHT2 update week plan
03:45 FHT3 update week plan
...

regards...

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com