How to install HASS.IO in QNAP NAS?

How to install HASS.IO in QNAP NAS?

In this tutorial you will learn how to easily install HASS.IO in QNAP NAS. HASS. IO not only including Home Assistant software but increasing Plugin download installation, management web interface integrated into Home Assistant, etc. Compare to Home Assistant, HASS.IO increase more convenient function for user to use.

 

HASS.IO will be managed by using Docker system. The below tutorial will teach you how to use Docker in LXC to install HASS.IO. (You may refer to “How to install Docker (x86) in QNAP NAS LXC container?” to acquire more information)


Installation

    1. Ensure you have edited your LXC setting file in your NAS (Container Station located in container-station-data/lib/lxc/ and add the below commands into the last line) (Note: This way will improve the authority that Container control Host, make sure all the process with security):

    2. Go into LXC Container Shell
    3. Enter the commands:

    4. Enter “ifconfig eth0″ to make sure Container IP location and open your browser: http://<Container IP>:8123/

    5. You may need to increase your account & password when you first time login.

External devices (Example: Z-wave Dongle)


    1. Go to Container Station > Container Settings >Device
    2. Set up your Permission:

    3. If you have used TTY devices then go to your NAS Host to edit LXC setting file and add device path & permission. (Refer to below sample):

      Note: This is only for sample, please refer to device instruction and LXC setting file instruction

Related posts

19 thoughts on “How to install HASS.IO in QNAP NAS?

  1. Max

    Hi!
    Step 1 ‘Installation’… what file exactly? I can’t figure it out what file you mean here?

    Thanks for this tutorial.

    Max

    1. tim

      Hi Max

      The LXC Container config file is in ” Container > container-station-data > lib > lxc > [Container name] > config” (If you use default container station install path)
      Please edit config file follow step.

      Thank you.

  2. If you disable the container from the container station application, then after re-enabling how to start Home Assistans?

    1. tim

      Hi Kuba

      Restart LXC container will auto start HASS.IO (Home Assistans).

  3. Max

    Hi Cheng, Istalled Hassio according to your manual. thank you for that. But running into som issues while installing Hassio add-ons. Eg. node-red. Getting error message; “Error grabbing logs: EOF”. Little bit of digging and i found another error message: “[hassio.docker] Can’t start addon_a0d7b954_nodered: 500 Server Error: Internal Server Error (“linux
    runtime spec devices: error gathering device information while adding custom device “/dev/mem”: no such file or directory”)”

    Any ideas?

    Thank you in advanced.

    Max

    1. tim

      Hi Max

      Because HASS.IO node-red need to access host’s “/dev” folder. You can try to add this to LXC config :

      “lxc.mount.entry = /dev dev none bind,optional,create=file 0 0”

      But you must protect your LXC Container, as this will allow the Container to fully access the dev folder on the host.

      You can try it, Thank you.

  4. Nix

    Hi Cheng, I’ve some problem when I start new installed add-on for example I’ve installed esphomeyaml and get this error: ERROR (SyncWorker_10) [hassio.docker] Can’t start addon_7bce6681_esphomeyaml: 500 Server Error: Internal Server Error (“linux runtime spec devices: error gathering device information while adding custom device “/dev/ttyS1″: no such file or directory”)
    How can solve this issue?
    Thanks in advance, and for your great work.
    Regards

    1. tim

      Hi Nix

      Because some HASS.IO add-on need to access host’s “/dev” folder. You can try to add this to LXC config :

      “lxc.mount.entry = /dev dev none bind,optional,create=file 0 0”

      But you must protect your LXC Container, as this will allow the Container to fully access the dev folder on the host.

      You can try it, Thank you.

      1. Nix

        Okay, I’il try. What do you mean, when you say “But you must protect your LXC container” How should I do this?
        Regard

        1. tim

          Hi Nix

          You can change username, password and upgrade software in LXC container like general Linux system.

          1. Nix

            Ok thanks, please reply at the questions below

  5. Nix

    Hi Tim, how can connect a NodeMCU ESP8266 to a USB port on the NAS to program with ESPhome addon on HASSIO?
    Thank you.

    1. tim

      Hi Nix,

      Due to the QTS OS Linux kernel driver support limitations, it does not necessarily support the usb to tty chip of your NodeMCU. If you can’t find any “ttyUSBx” in the “/dev/” path of the NAS, it is not supported.
      If you find “ttyUSBx”, you can follow this step “External devices” to add this device in Container.

      Thank you.

  6. Adam

    I can’t seem to get the frontend to load. When I run docker ps in the lxc it shows both homeassistant and hassio_supervisor containers running. Then I run ifconfig, copy the IP address from hassio and add 8123. Also tried the IP of docker0. Both aren’t working

  7. Nix

    Hello @Tim, How can connect xiaomi_aqara gateway, in the logs I see the following error, but the key is correct: ERROR (Thread-3) [xiaomi_gateway] Unknown gateway ip 192.168.173.190 – ERROR (SyncWorker_5) [xiaomi_gateway] Got error element in data {“error”:”Invalid key”}, the IP 192.168.173.190 it’s of the NAS; IP of Xiaomi Gateway is 192.168.173.222, why it goes to look for the Xiaomi gataway on IP 192.168.173.190. Thank You

    1. tim

      Hi Nix,

      You can reference this official document :
      https://www.home-assistant.io/components/xiaomi_aqara/
      in this document show “Xiaomi Aqara Gateway” is unsupported devices.

      Thank you.

      1. Nix

        Hello Tim, xiaomi Mijia is supported, on rpi3b+ with hass.io it’s perfect.
        Thanks anyway

  8. Adam

    My hassio is running fine but the hostname is empty and I got the following errors. ANy idea how to fix them?
    Can’t connect to hostname
    Can’t update host service information!

    1. tim

      Hi Adam,

      Please check your container’s “eth0” ip and try to connect it again.

      http://(Container's “eth0” IP):8123/

      Thank you.

Leave a Reply