*forgive me, I've used A.I to help articulate my problem*
I’m trying to troubleshoot what looks like a compatibility issue between a TP-Link Deco BE48-5G and certain 2.4 GHz IoT devices.
My internet is One NZ 5G Wireless Broadband, using the Deco BE48-5G as the main modem/router.
The main affected device is a eufy Indoor Cam 2K Pan & Tilt. I’m also having a similar issue with a Fujitsu AnywAIR controller.
The strange part is that the eufy successfully connects to the Deco:
2.4 GHz connection
strong signal
receives a valid LAN IP, e.g. 192.168.68.59
appears as an online client in the Deco app
But the camera itself stays offline in the eufy app and shows a blinking red LED, indicating it can’t establish its cloud/internet connection.
The camera is definitely not faulty because it works immediately when connected to my Samsung phone hotspot.
The most useful test I’ve done is this:
Deco Wi-Fi → Samsung phone → Samsung Wi-Fi sharing hotspot → eufy camera
For that test, I turned mobile data OFF on the Samsung. The phone itself stayed connected to the Deco Wi-Fi, then rebroadcast that connection through Samsung’s Wi-Fi sharing/mobile hotspot feature.
The eufy camera connected to the Samsung hotspot and worked perfectly.
So the internet path was still ultimately through the Deco/One NZ connection, but the camera was no longer directly associated with the Deco’s Wi-Fi.
That seems to suggest the issue is specifically related to how the Deco handles the eufy as a direct Wi-Fi client, rather than a general internet, cloud, or ISP problem.
Things I’ve already tried:
dedicated 2.4 GHz-only IoT SSID
WPA2-Personal
Fast Roaming disabled
Beamforming disabled
public DNS
firewall/DoS protection temporarily disabled
Device Isolation disabled
Camera Security / Local Only Mode checked
Network Access Control checked
IPv4-only APN profile tested
rebooted the Deco
checked for firmware updates
current firmware reports as fully up to date:
1.0.1 Build 20251114 Rel. 18794
tested the Deco using my Samsung hotspot as its upstream internet backup — the eufy still did not work when connected directly to the Deco
Another useful data point: I also have a Xiaomi C200, which is also 2.4 GHz-only, and that camera works normally on the Deco.
So this is not a blanket 2.4 GHz failure.
Current theory is either:
a Deco BE48-5G firmware/client compatibility bug affecting certain older IoT Wi-Fi chipsets, or
some lower-level Wi-Fi behaviour such as management frames, multicast/broadcast handling, ARP, NAT state, client isolation behaviour, or similar that the eufy doesn’t tolerate.
I’m considering putting a different-brand router behind the Deco and connecting the eufy/AnywAIR to that instead, since the Samsung Wi-Fi-sharing test effectively proves that another Wi-Fi layer fixes it.
Has anyone seen something similar with Deco Wi-Fi 7 hardware and older 2.4 GHz IoT devices?
I’d especially be interested in whether there are any hidden/advanced Deco settings, firmware fixes, or known issues around IoT client compatibility that I haven’t already tested.
*One important detail: everything worked perfectly on this Deco setup until about 2–3 months ago. Then, without me deliberately changing the network setup, certain devices suddenly stopped being able to reach the internet/cloud through the Deco. Other devices still work normally. That makes me wonder whether this is related to a firmware update, backend change, or some compatibility regression rather than a permanent hardware limitation.
Source: r/HomeNetworking · by /u/Crash_lolo