-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Govee Water/Leak sensor #2619
Comments
There is some discussion to this in #2605 |
@zuckschwerdt OK, well I already have the Govee water sensors but that last comment does not give much hope of making it work in HA. It would appear that all I can do is return them. Sigh. |
@ifuchs I think you can probably make them work,but you'll need to code up "if wet event then wet, and if no wet event for 30 minutes then dry" somehow. I don't have any and am understanding only from reading list/github traffic. So take my comments in that light. |
Can someone explain to me why when I run the rtl_433 (rtl_433 version nightly-33-gf775d1ac branch master at 202304221552 inputs file rtl_tcp RTL-SDR) on my raspberry pi with mqtt going to HA, the Govee device is seen (although I am still trying to get the payload recognized) but if I simply run rtl_433 from the CLI on my Mac w v22.11, the Govee does not show up. Did this work in the older RPi version and break in the most recent version? |
Further simplified failure: rtl_433 on the RPi0W shows the Govee when button pressed. Same command on Mac does not. Mac is running v22.11. FWIW, GQRX and URH both see the Govee transmissions. |
22.11 is ancient. compile git master. |
It's a year old, we still need to debug an rare exit failure before we release. Check the nightly changelog for interesting changes. E.g.
|
OK, I upgraded to the master branch and my Mac with rtl_sdr now sees the Govee (as does the Rpi0W.) Now if I could just get it to work with HA I could go on to something else. I will refrain from using issues for this sort of thing in the future. Thanks. |
@ifuchs if you switch to the “next” addon that ships rtl_433 master. It’s the same idea with the auto discovery addon. https://github.com/pbkhrv/rtl_433-hass-addons/tree/main/rtl_433-next |
I replaced the rtl_433_mqtt_hass.py file in the rtl_433_mqtt_autodiscovery addin (by using portainer and going into the addin container). I am not clear what else needs to be replaced. I don't run the rtl_433 addin, I run rtl_433 on a Raspberry Pi to send MQTT messages to HA. If I cause the Govee sensor to send a water leak message, it shows up in the HA MQTT broker (I see that with MQTT explorer on my Mac) but I do not see any entity in HA for this event. What am I missing? Do I need to replace rtl_433 on my Raspberry Pi? (HA does show a Govee device, but no entity for the event.) Any help would be very much appreciated. (On the RPi0W, I am running: rtl_433 version nightly-33-gf775d1ac branch master at 202304221552). |
FWIW, I updated rtl_433 on the RPI0w to 202308211241 with no noticeable change. |
At least something has been merged and I can't immediately understand what is left to do. Should this issue be closed? If not, please add a comment with a very brief summary of the remaining work. |
Has anyone gotten these leak detectors to work? I just want it to notify me when there's a leak so I can flip off my water pump breaker with HA. |
I have several Govee H5054 water leak sensors that I would like to bring into Home Assistant. rtl_433 Autodiscovery is seeing the device but only shows the battery status. My guess is that the key of interest is "event" which shows if there is a leak or if the button on the device is pressed. Home Assistant is adding the device but only with the battery_ok status. Could "event" be added as a valid key and would this solve the problem I am seeing?
If it helps, here is what MQTT explorer shows:
The text was updated successfully, but these errors were encountered: