Read the statement by Michael Teeuw here.
MMM-GoogleAssistant autostart
-
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 │
└──────┴────┴──────┴─────────┴───┴─────┴────────┘
Usepm2 show <id|name>
to get more details about an appSorry, limited by new user restriction of one post every 120 seconds
-
@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…
-
in the link it asks for ‘your service name’ make that GoogleAssistant
the command is ‘/home/pi/MagicMirror/modulesMMM-GoogleAssistant/python3 assistant.py’ -
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…
thensudo 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 startif all is good, reboot
service will start the assistant.py script
and pm2 will start mirror app -
Many thanks Sam! I’ll need to take a look at your suggestions tomorrow. I appreciate the quick (immediate!) help.
-
@poopyurinal no problem… let us know either way
i use the assistantmk2 module… don’t need that py file
-
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!
-
@poopyurinal also use the MMM-Alexa module
-
Tried and failed with MMM-Alexa. Doesn’t mean I can’t try again!
-
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!