Govee integration

phairplay · November 12, 2020, 9:41pm

Same here.
When the tv is on everything is good, google home govee app and HA

Gav_in · November 12, 2020, 9:43pm

Here’s the same log with the TV and Lights on…and API reporting Online as True

2020-11-12 21:40:10 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_states
2020-11-12 21:40:10 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] Rate limit total: 100, remaining: 98 in 40.21264290809631 seconds
2020-11-12 21:40:10 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] state returned from API: {'data': {'device': '`REDACTED', 'model': 'H6182', 'properties': [{'online': True}, {'powerState': 'on'}, {'brightness': 100}, {'color': {'r': 127, 'b': 255, 'g': 0}}]}, 'message': 'Success', 'code': 200}, resulting state object: GoveeDevice(device='REDACTED', model='H6182', device_name='Govee TV', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True, online=True, power_state=True, brightness=254, color=(127, 0, 255), timestamp=1605217210.413018, source='api', error=None, lock_set_until=0, lock_get_until=1605215588.553215, learned_set_brightness_max=None, learned_get_brightness_max=100, before_set_brightness_turn_on=False)
2020-11-12 21:40:10 DEBUG (MainThread) [custom_components.govee.light] Finished fetching govee data in 0.413 seconds
2020-11-12 21:40:22 DEBUG (MainThread) [custom_components.govee.light] async_turn_off for Govee light REDACTED
2020-11-12 21:40:22 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] control REDACTED: {'name': 'turn', 'value': 'off'}
2020-11-12 21:40:22 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] Rate limit total: 100, remaining: 97 in 28.105284929275513 seconds
2020-11-12 21:40:30 DEBUG (MainThread) [custom_components.govee.light] _async_update
2020-11-12 21:40:30 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] get_states
2020-11-12 21:40:30 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] Rate limit total: 100, remaining: 96 in 20.504639863967896 seconds
2020-11-12 21:40:30 DEBUG (MainThread) [govee_api_laggat.govee_api_laggat] state returned from API: {'data': {'device': 'REDACTED', 'model': 'H6182', 'properties': [{'online': True}, {'powerState': 'on'}, {'brightness': 100}, {'color': {'r': 127, 'b': 255, 'g': 0}}]}, 'message': 'Success', 'code': 200}, resulting state object: GoveeDevice(device='REDACTED', model='H6182', device_name='Govee TV', controllable=True, retrievable=True, support_cmds=['turn', 'brightness', 'color', 'colorTem'], support_turn=True, support_brightness=True, support_color=True, support_color_tem=True, online=True, power_state=True, brightness=254, color=(127, 0, 255), timestamp=1605217230.121256, source='api', error=None, lock_set_until=0, lock_get_until=1605217224.520494, learned_set_brightness_max=None, learned_get_brightness_max=100, before_set_brightness_turn_on=False)
2020-11-12 21:40:30 DEBUG (MainThread) [custom_components.govee.light] Finished fetching govee data in 0.121 seconds

LaggAt · November 12, 2020, 9:45pm

That must be the issue … the TV is turned off, unpowers the Govee and the state cannot be sent to the api server anymore as the device is down now. Great guys, we nailed it!

So, there should be an fairly easy solution. If we somehow could tell the library to consider an offline device as off, we are done. I do not want this as default, as an internet failure may trigger other automations, but for you two this would probably be perfect.

I added an feature request describing that idea in detail.

I think I’ll find some time on weekend to address this.
I will update the first post again, as the device is working as expected.

LaggAt · November 13, 2020, 8:53pm

Hi,

I found some time to turn some coffee into code.

This is new:

fixed before_set_brightness_turn_on, if you need it this works now. LaggAt/python-govee-api#72
the Warning unknown state property {‘colorTemInKelvin’: 2000} is gone. LaggAt/python-govee-api#71
Option to consider an offline device as “OFF”. LaggAt/python-govee-api#73
For Configuration see link.

Update is available via HACS.

GlennHA · November 14, 2020, 2:39am

There is a slight difference from before:
Using Dark Mode for Home Assistant the integration install box does not show “API:”. I knew what is supposed to go there, but for any others this may cause an issue.
govee

phairplay · November 14, 2020, 9:15am

Hi,
Where do you change it to false I can’t seem to find it in the files

I’m running home assistant OS and installed this via HACS

LaggAt · November 14, 2020, 3:05pm

In your config folder there should be a govee_learning.yaml - just next to your configuration.yaml.

the content of the file should already contain a block for each device.
You just need to add the config_offline_is_off line as shown below:

40:83:FF:FF:FF:FF:FF:FF:
  .....
  config_offline_is_off: true

we override that file when the integration learns something about your led strips, so it’s probably to edit the file when home assistannt is offline, or at least restart immediatly after edit.

For further informations also consult the docs:

github.com

LaggAt/hacs-govee/blob/master/README.md

# 'Govee' integration

The Govee integration allows you to control and monitor lights and switches using the Govee API.

## Installation

