Govee Smart Home Integration

Ok, I try it again with another browser (first one was Chrome than Safari).
Get the same failure. I rebooted the Remote 3.

I get this log. Seems a SSL Certificate Issue but I am not sure.

2025-10-28 18:14:14.648095 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,647 | INFO | main | Closing event loop…
2025-10-28 18:14:14.646887 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,646 | INFO | main | Stopping event loop…
2025-10-28 18:14:14.645068 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,644 | INFO | websockets.server | server closed
2025-10-28 18:14:14.643120 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,642 | INFO | websockets.server | server closing
2025-10-28 18:14:14.640719 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,639 | INFO | main | Cancelling remaining tasks…
2025-10-28 18:14:14.636598 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:14,635 | INFO | main | Closing Govee client…
2025-10-28 18:14:04.145280 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:04,144 | WARNING | main | Received signal 15. Shutting down…
2025-10-28 18:14:04.013374 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:04,011 | INFO | main | Remote disconnected.
2025-10-28 18:14:04.007591 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:14:04,006 | INFO | ucapi.api | WS: Client removed
2025-10-28 18:13:59.132321 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,131 | INFO | uc_intg_govee.setup | Setup aborted: IntegrationSetupError.CONNECTION_REFUSED
2025-10-28 18:13:59.132321 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,130 | INFO | uc_intg_govee.setup | Setup handler called with: AbortDriverSetup
2025-10-28 18:13:59.130433 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,128 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] <-: {“kind”:“event”,“msg”:“abort_driver_setup”,“cat”:“DEVICE”,“ts”:“2025-10-28T18:13:59.125764662Z”,“msg_data”:{“error”:“CONNECTION_REFUSED”}}
2025-10-28 18:13:59.123310 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,122 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.CONNECTION_REFUSED: ‘CONNECTION_REFUSED’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-10-28 18:13:59.122457 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,118 | ERROR | uc_intg_govee.setup | Govee API error during setup: Failed to get devices: ‘GoveeDevice’ object has no attribute ‘supports_color’
2025-10-28 18:13:59.118448 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:59,117 | ERROR | uc_intg_govee.client | Unexpected error getting devices: ‘GoveeDevice’ object has no attribute ‘supports_color’
2025-10-28 18:13:58.744317 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:58,743 | INFO | uc_intg_govee.client | Fetching devices from Govee API
2025-10-28 18:13:58.743282 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:58,742 | INFO | uc_intg_govee.setup | Discovering user’s Govee devices…
2025-10-28 18:13:58.097310 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:58,096 | WARNING | uc_intg_govee.client | Using fallback SSL settings due to certificate verification issues
2025-10-28 18:13:58.092882 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:58,091 | ERROR | uc_intg_govee.client | SSL Error connecting to Govee API: Cannot connect to host openapi.api.govee.com:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1016)’)]
2025-10-28 18:13:51.630781 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:51,630 | INFO | uc_intg_govee.setup | Testing connection to Govee API
2025-10-28 18:13:51.630781 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:51,628 | INFO | uc_intg_govee.setup | API key provided, testing connection…
2025-10-28 18:13:51.628544 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:51,627 | INFO | uc_intg_govee.setup | Setup handler called with: DriverSetupRequest
2025-10-28 18:13:51.627674 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:51,624 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] ->: {‘kind’: ‘resp’, ‘req_id’: 2, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-10-28 18:13:51.623653 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:51,622 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] <-: {“kind”:“req”,“id”:2,“msg”:“setup_driver”,“msg_data”:{“reconfigure”:false,“setup_data”:{“api_key”:“1xxx-xxx-xxx-xxx-xxx”}}}
2025-10-28 18:13:28.901342 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,899 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] ->: {‘kind’: ‘resp’, ‘req_id’: 1, ‘code’: 200, ‘msg’: <WsMsgEvents.DRIVER_VERSION: ‘driver_version’>, ‘msg_data’: {‘name’: ‘Govee Smart Home Devices’, ‘version’: {‘api’: ‘0.21.0’, ‘driver’: ‘0.2.0’}}}
2025-10-28 18:13:28.898343 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,896 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] <-: {“id”:1,“kind”:“req”,“msg”:“get_driver_version”}
2025-10-28 18:13:28.893358 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,891 | DEBUG | ucapi.api | [(‘127.0.0.1’, 60908)] ->: {‘kind’: ‘resp’, ‘req_id’: 0, ‘code’: 200, ‘msg’: <WsMessages.AUTHENTICATION: ‘authentication’>, ‘msg_data’: {}}
2025-10-28 18:13:28.890658 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,888 | INFO | ucapi.api | WS: Client added: (‘127.0.0.1’, 60908)
2025-10-28 18:13:28.887264 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,886 | INFO | websockets.server | connection open
2025-10-28 18:13:28.773637 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,771 | INFO | websockets.server | server listening on 127.0.0.1:9002
2025-10-28 18:13:28.766279 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,765 | INFO | main | Integration is running. Press Ctrl+C to stop.
2025-10-28 18:13:28.764592 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,763 | WARNING | main | Integration is not configured. Waiting for setup…
2025-10-28 18:13:28.763310 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,762 | INFO | main | Integration API initialized successfully
2025-10-28 18:13:28.761424 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,760 | INFO | ucapi.api | Driver is up: uc-intg-govee, version: 0.2.0, api: 0.3.2, listening on: 127.0.0.1:9002
2025-10-28 18:13:28.756516 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,755 | INFO | main | Using config file: /etc/custom-intg/uc-intg-govee/config.json
2025-10-28 18:13:28.755678 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,753 | INFO | main | Using driver.json from: /app/driver.json
2025-10-28 18:13:28.752377 +00:00 custom-intg-uc-intg-govee INFO 2025-10-28 19:13:28,751 | INFO | main | Starting Govee Integration Driver

