search

bwp91 / homebridge-govee

Homebridge plugin to integrate Govee devices into HomeKit.
MIT License
435 stars 49 forks source link

devices not responding #778

Open jhayarr1562 opened 2 months ago

jhayarr1562 commented 2 months ago

I installed the plugin and it isn't responding to me on homekit. I checked the logs and it tells me that it can not connect via HTTP, BLE , and AWS. I tried to troubleshoot, due to the openssl error. Now, I get "invalid code error 1".

I'm using Homebridge v1.8.1 UI : v4.56.2 Platform: Windows 10 Node: 20.11.1

govee plugin version 10.6.0 Screenshot (4)

usenameea commented 3 weeks ago

I have the same issue support help

[6/13/2024, 1:02:02 AM] [Govee] [HTTP] disabling client as Invalid openssl exit code: 1 % openssl pkcs12 -in C:\Windows\TEMP\6046777a86c28829d3909fc4399531cdcd58bf73 -passin file:C:\Windows\TEMP\7fdf7952581a1e9b663e88218547ceb019d8f063 -legacy -traditional -nodes pkcs12: unable to load provider legacy Hint: use -provider-path option or OPENSSL_MODULES environment variable. 44570000:error:12800067:DSO support routines:win32_load:could not load the shared library:crypto\dso\dso_win32.c:108:filename(C:\Program Files\OpenSSL-Win64\bin\openssl.cfg\legacy.dll) 44570000:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto\dso\dso_lib.c:152: 44570000:error:07880025:common libcrypto routines:provider_init:reason(524325):crypto\provider_core.c:911:name=legacy % openssl pkcs12 -in C:\Windows\TEMP\6046777a86c28829d3909fc4399531cdcd58bf73 -passin file:C:\Windows\TEMP\7fdf7952581a1e9b663e88218547ceb019d8f063 -legacy -traditional -nodes. [6/13/2024, 1:02:02 AM] [Govee] [AWS] disabling client as requires HTTP client. [6/13/2024, 1:02:02 AM] [Govee] [BLE] disabling client as required hardware/packages not available.