MMM-AssistantMk2

[A Former User]

@juantata
Just random.
When using useWelcomMessage, MMM-Hotword’s Mic should be closed. But by physical limitation, Sometimes MMM-Hotword’s mic was not completely closed when MMM-AssistantMk2 activation started. It’s not unpredictable. On the next version, it will be solved.

[juantata]

@Sean
Hi. Thanks for the reply, but I still have the same error

[juantata]

@Sean
Hi. Sorry for the insistence. I also show you the MMM-Hotword

[A Former User]

@juantata
What are you using as Mic? That error happens when your mic is not working properly.
Show me the result of arecord -l. Did you something on ALSA setup?

[juantata]

@Sean
Hi. Thank you for your interest in solving my problem. I realized that what didn’t work was the usb extension cable. Now what goes wrong is the connection between the MMM-Hotword keyword and the questions that can be asked.

I send you an image, so you can see it. I have to click with the mouse to put the microphone image

[A Former User]

@juantata
I need log when it is executed. To make things simple, remove all other modules from config.js except MMM-Hotword, MMM-AssistantMk2 and clock. Then try again and show me the logs.

[juantata]

@Sean
Hi. Fifthing all the modules except the ones you have said works perfectly.
I send you picture

magicmirror@2.8.0 start /home/pi/MagicMirror
sh run-start.sh

Starting MagicMirror: v2.8.0
Loading config …
Loading module helpers …
No helper found for module: alert.
Initializing new module helper …
Module helper loaded: updatenotification
No helper found for module: clock.
Initializing new module helper …
Module helper loaded: MMM-Hotword
Initializing new module helper …
Module helper loaded: MMM-AssistantMk2
All module helpers loaded.
Starting server on port 8080 …
You’re using a full whitelist configuration to allow for all IPs
Server started …
Connecting socket for: updatenotification
Connecting socket for: MMM-Hotword
[HOTWORD] MMM-Hotword starts
Connecting socket for: MMM-AssistantMk2
Sockets connected & modules started …
Launching application.
[AMK2] Recipe is loaded: hide_and_show_all_modules.js
[AMK2] Recipe is loaded: reboot.js
[AMK2] Recipe is loaded: recipe.template.js
[AMK2] Recipe is loaded: screen_onoff.js
[AMK2] Recipe is loaded: shutdown.js
[AMK2] Recipe is loaded: spotify.js
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[AMK2] Temporal storage directory is clearing.
[HOTWORD] stops.
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Started with text query: brief today
{ requestId: ‘5de8e91f-0000-248c-a774-089e08231078’ } { profileFile: ‘default.json’, lang: ‘es-ES’ }
[AMK2] Device Action: { requestId: ‘5de8e91f-0000-248c-a774-089e08231078’ }
[AMK2] Assistant Text Response:
[AMK2] Conversation Completed
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Detected: asistente
[HOTWORD] stops.
[HOTWORD] Final Result: { detected: true, hotword: ‘asistente’, file: null }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Assistant Text Response:
[AMK2] Transcription: qué hora — Done: false
[AMK2] Transcription: qué hora es — Done: false
[AMK2] end-of-utterance
[AMK2] Transcription: qué hora es — Done: true
{ requestId: ‘5deca769-0000-2b87-a3c0-089e08277c74’ } { profileFile: ‘default.json’, lang: ‘es-ES’ }
[AMK2] Device Action: { requestId: ‘5deca769-0000-2b87-a3c0-089e08277c74’ }
[AMK2] Assistant Text Response:
[AMK2] Conversation Completed
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Final Result: { detected: false }
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Detected: asistente
[HOTWORD] stops.
[HOTWORD] Final Result: { detected: true, hotword: ‘asistente’, file: null }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Assistant Text Response:
[AMK2] Transcription: cómo — Done: false
[AMK2] Transcription: cómo va — Done: false
[AMK2] Transcription: cómo va a — Done: false
[AMK2] Transcription: cómo va a hacer — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] Transcription: cómo va a hacer mañana — Done: false
[AMK2] end-of-utterance
[AMK2] Transcription: cómo va a hacer mañana — Done: true
{ requestId: ‘5dee51e6-0000-2a94-900a-f403043e4840’ } { profileFile: ‘default.json’, lang: ‘es-ES’ }
[AMK2] Device Action: { requestId: ‘5dee51e6-0000-2a94-900a-f403043e4840’ }
[AMK2] Assistant Text Response:
[AMK2] Conversation Completed
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Detected: asistente
[HOTWORD] stops.
[HOTWORD] Final Result: { detected: true, hotword: ‘asistente’, file: null }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Assistant Text Response:
[AMK2] Transcription: tiempo — Done: false
[AMK2] Transcription: tiempo para — Done: false
[AMK2] Transcription: tiempo para mañana — Done: false
[AMK2] Transcription: tiempo para mañana — Done: false
[AMK2] Transcription: tiempo para mañana — Done: false
[AMK2] end-of-utterance
[AMK2] Transcription: tiempo para mañana — Done: true
{ requestId: ‘5dee4ec1-0000-2199-8106-f403043e4994’ } { profileFile: ‘default.json’, lang: ‘es-ES’ }
[AMK2] Device Action: { requestId: ‘5dee4ec1-0000-2199-8106-f403043e4994’ }
[AMK2] Assistant Text Response:
[AMK2] Conversation Completed
[HOTWORD] begins.
[HOTWORD] Detector starts listening.

[A Former User]

@juantata
It means some of your other modules might have some errors to prevent the working of AssistantMk2.

[juantata]

@Sean
So, I have to try one by one to see which one fails?

[A Former User]

@juantata

So, I have to try one by one to see which one fails?

Maybe.
Or you can use npm start dev to investigate front-end logs on dev-console of MM screen. Anyway, that is out of range which I can help.