Home Assistant Supervised (previously known as Hass.io) on Synology DSM as native package (not supported or working atm)

pergola.fabio · October 21, 2019, 12:47pm

and comment the line default_config: ?

dwl99 · October 21, 2019, 7:05pm

Thanks, tried that too with same result

dwl99 · October 23, 2019, 7:46pm

In the end I just did a clean install & restored it bit by bit

PituaK · October 27, 2019, 10:00am

Hi @fredrike I used your apk in version 20190709 if I downloaded the new with date 20191006 I lost all my Hassion configurations if I upgrade in synology apps ?

I have a problem with CC2531 coordinator I plug in Synology but de addonn zigbeemqtt doesnt start.

/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014B884F9-if00": no such file or directory

Thankssss

nivong · October 28, 2019, 4:09pm

as long as you not delete you hassio folder you are save, but wouldn’t hurt to make a backup of the map

BullFrog · October 31, 2019, 12:03pm

Read the manual, do I understand correctly?

Original HomeAssistant docker is installed and working on my NAS.

When I install your app and start my HA container, It will become hass.io magically and will use my original config and database without issue. The only change will be that hass.io panel will appear on the left menu, right?
With stopping the container and stopping your app then restarting the container will revert the old same native HomeAssistant like before? It wont corrupt the database or anything else? Can I just revert back if something is not working in my setup?

davispeden · November 2, 2019, 1:16pm

@fredrike - I hope all is well with you. I am running into a strange issue when trying to upgrade from version 0.100.0 to 0.101.2. Hoping you can help out or provide some insight. I am using the most recent version of your install package - 20191006-3c5c9bce. See screenshots:

fredrike · November 2, 2019, 2:38pm

I’ll write an reply later but it requires some time.

Why are you running pip, all upgrades should be performed via the hass.io tab in home assistant.

davispeden · November 2, 2019, 9:47pm

I had an issue where I couldn’t get the update to work from the UI…figured out that it was due to two known issues related to the myq garage door opener and my roomba integrations. Commented those out of the config and re-started the update. All appears to be good…now on 0.101.2!

Thanks again for the work on this. Awesome stuff.

Romquenin · November 3, 2019, 11:49am

Thank you ver much for this great feature @fredrike, you are awsome !

I just wanted to report , i’m was able to install the addon ESPHome and i flashed a “nodemcuv2” (ESP8266) with USB and also over the air.

All the addons i’m using on Raspberry Pi are working fine on my old DS1513+, i think it’s time to go for a more powerfull Synology.

Many thanks from France !

fredrike · November 3, 2019, 9:07pm

Ok so I finally have some time to write…

If you are migrating from Docker home-assistant it should simply be to copy the content of the configuration folder (used in your Docker home-assistant) to the created homeassistant folder under the hassio share used during installation of the hassio package. Be aware that some network addresses might change and there might be issues with auto discover.

It is possible to run both the Docker version and the hassio version (also using Docker) in parallel, I’ve been doing so since the summer. Just make sure that you are not calling the Docker home-assistant container homeassistant as that will confuse hassio.

simonwood0609 · November 4, 2019, 1:36pm

Previously running hassio on Raspberry Pi. Lost my second MicroSD card today, decided to migrate to Synology using your package.

Sucessfully installed & configured (setup username/password etc). Copied my snapshot backup from previous instance and hit restore. Waited for 30 minutes, wouldn’t come back online. Stopped the service in synology, restarted it, still nothing. Uninstalled the package, re-installed, now it won’t launch (can’t access localip:8123).

Any clues?

Trying to do full uninstall/re-install of both hassio and docker now. That worked - only after uninstalling/re-installing Docker. SOLVED

But can I restore my backup/snapshot I took from the Raspberry Pi?

I tried a second time - restoring the backup breaks hassio

ChicJr · November 9, 2019, 9:41pm

Hi Fredrik,

Just wanted to say Thank you very much for this fantastic package!

I made the migration today from Hassio on RPI3, and the move went unbelievably smoothly. Did the install from your package, copied over my most recent snapshot and restored from there, and everything came to life!

Thanks again!

Michael_Griffin · November 10, 2019, 3:03am

Thank you for this awesome package. After reading this thread and doing some tinkering, I was able to migrate my rPi3 installation to my DS918+ without much issue. Using the latest package, my zwave usb stick was recognized without any updates. I do have a couple issues that don’t appear to have been addressed in this thread, though.

The Docker containers for both hassio_supervisor and hassio_dns are constantly restarting. They basically will stay up for around 5 minutes before something causes them to crash and then they restart. It doesn’t appear to be causing any operational issues, I’m still able to connect to the hassio panel and do everything, including upgrading hassio from within the webpage. I assume this isn’t normal, but it might be causing some of the `Unable to load the panel source: /api/hassio/app/entrypoint.js`` issues that people are having.
I’m trying to use the wyzesense component that was working without any issues on my rPi3. I’ve tracked down that the hub registers as /dev/usb/hiddev8 on my synology, but I can’t figure out how to get that exposed to the homeassistant container.

fredrike · November 10, 2019, 8:01am

I’m glad that is seems to be working quite nice, I guess I should try to migrate myself in the near future ;).

I’m not sure what is going on here. I’ve seen similar behavior on my own test environment. Stopping the docker package and starting everything again seems to fix it. It would however be good to get an idea what is going on here. Perhaps you can ask in the discord channel for hassio-dev someone there might have some insight on what is going on.

It might be that you need to install the serial drivers that have been linked to above. Are you sure that the /dev/usb isn’t exposed to the homeassistant container? There might be a workaround with creating a device rule file similar to what I was doing here (in fix_usb_devices) spksrc/spk/hassio/src/hassio.sh at 6dd0666ca5013b4bec6252a9f592adbeabed1d5e · fredrike/spksrc · GitHub

fredrike · November 10, 2019, 8:03am

Try to bring in your configuration in pieces to figure out what is going on. I also suggest that you have a look in the log file…

Michael_Griffin · November 10, 2019, 4:18pm

Regarding the restarting supervisor container, I do see these logs spammed the /var/log/messages

2019-11-08T23:24:16-05:00 alexandria synoscgi_SYNO.Docker.Container_1_list[26837]: container.cpp:435 success regen profile for container [hassio_dns]
2019-11-08T23:24:42-05:00 alexandria SystemInfo.cgi: SystemInfo.cpp:270 get network error.
2019-11-08T23:25:59-05:00 alexandria SystemInfo.cgi: SystemInfo.cpp:270 get network error.
2019-11-08T23:27:28-05:00 alexandria SystemInfo.cgi: SystemInfo.cpp:270 get network error.
2019-11-08T23:28:09-05:00 alexandria kernel: [223126.885758] BTRFS error (device dm-1): cannot find qgroup item, qgroupid=33728 !
2019-11-08T23:28:09-05:00 alexandria kernel: [223126.885758]
2019-11-08T23:28:09-05:00 alexandria kernel: [223127.028609] BTRFS error (device dm-1): cannot find qgroup item, qgroupid=33727 !
2019-11-08T23:28:09-05:00 alexandria kernel: [223127.028609]
2019-11-08T23:28:14-05:00 alexandria kernel: [223131.694361] BTRFS error (device dm-1): cannot find qgroup item, qgroupid=33726 !
2019-11-08T23:28:50-05:00 alexandria synoscgi_SYNO.Docker.Container_1_list[3358]: container.cpp:435 success regen profile for container [hassio_supervisor]
2019-11-08T23:28:50-05:00 alexandria synoscgi_SYNO.Docker.Container_1_list[3358]: container.cpp:505 Remove dummy container profile hassio_dns
2019-11-08T23:28:50-05:00 alexandria SystemInfo.cgi: SystemInfo.cpp:270 get network error.
2019-11-08T23:29:22-05:00 alexandria synoscgi_SYNO.Docker.Container_1_list[3359]: container.cpp:435 success regen profile for container [hassio_dns]
2019-11-08T23:33:30-05:00 alexandria ntpd[9202]: bind(37) AF_INET6 fe80::b09d:f5ff:fec4:3607%7311#123 flags 0x11 failed: Cannot assign requested address
2019-11-08T23:33:30-05:00 alexandria ntpd[9202]: unable to create socket on dockereb08280 (4922) for fe80::b09d:f5ff:fec4:3607%7311#123
2019-11-08T23:33:30-05:00 alexandria synoscgi_SYNO.Docker.Container_1_list[7926]: container.cpp:505 Remove dummy container profile hassio_supervisor
2019-11-08T23:33:34-05:00 alexandria ntpd[9202]: bind(38) AF_INET6 fe80::604b:4dff:feb4:23f3%7313#123 flags 0x11 failed: Cannot assign requested address
2019-11-08T23:33:34-05:00 alexandria ntpd[9202]: unable to create socket on docker8274bfd (4924) for fe80::604b:4dff:feb4:23f3%7313#123
2019-11-08T23:33:42-05:00 alexandria ntpd[9202]: bind(41) AF_INET6 fe80::2c3e:23ff:fef3:f3df%7315#123 flags 0x11 failed: Cannot assign requested address
2019-11-08T23:33:42-05:00 alexandria ntpd[9202]: unable to create socket on docker9bb9529 (4926) for fe80::2c3e:23ff:fef3:f3df%7315#123

With the WyzeSense, I double checked and it does look like the device is exposed to the container. I think the error is something else.

2019-11-09 21:24:00 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.wyzesense
2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.binary_sensor] WYZESENSE v0.0.4
2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.binary_sensor] Attempting to open connection to hub at /dev/usb/hiddev8
2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.wyzesense_custom] Start Inquiry...
2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=4327, Payload=<None>
2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa55430327016c'
2019-11-09 21:24:26 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of platform wyzesense is taking over 10 seconds.
2019-11-09 21:24:28 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up platform wyzesense
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
OSError: [Errno 22] Invalid argument

neil2048 · November 10, 2019, 11:30pm

Hi Fredrike, amazing thank you for the native package installer, is there a way to be able to ssh into the homeassistant container, i need to be able to run some python commands to debug issues with the hass-sonoff-ewelink integration. i have installed the ssh server hassio addon, but can’t see a way to get to the shell from the hassio prompt, Thanks in advance

fredrike · November 11, 2019, 3:42am

I would try to do the following.

ssh into your Synology box
access a shell on the homeassistant container via sudo docker exec - it homeassistant /bin/sh

neil2048 · November 11, 2019, 10:47pm

Perfect thanks, that did what i needed.