• 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
Consecutive pilight commands
#1
Hi,

in an older Openhab installation from ~2 years ago (not sure what pilight version was current at that time) I had a shell script that executed multiple pilight commands consecutively, and it had no issues to do so. The lights went on/off almost at the same time. 
With a fresh installation now and pilight 8.1.4, none of those consecutive commands is doing something (not even just the first or the last). Only if I separate them by at least a "sleep 0.2" they do their magic (sending a lengthy raw sequence). While this is not a problem within one script, I am curious whether this might lead to malfunctions if separate calls from different places in my home automation environment are called at the same time (e.g. Alexa "switch off all").

Or is there a "new way" of making such calls work properly in direct succession?

Regards, habitoti
 
Reply
#2
No, the reason it worked before was the performance of pilight itself. It was too slow enough in parsing these commands. Due to the parsing speed of the current pilight version, commands are sent too fast causing 433.92Mhz interference. The only workaround at the moment is the small delay.
 
Reply
#3
Hm, ok...

Would maybe be great if pilight would provide an -- optional/configurable -- global queue (per sender channel) in the future that would prevent sending something in shorter succession than configured. Even parallel requests from different callers would be strictly sequenced with an appropriate pause in between.

Regards, habitoti
 
Reply
#4
Exactly that feature is being discussed in the MQTT PR on github Smile
 
Reply
#5
Another preliminary „cheap“ option would be to make pilight optionally „slow“ again by having a parameter for an artificial delay/sleep amount. So I could ask pilight to not return before so-and-so many milliseconds have passed. This would probably be sufficient for the majority of cases in home automation usages.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 31 455 13 minutes ago
Last Post: Alex
  Raspberry PI, gpio-ir-tx and pilight not starting lordslash 5 45 06-11-2019, 05:19 PM
Last Post: curlymo
  pilight fails starting on boot Alex 5 114 06-09-2019, 06:02 PM
Last Post: curlymo
  Google Assistant coupled to pilight hansrijn2 4 505 05-29-2019, 06:54 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 146 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 166 05-15-2019, 08:03 AM
Last Post: va13
  cant configure or even start pilight on raspi 3b Xvnx23 2 155 05-06-2019, 09:47 PM
Last Post: fourty2
Sad Raspberry Pi: "NOTICE: no pilight ssdp connections found" abusch 8 238 04-30-2019, 09:10 PM
Last Post: curlymo
  Using pilight-daemon socket API def_meggi 4 149 04-29-2019, 05:58 PM
Last Post: curlymo
  pilight-flash not working danny 9 278 04-27-2019, 09:02 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)