MMM-AssistantMk2

A Former User

@cr4z33
Oops ! my mistake!

arecord -d 5 -D hw:0,0 test.wav

Cr4z33

@sean said in MMM-AssistantMk2 & MMM-GAction:

@cr4z33
cat ~/.asoundrc
Tell me the result.

How you can setup previously? (I think you purchased that device for Google AIY project. Was there any instructions?)

pi@raspberrypi:~ $ cat ~/.asoundrc
cat: /home/pi/.asoundrc: File or directory does not exist

It’s the so- called Google Voice Kit AIY (https://aiyprojects.withgoogle.com/voice-v1/).

I used a ready meal Raspbian image made by Google.
Apart from creating the JSON file everything else consists of ready scripts (i.e assistant_library_demo.py is a script to runs and uses Google Assistant):
https://github.com/google/aiyprojects-raspbian/tree/voicekit

A Former User

@cr4z33
Hmmm… As I know,

arecord -d 5 test.wav
aplay test.wav

This should work because there is no other suspicious things. your card and device no is 0,0 and that is the default.

Cr4z33

@sean
Again I made a noob error… I ran both commands at once lol! :smiling_face_with_open_mouth_cold_sweat:

Running them separately worked like a charm! :thumbs_up_medium-light_skin_tone:

I am going now to retry with the module addition.

Cr4z33

@sean
So after following the installation instructions I ran a test by using the ‘Very simple version but limited’ module.

As a result all I get now from MM is a black empty screen (no config.js message and no trace of other modules can be seen).

sgopala

@cr4z33 There is a small typo in the config file, please correct as under:

Incorrect: [replace this]
play: { // Full values are in FOR EXPERTS section.
playProgram: “mpg321”, // recommended.
}

Correct: [with this]
play: { // Full values are in FOR EXPERTS section.
playProgram: “mpg321”, // recommended.
},

A Former User

@sgopala Thank you!! I’ve fixed. I think I had assumed that was the last field of ESSENTIALS parts, so I might have missed the last comma.

sgopala

@sean Thanks a ton for your modules sir, you are a rockstar. But somehow I liked the previous version because of the following reasons:

(i) there is a delay after the hotword detection in the new version
(ii) the hotword detection hangs after 1st interaction with the assistant
(iii) the output window (iframe) was better sized and placed, too small on this version

Request to please see if these are feasible.

Once again, thanks a lot for this lovely module.

A Former User

@sgopala
You can always checkout the older version from github (use 1.x.x-final-snap)
And for the issues;

some delay is added intentionally to avoid possible collision. I’ll modify it could be customizable in next patch.
output size could be controllable with screenZoom field.

Thanks.

Cr4z33

@sgopala Thanks for pointing this out. ;)

@sean I keep getting either a black MM screen or the ‘config.js’ message.

At this point I prefer to work with a config with MMM-AssistantMk2 only and no other modules until everything is working 100%.

If you could help me by giving please a look at the below config? :)
Please note that I am trying to use

0:0

as device Id.

https://pastebin.com/ePfrtR75