Setting up jarvis.umdl

[Jacob-Meischner]

I just got this fully working finally and the last step I would like to do is change my assistant .umdl to jarvis instead of snowboy. I see that you need to put 2 sensitivities in for jarvis and also change the ApplyFrontend to true. I am completely lost on how to do this, I don't know a whole lot about coding so bare with me please! Would these changes just be a matter of editing the module in the config.js or do I need to go somewhere else to make the changes?

Thanks in advance!

[eouia]

Sorry for my absence, I was stuck in my real world. sorry again.
Frankly says, I'm not supporting this module anymore. I was so disappointed with this module's complexity and difficulty to maintain. A half was due to my poor skill, and the other half was due to incomplete Google Assistant SDK and MagicMirror-Electron problems and... even snowboy stuffs.

Anyway, Maybe this could be help.

file: 'resources/models/jarvis.umdl',
sensitivity: '0.8,0.80',
hotwords: ['jarvis','jarvis'] 

[Jacob-Meischner]

No problem man, real world unfortunately comes first haha. I replaced what you said in my module and FINALLY it recognized the jarvis hotword when I said it but the microphone immediately turned red and did not respond to my command. I did a pm2 logs and this is what it gave me.

PM2        | [2018-07-04 13:06:08] PM2 log: pid=2075 msg=process killed
PM2        | [2018-07-04 13:06:50] PM2 log: Starting execution sequence in -fork mode- for app name:MagicMirror id:0
PM2        | [2018-07-04 13:06:50] PM2 log: App name:MagicMirror id:0 online
PM2        | [2018-07-04 13:08:40] PM2 log: Stopping app:MagicMirror id:0
PM2        | [2018-07-04 13:08:40] PM2 log: App [MagicMirror] with id [0] and pid [2325], exited with code [0] via signal [SIGINT]
PM2        | [2018-07-04 13:08:40] PM2 log: pid=2325 msg=process killed
PM2        | [2018-07-04 13:13:47] PM2 log: Starting execution sequence in -fork mode- for app name:MagicMirror id:0
PM2        | [2018-07-04 13:13:47] PM2 log: App name:MagicMirror id:0 online
PM2        | [2018-07-04 13:14:59] PM2 log: App [MagicMirror] with id [0] and pid [2959], exited with code [0] via signal [SIGINT]
PM2        | [2018-07-04 13:14:59] PM2 log: Starting execution sequence in -fork mode- for app name:MagicMirror id:0
PM2        | [2018-07-04 13:14:59] PM2 log: App name:MagicMirror id:0 online
PM2        | [2018-07-04 13:15:05] PM2 log: Stopping app:MagicMirror id:0
PM2        | [2018-07-04 13:15:06] PM2 log: App [MagicMirror] with id [0] and pid [3142], exited with code [0] via signal [SIGINT]
PM2        | [2018-07-04 13:15:06] PM2 log: pid=3142 msg=process killed

/home/pi/.pm2/logs/MagicMirror-error-0.log last 15 lines:
0|MagicMir | 
0|MagicMir | (process:2360): Gtk-WARNING **: Locale not supported by C library.
0|MagicMir | 	Using the fallback 'C' locale.
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information
0|MagicMir | 
0|MagicMir | (process:2994): Gtk-WARNING **: Locale not supported by C library.
0|MagicMir | 	Using the fallback 'C' locale.
0|MagicMir | libGL error: MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information
0|MagicMir | MESA-LOADER: failed to retrieve device information
0|MagicMir | 
0|MagicMir | (process:3177): Gtk-WARNING **: Locale not supported by C library.
0|MagicMir | 	Using the fallback 'C' locale.

[Jacob-Meischner]

Just for giggles I tried using

resources/models/jarvis.umdl: Universal model for the hotword "Jarvis" (https://snowboy.kitt.ai/hotword/29). It has two different models for the hotword Jarvis, so you have to use two sensitivites and two hotwords. Set sensitivities to "0.8,0.80", hotwords to "['jarvis1','jarvis2']" and ApplyFrontend to true.

from one of the snowboy PR's Kitt-AI/snowboy@9c1c9a9 but that didn't work either.

[eouia]

I doubt it is not related with snowboy. Gtk is Graphic Tool Kit, so it means GTK problem could be related with graphical issue - especially electron updated to 2.0.
That might be out of my ability, sorry.