#SkyConnect not showing up on x86-64
1 messages ยท Page 1 of 1 (latest)
thanks, I should have started with that
HP 640 laptop, generic x86_64
If you have access to a shell, that'll make things easier. Run dmesg before plugging in the SkyConnect, make sure to do nothing else, then plug it in. Run dmesg again and see what changed.
version: '2.4'
services:
zigbee2mqtt:
container_name: zigbee2mqtt
restart: unless-stopped
image: koenkk/zigbee2mqtt
volumes:
- ./data:/app/data
- /run/udev:/run/udev:ro
ports:
- 8080:8080
environment:
- TZ=America/Chicago
devices:
- /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_xxxxxxxxxxxxxxxxxxxxxxxxxx-if00-port0:/dev/ttyUSB0```
is how I got mine to work, I still need to go rootless and fix the perms
When I plug mine in on a Yellow, it's seen by the kernel:
[3215374.757927] usb 1-1.2: new full-speed USB device number 15 using dwc2
[3215374.980676] usb 1-1.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[3215374.980712] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3215374.980729] usb 1-1.2: Product: SkyConnect v1.0
[3215374.980744] usb 1-1.2: Manufacturer: Nabu Casa
[3215374.980767] usb 1-1.2: SerialNumber: dad77e39c414ed11ad79bc8be054580b
[3215375.009693] usbcore: registered new interface driver cp210x
[3215375.009792] usbserial: USB Serial support registered for cp210x
[3215375.010168] cp210x 1-1.2:1.0: cp210x converter detected
[3215375.012797] usb 1-1.2: cp210x converter now attached to ttyUSB0
checking
zha or z2m?
The original issue was that it wasn't being seen by HA, so no Zigbee integration yet ๐
oh lol me and fedora IoT ๐
so its seeing a usbACM0 device
Can you post the last chunk of dmesg output? It should look similar.
I can't seem to get a copy from the cmd from within HA web
let me see if I can putty
A screenshot is fine
I don't have rights to post a screenshot
A link to one works too ๐
I'm not seeing anything in the log about a device connecting
hmm
that is so strange
let me check it again, because its in the USB port
and as far as I know, its a working port, un-used up until this point
You can run dmesg -c to fully clear output
So if it helps, run that first, then do something
one sec, home assistant is in my master closet with my server and network gear, let me unplug and try that
cp210 converter?
That's the USB to serial chip it's using, yes
But you should see SkyConnect v1.0 and such in the log as well
Since Windows was able to read it
Looks like a serial port is created as well
It should be auto-detected and show up in the integrations page as a suggestion
third screenshot
Third one looks fine to me, it ends with the port being detected
These logs can be from hours or days ago
DEVLINKS: >-
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_fa1c4a14a718ec118dabe99a47486eb0-if00-port0
/dev/serial/by-path/pci-0000:00:10.0-usb-0:2:1.0-port0
DEVNAME: /dev/ttyUSB1
DEVPATH: /devices/pci0000:00/0000:00:10.0/usb6/6-2/6-2:1.0/ttyUSB1/tty/ttyUSB1
ID_BUS: usb
ID_MODEL: SkyConnect_v1.0
ID_MODEL_ENC: SkyConnect\x20v1.0
ID_MODEL_ID: ea60
ID_PATH: pci-0000:00:10.0-usb-0:2:1.0
ID_PATH_TAG: pci-0000_00_10_0-usb-0_2_1_0
ID_REVISION: '0100'
ID_SERIAL: Nabu_Casa_SkyConnect_v1.0_fa1c4a14a718ec118dabe99a47486eb0
ID_SERIAL_SHORT: fa1c4a14a718ec118dabe99a47486eb0
ID_TYPE: generic
ID_USB_DRIVER: cp210x
ID_USB_INTERFACES: ':ff0000:'
ID_USB_INTERFACE_NUM: '00'
ID_VENDOR: Nabu_Casa
ID_VENDOR_ENC: Nabu\x20Casa
ID_VENDOR_ID: 10c4
MAJOR: '188'
MINOR: '1'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2782440895251'
so I see it under hardware now
but nothing under integrations
and the OS and Core are fully updated
to the normal stable
So if it's seen by the kernel and shows up as a serial port, it should be showing up in integrations as a suggestion
Try rebooting the host computer fully?
You can also manually try setting up ZHA (Zigbee Home Automation)
It should just ask you to choose that serial port, auto connect, then ask you to either restore a backup or to form a new network
let me give that a try after a reboot
it hasn't have a full restart in a while
funny, this is the firs problem I have had with it with the 2 years ive been tinkering
appreciate the insight and help
No worries. There should be nothing special about the SkyConnect in this regard, it's just a USB device with a (very common) serial chip
still nothing under the intergration screen but I see the Home Assistant Sky Connect (Configure) under Hardware
which is disabled
Try configuring ZHA, it should show up as a serial port you can select
so I am trying to migrate radio, I see it it there when I delete the sonoff but then it fails on setup
do I need to comptely delete the sonoff first?
then setup?
Ah
So if you already have ZHA enabled, it won't show up as anything other than a serial port
oh
Since only one instance of ZHA can be configured
even through its going to be thread/matter?
ZHA won't care/know about that half
No, the migration should still be working fine
it errors
If you have the Sonoff plugged in, you should be able to click "Migrate", select the migration option (which resets the Sonoff), then it will ask to select the new stick
probably need to document all these steps and post on the git
gets to the ttyUSB1, but the vendor and other info is ""
That doesn't sound right
doesn't seem to fully see the device and fails when I try to switch the radio
I do appreciate the help, going to have to pause on troubleshooting, need to get the kido to bed, will revisit later / tomorrow, flagged this so I can follow up, really really appreciate the time with this
its not critical, just something new to play with
No worries, something definitely weird is going on. For comparison, here's what I'm seeing with my SkyConnect: https://i.imgur.com/Tbd7CMp.png
I get the USB1 - s/n: ''
I'll get that documented on a screen, might post for the home assistant git for issues
Yet ls -l /dev/serial-by-id/ shows the SkyConnect serial port link when you re-run it? (I'm treating this thread as something asynchronous so feel free to respond whenever you have time)
after more troubleshooting, but the baby needs dad to put him down, back in a bit, again, thank you for the help!
no such file or dir
Oh, whoops, should be /dev/serial/by-id/