Is there any repository link I could use?

Error at end of import process.

Is it possible to rename the hostname from HASSIO to HASSOS? It would avoid an unpleasantness with duplicate names in the network as long as people like me still use both systems at the same time.

It's raising this error when I am trying to use the rpi_camera component.

[homeassistant.components.camera.rpi_camera] 'raspistill' was not found

Raspberry Pi 3 B+
HassOS 1.7
hassio version 1.3.1
home assistant version 0.74.0

This has probably to do with the container renaming. So I wait for the next version, but how can it get the OTA update if the container is not starting anymore?

Should I update it over USB? If so, how? Just drop the raucb file one one and plus it in before rebooting? Couldn't find instructions on this.

On flashing the latest image of HassioOS on Mac with etcher, on completion I see the following and cannot access the disk - any advice? When I insert the SD card into the pi HassOS does boot up, but since I cannot edit the network file via my Mac I cannot setup wifi.

The .6 beta OVA can not be imported into QTS 4.3 running VS3. TS453B x86 based QNAP.

Error is not very useful.

Import VM fail
[Import VM] Import VM fail config format error: Unknown ovf format

Have tried the OVA file and untarred it to try the OVF directly, Same error in both cases.

Haven’t managed to find any log files with any further data.

When performing an upgrade following these instructions, at the step where I am restoring from my full snapshot, I am having issues with it restoring everything. It is failing to restore my customize, automation, iframe, and lights yaml files. It also fails to restore my nest.conf file. I can add them back manually and keep on going but it is strange that it is not putting everything back. I am coming from a 32 bit RP3B upgrading to a 32 bit RP3B+.
Thanks for all your hard work!

HI
Today I try and test again hassos ver. 1.7 for 32bit and 64bit , it is very sad, the same situation is with ver 1.5, no data transfer by checking. waiting for almost 20 minutes every time.
I test it by different RPI 3B and different SD, it is also same. please check the reason.

regards

Dragon

On the RPI3, I have this device https://www.home-assistant.io/components/sensor.mitemp_bt/ but can not read the info.

i think that the problem is this

bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set BDADDR UART: b8:27:eb:aa:aa:aa
Set Controller UART speed to 921600 bit/s
Device setup complete

the number MAC not is correct. b8:27:eb:aa:aa:aa

1.5

• improvment: Move bluetooth to core host OS
• bugfix: Fix boot menu on UEFI for OTA updates

1.4

• bugfix: Store clock time on overlay for reboot

1.3

• improvment: Change dhcp client for store static lease / Remember IP on DHCP
• improvment: Reset u-boot on wrong boot
• bugfix: Dropbear/ssh can't start CLI and cut the connection
• bugfix: Avahi don't read the correct hostname

1.2

• bugfix: CLI lost access to supervisor after reboot/ota update
• bugfix: Journald is not persistent (reboot) and can fill overlay partition
• bugfix: Config load from USB looks to wrong label config instead CONFIG
• bugfix: Fix cgroup memory error on raspberrypi

1.1

• bugfix: configuration with USB is not fat32 friendly
• bugfix: Wireless work better with wpa_supplicant
• bugfix: SSH key folder is not persistent / service is not active anymore

Hass.io Supervisor 115
HassOS 1.7
Home-Assistant 0.74
Raspberry Pi 2 B

Home Assistant does not get an IPv6 address on my router, while other devices do get an IPv6 address.
Is IPv6 supported in HassOS?
If so, what configs/logs/... can I check to find the problem or enable IPv6 support?

Heyho..

tried to install it on my Synology DSM.. Got the same problem as other ppl with BIOS and UEFI.. that got fixed quickly..

but after that, i get to the bootmenu, i can select something and then it just freezez up or does nothing at all.. only the 4th option with the shell worked... any ideas?

