HomeAssistant | put some ass in your home.

/ NAS / By

Keep having connection issues – it works – then without an changes from me – it’s down.

NOTES:

When you are bridged, the virtual machine asks the router directly for an IP address and can have ports forwarded to it. (Don’t forward 8123 to it, if you have port 443 working). When you set the mode to NAT, it doesn’t ask the router for an IP address Virtualbox gives it an IP address inside the Virtualbox ONLY network, in this mode you would need to port forward to the PC running virtualbox, rather than to the virtual machine itself – though I am not entirely sure how this configuration works myself to be honest, because then you are dealing with double NAT which makes everything a headache to troubleshoot. I believe when you are using the NAT mode, that you need to access Home Assistant via it’s NAT IP which you probably can’t do – because the SSL certificate will probably complain.

Virtual box on NAS

https://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

 

  • then add the file to nas
  • then create new virtual machine
    (other linux system 65-bit)

  • pick ram
  • pick storage – existing
  • select image you downlaoded
  • macine – SETTINGS

    motherboard – enable EFI

    netowrk change to bridged adapter

  • then check cli output to get the ip address for home assitatnt.

     

    Install Home Assistant Operating System

    DOWNLOAD THE APPROPRIATE IMAGE

    Follow this guide if you already are running a supported virtual machine hypervisor. If you are not familiar with virtual machines we recommend installation Home Assistant OS directly on a Raspberry Pi or an ODROID.

    CREATE THE VIRTUAL MACHINE

    Load the appliance image into your virtual machine hypervisor. (Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs).

    Minimum recommended assignments:

    • 2 GB RAM
    • 32 GB Storage
    • 2vCPU

    All these can be extended if your usage calls for more resources.

    HYPERVISOR SPECIFIC CONFIGURATION

    VirtualBox
    KVM (virt-manager)
    KVM (virt-install)
    Vmware Workstation
    Hyper-V
    1. Create a new virtual machine
    2. Select Type “Linux” and Version “Linux 2.6 / 3.x / 4.x (64-bit)”
    3. Select “Use an existing virtual hard disk file”, select the unzipped VDI file from above
    4. Edit the “Settings” of the VM and go “System” then “Motherboard” and select “Enable EFI”
    5. 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 discard option must be enabled:

    VBoxManage storageattach <VM name> --storagectl "SATA" --port 0 --device 0 --nonrotational on --discard on
    Bash

    START UP YOUR VIRTUAL MACHINE

    1. Start the Virtual Machine
    2. Observe the boot process of Home Assistant Operating System
    3. 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).

    With the Home Assistant Operating System installed and accessible you can continue with onboarding.

    ONBOARDING

    Install Home Assistant Core

    INSTALL WSL

    To install Home Assistant Core on Windows, you will need to use the Windows Subsystem for Linux (WSL). Follow the WSL 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.

    INSTALL DEPENDENCIES

    Before you start, make sure your system is fully updated, all packages in this guide are installed with apt, if your OS does not have that, look for alternatives.

    sudo apt-get update
sudo apt-get upgrade -y
    Bash

    Install the dependencies:

    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
    Bash

    The above-listed dependencies might differ or missing, depending on your system or personal use of Home Assistant.

    CREATE AN ACCOUNT

    Add an account for Home Assistant Core called homeassistant. Since this account is only for running Home Assistant Core the extra arguments of -rm is added to create a system account and create a home directory.

    sudo useradd -rm homeassistant
    Bash

    CREATE THE VIRTUAL ENVIRONMENT

    First we will create a directory for the installation of Home Assistant Core and change the owner to the homeassistant account.

    sudo mkdir /srv/homeassistant
sudo chown homeassistant:homeassistant /srv/homeassistant
    Bash

    Next up is to create and change to a virtual environment for Home Assistant Core. This will be done as the homeassistant account.

    sudo -u homeassistant -H -s
cd /srv/homeassistant
python3 -m venv .
source bin/activate
    Bash

    Once you have activated the virtual environment (notice the prompt change to (homeassistant) homeassistant@raspberrypi:/srv/homeassistant $) you will need to run the following command to install a required Python package.

    python3 -m pip install wheel
    Bash

    Once you have installed the required Python package, it is now time to install Home Assistant Core!

    pip3 install homeassistant==2023.2.4
    Bash

    Start Home Assistant Core for the first time. This will complete the installation for you, automatically creating the .homeassistant configuration directory in the /home/homeassistant directory, and installing any basic dependencies.

    hass
    Bash

    You can now reach your installation via the web interface on http://homeassistant.local:8123.

    If this address doesn’t work you may also try http://localhost:8123 or http://X.X.X.X:8123 (replace X.X.X.X with your machines’ IP address).

    When you run the hass command 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.