PHAL is our Platform/Hardware Abstraction Layer, it completely replaces the concept of hardcoded "enclosure" from
Any number of plugins providing functionality can be loaded and validated at runtime, plugins can be system integrations to handle things like reboot and shutdown, or hardware drivers such as Mycroft Mark 2 plugin.
PHAL plugins can perform actions such as hardware detection before loading, eg, the mark2 plugin will not load if it does not detect the sj201 hat. This makes plugins safe to install and bundle by default in our base images.
Platform/Hardware specific integrations are loaded by PHAL, these plugins can handle all sorts of system activities.
|reboot / shutdown / factory reset
|mycroft mark1 integration
|mycroft mark2 integration
|respeaker 2mic hat integration
|respeaker 4mic hat integration
|wifi setup (central plugin)
|wifi setup (GUI interface)
|wifi setup (hotspot)
|wifi setup (network manager)
|automatic geolocation (IP address)
|automatic geolocation (GPS)
|dashboard control (ovos-shell)
|system notifications (ovos-shell)
|GUI color schemes (ovos-shell)
|UI to edit mycroft.conf (ovos-shell)
|video/audio capture devices (OCP)
|api and gui to interface with Home Assistant
AdminPHAL performs the exact same function as PHAL, but plugins it loads will have
This service is intended for handling any OS-level interactions requiring escalation of privileges. Be very careful when installing Admin plugins and scrutinize them closely
NOTE: Because this service runs as root, plugins it loads are responsible for not writing configuration changes which would result in breaking config file permissions.
AdminPlugins are just like regular PHAL plugins that run with
Admin plugins will only load if their configuration contains
"enabled": true. All admin plugins need to be explicitly enabled.
You can find plugin packaging documentation here.