Error while setting up platform netatmo

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 129, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/binary_sensor/netatmo.py", line 73, in setup_platform
    if not data.get_camera_names():
  File "/usr/lib/python3.6/site-packages/homeassistant/components/netatmo.py", line 82, in get_camera_names
    self.update()
  File "/usr/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 318, in wrapper
    result = method(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/netatmo.py", line 113, in update
    self.camera_data = pyatmo.CameraData(self.auth, size=100)
  File "/usr/lib/python3.6/site-packages/smart_home/Camera.py", line 50, in __init__
    for e in self.rawData['homes'][i]['events']:
KeyError: 'events'

netatmo camera is not detected in HassOS 1.5 I tried this solution: home-assistant/core#15047 modifying the camera.py file in another installation with Home Assistant and it works perfectly even from other users who had this problem. Is it possible to integrate this Fix also for HassOS in the next Update?

Hello,
I am trying to do fresh install of HomeAssistant based on HassOS.
I flashed (via Etcher) the latest version from https://www.home-assistant.io/hassio/installation/
I prepared USB Drive, generated new UUID, put the connection file into the network folder, inserted both to RPi and boot RPi.
That´s all, raspberry did not connect to preconfigured wifi, even if waiting one hour or so. (ie. cannot connect either to hassio.local:8123 or to static IP defined in the connection file)
Tested with both method=auto and static IP. No success at all :(
I did all descibed here https://www.juanmtech.com/home-assistant-hassos-beginners-guide/ up to point 2, or in any other guide.
If I insert microSD with previous version (based on HassIO), everything goes well again, well, it works except several weird error reports.
This is my connection config:

[connection]
id=hassos-network
uuid=d69b7932-02ea-4e14-b29a-8c0939e1fcae
type=802-11-wireless

[802-11-wireless]
mode=infrastructure
ssid=my wifi name

[802-11-wireless-security]
auth-alg=open
key-mgmt=wpa-psk
psk=my password

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=auto

Is there anything what I could do differently (in the better way)?

Update:
Installation is possible only while using ethernet. i.e. without USB..
Tested several USB sticks, FAT32, NTFS, FAT - if plugged, there is no internet connection at all.
Strange is that if using ethernet, it is impossible to bind mac address to IP (as I had it on Hassio) it means reconfigure everything where static IP is used.
So far- HassOS for me - no way :( :(

Update: Static IP solved by several reboots of my router.

To support more device, we need more Hardware. I live in Switzerland and our prices and duties (especially import) are high.
If you have a device which you don't need anymore and will send us or you want donate a small amount for a device, that would be amazing. Feel free to extend this list of hardware.

You can send donation to my paypal account and add a description with the name of you favorite device.

Hardware list

• ASUS Tinker Board: 70$ - 100%
• Pine64: 30$ - 0%
• Rock64: 50$ - 100%
• Raspberry Pi 3+: 50$ - 100%
• Intel nuc: 130$ - 100%
• Orange Pi PC 2: 28$ - 100%
• Orange Pi Zero: 18$ - 100%
• Orange Pi Zero 2: 28$ - 100%
• Odroid C2: 70$ - 0%
• ODROID-HC2: 75$ - 0%
• Odroid XU4: 85$ - 100%

Paypal: [email protected] / http://paypal.me/pvizeli
Patreon: https://www.patreon.com/pvizeli
For post address, send me a PM on discord.

Configuration instructs users to use "hassos-config" as name for USB volume name which cannot be done using FAT32.

Workaround: use Ext4 or wait for #48

HI:
I use version 1.3 into RPI 3B is ok, but use new version 1.5 32Bit or 64Bit are all no answer by checking data,RPI 3B are always red light on right side.
So, I don't know what is different between 1.3 and 1.5 on Installation method，anyway，this version 1.5 can not install into RPI 3B.
I change many different SD 16G ,32G and RPI 3B are same.
so please check what's problem for this version.

Dragon

I have a working Zwave network under Domoticz that I am trying to move to Home Assistant.

I have installed the ova on ESXi 6.5 using the link provided by mihalski for issue #102 and I have successfully updated from 1.5 to 1.8.

I use the ESXi web interface to connect my Aeotec Zstick Gen5 and my RFXCOM hub. The RFXCOM hub is recognised as /dev/ttyUSB0 and is working but the Aeotec Zstick is not.

Running lsusb I get

The Aeotec Zstick is recognised as Bus 002 Device 004.
But no device appears in the /dev directory so I can not connect to it.

From dmesg the boot process detects both USB devices and configures the RFXCOM hub but can not identify the Aeotec Zstick.

Can anyone help me please?
Thank you

This project looks promising - but how can I deploy a docker container on it?

After reading this article on the security of HA, I was wondering if Hass os runs it as root? Probably not, but just asking for clarity.

Also, are there any other security constraints we have to be aware of with Hass os? Any default passwords or things like that?

I have tried to get hassos working on Hyper-V running on Windows Server 2016 but was unable to. I will report my findings:

I used the 1.8 vmdk file which needed to be converted to VHD or VHDX to be able to used with hyperv. I tried both Starwind's V2V converter as Microsoft's Virtual machine converter. Both were able to convert to VHD / VHDX files without error.

I then created VM's, i tried both Gen 1 and 2 (hassos instructions mention UEFI needed so i think Gen 2 should be used). I attached the VHD(x) file.

In none of the cases the VM would actually boot - it would either show a blank screen with cursor blinking or it would display some UEFI booting diagnostic messages.

The last line I see is
IPv6: ADDRCONF(NETDEV_CHANGE): hassio: link becomes ready

Features OS

• Allow to use data partition on a USB drive

I've tried a process similarly to the Hass.io getting started procedure. I basically etch the image on my SD card.

When I do this, I don't see anything happening on the screen after booting my rpi. No splash screen nor code running.

When I wait longer I also don't see any IP coming online. Am I doing the right thing or is the process different?

I want to add onewire but I can access to boot folder.

Running HassOS in a Vitualbox VM with USB passthrough on (as a USB 2.0 EHCI Controller) the device does not appear in the hardware page. From the CLI, hassio hw info does not show it either.

Running 1.8

• Active rauc timer
• Disable system1 on init in dts for EFI
• Implement PKI
• Fix expander after rename
• Use AppArmor from URL (http://s3.amazonaws.com/hassio-version/apparmor.txt)
• Use official defconfig for u-boot

I tried to setup HassOS in Proxmox (KVM). Almost everything works as expected, HassOS boots and Home Assistant is running.
However, /dev/ttyUSB0 is not found in HassOS.
I think the drivers for the deCONZ USB dongle are not loaded. The device is found in the VM:

dmesg | grep FTDI
[    3.214149] usb 3-1: Manufacturer: FTDI

lsusb
...
Bus 003 Device 002: ID 0403:6015

In my original HassIO generic install on Ubuntu Server the folowing drivers where loaded for this device:

usbserial
ftdi_sio

dmesg | grep FTDI
[    2.418960] usb 1-6: Manufacturer: FTDI
[    3.904772] usbserial: USB Serial support registered for FTDI USB Serial Device
[    3.904858] ftdi_sio 1-6:1.0: FTDI USB Serial Device converter detected
[    3.908125] usb 1-6: FTDI USB Serial Device converter now attached to ttyUSB0

lsusb
...
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

How do I get this working in HassOS?

Hi!

I am having an issue where I cannot get the correct time in my logs. The hass.io log can have this event:
18-07-05 09:30:48 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3, but time was actually 11:30:48. There is a two hour offset...
I have set time_zone: Europe/Oslo in configuration.yaml.
Do we have access to set the time for supervisor in another way?

I did try pressing UPDATE on Hass.io System page, but after really long time it never came up again.

I then did a ard restart and it came up still running 15.

Is updating working, ad how long time is one to expect it takes ?

The Raspberry 3B does not have a clock, when first time boot the system after flashed the image to SD card, looks like the system doesn't sync the date/time with NTP, the wrong date, caused the hassos_supervisor can't connect to the server to download the landing page(SSL error: CERTIFICATE_VERIFY_FAILED).

Saw your question on #barebox about using EFI with barebox state.

A working example for using a fixed partition as storage backend for state I have is:

state: state {
        magic = <0x3f2ba231>;
        backend-type = "raw";
        backend = <&state_part>;
        backend-stridesize = <4096>;
        #address-cells = <1>;
        #size-cells = <1>;

        [...]
 }

partitions {
        compatible = "fixed-partitions";
        #address-cells = <1>;
        #size-cells = <1>;

        state_part: state {
                partuuid = "14367da7-c518-499f-9aad-e1f366692363";
        };
};

The partition in my case is crated with a script calling sfdisk:

sfdisk -X gpt /dev/sdX << EOF
start=2048,size=18432,type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B,bootable
start=20480,size=2048,uuid=14367da7-c518-499f-9aad-e1f366692363
[...]
EOF

Look like after OTA update or restart, the container will be not recreate and run with old machine-id.

Hi,
I recently switched to HassOS. Almost everything works fine - except the Raspicam.

I appended the following lines to config.txt:

# Camera       
gpu_mem=128    
start_file=start_x.elf         
fixup_file=fixup_x.dat         
disable_camera_led=1

But this results in the Raspberry Pi not booting at all (no screen output, nothing). I tried this on both armhf and aarch64.
Is there any HassOS specific config.txt voodoo that I am missing? Thanks.

I have a Raspberry Pi 3b. Which should I choose, 32 or 64 bits and why?

Thanks

I tried with 3 different Hdmi cables to scan the hdmi ports of my television. For all three I get the response "Autodetect failed"

Full log:
starting version 3.2.2
autodetect FAILED

I have tried to reboot the raspberry pi. Tried to reboot the TV as well. For one of the cables I'm absolutely positive that it should work, since I also use it with another device.

The error is not very helpful, so I'm not certain if the problem is with Hass os or the addon. Most issues with autodetect failed seem to be solved by using another cable. I've tried this but it didnt work.

Hi,

This is specific to the versions in the topic as I've had different experiences with HassOS 1.3 for example and not yet had the chance to try ESXi 6.7.

Problem:
Installing HassOS 1.5 directly in VMware ESXi 6.5 leads to no ip/interface on the LAN (DHCP server running on pfSense), so homeassistant cannot be installed.

Solution:
You can do the installation on an identically configured vm in VMware Fusion (or Workstation I presume) and it works fine. You can then export an OVA file and import it back into ESXi. Just make sure you've got the right compatibility settings before exporting.

In my case I chose Other Linux 3.x or greater as the OS and compatibility of vmx13.

Would be interested in hearing other people's experiences with HassOS and VMware ESXi.

Regards,
Michal

I installed the new distribution of HASSOS over the weekend (July 7). I created a USB stick per the instructions, named CONFIG with a directory named network and a plain-text file with no extensions called my-network, the file content is at the end of this note.

I have not been able to get WiFi going on the Pi.

I connected a keyboard & monitor to the Pi & logged in. I verified the file was copied correctly to /etc/NeworkManager/system-connections on the Pi. The file protection is -RW-------

The output from nmcli d says that wlan0 is disconnected

The output from dmesg | grep mmc1 says wlan0: link is not ready

Content of my-network file:

[connection]
id=hassos-network
uuid=72111c67-4a5d-4d5c-925e-f8ee26efb3c3
type=802-11-wireless

[wifi]
mode=infrastructure
ssid=mySSID

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
pskmyPSK

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=auto

Hi, I'd like to build this, but the instructions are not clear (for me).

• About the USB Stick & hass.json, how, and when does this get used?
• The line: make -C /build/buildroot BR2_EXTERNAL=/build/buildroot-external xy_defconfig isn't doing anything for me.
• How to actually get an Image for a RPI?

thank you!

I found your product via some mentions on the resin.os gitter chat. Am I guessing correctly that you abandoned resin.os and are now using buildroot instead?

The reason I ask is I'm trying to do something similar to what you were - I'm trying to run my own supervisor on a resin image and was hoping that you had some insight.

Any information you could provide would be helpful!

I was able to get the VMDK to boot on Proxmox. Is this an ok place to document how?

The working hardware config in my HASSOS vm is as below.

Hard Disk ide0 vm-100-disk-2.vmdk is the hassos vmdk just renamed.

Working on getting the Odroid-C2 working. (Will fork and post a pull request once I get everything working and tidied-up)

Seems I've gotten most of the "difficult" items worked out, but the docker instances seem not to play nice with the network interfaces? I can't see HomeAssistant on :8123, and I get:

hassio > ha info
The HTTP request failed with the error: Get http://hassio/homeassistant/info: dial tcp 172.30.32.2:80: getsockopt: connection refused

When I try to run any hassio commands.
Network is up (can ping into/out of and ssh into busybox).

Any thoughts?

VMware ESXi 6.5. Could not use the vmdk file so someone running the same version of ESXi who did not have this problem sent me an OVF/OVA export. This also would not import to ESXi so I loaded it in VMware Fusion and it worked. Then I exported that to an OVA and it DID import into ESXi. Worked fine but upon reboot Autoboot doesn't work and either Boot System 0 or Boot System 1 needs to be manually selected. This remains until now.

System 0 is 1.2 and System 1 is 1.3 as one time the Update button in the Host system panel successfully upgraded (through I needed to choose the OTHER Boot System than that I was currently booted into for it to start).

Now that 1.4 is available I can try to update from either the 1.2 or 1.3 version but it doesn't work either time. I have the following to provide as clues.

The Hass.io system log:

18-07-10 12:05:22 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
18-07-10 12:05:22 INFO (MainThread) [hassio.core] Hass.io is up and running
18-07-10 12:07:19 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/1.4/hassos_ova-1.4.raucb
18-07-10 12:09:14 INFO (MainThread) [hassio.hassos] OTA update is downloaded on /data/tmp/hassos-1.4.raucb
18-07-10 12:09:14 INFO (MainThread) [hassio.utils.gdbus] Call de.pengutronix.rauc.Installer.Install on /
18-07-10 12:09:14 INFO (MainThread) [hassio.utils.gdbus] Start dbus monitor on de.pengutronix.rauc

The home-assistant.log:

2018-07-10 22:05:06 WARNING (MainThread) [homeassistant.config] Incomplete core configuration. Auto detected elevation: 0
2018-07-10 22:05:08 WARNING (MainThread) [homeassistant.components.http] You have been advised to set http.api_password.
2018-07-10 22:12:20 ERROR (MainThread) [homeassistant.components.hassio.http] Client timeout error on API request hassos/u
pdate

And this:

The IMPORT FROM USB option did not work for either the update or authorized_keys as far as I could tell. But that's a secondary issue for me at the moment. I'd just like to figure out why OTA updates aren't working and why Autoboot isn't working.

An explanation of how the update process and the dual booting functions would be helpful to understanding how things SHOULD work.

Thanks in advance. I'm sure I missed some things but will be happy to provide any further information to help fix these problems.

Regards,
Michal

In progress

Tasks Supervisor

• dbus support
• Host config support over dbus

Tasks CLI

• Make a real CLI docker image

Tasks OS

• Cleanup filesystem
• Fix barebox state access
• Make a nice barebox menu
• Update OS/Version data
• Automatic Rauc OTA updates

Supported Hardware on beta release

• OVF/OVA
• Raspberry Pi
• Raspberry Pi 2
• Raspberry Pi 3/+

Supported Hardware on stable release (Need hardware donation)

• Orange Pi
• Pine
• Rock64

Hi Pvizeli!

As described on the original Hass.IO installation site's Z-Wave section the RazBerry board requires the same UART channel as BT is using on the Pi 3 to function. https://www.home-assistant.io/hassio/zwave/
The ResinOS based Hass.IO was utilizing the config.txt file, but the newer version of the system based on Buildroot does not or maybe it is just not that easy to figure out how to change the settings.

After some digging, assuming that I understand correctly what's happening in the image building process I found that based on the readme here: https://github.com/home-assistant/hassos/tree/dev/buildroot/board/raspberrypi
the UART is actually used by Buildroot to provide a console interface (see remark #2). This would mean that the ReZberry's communication channel is blocked.

Do you think that this could be the reason for what the users are describing in this topic: https://community.home-assistant.io/t/razberry-and-hassos/60283

Unfortunately I'm not an expert of the new system. But would it be possible to disable the console that is opened by default? Do you think that the BT is disabled on the PI 3s?

Regards:
Botond

With HassOS 1.2 release I'm able to deploy authorized_keys file with USB to HassOS. After reboot SSH accepts basic connection but denies key authentication after typing username "root". I use PuTTY. The authorized_keys file is correctly formatted. With the same authorized_keys file on another Linux machine it is working, so it seems there is still some error.
I tried twice even with generating new Pubkey/Privkey.

I have installed the addon Bluetooth BCM43xx, but the devices dont report.

Raspberry PI3B

The log of the add-on:

bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set BDADDR UART: b8:27:eb:60:46:d0
Set Controller UART speed to 921600 bit/s
Device setup complete

I have https://www.home-assistant.io/components/sensor.mitemp_bt/ and https://www.home-assistant.io/components/sensor.miflora/

Was trying to figure this out myself, but thought I would submit an issue for this. I have HassOS running under unraid. The USB device is passed through to the guest and HassOS appear to recognize it.

I know this usb stick worked on a previous installed of Hass.io, so I don't think its an issue with the USB stick or unraid server.

The device appears to be /dev/ttyS0 (as a previous issue mentioned) and the device appears to be recognized. Reviewing dmesg shows the only USB device as /dev/ttyS0, however I see the following errors under Configuration | Z-wave | OZW Logs:

2018-07-20 18:30:07.792 Always, OpenZwave Version 1.4.2926 Starting Up
2018-07-20 18:30:20.698 Info, Setting Up Provided Network Key for Secure Communications
2018-07-20 18:30:20.700 Info, mgr,     Added driver for controller /dev/ttyS0
2018-07-20 18:30:20.700 Info,   Opening controller /dev/ttyS0
2018-07-20 18:30:20.700 Info, Trying to open serial port /dev/ttyS0 (attempt 1)
2018-07-20 18:30:20.701 Info, Serial port /dev/ttyS0 opened (attempt 1)
2018-07-20 18:30:20.702 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-07-20 18:30:20.702 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-07-20 18:30:20.702 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-07-20 18:30:20.702 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-07-20 18:30:20.702 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-07-20 18:30:20.702 Detail,
2018-07-20 18:30:20.702 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-07-20 18:30:21.704 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-07-20 18:30:21.705 Detail, contrlr, Removing current message
2018-07-20 18:30:21.706 Detail, contrlr, Notification: Notification - TimeOut
2018-07-20 18:30:21.734 Detail,
2018-07-20 18:30:21.734 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-07-20 18:30:22.736 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-07-20 18:30:22.736 Detail, contrlr, Removing current message
2018-07-20 18:30:22.736 Detail, contrlr, Notification: Notification - TimeOut
2018-07-20 18:30:22.738 Detail,
2018-07-20 18:30:22.738 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-07-20 18:30:23.740 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-07-20 18:30:23.740 Detail, contrlr, Removing current message
2018-07-20 18:30:23.740 Detail, contrlr, Notification: Notification - TimeOut
2018-07-20 18:30:23.780 Detail,
2018-07-20 18:30:23.780 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-07-20 18:30:24.781 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-07-20 18:30:24.781 Detail, contrlr, Removing current message
2018-07-20 18:30:24.781 Detail, contrlr, Notification: Notification - TimeOut
2018-07-20 18:30:24.787 Detail,
2018-07-20 18:30:24.787 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-07-20 18:30:25.788 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-07-20 18:30:25.788 Detail, contrlr, Removing current message
2018-07-20 18:30:25.788 Detail, contrlr, Notification: Notification - TimeOut

After a few minutes following a reload, the following message is shown:

Log Details (WARNING)
Fri Jul 20 2018 22:00:56 GMT-0400 (Eastern Daylight Time)

Z-Wave not ready after 300 seconds, continuing anyway

Additionally, when trying to send an 'add node' command, I see the following error in the Home Assistant logs:

Log Details (ERROR)
Fri Jul 20 2018 18:40:04 GMT-0400 (Eastern Daylight Time)

Error executing service <ServiceCall zwave.add_node>

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1046, in _event_to_service_call
    await self._hass.async_add_job(execute_service)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1043, in execute_service
    service_handler.func(service_call)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/zwave/__init__.py", line 360, in add_node
    network.controller.add_node()
  File "/usr/local/lib/python3.6/site-packages/openzwave/controller.py", line 692, in add_node
    return self._network.manager.addNode(self.home_id, doSecurity)
  File "src-lib/libopenzwave/libopenzwave.pyx", line 4283, in libopenzwave.PyManager.addNode
TypeError: an integer is required

I'm not sure where the issue is at this point, so any help would be appreciated.

I'm on HassOS 1.1 and I can not bring dev SSH up. I tried both with FAT32 and with EXT4 USB stick and both variants with label "CONFIG" and with label "config" (because of bug with lowercase label). My authorized_keys file is in the root dir and after trying several variants and each time "Import from USB" via Hassio panel and reboots of my RPi I give up now. It seems not to work. SSH on port 22222 always says "connection refused".

home-assistant.log gives no errors.