Common Errors

Here are some of the common errors you may experience with the plugin and how to resolve.

Brightness Issues

For some Govee light models, they may be a scaling issue with the brightness. You may find that turning the brightness to 100% shows as 39% in the Home app. To fix:

• In the plugin settings in the 'Light Devices' section, enter the device ID and label for the device (this can be found in the Homebridge log when the plugin starts (this can be found in the Homebridge log when the plugin starts (skip this step if you already have an entry for your light configured)
• Check the 'AWS Brightness No Scale' option (note this option will not appear until the step above has been completed)
• Restart the plugin (or Homebridge)

Colour Issues

Different Govee light models use different commands to send colour updates. The plugin default is a command called colorwc which seems to be used by most newer models. Some older models use a different command. You need to use the plugin settings to change which mode is used per device.

• In the plugin settings in the 'Light Devices' section, enter the device ID and label for the device (this can be found in the Homebridge log when the plugin starts (skip this step if you already have an entry for your light configured)
• Find the 'AWS Colour Mode' option and choose the {r, g, b} option
• Restart the plugin (or Homebridge)
• Try and control colour from the Home app - if this works then great!
• If the above step still does not control colour properly, return to the settings and try the {red, green, blue} option
• Restart the plugin (or Homebridge)
• Try and control colour from the Home app - if this works then great!
• If after trying all the options and colour control still does not work, please create an issue on this repository

No Connection Method

Entry in the log may display as:

[Govee] [Device] could not be updated as no connection method available, see https://shorturl.at/eCN04 for more info.

The plugin uses different connection methods to try and control any accessory, depending on your configuration and what the device supports. The plugin will try in the following order:

• LAN Control: (local control) if the device supports it, the device has it enabled, and the option has not been disabled in the config
• AWS Control: (cloud control) if the device supports it, and the option has not been disabled in the config
• BLE Control: (bluetooth control) if the device supports it, BLE is set up on your platform correctly, and the option has been enabled in the config

Receiving this connection error means that none of these were successful when you tried to control the device.

The best way to debug this is to restart the plugin and watch the plugin setup logs, especially around these entries:

[Govee] [HTTP] client enabled and found X device(s).
[Govee] [AWS] client enabled.
[Govee] [BLE] client enabled.

You will likely see some sort of error here instead, which will most likely be the reason why controlling devices is not working.

Bluetooth Module Not Found Error

Entry in the log may display as:

[Govee] [BLE] disabling client as Cannot find package '@abandonware/bluetooth-hci-socket' imported from /.../platform.js at new NodeError (node:internal/errors:399:5).

Solution:

• SSH into your system, enter into the root plugin directory (where it is installed - the folder with a package.json file) and run the following command:

  sudo npm i -g @abandonware/bluetooth-hci-socket

OpenSSL Errors

This plugin requires OpenSSL to be installed to be able to create certificate files to access the AWS connection method. A separate wiki page exists for OpenSSL issues - see OpenSSL.

No Devices Error

Entries in the log may display as:

• [Govee] Disabling HTTP client as timeout of 10000ms exceeded at ...
• [Govee] Disabling BLE client as no enabled devices configured.
• [Govee] ***** Disabling plugin. *****
• [Govee] ***** No devices found to initialise. *****

It has been reported that simply changing your Govee password in the Govee app, then updating your password in the plugin configuration can solve this error. It is unknown why this happens.