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

Auto-spawn a genie-client on startup #288

Merged
merged 9 commits into from Nov 20, 2021
Merged

Auto-spawn a genie-client on startup #288

merged 9 commits into from Nov 20, 2021

Conversation

gcampax
Copy link
Contributor

@gcampax gcampax commented Nov 18, 2021

This is the basic change to get a genie-client to run in the container.

For the separate speaker use case, I think we'll expose the access token in the configuration page, and add the ability to create ingress session tokens using the supervisor API to communicate through the add-on ingress.

@gcampax gcampax requested a review from ad31c0 November 18, 2021 20:23
Make it more similar to the build of the Home Assistant add-on,
and bring in the genie-client in the container
@gcampax
Copy link
Contributor Author

gcampax commented Nov 18, 2021

With this PR, I have a working standalone docker that has sound, using the new client. The build is almost identical to the add-on so porting to Home Assistant should be straightforward.

@gcampax gcampax merged commit d6697af into master Nov 20, 2021
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

Successfully merging this pull request may close these issues.

None yet

1 participant