Discussions

Ask a Question

Response Header missing Rate Limit

After initiating a request (like retrieving a device list), I noticed the absence of rate limit keys and values in my response header. This was observed in both Postman and Java HttpURLConnection tests. The response header values are in the screenshot below. ![Postman Test](<>)

API Device State for Humidifier does not return Humdity State

I've noticed that the API for getting the device state for a H7142 Humidifier returns a blank value for the humidity level. Below is the returned response from <https://openapi.api.govee.com/router/api/v1/device/state> { "requestId": "b6bd865c-404f-444c-9246-f6becb0c31c6", "msg": "success", "code": 200, "payload": { "sku": "H7142", "device": "MACID", "capabilities": [ { "type": "devices.capabilities.online", "instance": "online", "state": { "value": true } }, { "type": "devices.capabilities.on_off", "instance": "powerSwitch", "state": { "value": 1 } }, { "type": "devices.capabilities.work_mode", "instance": "workMode", "state": { "value": { "workMode": 3, "modeValue": 1 } } }, { "type": "devices.capabilities.range", "instance": "humidity", "state": { "value": "" } } ] } } I assume this is suppose to either return the current set value of humidity or the humidity of the given room. Yes? David

How does this all work?

Hello, I have been researching how to trigger off scenes and snapshots for my live stream and I think I'm in the right area. I noticed that there's a lot of code snippets that we can copy but where do we paste these lines so we can make use of this? Any information would be extremely helpful. Thanks, \-CS

LAN Control for H601B / H6010 and integration with Home Assistant / WLED

Are there any plans to add LAN Control for the H601B and H6010 lights? I would like to integrate these into Home Assistant and/or WLED but right now the only way to do it is via Google Assistant SDK. The Govee Web API works, but limitations make it completely unusable for anyone with more than a couple of lights. LAN control would work but doesn't appear to be available for these lights. Can we get a better solution for integration?

What does Dreamview Toggle do?

I was working a issue in my integration and found that a new toggle was in my returned data on several devices. What does the Dreamview toggle really do?

Requesting the state of H713B returns "HTTP/1.1 500 Internal Server Error"

see title

Set Effect Speed

As of right now I haven't seen anything that indicates the ability to set effect speed is being enabled. Is there any chance we will see that added as a command, or added under the scene as a sub command?

H6061 - Segment colors do not work

On the Glide Hexa, sending the `segmentedColorRgb` instance and the `devices.capabilities.segment_color_setting` capability type does not appear to change the color of the panels. However, sending the `segmentedBrightness` instance to the same capability will adjust the brightness of individual panels.

H5040 doesn't exist when I query

Using the get-device api for my api key, the H5040 device(and associated H5054 devices) are not returned. Is this a bug or as designed? These devices appear in the Govee iOS application.

"Get Device State" request to Heater H713A always deliver empty thermostatToggle value

When requesting the device state of my Heater H713A, I get basically the entire status of the heater, but the thermostatToggle value is always empty: `{"requestId":"uuid","msg":"success","code":200,"payload":{"sku":"H713A","device":"##:##:##:##:##:##:##:##","capabilities":[{"type":"devices.capabilities.online","instance":"online","state":{"value":true}},{"type":"devices.capabilities.on_off","instance":"powerSwitch","state":{"value":1}},{"type":"devices.capabilities.toggle","instance":"oscillationToggle","state":{"value":1}},{"type":"devices.capabilities.toggle","instance":"thermostatToggle**","state":{"value":""}**},{"type":"devices.capabilities.temperature_setting","instance":"targetTemperature","state":{"value":{"unit":"Celsius","targetTemperature":20}}},{"type":"devices.capabilities.property","instance":"sensorTemperature","state":{"value":66}},{"type":"devices.capabilities.work_mode","instance":"workMode","state":{"value":{"workMode":3,"modeValue":0}}}]}}` Seems to be a problem in the API backend. Is there any Github page or email address to open an issue? In addition the targetTemperature is in degree Celsius, while the sensorTemperature is reported in degree fahrenheit. Not an error, but an inconsistency. Thanks in advance for pointing in the right direction to report an issue. Best regards André