Discussions

The Govee iOS mobile app can set the H7173's 'Keep Warm' setting but it appears that the Govee API will not recognize the autoStop parameter to control the same setting per the API documentation. <https://openapi.api.govee.com/router/api/v1/device/control> { "requestId": "uuid", "payload": { "sku": "H7173", "device": "XX:XX:XX:XX:XX:XX:XX:XX", "capability": { "type": "devices.capabilities.temperature_setting", "instance": "sliderTemperature", "value": { "temperature": 145, "unit": "Fahrenheit", **"autoStop": 1** } } } } { "requestId": "uuid", "msg": "success", **"code": 200,** "capability": { "type": "devices.capabilities.temperature_setting", "instance": "sliderTemperature", "state": { "status": "success" }, "value": { "temperature": 145, "unit": "Fahrenheit", **"autoStop": 1** } } }

I have a problem with H713C and the temperatures. In the App I use temperatures in °C and target-temperatur 21°C, room temperature is 21.1°C. In the API (.../state) I get this values: - type: devices.capabilities.temperature_setting instance: targetTemperature state: value: unit: Fahrenheit targetTemperature: 23 - type: devices.capabilities.property instance: sensorTemperature state: value: 70 So you see: temperature_setting has the wrong unit. SensorTemperature is always in Fahrenheit? By the way: the heater's AutoStop in Automode doesn't work: after a short heating period the app reports that the target temperature has reached and stops heating without reaching the target temperature or restart heating.

Hi there I am using the goveelife smart heater model H713A I have successfully turned on and off the heater using the API with the following code in the body {"device": "%deviceId","model": "H713A","cmd": {"name": "turn","value": "on"}} I have tried to switch mode using the following {"device": "%deviceId","model": "H713A","cmd": { "name": "mode","value": 2}} I received a response that the command has been executed successfully but the heater doesn't change mode. Can you please advise if my syntax is incorrect? Thanks

I started retesting the Events that are received via MQTT again today. I only have two devices that support it at the moment. One of them is working and the second is not. The device that I am not receiving MQTT messages for is a H7141. Nothing comes in when it runs out of water. This is confirmed with two different applications that are Node-Red and my integration with Hubitat. Can we look at getting this resolved.

I'm trying to read the current temperature from my thermometer: ```shell curl -i -X POST \ --header 'Govee-API-Key: <my api key>' \ --header 'Content-Type: applications/json' \ -d "{\"requestId\": \"$(uuidgen)\", \"payload\": {\"sku\": \"H5103\", \"device\": \"08:21:CB:39:32:34:50:23\"}}" \ https://openapi.api.govee.com/router/api/v1/device/state ``` The response is just a sad: ``` HTTP/2 500 date: Wed, 20 Mar 2024 08:39:08 GMT content-length: 0 ``` Any idea what I did wrong?

Hello, i can't find out how to get the device iid of my H6110 led strips. if someone could tell me how to get it, it would be much appreciated.

I'm receiving the value of `2131` for the thermometer's current temperature. What unit is this? ``` { type: 'devices.capabilities.property', instance: 'sensorTemperature', state: { value: 2131 } }, ```

I have the API key up and running successfully with 8 devices being detected. 4 devices are not detected - they are all H6004 series WiFi + Bluetooth bulbs. I've verified that all 4 are connected to my WiFi router by verifying them in the app, and also verifying they have IP addresses assigned to them in the DHCP routing table on my router. The API doesn't recognize them as devices. In the supported devices list, it lists the H6004. All ideas are welcome. Thanks to all for your time. Cheers

Since we have all this new functionality I was thinking about some of the quirks with end users having to get API tokens. I wanted to start a conversation about a better way to obtain API Keys. It would be nice if there was a authenticated way we can have users obtain the key/token instead of the formal request through the app. The idea is that instead of the user on of a external platform having to use the Govee Home app to request a key, what about allowing the integrator to write a process in their code to authenticate with the Govee Home App Creds and then in the return response received the API Token for use in their external app. This would allow a more clean function for users to use these added integrations. You could also require a unique additional value that represents the source system. Then govee could track what integrations a user is using from external sources.

So far the documentation has been written up very good to cover how the new API works, but I do have a problem with how to obtain information for all of the possible devices Govee makes. Simply put i do not have a way to obtain the device capabilities and data unless I first have the device. I would like to propose a solution to that What I would like to see somewhere is simply the output from the API for the "/router/api/v1/user/devices" endpoint from an api that has one of every supported device. This would preferably update daily, or weekly to show new devices,or to show what new capabilities are added over time. This would simply be for the purpose of reference so that as developers we can write for devices we don't, or are just released. Along this same line it might be nice to have a device reference that would also show what the output would be from "/router/api/v1/device/state" for each device.