kevinvincent / ha-wyzesense

A Home Assistant Component to interface with the WYZE Sense hub and sensor system
368 stars 97 forks source link

Dead battery on contact sensor now having issues reconnecting #98

Open gullygossner opened 4 years ago

gullygossner commented 4 years ago

A battery in one of my contact sensors died. I replaced the battery but was not getting a connection to home assistant. I did a wyzesense.remove for the contact sensor and then tried reading the sensor with wyzesense.scan. The sensor is discovered but there is no MAC address attributed to the sensor (binary_sensor.wyzsense) and the MAC address for the sensor is something like /0/0/0/0/0/0/0.

Is there a way to get the sensor correctly discovered again?

Wyze sense 0.0.7 Home Assistant 0.104.3

photinus commented 4 years ago

Do you have another battery you can try? I've seen this issue as well and swapping in a different battery has resolved it for me.

gullygossner commented 4 years ago

Do you have another battery you can try? I've seen this issue as well and swapping in a different battery has resolved it for me.

I do have others I can give a try. Have you checked the voltage of the ones that worked vs the ones that haven’t?

photinus commented 4 years ago

I have, The one that was failing for me was showing at 2.9v vs 3.1v for a new battery, though prior to it failing it was showing 75% battery. I've had a couple go into this state while I have a couple that have no issues at all still on their stock batteries.

gullygossner commented 4 years ago

Unfortunately I don’t think the battery is my problem. 4.6V is my reading across a couple batteries and same issue.

npotgieter commented 4 years ago

Same thing happened to me. I suspect that the sensors are defective. The 3 (out of 18 or so) that failed this way ran their batteries flat in a relatively short period of time. That combined with the "no MAC behavior" seems to indicate a hardware issue. I also obtained another bridge and these faulty sensors did the same thing when I used that bridge. These sensors are very cheap and I can't help but wonder if quality was sacrificed along the way.

gullygossner commented 4 years ago

I was wondering that as well, this sensor is the same location (unheated garage) where another sensor experienced a similar fate (dead battery and then no mac address after replacement). I have a motion sensor in the same location and it has been tip top. The most unfortunate part is that in Canada I cannot obtain the sensors outside of the full wyze sense package.

npotgieter commented 4 years ago

Overall, the sensors (as a system), not very reliable for me. I have to bounce my HA server once or twice a day to keep them working. (They just stop "sensing").

Probably time to look for something else. (Looking into some of the new, small form factor, 433Mhz PIR sensors with a Sonoff RF Bridge and Espurna firmware for a cost effective alternative).

stang70man commented 4 years ago

I have had the same issue. I noticed my contact sensors all lost their connection and were flashing either 3 or 5 times. I went around and reset all of the sensors and they all joined up but two of them. They were in difficult locations, so I didn't mess with them much, but when I tried to add them I got a message that the sensor was added as "binarysensor.wyzesense" with no mac address.

One of them showed up in the States UI (I'm gonna miss States for testing and troubleshooting!) and I was able to edit it and customize the sensor and put the MAC address back on it. It's working great now (with a new battery.) This final one will not show up anywhere with the MAC address attached. It will scan and attach, but no MAC address so I can't get it to show up in entities or any where else.

Here's the actual message when it scans it:

Sensor found and added as: binarysensor.wyzesense (unless you have customized the entitiy id prior). To add more sensors, call wyzesense.scan again. More Info: type=1, version=16

I'm not sure where to go from here, but I'll post here if I figure it out.

adtinnis commented 4 years ago

Was there ever a solution to this? I tried all sort of things, but could not get a mac address other than a bunch of zeros after replacing batteries.

npotgieter commented 4 years ago

Not that I am aware of.

I never could get the system to work reliably for any length of time.

Found a different solution.

On Fri, Apr 10, 2020 at 3:07 PM adtinnis notifications@github.com wrote:

Was there ever a solution to this? I tried all sort of things, but could not get a mac address other than a bunch of zeros after replacing batteries.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kevinvincent/ha-wyzesense/issues/98#issuecomment-612174571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENDDSL2PN4FZR3BJCZP73TRL5U5NANCNFSM4KOI5UYQ .

smoke007 commented 4 years ago

@gullygossner @adtinnis I had the exact same issue with a contact sensor that was not being used, suddenly ate the battery. After replacing with a new battery, scanning for the sensor again, it shows up with 00000000 MAC (or also seen in the configs as \0\0\0\0\0\0\0\0) I documents a work around to customize the entity from within the GUI, to put the MAC back in, and continue using this sensor for now here: https://github.com/kevinvincent/ha-wyzesense/issues/130#issuecomment-624960162

Time will tell if the sensor will eat the battery quickly again. More details in my other post. Cheers