Currently I know of no other way. I wanted to add this parameters to the options flow, sadly my dev environment broke (probably broke earlier, i moved to a new machinge and re-created the containers) and I need to fix my dev container scripts first.
Thanks alot 
I love coffee.
Thatâs what we long fore - I could use some more, but i first walked the Hue path.
well, as just said, not (jet) implemented here.
Sounds good, cann you change it from the Home Assistant UI directly somehow?
I saw some strange things yesterday too, maybe API had a hickup.
Added to the list. Do you also get state from the API (the two buttons changing back to one)?
I take that as a yes.
1 Like
You might want to theck this release, which allows to change the Pull Interval in the options menu.
As an educated guess I would not allow to more than 10% of requests for state - we also do not need that much as the integration tries to guess the new state and show it in the meanwhile.
So e.g. for 12 devices, set it to 120 seconds, for 8 start playing around with 80 seconds.
If you do not like the two-button-style until the api-state arrives, you could disable that also:
And as always: if you enjoy what I do and can afford it:
Amazing update sir! Great inclusion. I appreciate the hard work!
1 Like
QQ - Can i use 2 integrations? 2 APIs? (2 kids accounts)
1 Like
Havenât tried that, but seems legit to me as long as the device names differ.
confirmed to work fine with two integrations with two APIs
** update - two APIs does not work. When I added 2nd the 1st became unavailable. If I reload 1st, 2nd is unavailable.
1 Like
Just a quick question. Iti s locally runing right? no cloud needed? I wanna cut this device from inzternet if I buy it as i avoid ALL cloud services 
1 Like
Ha, sure. The instance of the library is stored in
hass.data{'govee'}['hub'] = hub
So at least here we do not support two instances.
If you really need that feature please report an feature request on GitHub.
Hi, we had that information many times now, so I added this to the top of first post:
Currently there is no implementation (nor official way) to use them locally.
Thanks - I just combined them into one account and works great. If they kids mess with each otherâs LEDs I said theyâll all be gone
1 Like
Iâm not sure if you ever fixed the brightness issue, but to me, 0-100 only equals 0%-40% because 100 is 40% of 255. It seems like this value should just need to be changed to allow for 255, no? All of my other brightness are this wayâŚ
1 Like
Yes, I implemented a learning algorithm for it. Make sure you are on the latest version updated by HACS.
Maybe it gone wrong some time ago on your machine - could you delete the govee_learning.yaml in your config folder and restart? This should be rebuilt automatically. Then switch to full brightness, and it should learn the correct ranges.
If that doesnât work please activate debug logging (see first post), delete that file again, and file a bug at Github please.
1 Like
This is amazing! Thank you! Now I can finally get rid of Hoobs and go full homeassistant with working homekit!
1 Like