Nick
The dependency should automatically be updated using jitpack. Has it not?
I just ran into this with an Angular project that I wanted to run in WSL Legacy 1.0 (because WSL 2 doesn't have file listeners). I can probably stick with...
Okay this seems to work if I go use fluent-ffmpeg directly: ``` async function concatAudioWithFluent(concats: string[], finalFile: string) { return new Promise((res, rej) => { console.log(`Concat (${concats.length}) - ${concats.join(',')}`) const...
How are you obtaining the `deviceCredentials` values? There may be an issue with how you obtained the `client_id`.
I don't have any experience or familiarity with IONIC, but I don't imagine it would necessarily be any different than calling the Node.js functions as they exist now.
Yeah, you'll need to create an [`AudioInConfig`](https://developers.google.com/assistant/sdk/reference/rpc/google.assistant.embedded.v1alpha2#google.assistant.embedded.v1alpha2.AudioInConfig) instead of the text query and then start sending [`audio_in`](https://developers.google.com/assistant/sdk/reference/rpc/google.assistant.embedded.v1alpha2#embeddedassistant) bytes up until you decide to close the connection or you receive `AssistResponse.event_type.END_OF_UTTERANCE`....
When you create a project, did you select the **Device Registration** option at the bottom of the onboarding page?
Specifically step 11 should point to [this link](https://developers.google.com/assistant/sdk/guides/library/python/embed/install-sample). We should probably update the README as some of the documentation links has changed.
Once you select a conversational or smart home action, it changes the console behavior for that action. In either of those cases Device Registration doesn't make sense so it's intended...
Right now the best way would be to create a new project, which I recognize isn't ideal.