Installation finished

So you've probably installed your own HAL9000 using this installer and got this URL from the installer - great! Now what? This page intends to guide you with the next steps. First off, it is important that you restart the Linux system in which you installed the HAL9000. This is primarily due to two aspects:

1. Ensure that the hardware-specific configurations are in effect (udev rules)
2. Let systemd (the user instance for the user 'hal9000') start the HAL9000-specific services

Runtime

First off: You either have a

• "virtual runtime", so no dedicated hardware and no Arduino (with a display)
  or
• "physical runtime", so maybe even in a the "full" HAL9000 enclosure with a Pi Zero2W and one of the supported microcontroller boards.

So just read the corresponding of the next sub-sections.

Virtual runtime

If you've installed on a system without an Arduino (with a display) then you need to open the HTML frontend to interact with the HAL9000 (aside from voice-interaction). The HTML frontend is published via HTTP on port 9000 and lets you interact with the user-interface just as if you had a physical runtime.

Physical runtime

If you've installed on a system with an Arduino (with a display) then you can just interact with the HAL9000 user-interface using that hardware. In addition, you could also use the HTML frontend via HTTP on port 9000 - both "displays" should be fully synchronized.

Voice activation (a.k.a. wake-word)

The wake-word is "OK, HAL". The installed wake-word-engine (openwakeword) has a pretty low false-positive rate but that comes with a only-good-enough false-negative rate, so you might have to repeat that wake-word every now and than. As an alternative, the voice activation can also be triggered from the user-interface: it should be the very first menu item listed when you use the control (physical) rotaries / (HTML) buttons.

Voice commands

Important: The TTS model is loaded when the first voice command is to be spoken - on a Pi Zero this takes about 10 seconds; currently there is no UI indication about this state. It's probably easiest to just wait until the timeout triggers and HAL responds with "I am sorry, I did not understand you" - and just trigger a new prompt. This happens only on the very first interaction after startup and will be adressed (soon'ish) by pre-loading the TTS model during startup.

The installed container images comes with a few "demo" commands. Multiple command variants are usually configured as listed below - some variations are just simply different ways of phrasing the same intent but some variations exist because the text-to-speech (TTS) engine might churn out slightly different wordings (for example: "shutdown" vs. "shut down")

Command group: Date/time query

• Let HAL tell you the current time
  • What time is it?
  • What's the time?
  • How late is it?
• Let HAL tell you the current date
  • What date is today?
  • What day is today?
  • What is todays date?

Command group: Reminder

• Let HAL remind you in a number of minutes
  • Set a timer for <X> minutes

Command group: System shutdown/reboot

• Linux shutdown
  • Turn yourself off
  • Power off
  • Shut down
  • Shutdown
• Linux reboot
  • Restart yourself
  • Reboot

Changing voice commands

tl;dr: "console" HTML user-interface on port 8080, first screen on first column.

TODO