11,000 requests in just a few hours? What is going on? It’s non-stop. The hub has access to the internet, nothing is blocked and the hub is working correct?
Looks like it has the heartbeat set to ping every 4 seconds.
Typically I see this when someone blocks the ping in some way, then it escalates ping attempts until it is successful. If you haven’t blocked or restricted any of its DNS or ping attempts, then this feels abnormally frequent.
This says it’s using the API. Are you using any third party access to your Wyze account such as home assistant or the Python SDK or anything? If so, I’d guess it might be related since unofficial API access currently requires manual “polling” instead of getting things pushed to them directly.
3 Likes
Wyze doesn’t publish what domains their devices need access to so it’s a moot question, no offense. That said, this device has no DNS restrictions. Not using any 3rd party software either. This is a problem with the device. Other wyze devices on the network are OK and not spamming.
Are Wyze devs just brute force hacks? If your ping theory is true (and I have no way to verify because Wyze publishes no documentation on how their devices work), it’s completely ridiculous the device would try to brute force it’s way out of the network and bombard the DNS server. Absolutely lazy and inept programmers. Hire someone that knows what they are doing.
I always understood the increased pinging to be more about trying to know when the device comes back online since a ping can’t brute force anything. Interestingly, Wyze has a history of often doing the opposite where they will reduce the frequency of how often they check for a restored connection (set the check-in interval to double every time it fails), but we have seen some cases where it increases instead too. I SUSPECT it may partially depend on the default algorithm of the particular supplier they partner with for the model in question.
I decided to check my flow history for my Wyze Sense hub to see if mine is doing the same thing. Strangely, my hub almost never checks in to api.wyzecam.com like yours is doing. I had one ping there at 1:34pm and then nothing else the entire last month from that device.
But my Dining Room V3Pro is going insane. It has had 40K flows in the last 1 day (though only 1525 of those were to the api.wyzecam.com), nearly 3K in the last hour. 935K in the last month. That’s way excessive.
My Bulb Cam and Floodlight Pro are doing something similar.
But not my HMS Sense Hub. Maybe it’s because I keep the HMS on “Test Mode” so my alarms don’t accidentally trigger a dispatch without my consent? Maybe it wants to ensure a constant heartbeat when it is active to force an NAT Keep-Alive situation so it doesn’t fall behind a closed door on the router when it thinks a device becomes idle. But even then, every 4 seconds is ridiculous.
My suggestion would be to try to restart the hub and see if that breaks it out of the loop. → Hold the reset button firmly for 9-10 seconds until the LED lights flash, then immediately let go. The hub will restart and come back up and hopefully it will be out of that loop. If you try that, I’d be interested to hear if it affected it. If mine was doing the same thing then I would think it was intentional and built in to the firmware to do it for everyone, but since mine isn’t doing it and yours is, I have to wonder what the difference is and this would be a good test to see if it got stuck in some kind of unintended loop. It could also be a particular sensor spazzing out. Depending on how many you have, you could also try pulling the battery out and sticking it back in for a few of those.
1 Like