Wyze bridge going to sleep?

Czechmarty commented 3 years ago

It seems like the Wyze bridge is "going to sleep" or disconnects in some period of time (maybe when there are no sensor interactions). To remedy this I have to go to server controls and restart the server. First I thought the USB is going to sleep, but don't see that happening.

Anyone else seeing this???

Running HAOS 2021.4.2 on Oracle VM Virtual Box on Win10 mini PC. Details below...

System Health

version	core-2021.4.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.8.7
os_name	Linux
os_version	5.4.109
arch	x86_64
timezone	America/New_York

Home Assistant Community Store

AccuWeather

can_reach_server | ok -- | -- remaining_requests | 19

Home Assistant Cloud

Home Assistant Supervisor

Lovelace

Czechmarty commented 3 years ago

Is this integration completely dead? Anyone has suggestions? I really like the Wyze gizmos but this is making them unusable in HA :( :(

stanwebber commented 3 years ago

I haven't had a problem in at least 6 months. I'm on hass 2021.3.4 running the erlanger wyzesense fork. I probably restart every couple weeks or so.

perhaps it's something specific to my setup. I run on an rpi4 2gb with the most current x64 hassos. I disable wifi, bluetooth and all system/ethernet leds in my boot config. I run the nodered addon with multiple nodes constantly monitoring the wyze entities for state changes. additionally, I run ssh, autossh, emulated hue, plight addons and localtuya, badnest, nodered-companion hacs integrations.

I also use this in my configuration.yaml, recorder: db_url: 'sqlite:///:memory:'

Czechmarty commented 3 years ago

Thank you for the reply!! It's super weird, I can't figure it out and it's driving me crazy. Sometimes the system will run for a day no problem. Sometimes just a few hours and all WYZE sensors are not responding (because of the bridge went to "sleep" or something). I'm running full mini PC with 8GB memory and 120GB SSD (and SD card).

Couple questions if I can: What is the "erlanger wyzesense fork? What does the "nodered addon" mean? What does the "recorder:" does?

stanwebber commented 3 years ago

oh, another detail that comes to mind is that my wyze bridge is on firmware v0.0.34. in response to your questions:

I run a fork of this repository with 1 additional fix (issue #189) not in master: https://github.com/erlanger/ha-wyzesense
https://community.home-assistant.io/t/home-assistant-community-add-on-node-red/55023
this directive under recorder runs the hass database completely in memory and never commits it to disk. thought it worth mentioning since this is not common.

Czechmarty commented 3 years ago

Hello stanwebber! Thank you for more info. This is still driving my crazy and I'm about to give up on Wyze. I looked at the erlanger fork, but it looks like it was merged with repo and the Readme is carbon copy of this one, so it actually points to this repo for install. I got node red as well, sorry, misunderstood when you put there nodered. Duh :) I do have the same 0.0.34 firmware. Can you update the bridge outside of the Wyze camera? I'm assuming you have the type of bridge that you originally put at the back of camera correct? Oh and how do you monitor the Wyze Entities thru Node RED? Can you please show me? Thanks again!

atjshop commented 3 years ago

Mine had died 3 times in the past 6 months. Sometime it has error sometime it just died without any error in log. I have to unplug/plug the bridge, change hidraw value in the HASS docker and restart HASS to make it work.

I already manually added the fix of https://github.com/kevinvincent/ha-wyzesense/issues/189

Error is something like below:

2021-06-04 08:52:02 ERROR (Thread-7) [custom_components.wyzesense.wyzesense_custom] Invalid packet: b'55aa531d1900000179d74b0deda2373737424533353717175d0001010c314a078a' 2021-06-04 08:52:02 ERROR (Thread-7) [custom_components.wyzesense.wyzesense_custom] Mismatched checksum, remote=078A, local=079F 2021-06-04 12:39:04 ERROR (Thread-7) [custom_components.wyzesense.wyzesense_custom] Invalid packet: b'55aa531d1900000179d81b15eca2373737424533353702175d0001010c45070776' 2021-06-04 12:39:04 ERROR (Thread-7) [custom_components.wyzesense.wyzesense_custom] Mismatched checksum, remote=0776, local=073

stanwebber commented 3 years ago

this is a simple nodered flow for email notification monitoring of wyze sensor battery state.

[ { "id": "5b75cf5d.d2216", "type": "trigger-state", "z": "c998d28f.9e52a", "name": "wyze_hallway", "server": "1753ac5c.e43cc4", "exposeToHomeAssistant": false, "haConfig": [ { "property": "name", "value": "" }, { "property": "icon", "value": "" } ], "entityid": "binary_sensor.wyzesense_777cxxxx", "entityidfiltertype": "exact", "debugenabled": false, "constraints": [], "outputs": 3, "customoutputs": [ { "messageType": "payload", "messageValue": "family motion", "messageValueType": "str", "comparatorPropertyType": "property", "comparatorType": "<", "comparatorValue": "80", "comparatorValueDataType": "num", "comparatorPropertyValue": "new_state.attributes.battery_level" } ], "outputinitially": false, "state_type": "str", "x": 120, "y": 60, "wires": [ [], [], [ "1acf03ca.1d7d6c" ] ] }, { "id": "1acf03ca.1d7d6c", "type": "change", "z": "c998d28f.9e52a", "name": "yahoo_content", "rules": [ { "t": "set", "p": "topic", "pt": "msg", "to": "SENSOR BATTERY LOW", "tot": "str" } ], "action": "", "property": "", "from": "", "to": "", "reg": false, "x": 400, "y": 380, "wires": [ [ "175a68ce.147757" ] ] }, { "id": "175a68ce.147757", "type": "e-mail", "z": "c998d28f.9e52a", "server": "smtp.mail.yahoo.com", "port": "465", "secure": true, "tls": true, "name": "username@yahoo.com", "dname": "yahoo_notify", "x": 590, "y": 380, "wires": [] }, { "id": "1753ac5c.e43cc4", "type": "server", "name": "Home Assistant", "addon": true } ]

kevinvincent / ha-wyzesense

Wyze bridge going to sleep? #209

System Health