If your Deco mesh went offline right after you switched the WAN connection to a static IP, the usual cause is a bad WAN setting or an ISP requirement you missed, not a failed Deco. First, confirm you changed the Deco WAN side and not just a device on your LAN. Then check the four WAN values: IP address, subnet mask, default gateway, and DNS. If those are right and the modem or ONT still looks healthy, the next suspects are Router mode vs Access Point mode, MAC binding, VLAN tagging, or PPPoE.
What usually breaks when Deco stops online after static IP
Most of the time, the Deco itself is fine. The problem is that the static WAN details no longer match what the ISP or upstream device expects. The mesh may still look normal inside the app, while internet traffic never gets through.
The symptoms point to different failures:
- Wrong IP address or subnet mask: the Deco may not get a usable upstream connection at all.
- Wrong default gateway: the Deco can look connected to the modem or ONT, but traffic stops there.
- Wrong DNS: you may still reach sites by IP address, but names like
example.comfail to load.
That split matters because DNS-only problems are annoying but usually easy to fix. A bad IP, subnet mask, or gateway is a different problem entirely. It will keep the Deco offline no matter how healthy the Wi‑Fi looks inside the home.
Is the static IP on the Deco WAN or on one device in your home
This is the first thing I would separate before changing anything else. A WAN static IP changes how the Deco itself reaches the internet. A LAN fixed address only gives one device in your home the same local IP every time.
If you meant to keep a printer, NAS, or Home Assistant box on the same local address, a DHCP reservation is usually the better choice. It leaves the WAN link alone and tells the Deco’s DHCP server to hand that device the same LAN address each time. The Home Assistant discussion also shows a common trap here: the Deco app only offers static assignment for devices it recognizes on the local network. A device that already has an address in another way may not appear where you expect.
If the internet broke right after you edited the WAN settings, undo that change first. Then use a reservation for the device instead. If the WAN was never touched, you probably have a LAN addressing issue, not a dead mesh.
Check the four WAN fields before anything else
Before you chase ISP settings or reset the mesh, verify the four WAN values together. All four need to match the handoff exactly: IP address, subnet mask, default gateway, and DNS.
Use the symptom to narrow the fault:
- If the Deco never comes online or cannot pass traffic at all, suspect the IP address or subnet mask.
- If the Deco seems to connect but nothing leaves the modem or ONT, suspect the default gateway.
- If the internet works by IP but not by name, suspect DNS.
If you are not sure which field is wrong, fix the IP address, subnet mask, and gateway first. DNS comes last, because a DNS-only mistake does not usually explain a full WAN outage.
Why it works on DHCP but fails on static IP
DHCP works because the ISP or upstream device hands the Deco the right settings automatically. The moment you switch to static, you take over every part of that handoff. That includes any hidden requirement the ISP was handling for you.
That is why a setup can work perfectly on DHCP and fail immediately on static IP. A modem or ONT may also be part of the problem. This is especially true if it is still expecting the old handoff or if the ISP has locked service to the first router it saw.
Mode matters here. In Router mode, the Deco owns the WAN connection, so the static IP settings directly control internet access. In Access Point mode, the main router or ISP gateway usually owns the WAN side, so the Deco’s own WAN static setting often is not what decides whether the internet works. If you are in AP mode and the internet died after a static change, check the upstream router or gateway first.
There are also ISP rules that can block a correct-looking setup:
- MAC binding: the ISP may tie service to the first MAC address it saw, so a different router or a changed WAN MAC can fail until the ISP updates it.
- VLAN tagging: some providers require a specific VLAN tag on the WAN, and the connection fails without it.
- PPPoE: some ISPs require a PPPoE username and password instead of plain static IP settings, so the address fields alone are not enough.
If those requirements are missing, the Deco can look configured correctly and still stay offline.
The safest recovery order and when to call the ISP
Start with the least risky check and keep a way back to the last working setup. If DHCP worked before, that is your recovery path.
- Switch the Deco back to the last working WAN setting, usually DHCP, and see whether internet returns.
- Check the modem or ONT before blaming the Deco. Confirm it has a normal internet or online light and that the upstream device itself still has service.
- If DHCP works again, the issue is probably the static WAN details or an ISP requirement that the static setup missed.
- Re-enter the static IP only after you have the exact
IP address,subnet mask,default gateway, andDNSfrom the ISP. - If it still fails, check whether the ISP expects MAC binding, VLAN tagging, or PPPoE, and whether the Deco is in Router mode or Access Point mode.
If you still cannot get online after the rollback test, call the ISP. Give them the exact WAN values you entered, the Deco mode, the modem or ONT model, and whether the service requires MAC binding, VLAN tagging, or PPPoE. That is usually enough for them to tell you whether the block is on their side or in the Deco settings.
Verify the fix
Once you make the change, confirm the result in the same order you diagnosed it.
- If you switched back to DHCP, the Deco should come online again and clients should regain internet access.
- If you kept static IP, the WAN status should show a usable internet connection, not just a local link to the modem or ONT.
- If DNS was the issue, websites should load by name after the DNS values are corrected.
If the Deco still fails after the rollback test, stop changing settings one by one. Collect the exact WAN details before another attempt. At that point, the problem is usually the ISP handoff, not the mesh hardware.
Conclusion
If the mesh went offline right after the static IP change, back out of the WAN edit first. Then reapply the static settings only after you have the ISP’s exact values and any special requirements. If you were really trying to fix one device on your LAN, use a DHCP reservation instead of a WAN static IP.
Frequently Asked Questions
Should I use a DHCP reservation instead of a true static IP?
Yes, if you only want one device in your home to keep the same local address. A DHCP reservation is usually the better choice for printers, NAS boxes, and home servers. It avoids changing the WAN connection that keeps the Deco online.
Does access point mode ignore the Deco static IP setting?
Usually it does for the internet handoff, because the main router or ISP gateway owns the WAN connection in AP mode. The Deco can still manage local Wi‑Fi, but the upstream addressing problem is often elsewhere.
When is a factory reset justified?
Only after you have confirmed the modem or ONT is healthy, the DHCP rollback works or has been ruled out, and you know the ISP handoff details are correct. If you reset too early, you can make a recoverable WAN problem harder to unwind.
Sources
- Static ip on deco mesh - Configuration - Home Assistant Community (community.home-assistant.io)