It does sound like the battery is kaput if it is rebooting when the plug power cycles.
The key here is that it is reconnecting to the router and getting a refreshed connection. There is something odd causing this in the relationship the hub has with the router that causes the connection to fail.
I have put the Wyze Hub in DMZ (Asus as well as Netgear) routers, plus no other firewall in the network, DNS used in the network at home is 8.8.8.8 (Google)
I upgraded the firmware on Wyze hub and other wyse devices towards mid December since when I started seeing this issue… Hope wyze comes up with some fix.
That’s the problem. To fix it they have to know where to look. This isn’t a system wide bug that affects everyone. It is very limited to only a handful of users reporting which means there is something in the network configuration that the hub doesn’t like or vice versa. Finding that is like a needle in the haystack without digging into individual hub and router logs.
I am on that same firmware since it was in Beta and my hub has never gone offline outside of an ISP failure.
And just to emphasize that point, I have another hub that’s at my current residence that hasn’t had a problem at all… Ever. It’s been working fine on WiFi at least as long as the one i have in a remote location that’s been flaking out.
Just a thought… If the battery is tired, might that be causing a logic conflict issue in the FW when it polls the battery? If that’s tired, it makes me wonder what else inside is tired. (EDIT - Oops, wrong OP) If the other one work fine on the same FW, that indicates a hardware issue.
Wonder what would happen if you were to swap them? I know… Insane idea given the complexity of a total sensor reinstall… I wouldn’t do it, but it would be interesting to know if the same hub acted the same way on a different network that is known to support a healthy hub.
Could be bad hardware, but don’t forget that the hub on my boat worked fine for over a year and only started losing connection a few weeks after I upgraded to new firmware. Made no hardware changes - same router etc.
Hate to wish this on anyone, but if enough people start having this problem then maybe it’ll get Wyze’s attention!
FYI the switch method worked fine for me too - it was offline yesterday morning, so I powered it off remotely, waited all day and powered it on, and everything came back. Next time I’ll try just waiting a minute, per the thread above.
A firmware bug would have produced the issue as soon as it was installed. Since it took several weeks, I would suspect a hardware issue that just happened coincidentally around the time after the update.
Try to see if changing the DNS server for your wyze cam, helps stabilize the connection. For some reason, when my wyze cams use my router (MikroTik RouterOS v7) as their DNS server, they keep disassociating from DHCP and rebooting themselves. If I direct them to 1.1.1.1 or 8.8.8.8 for dns, they stabilize. Not sure what or where is broken but that fixed it for me