Home Assistant Home Automation

Using the Govee Bluetooth Thermometer with Home Assistant (Python and MQTT)


Like many other Home Automation enthusiasts, I have been on the lookout for a cheap thermometer/hygrometer that has either WiFi or Bluetooth connectivity. I think I found the answer in the $12 USD Govee Bluetooth Digital Thermometer and Hygrometer. The fact that the device broadcasts the current temperature and humidity every 2 seconds via low energy Bluetooth (BLE) is the metaphorical icing on the cake. Here is a pic of the unit in our garage:

Govee bluetooth thermometer and hygrometer showing 56*F/24% in a garage


This is a pretty basic device. It has a screen that shows the current temperature, humidity, and min/max values. It sends the current readings (along with battery health) every 2 seconds via low-energy bluetooth (BLE). The description on Amazon says it has a “Swiss-made smart hygrometer sensor”. Dunno if I believe that but for $12 it is good enough. The temperature is accurate to +/- 0.54F and humidity is +/- 3% RH. If you use the app, it is apparently possible to read the last 20 days or 2 years of data from the device (I haven’t used the app at all).

Enough with the boring stuff. Let’s get it connected to Home Assistant.

Reading the Govee bluetooth advertisements with Python

I found some sample code on tchen’s GitHub page (link) to help get me going in the right direction.

Without further ado, here is the code I’m using to read the data and publish via MQTT: (updated 2022-01-04 with some logging improvements. default logging level is now WARNING, which disables printing every advertisement)

# basic govee bluetooth data reading code for model
# written/modified by Austin of 2021-12-27
# original source:
import logging
import json
from time import sleep
from basic_mqtt import basic_mqtt
from bleson import get_provider, Observer

	format='%(asctime)s.%(msecs)03d - %(name)s - %(levelname)s - %(message)s',
	datefmt='%Y-%m-%d %H:%M:%S',

# I did write all the mqtt stuff. I kept it in a separate class
mqtt = basic_mqtt()

# writing code on my windows computer, committing, pushing, and then 
# pulling the new code on the Raspberry Pi is a tedious "debug" process.
# there are quite a few errors that spit out from bleson, which as far
# as I can tell, isn't super polished. if we set the debug level to
# critical, most of those disappear.

# basic celsius to fahrenheit function
def c2f(val):
    return round(32 + 9*val/5, 2)

last = {}

# I didn't write this, but it takes the raw BT data and spits out the data of interest
def temp_hum(values, battery, address):
    global last
    # there is a fix for temperatures below freezing here - 
    # I will adjust post code afternoon of 2022-11-28
    values = int.from_bytes(values, 'big')
    if address not in last or last[address] != values:
        last[address] = values
        temp = float(values / 10000)
        hum = float((values % 1000) / 10)
        # this print looks like this:
        # 2021-12-27T11:22:17.040469 BDAddress('A4:C1:38:9F:1B:A9') Temp: 45.91 F  Humidity: 25.8 %  Battery: 100 %"decoded values: {address} Temp: {c2f(temp)} F  Humidity: {hum} %  Battery: {battery}")
        # this code originally just printed the data, but we need it to publish to mqtt.
        # added the return values to be used elsewhere
        return c2f(temp), hum, battery

def on_advertisement(advertisement):
    mfg_data = advertisement.mfg_data

    # there are lots of BLE advertisements flying around. only look at ones that have mfg_data
    if mfg_data is not None:
        # there are a few Govee models and the data is in different positions depending on which
        # the unit of interest isn't either of these hardcoded values, so they are skipped
        if == 'GVH5177_9835':
            address = advertisement.address
            temp_hum(mfg_data[4:7], mfg_data[7], address)
        elif == 'GVH5075_391D':
            address = advertisement.address
            temp_hum(mfg_data[3:6], mfg_data[6], address)
        elif != None:
            # this is where all of the advertisements for our unit of interest will be processed
            address = advertisement.address
            if 'GVH' in
                temp_f, hum, battery = temp_hum(mfg_data[3:6], mfg_data[6], address)

                if temp_f > 180.0 or temp_f < -30.0:
                # as far as I can tell bleson doesn't have a string representation of the MAC address
                # address is of type BDAddress(). str(address) is BDAddress('A4:C1:38:9F:1B:A9')
                # substring 11:-2 is just the MAC address
                mac_addr = str(address)[11:-2]

                # construct dict with relevant info
                msg = {'temp_f':temp_f,
                # looks like this:
                # msg data: {'temp_f': 45.73, 'hum': 25.5, 'batt': 100}
      "MQTT msg data: {msg}")

                # turn into JSON for publishing
                json_string = json.dumps(msg, indent=4)

                # publish to topic separated by MAC address
                mqtt.publish(f"govee/{mac_addr}", json_string)

