Why doesn't SkyConnect show up in HA? (HA Green)

Hello,

I’m taking my first steps into home automation and in the hope of making my life easier have just become the proud owner of a Home Assistant Green and a SkyConnect dongle.

I’ve connected the HA Green to my router via ethernet and am now all set up with the HA application running in my browser and connecting to the Green. However, when I plug the SkyConnect into either of the USB sockets on the Green (using the supplied USB extension cable), nothing shows up in the HA application in my browser under devices.

I’ve followed the troubleshooting advice of:

  1. Waiting a while (I’m not sure how long is meant by this, but I’ve waited at least half an hour between plugging in attempts).
  2. Clicking on ‘show ignored installations’
  3. Refreshing the browser

The only thing I can think that I might have done to hinder this process is I did originally try plugging the SkyConnect into my laptop to connect it to a virtual machine that I was testing out HA with, but I gave up on that because I couldn’t get it to connect there!

Is there any way I can confirm that the SkyConnect is not dud or that I have not somehow broken it?

Any advice very welcome. Thanks!

Check under UI->Settings->Hardware->All Hardware and see if there is a /dev/ttyUSBx. If you don’t see anything (and this is the only stick plugged in), then yeah it might be a dud. However if there is something there, but nothing indicates its a SkyConnect or from Nabu Casa, we are finding that some of the latest batches of SkyConnects are not programmed with the proper USB IDs, and this keeps HA from auto-discovering the SkyConnect.

1 Like

I’ve found the following under Settings>System>Hardware. The “Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller” is the same device name I see when plugging the SkyConnect into my laptop, so I think it could be related. I’m not sure why HA isn’t detecting it as a SkyConnect integration/device though. I’m not sure if anyone can read anything into this from the HA hardware log.

Thanks

ttyUSB0
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_38005d521cb7ed11adc3975938a92db5-if00-port0
Subsystem:
tty
Device path:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_38005d521cb7ed11adc3975938a92db5-if00-port0
Attributes:
DEVLINKS: >-

  • /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_38005d521cb7ed11adc3975938a92db5-if00-port0*
  • /dev/serial/by-path/platform-fd840000.usb-usb-0:1:1.0-port0*
    DEVNAME: /dev/ttyUSB0
    DEVPATH: /devices/platform/fd840000.usb/usb5/5-1/5-1:1.0/ttyUSB0/tty/ttyUSB0
    ID_BUS: usb
    ID_MODEL: CP2102N_USB_to_UART_Bridge_Controller
    ID_MODEL_ENC: CP2102N\x20USB\x20to\x20UART\x20Bridge\x20Controller
    ID_MODEL_ID: ea60
    ID_PATH: platform-fd840000.usb-usb-0:1:1.0
    ID_PATH_TAG: platform-fd840000_usb-usb-0_1_1_0
    ID_REVISION: ‘0100’
    ID_SERIAL: >-
  • Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_38005d521cb7ed11adc3975938a92db5*
    ID_SERIAL_SHORT: 38005d521cb7ed11adc3975938a92db5
    ID_TYPE: generic
    ID_USB_DRIVER: cp210x
    ID_USB_INTERFACES: ‘:ff0000:’
    ID_USB_INTERFACE_NUM: ‘00’
    ID_USB_MODEL: CP2102N_USB_to_UART_Bridge_Controller
    ID_USB_MODEL_ENC: CP2102N\x20USB\x20to\x20UART\x20Bridge\x20Controller
    ID_USB_MODEL_ID: ea60
    ID_USB_REVISION: ‘0100’
    ID_USB_SERIAL: >-
  • Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_38005d521cb7ed11adc3975938a92db5*
    ID_USB_SERIAL_SHORT: 38005d521cb7ed11adc3975938a92db5
    ID_USB_TYPE: generic
    ID_USB_VENDOR: Silicon_Labs
    ID_USB_VENDOR_ENC: Silicon\x20Labs
    ID_USB_VENDOR_ID: 10c4
    ID_VENDOR: Silicon_Labs
    ID_VENDOR_ENC: Silicon\x20Labs
    ID_VENDOR_ID: 10c4
    MAJOR: ‘188’
    MINOR: ‘0’
    SUBSYSTEM: tty
    TAGS: ‘:systemd:’
    USEC_INITIALIZED: ‘760908764’

You beat me to it! Thanks for your reply, @wmaker . I have just discovered the ttyUSB in the area you mentioned (I have posted the accompanying text).

Is there a known fix to do get around it not autodiscovering?

Looks like it is one of those that didn’t get programmed properly with SkyConnect/NabuCasa USB IDs.
I don’t know of a work-around for the auto-discovery, but if you are using it only for ZHA, then it should still work fine. If you are going to use it with HA Thread, then the HA Add-ONs for Thread won’t recoginize it and reflash it. You should probably contact the seller you got it from and let them know of the problem.

1 Like

I see.

My immediate plans are just ZHA but I’d rather be future proofed. Do you know if the problem is with whole batches of SkyConnects or more random? (I’m wondering if I get a replacement from the same seller if it’s likely to have the same problem).

Thanks again.

I’ve seen 4 reports on this Forum just in the last couple of days from newly purchased SkyConnects, so my guess is yes, your replacement will likely have the same issue.

1 Like

Looks like now there is a work-around. See the following:

1 Like

this solution worked for me on a rpi4 with HA installed. tnx