It is wifi enabled and added to your govee account? Does it have local api support, and did you try that option?
Else restart the govee app on homey try to add it as a light again and send me a diagnostic report
Would it be possible to add âDurationâ to the âDim Toâ function?
Use Case:
Slowly dim the lights down when watching a movie (or a romantic evening;)
Start at current setting and use function âDim To-â to dim to eg 0% slowly over a duration of 10 seconds.
Request: Add duration setting to ui and manage time based timming loop.
Additional notes:
Shelly has this but does not really work. Changed to Govee but does not seem to be available there.
The Transition plug-in helps and is cool but to choppy with the 1 second interval.
Would be awesome to have 
Yes, Wi-Fi is on, and I can see that on the icon in the Govee app. Both Bluetooth and Wi-Fi are enabled. I also enabled the LAN Control option as a test. I suspect that the Govee LED bulb 7037 might not be supported, as I donât see it listed in the following guide: https://app-h5.govee.com/user-manual/wlan-guide.
I do have two outdoor decks from Govee that are recognized every time I search for new devices, so I know the app works with other Govee products. The 7037 bulb is listed in the supported devices in the Govee app, but it still doesnât seem to work.
Is there anything else I can try to get it working? I have already searched for both âlight bulbâ and âlocal API devicesâ in the app.
Not for cloud devices, they donât have such a feature on the api, and doing it from code would overload the api limits
For local devices it would be possible, ill give it a go for the new version (waiting for homey os 2.2 with to support of the new capabilities)
1 Like
Please restart the homey govee app and try to add it using the light device wait for it to not lost the lights and send me a diagnostic report please, ill check if it shows up in your api response. Right now the api seems to support all wifi lights when though the list is shorter. So it surprises me.
Then do the same (donât restart the app) with the local api device, and send another report.
It suddenly appeared on the local API devices after restart 
1 Like
I would still like to investigate the cloud version if you would be so kind to send te report for that part, then i can see why itâs not showing up.
I just published a new version (see test channel) with support for new capabilities in Homey 2.2, this includes upgrades to the oscillating control for Heaters and for the humidifier mist level control.
I also enhanced the settings page to show the device capabilities from the apiâs so you can share it more easy with me.
Hi all,
I installed the Grovee app (2.11.8) today and it crashed after installation without the possibility to manage everything.
What can I do?
Thanks!
As emailed several times: Itâs always caused by a conflicting app like the Yamaha app. Disable all other apps to identify the one that conflicts. The local discovery needs a fixed port and if it is in use it crashes (need to handle it better)
Iâm having trouble setting the âcloud api enhance this local deviceâ option. it then gives the following error message âcannot set settings while this .onSettings is still pendingâ can you help me solve this problem so that I can also start scenes via homey pro. thank you in advance.
Rapport code:
098e9758-fe3a-4cfb-9d4e-4f5f3d8ded36
Did you set the api key in the app settings before you tried to enable this feature?
not the first time, I entered the email address as API. then I entered the correct API key and tried again. When this did not work, I deleted the app and tried it by first entering the correct API key and then checking the option while connecting the LED strip. The same message is returned in all ways.
Hmm, can you try if adding the device through the cloud works? If it does try the local way again, if it still works you can remove the cloud variant. Maybe the app settings part just doesnât work well since i added the api key as part of the new cloud device wizard
I connected the LED strip via local API devices and via Matters, both work. Is it true that you can set more scenes with that option that doesnât work for me?
Correct but the device must indeed support the cloud api, if it doesnât this might explain the issue. Thatâs why for the test it is useful.
The cloud hybrid scenarios supports potentially scenes, diy scenes and snapshots.
So more ways to go with the fancy setups but without the dependency on cloud for all primary operations, they remain fully local
it is the govee h61c3 neon led strip. All the things you mention work on the Govee app itself.
That is not relevant, since it has other means to work with the light (like Bluetooth and bt codes over lan that are not documented). So please just check, i donât get why you donât preform the test i asked you to perform? If you want that feature it will use that line of communication anyway.
It is Govee that has the local api limited in capabilities, at least the documentation is.
I would like to do this but I donât really understand how. I thought I had already done this correctly by using the local api and matters option.
ok, when you add a device you have three light types, the ânormalâ Light, the local Light and the Matter light. So use the normal light instead.
By using the normal light device you are passed through the set key wizard etc before it lists all lights you have that are cloud supported. If it is not listed, it might not (yet) be supported by Govee, if it is listed it is supported, you can then abort the process.
Might works best from a clean install of the app though.
