asednev / homebridge-plugin-govee Goto Github PK
View Code? Open in Web Editor NEWGovee H-series Thermometer Hygrometer plugin for Homebrige.
License: Apache License 2.0
Govee H-series Thermometer Hygrometer plugin for Homebrige.
License: Apache License 2.0
Describe Your Problem:
I have two H5101 that can't be discovered after installing the plugin.
Logs:
Show the Homebridge logs here, remove any sensitive information.
[1/11/2021, 8:08:28 PM] [Govee] Initializing GoveeHomebridgePlugin platform...
[1/11/2021, 8:08:28 PM] [Govee] Finished initializing platform: Govee
[1/11/2021, 8:08:28 PM] [Govee] Executed didFinishLaunching callback
[1/11/2021, 8:08:28 PM] [Govee] Start discovery
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
Environment:
This plugin is awesome! My H5072 & H5075 have been rock solid HomeKit devices with this plugin!
Any chance the H5101 could be added? I'd happily purchase you one or do any helpful grunt-work to assist in this effort.
Thanks for all you do!
Describe The Bug:
Illegal temperature value, exceeds 100.
To Reproduce:
Start HomeBridge
Expected behavior:
Temperature value within acceptable range
Logs:
[01/09/2021, 22:12:01] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:05] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:09] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:11] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:13] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:15] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:25] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:27] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:29] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:32] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:50] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:52] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:54] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:56] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:10] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:31] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:33] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:37] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:39] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:41] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:47] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:49] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:53] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:57] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:01] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:03] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:07] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:11] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:13] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:15] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:17] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:24] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:26] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:30] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:32] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:34] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:36] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:38] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:46] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:50] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:00] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:10] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:29] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:31] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:39] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7808 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:41] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
},
Environment:
Hi,
I love this plugin. I have been using Govee H5102 and it works perfectly. However once I decided to change the name of the humidity and temperature widgets on Homekit, a bug developed. After I changed the names two new widgets created with the old name, and they are stuck with the last temperature measurement before I changed the names. I was unable to find a way to get rid of the duplicate/stuck sensors.
This also is replicated in the accessories window. See below.
Thanks a lot!
I use the plugin in my homebridge with v16.13.1. The plugin is up to date.
I am currently using two govee sensors.
LG
Hello @asednev
I was curious, does this plugin support Raspberry Pi with Homebridge? I dug into the Linux details and saw it had Raspbian support but I wanted to clarify since I didn’t see the RPI3+ as a supported device.
If it is supported, could you provide any details as to how I could get it installed?
Thanks for the clarification!
Describe The Bug:
Plugin fails after latest updates of Node.JS and NPM
Core error is:
was compiled against a different Node.js version using
NODE_MODULE_VERSION 83. This version of Node.js requires
NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
To Reproduce:
Restart Homebridge and see the log
Expected behavior:
Plugin used to work.
Logs:
[31/10/2021, 12:17:10] ERROR LOADING PLUGIN homebridge-plugin-govee:
[31/10/2021, 12:17:10] Error: The module '/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 83. This version of Node.js requires
NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1183:18)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/bluetooth-hci-socket/lib/native.js:6:15)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
[31/10/2021, 12:17:10] ====================
Plugin Config:
{
"bridge": {
"name": "Homebridge 0B0E",
"username": "8D:B1:26:D1:0B:0E",
"port": 51605,
"pin": "552-54-814",
"bind": [
"eth0"
],
"advertiser": "bonjour-hap"
},
"accessories": [
{
"delay": 5000,
"disableSensor": false,
"startOnReboot": false,
"accessory": "DelaySwitch"
}
],
"platforms": [
{
"name": "Config",
"port": 8581,
"auth": "form",
"theme": "auto",
"tempUnits": "f",
"lang": "auto",
"sessionTimeout": 86400000,
"platform": "config"
},
{
"controllers": [
{
"address": "172.16.16.1",
"password": "secret",
"username": "secret"
}
],
"verboseFfmpeg": false,
"platform": "UniFi Protect"
},
{
"name": "Govee Hydrometer",
"batteryThreshold": 25,
"debug": false,
"platform": "GoveeHomebridgePlugin"
},
{
"bonds": [
{
"ip_address": "172.16.16.162",
"token": "e93448df34bs15"
}
],
"include_dimmer": false,
"include_toggle_state": false,
"fan_speed_values": true,
"platform": "Bond"
},
{
"name": "Meross",
"username": "secret",
"password": "secret",
"ignoreHKNative": true,
"platform": "Meross"
},
{
"name": "Govee",
"username": "secret",
"password": "secret",
"apiKey": "372-sdgwadfsdg-9f4f-b3f6b0e9f69b",
"platform": "Govee"
}
],
"disabledPlugins": []
}
Screenshots:
Environment:
Describe The Bug:
With the Govee plugin running on a child bridge, the child bridge is stuck in a restart loop, causing previously discovered accessories to be unavailable to Homekit/Homebridge.
To Reproduce:
Configure and run the Govee plugin.
Expected behavior:
Govee child bridge comes online and works properly.
Logs:
[14/02/2022, 09:52:33] [Govee] Restarting Process...
[14/02/2022, 09:52:34] [Govee] Launched child bridge with PID 22164
[14/02/2022, 09:52:34] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
[14/02/2022, 09:52:34] [Govee] Loaded homebridge-plugin-govee v1.1.4 child bridge successfully
[14/02/2022, 09:52:35] Loaded 2 cached accessories from cachedAccessories.xxxxxxxxxxxx.
[14/02/2022, 09:52:35] [Govee] Finished initializing platform: Govee
[14/02/2022, 09:52:35] [Govee] Loading accessory from cache: xxxxxxxxxxx
[14/02/2022, 09:52:35] [Govee] Loading accessory from cache: xxxxxxxxxxx
[14/02/2022, 09:52:35] Publishing bridge accessory (name: Govee, publishInfo: {
username: 'xx:xx:xx:xx:xx:xx',
port: 49339,
pincode: '***-**-***',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'ciao'
}).
[14/02/2022, 09:52:35] [Govee] Executed didFinishLaunching callback
[14/02/2022, 09:52:35] [Govee] Start discovery
[14/02/2022, 09:52:35] Homebridge v1.4.0 (HAP v0.10.0) (Govee) is running on port 49339.
/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:121
this._socket.bindRaw(this._deviceId);
^
Error: ENODEV, No such device
at Hci.init (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:121:20)
at NobleBindings.init (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:93:13)
at Noble.startScanning (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:145:20)
at /usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:155:44
at node:internal/util:360:7
at new Promise (<anonymous>)
at node:internal/util:346:12
at Noble.startScanningAsync (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:155:99)
at startDiscovery (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/govee-bt-client/dist/index.js:84:27)
at GoveeHomebridgePlatform.discoverDevices (/usr/local/lib/node_modules/homebridge-plugin-govee/src/platform.ts:88:24)
[14/02/2022, 09:52:35] [Govee] Child bridge process ended
[14/02/2022, 09:52:35] [Govee] Process Ended. Code: 1, Signal: null
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"humidityOffset": 0,
"_bridge": {
"username": "xx:xx:xx:xx:xx:xx",
"port": 49339
},
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
Environment:
Describe The Bug:
After the upgrade to Node 16.13 the govee Homebridge plugin no longer loads.
To Reproduce:
Upgrading to Node 16.13 and rebooting the service causes this. The downgrade back to Node 14 makes the plugin work again.
Expected behavior:
The plugin should work the sameway regardless of the node version.
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 20,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin",
"_bridge": {
"username": "0E:AA:3C:XX:XX:XX",
"port": 57030
}
},
Screenshots:
Environment:
Describe Your Problem:
Logs:
Install:
/homebridge # npm install --save homebridge-plugin-govee@latest
> [email protected] install /homebridge/node_modules/homebridge-plugin-govee/node_modules/usb
> prebuild-install --verbose || node-gyp rebuild
prebuild-install info begin Prebuild-install version 5.3.6
prebuild-install info looking for cached prebuild @ /root/.npm/_prebuilds/a5f1ee-usb-v1.6.3-node-v83-linuxmusl-x64.tar.gz
prebuild-install http request GET https://github.com/tessel/node-usb/releases/download/v1.6.3/usb-v1.6.3-node-v83-linuxmusl-x64.tar.gz
prebuild-install http 404 https://github.com/tessel/node-usb/releases/download/v1.6.3/usb-v1.6.3-node-v83-linuxmusl-x64.tar.gz
prebuild-install WARN install No prebuilt binaries found (target=14.15.0 runtime=node arch=x64 libc=musl platform=linux)
make: Entering directory '/homebridge/node_modules/homebridge-plugin-govee/node_modules/usb/build'
CC(target) Release/obj.target/libusb/libusb/libusb/core.o
CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
CC(target) Release/obj.target/libusb/libusb/libusb/io.o
CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
../libusb/libusb/os/linux_udev.c:40:10: fatal error: libudev.h: No such file or directory
40 | #include <libudev.h>
| ^~~~~~~~~~~
compilation terminated.
make: *** [libusb.target.mk:150: Release/obj.target/libusb/libusb/libusb/os/linux_udev.o] Error 1
make: Leaving directory '/homebridge/node_modules/homebridge-plugin-govee/node_modules/usb/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Linux 5.4.0-52-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /homebridge/node_modules/homebridge-plugin-govee/node_modules/usb
gyp ERR! node -v v14.15.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-plugin-govee/node_modules/usb):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `prebuild-install --verbose || node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
+ [email protected]
updated 1 package in 19.522s
Startup:
Loaded plugin: [email protected]
Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
Plugin Config:
{
"bridge": {
...
},
"accessories": [],
"platforms": [
{
...
"platform": "config"
},
{
...
"platform": "BelkinWeMo"
},
{
...
"platform": "myQ"
},
{
...
"platform": "HarmonyHubWebSocket"
},
{
...
"platform": "Camera-ffmpeg"
},
{
...
"platform": "TplinkSmarthome"
},
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"platform": "GoveeHomebridgePlugin"
}
]
}
Screenshots:
n/a
Environment:
I would love to be able to use my HomeKit hub's "Sensor detects something" feature to automatically trigger based on the temp/humidity getting too low.
Homekit doesn't let you observe readings of a device and make automation decisions that way, the output needs to be binary (temperature IS or ISN'T too low). The idea is to augment this plugins with optional fields in the config like:
{
"minimum_temp_f" : 65,
"minimum_humidity": 35
}
When the plugin checks the bluetooth device status, it can output a "true" or "false" based on the condition. Perhaps it can mimic a motion sensor and act that way to trigger the automation.
Have you thought about adding this/hit any roadblocks. I'm new to the homekit/homebridge api, so perhaps i'm missing something that makes this not feasible. Happy to implement it myself once I get some time.
Describe Your Problem:
No devices detected, even after waiting 20 minutes after plugin load
Logs:
�[37m[1/18/2022, 8:37:34 PM] �[39mLoaded plugin: [email protected]
�[37m[1/18/2022, 8:37:34 PM] �[39mRegistering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
�[37m[1/18/2022, 8:37:35 PM] �[39m�[36m[Govee]�[39m Initializing GoveeHomebridgePlugin platform...
�[37m[1/18/2022, 8:37:35 PM] �[39m�[36m[Govee]�[39m Finished initializing platform: Govee
�[37m[1/18/2022, 8:37:35 PM] �[39m�[36m[Govee]�[39m �[90mExecuted didFinishLaunching callback�[39m
�[37m[1/18/2022, 8:37:35 PM] �[39m�[36m[Govee]�[39m �[90mStart discovery�[39m
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
N/A
Environment:
Describe Your Problem:
The H5075 hygrometers load into Homebridge just fine with the plugin. I see a flurry of updates from the hygrometers after the boot has completed of HomeBridge and it stabilizes. The issue is after a little bit of time the status changes don't appear to happen and the data in the Home App becomes stale and does not update. I can sometimes trigger an update by closing the Home App and opening it back up but this is rare.
I have tried to trigger changes with one of the hygrometers and even after a 5 degree change in temperature there is no change in the HomeBridge logs with debugging turned on. I know the hygrometers are working beucase I am also using their data in Home Asistant and the sensors in there react to the data coming from the hygrometers.
Logs:
The only thing after the initial updates that I see in the logs with debugging turned on is the like the following. It appears that only one is giving updates.
[28/01/2021, 16:39:37] [Backyard Christmas Lights Plug 2] Retrieved status unsuccessfully.
[28/01/2021, 16:39:37] [Backyard Christmas Lights Plug 2] getOnCharacteristicHandler: false
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getStatusLowBattery
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getCurrentTemperature 21.5369
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getCurrentRelativeHumidity 36.9 offset 0
[28/01/2021, 16:39:38] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:43] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:48] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:53] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:02] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:03] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:08] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:13] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:18] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:23] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:28] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:33] [Garage Door] Current state CLOSED
Show the Homebridge logs here, remove any sensitive information.
[28/01/2021, 16:39:37] [Backyard Christmas Lights Plug 2] Retrieved status unsuccessfully.
[28/01/2021, 16:39:37] [Backyard Christmas Lights Plug 2] getOnCharacteristicHandler: false
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getStatusLowBattery
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getCurrentTemperature 21.5369
[28/01/2021, 16:39:37] [Govee-Home-Hygrometers-3] getCurrentRelativeHumidity 36.9 offset 0
[28/01/2021, 16:39:38] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:43] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:48] [Garage Door] Current state CLOSED
[28/01/2021, 16:39:53] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:02] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:03] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:08] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:13] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:18] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:23] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:28] [Garage Door] Current state CLOSED
[28/01/2021, 16:40:33] [Garage Door] Current state CLOSED
Plugin Config:
{
"name": "Govee-Home-Hygrometers-3",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
{
"bridge": {
"name": "ABIT-H-HomeBR",
"username": "XXXX",
"port": XXXX,
"pin": "XXX-XX-XXX"
},
"accessories": [
{
"model": "MSG100",
"name": "Garage Door",
"deviceUrl": "172.30.20.70",
"channel": 0,
"messageId": "XXXXXX",
"timestamp": XXXXXX,
"sign": "XXXXX",
"garageDoorOpeningTime": 20,
"accessory": "Meross"
},
{
"model": "MSS620",
"name": "South Fence Rope Light",
"deviceUrl": "172.30.20.72",
"channel": 1,
"messageId": "XXX",
"timestamp": XXX,
"sign": "XXX",
"accessory": "Meross"
},
{
"model": "MSS620",
"name": "Backyard Christmas Lights Plug 2",
"deviceUrl": "172.30.20.72",
"channel": 2,
"messageId": "XXXXX",
"timestamp": XXXXX,
"sign": "XXXXX",
"accessory": "Meross"
},
{
"model": "MSS620",
"name": "North Fence Rope Light",
"deviceUrl": "172.30.20.71",
"channel": 2,
"messageId": "XXXX",
"timestamp": XXXX,
"sign": "XXXXX",
"accessory": "Meross"
},
{
"model": "MSS620",
"name": "Stars and Pole Rope Lights",
"deviceUrl": "172.30.20.71",
"channel": 1,
"messageId": "XXXXX",
"timestamp": XXXXX,
"sign": "XXXX",
"accessory": "Meross"
}
],
"platforms": [
{
"name": "ABIT-H-HomeBridge1911",
"port": XXXX,
"auth": "form",
"theme": "auto",
"tempUnits": "f",
"lang": "auto",
"platform": "config"
},
{
"name": "Nest",
"googleAuth": {
"issueToken": "XXXXXX",
"cookies": "XXXXX"
},
"platform": "Nest"
},
{
"name": "ABIT-HUB",
"hubIP": "172.30.20.92",
"hubName": "ABIT-HUB",
"platform": "HarmonyHubWebSocket"
},
{
"name": "Camera FFmpeg",
"cameras": [
{
"name": "Front Yard",
"videoConfig": {
"source": "-i rtsp://XXXXXX",
"maxStreams": 3,
"maxFPS": 0,
"audio": true
}
},
{
"name": "Side Yard",
"videoConfig": {
"source": "-i rtsp://XXXX:XXXXXX",
"maxStreams": 3,
"maxFPS": 0
}
}
],
"platform": "Camera-ffmpeg"
},
{
"name": "Wemo",
"discoveryInterval": 30,
"disableDiscovery": false,
"disableDeviceLogging": false,
"debug": false,
"disablePlugin": false,
"noMotionTimer": 60,
"doorOpenTimer": 20,
"manualDevices": [
"http://172.30.40.70:49153/setup.xml",
"http://172.30.40.71:49153/setup.xml",
"http://172.30.40.72:49153/setup.xml",
"http://172.30.40.73:49153/setup.xml",
"http://172.30.40.74:49153/setup.xml",
"http://172.30.40.75:49153/setup.xml"
],
"makerTypes": [
{
"makerTimer": 20
}
],
"platform": "BelkinWeMo"
},
{
"name": "Govee-Home-Hygrometers-3",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
]
}
Screenshots:
Environment:
My hygrometer has always run about 10% high. Is there something I could add to the config to reduce the value displayed in homekit by the device? I’m running the h5072.
Describe Your Problem:
I had some issues in the past with Bluetooth plugins conflicting. renssies/homebridge-am43-blinds#31
I think one of them was making continuous calls and so was overusing noble while the other couldn't. Have you experienced this/tried this plugin with other plugins using noble? Just wanted to check before buying.
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
Describe Your Problem:
I have a 5075, this plugin is not detecting it/not working
Thermometer is otherwise working fine and shows data in the Govee app
The Thermostat is less than 10 feet away form the Raspberry Pi running homebridge
Logs:
discovered a4c138bc6239 a4c138bc6239 a4:c1:38:bc:62:39 disconnected -63
invalid peripheral, scan for another
Many of these over and over again...
Plugin Config:
{
"name": "Govee Thermo",
"batteryThreshold": 25,
"debug": true,
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
None
Environment:
Hi,
I have two Govee temp/humidity sensors, the H5051 and H5071. They both advertise over BLE and I can see them from my RPI when I scan for BLE devices.
I have this plugin installed for Homebridge, and when debug is checked it spits out a series of “invalid peripheral” messages as it presumably discovers things it doesn’t understand.
Would it be possible to add support for these two devices? Happy to help if I can.
Thanks!
Dan
Describe The Bug:
Upgrading to 1.1.5 broke the plugin, causing a TypeError
To Reproduce:
Install 1.1.5
Configure with no ignored devices.
Expected behavior:
Expected the plugin to continue to work correctly,
Logs:
TypeError: Cannot read properties of undefined (reading 'includes')
at GoveeHomebridgePlatform.goveeDiscoveredReading (/usr/local/lib/node_modules/homebridge-plugin-govee/dist/platform.js:76:32)
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
},
Environment:
Hi!, I've installed your plugin but I had to disable it due to multiple log messages like those:
29/6/2021 18:25:16] [Termohigrómetro] Govee discovery stopped while Homebridge is running.
[29/6/2021 18:25:16] [Termohigrómetro] Restart Discovery
[29/6/2021 18:25:16] [Termohigrómetro] Govee discovery stopped while Homebridge is running.
[29/6/2021 18:25:16] [Termohigrómetro] Restart Discovery
scanStart
[29/6/2021 18:25:16] [Termohigrómetro] Govee Scan Started
scanStop
[29/6/2021 18:25:16] [Termohigrómetro] Govee Scan Stopped
[29/6/2021 18:25:16] [Termohigrómetro] Govee discovery stopped while Homebridge is running.
[29/6/2021 18:25:16] [Termohigrómetro] Restart Discovery
scanStart
[29/6/2021 18:25:16] [Termohigrómetro] Govee Scan Started
[29/6/2021 18:25:16] [Termohigrómetro] Govee discovery stopped while Homebridge is running.
[29/6/2021 18:25:16] [Termohigrómetro] Restart Discovery
scanStop
[29/6/2021 18:25:16] [Termohigrómetro] Govee Scan Stopped
[29/6/2021 18:25:16] [Termohigrómetro] Govee discovery stopped while Homebridge is
the plugin is in the last version (1.1.2) and the device is H5075.
Thanks in advance!
Describe The Bug:
When running homebridge with docker / docker-compose, the plugin doesn't work. In Debug mode, the error Could not start scanning, state is unsupported (not poweredOn)
appears when homebridge boots up.
I also tried to run homebridge with the -privileged
and --net=host
flags but it still throws the error.
The Bluetooth dongle works as expected!
A found similar issues from other (homebridge) projects that might help:
hannseman/homebridge-mi-hygrothermograph#48
noble/noble#228
To Reproduce:
Expected behavior:
The scanning process should work with a docker / docker-compose setup.
Logs:
Full error log in Debug mode:
Error: Could not start scanning, state is unsupported (not poweredOn)
at Noble.scan (/homebridge/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:107:21)
at Object.onceWrapper (node:events:510:26)
at Noble.emit (node:events:390:28)
at Noble.onStateChange (/homebridge/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:87:8)
at NobleBindings.emit (node:events:390:28)
at NobleBindings.onStateChange (/homebridge/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:125:8)
at Hci.emit (node:events:402:35)
at Hci.processCmdCompleteEvent (/homebridge/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:699:12)
at Hci.onSocketData (/homebridge/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:567:12)
at BluetoothHciSocket.emit (node:events:390:28)
Plugin Config:
Default
Environment:
Is your feature request related to a problem? Please describe:
I have two of the H5074 BLE devices and have been looking for a way to integrate with HomeBridge
Describe the solution you'd like:
Support for H5074 model
I can test if you would like.
I have previously looked into doing this on my own (to no avail) but I was able to read the devices from my Pi.
Thanks!
Describe Your Problem:
I run Homebridge through Docker on a Raspberry Pi 4B running Ubuntu. Everything is up to date.
After installing homebridge-plugin-govee v1.0.12 through the web-interface the logs show following issues
Logs:
[3/30/2021, 3:38:45 PM] Homebridge v1.3.4 (Homebridge) is running on port 51735.
(node:1617) UnhandledPromiseRejectionWarning: Error: ENODEV, No such device
at Hci.init (/homebridge/node_modules/govee-bt-client/node_modules/@abandonware/noble/lib/hci-socket/hci.js:114:35)
at NobleBindings.init (/homebridge/node_modules/govee-bt-client/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:82:13)
at Noble.startScanning (/homebridge/node_modules/govee-bt-client/node_modules/@abandonware/noble/lib/noble.js:132:20)
at /homebridge/node_modules/govee-bt-client/node_modules/@abandonware/noble/lib/noble.js:142:44
at internal/util.js:297:30
at new Promise (<anonymous>)
at internal/util.js:296:12
at Noble.startScanningAsync (/homebridge/node_modules/govee-bt-client/node_modules/@abandonware/noble/lib/noble.js:142:99)
at Object.exports.startDiscovery (/homebridge/node_modules/govee-bt-client/dist/index.js:83:27)
at GoveeHomebridgePlatform.discoverDevices (/homebridge/node_modules/homebridge-plugin-govee/src/platform.ts:78:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1617) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:1617) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[3/30/2021, 3:38:45 PM] [BroadlinkRM] [INFO] ...
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Environment:
Describe The Bug:
Incompatible with other plugins using noble, like: https://github.com/SwitchBot/homebridge-switchbot-ble/
What happens is the switch bot activates and turns the switch, but then this plugin is causing homebdige to crash.
To Reproduce:
Install a Switch Bot (or any other bluetooth device that has a Homebridge plugin), add the Homebridge plugin, configure the device. Click the switch to make the switch bot go (or whatever for your bluetooth device) and this is when Homebridge crashes with the following error log below.
Expected behavior:
No crash from Homebridge. Seems like this or govee-bt-client
are looking at requests it should be be and causing a crash.
Logs:
noble: unknown peripheral <MAC OF SWITCHBOT> handle notify!
[08/11/2020, 21:35:59] TypeError: Cannot set property 'mtu' of undefined
at Noble.onMtu (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:564:18)
at NobleBindings.emit (events.js:315:20)
at NobleBindings.onMtu (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:277:8)
at Gatt.emit (events.js:315:20)
at Object.callback (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/gatt.js:329:10)
at Gatt.onAclStreamData (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/gatt.js:133:26)
at AclStream.emit (events.js:327:22)
at AclStream.push (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/acl-stream.js:33:10)
at NobleBindings.onAclDataPkt (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:288:15)
at Hci.emit (events.js:315:20)
at Hci.onSocketData (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:501:14)
at BluetoothHciSocket.emit (events.js:315:20)
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"platform": "GoveeHomebridgePlugin"
},
{
"platform": "SwitchBotPlatform",
"name": "SwitchBotPlatform",
"devices": [
{
"type": "bot",
"name": "Switch Bot Switch 1",
"bleMac": "<MAC>"
}
]
}
Screenshots:
None needed
Environment:
Describe Your Problem:
The plug is no longer working after the upgrade to 1.3.3
Logs:
ERROR LOADING PLUGIN homebridge-plugin-govee:
[3/11/2021, 8:43:47 AM] TypeError: require(...) is not a constructor
at module.exports (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/resolve-bindings.js:11:12)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/index.js:2:51)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/govee-bt-client/dist/index.js:17:33)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
[3/11/2021, 8:43:47 AM] ====================
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
Environment:
I've loved this plugin for my H5072 & H5075 thermometer's.
Any chance of it working with the bluetooth meat thermometer's? I just purchased a one of each of the following. One for my smoker and one for my pool. I'd be thrilled it I could get them connected to homebridge like my other Govee devices.
From what I can tell, it looks like temperature is ROUNDED UP, to the nearest degree. Why?
Why not, not round at all and just give the temperature to the tens?
Describe Your Problem:
I am seeing 3 devices with different names instead of 2. My believe is, that one of my neighbors has on of the H5075, which will show in my Govee Pluign.
Logs:
[12/11/2021, 10:56:51] [Govee] Adding new accessory: GVH50753B9C
[12/11/2021, 10:56:54] [Govee] Adding new accessory: GVH507552D0
[12/11/2021, 10:57:06] [Govee] Adding new accessory: GVH50759447
the one with 2D0 is not mine.
I tried to disable it on the Homebridge GUI by hiding it, but it will end up in homekit anyhow and cannot delete it in homekit.
Is there any way to configure the Govee Plugin to not deliver this device anymore.
And if not, I believe it would be a needed enhancement.
Describe The Bug:
logs running constantly and possibly kiliing my Hoobs hub in HOOBS 4
To Reproduce:
Running 5 sensors
Expected behavior:
less verbose logs and stable in Hoob 4
Logs:
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
ERROR
(node:630) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 scanStart listeners added to [Noble]. Use emitter.setMaxListeners() to increase limit
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Govee Scan Started
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Govee Scan Started
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Govee Scan Started
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:10 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:15 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
Restart Discovery
4/15/2021, 8:41:20 AM
Plugin Govee Bridge
Govee
WARNING
Govee discovery stopped while Bridge is running.
4/15/2021, 8:41:25 AM
Plugin Govee Bridge stopping
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
4/15/2021, 8:41:25 AM
Plugin Govee Bridge
Govee
Govee Scan Stopped
Show the Homebridge logs here, remove any sensitive information.
**Plugin Config:**
{
"accessories": [],
"platforms": [
{
"platform": "GoveeHomebridgePlugin",
"name": "Govee",
"batteryThreshold": "25",
"humidityOffset": "0"
}
]
}
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
Describe Your Problem:
Preface this by saying I am new to HB. I have attempted to install this plugin on a raspberry pi 4. The HB interface is saying it is installed successfully and showing it in my configuration, but it is not showing in my logs. During install, I am seeing errors flash, but not sure how to capture what they are (install window on HB goes by so fast and can’t find records afterwards). What could I try differently to successfully install the plugin?Logs:
Plug in not showing in logs
Plugin Config:
"batteryThreshold": 20,
"debug": true,
"platform": "GoveeHomebridgePlugin"
Screenshots:
Environment:
Describe The Bug:
The plugin appears to be finding the same device but with extra non-printable-characters in various places:
I have tried deleting these extraneous/duplicate devices from the cache but they keep coming back
Perhaps needs some ascii encoding of device name prior to accepting? Some kind of bluetooth issue that we need to account for?
To Reproduce:
Auto-discovery
Expected behavior:
Its duplicate with a strange name:
Logs:
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075BCCA
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075F5C1
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075E486
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH50753CCC
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075E46
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075F51
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: VH50753CCC
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: VH5075F5C1
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH50753CC
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075FC1
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075E86
[13/03/2021, 12:46:06] [Govee] Loading accessory from cache: GVH5075BCA
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 15,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Environment:
First off, thanks for the great plugin. It works incredibly well and does exactly as advertised, right out of the box. Was surprised and happy to see my two new 5075s added a few seconds after I put the batteries in. No config or anything required, Effectively instant. Great stuff!
Is your feature request related to a problem? Please describe:
I'm looking to collect historical data. I need to see a time series on temperatures in the rooms I place the devices. I currently use the TIG stack on my raspberry 4B. But can also do MQTT. Just need the data to start being exported somewhere.
Describe the solution you'd like:
Some kind of facility within the plugin to specify a destination for data collected on devices, ideally per output type. So for a 5075 it'd be ideal to give it a name to associate with the data "Office Temp", "Office Humidity", and simply have the data punted off to a data storage system (Telegraf, MQTT, whatever is easiest for you to implement).
Describe alternatives you've considered:
I looked around for ways to get homebridge to do this as I'm very new to it and expected that this would be an out-of-the-box function for a system like this. Especially since "data collection" comes hand-in-hand with the community that wants data presentation / smart home systems like this, For whatever reason, it's not though :(. Not complaining - homebridge is a great tool that works incredibly well - just very surprised.
I also looked at whether there were other plugins that would allow me to get access to the data you are presenting and then log it. But it appears (perhaps I'm wrong?) that each plugin and its respective data is quite discrete, and as such another plugin isn't able to see & store your plugin's data.
Additional context:
homebridge-mqttthing does this for a bunch of homekit devices and may provide a rich library of code from which equal functionality could be derived.
homebridge-mi-hygrothermograph also specifically supports MQTT. Given the similarities this may be even better than mqttthing for copy-paste of functionality.
I've not seen anything support Telegraf or other data storage so can't provide examples, though I think Telegraf would be a more ideal destination for the data given its rich feature set.
Describe Your Problem:
Plug-in worked just fine up until a few versions ago, (2) I believe. Now I get the below error, even after following the Bluetooth instructions
(Also get same error if not in a child bridge)
Logs:
[08/01/2022, 16:58:53] [Govee] Launched child bridge with PID 15258
[08/01/2022, 16:58:54] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
[08/01/2022, 16:58:54] [Govee] Loaded homebridge-plugin-govee v1.1.4 child bridge successfully
[08/01/2022, 16:58:54] [Govee] Finished initializing platform: Govee
[08/01/2022, 16:58:54] Homebridge v1.3.9 (HAP v0.9.8) (Govee) is running on port 49007.
/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:121
this._socket.bindRaw(this._deviceId);
^
Error: ENODEV, No such device
at Hci.init (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:121:20)
at NobleBindings.init (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:93:13)
at Noble.startScanning (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:145:20)
at /usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:155:44
at node:internal/util:360:7
at new Promise (<anonymous>)
at node:internal/util:346:12
at Noble.startScanningAsync (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:155:99)
at startDiscovery (/usr/local/lib/node_modules/homebridge-plugin-govee/node_modules/govee-bt-client/dist/index.js:84:27)
at GoveeHomebridgePlatform.discoverDevices (/usr/local/lib/node_modules/homebridge-plugin-govee/src/platform.ts:88:24)
[08/01/2022, 16:58:54] [Govee] Child bridge process ended
[08/01/2022, 16:58:54] [Govee] Process Ended. Code: 1, Signal: null
[08/01/2022, 16:59:01] [Govee] Restarting Process...
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin",
"_bridge": {
"username": "0E:D5:D9:F9:7D:BE",
"port": 49007
}
Screenshots:
Environment:
Just something else I wanted to mention, the name of this plugin considering it's unique purpose is too simple. It could easily be confused with the Govee Light plugin (which uses the Govee API, not bluetooth) https://www.npmjs.com/package/homebridge-govee
Perhaps renaming it to homebridge-govee-thermo-hygrometer
or something?
Only using one Govee sensor (H5074) with the plugin and it seems to stop updating several hours after Homebridge starts:
Here's the debug log while working:
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -63
invalid peripheral, manufacturerData=[4c000215494e54454c4c495f524f434b535f485750740d6dc2]
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -70
invalid peripheral, manufacturerData=[4c000215494e54454c4c495f524f434b535f485750740d6dc2]
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -60
invalid peripheral, manufacturerData=[4c000215494e54454c4c495f524f434b535f485750740d6dc2]
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -62
invalid peripheral, manufacturerData=[4c000215494e54454c4c495f524f434b535f485750740d6dc2]
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -62
invalid peripheral, manufacturerData=[4c000215494e54454c4c495f524f434b535f485750740d6dc2]
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -63
e38c81326d0d: 88ec0078038c136402
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -71
e38c81326d0d: 88ec0078038c136402
Debug log once it stops updating:
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -50
e38c81326d0d: 88ec0058045b0e6402
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -65
e38c81326d0d: 88ec0058045b0e6402
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -50
e38c81326d0d: 88ec0058045b0e6402
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -66
e38c81326d0d: 88ec0058045b0e6402
discovered e38c81326d0d e38c81326d0d e3:8c:81:32:6d:0d disconnected -50
e38c81326d0d: 88ec0058045b0e6402
Describe The Bug:
Multiple entries or sensors are showing up for the sensors in my Home app
To Reproduce:
Install homebridge-plugin-govee start home bridge service, open Home app
Expected behavior:
App should only show 2 sensors per device, 1 for RH and 1 for temp
Logs:
M [Govee] Initializing GoveeHomebridgePlugin platform...
1/30/2021, 9:01:36 PM [Govee] Finished initializing platform: Govee
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: GoveeH5074_D50C
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: GoveeH5074_DC�
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: Govee4_D50C��>
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: GoveeH5074_D5C
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: Govee5074D50C�
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: GVH507526A4
1/30/2021, 9:01:36 PM [Govee] Loading accessory from cache: GVH50756A4
Plugin Config:
},
"name": "Govee",
"batteryThreshold": "25",
"debug": false,
"humidityOffset": "0"
}
Environment:
Is your feature request related to a problem? Please describe:
I have mulitiple sensors and they seem to come in as names like GVH5075C68A but I cant fina a correlation in the Govee app so I having a hard time adding multiple sensors and differentiating them
Describe the solution you'd like:
possibly a way to correlate the sensor name as they are labeled in the Govee app or another method to tell them apart
Describe alternatives you've considered:
Tried looking for these IDs in the Govee app but cant find them
Additional context:
Describe Your Problem:
Each of my sensors have a name (Garage, Office, Small/Large Bin). Each of those I have set up in the UI to have that name, but when looking at HomeKit (and the 'Name' section in the accessory) It is the GVH5101XXXX. I was wondering if instead of those names going to HomeKit, the 'chosen' name given in the UI could instead (if set).
Logs:
[1/2/2022, 9:09:27 PM] [Govee] Restoring existing accessory from cache: GVH51011234
[1/2/2022, 9:09:27 PM] [Govee] Restoring existing accessory from cache: GVH51015555
[1/2/2022, 9:09:28 PM] [Govee] Restoring existing accessory from cache: GVH51016633
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
None
Environment:
BTW I am testing this on HOOBS 4 Beta now... seems to be working... just getting this in logs...
4/3/2021, 2:58:21 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH50755A3F@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:21 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:21 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:21 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:23 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH50755A3F@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:23 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH50755A3F@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:23 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH50755A3F@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:25 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:25 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:25 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:33 PM
Plugin Govee Bridge
WARNING
[Plugin Govee Bridge E6D8@GVH5075C68A@@current Relative Humidity] characteristic was supplied illegal value: number 290 exceeded maximum of 100
4/3/2021, 2:58:33 PM
Plugin Govee Bridge
WARNIN
Originally posted by @saiajin in #30 (comment)
Describe The Bug:
Every time I reboot Homebridge I get errors when it try to start up this plugin. It then never scans for/shows my devices.
To Reproduce:
Start homebridge
I have re-installed homebridge, and even raspberry pi os itself
Expected behavior:
Plugin to find and display my govee thermometers
Logs:
[16/03/2021, 03:05:52] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[16/03/2021, 03:05:57] [HB Supervisor] Restarting Homebridge...
[16/03/2021, 03:05:57] [HB Supervisor] Starting Homebridge with extra flags: -I
[16/03/2021, 03:05:57] [HB Supervisor] Started Homebridge v1.3.3 with PID: 3641
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 03:05:58] Loaded config.json with 4 accessories and 5 platforms.
[16/03/2021, 03:05:58] Loaded 0 cached accessories from cachedAccessories.
[16/03/2021, 03:05:58] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering platform 'homebridge-config-ui-x.config'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering accessory 'homebridge-dummy.DummySwitch'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering accessory 'homebridge-messenger.HomebridgeMessenger'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering platform 'homebridge-nest.Nest'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:05:59] Loaded plugin: [email protected]
[16/03/2021, 03:05:59] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
[16/03/2021, 03:05:59] ---
[16/03/2021, 03:06:00] Loaded plugin: [email protected]
[16/03/2021, 03:06:00] Registering platform 'homebridge-ring.Ring'
[16/03/2021, 03:06:00] ---
[16/03/2021, 03:06:00] Loading 5 platforms...
[16/03/2021, 03:06:00] [Config] Initializing config platform...
[16/03/2021, 03:06:00] [Config] Running in Service Mode
[16/03/2021, 03:06:00] [Ring] Initializing Ring platform...
[16/03/2021, 03:06:00] [Ring] Initializing child bridge 0E:BD:D2:B3:8D:00
[16/03/2021, 03:06:00] [Nest] Initializing Nest platform...
[16/03/2021, 03:06:00] [Nest] Initializing child bridge 0E:ED:C4:3E:E2:D9
[16/03/2021, 03:06:00] [Camera FFmpeg] Initializing Camera-ffmpeg platform...
[16/03/2021, 03:06:00] [Camera FFmpeg] Initializing child bridge 0E:1A:D9:82:FA:6C
[16/03/2021, 03:06:00] [Govee] Initializing GoveeHomebridgePlugin platform...
[16/03/2021, 03:06:00] [Govee] Finished initializing platform: Govee
[16/03/2021, 03:06:00] Loading 4 accessories...
[16/03/2021, 03:06:00] [Messenger] Initializing HomebridgeMessenger accessory...
[16/03/2021, 03:06:00] [Messenger] Initializing child bridge 0E:C5:10:F1:DD:94
[16/03/2021, 03:06:00] [Present] Initializing DummySwitch accessory...
[16/03/2021, 03:06:00] [Present] Initializing child bridge 0E:AB:37:4C:1E:AC
[16/03/2021, 03:06:00] [Present] Initializing DummySwitch accessory...
[16/03/2021, 03:06:00] [Present] Initializing child bridge 0E:EB:E0:4E:F5:9A
[16/03/2021, 03:06:00] [Present] Initializing DummySwitch accessory...
[16/03/2021, 03:06:00] [Present] Initializing child bridge 0E:DF:32:A6:D4:1C
Preparing Advertiser for 'Homebridge 1234 567' using bonjour-hap backend!
Setup Payload:
X-HM://0024LMNIH2CE9
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ ABC-12-123 │
└────────────┘
Starting to advertise 'Homebridge ABCD 1234' using bonjour-hap backend!
[16/03/2021, 03:06:01] Homebridge v1.3.3 (Homebridge 8C5D) is running on port 51627.
(node:3641) UnhandledPromiseRejectionWarning: Error: ENODEV, No such device
at Hci.init (/usr/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/hci.js:114:35)
at NobleBindings.init (/usr/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:82:13)
at Noble.startScanning (/usr/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:132:20)
at /usr/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:142:44
at internal/util.js:297:30
at new Promise (<anonymous>)
at internal/util.js:296:12
at Noble.startScanningAsync (/usr/lib/node_modules/homebridge-plugin-govee/node_modules/@abandonware/noble/lib/noble.js:142:99)
at Object.exports.startDiscovery (/usr/lib/node_modules/homebridge-plugin-govee/node_modules/govee-bt-client/dist/index.js:83:27)
at GoveeHomebridgePlatform.discoverDevices (/usr/lib/node_modules/homebridge-plugin-govee/src/platform.ts:78:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:3641) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:3641) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Initializing HAP-NodeJS v0.9.3...
[16/03/2021, 03:06:02] [Present] Launched child bridge with PID 3684
Then it just continues as normal from that point.
Plugin Config:
},
{
"name": "Govee",
"batteryThreshold": 25,
"debug": false,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
}
]
}
Screenshots:
n/a
Environment:
I tried the plugin with the Smart Thermo-Hygrometer Model H5174, and it works well. Homebridge on Raspberry Pi 4.
Homebridge v1.3.8 (HAP v0.9.7) (Homebridge 9601)
homebridge-config-ui-x v4.41.3
Node.js 14.18.2
NPM 6.14.15
Raspbian GNU/Linux Buster
Linux 5.10.63-v7l+ armv7l
Describe The Bug:
Using H5102 units, saw the same 100c temp.
Altering the code to use the same mechanism as the H5075 to detect temps below freezing works:
const decodeH5101Values = (streamUpdate) => {
// TODO would be great to find a way to validate
let encodedData = parseInt(streamUpdate.substring(8, 14), 16);
let tempIsNegative = false;
if (encodedData & 0x800000) {
tempIsNegative = true;
encodedData = encodedData ^ 0x800000;
}
const battery = parseInt(streamUpdate.substring(14, 16), 16);
let tempInC = encodedData / 10000;
if (tempIsNegative) {
tempInC = 0 - tempInC;
}
const tempInF = (tempInC * 9) / 5 + 32;
const humidity = (encodedData % 1000) / 10;
return {
battery,
humidity,
tempInC,
tempInF,
};
};
To Reproduce:
Add H5102 device and chill it below 0c/32F
Expected behavior:
Should see the lower temps and not 100c
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
{
"bridge": {
"name": "Homebridge C343",
"username": "XXXXXXXXX",
"port": 51184,
"pin": "XXX-XX-XXXX"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"name": "Govee",
"batteryThreshold": 25,
"debug": true,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin"
},
{
"platform": "WLED",
"name": "WLED",
"wleds": [
{
"name": "WLED-Stove",
"host": "10.20.10.131",
"effects": [
"Rainbow Runner",
"Circus",
"Lake",
"Sine"
],
"showEffectControl": true,
"log": true
}
]
}
]
}
Screenshots:
Environment:
Hi
I've got a H5075 which was working fine until the last update. Since then, only the temperature comes up as an accessory.
When I check the logs, I see this message:
Plugin Govee BridgeERROR[Plugin Govee Bridge C27E@GVH5075E37C@@Current Relative Humidity] characteristic was supplied illegal value: number 540 exceeded maximum of 100
Is there a way to solve this?
Please let me know if you need me to provide any information
Thanks!
Describe The Bug:
When the sensor of my H5075 goes below 32F (0C), the Home app displays the device's temperature as 212F. In the app "Controller for Homekit" the message traffic for the temperature is missing when the temperature is below freezing, although humidity messages still happen.
To Reproduce:
Put a H5075 sensor in the freezer, and watch the message traffic in Controller for Homekit, and in Home.app
Expected behavior:
The correct temperature is shown on the sensor display, so I would expect this to be shown in the apps and in the message traffic. I have verified using an Aqara Homekit-compatible temperature sensor that Homekit does support temperatures below freezing. My guess is that the plugin as-written uses a data type that doesn't support negative numbers, and that the native data computations are done in Celsius.
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
homebridge running on the official rasPi install, 1.1.17
Describe The Bug:
When using Govee, http shows the proces. Quite often as Top process.
I noticed, when I am running the Govee plug-in, that the temperature of the RaspiZero2 is about 6-8 degree Celsius higher then without the plug-in.
Maybe someone can have a look if polling is too often or maybe that the polling process it self consumes too much cpu-power? Looks like throttling the cpu down is not as effective when running the plug-in.
To Reproduce:
Activate plug-in for some time, look at the cpu temperature then disable it and look again at the cpu temperature
Expected behavior:
Would expect the plug-in to behave cpu friendly and m"bye let me configure now often to poll the devices.
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
I am wondering if it is possible to add similar BT-enabled Govee thermometer/hygrometers? The model I own is this one. Would love to hear your thoughts - thanks!
Is your feature request related to a problem? Please describe:
It does not appear that wifi hygrometers are supported. Is there any chance they can be added, suggestions for workarounds? or will this only be for bluetooth-only devices going forward? Thanks.
Working great for both Govee's! Unfortunately I am a stupid American who thinks in fahrenheit.
Describe Your Problem:
I added one device with no problem after adding a second device to the govee app it does not expose ...only the first one shows
Logs:
3/7/2021, 7:28:12 PM Loaded plugin 'homebridge-plugin-govee'
3/7/2021, 7:28:12 PM [3/7/2021, 8:28:12 PM] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
3/7/2021, 7:28:17 PM [GoveeHomebridgePlugin] Initializing GoveeHomebridgePlugin platform...
3/7/2021, 7:28:17 PM [GoveeHomebridgePlugin] Finished initializing platform: undefined
3/7/2021, 7:28:17 PM [GoveeHomebridgePlugin] Loading accessory from cache: GVH50755A3F
3/7/2021, 7:28:18 PM at Noble.scan (/home/hoobs/.hoobs/node_modules/@abandonware/noble/lib/noble.js:107:21)
3/7/2021, 7:28:18 PM at Noble.startScanning (/home/hoobs/.hoobs/node_modules/@abandonware/noble/lib/noble.js:136:10)
3/7/2021, 7:28:18 PM at /home/hoobs/.hoobs/node_modules/@abandonware/noble/lib/noble.js:142:44
3/7/2021, 7:28:18 PM at internal/util.js:297:30
3/7/2021, 7:28:18 PM at new Promise ()
3/7/2021, 7:28:18 PM at internal/util.js:296:12
3/7/2021, 7:28:18 PM at Noble.startScanningAsync (/home/hoobs/.hoobs/node_modules/@abandonware/noble/lib/noble.js:142:99)
3/7/2021, 7:28:18 PM at Object.exports.startDiscovery (/home/hoobs/.hoobs/node_modules/govee-bt-client/dist/index.js:83:27)
3/7/2021, 7:28:18 PM at GoveeHomebridgePlatform.discoverDevices (/home/hoobs/.hoobs/node_modules/homebridge-plugin-govee/src/platform.ts:66:5)
3/7/2021, 7:28:18 PM at HomebridgeAPI. (/home/hoobs/.hoobs/node_modules/homebridge-plugin-govee/src/platform.ts:36:12)
3/7/2021, 7:28:18 PM at HomebridgeAPI.emit (events.js:327:22)
3/7/2021, 7:28:18 PM at HomebridgeAPI.signalFinished (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/homebridge/src/api.ts:275:10)
3/7/2021, 7:28:18 PM at Server.start (/usr/local/lib/node_modules/@hoobs/hoobs/bridge/server.js:161:18)
3/7/2021, 7:28:18 PM at /usr/local/lib/node_modules/@hoobs/hoobs/bridge/cli.js:94:16
3/7/2021, 7:28:18 PM at processTicksAndRejections (internal/process/task_queues.js:93:5)
3/7/2021, 7:28:18 PM (Use node --trace-warnings ...
to show where the warning was created)
3/7/2021, 7:28:18 PM (node:4073) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
3/7/2021, 7:28:18 PM (node:4073) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Plugin Config:
{
"plugin_map": {
"plugin_name": "homebridge-plugin-govee"
},
"platform": "GoveeHomebridgePlugin"
}
Screenshots:
Environment:
HOOBS Version | 3.3.3
Node Version | 14.16.0
Plugin Version:
1.0.8
Operating System:
Raspian
Is your feature request related to a problem? Please describe:
Hello,
In 2022, Goveee Home iOS App version 4.8.0, Govee added VPD and Dew Point to all thermo-hygrometers (H5075 included). So in the iOS app, I can see two additional set of data for each H5075: VPD and Dew Point. However, these two new fields are not visible in HomeBridge Plugin yet.
Describe the solution you'd like:
Would you please expose VPD and Dew Point from H5075 to Homebidge Plugin?
Thanks....
Describe alternatives you've considered:
Additional context:
Describe Your Problem:
The plug-in was installed without any problems and the log on the plug-in and homebridge are enabled.
Waited more then 15m and no sensor was found
Logs:
[18/07/2021, 11:34:01] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[18/07/2021, 11:34:01] [HB Supervisor] Started Homebridge v1.3.4 with PID: 1971
Initializing HAP-NodeJS v0.9.4...
[18/07/2021, 11:34:16] Loaded config.json with 0 accessories and 2 platforms.
[18/07/2021, 11:34:17] Loaded 0 cached accessories from cachedAccessories.
[18/07/2021, 11:34:17] ---
[18/07/2021, 11:34:33] Loaded plugin: [email protected]
[18/07/2021, 11:34:33] Registering platform 'homebridge-config-ui-x.config'
[18/07/2021, 11:34:34] ---
[18/07/2021, 11:34:36] Loaded plugin: [email protected]
[18/07/2021, 11:34:36] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
[18/07/2021, 11:34:36] ---
[18/07/2021, 11:34:36] Loading 2 platforms...
[18/07/2021, 11:34:36] [Config] Initializing config platform...
[18/07/2021, 11:34:36] [Config] Running in Service Mode
[18/07/2021, 11:34:36] [Govee] Initializing GoveeHomebridgePlugin platform...
[18/07/2021, 11:34:36] [Govee] Initializing child bridge XX:XX:XX:XX:XX:XX
Preparing Advertiser for 'Homebridge 91CD 96F7' using bonjour-hap backend!
Setup Payload:
X-HM://0023UZ3SSG4VW
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ XXX-XX-XXX │
└────────────┘
Starting to advertise 'Homebridge 91CD 96F7' using bonjour-hap backend!
[18/07/2021, 11:34:37] Homebridge v1.3.4 (Homebridge 91CD) is running on port 51272.
Initializing HAP-NodeJS v0.9.4...
[18/07/2021, 11:35:01] [Govee] Launched child bridge with PID 1998
[18/07/2021, 11:35:04] Registering platform 'homebridge-plugin-govee.GoveeHomebridgePlugin'
[18/07/2021, 11:35:05] [Govee] Loaded homebridge-plugin-govee v1.1.2 child bridge successfully
[18/07/2021, 11:35:05] Loaded 0 cached accessories from cachedAccessories.0E44CC7E8483.
[18/07/2021, 11:35:05] [Govee] Finished initializing platform: Govee
Preparing Advertiser for 'Govee A4CF' using bonjour-hap backend!
[18/07/2021, 11:35:06] [Govee] Executed didFinishLaunching callback
[18/07/2021, 11:35:06] [Govee] Start discovery
Starting to advertise 'Govee A4CF' using bonjour-hap backend!
[18/07/2021, 11:35:06] Homebridge v1.3.4 (Govee) is running on port 37348.
Plugin Config:
{
"name": "Govee",
"batteryThreshold": 20,
"debug": true,
"humidityOffset": 0,
"platform": "GoveeHomebridgePlugin",
"_bridge": {
"username": "0E:44:CC:7E:84:83",
"port": 37348
}
}
Environment:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.