on-for-timer...

[Guest]

Originally posted by: <email address deleted>

Hello,
I have problem with on-for-timer ,because after sending command fhem
doesn't change state to "off" after specyfied time , what could couse
the problem?

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

[rudolfkoenig]

                                                   

> I have problem with on-for-timer ,because after sending command fhem
> doesn't change state to "off" after specyfied time , what could couse
> the problem?

This is normal. You could try the attribute "follow-on-for-timer" though.

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

[Zrrronggg!]

                                                     

Basically the concept of FHEM is to show the last known command which
was sent out to a device and NOT the current state of the device.
This is due to the fact, that DS20 actuators do not send back any
information and therefore FHEM cannot be certain what the status of
the device might be.

And since the "off" part is not a command send out by FHEM but
something which (hopefully) happens in the actor, FHEM does not know
about it. And the last thing FHEM knows is that it sent "on-for-
timer".

Of course FHEM can calculate when the "for-timer" time is reached and
then change the interface display to off.
To let FHEM know that it should do that, the "follow-on/off-for-timer"
attribute may be used as Rudolf mentions.
But please note, that these changes in the interface are purely based
on counting back the time after the command was issued, there is no
way to know for FHEM, if the actuator really is switched off.




On 18 Dez., 10:37, Rudolf Koenig wrote:
> > I have problem with on-for-timer ,because after sending command fhem
> > doesn't change state to "off" after specyfied time , what could couse
> > the problem?
>
> This is normal. You could try the attribute "follow-on-for-timer" though.

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

[Guest]

Originally posted by: <email address deleted>

I think that's clear thanks for the answer!

On 19 Gru, 23:44, "Zrrronggg!" wrote:
> Basically the concept of FHEM is to show the last known command which
> was sent out to a device and NOT the current state of the device.
> This is due to the fact, that DS20 actuators do not send back any
> information and therefore FHEM cannot be certain what the status of
> the device might be.
>
> And since the "off" part is not a command send out by FHEM but
> something which (hopefully) happens in the actor, FHEM does not know
> about it. And the last thing FHEM knows is that it sent "on-for-
> timer".
>
> Of course FHEM can calculate when the "for-timer" time is reached and
> then change the interface display to off.
> To let FHEM know that it should do that, the "follow-on/off-for-timer"
> attribute may be used as Rudolf mentions.
> But please note, that these changes in the interface are purely based
> on counting back the time after the command was issued, there is no
> way to know for FHEM, if the actuator really is switched off.
>
> On 18 Dez., 10:37, Rudolf Koenig wrote:
>
>
>
>
>
>
>
> > > I have problem with on-for-timer ,because after sending command fhem
> > > doesn't change state to "off" after specyfied time , what could couse
> > > the problem?
>
> > This is normal. You could try the attribute "follow-on-for-timer" though.

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