• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
All remotes should switch via pilight
#1
Hello,

I am a new pilight user and thank you very much for this project, pilight is really a nice product!

I use pilight 7.0, v65534 on a Raspberry PI 3, a 433 MHz sender and -receiver.

I have some different ERLO switches with 3 different remotes, i. e. 1 remote with 2 switches for kitchen light, 1 remote with 4 switches in living room for evening light, etc.

I set up pilight and I am able to switch all devices via webGUI without any problems - it works great.

My problem: Since the RPI is located in the living room and when someone is using the "kitchen remote" for switch on the light in the kitchen, pilight does not get this signal and the state of this switch in pilight is not like the status of the light in the kitchen (ON/ OFF).

So, I changed the "DIP Switches" (is it english?) of each remotes to another systemcode and configured "virtual switches" in config.json. In fact of that, each remote doesn't switch the switches directly - just the virtual switches in pilight. I set up some rules like that:
Code:
"vitrinean": {
    "rule": "IF Switch10.state IS on THEN switch DEVICE Switch1 TO on",
    "active": 1
}
I included also this "virtual Switches" for testing reasons in the webGUI. When I use them, everthing is working fine, too. pilight is able to switch light in each room from the living room.

But when I switch these switches with any remote (remote --> pilight --> physical switches) it does not work. The switches in the webGUI changes, but the physical switches do not, like, when I use the GUI direct - sometimes they do, sometimes not.

I hope it is clear: I tried that, because I would like to have anytime the "real state" of my lights in pilight.

Any help are welcome.

Thank you, Laret
 
Reply
#2
Add a delay before switching the real switch.
 
Reply
#3
Thank you for the hint!

I updated my rule to:
Code:
"vitrinean": {
    "rule": "IF Switch10.state IS on THEN switch DEVICE Switch1 TO on AFTER 800 MILLISECOND",
    "active": 1
}
...and it works.

Best regards, Laret
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Tongue pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 4 83 08-17-2019, 01:04 PM
Last Post: curlymo
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 1,488 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 335 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 228 07-14-2019, 08:32 AM
Last Post: curlymo
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 47 1,979 06-29-2019, 08:58 PM
Last Post: curlymo
  Raspberry PI, gpio-ir-tx and pilight not starting lordslash 5 523 06-11-2019, 05:19 PM
Last Post: curlymo
  pilight fails starting on boot Alex 5 461 06-09-2019, 06:02 PM
Last Post: curlymo
  Google Assistant coupled to pilight hansrijn2 4 895 05-29-2019, 06:54 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 454 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 509 05-15-2019, 08:03 AM
Last Post: va13

Forum Jump:


Browsing: 1 Guest(s)