Wyze Cam Floodlight Pro - "This device is offline" error but local AI/hardware is fully operational

Cameras
, ,
1

Hello everyone,

I’m hoping to get some insight into a bizarre and incredibly frustrating issue I’m having with my Wyze Cam Floodlight Pro. The camera is hardwired with constant power, but it has fallen into a state where the Wyze app continuously shows a “This device is offline” overlay with a frozen thumbnail.

Here is the catch: The hardware and local AI are 100% alive.

When I walk into the driveway, the camera physically tracks me, triggers the floodlight, and plays the local voice recording warning “You are being recorded.” It is executing its local automation perfectly, but it is experiencing a complete one-way cloud communication block and refuses to stream live video to the app.

My Setup:

Camera: Wyze Cam Floodlight Pro (hardwired directly into a garage ceiling junction box by an electrician, receiving constant power).

Network: TP-Link Deco Mesh system. I recently purchased and installed a brand-new Deco unit directly in the garage specifically to give this camera a pristine signal.

What I Have Already Done to Troubleshoot:

We have completely optimized the network side to the absolute limit, eliminating every standard Wi-Fi bottleneck, without success:

1. IP Address Reservation: Assigned a static DHCP IP reservation (⁠192.168.68.76⁠) inside the Deco app so the router never dynamically changes its slot.

2. Node Locking: Locked the camera strictly to the new Garage Deco node. The app explicitly states “This client will ONLY connect to Garage Deco.”

3. Wi-Fi Band Isolation: We tried locking the preferred band strictly to 2.4 GHz to eliminate band-steering confusion. We also tested switching it to 5 GHz to utilize the Pro’s dual-band capability for its high-res 2.5K data stream. Neither changed the offline status.

4. Disabled Advanced Router Features: Disabled both Fast Roaming and Beamforming globally/locally in the Deco settings to prevent dynamic packet shaping from dropping the camera’s wireless module.

5. Custom DNS: Changed the router’s WAN DNS from Auto to Manual, routing through Google’s public DNS (⁠8.8.8.8⁠ / ⁠8.8.4.4⁠) to bypass any ISP cloud handshake issues.

6. App & Phone Reset: Force-closed the Wyze app, cleared app caches, and cycled phone Wi-Fi connections.

The Core Problem:

Despite a flawless, dedicated Wi-Fi signal inches away from the garage node, the camera’s wireless module seems completely locked up regarding cloud sync. Because the electrician hardwired it directly to the garage circuit for constant power, I have no physical power switch to easily reboot the unit when it gets into this frozen state—forcing me to trip the main house breaker just to power cycle it.

Before I pay an electrician to come back out to install a physical inline toggle switch to force-reboot it, or change out the camera for a different one, has anyone seen the Floodlight Pro’s network module completely freeze up like this while the local AI/motion hardware continues to run perfectly fine? Is this a known firmware handshake glitch with mesh networks, or am I looking at a hardware defect in the camera’s wireless transmitter?

Any help or insight from the community or Wyze team would be greatly appreciated!

2

I don’t use Cam Floodlight Pro, so I can’t offer direct experience for this issue, but what comes to my mind is that some recent firmware for that Cam has apparently been problematic, and I didn’t see any mention of your current Cam Floodlight Pro firmware version or Wyze App version in your post. I also couldn’t tell from your post if your LAN indicates that it still has a connection to the Cam even when the Wyze app reports that it can’t connect. Determining that might help to narrow the scope of the problem.

In case you’re using beta firmware, note this:

You may wish to search other Wyze News and/or Beta category topics for posts related to whichiver specific firmware version you’re using.

3

I have seen something similar in the past On a couple of my FLPros (I currently have 6 actively deployed). Haven’t seen this for a long time though.

Besides making sure you’re on the latest firmware, what I would suggest considering trying before you pay someone to do something drastic is to force a factory reset on the floodlight Pro.
There have been a couple of times after a firmware update where the firmware didn’t fully take correctly. Forcing factory reset the device reload everything from scratch and fixed the issue for me. In another case I just waited through a couple of new updates and it just resolved itself.

