Skip to content

Adding support for v2 sensors#81

Merged
raetha merged 3 commits intoraetha:develfrom
HclX:master
Mar 19, 2025
Merged

Adding support for v2 sensors#81
raetha merged 3 commits intoraetha:develfrom
HclX:master

Conversation

@HclX
Copy link
Copy Markdown

@HclX HclX commented Mar 17, 2025

This change updated wyzesense python library so it can correctly detect and decode the following v2 sensors:
Motion V2 sensor
Door v2 sensor
Leak sensor
Climate sensor

The MQTT bridge is also updated so all v2 sensors will now show up in homeassistant. There are a couple "breaking" changes:

  1. The "invert_state" is no longer supported with this change. However, you can specify the "on"/"off" state directly from the sensor config file.
  2. Now you need a "sensor_type" value in your sensor configuration. For sensors already paired with the dongle, you can either manually update them, or wait until the program udpates them automatically, which happens when there is a message/alarm sent from the device.

This change also added partial support of the wyze doorbell v1 chime. However, this device is not integrated in homeassistant yet. The only way to trigger the chime right now is through the updated bridge_tool command line interface.

This change is only tested with dongles updated to the v2 dongle firmware (GW3U). Checking out https://github.com/HclX/WyzeSenseUpdater on how to do it.

raetha and others added 3 commits March 6, 2025 17:07
Various fixes from HclX and nabahr
This change updated wyzesense python library so it can correctly
detect and decode the following v2 sensors:
  Motion V2 sensor
  Door v2 sensor
  Leak sensor
  Climate sensor

The MQTT bridge is also updated so all v2 sensors will now show up
in homeassistant. There are a couple "breaking" changes:
1. The "invert_state" is no longer supported with this change.
   However, you can specify the "on"/"off" state directly from the
   sensor config file.
2. Now you need a "sensor_type" value in your sensor configuration.
   For sensors already paired with the dongle, you can either manually
   update them, or wait until the program udpates them automatically,
   which happens when there is a message/alarm sent from the device.

This change also added partial support of the wyze doorbell v1 chime.
However, this device is not integrated in homeassistant yet. The only
way to trigger the chime right now is through the updated bridge_tool
command line interface.

This change is only tested with dongles updated to the v2 dongle
firmware (GW3U). Checking out https://github.com/HclX/WyzeSenseUpdater
on how to do it.
@raetha raetha changed the base branch from master to devel March 17, 2025 02:28
@raetha
Copy link
Copy Markdown
Owner

raetha commented Mar 19, 2025

@HclX @nabahr I'm pulling this into the devel tree now so that docker builds are there for me to help with testing. If either of you are also using docker, please switch to devel image so we can validate before pushing all of this to main/latest!
Thanks!

@raetha raetha merged commit 6e92254 into raetha:devel Mar 19, 2025
2 of 3 checks passed
@github-actions github-actions bot mentioned this pull request Jul 28, 2025
@dmyoung9
Copy link
Copy Markdown

@HclX Is the firmware needed for this different from the one needed for #54?

Do you know if the GW3U firmware will communicate with the keypad?

@dmyoung9
Copy link
Copy Markdown

Trying this out with my keypad. It seems like the keypad and leak sensor both have 0xEA as the first byte in the payload... I don't have a leak sensor, but from what I'm getting from the code, those have the "sensor type" byte set to 0x03.

Could anyone that has a leak sensor confirm this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Climate & Leak Sensors Sensors stopped picking up events Wyze Sense V2 Devices

3 participants