Just curious (and so I can sub the thread!), has anyone flashed the govee bridge?
I don’t think anyone here has, but it should be possible with that chip. You would then have to figure out how the pins are used. Since I don’t have one, is was just easier to flash the sonoff bridge.
Yeah I have been using the sonoff bridge and unplugged my govee bridge. Would definitely be nice to get something figured out, but for now this seems to work. (I usually will test the sensors every so often when I think about it to see if the alert comes to my phone, so far they have been pretty solid!)
Hi
I have a sonoff bridge flashed with Tasmota. Can you explain how you get the Govee Sensors reporting via this method?
This is the video I used to help me understand and configure the bridge with the sensors, it’s very helpful: https://www.youtube.com/watch?v=Ega4U1KRlso
Basically, I logged into the Sonoff Bridge Console and set off each of the senors and wrote down the hex code associated with each sensor. I then used those hex codes in my binary sensor yaml file to create the sensors in HA, then I used automations to push an alert to my phone if one of the senors goes off.
I think the video posted above will probably help you solve it, but as they said: just manually activate them (I just used a screwdriver to short out the bottom contacts of the sensor), and then you can set up your binary_sensors as below (modify the state topic and payload_on/off):
from my configuration.yaml:
binary_sensor:
- platform: mqtt
name: "kitchen sink leak detector"
payload_on: "00D6FB"
payload_off: "00D6FC"
device_class: moisture
state_topic: "tele/tasmota_C370F0/RESULT"
value_template: "{{ value_json.RfReceived.Data }}"
availability_topic: "tele/tasmota_C370F0/LWT"
payload_available: "Online"
payload_not_available: "Offline"
- platform: mqtt
name: "bathroom sink leak detector"
payload_on: "001BFB"
payload_off: "001BFC"
device_class: moisture
state_topic: "tele/tasmota_C370F0/RESULT"
value_template: "{{ value_json.RfReceived.Data }}"
availability_topic: "tele/tasmota_C370F0/LWT"
payload_available: "Online"
payload_not_available: "Offline"
from my automations.yaml:
- id: '1599002167148'
alias: Leak Alert
description: ''
trigger:
- entity_id: binary_sensor.bathroom_sink_leak_detector
from: 'off'
platform: state
to: 'on'
- entity_id: binary_sensor.kitchen_sink_leak_detector
from: 'off'
platform: state
to: 'on'
- entity_id: binary_sensor.valve_leak_detector
from: 'off'
platform: state
to: 'on'
- entity_id: binary_sensor.water_heater_leak_detector
from: 'off'
platform: state
to: 'on'
condition: []
action:
- data_template:
message: '{{ trigger.from_state.attributes.friendly_name }}: Leak Detected!'
service: notify.notify
- data: {}
entity_id: switch.elexa_consumer_products_inc_dome_water_shut_off_valve_switch
service: switch.turn_off
Thanks for all your help. I will give it a try.
So, I got ON working, was pretty easy once I understood how to see the payload (I’m a bit new to Tasmota). I am unclear on how you have a value for OFF, as I do not see the sensor reporting anything once the alarm stops.
So that is where I used the example from the video. You don’t really have an “OFF” signal sent. So you can either setup for it to persist, or maybe make it a ‘switch’ that you then have to manually turn off which would ensure the alarm doesn’t clear in HA until you actually verify the leak and manually turn the switch off. I think this is what I will end up doing as I start to refine it. Right now it just sends a persistent push notification to my phone but may setup a swtich that will trigger an automation that will continue to push a notification or do something at a regular interval until turned off by me.
In my case, I used the button press on the sensor for that code. So it will be ‘ON’ until the button is manually pressed on the sensor that reported it. Sorry about leaving that detail (it’s been awhile since I did it now), but as mentioned above - there are several approaches you could take! I wanted something that forced me to have the sensor itself checked.
Great idea, thanks
Just looking to clarify, do you need the Govee bridge or app at all if you’re monitoring the sensors through an RF bridge or radio?
I’m wondering if I could just purchase the 5-pack of sensors and get them connected to HA through RF. These sensors seem like a great solution for me, connected monitoring plus a built-in alarm.
Nope, just the sensors should be enough
ive been following this thread, would it be better to just use a water sensor connected to gpio pins of an ESP8266? I guess then you don’t get easy long battery life
I don’t see why not. I have seen people also use the Wyze contact sensor reconfigured as a leak detector. This thread was mostly started for the people who already had the Govee ones and wanting to utilize them somehow with HA. Though they are pretty easy to setup if you have an RF Bridge so a simple solution that doesn’t require any hardware tinkering.
I had originally considered something like this, specifically using a contact sensor like @smoysauce mentioned. Ultimately, I decided I wanted something with an audible alert not tied to Home Assistant. Having dealt with water leaks in the past, I wanted to reduce the number potential failure points to make sure I am alerted in a timely fashion.
That is a really good point too! The Govee sensors have built in sirens.
I’m curious if they chirp or anything when the batteries get low, since I haven’t been able to figure out how to get battery status in HA.
According to at least one Amazon review, they produce a really annoying, consistent chirp which can only be stopped by replacing the batteries. I’m hoping to get the battery status reporting to work in general, but especially if the claims of this review are true!
I plan to run some tests by hooking a sensor up to my adjustable power supply and simulate a low battery situation. I’ll report back with my findings.
According to the manual that came with mine (from this 3-pack + hub) it says the low battery alarm on the sensor flashes a red light and makes a “dududu” sound. Whatever that is
That would mean I would have had to read the manual! Ha! Looking at their site you are right, it does alert for low battery. Also it shows the button is a “Mute/Test” key. So I am guessing it must send the battery level code every-so-often when connected to the official gateway (unless the gateway has a way to poll the sensor), but I do notice when I push the button, the RF bridge picks up a code which makes me wonder if that code is the battery status. So maybe it sends a “gross” status of High, Med, Low and just need to figure out which code correlates to what. I’m now curious again! I’m eager to see what @DeltaNoir finds!