I was trying to install LIFX in Home Assistant with the standard integration (it works fine on the regular unraid docker) but I’m unable to discover any bulbs on the VM. I attribute this to the VM network, the VM is assigned IP 172.16.16.18 but Hassio when running show IP address shows 172.30.32.1/23. I’m thinking it’s only running discovery on the Hassio subnet. Do I need a route in networking for this or something else on hassio?
I finally figured it out … i had a very big mess with the database in influxdb the size was almost 13 GB so i uninstalled and going to do a different approach with the database thanks for the help tho. Snapshots are working properly now.
I ended up making a new VM and restoring from snapshot. From the Youtube video in this feed the guy responded to me and said I could resize it using the command below. Adjust filename and size to your situation. I didn’t try this because I already made the new VM before I got a reply.
UPDATE: Please see my post below: the stick was not flashed with firmware by vendor as promised. After flashing stick all worked as expected. Leaving this here as a warning to others who trusted the vendor too much!
I am aware there are quite a few comments in this thread on passing through a USB device to hassio as a VM on unraid, I have read them all but I am still struggling and I would love some help if possible.
I have a Zigbee2MQTT stick (CC2531 USB sniffer) connected to a USB port on my unraid server (3rd device listed below):
root@Tower:~# lsusb
Bus 002 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 006: ID 0451:16ae Texas Instruments, Inc.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@Tower:~#
I have passed this device through to my hassio VM with settings as follows:
UPDATE: I am beginning to think that the CC2531 is faulty or not flashed corrected. I tested things by plugging in a NodeMCU into the same USB port and passing it through to the hassio VM: it passed through without problems.
UPDATE #2: Confirmed, stick was not flashed by vendor as promised. Apologies to all
Strange but I have the exact same problem and those screens look very familiar, it also started yesterday.
It started when I pressed the “Update” button under host section in the homeassistant webgui. Homeassistant became unavailable but after few hours it did not came back.
I got a feeling that the disk became corrupted, even trying to retrieve files and snapshots from the VM disk seems difficult as I keep getting errors reading the disk. I did get one snapshot back from August 2019 which seems to be fine and some additional configuration files from homeassistant.
I did see that the filesystem was missing some files which were important in my homeassistant installation.
I’ve started a fresh install and will restore from the snapshot. Then I need to update everything that was changed since August (which is a lot …)
I’m getting the same error as well. I guess I will wait long enough that hopefully it loads again. It has not so far. I tried creating a new VM and getting the same issues as well. Have not idea what it is??
I have been having the same issue for awhile. To restart I first check config, and all is well. If I the press restart it hangs and never comes back. If I ssh into the VM I see that the database is not being updated.
If I run
hassio homeassistant rebuild
Then the HA instance starts running again.
I have also had times where I have to delete the db prior to being able to run rebuild.
