This object is in archive!
How to use Virtual Switch in IF Rule
Need Answer
Hi,
I want to use a virtual switch in a IF block (the behaviour of the rule depends on the switch status when the Rule is fired).
Is it possible?
I think I tried every combinations possible, but that never worked...
Thank you for your help
Files:
zipa.JPG
The same question 
No connection
Real-time notifications may not work
This one trigs every time that "Z Solen uppe" goes "ON".
This one trigs every time that "Z Solen uppe" goes "ON".
Thank you.
But that I want to do is to allow or avoid the action of the rule (here send a message) with the status of "Bloque Store" Switch. The Rule is triggered by "Test Switch", if "Bloque Store" is ON do something, if "Bloque Store" is OFF do nothing.
May be there is another solution to do that.
My goal is to prevent a roller shutter controled by a Fibaro module and a electrical switch to move even if the the roller shutter receive the order to move from the electrical switch (in fact neutralize the electrical switch).
Thank you.
But that I want to do is to allow or avoid the action of the rule (here send a message) with the status of "Bloque Store" Switch. The Rule is triggered by "Test Switch", if "Bloque Store" is ON do something, if "Bloque Store" is OFF do nothing.
May be there is another solution to do that.
My goal is to prevent a roller shutter controled by a Fibaro module and a electrical switch to move even if the the roller shutter receive the order to move from the electrical switch (in fact neutralize the electrical switch).
Sorry. I didn't think that part was a problem.
Sorry. I didn't think that part was a problem.
Wrong language. In English.
Wrong language. In English.
Alain, are you perhaps experiencing the virtual switch state synch problem that happens after reboots or disconnects?
What are you seeing? Does the message never get sent? Or always get sent?
Alain, are you perhaps experiencing the virtual switch state synch problem that happens after reboots or disconnects?
What are you seeing? Does the message never get sent? Or always get sent?
Hello,
I dont know for the rule synch, but it's very long...
The message is never sent.
Actually I did exactly what henryfredrikson suggested, without success.
I tried using the http switch as Actuator (Attribut Events=On) or as Control (Attribut Events=On or Action Events)
Hello,
I dont know for the rule synch, but it's very long...
The message is never sent.
Actually I did exactly what henryfredrikson suggested, without success.
I tried using the http switch as Actuator (Attribut Events=On) or as Control (Attribut Events=On or Action Events)
Try a couple of things:
1) Toggle your Bloque Store switch twice, to make sure that it's really on. Sometimes what happens is that we are seeing a switch as "on" in the cloud, but because of a disconnect or reboot it's actually off in the Zipabox's memory. (off, or in a "null" state). Toggling the switch twice will resynch it and ensure it's on. Then run your test rule and see if it works. If it does, this is your problem.
2) Try using a variable instead of a virtual switch, if you can. See if that works.
If 1) is confirmed, then you might find that 2) works more reliably. Also look up "reboot detector" to see what Henry and I have done to get around the state synch problem.
Try a couple of things:
1) Toggle your Bloque Store switch twice, to make sure that it's really on. Sometimes what happens is that we are seeing a switch as "on" in the cloud, but because of a disconnect or reboot it's actually off in the Zipabox's memory. (off, or in a "null" state). Toggling the switch twice will resynch it and ensure it's on. Then run your test rule and see if it works. If it does, this is your problem.
2) Try using a variable instead of a virtual switch, if you can. See if that works.
If 1) is confirmed, then you might find that 2) works more reliably. Also look up "reboot detector" to see what Henry and I have done to get around the state synch problem.
I should also say that, if you have the state synch problem, Zipato claim that it's fixed in the newest beta firmware. But I can't confirm that yet. I'm still testing. You could try the beta firmware to see if it helps.
I should also say that, if you have the state synch problem, Zipato claim that it's fixed in the newest beta firmware. But I can't confirm that yet. I'm still testing. You could try the beta firmware to see if it helps.
David, you got it.
I moved the Bloque Store Switch a couple of times and ... it works !!!
Thank you all for your help.
(grrrr 2 hours just for that and my home credibility at very very low level...)
David, you got it.
I moved the Bloque Store Switch a couple of times and ... it works !!!
Thank you all for your help.
(grrrr 2 hours just for that and my home credibility at very very low level...)
Right, so it's definitely the switch state synch problem. The web interface is "lying" to you about its true state.
1) Try a variable
2) Try updating the firmware
3) Try setting up a rule to detect reboots and reset the switch states after the reboot
4) If the switch state is something that you can derive from basic information like time/date etc, try setting up a rule to recalculate its state every 10 minutes or half an hour or whatever.
Right, so it's definitely the switch state synch problem. The web interface is "lying" to you about its true state.
1) Try a variable
2) Try updating the firmware
3) Try setting up a rule to detect reboots and reset the switch states after the reboot
4) If the switch state is something that you can derive from basic information like time/date etc, try setting up a rule to recalculate its state every 10 minutes or half an hour or whatever.
Replies have been locked on this page!