Govee LED Strip H6125 not responding

[dzmertt]

What issue do you have? Please be as thorough and explicit as possible.

Govee RGBIC Led Strip not responding 5min after homebridge restart. This issue is only on my bluetooth strips. Wifi Strips works fine.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS? Homebridge UI-X

• Which version of Homebridge/HOOBS do you have? homebridge-config-ui-x v4.48.1

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known. Raspberry Pi Zero 2 W Node v16.15.1

• Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version? homebridge-govee v5.2.0

• Which Govee devices do you have that are causing issues? Please include product models if applicable. H6125

Please paste any relevant logs below.

[03/07/2022, 20:05:32] [Govee] [Schrank] starting update with params [{"cmd":1,"data":0}]. [03/07/2022, 20:05:32] [Govee] [Schrank] starting timer. [03/07/2022, 20:05:32] [Govee] [Schrank] starting scan. [03/07/2022, 20:05:32] [Govee] [Schrank] scanning started. [03/07/2022, 20:05:32] [Govee] [Schrank] starting loop. [03/07/2022, 20:05:32] [Govee] [Schrank] found correct characteristic so breaking loop. [03/07/2022, 20:05:32] [Govee] [Schrank] [BLE] sending update {1: 0}. [03/07/2022, 20:05:32] [Govee] [Schrank] current state [off]. [03/07/2022, 20:05:32] [Govee] [noble] found device [ef:3f:fe:cb:f3:6e] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [4d:ef:e1:0a:1c:62] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [d0:bf:91:22:25:2e] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [64:08:5b:a3:d3:01] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [7f:eb:01:91:1e:5a] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [29:f9:55:6e:09:b2] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [38:65:5d:52:7b:80] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [18:82:5f:f5:81:a0] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [90:dd:5d:d1:f6:30] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [65:95:e3:37:4d:3b] [undefined]. [03/07/2022, 20:05:32] [Govee] [noble] found device [a4:c1:38:65:e5:98] [ihoment_H6125_E598]. [03/07/2022, 20:05:32] [Govee] [Schrank] has been reported [discoverable] via BLE. [03/07/2022, 20:05:32] [Govee] [Schrank] attempting to connect. processLeAdvertisingReport: Caught illegal packet (buffer overflow): Error: Peripheral already connected

[DuckMasterAl]

Also occurs with H6138

[romainhe]

Same with H6125 and H6126... Any idea to fix ?

[romainhe]

maybe that can help

[stale[bot]]

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[FelixG28]

Same Issue Here with H6102 Strip

[Govee] [Felge] attempting to connect. processLeAdvertisingReport: Caught illegal packet (buffer overflow): Error: Peripheral already connected

[stale[bot]]

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[byteduck]

Also having this issue with H617C.

[bwp91]

Closing this as a bit overwhelmed with issues. Please update to the beta version of the plugin, and if you are still having issues, do reopen this ticket! Thanks and apologies if closing prematurely.