Fix broken Sync button after 0.15 refactor

[Arcitec]

(Pull request to fix the broken Sync button, after previous discussions here: #4810 (comment))

Summary:

---

In the past, the "notify direct" flag controlled all network syncing, propagating all color changes to other devices on the network. Pressing the UI Sync button only toggled this flag, so "notify direct" was set to false by default.

In version 0.15, a separate "master" sync flag was introduced, and the UI Sync button now only activates this master flag. However, the rest of the flag defaults weren't configured to sync anything at all. As a result, users pressing Sync saw no syncing at all, leading to multiple bug reports.

Defaults are now user-friendly: Enabling Sync on a WLED device syncs all of its color changes, whether made via the UI, API or remote button, providing a consistent experience which matches the intended behavior from past WLED versions.

Philips Hue sync is now also disabled by default, making the stock defaults focused on WLED devices. Users with other RGB ecosystems can manually enable the Hue or Alexa syncing in the settings.

Summary by CodeRabbit

• Behavior Changes
  • Notifications for UI/HTTP actions are now enabled by default.
  • Notifications for button/IR remote actions are now enabled by default.
  • Notifications for Hue Bridge changes are now disabled by default.
  • Applies to fresh installs/resets using default settings; existing custom configurations are unaffected.
  • Expect more immediate notifications during direct control, with quieter behavior for Hue-driven updates unless re-enabled in settings.

[coderabbitai]

Walkthrough

Adjusted default initializers for three global notification flags in wled00/wled.h (non-PSRAM branch): notifyDirect and notifyButton set to true; notifyHue set to false. No type, signature, or other logic changes.

Changes

Cohort / File(s)	Summary
Notification defaults (non-PSRAM) wled00/wled.h	Changed default initializers: notifyDirect false→true, notifyButton false→true, notifyHue true→false. No other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7285efe and 4ac7eb7.

📒 Files selected for processing (1)

• wled00/wled.h (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

wled00/wled.h (2)

wled00/fcn_declare.h (4)

• bool (433-433)
• bool (434-434)
• bool (443-443)
• bool (444-444)

usermods/audioreactive/audio_source.h (1)

• bool (140-140)

🔇 Additional comments (1)

wled00/wled.h (1)

736-740: Sync defaults updated as intended (Direct/Button on, Hue off).

These initializers align with the PR goal: after enabling Sync (master switch), changes from UI/API/remote button will propagate; Hue is disabled by default.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.