I think the difference with the cams, is that they connect to the Wyze server temporarily to get authorization the establish a local connection. After that, there shouldn’t be much load from the camera on the Wyze servers in theory from what I’ve been told.
With Home Assistant, the add-on was continually polling the servers to see if anything changed on the sensor status. It didn’t establish a local connection for those, so it was continually draining the Wyze servers’ resources.
They may have changed the throttling, but the previous throttle was more of a long term suspension. So if it’s hard to hold onto an ongoing going connection with the cams through tiny cam, but possible to try again and still connect at least temporarily, then that should mean this is not the same issue, but could still be something similar and related (ie: a timeout/disconnect for something), though that seems really weird if the connection is entirely local and shouldn’t be affecting them anymore after it’s established. Causing people to have to connect back over and over again will make things worse for them because it will have to keep authenticating through their server for the initial authorization…which would be unnecessary if they just let it stay connected. So it seems to me it SHOULDN’T be something they are doing intentionally here. Best thing to do would be to post the issue in the Tiny Cam Forums. Alexy has been pretty good at resolving issues he is informed about.