Hi there,
since I upgraded to 2.4, I have hiccups with my daylight32 based blind control. Up to then, I used daylight32 as a switch and depending on the setting, I activated the suitable scene. But now regardless if daylight is being "switched off" or "switched on" the scene daylight_on is being activated as well.
Seems to me that the value of the daylight switch is not being properly processed. I already cleaned out all if-then actions that depend on daylight32 to ensure that there are no hidden or conflicting actions. After this I only set up one scene that should activate the scene daylight_on when the sun rises but - as I said - it's also being activated when the sun sets.
Does anybody have a similar problem?
Kinds Regards,
rws
Daylight32 & IF->THEN problems
Re: Daylight32 & IF->THEN problems
Somewhat similar (viewtopic.php?f=3419&t=24029) I there have a well functioning Window/Door sensor as input to IFTHEN. No answer yet on that post unfortunately.
Since 29-12-2016 I am no longer a moderator for this forum
-
- Posts: 155
- Joined: 02 Jan 2016 01:20
Re: Daylight32 & IF->THEN problems
Hi there,
possibly the same source, but possibly different reasons. So far only my daylight app is being affected. Don't know or unterstand why.
Regards,
rws
possibly the same source, but possibly different reasons. So far only my daylight app is being affected. Don't know or unterstand why.
Regards,
rws
- Z-Wave Support
- Posts: 353
- Joined: 21 Oct 2016 15:49
Re: Daylight32 & IF->THEN problems
Hello,
have you tried to make a Logical Rule?
We tested the IFTHEN-App with 2.2.4 and have no Problems.
Regards
Z-Wave Support Team
have you tried to make a Logical Rule?
We tested the IFTHEN-App with 2.2.4 and have no Problems.
Regards
Z-Wave Support Team
-
- Posts: 155
- Joined: 02 Jan 2016 01:20
Re: Daylight32 & IF->THEN problems
Hi there,
first of all, thanks for the reply.
I use the IF-THEN App for mapping scenes to switches and those all work fine. Only mapping Daylight32 to a scene somehow fails. Maybe that helps in diagnosing.
To follow your advice, I just set up a logical rule as replacement, it'll take a 24h cycle to find out if it works properly.
Thanks and best regards,
rws
first of all, thanks for the reply.
I use the IF-THEN App for mapping scenes to switches and those all work fine. Only mapping Daylight32 to a scene somehow fails. Maybe that helps in diagnosing.
To follow your advice, I just set up a logical rule as replacement, it'll take a 24h cycle to find out if it works properly.
Thanks and best regards,
rws
Re: Daylight32 & IF->THEN problems
Have you checked the logs that the "switched off" is actually received by the controller and what then happens, i.e. the corresponding scene called?
-
- Posts: 155
- Joined: 02 Jan 2016 01:20
Re: Daylight32 & IF->THEN problems
Hello,
yes, the switched off was actually sent but nothing was triggered by it. (It worked for months with 2.2.2 and only with 2.2.4 the problems appeared)
clarification: I only need the "daylight on" to trigger something, "daylight off" is not needed, hence it doesn't trigger anything. Still, I can see on and off in the log.
Regards, rws
yes, the switched off was actually sent but nothing was triggered by it. (It worked for months with 2.2.2 and only with 2.2.4 the problems appeared)
clarification: I only need the "daylight on" to trigger something, "daylight off" is not needed, hence it doesn't trigger anything. Still, I can see on and off in the log.
Regards, rws
-
- Posts: 155
- Joined: 02 Jan 2016 01:20
Re: Daylight32 & IF->THEN problems
Update: I just found out I have a similar problem with my minimote. This might actually help to debug it.
My Minimote is configured so that is transmits scenes. Two of the buttons are used to control a Fibaro Wall Plug and the other controls a Fibaro Roller Shutter 2.
Two minimote scene buttons are bound via if->then to a fixed button level of the Fibaro Wall Plug. Two minimote scene buttons are bound via if->then to a fixed button level of the Fibaro Roller Shutter. Now the Wall Plug works as expected, all good here.
The Roller Shutter on the other hand does not. I have a feeling that it might be related to the fact, that it doesn't update it's status properly. It always reports to be switched on, except when it's fully down. Then it reports being off. Clicking the on/off in the browser gui works as it should, but triggering the on/off from the minimote via if->then ONLY works in the direction OFF.
Is it possible that the direction only get properly transmitted depending on the current status ZWay "thinks" or "knows" the roller shutter has?
Kind Regards,
rws
Does this help
My Minimote is configured so that is transmits scenes. Two of the buttons are used to control a Fibaro Wall Plug and the other controls a Fibaro Roller Shutter 2.
Two minimote scene buttons are bound via if->then to a fixed button level of the Fibaro Wall Plug. Two minimote scene buttons are bound via if->then to a fixed button level of the Fibaro Roller Shutter. Now the Wall Plug works as expected, all good here.
The Roller Shutter on the other hand does not. I have a feeling that it might be related to the fact, that it doesn't update it's status properly. It always reports to be switched on, except when it's fully down. Then it reports being off. Clicking the on/off in the browser gui works as it should, but triggering the on/off from the minimote via if->then ONLY works in the direction OFF.
Is it possible that the direction only get properly transmitted depending on the current status ZWay "thinks" or "knows" the roller shutter has?
Kind Regards,
rws
Does this help
Re: Daylight32 & IF->THEN problems
Did you ever find a solution or workaround?
I just updated my Z-Way install and I'm experiencing the exact same symptoms
I just updated my Z-Way install and I'm experiencing the exact same symptoms
-
- Posts: 155
- Joined: 02 Jan 2016 01:20
Re: Daylight32 & IF->THEN problems
Hi there,
unfortunately, no I haven't. As this is my outdoor Shade-Control and I won't need it until next Spring, I am hoping that the next release will fix this problem in the meantime. Lazy approach, I know.
Regards,
rws
unfortunately, no I haven't. As this is my outdoor Shade-Control and I won't need it until next Spring, I am hoping that the next release will fix this problem in the meantime. Lazy approach, I know.
Regards,
rws