Camera stream

[zackcornelius]

This adds webRTC stream implementation based off the my.wyze.com/live web implementation

Tested with Wyze v2, v3, and Floodlight pro, but the mechanism appears to be the same (using Kinesis video streams with webRTC) for all wyze web view supported cameras (which is maybe all of them?)

This does use the cloud implementation of streaming, rather than the local tutk interface, but does not require a local streaming server (no go2rtc, etc), as it uses HA's native webRTC implementation.

[CLAassistant]

All committers have signed the CLA.

[diogormendes]

@zackcornelius , is this PR still alive ?

[zackcornelius]

Yes, mostly. I had a death in the family, so time the last few weeks has been hard to come by. I'll hopefully get a little bit of time to work on this and finish it up this weekend.

…

On Sat, Mar 21, 2026, 04:52 Diogo Mendes ***@***.***> wrote: *diogormendes* left a comment (SecKatie/ha-wyzeapi#800) <#800 (comment)> @zackcornelius <https://github.com/zackcornelius> , is this PR still alive ? — Reply to this email directly, view it on GitHub <#800?email_source=notifications&email_token=AJHQCS25VUKF2KCO7HECHID4RZQ6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQGI4TOMRYGEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4102972811>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJHQCS3XKGWTRQYFK2FUCCL4RZQ6JAVCNFSM6AAAAACWKN26OGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBSHE3TEOBRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[brg468]

Small addition to hopefully avoid the blocking call.

[brg468]

@zackcornelius while you're cleaning things up can you address some of the formatting issues, like unsorted imports and missing docstrings. That's been on my list of things to do for the other platforms and this will help out with one less to tackle. Thanks!

[zackcornelius]

@diogormendes - Since I've merged your PR to my branch, can you sign the CLA? There's a comment at the top of the issue with instructions

[zackcornelius]

@SecKatie , @brg468 - I think this is probably good for re-review now, did some cleanup, incorporated fixes, tested. Seems good from my end.

[zackcornelius]

@SecKatie - Can you release wyzeapy 0.5.33? Seems the changes are working well for several people here

[brg468]

Couple things I think would help with getting current camera status info, otherwise looks good to me!

[brg468]

       if data["property"]["iot-device::iot-state"] != 1:
            raise UnknownApiError(
                "Camera is offline according to get_stream_info response: " + str(data)
            )
        if data["property"]["iot-device::iot-power"] != 1:
            raise UnknownApiError(
                "Camera is off according to get_stream_info response: " + str(data)
            )

Over in the other lib, I played around with not raising an error for the cam being off or unavailable and instead still fetching the config on startup. This way if a cam comes online or is turned on after startup it would still be able to stream. It seemed to work fine when I tried it, but I'll defer to you if think there's a reason that wouldn't always be the case.

[brg468]

I think the hassfest check is failing because of the added line in manifest.json

[Error: R] [MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order

[diogormendes]

Just FYI, ive just updated to thr latest firmware released today for the v3 and everything still working

[zackcornelius]

@brg468 - Applied your suggestions, and (hopefully) fixed up the hassfest check

[brg468]

Looks good! Tested with multiple cameras and browsers and works great.