* The installation is done inside [HACS](https://hacs.xyz/) (Home Assistant Community Store). If you don't have HACS, you must install it before adding this integration. [Installation instructions here.](https://hacs.xyz/docs/setup/download)
* Once HACS is installed, navigate to the 'Integrations' tab in HACS and search for the 'Govee' integration there. Click "Download this repository in HACS". On the next screen, select "Download". Once fully downloaded, restart HomeAssistant.
* In the sidebar, click 'Configuration', then 'Devices & Services'. Click the + icon to add "Govee" to your Home Assistant installation. An API key
is required, you need to obtain it in the 'Govee Home' app on your mobile device. This can be done from the Account Page (Far right icon at the bottom) > Settings (top right icon) > About Us > Apply for API Key. The key will be sent to your account email.

## Sponsor

A lot of effort is going into that integration. So if you can afford it and want to support us:

<a href="https://www.buymeacoffee.com/LaggAt" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a>

Thank you!

## Is it stable?

This file has been truncated. show original

LaggAt · November 14, 2020, 3:44pm

Correct, thank you.
I was asked to remove the translations folder during review process, seems HACS needs them again. I re-add them.

LaggAt · November 15, 2020, 4:50pm

Hi, does color temperature work for you?
Just wondering if everyone here has this issue:

I could set color temperature once, where I land on the center of the color wheel selecting white with some low brightness. From that on nothing changes anymore, no matter which color temperature I select.

From library side anything looks fine, just mailed api support and want to know where it is working or not.

edit: Answer from Support:
We had fixed the issue you had, please try it again to check if you still have the issue.

I havn’t checked this as I am at work.

phairplay · November 16, 2020, 4:31pm

Hi
I’ve added the line to the yaml as adviced, yet it’s still reverting back to on even when I manually turn it off.

I tried a reload and its the same

MAC:
  set_brightness_max: 100
  get_brightness_max: 100
  before_set_brightness_turn_on: false
  config_offline_is_off: true

LaggAt · November 16, 2020, 6:35pm

uh, sorry for that, I probably overlooked something. I need to check that.

Well, maybe even I should reconsider mis-using the learning file for such things - i started an Options menu which will be much better suited for such configurations. Think I’ll put it in there.

I’ll come back to you when I have progress here.

LaggAt · November 16, 2020, 11:01pm

So finally, we have an options menu …

You may find the first option interresting - I know some of you don’t like that locally generated state with two buttons to turn on and off just after switching - you can turn this behavour off now if you like.

@phairplay your bug was a tricky one
When the device is online, we get a boolean true from API. In my tests I used this. Therefore I wrote tests which test against false as boolean. But the API returns ‘false’ --> to be exact the string ‘false’ which - in python - is true because it isn’t an empty string. Glad I found this in reasonable time
Nevertheless - it should work with both variants now - either in the learning config for each individual led, or (as global override) in this options menu.

Update is available in HACS searching ‘govee’ in integrations.

Good night

aamans · November 17, 2020, 7:55pm

Is there a way to set scene/effect from the app? e…g mode: scene, effect: Universe ?

LaggAt · November 17, 2020, 10:22pm

Sadly no, the public API doesn’t support it. You may always mail the API support and request it, maybe it helps if more users are requesting features.

I myself asked for a blink command, I got a no some weeks ago, yesterday they wrote they’ll look into it.

Ransonneil · November 21, 2020, 5:10pm

Hoping someone can help

Govee H6182_EF38 not working

I’ve set it up and HA has picked up the entity.

When I turn it on/off change colour nothing actually happens with the LED strip

Not sure if this is the log needed…

Logger: govee_api_laggat.govee_api_laggat
Source: /usr/local/lib/python3.8/site-packages/govee_api_laggat/govee_api_laggat.py:678 
First occurred: 17:04:02 (29 occurrences) 
Last logged: 17:08:42
error getting state for device 34:D6:A4:C1:38:00:EF:38: API-Error 400: Can not found device state in database
Logger: custom_components.govee.light
Source: custom_components/govee/light.py:105 
Integration: Govee LED strips ([documentation](https://github.com/LaggAt/hacs-govee/blob/2f23b2d7a55a0d044e28487f56c320f6d4113745/README.md), [issues](https://github.com/LaggAt/hacs-govee/issues)) 
First occurred: 17:04:02 (21 occurrences) 
Last logged: 17:07:22
update failed for 34:D6:A4:C1:38:00:EF:38: API-Error 400: Can not found device state in database

LaggAt · November 21, 2020, 10:12pm

Hm, that log looks strange …
could you enable debug logging (see first post for instructions) and log startup, a status request and maybe one control action as turning on?

I wonder why you get the device in the first place, but having issues coltrolling and getting state from it later. The debug logs willl give some hints here.

Thanks.

Ransonneil · November 22, 2020, 9:32am

Think I’ve figured it out

I’m an idiot

It’s picking it up

But on the govee app it hadn’t connected to wifi

And I can’t connect it to wifi on the govee app

Just not working

This must be the issue

Scope666 · November 22, 2020, 2:41pm

I had this problem on one of my strips, this was the solution from Govee Support. (1. worked for me)

Please don’t worry, we are always here to help you.

•1. De-lete the strip light from Govee app first and then reset the strip light (Reset: Turning on the strip
light, press the middle button on control box for four times while holding the power button.) After
resetting the device, add it again on Govee App.

Unplug the strip light for 20 mins and then replug it.

LaggAt · November 22, 2020, 5:00pm

Could you provide the logs anyway? It would be nice if we could give prettier error messages to people with the same issue, for that I need to know how to interpret the api answers in this case.

phairplay · November 25, 2020, 7:19pm

Hey are any of you guys having issues controlling the lights?

Using the app it only shows a Bluetooth connection yet my router does show them connected to the network

Edit looks like an issue with AWS

To our valuable Govee users,

Some of you may find you are not able to use our app properly. Amazon Web Services as a whole are operating abnormally today, which then also affects how Govee Home App works. You may not control your devices via Alexa currently. We need to wait Amazon Web Services getting back to normal. Our technical team are working on this issue right now and we’re hoping to have this issue solved ASAP. We are sincerely sorry for any inconvenience this may cause to you.