Hey all,
I have created to virtual switches for to different shifts at work. Depending on the fact that either one of them or none (holidays or other exceptions) is set to On execute some actions at the time specified according to the shift.
Yesterday I activated the 830 button and closed the blinds. But this morning nothing happened (blind nor lights) as if the conditions were not met.
Any ideas why?
Blockly: timed (and conditioned) event not triggered
Moderator: leecollings
-
tozzke
- Posts: 135
- Joined: Friday 02 January 2015 9:22
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Stable
- Location: Netherlands
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
How did you close your blinds? Did you do it from Domoticz itself? or did you close them with another switch/app/button/whatever?
Or shouldn't it be If [shift830=on] and [Blinds=closed] and....?
Or shouldn't it be If [shift830=on] and [Blinds=closed] and....?
-
elmortero
- Posts: 248
- Joined: Sunday 29 November 2015 20:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.9639
- Location: Spain
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
The blinds are always managed by domoticz, either from mobile phone or remote control.
I will try the Closed status tonight, I used on/off as this is the command in the timers, where open/closed are not available. The status is however shown as open/closed.
Thanks for the tip, I will post update tomorrow after the test.
*update: in the logs the status of the blinds is always shown On/Off so not sure that this is the reason.
I will try the Closed status tonight, I used on/off as this is the command in the timers, where open/closed are not available. The status is however shown as open/closed.
Thanks for the tip, I will post update tomorrow after the test.
*update: in the logs the status of the blinds is always shown On/Off so not sure that this is the reason.
- Attachments
-
- blinds_stat.JPG (19.92 KiB) Viewed 1593 times
-
tozzke
- Posts: 135
- Joined: Friday 02 January 2015 9:22
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Stable
- Location: Netherlands
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
Well.... I have this just set up for testing purposes (don't actually have blinds or whatsoever)

and it seems to work quite well

and it seems to work quite well
-
elmortero
- Posts: 248
- Joined: Sunday 29 November 2015 20:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.9639
- Location: Spain
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
ok, thanks for the effort.
Having good hope for tomorrow morning.
Will let you know
Having good hope for tomorrow morning.
Will let you know
-
elmortero
- Posts: 248
- Joined: Sunday 29 November 2015 20:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.9639
- Location: Spain
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
It works!!
Yesterday it still didn't, at least the blinds part. The lights were switched on.
Conclusion: checking the state of the blinds uses Open/closed, in the Set part I needed to use On/Off.
So, this morning it was all working.
Yesterday it still didn't, at least the blinds part. The lights were switched on.
Conclusion: checking the state of the blinds uses Open/closed, in the Set part I needed to use On/Off.
So, this morning it was all working.
-
tozzke
- Posts: 135
- Joined: Friday 02 January 2015 9:22
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Stable
- Location: Netherlands
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
great! 
but why didn't it work at first yesterday?
but why didn't it work at first yesterday?
-
elmortero
- Posts: 248
- Joined: Sunday 29 November 2015 20:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.9639
- Location: Spain
- Contact:
Re: Blockly: timed (and conditioned) event not triggered
Well, the first time because I used On/OFF for both the IF and THEN block.
Second day because I used Open/Close for both.
In the end it had to be Open/Close when checking the state and On/Off for setting the state.
Now all is good (tested the 930 shift today).
Thank you for your help.
Second day because I used Open/Close for both.
In the end it had to be Open/Close when checking the state and On/Off for setting the state.
Now all is good (tested the 930 shift today).
Thank you for your help.
Who is online
Users browsing this forum: No registered users and 1 guest