Problem with SkyConnect ZBT-1 integration installation - Unknown Error Occurred

[Bhrudwo]

The problem

I bought a ZBT-1 to work with the aqara stuff I just bought, have had the ZBT-1 for 5 days, have updated to: HAOS 13.0 HA Core 2024.8.1 Running full HA via a virtualbox VM, on a windows 10 machine (Lenovo M92p).

I have the ZBT-1 being detected (so passed through to the VM). Click the configure. Select Zigbee (only trying for Zigbee due to the aqara hub and sensors; no other thread devices at present).

Clicking the Submit button the action button starts as the swirling icon and then eventually responds as "Unknown error occurred". Closing this via the "X", and trying to navigate to Settings > Logs - the Lods are unreachable, as HA has crashed.

I have to End Task the VM. Upon restarting the VM and waiting for HA to load fully, but the log files are empty (from what I can see) of anything that went on with the ZBT-1

What version of Home Assistant Core has the issue?

core-2024.8.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Home Assistant Connect ZBT-1

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logs are attached from before the last attempt and after the last attempt.
Had posted on Issue 116545, told to create a new issue.

Additional information

home-assistant_2024-08-15T04-16-37.917Z.log home-assistant_2024-08-15T04-26-46.901Z.log

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (homeassistant_sky_connect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_sky_connect can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign homeassistant_sky_connect Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homeassistant_sky_connect documentation homeassistant_sky_connect source _{^{(message by IssueLinks)}}

[ShaKann]

I have exactly same problem... After trying to add ZigBee configuration using SkyConnect of Sonoff USB dongle 3.0 I have same result - HA crushes. Then it is not possible even close VM, I need to kill it from OS level. I am running newest VirtualBox 7.0.20 with haos_ova-12.4 disk image... I just tested using another Windows machine with fresh haos_ova-13.1.vdi. I started new Ha instance from scratch. First thing I have done is just try to add SkyConnect. It detects it correctly, after clicking configure, I choose ZigBee and then new option apear - Home Assistant SkyConnect. After clicking configure everything hangs...

[mtzbuttz]

Thought I'd also chime in I also have the same issue.

Bought the Skyconnect this last weekend, marked as batch: 232401

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[puddly]

Without debug logs this is going to be very difficult to diagnose or figure out what's wrong. Is there anything at all in the Core log?

[mtzbuttz]

I Tried updating the firmware on the website, it looks like this now:

First the USB-Stick shows up like this. it's the cygnal products one

If I Attach it I get 2 disconnect sounds on my pc and then the Nabu Casa Skyconnect shows up, aswell as the old one:

I did a fresh version of the VM before this, and cloned it so I can go back just in case.

Now I can't get it to attach at all, is this a problem with VirtualBox maybe?

I found this page

https://github.com/NabuCasa/silabs-firmware-builder/releases

Should I try a different firmware or something? Before I updated it I could attach it to the VM atleast... But it also had this strange behaviour changing its device name in the same way even before I updated it.

Unfortunately I did not save any logs from before I wiped it, if I get it to attach and manage to recreate the issue I will add it

EDIT:

Hello again! I managed to get it to attach by uninstalling the drivers for cygnal uart thingy in the unit manager in windows, so now HAS does discover the stick again and I can attach it.

However now I can't get past the first stage where it initiates, it freezes up the VM so something is not quite right, How can I get the log if the VM is frozen?

I tried to find them using the terminal but have no idea how to print them out

Feeling lost :/

This is how it looks in the HW section

DEVLINKS: >- /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_1ef6621b28eced119c30141d62c613ac-if00-port0 /dev/serial/by-path/pci-0000:00:06.0-usb-0:2:1.0-port0 /dev/serial/by-path/pci-0000:00:06.0-usbv1-0:2:1.0-port0 DEVNAME: /dev/ttyUSB0 DEVPATH: /devices/pci0000:00/0000:00:06.0/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0 ID_BUS: usb ID_MODEL: SkyConnect_v1.0 ID_MODEL_ENC: SkyConnect\x20v1.0 ID_MODEL_ID: ea60 ID_PATH: pci-0000:00:06.0-usb-0:2:1.0 ID_PATH_TAG: pci-0000_00_06_0-usb-0_2_1_0 ID_PATH_WITH_USB_REVISION: pci-0000:00:06.0-usbv1-0:2:1.0 ID_REVISION: '0100' ID_SERIAL: Nabu_Casa_SkyConnect_v1.0_1ef6621b28eced119c30141d62c613ac ID_SERIAL_SHORT: 1ef6621b28eced119c30141d62c613ac ID_TYPE: generic ID_USB_DRIVER: cp210x ID_USB_INTERFACES: ':ff0000:' ID_USB_INTERFACE_NUM: '00' ID_USB_MODEL: SkyConnect_v1.0 ID_USB_MODEL_ENC: SkyConnect\x20v1.0 ID_USB_MODEL_ID: ea60 ID_USB_REVISION: '0100' ID_USB_SERIAL: Nabu_Casa_SkyConnect_v1.0_1ef6621b28eced119c30141d62c613ac ID_USB_SERIAL_SHORT: 1ef6621b28eced119c30141d62c613ac ID_USB_TYPE: generic ID_USB_VENDOR: Nabu_Casa ID_USB_VENDOR_ENC: Nabu\x20Casa ID_USB_VENDOR_ID: 10c4 ID_VENDOR: Nabu_Casa ID_VENDOR_ENC: Nabu\x20Casa ID_VENDOR_ID: 10c4 MAJOR: '188' MINOR: '0' SUBSYSTEM: tty TAGS: ':systemd:' USEC_INITIALIZED: '2461696233'

[meinol1]

I have the same issue but with thread. Fresh install of the latest version of HA in virtual box on windows 11 (new sky connect zbt-1).

HA detects the skyconnect, pressing configure and selecting thread crashes home assistant/not responding. It did install the matter integration, redoing the step gives me Failed to set OpenThread Border Router configuration, connection lost/crashes.

available logs @puddly

DNS .:53 .:5553 CoreDNS-1.8.7 linux/amd64, go1.22.2, a9adfd5-dirty [INFO] 127.0.0.1:42831 - 18874 "HINFO IN 4374139010957346486.2492583750329251853. udp 68 true 2048" REFUSED qr,aa,rd 57 0.000964935s [INFO] 127.0.0.1:51852 - 42993 "HINFO IN 4374139010957346486.2492583750329251853. udp 57 false 512" REFUSED qr,aa,rd 57 0.012822094s

OpenThread Border Router No errors have been reported

Home Assistant Core 2024-10-12 00:43:41.498 ERROR (SyncWorker_3) [homeassistant.util.json] Could not parse JSON content: /config/.storage/lovelace.map Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/util/json.py", line 75, in load_json return orjson.loads(fdesc.read()) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^^^^^^^^ orjson.JSONDecodeError: Input is a zero-length, empty document: line 1 column 1 (char 0) 2024-10-12 00:43:41.764 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 2024-10-12 00:43:41.794 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=2 from 2024-10-11 22:02:08.023420)

Logger: homeassistant.components.recorder.util Source: components/recorder/util.py:630 integration: Recorder (documentation, issues) First occurred: 12:43:41 AM (1 occurrences) Last logged: 12:43:41 AM

Ended unfinished session (id=2 from 2024-10-11 22:02:08.023420)

Logger: homeassistant.components.recorder.util Source: components/recorder/util.py:299 integration: Recorder (documentation, issues) First occurred: 12:43:41 AM (1 occurrences) Last logged: 12:43:41 AM

The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly

Logger: homeassistant.util.json Source: util/json.py:75 First occurred: 12:43:41 AM (1 occurrences) Last logged: 12:43:41 AM

Could not parse JSON content: /config/.storage/lovelace.map Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/util/json.py", line 75, in load_json return orjson.loads(fdesc.read()) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^^^^^^^^ orjson.JSONDecodeError: Input is a zero-length, empty document: line 1 column 1 (char 0)

Matter Server [00:01:57] INFO: Using 'enp0s3' as primary network interface. [00:01:57] INFO: Successfully send discovery information to Home Assistant. 2024-10-12 00:01:59.621 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging... 2024-10-12 00:01:59.621 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack... [1728684119.876421][126:126] CHIP:CTL: Setting attestation nonce to random value [1728684119.884938][126:126] CHIP:CTL: Setting CSR nonce to random value [1728684119.916799][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs [1728684119.917205][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-cdTUJI) [1728684119.917492][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs) [1728684119.918107][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini [1728684119.924359][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini [1728684119.925091][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini [1728684119.928315][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-lvCAvH) [1728684119.928809][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini) [1728684119.928821][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2) [1728684119.929403][126:126] CHIP:DL: Got Ethernet interface: enp0s3 [1728684119.929874][126:126] CHIP:DL: Found the primary Ethernet interface:enp0s3 [1728684119.930690][126:126] CHIP:DL: Failed to get WiFi interface [1728684119.930865][126:126] CHIP:DL: Failed to reset WiFi statistic counts 2024-10-12 00:01:59.931 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json 2024-10-12 00:01:59.931 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json... 2024-10-12 00:01:59.993 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage... 2024-10-12 00:01:59.995 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1 2024-10-12 00:02:00.001 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage... 2024-10-12 00:02:00.002 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B 2024-10-12 00:02:00.002 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized. 2024-10-12 00:02:00.003 (MainThread) INFO [matter_server.server.server] Starting the Matter Server... 2024-10-12 00:02:00.011 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h). 2024-10-12 00:02:00.011 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: [] 2024-10-12 00:02:00.130 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 117 ms, for event type 2 2024-10-12 00:02:00.138 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage. 2024-10-12 00:02:00.138 (MainThread) INFO [matter_server.server.vendor_info] Loaded 0 vendors from storage. 2024-10-12 00:02:00.138 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL. 2024-10-12 00:02:00.555 (MainThread) INFO [matter_server.server.vendor_info] Fetched 251 vendors from DCL. 2024-10-12 00:02:00.556 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage. 2024-10-12 00:02:00.557 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration 2024-10-12 00:02:00.563 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized. s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service banner: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started

Add-on: Matter Server Matter WebSocket Server for Home Assistant Matter support.

Add-on version: 6.6.0 You are running the latest version of this add-on. System: Home Assistant OS 13.1 (amd64 / qemux86-64) Home Assistant Core: 2024.10.2 Home Assistant Supervisor: 2024.10.0

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

[meinol1]

As Hyper-V does not support USB passthrough (haven't tested KVM) I got it working on VMware personal use/free version "VMware® Workstation 17 Pro 17.6.1 build-24319023 on host Windows 11 Pro". Either it was a configuration issue, issue with usb-passtrhough on virtual box in windows or issues with home assistant utilizing the usb device passthrough from Virtualbox when trying to set the firmware to either thread or matter.

Read somewhere that someone got it working using the web-flasher https://connectzbt1.home-assistant.io/firmware-update/ assuming by-passing setting it to thread or matter in HAOS. It has since then been removed as the firmware is deemed stable with reference to HAOS (which does not work with virtualbox)

I would propose clarififying that https://www.home-assistant.io/installation/windows/ virtual box is not supported with skyconnect. Or just state that the preferred way would be VMWare (or KVM?).

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[olomhuszar]

I ran into the exact same problem, but the host is a Ubuntu 2024.1 server.

I managed to get it work by doing two things:

• Disabled OHCI(usb1.1) and EHCI(usb2.0) and enabled only xHCI (USB 3) support. (With EHCI it did not even passthrough the device, it did with ohci but I ran into the error described here)
• Upgraded to the latest version (2025.2.0)

I don't know which step was the key step, but now I could add it successfully.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[meinol1]

Documentation still does not state that sky connect is not compatible with VM's

[puddly]

The SkyConnect/ZBT-1 is very much compatible with VMs. Your hypervisor needs to be properly configured to pass through the USB device and the USB serial port.

[meinol1]

According to the information in this bug report it's correctly configured and detected, I have the same issue and it has been reported in other threads/known issue. Either it's supported and not working or it's not supported and the documentation should be updated.