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.

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

"Effects" not present unless auth/api are provided #349

Closed
AlgoClaw opened this issue Dec 31, 2024 · 2 comments
Closed

"Effects" not present unless auth/api are provided #349

AlgoClaw opened this issue Dec 31, 2024 · 2 comments

Comments

@AlgoClaw
Copy link

Govee Device SKU

H61A8

Govee2MQTT Version

2024.12.30-c0545a87

Describe the issue

If I start the docker container with the environment variables "GOVEE_EMAIL", "GOVEE_PASSWORD", and "GOVEE_API_KEY", the "Effects" UI element is present in HA.

However, if I exclude those variables when spinning up the container, the "Effects" button is not present.

Startup Diagnostics

.

Additional Logs

No response

Home Assistant Logs

No response

Anything else?

No response

wez added a commit that referenced this issue Dec 31, 2024
We default to querying the list of scene effects from the platform
API, but if you are running without the platform API credentials
(eg: want to run in LAN only mode) then we'd punt on getting
the list of scenes, even though we do actually have a way to
obtain that information to pave over gaps in the Govee API.

This commit adds a fallback to querying that light effect
catalog.

refs: #349
@wez
Copy link
Owner

wez commented Dec 31, 2024

I added a fallback for this case in the latest build; how's that work for you?

@AlgoClaw
Copy link
Author

That worked. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants