The problem

When attempting to flash a SkyConnect via the WebSerial updater, the following is seen in browser JS console. It seems that the ssl library needs to be manually installed, as it's not bundled with pyodide.

pyodide.asm.js:10 Uncaught (in promise) PythonError: Traceback (most recent call last):
  File "/lib/python3.10/_pyodide/_base.py", line 460, in eval_code
    .run(globals, locals)
  File "/lib/python3.10/_pyodide/_base.py", line 304, in run
    coroutine = eval(self.code, globals, locals)
  File "<exec>", line 2, in <module>
  File "/lib/python3.10/site-packages/universal_silabs_flasher/flasher.py", line 15, in <module>
    from .gbl import GBLImage
  File "/lib/python3.10/site-packages/universal_silabs_flasher/gbl.py", line 8, in <module>
    from zigpy.ota.validators import parse_silabs_gbl
  File "/lib/python3.10/site-packages/zigpy/ota/__init__.py", line 23, in <module>
    import zigpy.ota.provider
  File "/lib/python3.10/site-packages/zigpy/ota/provider.py", line 14, in <module>
    import ssl
ModuleNotFoundError: The module 'ssl' is unvendored from the Python standard library in the Pyodide distribution.
You can install it by calling:
  await micropip.install("ssl") in Python, or
  await pyodide.loadPackage("ssl") in JavaScript
See https://pyodide.org/en/stable/usage/loading-packages.html for more details.

    at new_error (pyodide.asm.js:10:179954)
    at pyodide.asm.wasm:0xe78a8
    at pyodide.asm.wasm:0xe79ad
    at Module._pythonexc2js (pyodide.asm.js:10:928566)
    at Module.callPyObjectKwargs (pyodide.asm.js:10:123572)
    at Module.callPyObject (pyodide.asm.js:10:123781)
    at Function.apply (pyodide.asm.js:10:134751)
    at Object.apply (pyodide.asm.js:10:133745)
    at Object.runPython (pyodide.asm.js:10:161550)
    at Ne.onPyodideLoaded (flashing-dialog-a8f5f5ab.js?module:281:970)
    at Ne.selectSerialPort (flashing-dialog-a8f5f5ab.js?module:281:552)

This causes the updater to hang at the Connecting... This can take a few seconds. step.

Using Chrome 120.0.6099.71 on Linux x86_64.

Link to the page

https://skyconnect.home-assistant.io/firmware-update/

requested by NanoWireDnB

see #3

Hey guys!
I'm experiencing a very annoying error with the SkyConnect setup wizard:
I will describe what happened and get to the point. I updated the system to the new version and managed to update the SkyConnect FW as well.
It worked perfectly with MultiPan FW. Unfortunately, due to another system error, the Home Assistant did not start again and could not be repaired.
That's why I restored the previous save and then also updated it to the new version.
This is where the problems started: The system recognized SkyConnect, but the new device says SkyConnect v1.0, even though MultiPan FW is already installed on it.
Unfortunately, the configuration fails, it always runs into an error. It shows the USB path well, but cannot set it.

(I think the problem is that the configuration process does not know MultiPan FW SkyConnect)

The image shows "Failed to scan USB device"

Unfortunately, my entire ZigBee network is unusable, luckily I have a backup of it, but the device cannot be configured.

What can I do? Thanks in advance for answers!

After updating, setup error arised. deleted skyconnect integration, tried to reinstall other error showed up

First error:

2023-01-20 13:09:20.053 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SkyConnect v1.0 for zha
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 111, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 189, in async_initialize
raise exc
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 169, in new
await app.startup(auto_form=auto_form)
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 104, in initialize
await ezsp._startup_reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 95, in _startup_reset
await self.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 124, in reset
await self._gw.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 251, in reset
return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

after restart of HA, skyconnect found, but could not complete installation.

Error:
Kon het USB apparaat niet onderzoeken
Could not investigate the usb device

Could not find a specific log entry for this generated error.

SkyConnect requires a hard reset (unplugging the dongle, and replugging) after adding some devices. This has happened with devices from various manufactureres including Sonoff, Sengled and Innr. This is an intermittent issue, so it doesn't occur everytime a new device is added.

Reloading the ZHA integration fails, and the logs show the following error:

Logger: homeassistant.config_entries
Source: components/zha/core/gateway.py:205
First occurred: 6:00:20 PM (1 occurrences)
Last logged: 6:00:20 PM

Error setting up entry SkyConnect v1.0 for zha
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
    return fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 122, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 220, in async_initialize
    raise exc
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 205, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 191, in new
    await app.startup(auto_form=auto_form)
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 165, in startup
    await self.connect()
  File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 125, in connect
    self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
  File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 106, in initialize
    await ezsp._startup_reset()
  File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 97, in _startup_reset
    await self.reset()
  File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 126, in reset
    await self._gw.reset()
  File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 260, in reset
    return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

First let me tell you what a wonderful program Home Assistent is and I am using it many years.
I have installed SkyConnect and ZHA paired the Aqara Smart Plugs but some don't give any power measurements.
If I connect the Smart Plugs without power measurements to a system with ZHA and Conbee II the power measurement is working.
This is my first issue I reported, so if you need more information then please let me know?

Best regards,
Iwan Celissen

Please add support for containerized installations of Home Assistant.

My apologies if I missed this, but I couldn't find any mention in the documentation or pull requests of support for containerized installations of Home Assistant. I also didn't see any open issues.

Thanks!

Feedback

Please provide full SkyConnect Documentation on

• technical specs,
• datasheet,
• setup with HA core (addon->configuration->integration->adding devices),
• settings

and of course FAQ relating especially to

