Thanks for the detailed report. The H7107 is correctly recognised as a fan and the on/off command goes through the documented Govee /device/control endpoint with the right payload — that code path hasn’t changed since fan support was added. So whatever changed between last summer and now isn’t on the Homey app side.
To diagnose, can you share a Homey log from the moment you press the on/off toggle in the Homey app
Ooops! My mistake - it is working properly! I think I was confused by Homey not tracking the on / off state well when the fan is control by hand or by the Govee App. That and some rather pointless “if on” or “if off” clauses in my flows. Sorry for the noise! 
Hi @Mark_Sands ,
I have now the same since a week or so. Did debugging with multiple scripts but Homey writes the commands locally just fine, but the Fan isn’t working at all. Even deleting and adding again does nothing. Via de iPhone Govee app it works fine. Is the fan still working on your end?
Assumption is that something has changed in the API. Is this something the main developer @Kaoh of the app can investigate? If necessary I can share diagnostic reports.
EDIT: nevermind, i finally tried power off with the plug out of the socket. Waited 30sec and now it works again.
Yeah that is something I needed to do twice in a year or less for some devices.
Today I do install 2 pcs H7076
Connected to the Govee APP on Andriod phone and everything is working fine
Then added into Homey with the Govee app and set LAN, and all to local, so I have all posibilities
I like to switch the side lights of within the Homey Advanced flow, but whatever I try, there change noting. Turning on and off, dimming and change to a color or color temperature is no problem at all.
Can somebody clarify how I could fix this?
Thanks in advance and greeting Steven
edit
with the card set … or segments … to color is working
and to brightness is not working
Some govee devices respond weird sets. Please use the test page to list and poll devices data and send me the reasons json. Also do this for the local api test page, and send me a diagnostic report. Maybe that device is off
I checked your log and device response. Based on what it tells me to do, thats how I send commands to the segments. So if it then ignores the commands… then its a Govee problem I believe. You can try to capture your commands in a new diag report, have the app running for a while, send the commands you wanted to send, create a diag report within a couple of minutes of those actions and send it over, also tell me what commands you gave, than Ill see if the API is giving a response telling me something usefull or not.
I tried this 2 cards, of course not the same time.
What I can see. The H7076 is turning on, when it is of, but there is no change in the brightness.
When I use this card for … to color, it is correctly changing the color. I do not do this, so this is not in the diag report included for now.
Diagnostic report : 2adf6498-85ee-4441-86c7-7199457ddd69
I really hope you are able to solve and fix. If you need more date, information or assistance from me, please tell me.
Greetings,
Steven
Govee’s cloud API accepts the call without error. The H7076 firmware simply does not honour the brightness value, it flips the device on as a side effect but leaves brightness where it was.
Why the Govee App can do it and we can’t:
The Govee App uses BLE (Bluetooth) directly, or tunnels BLE-style commands over WiFi through non-public channels. Those commands are not part of the public API that Govee offers third-party integrators. Homey apps cannot use them because they simply don’t exist in Govee’s public documentation.
Interestingly, the segmentedBrightness capability IS advertised by Govee in the device’s capability list, which is misleading, it suggests it should work and it does for other devices. But the actual firmware/backend combo doesn’t process it for H7076 via the public path. segmentedColorRgb on the SAME device does work, same code path in our app, only the API instance name differs, so we can rule out an issue on our end.
So unfortunatly we have to wait for the people that maintain the cloud api to fix this issue.
Thanks for your reply and information!
Highly appriciated.
Could we bring it to the right people???
Do you think BTW, that the same reason for this that a DIY or Screenshot do not work as well, from Homey.
I have no contact points, so I have no idea if you have them 
But I wouldnt hold my breath, the progress on the cloud api is slow and there are many devices that lack a method or dont behave exactly as the cloud api suggests, I rarely see them fixed.
probably, they have cloud api support diy’s and non supported diy’s now, and some devices did not implement them at all and some ignore them. It works for 80% of their devices very well, but they make so many devices they clearly have a testing issue to make sure all of them have firmware that understand the cloud api the same.
Send an email to support.
We will see!
But this is an official app? Those are always created in collaboration with the brand, so maybe @Doekse has contacts at Govee
Hi,
Not sure if to ask here but here i go.
Anyone have the Tree Floor Lamp H60B2 or 52’’ Smart Ceiling Fan H1310 working?
If yes.
Can you select each one of the 3 lights individually for the Tree floor lamp?
And also can you select the upper and lower light separately for the Ceiling fan?
Thanks!
It’s supported by Athom in approval of Govee arranged by Doekse, but I don’t have direct links or connections with Govee. So I still do this using public info in my spare time. And Athom supports me as much as they can.
If you need anything you know where to find me! There’s a constant revolving door of contacts at Govee but usually it ends up in the right place.
Well, Govee need to fix some API’s for proper working of their products on Homey!
