WLED icon indicating copy to clipboard operation
WLED copied to clipboard

UDP sync unreliable

Open ThatBigPrint opened this issue 4 years ago • 7 comments

Describe the bug First issue,

when I have multiple wled modules one or two of them don't sync properly you then need to resubmit the change then it applies this is intermittent.

second issue,

the wled app finds the uniquely named modules but after you click the tick it only populates a few but if you manually type in IP address it populates as it should ?

To Reproduce first issue you just need multiple items on one sync id for instance I have 11

second issue again multiple items on same network I have 15 in this instance

Expected behavior all wled to sync reliably

app to be able to find nodes every time and populate

WLED version

  • Board: [e.g. ESP32 dev]
  • Version [e.g. 0.13.0, beta] although other nodes I'm having the same issue with are on stable old releases
  • Format [e.g. Binary, self-compiled] both

Additional context Anything else you'd like to say about the problem?

Thank you for your help!

ThatBigPrint avatar Aug 01 '21 16:08 ThatBigPrint

How many wifi access points do you have? Are all WLED installs connect to the same wifi AP? The sync protocol does not route as far as I know since it's a simple UDP broadcast. WLED simply sends out to whoever is capable of listening, and is listening. The networking configuration determines whether they are capable of listening.

huggy-d1 avatar Aug 02 '21 13:08 huggy-d1

they are all on the same network they only produce ap if they can't find the known SSID ? so far they are all on the network and not complaining, the issue lies in reliable sync and pulling into the app on both platforms... they initially worked but since I deleted the list and re searched only one or two come back and its always the same one or two

ThatBigPrint avatar Aug 03 '21 06:08 ThatBigPrint

a bit more info on this... the Host light seems to drop out for whatever reason, and then comes back around it happens on all of the elements whichever is the host I'm even considering making a hidden dummy hoast? anyway use this link to see a video of the issues https://youtu.be/eC7rsYlEwow

thanks chris

ThatBigPrint avatar Aug 06 '21 19:08 ThatBigPrint

WLED Sync uses UDP. That is in itself enough said about reliability on WiFi. You can slightly improve the situation by telling WLED to transmit sync message twice. Use Settings page.

blazoncek avatar Aug 23 '21 10:08 blazoncek

We are experiencing the same issue even with double send turned on, we think it is something to do with maybe the "sync master" crashing and rebooting as it seems to drop off the network for a few seconds.... we are running this on a pico D4 so maybe hardware limitation but as far as I'm aware the d4 is pretty high up there in terms of processing power? and we don't get any dropped frames with large quantities of leds?

ThatBigPrint avatar Aug 26 '21 05:08 ThatBigPrint

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED!

stale[bot] avatar Apr 16 '22 09:04 stale[bot]

The sync feature relies on mDNS and UDP broadcasting. Depending on your networking equipment and topology, these two features may or may not be enabled/blocked. I found with the default settings on my network, that enumerating the WLEDS on the network was unreliable as was syncing and that nodes would periodically drop off the network. After enabling mDNS and making sure UDP broadcasts would get through, everything started to work reliably.

keck9939 avatar Dec 04 '22 01:12 keck9939

Mitigation added in #2830

blazoncek avatar Jan 25 '23 12:01 blazoncek