I probably should be banned from this forum! The issue actually lied in my cfg.json
settings –
I was directly editing the file (rather than using the browser’s Sync Interface
), and it turns out that I had overlooked the "btn":true
requirement for the sender! None of the naïve hackery I proposed in the previous posts was necessary at all! Don’t do it! It’s heresy!
Bottom line… multi-segment UDP sync works like a CHAMP with v0.13.1 … just get your Sync Interface
settings right! Here are mine:
-
Sender
cfg.json
settings"if":{ "sync":{ "port0":21324,"port1":65506, ... "send":{ "dir":true,"btn":true,"va":false,"hue":true,"macro":false,"twice":true,"grp":1 } },
… you may ignore the Philips Hue setting…
-
Receiver
cfg.json
setings"if":{ "sync":{ "port0":21324,"port1":65506, "recv":{ "bri":true,"col":true,"fx":true,"grp":1,"seg":true,"sb":true }, ... },
-
For illustration, the combined web interface settings for receiver (red) and sender (green)
I’m currently running “stress” tests, but I think this issue should be closed…