← Back to Community

Control4 Not Working After a New Router or Mesh Wi-Fi?

By Ixome · Control4 & Lutron service•6 min read•Published •Updated

Free: what can your Control4 controller still do? →

A new router is one of the most common reasons a Control4 system that was working fine stops answering. It might be a new internet-company router, a mesh Wi-Fi kit, or an extra router added for weak Wi-Fi. Usually nothing is broken. The parts of the system just can't find each other anymore, and most of that can be fixed in the router.

A small white mesh Wi-Fi unit on a bookshelf in a bright living room
Illustration

Why a new router breaks Control4

Every device on a home network gets an address from the router. This is called DHCP. A new router hands out new addresses, and often a whole new range: one router uses addresses starting 192.168.1, the next 192.168.0. Google Wifi, for example, uses 192.168.86 by default.

Control4 keeps track of devices in one of two ways:

  • Devices that announce themselves. Control4's discovery protocol, SDDP, lets a device tell the system who and where it is. Control4 says SDDP identifies a device even when its address changes. These usually come back on their own.
  • Devices set by an IP address. Many others have an address typed into the Control4 project. If that device moves, the system keeps looking at the old address. As a Control4 engineer put it on the C4 Forums, without SDDP Control4 has no way to know the address changed.

That's why the damage looks random: some things work and some don't.

What it usually looks like

  • The app can't find the system. Control4's app guide says that if you're on the same Wi-Fi and the app still can't find the system, the network is set up in a way that stops the app from seeing it.
  • One device stops responding. A TV, receiver, streamer or amplifier set by IP stops answering. One owner on the C4 Forums could still switch inputs after a new modem and router, but had lost volume control.
  • Lights from another brand go quiet. One owner on r/Control4 lost Control4's connection to Lutron lights and shades after upgrading the router.
  • Switches and keypads stop responding in the app and in schedules. That can be the network or the radio (see below).
  • Nothing works, and the controller isn't in the router's device list. This often means the controller has a fixed address from the old network.

Step 1: Find the controller

Log in to the new router, or open its app, and find the list of connected devices. Control4 hardware has a hardware (MAC) address starting 00:0F:FF, the block registered to Control4. Write down the address the controller has now.

If the controller has power and a link light but isn't in the list, it probably has a fixed address from the old network. In one C4 Forums thread, the controller was fixed at 192.168.1.15 and the new router handed out 192.168.0 addresses. Setting the new router to the 192.168.1 range brought back both the controller and the app.

Check for two networks as well. When a mesh system is plugged in behind an existing router, eero describes the result as "two separate networks." A phone on one can't find a controller on the other. The usual fix is to put the mesh system in bridge mode, or the internet company's box in bridge mode, so there's only one network.

Also check which Wi-Fi the phone is on. Snap One's checklist turns on "client isolation" for guest networks, which keeps devices from seeing each other, so the app won't find the system from the guest Wi-Fi.

Step 2: Match the old network, or lock in today's addresses

The cleanest fix is to make the new router look like the old one. That means the same address range, the same reservations (each device's hardware address paired with its old address), and the same Wi-Fi name and password. If the old router still powers on, copy those pages first. If this works, nothing in the Control4 project has to change.

If the old addresses are gone, reserve the addresses devices have now. A DHCP reservation tells the router to give a device the same address every time. Reserve the address each device is on today. If you reserve a different one, the device moves to it the next time it renews or restarts, and anything that had found it loses it again. Start with the controller. Snap One's checklist sets networks up this way: DHCP, fixed addresses only when required, and reservations for key equipment.

Then the drivers set by IP need the new addresses. That's a change to the Control4 project, made in Composer Pro, which is dealer software. A Control4 dealer on the forums points out that Composer HE, the owner's edition, can't change network connections. It's a small job and can be done remotely when someone can reach the system.

Don't factory reset the controller. Control4's installation guide warns that a factory restore removes the Composer project. The controller has a separate network-settings reset that leaves the project alone. A dealer may ask you to use it, but it isn't a first step.

Why Control4 switches go offline after a Wi-Fi change

Control4 wireless switches, dimmers and keypads don't use the router. They talk to a controller over Zigbee, their own mesh network on the 2.4 GHz band. A new router can still knock them out in two ways.

The network path. One controller runs the Zigbee mesh. Control4's design guide recommends a second controller for this where possible, wired to a reliable network so it can reach the main one. If that controller lost its address in the router change, every switch on its mesh goes quiet as far as the system is concerned.

The radio. Wi-Fi and Zigbee share the 2.4 GHz band. Control4 uses Zigbee channels 11 to 25, which overlap Wi-Fi channels 1 to 11. A Zigbee channel is 2 MHz wide and a Wi-Fi channel about 22 MHz, so one Wi-Fi channel covers several Zigbee channels:

  • Wi-Fi channel 1 overlaps Zigbee 11 to 14
  • Wi-Fi channel 6 overlaps Zigbee 16 to 19
  • Wi-Fi channel 11 overlaps Zigbee 21 to 24
  • Zigbee 15, 20 and 25 sit in the gaps. These are the channels Control4 recommends.

Control4 says the controller picks its Zigbee channel once, at setup, and never checks again. A new router that puts its 2.4 GHz Wi-Fi on top of that channel can make switches slow or drop out. Placement matters too: Control4 warns that a Wi-Fi router or access point right next to the Zigbee controller can drown out Zigbee even when the channels don't overlap. Keep them at least 5 meters (15 feet) apart.

Fix the Wi-Fi side. Ask a dealer which Zigbee channel the system uses, set the router's 2.4 GHz channel by hand so it stays clear, and move any new mesh unit away from the controller. Snap One's checklist also sets the 2.4 GHz band to 20 MHz wide, turns band steering off, and assigns channels by hand rather than on auto. Not every consumer mesh system offers all of these settings. Changing the Zigbee channel itself is done in Composer.

What you can do, and what needs a dealer

  • In the router, yourself: find the controller, match the old Wi-Fi name and password, restore the old range and reservations or reserve today's addresses, put a second router in bridge mode, and move the 2.4 GHz channel and the mesh units.
  • In Composer Pro, a dealer: point drivers set by IP at their new addresses, re-identify devices, and change the Zigbee channel.

Before the next router change

Keep a one-page list: device, hardware address, reserved address. Back up the router's settings. Then whoever installs the next router can copy the range and reservations across before anything is unplugged.

For a second opinion, ixome.ai can check a Control4 system remotely and tell you which of these you're dealing with.

What can your Control4 controller still do?

Three questions: which OS it can reach, whether it will register, and whether it can be done remotely. Free, no signup.