Home Assistant integration for a Govee Bluetooth Low Energy (BLE) devices.

• H5051
• H5052
• H5071
• H5072
• H5074
• H5075
• H5101
• H5102
• H5174
• H5177
• H5179

This component will set up the following platforms.

There are two main ways to install this custom component within your Home Assistant instance:

1. Using HACS (see https://hacs.xyz/ for installation instructions if you do not already have it installed):

   1. From within Home Assistant, click on the link to HACS
   2. Click on Integrations
   3. Click on the vertical ellipsis in the top right and select Custom repositories
   4. Enter the URL for this repository in the section that says Add custom repository URL and select Integration in the Category dropdown list
   5. Click the ADD button
   6. Close the Custom repositories window
   7. You should now be able to see the Govee BLE card on the HACS Integrations page. Click on INSTALL and proceed with the installation instructions.
   8. Restart your Home Assistant instance and then proceed to the Configuration section below.

2. Manual Installation:

   1. Download or clone this repository
   2. Copy the contents of the folder custom_components/govee_ble into the same file structure on your Home Assistant instance
      • An easy way to do this is using the Samba add-on, but feel free to do so however you want
   3. Restart your Home Assistant instance and then proceed to the Configuration section below.

While the manual installation above seems like less steps, it's important to note that you will not be able to see updates to this custom component unless you are subscribed to the watch list. You will then have to repeat each step in the process. By using HACS, you'll be able to see that an update is available and easily update the custom component.

There is a config flow for this integration. After installing the custom component and restarting Home Assistant:

1. Go to Configuration -> Integrations
2. Click + ADD INTEGRATION to setup a new integration
3. Search for Govee BLE and click on it
4. You will be guided through the rest of the setup process via the config flow

If one of your sensors is reporting incorrectly or you have a sensor that isn't showing up at all, you can enable debugging on the custom component by utilizing Home Assistant's built-in logger. Just add the following entry under the logs section in your configuration.yaml file:

custom_components.govee_ble: debug

After restarting Home Assistant, go to the logs, watch the output and consider opening a new issue on GitHub. Make sure you search for open issues before reporting, just in case someone else has already encountered it.

Because of the number of Bluetooth devices that may be within range and to limit the number of log entries, only devices that advertise their name and start with ihoment_, Govee_, Minger_, GBK_ or GVH will be logged. This is the same way the Govee app currently determines supported devices, so it may change as new devices are released. If you have a Govee device that doesn't match this pattern, please open an issue on GitHub and include the name of your Govee device that is being advertised so it can be added to the logic.

If you want to contribute to this please read the Contribution guidelines

This was originally based on/shamelessly copied/inspired from Home-Is-Where-You-Hang-Your-Hack/sensor.goveetemp_bt_hci and irremotus/govee. These, as well as asednev, were incredibly valuable resources for identifying packet data for sensors I don't own myself.