Virtual box on NAShttps://www.asustor.com/en/online/College_topic?topic=249
So I think if you take the homeassistant ip and add the port from here 3389 you can ssh into the machine.
ssh -p 2222 user@host
Install Home Assistant
- Install virtual box + extension from app center
- admin/admin – default pw
- once virtural box is running
- search for home assistant install – https://www.home-assistant.io/installation/
- We want windows – virtual box
(other linux system 65-bit)
motherboard – enable EFI
netowrk change to bridged adapter
Install Home Assistant Operating SystemRaspberry Pi or an ODROID.
- 2 GB RAM
- 32 GB Storage
- Create a new virtual machine
- Select Type “Linux” and Version “Linux 2.6 / 3.x / 4.x (64-bit)”
- Select “Use an existing virtual hard disk file”, select the unzipped VDI file from above
- Edit the “Settings” of the VM and go “System” then “Motherboard” and select “Enable EFI”
- Then go to “Network” “Adapter 1” choose “Bridged Adapter” and choose your Network adapter
Please keep in mind that the bridged adapter only functions over a hardwired ethernet connection. Using Wi-Fi on your VirtualBox host is unsupported.6. Then go to “Audio” and choose “Intel HD Audio” as Audio Controller.
By default VirtualBox does not free up unused disk space. To automatically shrink the vdi disk image the
discardoption must be enabled:
VBoxManage storageattach <VM name> --storagectl "SATA" --port 0 --device 0 --nonrotational on --discard on
- Start the Virtual Machine
- Observe the boot process of Home Assistant Operating System
- Once completed you will be able to reach Home Assistant on homeassistant.local:8123. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at homeassistant:8123 or
http://X.X.X.X:8123(replace X.X.X.X with your ’s IP address).
ONBOARDINGWSL installation instructions and install Ubuntu from the Windows Store. As an alternative, Home Assistant OS can be installed in a Linux guest VM. Running Home Assistant Core directly on Windows is not supported.
This is an advanced installation process, and some steps might differ on your system. Considering the nature of this installation type, we assume you can handle subtle differences between this document and the system configuration you are using. When in doubt, please consider one of the other installation methods, as they might be a better fit instead.
PrerequisitesThis guide assumes that you already have an operating system setup and have installed Python 3.10 (including the package
python3-dev) or newer.
apt, if your OS does not have that, look for alternatives.
sudo apt-get update sudo apt-get upgrade -y
sudo apt-get install -y python3 python3-dev python3-venv python3-pip bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata
homeassistant. Since this account is only for running Home Assistant Core the extra arguments of
-rmis added to create a system account and create a home directory.
sudo useradd -rm homeassistant
sudo mkdir /srv/homeassistant sudo chown homeassistant:homeassistant /srv/homeassistant
sudo -u homeassistant -H -s cd /srv/homeassistant python3 -m venv . source bin/activate
(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $) you will need to run the following command to install a required Python package.
python3 -m pip install wheel
pip3 install homeassistant==2023.2.4
.homeassistantconfiguration directory in the
/home/homeassistantdirectory, and installing any basic dependencies.
http://homeassistant.local:8123. If this address doesn’t work you may also try
http://X.X.X.X:8123(replace X.X.X.X with your machines’ IP address).
When you run the
hasscommand for the first time, it will download, install and cache the necessary libraries/dependencies. This procedure may take anywhere between 5 to 10 minutes. During that time, you may get “site cannot be reached” error when accessing the web interface. This will only happen for the first time, and subsequent restarts will be much faster.