# base stuff from the original gist
logging.warning(f"initializing bluetooth")
adapter = get_provider().get_adapter()
observer = Observer(adapter)
observer.on_advertising_data = on_advertisement

logging.warning(f"starting observer")
logging.warning(f"listening for events and publishing to MQTT")
while True:
    # unsure about this loop and how much of a delay works

And for the MQTT helper class (

# basic MQTT helper class. really needed to write one of these to simplify basic MQTT operations
# written/modified by Austin of 2021-12-27
# original source:
# filename is
from paho.mqtt import client as mqtt_client
import logging
import datetime
	format='%(asctime)s.%(msecs)03d - %(name)s - %(levelname)s - %(message)s',
	datefmt='%Y-%m-%d %H:%M:%S',

mqtt_host = ""
test_topic = "mqtt_test_topic"

# this is really not polished. it was a stream of consciousness project to pound
# something out to do basic MQTT publish stuff in a reusable fashion.
class basic_mqtt:
	def __init__(self):
		self.client = mqtt_client.Client()
		self.subscription_topic_name = None
		self.publish_topic_name = None
		self.callback = None = mqtt_host
	def connect(self):
		self.client.on_connect = self.on_connect
		self.client.on_subscribe = self.on_subscribe
		self.client.on_message = self.on_message"connecting to MQTT broker at {mqtt_host}")

	def on_connect(self, client, userdata, flags, rc):
		print("Connected with result code "+str(rc))

		# Subscribing in on_connect() means that if we lose the connection and
		# reconnect then subscriptions will be renewed.

	def on_message(self, client, userdata, msg):
		print(f"got message of topic {msg.topic} with payload {msg.payload}")

	def on_subscribe(self, client, userdata, mid, granted_qos):
		print("Subscribed: " + str(mid) + " " + str(granted_qos))

	def publish(self, topic, msg):
		self.client.publish(topic=topic, payload=msg)

	def subscribe_to_test_topic(self, topic=test_topic):

	def send_test_message(self, topic=test_topic):

		self.publish(topic=topic, msg=f"test message from python script at {}")

	def disconnect(self):

	def loop(self):

if __name__ == "__main__":"running MQTT test")
	mqtt_helper = basic_mqtt()


Running this script on a Raspberry Pi 3 shows the advertisements coming in as expected. The updates are very quick compared to the usual 16 second update interval for my Acurite stuff.

screenshot of Python code running to receive BLE advertisements from Govee Bluetooth Thermometer
screenshot of Python code running to receive BLE advertisements from Govee Bluetooth Thermometer

