netzzwergegithub/bootcontrol

use snips to reboot or shutdown the underlying raspberry (linux) system

Bootcontrol Snips skill

Skill to shutdown or reboot the underlying raspberry pi system via voice control. It's a case study for executing system commands as voice commands.

It uses the raspberry pi with raspian an the seeeds ReSpeaker 2 Mic hat. It expects having installed a snips system on a raspberry pi (e.g. https://docs.snips.ai/getting-started/quick-start-raspberry-pi) and the ReSpeaker 2-Mics Pi HAT ( http://wiki.seeedstudio.com/ReSpeaker_2_Mics_Pi_HAT/#getting-started)

The dialog can be started using the push-button on ReSpeaker 2 Mic hat. It's an example how to initiate an snips dialog via an external event.

Caution: The project manipulates the underlying raspberry pi system. You should have experience in using the unix commandbline using ssh.

Possible commands

Some commands have a optional time-parameter. If you add no time-parameter the command is executed immediately.

reboot [time to reboot]

Schedule a a reboot of the system. Optionally you can add a time value like 'in five minutes' or 'tommorow at noon'. Examples:

reboot
reboot in ten minutes

shutdown [time to shutdown]

Schedule a a shutdown of the system. Optionally you can add a time value like 'in five minutes' or 'tommorow at noon'. Examples:

shutdown
shutdown at ten o clock

halt [time to shutdown]

Schedule a a halt of the system. Optionally you can add a time value like 'in five minutes' or 'tommorow at noon'. Examples:

halt
halt at tomorrow at 10 am

stop shutdown

Stop a scheduled reboot, shutdown or halt. Usage:

stop shutdown

help

Get a short help which commands the app understands. Usage:

help

Adaption of the underlying system

The following changes have to be made directly on the raspberry pi.

increase dialog timeout

Because the respond text of the help command is a little bit longish you have to increase the timeout for the session to 25 seconds. You have to add a line to the file '/etc/snips.toml' for the category '[snips-dialogue]' using the sudo command with your favorite editor:

[snips-dialogue]
session_timeout = 25

Please restart the snips-service to activate changes:

sudo systemctl restart  "snips-*"

add skills user to sudoers

You have to configure the system to allow the _snips_skills user to execute the bootcontrol commands. First open the sudoers file via the command sudo visudo and add the following lines and save and exit the editor:

 Cmnd_Alias      SHUTDOWN = /sbin/shutdown
 # allow shutdown
_snips-skills  ALL=(ALL) NOPASSWD: SHUTDOWN

Test your assistant

After doing that you should test the system by activating the dialog saying your hotword (e.g. hey snips) to see if you can reboot your system via speech command, saying:

hey snips
reboot

After confirming the execution the system should reboot. You may consult the log if there are any errors:

 journalctl -u snips-skill-server

add user '_snips_skills to group 'gpio'

To use any gipo ports, so the button on the ReSpeaker head, you have to add the skill-user to group 'gpio'

sudo usermod -a -G gpio _snips-skills

Caution: May be you have to reboot the system to get the new permissions run.

deactivate hotword detection

To limit the activation of the installed assistant to pushing the button you have to stop and disable the snips hotword detection with the command:

sudo systemctl stop snips-hotword.service
sudo systemctl disable snips-hotword.service

Caution: This command will deactivate the activation of the snips dialog via the hotword (e.g. hey snips) for the whole system. To reactivate it use the commands: sudo systemctl enable snips-hotword.service and sudo systemctl start snips-hotword.service

Test your assistant with push button

After doing that you should test the system by activating the dialog by pushing the button on the ReSpeaker hat. The dialog should start and you should be able to reboot your system via speech command, saying:

reboot

After confirming the execution the system should reboot.