#hi I have a an existing HA installation

1 messages · Page 1 of 1 (latest)

tardy dove
#

any suggestions on what to try or how to troubleshoot? I've not found much in the way of troubleshooting guides for skyconnect...

languid atlas
#

what does your compose file look like

tardy dove
#

not using compose for the docker container, it's launched like this:

#

I have a significant number of z-wave devices on a z-wave network using another usb stick (zooz 800)

#

(if that matters)

#

I'm hoping to get just basic information like 'skyconnect uses this device in linux' or 'run this command to see if skyconnect is installed properly at the OS level'

languid atlas
#

you need to pass it to the container

tardy dove
#

ah ok that makes sense. how do I do that?

#

something like --device=/dev/ttyUSB0?

languid atlas
#

using /dev/serial/by-id/ is better because it's consistent

tardy dove
#

yah just found the device under /dev/serial/by-id, thanks. That at least gives me some confidence that the USB stick is working properly. I'll try adding the argument to the container and if that fixes it up. Thanks!

full tundra
#

So you passed the USB device to the container but it didn't work?

tardy dove
#

y seems not to work, there was no discovery in HA

#

revised launch command:

    -v /etc/localtime:/etc/localtime:ro   \
    -v /opt/homeassistant:/config \
    -v /etc/letsencrypt:/etc/letsencrypt \
    --device /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_2cf16a01327ded11bb77b96c4fc49859-if00-port0 \
    --network host ghcr.io/home-assistant/home-assistant:stable
#

rats looks like bad command; no '='

languid atlas
#

--device=

tardy dove
#

yep restarting now will give it another try

#

still no joy, nothing discovered.

#

If I manually add the ZHA integration, it fails with "Unknown Error"

full tundra
#

It's a mapping command, just like with volumes. Try something like.

--device=/dev/serial/by-id/and so on:/dev/zigbee
tardy dove
#

ah so I need to add the :/dev/zigbee will do.

full tundra
#

Yeah you have to give Docker a path to map it to inside the container.

tardy dove
#

😦

#
    --restart=unless-stopped   \
    -v /etc/localtime:/etc/localtime:ro   \
    -v /opt/homeassistant:/config \
    -v /etc/letsencrypt:/etc/letsencrypt \
    --device=/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_2cf16a01327ded11bb77b96c4fc49859-if00-port0:/dev/zigbee \
    --network host ghcr.io/home-assistant/home-assistant:stable```
#

but no discovery. Manual add of ZHA fails with "unknown error". I must be missing something...

languid atlas
#

is there a reason you aren't using compose and a newer version of home assistant

tardy dove
#

no good reason for not upgrading to compose, I do use it for another container on the same instance. When I first installed HA I didn't know much about Docker

#

as for HA, it's the stable version and about a 2 months old. Should that be a problem?

languid atlas
#

compose makes testing changes so much easier

#

HA moves fast

tardy dove
#

what's a better version to run?

languid atlas
#

latest which is 2023.6.3

tardy dove
#

ok, let me give that a shot. ty

languid atlas
#

if that doesn't work, you can open the terminal inside the container and check if the usb device is there

tardy dove
#

is there a command I can send it to verify it's working from inside the container?

#

cat some message into /dev/zigbee, maybe?

languid atlas
#

docker exec -it homeassistant bash

#

ls /dev

tardy dove
#

y, I did that and /dev/zigbee is present

#

let me try the image upgrade

#

ok, now running 2023.6.3. Device is mapped inside the container:

CONTAINER ID   IMAGE                                          COMMAND                  CREATED         STATUS         PORTS                                       NAMES
2c9bd7bcc8d6   ghcr.io/home-assistant/home-assistant:stable   "/init"                  3 minutes ago   Up 3 minutes                                               homeassistant
326fd5bff68b   ghcr.io/kpine/zwave-js-server:latest           "/sbin/tini -- docke…"   3 weeks ago     Up 12 hours    0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   zjs
root@apacheland:/opt/homeassistant# docker exec -it 2c9bd7bcc8d6 ls /dev/
core     full     null     pts      shm      stdin    tty      zero
fd       mqueue   ptmx     random   stderr   stdout   urandom  zigbee
#

going to reboot the system, see if that helps...

#

no change after reboot. I'm stumped...

languid atlas
#

hmm

#

you could try running the container in privledged mode

#

other than that I don't have any ideas

full tundra
#

Or try running the container as root

tardy dove
#

my docker container is old, going to upgrade that next

#

rather my docker runtime I mean

tardy dove
#

update: stack is all up to date; Ubuntu 22.04.2, Docker CE 24.02, HA 2023.6.3

#

still no discovery of the SkyConnect stick

#

are there any kind of diagnostics for SkyConnect or ZHA to indicate why it's not working?

tardy dove
#

ok, so I finally got it to work but I'm in privileged mode. Not what I want long-term; is it a simple problem of '/dev/zigbee' needing a 'chmod'?

#

@full tundra you were right...