Tutorial · updated 2026-05-28 · 1 min read
Set WLED controller addresses without breaking sync
Before assigning static IPs to multiple WLED nodes, make sure the addresses, gateway, and subnet belong to a sane local network.
WLED sync problems get much harder when every controller has a hand-entered address that does not match the rest of the LAN. If one node disappears after changing the IP, undo the network experiment before tuning LED presets.
Use a normal address plan
- Put every WLED controller on the same LAN as the device sending sync data.
- Prefer DHCP reservations in the router over static addresses typed into each controller.
- If you must set static IPs, use the router’s real subnet, gateway, and DNS values.
- Avoid unusual ranges for a home setup unless the entire network is intentionally designed around them.
- Change one controller at a time and verify the web UI before moving to the next.
Then test lighting behavior
After each controller is reachable, test WLED preset sync, UDP settings, and any software that sends live color data. Rhythm can sit above a stable lighting network for room state and scenes, but packet routing and controller addressing have to be correct first.