MMM-GoogleAssistant autostart

sdetweil

poopyurinal

pm2 stop mm
[PM2] Applying action stopProcessId on app [mm](ids: 0)
[PM2] mm ✓
┌──────┬────┬──────┬─────────┬───┬─────┬────────┐
│ Name │ id │ mode │ status │ ↺ │ cpu │ memory │
├──────┼────┼──────┼─────────┼───┼─────┼────────┤
│ mm │ 0 │ fork │ stopped │ 1 │ 0% │ 0 B │
└──────┴────┴──────┴─────────┴───┴─────┴────────┘
Use pm2 show <id|name> to get more details about an app

Sorry, limited by new user restriction of one post every 120 seconds

sdetweil

@poopyurinal cool now follow the link i gave about creating a service that will autostart and make it start the assitant.py

I don’t understand why the MMM-GoogleAssistant module doesn’t do this… it would be so easy…

sdetweil

in the link it asks for ‘your service name’ make that GoogleAssistant
the command is ‘/home/pi/MagicMirror/modulesMMM-GoogleAssistant/python3 assistant.py’

sdetweil

once u create the service… make sure assistant.py is not running already

ps -ef | grep assistant

the 1st number on the output is the process id
pi xxxx yyyy etc…
then

sudo kill -9 xxxx

then do

sudo systemctl start GoogleAssistant

then

ps -ef | grep assistant

to insure assistant is running
then start mirror manually with npm start

if all is good, reboot

service will start the assistant.py script
and pm2 will start mirror app

poopyurinal

Many thanks Sam! I’ll need to take a look at your suggestions tomorrow. I appreciate the quick (immediate!) help.

sdetweil

@poopyurinal no problem… let us know either way

i use the assistantmk2 module… don’t need that py file

poopyurinal

I’ll have to look at it. Tried the MM-GA module after 3+ failures of Alexa modules. Just would like one of them to work!

sdetweil

@poopyurinal also use the MMM-Alexa module

poopyurinal

Tried and failed with MMM-Alexa. Doesn’t mean I can’t try again!