And running mosquitto_sub with the right arguments (mosquitto_sub -h mqtt -v -t “govee/#”) shows the MQTT messages are being published as expected:

mosquitto_sub showing our published MQTT messages with temperature/humidity data from the Govee sensor

Getting Govee MQTT data into Home Assistant

Lastly, we need to add a MQTT sensor to get the data importing into Home Assistant:

- platform: mqtt
  state_topic: "govee/A4:C1:38:9F:1B:A9"
  value_template: "{{ value_json.temp_f }}"
  name: "garage temp"
  unit_of_measurement: "F"

And from there you can do whatever you want with the collected data!

Home Assistant displaying data from Govee Bluetooth temperature and humidity sensor


This was a relatively quick post and code development. I really hate the cycle of developing on my Bluetooth-less Windows computer, committing the code, pushing to Git, pulling on the Pi, and running to “debug”. Thus, the code isn’t as good as it can be. I probably did 20-25 iterations before calling it good enough.

Regardless, I think this $12 Govee Bluetooth Thermometer and Hygrometer is a great little tool for collecting data around the house. You don’t need an SDR to get Acurite beacons, and you don’t need to spend a lot either. You just need a way to receive BLE advertisements (basically any Bluetooth-capable device can do this). There is even a 2 pack of just the sensors that I just discovered on Amazon for $24 – 2 pack of Govee bluetooth thermometer and hygrometer. I know there are other Bluetooth devices but they’re quite a bit more expensive.

Disclosure: Some of the links on this post are Amazon affiliate links. This means that, at zero cost to you, I will earn an affiliate commission if you click through the link and finalize a purchase.

Also, at least for me, these are available with same day shipping on Amazon. Scratch that instant gratification itch.

Same day shipping available on Amazon near Denver for the Govee sensors

19 replies on “Using the Govee Bluetooth Thermometer with Home Assistant (Python and MQTT)”

There is an easier way with Home Assistant Community Store (HACS) with an integration called “Govee Temperature/Humidity BLE Home Assistant Component”. Works flawlessly with my setup.

Hi MrBlueSea, I have seen that recommendation a few times. I have no doubt it works as advertised. My issue is my HA is in a virtual machine without access to Bluetooth, which is why I developed this code. Also, putting the data onto MQTT allows applications other than HA to use the data.

Thanks for doing this! I live on a sailboat and have a number of small automation servers running. To have this data available via MQTT permits me to import it into my onboard NMEA-2000 network in addition to using it (more) directly by logging/graphing applications.

Hei Austin. Thanks for this.

I was wondering how you would manage with let’s say 5 devices in the house. Is there a change necessary in the python code to determine which signal comes from which device? What would your recommendation be for a Bluetooth device receiving the signals? For now I don’t plan to install an raspy next to each device to process the signalling! Thanks from Germany, Johannes

Hi Johannes, the code will automatically handle multiple devices. Each device will be published to a different MQTT topic, in the form of “govee/XX:XX:XX:XX:XX:XX” where the XX is the MAC address of the sending Govee device. You would just have to create a new sensor in the Home Assistant config for each device. A sensor is defined in HA as a few lines of text in a config file.

You may be integrated in the Xiaomi Mijia Bluetooth Thermometer 2 devices with very similar features. I grabbed a 10 pack for $28 from AliExpress. You can flash custom firmware from a chromium based browser (including your phone) to have them broadcast on any format you want, and even tweak to save battery:

All the custom firmware code is open, verifiable, and changeable.

They’re directly supported by ESPHome and just pop up in HA once configured. These little things are awesome!

thanks for the article. I am using several snippets of your code to build my own py home automation functionality.
Really like the approach to decouple HA which is just the user interface and the low level functionality, and link them via MQTT.
I am using Domoticz and HA next to each other on the same smart home in a similar way and just started to use python for the low level functionality.

I got this set up and it works great… except, I stuck one in my freezer (mostly to see if the bluetooth would still reach my raspberry pi to see if it was a viable way to monitor my freezer temp, and noticed messages stopped flowing when the sensors hit 0C.

A bit of investigative work later, and that data field just uses the first bit as a sign bit.

Here’s the snippet I came up with (I stripped a good bit out of the temp_hum function):

def temp_hum(values, battery, address):
# the data has a 1 bit in the first position if it’s negative.
mult = 1
if values[0] & 0x80 == 128:
mult = -1
# mask out the first bit
values = bytes(values[0] & 0x7ff) + values[1:]
values = int.from_bytes(values, “big”)
temp = float(values / 10000) * mult

My updated code in its entierlty can be found here:

One minor addendum – my assumptions about how ints and bytes work together was flawed, so the bitmath I posted earlier is wrong. It should look something more like:

values = (values[0] & 0x7f).to_bytes(1, “big”) + values[1:]

I went ahead and updated my github repo. This is what I get for making assumptions about “oh my freezer’s 22 degrees (F) because it’s in defrost”. ? I went and checked this time, the temperatures match!

maybe the Goove people changed something, cause the mfg_data in the Goove bluetooth advertisements does not contain any information now. (Model H5075, Firmware 1.04.04, Hardware 1.03.02)

Thank for the reply

This is what is printed into the shell/terminal:

2023-01-11 17:55:50.318 – root – INFO – connecting to MQTT broker at
2023-01-11 17:55:50.529 – root – WARNING – initializing bluetooth
2023-01-11 17:55:50.562 – root – WARNING – starting observer
2023-01-11 17:55:50.642 – root – WARNING – listening for events and publishing to MQTT
Connected with result code 0
no Data in GVH5075_FF3A
Advertisement(flags=0x00, name=’GVH5075_FF3A’, txpower=None, uuid16s=[], uuid128s=[], rssi=-63, mfg_data=None)

PS: I meant Grovee (not Groove)

I’m confused about what unit the temperature is in. I’m getting readings of 43.95 for tempF and the app gives a reading of 70+ F.

Leave a Reply

Your email address will not be published. Required fields are marked *