MMM-AssistantMk2

[A Former User]

@citizendevpi @Cr4z33
Still got problem?
I’m making whole new update. It will be more stable and easy to install & use. I’ll release this new update in this week. Plz wait a few days.

[citizendevpi]

@sean no i did some tweeking with mp3 for audio.encoding out and that cleared up the sound issue i do get a frequent js error like every time i use the hotword:Error: open() failed: -1
at Speaker._open (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/speaker/index.js:106:13)
at Speaker._write (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/speaker/index.js:183:23)
at doWrite (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Speaker.Writable.write (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:334:11)
at Reader. (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_helper.js:287:17)
at emitNone (events.js:111:20)
at Reader.emit (events.js:208:7)
at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/wav/node_modules/readable-stream/lib/_stream_readable.js:934:16
at _combinedTickCallback (internal/process/next_tick.js:131:7)
Some error happens. Try again.

[A Former User]

@citizendevpi
First, I will abandon this annoying module dependency - Speaker. Sometimes it will not work as my feature. So, currently I’m not making fix about Speaker module. it will be deprecated.
Instead using node module, I will use other stable method - your default audio player program. I’m testing now and it will be released soon.

[citizendevpi]

@sean you are the man !!! thank you for the info and i will be looking forward to the latest release any time you need anything let me know fyi i love ghost in the shell also keep workin.

[Cr4z33]

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

@citizendevpi @Cr4z33
Still got problem?
I’m making whole new update. It will be more stable and easy to install & use. I’ll release this new update in this week. Plz wait a few days.

Fortunately I was busy at getting to work two LED strips so OK I will wait with pleasure hehe.

Thanks for letting me know. :thumbs_up_medium-light_skin_tone:

[A Former User]

UPDATED (2.0.0)

• Whole new build-up.
• Annoying speaker dependencies deprecated
• More stable. (I think)
• Choppy sound issue solved(I think), If you get still this issue, that might be the lack of computing power of your device.
• NotificationTrigger dependency free. Now you can activate without NotificationTrigger (But If you want, you can still use it.)
• Making Hook and GAction becomes easier
• MMM-TelegramBot and other modules supported

[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?