Hello, My issue is similar to this question . I’m currently using v0.13.1, and as discussed @ here , “multi-segment UDP sync” should work as of v0.13. When the following is set in cfg.json "if":{"recv":{...,"seg":true,"sb":true} (i.e. receiveSegmentOptions and receiveSegmentBounds, resp.) things s…

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 …

Sorry guys, Actually sync’ing individual presets works… this is how I achieved this already! It must have slipped my mind as I did it quite some time ago… I’m re-inventing the wheel and I just have to figure out what I’ve messed up in this new implementation… Regards, Gbd

I think I’ve identified the issue. But since I haven’t yet fully analyzed the pertinent WLED internals, I’ll leave the final say to the maestros. When a preset change is due to UI, or API over HTTP, or API over serial communication, callMode == CALL_MODE_DIRECT_CHANGE (notifyDirect == true). This …

One more thing: It seems that with UDP sync, it’s best not to omit the {"stop":0} segment objects when sending preset JSON API. While omitting these objects – in the interests of more compact data transfers – may not cause problems when remotely updating the state of a “stand-alone” WLED instance, …

Thanks for posting this info. @gbd - I’m wondering if you have any pointers for me on firing UDP packets at WLED to control individual segments. I can control basic stuff like brightness and FX, but it only seems to apply whatever the selected segments are, rather than being assignable through the…

@beatKeeper Do you mean explicitly packing WLED multi-segment preset JSON into a UDP message from a custom/stand-alone program (just like udp.cpp::notify() does), and then sending this to a WLED instance?

Would it be heresy to simply replace CALL_MODE_BUTTON_PRESS with CALL_MODE_DIRECT_CHANGE? As in: void decodeIRJson(uint32_t code) { ... cmdStr = fdo["cmd"].as<String>(); jsonCmdObj = fdo["cmd"]; //object if (jsonCmdObj.isNull()) // we could also use: fdo["cmd"].is<String>() { ... …

Basically, yes. I’m using a Python script to fire UDP packets at a WLED instance. Until I figure out what I’m doing, I’m putting this at the byte level, manually creating the data payload to make sure I know what I’m changing. So in that sense I’m pretending that I’m another instance of WLED noti…

@beatKeeper What version of WLED are you using? Multi-segment UDP sync support was introduced in 0.13 . However, you should be using at least v0.13.1 (since v0.13.0 is not recommended – has a “critical” bug w/ presets creation)…

@gbd - Just want to be clear. I can make this work firing JSON at the WLED - controlling individual segements. Just trying to figure out how to get the same result through a UDP packet so it’s faster.

Multi-segment UDP sync via IR remote

Issues

beatKeeper November 17, 2022, 10:12pm 18

Just got it posted:

Topic		Replies	Views
Sending Multi Segment UDP Packets to WLED Integrations	10	1062	March 21, 2024
Are presets supposed to work with UDP Sync? Questions	10	967	December 6, 2022
Directly send sync broadcast from Python Questions	1	60	July 16, 2026
How to "erase" segments? Questions	26	4547	December 9, 2020
Generate UDP realtime WARLS data for sync Enhancements	0	1050	September 15, 2021

Multi-segment UDP sync via IR remote

Related topics