Yeah, the main problem is that because it’s a reverse hack, the seckatie integration relied on “polling” which was overwhelming Wyze’s servers, especially for things like sensors and camera motion events working as motion sensor. More than half of all server traffic was being used up by something like 1% of users using Home Assistant polling. Wyze talked with seckatie about how they could manage allowing the integration to continue without overwhelming their server with excessive polling, and the compromise was to remove sensor polling and camera polling but mostly allow the rest to continue.
If Wyze makes their own integration with OFFICIAL API access, then it wouldn’t rely on over-polling nonsense and could simply get pushed when it’s relevant similar to the other integrations for Alexa or Google that don’t overwhelm Wyze’s servers. The problem with the Home Assistant integration was because it wasn’t official, it had to rely on excessive polling. They could easily resolve that by making it official. Like you said, most of the work has already been done for them and is open source. They just need to make a few tweaks.
I’m reasonably optimistic that good improvements are coming.
The timeline is another matter though.
I’m actually pretty surprised Wyze is pushing forward with RTSP right now. I was pretty confident they would at least wait until the matter camera libraries were finalized and then decide after that. I just with the CSA would quit dragging their feet on it.