My desk lighting comes from several makers: motherboard, RAM, aRGB fans, rear light strips, and floor lamps. SignalRGB brings those separate devices under one system so they can act together.
I chose WiZ because Philips Hue and Nanoleaf were beyond my lighting budget. SignalRGB doesn’t officially support WiZ, but third-party GitHub plugins can connect it. Getting that working took more network troubleshooting than I’d expected. These notes are for anyone who hits the same problem, including me if I need to set it up again.
WiZ App Settings: 2.4GHz Connection and Local Communication Permissions
Due to hardware limitations, WiZ devices must be connected to a 2.4GHz Wi-Fi band to function properly. Ensure you switch your connection to 2.4GHz before starting the app configuration. Once setup is complete, you can connect your main PC to a 5GHz network or a wired LAN; as long as they are on the same subnet under the same router, they will communicate fine. You must also enable control permissions in the smartphone app; otherwise, the lights will ignore all external control signals. Follow these steps:
- Launch the WiZ V2 app on your smartphone.
- Tap the ‘Gear’ icon in the top right corner of the home screen.
- Go to the ‘Security’ menu under the current Home section.
- Enable the ‘Allow local communication’ switch.
- Select ‘Allow all controls’.
SignalRGB Settings: Adding the WiZ Direct Plugin
Adding WiZ support means installing an external plugin. You don’t have to move script files manually: SignalRGB can load the plugin from its URL. Here’s the sequence I used:
- Launch SignalRGB on your desktop.
- Go to the settings menu via the gear icon at the bottom of the left tab.
- Select the ‘Addons’ menu (puzzle piece icon).
- Paste the GitHub address into the plugin search/input box at the top.
- URL: https://github.com/GreenSky-Productions/SignalRGB-WIZ-Network-Plugin
- Turn on the power switch for the newly created ‘WIZ Network Plugin’ in the list.
- Ensure the branch is set to ‘main’.
PC Network Settings: Passing the Firewall via Private Network Profile
I finished both the phone-app permissions and the plugin setup, yet discovery still sat there loading indefinitely. That made the problem more confusing than a simple missing setup step. The console reported that the communication socket had opened, which suggested that something had started, but the lights were not appearing. I spent some time working through that gap between an apparently active connection and an empty device list. Eventually, I found that the cause was the Windows Firewall policy tied to the network profile. Getting the app and plugin in place was only part of making the communication work.
When the discovery script broadcasts packets, the WiZ lights send response packets containing their unique IP addresses back to the PC. If your Windows network profile is set to ‘Public,’ the firewall will block these unfamiliar response packets. To resolve this:
- Open Windows Settings and go to ‘Network & internet’.
- Open the properties window for your currently connected Wi-Fi or Ethernet.
- Change the Network Profile type to ‘Private’.
- Power cycle your WiZ lights (turn the physical switch off, wait 5 seconds, then turn it back on).
- Completely exit and restart the SignalRGB process.
Wrapping Up the Sync Setup
Once the firewall issue was resolved, the lights’ IP addresses finally appeared in the console. Seeing them there was the sign that communication was working, and the lights then became available in the device layout for synchronization. The motherboard, aRGB hardware, and room lighting could follow the same game effects or audio beat together. Watching products from different manufacturers move with the screen as one coordinated setup made the debugging feel worthwhile. It was the result I had wanted from the mix of light strips, floor lighting, and PC components at the start.
A coordinated lighting setup doesn’t have to rely entirely on expensive products. I hope the mistakes recorded here save someone else a little time.
