c6f5a1bb27
Just as it happens for the `/etc/network/interfaces` it would be more polite to actually ask the user if they want to overwride their `/etc/NetworkManager/NetworkManager.conf`. Changing this file by force will most likely shut a user out of their PI, because of wifi MAC address randomization, which is hardly the expected behavior from an install script. __Those choosing to use this install script do it to keep control over their machine, which includes avoiding unexpected deletion of their config files.__ For instance, things work just fine for me with the following `NetworkManager.sh`: ``` [main] plugins=ifupdown,keyfile [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ``` If something out of the downloaded `NetworkManager.sh` is actually mandatory (doesn't seem so tho) It's would be better di explicitly explain it to the user so their can take actions, rather than causing them unexpected behaviors. |
||
|---|---|---|
| .github | ||
| files | ||
| azure-pipelines.yml | ||
| installer.sh | ||
| LICENSE | ||
| README.md | ||
This installation method is for advanced users only
Make sure you understand the requirements
Install Home Assistant Supervised
This installation method provides the full Home Assistant experience on a regular operating system. This means, all components from the Home Assistant method are used, except for the Home Assistant Operating System. This system will run the Home Assistant Supervisor. The Supervisor is not just an application, it is a full appliance that manages the whole system. It will clean up, repair or reset settings to default if they no longer match expected values.
By not using the Home Assistant Operating System, the user is responsible for making sure that all required components are installed and maintained. Required components and their versions will change over time. Home Assistant Supervised is provided as-is as a foundation for community supported do-it-yourself solutions. We only accept bug reports for issues that have been reproduced on a freshly installed, fully updated Debian with no additional packages.
This method is considered advanced and should only be used if one is an expert in managing a Linux operating system, Docker and networking.
Installation
Run as root (sudo su):
curl -Lo installer.sh https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh
bash installer.sh
Command line arguments
| argument | default | description |
|---|---|---|
| -m | --machine | On a special platform they need set a machine type use | |
| -d | --data-share | $PREFIX/share/hassio | data folder for hass.io installation |
| -p | --prefix | /usr | Binary prefix for hass.io installation |
| -s | --sysconfdir | /etc | Configuration directory for hass.io installation |
you can set these parameters by appending --<parameter> <value> like:
curl -Lo installer.sh https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh
bash installer.sh --machine MY_MACHINE
Supported Machine types
- intel-nuc
- odroid-c2
- odroid-n2
- odroid-xu
- qemuarm
- qemuarm-64
- qemux86
- qemux86-64
- raspberrypi
- raspberrypi2
- raspberrypi3
- raspberrypi4
- raspberrypi3-64
- raspberrypi4-64
- tinker
Troubleshooting
If somethings going wrong, use journalctl -f to get your system logs. If you are not familiar with Linux and how you can fix issues, we recommend to use our Home Assistant OS.