i agree, this is an interesting issue. we can see the setup continue as expected so the tar.gz is good but you are getting bad certificate back from Govee server during setup and bein refused to establish the connection… is the remote behind a vlan or some network constraints?

No, it’s not in a separate VLAN or something. I will try it in a few days, hopefully I am lucky.
It would be so great If I can use this wonderfull integration.
I will check my network settings, safety first.

of course :slight_smile: i use it, unable to replicate and so i am very curious… since this integration is cloud based, maybe a good test would be to hot spot your phone, setup the integration just to see if it pass full auth and then go back on your network? just thinking creatively.

New version up, try to address issue unable to configure for those with lights

Awesome! It works!

I set up the integration without any issues — it worked perfectly on the first try. I’ll run some tests over the weekend.

Thank you man!!!:+1:

Awesome, glad to hear it solved the issue. thanks.

Great I can switch my LEDs on in my theater room.

Is it possible to use scenes?

I added “tap to run” scenes for my leds.
In Alexa I can use it with out problems so I hoped to use them also in the integration.

it is definitely possible, but i have never done so and dont have a light to test with, i have seen this definitely supported so i will need to research/learn and build without testing. else i decide to buy a light so i can test locally during dev…. if there is an integration where scene is supported, send it so i can see how they did it.

1 Like

Great, if you need a tester let me know! :slight_smile:

Hi,

sorry, maybe a stupid question, but i did not get an API Key from Govee. Maybe there is an other way to get it?

Many thanks + BR

Peter

There isnt any other way, you submit the request and wait until the email come in.

OK, thanks. Request was submitted several times, but never got an answer…

  • Check Spam/Junk Folder:

    The API key is sent via email, so ensure it has not been filtered into your spam or junk folder.

  • Verify Application Process:

    • Open the Govee Home App.

    • Navigate to your “Profile” (bottom right icon).

    • Tap the “Settings” gear icon (top right).

    • Select “Apply for API Key.”

    • Fill out the required information accurately and clearly state your reason for needing the API key.

    • Agree to the Govee Developer API Terms of Service.

    • Submit the application.

  • Allow Processing Time:

    API key approval is not instantaneous and may take some time. Govee reviews applications, and approval is at their discretion.

  • Reapply if Necessary:

    If a significant amount of time has passed and you still haven’t received the key, and it’s not in your spam folder, you may consider reapplying, ensuring all information is correct and the reason for application is clear.

  • Contact Govee Support:

    If you have followed the steps and are still unable to obtain your API key, reach out to Govee customer support for assistance. Provide them with details of your application and any relevant information.

Many thanks @M.a.S.e . I proceeded exactly as you described. Only the last point i did not try so far. Will contact support.

sound good, good luck.

Original answer from Govee contact support:

„Dear Customer,
Thank you for reaching out to Govee Support.
I apologize for the inconvenience. At this time, we are unable to provide an API key for home integrations. Your understanding is greatly appreciated.
Feel free to let me know if you need further assistance!
Kind regards,
Chris
Govee Support Team“

So, i have to give up. But i am sure it is an amazing integration @M.a.S.e

oh wow. i wonder why…..

Everything’s going great! I do have one question though. How can I update my version 027 to 033 or the new 034 without having to reinstall everything? Thank you very much for your answer.

Hey, to do that you have the option of using the docker image and install WATCHTOWER to automatically update your docker container each time there is a new version. Also, to update if its uploaded via tar.gz , you can just delete the integration twice from web configurator and uplaod the new version tar.gz , if you have it in an activity, you will not lose anything, it will all come back as soon as you comlete re setup.