Read the statement by Michael Teeuw here.
MMM-AssistantMk2
-
@Cr4z33
Well, now it is on development and not ready to release so details could be changed.
But it might have these features;- No need to wait after hotword. You could say “mirror, blahblah” instead “mirror (pause and wait activation) blahblah.”
- Some annoying dependency would be removed. HTML5 default audio output would be used, so you don’t be bothered by sound output configuration. If your web browser can play some audio, it would be enough
- Installer will be provided.
- Recorded wav file by user or other module could be used for your query. (So User can query via 3 ways - text, real-time vocal query, pre-recorded vocal query)
- Annoying
center
region issue would be gone. - ScreenOutput would be more controllable (duration time, size, activation inner links, suggested commands, …)
- The core informations of screenOutput would be extracted for later using. (e.g: external link to open a broswer for getting additional information. it could be transferable to other module for later using.)
- Creating and managing
custom action
would be easier.- So I’m considering to remove
transcriptionHook
trick to useaction
instead. - I served
transcriptionHook
for making simple voice command, but that is not a natural way to use Google Assistant. In many cases, Ppl tried to make commands which are not related with google assistant directly. Rather those kinds of commands could be achieved by just simple voice detection without AI. So I now add that feature toMMM-Hotword
and being condering to drop out fromMMM-AssistantMk2
- So I’m considering to remove
- YouTube features will be removed. (And Spotify also)
- Instead, YouTube, Spotify, Web Browsing, Map Direcions, Image search would be separated as independent module. those modules will use the info which is extracted from result of query. Of course, each module could be used standalone without AMK2. I’ll make it one-by-one. (Or whoever has interests could)
-
@Sean wow that’s a BIG change in the module! 😲
Can’t wait to start trying it out mate to use all the good stuff you are adding in it.
Thanks for letting us know and have a nice Sunday. 😁
-
Wonderful. I want to try these changes!!!
-
Hello
How can I stop Assistant’s response and make request again like Google Home Speaker can ? -
This is my config, still don’t work yet
{ module: "MMM-AssistantMk2", ..... notifications: { ... ASSISTANT_UNDERSTOOD: "HOTWORD_RESUME", }, } }, { module: "MMM-Hotword", ... models: [ ... { hotwords : "stop", file : "stop.pmdl", sensitivity : "0.5", }, ], command: { ... "stop":{ notificationExec: { notification: "ASSISTANT_CLEAR", payload: (detected, afterRecord) => { return {profile:"default"} } }, afterRecordLimit:0, restart:false, }, }, },
-
@smarthome Sorry, at this moment, there is no way to interrupt response. Just wait ends.
-
@Sean said in MMM-AssistantMk2:
@smarthome Sorry, at this moment, there is no way to interrupt response. Just wait ends.
Tks for your quick answer! Can we make a command exec to mpg21 to stop blayback google response?
-
And other question is, if I ask a command that Google can not find the suitable answer, there’s no response while google home speaker give a promise answer? Is there any configure to do that?
-
Can we make a command exec to mpg21 to stop blayback google response?
Ideally, might be possible. But not only playing sound is the issue related. So, currently not so easy.
And other question is, if I ask a command that Google can not find the suitable answer, there’s no response while google home speaker give a promise answer? Is there any configure to do that?
Currently, No.
Anyway, I’m building a new updates. It might have possibility of solving your issue. I’m planning to remove dependencies about sound out. It might become more controllable about voice response.
But due to my vacation, and new RPI4, Raspiban Buster and other many things which I should concern besides make its release somewhat lately. sorry. -
This post is deleted!