Do I need to disable the itegration then copy it over then reenable it?
or just copy over the existing
Getting some weirdness with the latest version, sometimes I can change brightness, sometimes I cant:
2020-09-21 20:48:27 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 101}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 102}
2020-09-21 20:48:47 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 254}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 255}
2020-09-21 20:48:52 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 254}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 255}
2020-09-21 20:48:59 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 254}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 255}
2020-09-21 20:49:14 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 239}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 240}
2020-09-21 20:49:27 WARNING (MainThread) [custom_components.govee.light] async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 254}: Unsupported Cmd Value for device GoveeDevice(device='0D:D7:A4:Cx:xx:F1:xx:xC', model='H6159', device_name='Bedroom LED', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 0D:D7:A4:Cx:xx:F1:xx:xC, kwargs: {'brightness': 255}
1 Like
It does turn on the H6104 and states it is on.
It also leaves it in the last mode, which is what I want.
It does turn it off and states it is off.
The brightness control takes a few minutes to adjust brightness (does not work everytime)
Color wheel works, it will put it in color mode when a color is selected; immediate every time.
Temperature control does not appear to have any change; there is no temperature control in the Govee Android app for H6104.
I might have to send you screenshots of the options I can see in the Govee Android app.
Automatons to turn on and off work as long as it is a 30 sec wait. It won’t work at 10 sec for some reason, I don’t think it would be polling too much. I am content with 30 sec. It did not try anything less than 30 other than 10 sec; I just initially tried 10 sec and even manually executing the automation would not work.
Thanks for your contribution.
Let me know what other testing you need from me; I am more than happy to help you, which in turn helps me.
I’ve got an information of devices which need different ranges for setting brightness. Please step back for a second, I think the model list was wrong. I wrote support about that.
Brightness mitht be the same issue, the 30 seconds thing is strange.
Could you provide the logs together with what you are doing at the time a log is written?
I reverted back to the previous version, that one seems to work perfectly, other than the “bounce” you described. I think something changed in the API call that the API is complaining about in that latest version.
1 Like
Logs don’t help much, this is all that is in the logs and this at the time I was attempting the automation.
Logger: custom_components.govee.light
Source: custom_components/govee/light.py:100
Integration: Govee LED strips ([documentation](https://www.home-assistant.io/integrations/govee))
First occurred: September 21, 2020, 5:57:38 PM (23 occurrences)
Last logged: September 21, 2020, 7:37:38 PM
* async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 126}: Unsupported Cmd Value for device GoveeDevice(device='99:F8:XX:XX:XX:XX:XX:XX', model='H6104', device_name='H6104_22DC', controllable=True, retrievable=False, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 99:F8:XX:XX:XX:XX:XX:XX, kwargs: {'brightness': 127}
* async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 235}: Unsupported Cmd Value for device GoveeDevice(device='99:F8:XX:XX:XX:XX:XX:XX', model='H6104', device_name='H6104_22DC', controllable=True, retrievable=False, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 99:F8:XX:XX:XX:XX:XX:XX, kwargs: {'brightness': 236}
* async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 253}: Unsupported Cmd Value for device GoveeDevice(device='99:F8:XX:XX:XX:XX:XX:XX', model='H6104', device_name='H6104_22DC', controllable=True, retrievable=False, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 99:F8:XX:XX:XX:XX:XX:XX, kwargs: {'brightness': 254}
* async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 245}: Unsupported Cmd Value for device GoveeDevice(device='99:F8:XX:XX:XX:XX:XX:XX', model='H6104', device_name='H6104_22DC', controllable=True, retrievable=False, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 99:F8:XX:XX:XX:XX:XX:XX, kwargs: {'brightness': 246}
* async_turn_on failed with 'API-Error 400 on command {'name': 'brightness', 'value': 152}: Unsupported Cmd Value for device GoveeDevice(device='99:F8:XX:XX:XX:XX:XX:XX', model='H6104', device_name='H6104_22DC', controllable=True, retrievable=False, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True)' for 99:F8:XX:XX:XX:XX:XX:XX, kwargs: {'brightness': 153}
2 Likes
Thank you for the logs, I think a information I got from api support was incorrect.
“H6089”,“H7022”,“H6086”,“H6135”,“H6137”,“H7005”,“H6002”,“H6003”
These devices should need a value of 0 to 100 when setting brightness, others should use 0 to 254.
We now know that my “H6163” and your “H6104” also need 0 to 100 as value. I’ll turn it around, it seems 0-100 is the default, and where we discover we will add a list of devices supporting 0 to 254. This way we will have some devices, when you set them to max brightness they will to around 40% light (but not failing) --> this would indicate us we have to include that specific model in that list.
Also I asked govee api support to check their list of devices for both variants.
You may test this zip with just the brightness fix.
Ah yes - about logging: if you have an issue you may choose to activate debug logging, just put this in your configuration.yaml:
logger:
default: warning
logs:
homeassistant.components.govee: debug
custom_components.govee: debug
govee_api_laggat: debug
Then on Settings - Logs click on “full logs” button.
1 Like
Ok, that makes sense. So, it probably was not the 10 seconds; it was that I was also trying different brightness values since that is required in the automation. Although, it never turned on when it was set to “0” (the default in HA automation). I have it set to 60% in my current automation and that works without error…
1 Like
Pull request for icon/logo is pending: https://github.com/home-assistant/brands/pull/1875
Next step: tests for ConfigFlow and Integration, and pull request to core.
All is working fine on my side, are there open issues?
Hello there,
I got this up and running for H6104. Can turn on/off and can change color and brightness.
My concern do you think you can add somehow to be able to control the MODE like in the grovee app
(Music,Video, Color, Scenes) my only goal here is to be able to set Full white (just color) on some node-red automations (this works already), and on some other automation make it change to VIDEO mode.
Thanks!
Hi, as it is not in the api i did question the api support team about that too. Here are the excerpt of my mail regarding this features:
- Feature Request: API limitations
The API is limited in some places - e.g. we cannot blink, or define different colors on different strip segments. Would be great to offer these features to implementations
the answer for now is:
- I’m sorry that our server could not support protocol for segmented control of lights.
… so using the official API we 're out of luck. Maybe in future someone may try to use the bluetooth api (which isn’t public, but parts of it are known), but that is currently out of scope for me.
OK I understand. But here is not to partially control the led strip. It’s just to select the right MODE that’s all.
There are different modes in the Govee app.
I know, as soon as it is in the API we can implement it. Feel free to contact them (mail address is in the mail you got the api key with), they answer within hours and are very friendly and helpful 
1 Like
@LaggAt I think I updated it correctly? Just replaced the files in the Govee folder? I got these errors on startup, but all seems to be working now:
2020-09-22 15:56:16 WARNING (MainThread) [custom_components.govee.light] cannot get state for 6D:4E:A4:C1:38:B5:27:34: API-Error 429: None
2020-09-22 15:57:16 WARNING (MainThread) [custom_components.govee.light] cannot get state for 6D:4E:A4:C1:38:B5:27:34: API-Error 429: None
2020-09-22 15:58:16 WARNING (MainThread) [custom_components.govee.light] cannot get state for 6D:4E:A4:C1:38:B5:27:34: API-Error 429: None
2020-09-22 15:59:20 WARNING (MainThread) [govee_api_laggat.govee_api_laggat] Rate limiting active, 1 of 100 remaining, sleeping for 2.5246808528900146s.
Also, you have a H6163? Does your color picker in the app reflect the actual color of the light? Mine does not - but it doesn’t work in the Govee app, either. I can pick the color, but when I close and come back, the picker is in the center of the screen (white).
Hm … 429 means you are over API limit and have to wait (what the library should do than, instead of trying 3 times …), could you restart with debugging and post a full log with all what is happening?
configuration.yaml part for debug log is here: Govee integration - #28 by LaggAt
Ah … and was there something else using the API? App or so?
Ah … and was there something else using the API? App or so?
Just the default Govee app on my iPhone.
Here is the full log. Let me know if you want me to clean it up to remove some of my other issues…
2020-09-22 16:07:56 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-22 16:07:56 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for emporia_vue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-22 16:07:56 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-22 16:08:01 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:03 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:03 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:04 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:04 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:04 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/__init__.py, line 61: result = vue.login(username=email, password=password)
2020-09-22 16:08:04 DEBUG (MainThread) [custom_components.govee.light] Setting up Govee lights
2020-09-22 16:08:04 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_devices
2020-09-22 16:08:05 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for govee_ble_hci which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-22 16:08:05 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2020-09-22 16:08:05 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/sensor.py, line 15: vue_devices = vue.get_devices()
2020-09-22 16:08:05 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/sensor.py, line 20: device = vue.populate_device_properties(device)
2020-09-22 16:08:06 WARNING (MainThread) [homeassistant.util.async_] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for emporia_vue doing I/O at custom_components/emporia_vue/sensor.py, line 20: device = vue.populate_device_properties(device)
2020-09-22 16:08:06 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:08:06 WARNING (MainThread) [homeassistant.config_entries] Config entry for glances not ready yet. Retrying in 5 seconds
2020-09-22 16:08:07 ERROR (MainThread) [homeassistant.components.sensor] The glances platform for the sensor integration does not support platform setup. Please remove it from your config.
2020-09-22 16:08:07 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Timeout occurred while connecting to device
2020-09-22 16:08:07 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 5 seconds
2020-09-22 16:08:08 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:08:16 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 10 seconds
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93eadbeef13
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.sensor] Platform glances does not generate unique IDs. ID localhost-Glances Package id 0 Temp already exists - ignoring sensor.glances_package_id_0_temp
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.sensor] Platform glances does not generate unique IDs. ID localhost-Glances Core 0 Temp already exists - ignoring sensor.glances_core_0_temp
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.sensor] Platform glances does not generate unique IDs. ID localhost-Glances Core 1 Temp already exists - ignoring sensor.glances_core_1_temp
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.sensor] Platform glances does not generate unique IDs. ID localhost-Glances Core 2 Temp already exists - ignoring sensor.glances_core_2_temp
2020-09-22 16:08:16 ERROR (MainThread) [homeassistant.components.sensor] Platform glances does not generate unique IDs. ID localhost-Glances Core 3 Temp already exists - ignoring sensor.glances_core_3_temp
2020-09-22 16:08:18 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:08:28 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:08:30 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:08:30 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 20 seconds
2020-09-22 16:08:38 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:08:42 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:08:42 ERROR (MainThread) [homeassistant.components.glances] Unable to fetch data from Glances
2020-09-22 16:08:49 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:08:53 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:08:53 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 40 seconds
2020-09-22 16:08:59 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:03 WARNING (MainThread) [homeassistant.components.automation.homekit_start] HomeKit Start: Already running
2020-09-22 16:09:09 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:19 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:29 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:36 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:09:36 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 80 seconds
2020-09-22 16:09:39 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:49 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:09:59 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:09 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:19 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:29 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:39 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:49 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:59 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:10:59 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:10:59 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 80 seconds
2020-09-22 16:11:04 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:11:04 ERROR (MainThread) [homeassistant.components.glances] Unable to fetch data from Glances
2020-09-22 16:11:09 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:11:19 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:11:29 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:11:41 ERROR (MainThread) [homeassistant.components.hue.sensor_base] Timeout fetching sensor data
2020-09-22 16:11:41 ERROR (MainThread) [homeassistant.components.hue.light] Timeout fetching light data
2020-09-22 16:11:42 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:11:42 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:11:42 ERROR (MainThread) [homeassistant.components.glances] Unable to fetch data from Glances
2020-09-22 16:11:51 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2020-09-22 16:11:52 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:11:52 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:11:52 ERROR (MainThread) [homeassistant.components.glances] Unable to fetch data from Glances
2020-09-22 16:12:03 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:12:12 ERROR (MainThread) [glances_api] Can not load data from Glances API
2020-09-22 16:12:12 ERROR (MainThread) [homeassistant.components.glances] Unable to fetch data from Glances
2020-09-22 16:12:14 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:12:23 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device
2020-09-22 16:12:23 WARNING (MainThread) [homeassistant.config_entries] Config entry for roku not ready yet. Retrying in 80 seconds
2020-09-22 16:12:25 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:12:35 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:12:45 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:12:55 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:13:05 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:13:05 WARNING (MainThread) [custom_components.govee.light] cannot get state for 6D:4E:A4:C1:38:B5:27:34: API-Error 429: None
2020-09-22 16:13:15 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:13:25 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:13:35 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
2020-09-22 16:13:45 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_state 6D:4E:A4:C1:38:B5:27:34
Yes and yes, I have this led strip and it reflects the correct color. I tried a bit around and it’s just jumping a bit on first reload.
I could explain it stays for two seconds, the api is giving an old color status immediatly after selecting, so the library is blocking updates for 2 seconds. After that the real status is queried.
What I can think of - do you have color temp centered? That would match color white.
Here are a couple screenshots of my Govee App and your (wonderful ) integration. I think it’s something wrong with Govee?
Govee App Showing a Pinkish Color
Govee App Showing Color Picker in the Center (White)
Light in HA Showing the Same, White Color in the Color Picker
Thanks. I’m wondering … all looks fine, getting state every 10 seconds. Allowed limit is 60/Minute per IP-Address requesting, so this isn’t too agressive.
Then we get this Error 429 which tells us we exceeded the API Limit. I just checked the logs, and I had this too. I’ll implement some more logging here in the dev enviroment to track it down.