Z-wave config files for Inovelli LZW60 with Home Assistant docker

[firstof9]

I just verified from my docker compose:

  homeassistant:
    container_name: home-assistant
    restart: unless-stopped
    image: homeassistant/home-assistant:beta
    depends_on:
      - "mariadb"
    volumes:
      - /home/docker/home-assistant:/config
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/localtime:/etc/localtime:ro
    network_mode: host
    privileged: true

-v /etc/localtime:/etc/localtime:ro should work

[dbrunt (Daniel)]

I used this link to install hass and I have a systemd service:

[Unit]
Description=Hass.io supervisor
Requires=docker.service
After=docker.service dbus.socket

[Service]
Type=simple
Restart=always
RestartSec=5s
ExecStartPre=-/usr/bin/docker stop hassio_supervisor
ExecStart=/usr/sbin/hassio-supervisor
ExecStop=-/usr/bin/docker stop hassio_supervisor

[Install]
WantedBy=multi-user.target

/usr/sbin/hassio.supervisor:

#!/usr/bin/env bash
set -e

# Load configs
CONFIG_FILE=/etc/hassio.json

SUPERVISOR="$(jq --raw-output '.supervisor' ${CONFIG_FILE})"
HOMEASSISTANT="$(jq --raw-output '.homeassistant' ${CONFIG_FILE})"
DATA="$(jq --raw-output '.data // "/usr/share/hassio"' ${CONFIG_FILE})"

# AppArmor Support
if command -v apparmor_parser > /dev/null 2>&1 && grep hassio-supervisor /sys/kernel/security/apparmor/profiles > /dev/null 2>&1; then
    APPARMOR="--security-opt apparmor=hassio-supervisor"
else
    APPARMOR="--security-opt apparmor:unconfined"
fi

# Init supervisor
HASSIO_DATA=${DATA}
HASSIO_IMAGE_ID=$(docker inspect --format='{{.Id}}' "${SUPERVISOR}")
HASSIO_CONTAINER_ID=$(docker inspect --format='{{.Image}}' hassio_supervisor || echo "")

runSupervisor() {
    docker rm --force hassio_supervisor || true

    # shellcheck disable=SC2086
    docker run --name hassio_supervisor \
        --privileged \
        $APPARMOR \
        --security-opt seccomp=unconfined \
        -v /run/docker.sock:/run/docker.sock \
        -v /run/dbus:/run/dbus \
        -v "${HASSIO_DATA}":/data \
        -e TZ=America/Vancouver \
        -e SUPERVISOR_SHARE="${HASSIO_DATA}" \
        -e SUPERVISOR_NAME=hassio_supervisor \
        -e HOMEASSISTANT_REPOSITORY="${HOMEASSISTANT}" \
        "${SUPERVISOR}"
}
# Run supervisor
mkdir -p "${HASSIO_DATA}"
([ "${HASSIO_IMAGE_ID}" = "${HASSIO_CONTAINER_ID}" ] && docker start --attach hassio_supervisor) || runSupervisor
root@hassio:~# 

but there’s no TZ variable set inside the container:

.
.
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=1
SUPERVISOR_NAME=hassio_supervisor
SUPERVISOR_SHARE=/usr/share/hassio
TERM=xterm
UID=0
_=bash
bash-5.0# 

The ‘cat … > /etc/localtime’ is sticking so I’m good.

[dbrunt (Daniel)]

Matt,

As I’m sure you’re aware, but for the benefit of other readers who might see this, you need:

Supervisor, Add-on: Mosquitto Broker
Configuration, Integration: MQTT Mosquitto Broker
Configuration, Integration: OpenZWave (beta)
and one piece left…
either

1. Supervisor, Add-on: OpenZWave (which lags behind the latest OpenZWave 1.6)
   or
2. Your own docker container with OpenZwave 1.6

I’m not sure if you can go option 1 and somehow upgrade it to openzwave:latest or not…

[mattmoo]

I’m not particularly aware haha.

So if I perform those steps, my Zwave devices will appear to HA as MQTT devices?

[dbrunt (Daniel)]

No, they appear as OpenZWave devices. MQTT is the middleman between the OpenZWave 1.6 (add-on/separate docker container) and the OpenZWave (beta) integration.

[mattmoo]

Very interesting, maybe I’m getting closer to comprehension.

I have been using the Zwave integration, maybe I should be trying to use this Openzwave beta integration

[dbrunt (Daniel)]

It is the way of the future…