Discussions

Ask a Question

Will the Motion Sensors/ other sensors make it to the api?

Hello! I love Govee, they have been my go to for years, in several houses, for many things, I've just now gotten deep into the Smart Home Field, and Govee was a good entry point for new integrations Which leads to my question, will Govee ever add their sensors (i.e. window/door sensor, Motion Sensor, Presence Sensor, Vibration Sensor, etc.) To the api, or is this simply not possible, This would be the perfect chance for Govee to step into the market, and be a great competitor to Aqara or other sensor and light brands, The automation on the govee app, are less than stellar, the refresh rate is a little slow, such as when a door gets closed and opened too quickly, it doesn't recieve the notice, And you can't set things like, (after 5 minutes, if no Motion is detected, turn off the strip lights) or ( if Motion is detected on "Closet Motion sensor" turn on "Outdoor flood light" segment 4) I hope to hear more, and look forward to some form on integration or ability to use outside of govee

Govee Hygrometer H5179 is not listed in device list

<https://developer-api.govee.com/v1/devices> I have a hygrometer added to my account, but the device does not show up when I list devices via the above URL. It's the only device on my account, and so the device list is empty. Is this supposed to work for the hygrometer?

Govee Hygrometer H5179 is not listed in device list

<https://developer-api.govee.com/v1/devices> I have a hygrometer added to my account, but the device does not show up when I list devices via the above URL. It's the only device on my account, and so the device list is empty. Is this supposed to work for the hygrometer?

segmentedColorRgb not working for H6061

I'm currently trying to use the API to change the colour of individual segments of my Glide Hexa Light Panels but despite receiving a 200, the colour does not change. I have had success with changing individual segment brightness. ``` { "requestId": "1", "payload": { "sku": "H6061", "device": "<mac addr>", "capability": { "type": "devices.capabilities.segment_color_setting", "instance": "segmentedColorRgb", "value": { "segment":[2], "rgb":255 } } } } ``` returns ``` { "requestId": "1", "msg": "success", "code": 200, "capability": { "type": "devices.capabilities.segment_color_setting", "instance": "segmentedColorRgb", "state": { "status": "success" }, "value": { "segment": [ 2 ], "rgb": 255 } } } ``` But the light does not change colour! Can this be resolved?

How can I get the reponse like in the documentation about the lights scenes?

In the documentation there is an example response like the one below. What is the request to get this response? { "sku": "H605C", "device": "64:09:C5:32:37:36:2D:13", "category": "devices.types.light", "capabilities": \[ { "type": "devices.capabilities.dynamic_scene", "instance": "lightScene", "parameters": { "dataType": "ENUM", "options": \[ { "name": "Sunrise", "value": 0 }, { "name": "Sunset", "value": 1 }, { "name": "Movie", "value": 4 }, { "name": "Dating", "value": 5 }, { "name": "Romantic", "value": 7 }, { "name": "Flash", "value": 8 }, { "name": "Candle", "value": 9 } ``` ] } }, ] ``` } you

How can get the scene that is already played on the device? (H7020)

I saw some info about how to set a scene. but nothing about how to get the scene that is actually already set?

Local proxy for AWS IoT devices

As I understand it devices like the H6008 are limited to AWS IoT control, but it's highly desirable to control these bulbs locally. For end-users, local control means more responsive changes and more graceful behavior after power or internet outages. For Govee, local control means reduced infrastructure bills for every user who takes advantage. I propose these devices could listen for service advertisements on the LAN from a Govee-developed proxy. The proxy could be provided by a foreground mobile app with built-in broker, background desktop app with built-in or external broker, or standalone with an external broker for use with platforms like HomeAssistant and Hubitat. While the local proxy is available, the devices would subscribe to the appropriate local broker. In turn, the local proxy would subscribe to the IoT MQ to handle non-local messages on behalf of its local subscribers. Other potential proxy providers joining the network would defer to any provider already advertising, and would self-elect a new provider when the active provider leaves the network. This approach would be low-overhead, low-maintenance, and could be tucked behind a switch for advanced users like LAN control for other devices.

Difference Between 600A and 6009 and API control

The API support says that H6009 is supported, but doesn't mention anything about H600A. What is the difference between these models as I assumed that they were the same? The Govee website 1200LM bulb is the only 1200LM bulb they sell, and is listed as the H6009 which is listed in the API supported devices. However the Amazon 1200LM bulb, which is also the only 1200LM Govee bulb they sell, when I set it up is listed as H600A. Is there a difference between these two bulbs? Are only the ones sold directly from Govee listed as H6009 and supported by the API? <br /> Thanks

Support for Govee H60A1 Ceiling Light

Hi, When will the H60A1 ceiling light be added into the API. <https://uk.govee.com/products/govee-rgbww-rgbic-smart-ceiling-light> I installed one today and am very disappointed it doesn't seem to publish state through to the API? Many thanks, Tom

H5085 Smart Plug Pro Support

Please add support for the new Smart Plug Pro plugs.