• 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
Question Pi 3+ & pilight & 433Mhz RXB6: no receiption hacklschorsch 3 382 02-05-2019, 10:37 PM
Last Post: hacklschorsch
  pilight not working with fresh Openhab 2 image habitoti 2 221 01-24-2019, 08:44 PM
Last Post: habitoti
  REST API problem kaku_screen_old / elro_800_switch with pilight 8.1.4 pisperate 4 217 12-20-2018, 09:26 PM
Last Post: pisperate
  pilight v8.0 - Current work in progress curlymo 32 19,327 12-06-2018, 10:06 PM
Last Post: curlymo
  RPI3 b+ Raspbiam Stretch and pilight-7_oregon Tueftler1983 1 240 12-04-2018, 11:59 PM
Last Post: Tueftler1983
  pilight integration in ioBroker Trashware 2 1,185 11-29-2018, 09:14 PM
Last Post: bnk72
  Config migration from pilight 7 .0 to 8.1.3 "Rules" Nonaamee 4 495 11-17-2018, 08:35 PM
Last Post: Nonaamee
  pilight-daemon does not start since 8.1.3-21 robertkrause 1 418 11-05-2018, 07:01 PM
Last Post: robertkrause
Exclamation Brennenstuhl 433MHz RC C1 - pilight not work pitje87 0 379 10-31-2018, 12:38 PM
Last Post: pitje87
  new pilight versions needs new pakets JoeC. 10 2,945 10-16-2018, 05:31 PM
Last Post: Dimi66

Forum Jump:


Browsing: 1 Guest(s)