PSA to anyone using Wyze contact/motion sensors

Hardware
1

As many of you probably already know, if you let the battery die in the Wyze Sense motion or contact sensors, it can potentially render the sensors unusable. The sensor can lose its MAC address which makes it impossible to pair to the bridge. Reportedly this is more common with the contact sensors than the motion sensors, but I can’t confirm that. I’ve lost three contact sensors this way, but thankfully Wyze replaced them for free.

Anyway, to the point–it appears the battery percentage that indicates low battery is 84% (at least with wyzesense2mqtt). I’ve replaced the batteries in three sensors that all showed low battery on the sensor itself (three blinks of the LED every 10 seconds) at around 84%. Might be the same for the Wyze Sense custom integration since they use the same underlying Python library. You might want to set up an automation that notifies you when any of your Wyze sensor batteries goes below 85%.

2

As I have also lost a few I added automations for each as well as added the custom battery entity card to my lovelace system tab. Not knowing what the low battery reading really is, I set my automations to trigger on below 86%. A lot of talk in other forums that wyze knows of the issue, but as yet no one has confirmed if it has been fixed in new versions.

3

I saw a tweet from Wyze that the second gen sensors won’t have this issue.

4

Did they say how to tell the difference?

5

They haven’t been released yet

6

That could be why you can’t buy new ones now.

7

I’ve moved to RF 433 sensors.

8

There is also a mention in the new beta release of a new requirement to have the code. If no one is working this anymore, it will die soon in Home Assistant. * No ‘version’ key in the manifest file for custom integration ‘wyzesense’. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of ‘wyzesense’

9

any response from the developer on whether this will be fixed?

10

No one is working on it. Fairly easy to modify the ma
Manifest.json file. If you need help I can let you know what I changed.

11

Thanks Bill. I would appreciate if you post some instructions when you get a chance

12

This is my new manifest.fson file:

{
    "domain": "wyzesense",
    "name": "Wyze Sense Component",
    "version": "1.8.2",
    "documentation": "https://github.com/kevinvincent/wyzesense",
    "requirements": ["wyzesense==0.0.4","retry==0.9.2"],
    "dependencies": [],
    "codeowners": ["@kevinvincent"]
}

I had to add “version”: “1.8.2”, Not sure the intent on this new requirement so I do not know if it causes other issues. This works for me. This must be done in a text editor. I used notepad++.

13

Ugh, the RF 433 sensors seem no where near as reliable with open and close as the wyze. it looked promising, and just as cheap, but RF 433 are way bigger. I might have to try new new wyze contact sensors.

14

I just modified it in File Editor in Home Assistant GUI. But thanks. Working great (for my last two working Wyze sensors…lol).

15

I just modified my manifest.json like your example and it works. I love the wyze sensors, I have them everywhere.

16

Old thread, but I finally got around to setting up a group named wyzesense with a binary sensor.

template:
  - binary_sensor:
      wyzesense_battery_low:
        value_template: "{{ expand('group.wyzesense') | selectattr('attributes.battery_level', 'lt', 85) | list | length > 0}}"

and an alert

alert:
  wyzesense_battery_low:
    name: Wyzesense Battery Low
    entity_id: binary_sensor.wyzesense_battery_low
    state: 'on'
    repeat: 500
    can_acknowledge: true
    message: >
      {% set low_battery = expand('group.wyzesense') |selectattr('attributes.battery_level', 'lt', 85) | map(attribute='entity_id') | list %}
      Low Battery:
      {%- for entity_id in low_battery %}
        {{ state_attr(entity_id, 'friendly_name') }}: {{ state_attr(entity_id, 'battery_level') }}%
      {% endfor %}
    notifiers:
      - mobile_app_sm_g930t

I thought it might help someone that hasn’t done this yet

17

Has anyone else noticed that the (rssi & battery) attributes for the binary_sensor.wyzesense_xxxxxxxx in the ‘Wyzesense’ custom component are no longer available after latest HA update 2022.4.1 ?

This is significant in that one can no longer monitor the battery level for the sensors.

Screen Shot 2022-04-08 at 4.33.50 PM
Screen Shot 2022-04-08 at 4.33.50 PM814×496 62.5 KB

Any ideas on how to resolve would be appreciated.

18

Go to

https://github.com/kevinvincent/ha-wyzesense/issues/223

for the solution.

1 Like
19

Thanks for pointing me in the right direction, really appreciate it!

20

That solved it, thank you!

1 Like