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!

poopyurinal

Looking for some clarifications here. I tried Sam’s suggestion and created a GoogleAssistant.service in /etc/systemd/system. I am a little confused on the command though:

‘/home/pi/MagicMirror/modulesMMM-GoogleAssistant/python3 assistant.py’

The assistant.py file is located in /home/pi/MagicMirror/modules/MMM-GoogleAssistant/pi. And wouldn’t the “python3” command come first? Could someone clarify?

Then, continuing to follow this post, he suggested running:

ps -ef | grep assistant

to find the process id. However, when i try to kill that process id, is says it “No such process”. If I run the same command several times in a row, I get different process ids each time. Is it trying to run via some other pathway and retrying constantly? It wouldn’t surprise me, as I’ve tried to get this working via many methods. How can I track this down?

Thanks for your help!

sdetweil

@poopyurinal you are right. python3 should come first.

poopyurinal

Thanks for clarifying. Any idea on the process id changing with

ps -ef | grep assistant

??

sdetweil

@poopyurinal sounds like assistant is ending on its own.

When u do this manually, do you have to be in the module folder?

If you run the python3 path…/assistant.py

When u are NOT in the module folder, does it work, or give an error?

poopyurinal

I can run the command:

python3 /home/pi/MagicMirror/modules/MMM-GoogleAssistant/pi/assistant.py

as long as I first run:

source /env/bin/activate

It works appropriately after running those two commands. Running the top command in this post without running the bottom command results in an error.

sdetweil

@poopyurinal ok, make a two line script to execute both commands, and use that script as the exec script in the service

poopyurinal

Sorry, can you go into a little more detail on that? How would I create that script?

sdetweil

@poopyurinal edit a new file, add the two lines to it, and save.

The do

chmod +x ????

Where ??? is the name of the file you just created

Then make that file name the name of the exec script.

poopyurinal

Do you mean a shell script? Or a python script?

sdetweil

@poopyurinal shell script