Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Service shuts down on startup with 504 Gateway Timeout #254

Closed
CamSoper opened this issue Jul 31, 2024 · 6 comments
Closed

Service shuts down on startup with 504 Gateway Timeout #254

CamSoper opened this issue Jul 31, 2024 · 6 comments
Labels
responsible:govee The issue seems to be on Govee's side and needs them to take action

Comments

@CamSoper
Copy link

CamSoper commented Jul 31, 2024 •
edited
Loading

Govee Device SKU

any

Govee2MQTT Version

2024.07.21-c9d27764

Describe the issue

govee2mqtt is currently failing on startup with a 504 Gateway Timeout from the API.

Based on users currently reporting Govee app issues on this old resurrected Reddit thread, it appears to be a server-side issue and no remediation in govee2mqtt should be required. I'm opening an issue for tracking and to provide a searchable artifact if it happens in the future. I'll close the issue when the issue clears up.

Startup Diagnostics

govee2mqtt | [2024-07-30T19:31:50 INFO  govee::commands::serve] Starting service. version 2024.07.21-c9d27764
govee2mqtt | [2024-07-30T19:31:50 INFO  govee::commands::serve] Querying platform API for device list
govee2mqtt | Error: request https://openapi.api.govee.com/router/api/v1/user/devices status 504: Gateway Timeout. Response body: <html>
govee2mqtt | <head><title>504 Gateway Time-out</title></head>
govee2mqtt | <body>
govee2mqtt | <center><h1>504 Gateway Time-out</h1></center>
govee2mqtt | </body>
govee2mqtt | </html>
govee2mqtt |
govee2mqtt |
govee2mqtt | Stack backtrace:
govee2mqtt |    0: anyhow::error::<impl anyhow::Error>::msg
govee2mqtt |    1: anyhow::__private::format_err
govee2mqtt |    2: govee::cache::CacheResult<T>::into_result
govee2mqtt |    3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
govee2mqtt |    4: govee::commands::serve::ServeCommand::run::{{closure}}
govee2mqtt |    5: govee::Args::run::{{closure}}
govee2mqtt |    6: tokio::runtime::park::CachedParkThread::block_on
govee2mqtt |    7: tokio::runtime::context::runtime::enter_runtime
govee2mqtt |    8: tokio::runtime::runtime::Runtime::block_on
govee2mqtt |    9: govee::main
govee2mqtt |   10: std::sys_common::backtrace::__rust_begin_short_backtrace
govee2mqtt |   11: std::rt::lang_start::{{closure}}
govee2mqtt |   12: std::rt::lang_start_internal
govee2mqtt |   13: main

Additional Logs

No response

Home Assistant Logs

No response

Anything else?

No response
@CamSoper CamSoper mentioned this issue Jul 31, 2024
Closed
@CamSoper CamSoper changed the title 504 Gateway Timeout Service shuts down on startup with 504 Gateway Timeout Jul 31, 2024
@dog5point0
Copy link

Having the same issue here.

@Rodney-Smith
Copy link

Also having the issue with openapi.api.govee.com
curl --request GET
--url https://openapi.api.govee.com/v1/devices
--header 'Govee-API-Key: '
--header 'accept: application/json'

<title>504 Gateway Time-out</title>

504 Gateway Time-out

This URL of developer-api.govee.com seems to be functioning just fine
curl --request GET
--url https://developer-api.govee.com/v1/devices
--header 'Govee-API-Key: '
--header 'accept: application/json'

{"data":{"devices":[]...,"message":"Success","code":200}

@Nitnomart
Copy link

I've noticed the same issue, clearly a Govee side issue, hopefully just temporary and not a breaking change for the integration.

With local LAN control enabled on the devices and govee2mqtt talking locally to the devices is there a way to avoid issues should the internet go down or some other Govee issue like this? Is this integration 100% reliant on the cloud hosted Govee API to function? Or was I unlucky because I restarted HA while Govee had an issue and then purged caches in an attempt to get this working?

Is govee2mqtt simply trying to speak to the Govee cloud API for a list of devices to then talk locally to?

For info there is a similar more recent Redit post here talking about server issues with many people reporting them with the standard Govee app: https://www.reddit.com/r/Govee/comments/1eg6rj1/network_error/

Interestingly my Govee app works fine but I believe I am able to control my devices via Bluetooth at the moment rather than Wi-Fi if I'm correct.

@Explodedkola
Copy link

Now when I try to start the addin I get this error “status 500: Internal Server Error.”

@Explodedkola
Copy link

Now it is all working again for me!

@CamSoper
Copy link
Author

Seems fixed for now!

I hope this issue helps next time it happens. Happy automating, everyone!

@wez wez added the responsible:govee The issue seems to be on Govee's side and needs them to take action label Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
responsible:govee The issue seems to be on Govee's side and needs them to take action
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@wez @CamSoper @Rodney-Smith @dog5point0 @Nitnomart @Explodedkola