MMM-AssistantMk2

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.

0_1575905110988_01ad4bb6-e448-4c4c-b0f4-2944f2a160fb-image.png

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.

juantata

@Sean
Thank you very much for the help and time you have dedicated to me.

juantata

@Sean
Hi. Sorry for the inconvenience again. It tells me to update MMM-AssistantMk2, and when I update it it doesn’t stop.

0_1575987582077_034a034b-9337-48c1-b5e0-74338001b417-image.png

A Former User

@juantata
If you have no unsatisfying or any issue with current version, You don’t need to update. Not for only this module, but for all modules of MagicMirror, and forMagicMirror itself. This is my personal recommendation.

The error means you’d modified the source (Why?) Usually, a user doesn’t need to (SHOULDN’T) do modifying the source itself.
Don’t do what you don’t understand.

However you want to update anyway, just remove those files then git pull again. (If not work, try git stash)

berne

@Sean said in MMM-AssistantMk2:
-Multi profile and language demo

mmm so i can use google assistant and speak Swedish to it in the new mk2?
if so… im going to make a new build

A Former User

@berne
Swedish is not supported by Google officially yet.
https://developers.google.com/assistant/sdk/reference/rpc/languages

tontonchow

Hi
This module is fine but I I can’t get it to work in French. When I call “jarvis”, mk2 assistant don’t undertand french, only english. Someone have the same issue ?

A Former User

@tontonchow
simply, adjust your account setting on your google assistant app of your smartphone.

tontonchow

@Sean my app is correctly configure for me. If he don’t understand histoire reply is in french but if i speak french he don’t understand.

Étrange

A Former User

@tontonchow
Weird. Transcription on the log is returned as French as expected?

tontonchow

@Sean Yes
I don’t know why but it seems to work after adjust config.js and reboot

add , after lang line

profiles: {
         "default" : {                                                                                                                   
                    profileFile: "default.json",                                                                                            
                    lang: "fr-FR",

A Former User

@tontonchow
Can you show me the log of transcription part when you said some phrases as French? To see whether transcription was recognized as French or not.

MisterT

Hi Sean,
Nice works for MK2 update but i have a problem to install it. I launched the auto installation but a packet is not found. gcc-7 is missing. when a try to install manually the answer is (in french):

pi@raspberrypi:~/MagicMirror/modules/MMM-AssistantMk2 $ sudo apt-get install gcc-7
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
E: Impossible de trouver le paquet gcc-7

when i write gcc -v the result is:

gcc version 6.3.0 20170516 (Raspbian 6.3.0-18+rpi1+deb9u1)

And without this my Magic mirror turn into a black screen

How i can install gcc-7 ?
Do i need an update of raspbian to install gcc-7. I’m on last version of raspbian Stretch

Thanks for your support and your next answers

A Former User

@MisterT
first, try to install without gcc7. usually gcc8 on buster was a reason of problem, so gcc6 on stretch might be ok(not tested currently but it worked a year ago)

MisterT

hi @Sean thanks for your reply. So retry auto installation with gc6 and rebuild electron. Then finish the config with my audio and mic. Great
After these, i download my credentials then make my default profile.
So everithing seem to bo good. that’t why i start MM and:
MK2v3 logo is on my Magic mirror with animation but when i say a simple sentence, nothing happen.
I changed hotword word to Jarvis and html5 to mpg321 but it’s the same thing.

See below my config js for hotword and MK2

			{
	module: "MMM-Hotword",
	position: "top_left",
	config: {
	useDisplay: false,
	chimeOnFinish: null,
	recipes: ["with-AMk2v3_Jarvis.js"],
	mic: {
		recordProgram: "arecord",
		device: "plughw:1",
            },
				  },
	},
		{
  	module: "MMM-AssistantMk2",
  	position: "top_right",
  	config: {
	debug: true,
	 ui: "Classic",
	assistantConfig: {
	latitude: 43.64074, // -90.0 - +90.0
	longitude: 5.09545, // -180.0 - +180.0
					  },
	responseConfig: {
	useHTML5: false, // sound render by HTML5
	playProgram: "mpg321",
				},
	micConfig: {
	recorder: "arecord",
	device: "plughw:1",
				   },
	recipes: [
	"with-MMM-Hotword.js"
				   ],
	profiles: {
	"default": {
		profileFile: "default.json",
			lang: "fr-FR"
				 }

				  },
			},
		},

have you an idea ?