MMM-AssistantMk2

juantata · Dec 7, 2019, 7:24 PM

@Sean
Good. I have a problem, it has started happening today.

Today’s summary works perfectly, but then the microphone does not listen and therefore there is no conversation.

pi@raspberrypi:~/MagicMirror $ npm start

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: calendar
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper …
Module helper loaded: MMM-GoogleMapsTraffic
No helper found for module: MMM-YouTube.
No helper found for module: MMM-connection-status.
Initializing new module helper …
Module helper loaded: newsfeed
Initializing new module helper …
Module helper loaded: MMM-Remote-Control
Initializing new module helper …
Module helper loaded: MMM-Hotword
Initializing new module helper …
Module helper loaded: MMM-AssistantMk2
Initializing new module helper …
Module helper loaded: MMM-Spotify
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: calendar
Starting node helper for: calendar
Connecting socket for: MMM-GoogleMapsTraffic
Starting node_helper for module: MMM-GoogleMapsTraffic
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: MMM-Hotword
[HOTWORD] MMM-Hotword starts
Connecting socket for: MMM-AssistantMk2
Connecting socket for: MMM-Spotify
[SPOTIFY_AUTH] Token is fresh.
Sockets connected & modules started …
Launching application.
ERROR! Could not find main module js file for pir
Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/juanan+++ioiglesias21%40gmail.com/private-225241cce3b9ecf***011ef3193f0934/basic.ics - Interval: 300000
Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: ‘standard’ }
Create new news fetcher for url: https://okdiario.com/feed - Interval: 300000
[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
[AMK2] Temporal storage directory is clearing.
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] stops.
[HOTWORD] Final Result: { detected: false }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Started with text query: brief today
{ requestId: ‘5deab96c-0000-2e12-9cee-f403043d40d8’ } { profileFile: ‘default.json’, lang: ‘es-ES’ }
[AMK2] Device Action: { requestId: ‘5deab96c-0000-2e12-9cee-f403043d40d8’ }
[AMK2] Assistant Text Response:
[AMK2] Conversation Completed
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Final Result: { detected: false }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Assistant Text Response:
[AMK2] Conversation Error: { Error: 14 UNAVAILABLE: Service unavailable.
at Object.exports.createStatusError (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/common.js:91:15)
at ClientDuplexStream._emitStatusIfDone (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:233:26)
at ClientDuplexStream._receiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:211:8)
at Object.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1306:15)
at InterceptingListener._callNext (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:618:8)
at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1123:18
code: 14,
metadata:
Metadata { _internal_repr: { ‘content-disposition’: [Array] }, flags: 0 },
details: ‘Service unavailable.’ }
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Final Result: { detected: false }
[AMK2] assistant ready
[AMK2] Conversation starts.
[AMK2] Assistant Text Response:
[AMK2] Conversation Error: { Error: 14 UNAVAILABLE: Service unavailable.
at Object.exports.createStatusError (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/common.js:91:15)
at ClientDuplexStream._emitStatusIfDone (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:233:26)
at ClientDuplexStream._receiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:211:8)
at Object.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1306:15)
at InterceptingListener._callNext (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:618:8)
at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1123:18
code: 14,
metadata:
Metadata { _internal_repr: { ‘content-disposition’: [Array] }, flags: 0 },
details: ‘Service unavailable.’ }
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
[HOTWORD] Final Result: { detected: false }
^C
pi@raspberrypi:~/MagicMirror $

A Former User · Dec 8, 2019, 2:03 PM

@juantata
Just remove useWelcomeMessage. That feature needs more configuration when using together MMM-Hotword. Not difficult but if you don’t understand what’s going on, just remove it.

juantata · Dec 8, 2019, 2:33 PM

@Sean
Thanks for the reply. But one question, if there has never been a problem with the daily summary, why now?

A Former User · Dec 8, 2019, 2:44 PM

@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 · Dec 9, 2019, 1:05 PM

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

juantata · Dec 9, 2019, 1:16 PM

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

A Former User · Dec 9, 2019, 1:24 PM

@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 · Dec 9, 2019, 3:25 PM

@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 · Dec 9, 2019, 3:32 PM

@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 · Dec 9, 2019, 3:52 PM

@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.