Wyze

Summary - Detect Wyze Bulb Cam (HL_BC) and create a light entity for its integrated bulb - Add "bulbcam" light type with "Light" name suffix and lightbulb icon - Refactor `name` and `icon` properties to use dict lookup for cleaner, more maintainable code ## Details This PR adds Home Assistant light entity support for the Wyze Bulb Cam (model `HL_BC`). The Bulb Cam has an integrated light that can be controlled via the Wyze API. Dependencies: This PR requires SecKatie/wyzeapy#195 to be merged first, which adds the underlying API support for controlling the Bulb Cam light. ## Test plan - [ ] …

Excerpt saved from GitHub on 2026-10-23.

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.

Excerpt saved from GitHub on 2026-10-23.

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.

Excerpt saved from GitHub on 2026-10-23.

my bulbs are on the same network as my server, but I'm getting the log you mentioned (and it fails to properly interact with the bulbs): > > Logger: wyzeapy.services.base_service Source: .local/lib/python3.9/site-packages/wyzeapy/services/base_service.py:613 First occurred: 8:10:03 PM (1 occurrences) Last logged: 8:10:03 PM > > Failed to connect to bulb 7C78B232371B This is the same error I randomly get with my color bulbs. They work for a bit, but seem to stop responding to commands after some time. In my case, the bulbs fail to respond to commands but seem to always revert back to the …

Excerpt saved from GitHub on 2026-10-23.

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.

Excerpt saved from GitHub on 2026-10-23.

The original text was already deleted or overwritten when we archived it.

This PR adds support for my irrigation api work in this other PR https://github.com/SecKatie/wyzeapy/pull/127 and related issue https://github.com/SecKatie/ha-wyzeapi/issues/230 Again, my first time adding to a home assistant component, but ive added my code to the sensor.py, switch.py and a new number.py. Each irrigation device has multiple zones. The parent device has several sensors (RSSI, wifimac, ip address, etc), and then the zones are represented as switches. they have attributes as well (name, id, etc), but my thought in home assistant is to be able to turn them on and off like a …

Excerpt saved from GitHub on 2026-10-23.

I own two different Wyze Light Strips models. The Wyze Light Strip - 16.4ft (purchased 5/2022) with the latest firmware version 1.1.1.170 works perfectly. The Wyze Light Strip - 32.8ft (purchased 12/23) with the latest firmware version 1.2.0.3 is unresponsive despite showing up under devices and allowing input. Ideally, both models of the Wyze Light Strip would be supported by the extension and offer the same functionality. Currently, I don't know of any way to control the 1.2.0.3 light strip outside of the Wyze app.

Excerpt saved from GitHub on 2026-10-23.

Summary Adds Home Assistant live-view support for Wyze "Gwell" cameras, the family that streams over Agora RTC instead of the TUTK/Kinesis path this integration already handles. These cameras (Wyze Solar Cam Pan `ME_WCO3`, Cam OG `GW_GC1`, Doorbell Pro `GW_BE1`, and more as Wyze moves to Agora) currently show up as unavailable with no stream. Everything here branches on `provider == "lake"` / `wyzeapy`'s `LAKE_API_MODELS`, never a hardcoded model, so it covers the whole Gwell family, current and future, automatically. > Companion PR (required first): SecKatie/wyzeapy#336 adds the …

Excerpt saved from GitHub on 2026-10-23.

… master, worked through the three review comments, and tested it on hardware. Should close #734, and covers what #839 was asking for. ## What it does The Lock Bolt v2 (`DX_LB2`) and the Palm Lock (`DX_PVLOC`) report `product_type: "Common"`, so `lock_service.get_locks()` never returns them and they do not show up in Home Assistant at all. They are not Bluetooth devices either, so the Lock Bolt v1 coordinator does not apply to them. Wyze serves them from a separate cloud API under `/app/v4/iot3/` with a signed request body. This adds an IoT3 client and a per-device coordinator, finds DX devices …

Excerpt saved from GitHub on 2026-10-23.

Asking for support to be added for Wyze OG Cameras to allow control in both HA and Apple Home. Currently there is no direct control for OG Cameras in HA or Apple Home. As such, I can no longer use HA or Apple Home to turn cameras on/off when arming or disarming Wyze Sense Hub. Other cameras allowed this function like V2 and V3 cameras. I currently have to use location triggers in Wyze app to turn on/off my cameras when leaving home instead of just being able to turn off/on when arming/disarming.

Excerpt saved from GitHub on 2026-10-23.

… master, worked through the three review comments, and tested it on hardware. Should close #734, and covers what #839 was asking for. ## What it does The Lock Bolt v2 (`DX_LB2`) and the Palm Lock (`DX_PVLOC`) report `product_type: "Common"`, so `lock_service.get_locks()` never returns them and they do not show up in Home Assistant at all. They are not Bluetooth devices either, so the Lock Bolt v1 coordinator does not apply to them. Wyze serves them from a separate cloud API under `/app/v4/iot3/` with a signed request body. This adds an IoT3 client and a per-device coordinator, finds DX devices …

Excerpt saved from GitHub on 2026-10-23.

Summary Adds native Wyze Scale support as sensor entities in Home Assistant. This is v1 support and would love if someone could further refine. ## Dependency ⚠️ Depends on SecKatie/wyzeapy#271 being merged and published to PyPI first. The `manifest.json` version requirement will be updated to match the new wyzeapy release before this is merged. ## Changes - `sensor.py`: Added `WyzeScaleSensor` entity class and scale setup in `async_setup_entry` ## Sensors added - Weight (kg) - BMI - Body Fat % - Muscle Mass (kg) - Body Water % - Bone Mineral (kg) - Metabolic Age - Visceral Fat Rating ## …

Excerpt saved from GitHub on 2026-10-23.

`ha-wyzesense` requires you to pair the sensors with a bluetooth device, which unpairs them from the Wyze cloud service. I tried downgrading `ha-wyzeapi` to an older version but looks like Homeassistant has new IO rules: > `` RuntimeError: I/O must be done in the executor; Use `await hass.async_add_executor_job()` at custom_components/wyzeapi/smartbridge/providers/wyze/client.py, line 245: response = session.send(request, settings) `` > > I can't lose support for V1 sensors, so I might just fork an old version of this repo and update it to work with recent HA versions. Did you get change to …

Excerpt saved from GitHub on 2026-10-23.