See if it reports it’s existence in the api, it is not documented as supported. But so we’re the Fan types.
Use postman to get your device list and send me the response.
For info for the rest, the api response did not include the kettle. So we have to wait for support.
Is there a way to find out whether a lamp supports the local/LAN API, before buying and connecting the actual device?
Not really I think, sometimes it’s cryptic listed but mostly it is not. Maybe someone else can give us tips
1 Like
I purchased outdoor clear bulb string lights (H7025), connected via Matter to Homey Pro, but it keeps losing the connection. I have requested the API, and now it seems to be working, but I can’t figure out how to start scenes from Homey. I can only turn it on/off, adjust brightness, and change the color, but not the color sequences, etc. To do that, I have to use the Govee app. Can anyone tell me if there’s a way to do it directly from Homey
Using flows you can interact with scenes and other additions.
I have no control on the matter quality, I have the same issue with matter and Homey and govee
Hi everyone,
Since yesterday I’ve gotten an “Discovering the device…” error on 3 out of my 5 Govee lights in Homey
Anyone else? I’ve tried to restart my network/app/Homey to no avail.
Please try power cycling your lights, I had a similar thing that caused the local api on the device to be unavailable
First off great work and love this app. I have 3 devices I am trying to understand how to get working in flows. Curtain Lights 2 (H70B3), Curtain Lights 2 (H70B5), and permanent outdoor lights 2 (H705F). I have been able to successfully add them and have Govee API setup, but what I can not figure out is why only some of my DIY Scenes show up in flows. I have more DIY scenes than are showing up in options. Any help of ideas?
Some more advanced scene features make them unsupported by the api, I don’t know why govee does this. Could be your case. Also I dint update the list always, so restart the app if those are new to see if they show up.
Interesting. One of the DIY scenes that did show up is a combo layer with animation and the ones that didn’t show up are basic single layer canvas finger scratch.
Frustrating. I did try the reboot of the app and no luck.
I appreciate response. Is there any features that you are aware of that cause this within diy api ? Like GIFs or animations or multi layer canvas etc?
I only noticed it once with the advanced mode or something, and I reverted back in my own design. Left it at that and never did new designs anymore. So I never went through them to figure it out.
hi all,
are there any problems known with the Govee Api access. i can see my thermometers locally in the app (Bluetooth), but homey is not updating the temperature and shows -17.8°
I have same myself, so I guess it’s an Api issue…
1 Like
None of my Govee devices are working currently.
works again for my thermometers…
There are platforms having issues, seems to be AWS related so might be that govee users them also and these issues are related.
Timelines match with other apps and platforms on AWS having outages and disruptions
Something weird is going on with my Govee lights since yesterday night. They showing in Homey normally but sometimes they are on but after some time they are off, on again etc. On official app everything seems to be ok. I can steer them but when I turn it on after some time Homey shows that they are off. I didn’t do anything since yesterday. When I change state on officiall app…Homey does’t recognize anything 
I have a lot of them
Your the second reporting this, I would say AWS outage related but that’s resolved now. Restarted the app in Homey?
Local api devices or cloud api?
Restarted couple of times. Cloud api devices.
Homey doesn’t read actual state of devices. It can steer them.
I tested it and Local devices are working ok.
I changed almost everything to Local API but I have 3 bulbs that doesn’t have this function
I have hope that Govee and Home are going to repair this issue.
I reported this issue to Govee.
Edit: I receive info from Govee that this situation is related to AWS problems but it should works now.