• features,
• information on running two ZigBee radios simultaneously, (for legacy support, offloading or migration)
• compatibility with addons/integrations,
• migration from other ZigBee radios/gateways/controllers (Conbee/deconz, Sonoff, ZHA, Zigbee2MQTT etc.),
• status of matter/thread support
• and so on.

Maybe you can also share experimental/alpha/beta firmware for those who want to test out thread/matter.

Thanks in advance.

URL

https://skyconnect.home-assistant.io/
https://www.home-assistant.io/skyconnect/
https://www.home-assistant.io/integrations/homeassistant_sky_connect/
https://www.home-assistant.io/integrations/homeassistant_hardware/

Version

No response

Additional information

https://community.home-assistant.io/t/skyconnect-setup-with-ha-os-missing-official-documentation/502849

I have connected the SkyConnect to my Mac, opened the site via Google Chrome.
The SkyConnect is recognized, but the current firmware could not be read out.

Logs

2023-02-08 21:18:21 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-02-08 21:18:21 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x13d8010>
2023-02-08 21:18:21 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'3'
2023-02-08 21:18:23 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC
2023-02-08 21:18:23 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1756608>
2023-02-08 21:18:23 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-02-08 21:18:23 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-02-08 21:18:24 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2023-02-08 21:18:24 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-02-08 21:18:24 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-02-08 21:18:25 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2023-02-08 21:18:25 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-02-08 21:18:25 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-02-08 21:18:26 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2023-02-08 21:18:26 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-02-08 21:18:26 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-02-08 21:18:27 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2023-02-08 21:18:27 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.EZSP
2023-02-08 21:18:27 emscripten bellows.ezsp[42] DEBUG Resetting EZSP
2023-02-08 21:18:27 emscripten bellows.uart[42] DEBUG Resetting ASH
2023-02-08 21:18:27 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e'
2023-02-08 21:18:32 emscripten bellows.uart[42] DEBUG Connection lost: None
2023-02-08 21:18:32 emscripten bellows.uart[42] DEBUG Closed serial connection

I received a repair warning that the zigbee and thread channels were different. However, the repair warning is wrong.

It states my thread channel is 25 and ZHA is 15, but it is actually the reverse. My ZHA is channel 25 and Thread is 15 (see images below).

However, the instructions to fix a channel mismatch given herehttps://skyconnect.home-assistant.io/about-multiprotocol/#resolve-channel-conflict do not work either. I have tried Option 2 in that document, because I want my Thread channel to match my Zigbee channel but when I reset my Thread nothing happens, the channel stays at 15. Have also tried restarting after reset.

Repair Notification

ZHA

Thread (before and after reset)

Hi, when I initially configured my SkyConnect devices, it was on /dev/ttyUSB2 in my docker container and the setup went fine and everything worked. However, since I am using three USB devices in HA and in order to keep the mapping stable, I needed to map the host OS USB ports via /dev/serial/by-id/ links and compose.yaml into the docker container, which in my case looks like this:

    devices:                                                                                                                                                                                  
        - "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0KTQ80-if00-port0:/dev/ttyUSB_XCom485i"
        - "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AQ00K6WL-if00-port0:/dev/ttyUSB_RS485"
        - "/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ae94a629d960ed119dcdcde05720eef3-if00-port0:/dev/ttyUSB_SkyConnect"

In the docker container I then see the following USB devices:

The mapping is stable and works fine for the other two USB devices, where the USB port configuration in HA is in clear text in some config files and I just use /dev/ttyUSB_RS485 and /dev/ttyUSB_XCom485i. However, for SkyConnect, I had to use "Migrate Radio" to change the USB port setting. Which I did here:

This worked and ZigBee worked fine afterwards and also /dev/ttyUSB_SkyConnect showed up in the SkyConnect configuration settings in HA.

However, unfortunately the new setting to /dev/USB_SkyConnect does not persist after a reboot! After a reboot, the SkyConnect configuration still seems to assume /dev/ttyUSB2 (which was the USB port with which it was originally set up and configured). But if after a reboot USB2 on the host OS happens to be assigned to one of the other two USB devices, SkyConnect interferes with those devices and HA won’t start and I have to reboot until USB2 in the host OS happens to be mapped to the SkyConnect device. Then HA starts again, but instead of /dev/ttyUSB_SkyConnect, /dev/ttyUSB2 shows up in the SkyConnect configuration settings in HA. I can then again use "Migrate Radio" to change this to /dev/ttyUSB_SkyConnect and again everything works fine afterwards, but again that setting does not persist after a reboot…

This seems like a bug? It would be great if anyone could look into this? Thanks much!

P.S. More context here.

Is there an official number of devices this dongle can support? I'm failing to find any documentation about device limits...

Thanks!

Hi,
I'm trying to disable multiprotocol on my Skyconnect. It's flashed with the latest firmware. I follow the instructions (https://skyconnect.home-assistant.io/procedures/disable-multiprotocol/) but once I press the "Configure" button for my Skyconnect in the Hardware page all I see is this:

How do I disable multiprotocol?

Thank you for your help!

requested by @NanoWireDnB
#3

Hi,
like the title says I'm having this annoying problem with the SkyConnect Stick. I've set it up with my Home Assistant OS installation on a Raspberry Pi 4 8GB. I've added some Nanoleaf Essentials and Eve devices to the Thread network. After a couple of hours all Thread devices are unresponsive.

The log of Home Assistant Core looks like this:
home_assistant_core_log.txt

The log of the Silicon Labs Multiprotocol addon looks like this:
silicon_labs_multiprotocol_logs.txt

System info:
Home Assistant OS (2023.9.2)
Raspberry Pi 4 8GB