I have a Govee device that is unresponsive that constantly shows Retry for the CloudAPI. I found a suggestion in another thread that suggesting clicking on the initialize button. I’ve done that a few times and the status goes from Retry to Pending and then back to Retry. Still no device control. I’ve also tried to reboot the hub with no joy. Anyone have any ideas?
What is the device? What driver is it using?
Generally this can be a problem when you slam the API with your device.
Initialize should reset the status and if it is not i need to figure out why so i can fix it.
Also what do the logs say for the device?
The device is an Govee RGB strip H6159. The driver is Govee Lights, Plugs, and Switches Driver.
I can’t seem to post a shot of the log so I went about this the long way.
dev:82
dev:82
min.
2024-09-17 10:05:24.817 PM
error on):
CloudAPI already in retry state. Aborting call.
2024-09-17 10:05:22.486 PM
error
sendCommand):Unknwon Error. Attempting again in one
dev:82
2024-09-17 10:05:22.485 PM
error
groovyx.net.http.HttpResponseException: status code: 500, reason phrase: Internal Server Error
dev:82
2024-09-17 10:05:22.484 PM
error
Error:
e.statusCode 500
dev:82
2024-09-17 10:05:22.423 PM
error
sendCommand):Unknwon Error. Attempting again in one min.
dev:82
2024-09-17 10:05:22.422 PM
error
groovyx.net.http.HttpResponseException: status code: 500, reason phrase: Internal Server Error
dev:82
2024-09-17 10:05:22.421 PM
error
Error:
e.statusCode 500
dev:82
2024-09-17 10:05:22.420 PM
error
sendCommand):Unknwon Error. Attempting again in one min.
dev:82
2024-09-17 10:05:22.419 PM
error
groovyx.net.http.HttpResponseException: status code: 500, reason phrase: Internal Server Error
dev:82
2024-09-17 10:05:22.418 PM
error
Error:
e.statusCode 500
dev:82
min. dev:82
2024-09-17 10:05:22.372 PM
error
sendCommand):Unknwon Error. Attempting again in one
A few things.
That driver is from the Old V1 integration. You really need to upgrade to V2
That retry should only be occuring at most every min. But it looks like it is happening every second. Is your log being spammed.
Honestly my suggestion would be scroll to the bottom of the device page and remove the device. That should stop the loop from continuing. Then use HPM to instal the Govee Integration V2 and use that. Allot has changes since V1 at this point.
The errors from the log look like their Cloud API Server is having a issue.
I have stopped updating the V1 integration so please upgrade first and if you continue to have issues let me know.
Tip.. you can use the Same API key with V2. No nees to request a new one.
1 Like
You need to add yourself to the owners group.
1 Like
@mavrrick58 - Thanks for the help on this. Got everything going again by following the steps you listed.
@Evilborg - Thanks for the tip on joining the owners group.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