But without waiting, try the factory reset. Basically, you go up and you press the reset button and hold it in firmly for something like 10 to 30 seconds or so (I think the instructions say 10 seconds, but I was pretty sure it took me 30 seconds to do this correctly). You’ll know it’s finally doing the factory reset with some kind of cue. I think the status light changes to red. Then let go of the button, let it reset and restart, and then go through setup again. That fixed my issues in the past.

Worst case scenario, yeah get a simple light switch installed that you can flip on and off to restart the camera manually.

If this was still happening to me on mine (again, I haven’t seen this for months or maybe even years now) I would probably set up some kind of automation using home assistant. Have it track when my FLPro goes offline

Like I said, I had this issue in the past and I don’t anymore, so hopefully it resolves itself for you.

What firmware version are you on?

Believe it or not, sometimes this causes an issue when the router signal is too close to a device.

This could also be the problem. I have frequently seen a lot of people report connection issues with Wyze on Deco routers. People have found the issue typically stems from a few things here:

Aggressive Band Steering (Smart Connect). While most routers use some form of band steering, for some reason the Deco routers have some kind of aggressive algorithm that sometimes causes issues with some IoT devices like Wyze’s Smart Cameras which need a consistent, smooth connection, not continual pushing to try something it doesn’t support.

“Fast Roaming” setting sometimes causes conflicts. Deco implements this more aggressively than others but for a stationary device that doesn’t have built in support for fast roaming, the conflicting requests may cause the cameras to repeatedly drop their connection or fail to authenticate because they cannot handle the constant “handshake” request to switch nodes.

Some TP-Link Deco models come with built-in “HomeCare” or “HomeShield” security features powered by Trend Micro.

In the past, users have reported that the malicious content filters or intrusion prevention systems in this software can falsely flag Wyze’s video traffic. I know in one case, it had banned all traffic that goes through TUTK (a popular Taiwanese company many IoT companies use for things such as authentication, including Wyze). Though people have been reporting that Wyze recently switched away from TUTK support, but it could be something similar interfering with your authentication.. In other cases, the software has been seen to mark keep-alive signals as suspicious, blocking the camera’s internet access.

Do you have your Wi-Fi set to WPA2 or WPA2/3 compatibility mode? I haven’t verified this, but I have heard in some cases people having issues with the WPA2/3 compatibility mode on the same band instead of separating out version 2 and version 3.

Some people have found good solutions to this by doing things like creating a guest Network specifically for the cameras with only 2.4 GHz band. So there is no aggressive band steering issue. Disable “Fast Roaming”, Disable “Mesh Technology” for the Camera.

Also, do not use anything similar to QoS (quality of service device prioritization) or WMM (Wi-Fi multimedia setting) on your router. QoS features work great for things like TV streaming (which can buffer and handle inconsistent intermittent signals) or browser traffic, etc. But it kills things like Smart Cameras.

I’ve heard there are some other unique protocols specific to Deco routers that seem to have conflicts for some reason, But I don’t recall all the details. I only remember they are a common culprit based on their unique methods other routers don’t do. (I could probably make a list of several pages of other things to consider, but the above are my primary suspicions)

I’m personally currently running mine on Ubiquity UniFi (Dream machine SE with 4 U7 Pro APs). I currently have 150 devices connected, sometimes >200. 6 of them are FLPros. I’ve used 4TB of data in the last 30 days, 2.4TB of that is from uploaded cloud events to Wyze from ~50 cameras. They’re all currently running well without connection issues including my 6 FLPros.

I honestly lean toward thinking that the issue is most likely related to Deco’s special different unique protocols. But it is worth seeing if a factory reset helps or if changing some of the settings in the deco might help.

Worst case scenario, you might have to consider either getting some kind of separate router just for your cameras and IoT or find something that is designed to play nicely with Deco’s unique protocols.

Either way, don’t shoot the messenger. :slight_smile: I hope you find something in the above that can help you figure out or try things that will resolve it for you.