MMM-AssistantMk2

Cr4z33

@sean
HURRAY! :man_dancing_medium-light_skin_tone:
Going to implement it right now!

Cr4z33

@sean hmm it is to my understanding that a device ID is mandatory right?

Do you have any idea if the Raspberry Voice HAT can be used with your model?
And if yes how can I find out the device id then? :thinking_face:

A Former User

@cr4z33
Do you mean device ID for audio device?
If you have a sound card(HAT) or audio processing integrated into your motherboard, get a list of all the audio devices on your system by executing this command:

arecord --list-devices

You should get output similar to this:

**** List of CAPTURE Hardware Devices ****
card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

In this case, your recording device is hw:0,0.
You can test with this.

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

For output device, similar. use

aplay --list-devices

Cr4z33

@sean
Thanks for helping a (Raspberry) noob here hehe.

I got a different result:

$ arecord --list-devices
**** List of CAPTURE Hardware Devices ****
card 0: sndrpigooglevoi [snd_rpi_googlevoicehat_soundcar], device 0: Google voiceHAT SoundCard HiFi voicehat-hifi-0 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

Therefore would my recording device still be hw:0,0?

aplay gave me this:

aplay --list-devices
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpigooglevoi [snd_rpi_googlevoicehat_soundcar], device 0: Google voiceHAT SoundCard HiFi voicehat-hifi-0 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

I believe it’s the same ID like above right?

A Former User

@cr4z33 Details are dependent with also your asound config. But,
Can you record and play some audio in Terminal?

arecord -t 5 test.wav & aplay test.wav

Can you execute this? tell me the result.

(I haven’t had voiceHAT, so cannot guaranteed, but same name could be available.)

Cr4z33

@sean
I get an error and please note that I’ve tried to translate to English. :winking_face:

arecord -t 5 test.wav & aplay test.wav
[1] 2911
arecord: main:574: unrecognized file format 5
test.wav: File or directory does not exist
[1]+  Output 1                arecord -t 5 test.wav

A Former User

@cr4z33
Try this.

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

Does this make test.wav?
If so, try this again.

aplay -D hw:0,0 test.wav

Cr4z33

@sean
Nope. :pensive_face:

arecord -t 5 -D hw:0,0 test.wav
arecord: main:574: unrecognized file format 5

A Former User

@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?)

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

A Former User

@cr4z33
Try this.

{
  module: "MMM-AssistantMk2",
  position: "top_right",
  config: {
    record: {
      recordProgram: "arecord",
      device: null        // or device: "hw:0,0"
    },

    play: {
      playProgram: "mpg321",
    },
  }
},