I don’t have a Govee, but thought I would try to help.
Maybe give the following a try (note I added quotation marks in various places as well).
Also from looking at docs.
How did you get your additional attributes to pull in? (ie time, id, etc). I think I have mine setup just like yours (maybe a different rtl_433 config?) but it only pulls in device class and friendly name. I’m also curious if you chose to do anything to get the battery to pull in.
That link has some code around health checks/battery status. I have yet to implement those, but plan to spend some time on it this weekend. I will post back here if I have any success.
Appreciate the response. I checked out that blog late last night and today and finally connected the dots of all the different posts I was reading. I have now successfully got the events, battery % and battery mV pushing to HA. Thanks!
@smoysauce This is very helpful as I have been struggling with auto_discovery and the Govee sensors. Where exactly do the binary sensor and sensor sections belong? I thought I could put them in configuration.yaml but I’m getting error messages there:
Invalid config for [sensor]: required key not provided @ data[‘platform’]. Got None. (See /config/configuration.yaml, line 100).
Invalid config for [sensor]: required key not provided @ data[‘platform’]. Got None. (See /config/configuration.yaml, line 100).
Invalid config for [binary_sensor]: required key not provided @ data[‘platform’]. Got None. (See /config/configuration.yaml, line 92).
MQTT Explorer shows this for the sensor:
It appears there is no voltage reading, so perhaps I have a different type of Govee sensor.
Since my sensor does not seem to report battery level or voltage I took those defns out and I’m left with the binary sensor and I get this error:
Invalid config for [binary_sensor]: required key not provided @ data[‘platform’]. Got None. (See /config/configuration.yaml, line 92).
I went back to using basic 433 with my RF bridge but looking at my config I have those entries for the RTL under my mqtt.yaml file; since I parse my yaml files out. If you are putting everything in your config.yaml file, I think you’ll need to add the mqtt platform header before it.