SkyConnect ZHA Integration Not Starting

My SkyConnect (ZHA) integration won’t start and keeps showing the below:

Screenshot 2023-05-24 at 18.55.59

Can anyone decipher the below from the logs for help on how to resolve the issue please?

Logger: zigpy.application
Source: /usr/local/lib/python3.10/site-packages/zigpy/application.py:196 
First occurred: 6:44:52 PM (11 occurrences) 
Last logged: 6:54:21 PM

Couldn't start application
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 193, in startup
    await self.connect()
  File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 131, in connect
    self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
  File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 147, in initialize
    await ezsp.connect(use_thread=zigpy_config[conf.CONF_USE_THREAD])
  File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 164, in connect
    self._gw = await bellows.uart.connect(self._config, self, use_thread=use_thread)
  File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 414, in connect
    protocol, _ = await _connect(config, application)
  File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 385, in _connect
    transport, protocol = await zigpy.serial.create_serial_connection(
  File "/usr/local/lib/python3.10/site-packages/zigpy/serial.py", line 31, in create_serial_connection
    transport, protocol = await loop.create_connection(
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1076, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1060, in create_connection
    sock = await self._connect_sock(
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 969, in _connect_sock
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 501, in sock_connect
    return await fut
  File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 541, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('172.30.32.1', 9999)

I am having this same issue. Were you able to find a solution?


Logger: zigpy.application
Source: /usr/local/lib/python3.11/site-packages/zigpy/application.py:196 
First occurred: August 10, 2023 at 11:35:13 PM (326 occurrences) 
Last logged: 6:48:17 AM

Couldn't start application
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 193, in startup
    await self.connect()
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 133, in connect
    self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 164, in initialize
    await ezsp.connect(use_thread=zigpy_config[conf.CONF_USE_THREAD])
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 181, in connect
    self._gw = await bellows.uart.connect(self._config, self, use_thread=use_thread)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bellows/uart.py", line 414, in connect
    protocol, _ = await _connect(config, application)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bellows/uart.py", line 385, in _connect
    transport, protocol = await zigpy.serial.create_serial_connection(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/serial.py", line 31, in create_serial_connection
    transport, protocol = await loop.create_connection(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1085, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1069, in create_connection
    sock = await self._connect_sock(
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 628, in sock_connect
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 668, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('172.30.32.1', 9999)

ZHA is trying to connect to the SiLabs Multiprotocol Addon’s Zigbee stack and failing.
Maybe check the logs in the Multiprotocol Addon to see if there are any errors in it.

Thanks for the tip. It does look like it’s not starting correctly.


[20:29:05] INFO: The otbr-web is disabled.
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/check-cpcd-shm.sh
[20:29:05] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Aug  4 2023 21:48:56) starting
Default: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
cont-init: info: /etc/cont-init.d/check-cpcd-shm.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting
-----------------------------------------------------------
 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 2.3.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.8.1
 Home Assistant Supervisor: 2023.08.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[20:29:08] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[20:29:08] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2023-08-11 20:29:09 homeassistant universal_silabs_flasher.flash[181] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2023-08-11 20:29:09 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-08-11 20:29:11 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 460800 baud
2023-08-11 20:29:15 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 115200 baud
2023-08-11 20:29:20 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 230400 baud
2023-08-11 20:29:24 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.EZSP at 115200 baud
2023-08-11 20:29:29 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Aug  4 2023 21:48:56) stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[20:29:34] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

The SiLabs Multiprotocol Add-On is not able to communicate with the SkyConnect.

In the AddOn’s “configuration” tab, make sure the “Device” is set to something like “/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_blah-blah-if00-port0

I have the same issue.
Occured 2 times now.
First time I manage to solve it by enabling Multipan but now it has “crashed” again.

Getting:

ACCEPT all anywhere anywhere
[12:15:56] INFO: OTBR firewall teardown completed.
[12:15:56:454027] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
[12:15:56:454063] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
[12:15:56:455067] Info : Client disconnected
[12:15:56:563954] Info : New client connection using library v4.3.1.0
[12:15:58] INFO: Setup OTBR firewall…
[12:15:58] INFO: Starting otbr-agent…
otbr-agent[23582]: [NOTE]-AGENT—: Running 0.3.0
otbr-agent[23582]: [NOTE]-AGENT—: Thread version: 1.3.0
otbr-agent[23582]: [NOTE]-AGENT—: Thread interface: wpan0
otbr-agent[23582]: [NOTE]-AGENT—: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[23582]: [NOTE]-ILS-----: Infra link selected: eth0
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
close cpc endpoint: No such file or directory
By using this software, you are agreeing to the Silicon Labs MSLA found at Master Software License Agreement - Silicon Labs - Silicon Labs.
[12:15:58] INFO: zigbeed ended with exit code 1 (signal 0)…
[12:15:58:398414] Info : New client connection using library v4.3.1.0
[12:15:58:454016] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
[12:15:58:454046] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
[12:15:58:454794] Info : Client disconnected
[12:15:59] INFO: Starting zigbeed…
otbr-agent[23582]: 49d.17:27:37.660 [C] Platform------: CPC endpoint open failed
otbr-agent[23582]: 49d.17:27:37.660 [C] Platform------: mCpcBusSpeed = 115200
otbr-agent[23582]: 49d.17:27:37.660 [C] Platform------: Init() at radio.cpp:121: Failure
close cpc endpoint: Resource temporarily unavailable
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
WARNING in function ‘system_send_open_endpoint_ack’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #122 : Failed to acknowledge the open request for endpoint #12. Bad file descriptor
[12:16:00] INFO: otbr-agent ended with exit code 1 (signal 0)…
OTBR_FORWARD_INGRESS all opt in * out wpan0 ::/0 → ::/0
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all anywhere anywhere PKTTYPE = unicast
DROP all anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all anywhere anywhere PKTTYPE = unicast
ACCEPT all anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
OTBR_FORWARD_EGRESS all opt in wpan0 out * ::/0 → ::/0
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all anywhere anywhere
[12:16:00] INFO: OTBR firewall teardown completed.
[12:16:00:423064] Info : Client disconnected
[12:16:00:454026] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
[12:16:00:454060] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
[12:16:00:454068] WARNING : In function ‘system_send_open_endpoint_ack’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #122 : Failed to acknowledge the open request for endpoint #12. Bad file descriptor
[12:16:00:569001] Info : New client connection using library v4.3.1.0
[12:16:02] INFO: Setup OTBR firewall…
[12:16:02] INFO: Starting otbr-agent…
otbr-agent[23700]: [NOTE]-AGENT—: Running 0.3.0
otbr-agent[23700]: [NOTE]-AGENT—: Thread version: 1.3.0
otbr-agent[23700]: [NOTE]-AGENT—: Thread interface: wpan0
otbr-agent[23700]: [NOTE]-AGENT—: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[23700]: [NOTE]-ILS-----: Infra link selected: eth0
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
close cpc endpoint: No such file or directory
By using this software, you are agreeing to the Silicon Labs MSLA found at Master Software License Agreement - Silicon Labs - Silicon Labs.
[12:16:02] INFO: zigbeed ended with exit code 1 (signal 0)…
[12:16:02:408368] Info : New client connection using library v4.3.1.0
[12:16:02:454018] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
[12:16:02:454055] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
[12:16:02:454840] Info : Client disconnected
[12:16:03] INFO: Starting zigbeed…
otbr-agent[23700]: 49d.17:27:41.660 [C] Platform------: CPC endpoint open failed
otbr-agent[23700]: 49d.17:27:41.660 [C] Platform------: mCpcBusSpeed = 115200
otbr-agent[23700]: 49d.17:27:41.660 [C] Platform------: Init() at radio.cpp:121: Failure
close cpc endpoint: Resource temporarily unavailable
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
WARNING in function ‘system_send_open_endpoint_ack’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #122 : Failed to acknowledge the open request for endpoint #12. Bad file descriptor
[12:16:04] INFO: otbr-agent ended with exit code 1 (signal 0)…
OTBR_FORWARD_INGRESS all opt in * out wpan0 ::/0 → ::/0
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all anywhere anywhere PKTTYPE = unicast
DROP all anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all anywhere anywhere PKTTYPE = unicast
ACCEPT all anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
OTBR_FORWARD_EGRESS all opt in wpan0 out * ::/0 → ::/0
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all anywhere anywhere
[12:16:04] INFO: OTBR firewall teardown completed.
[12:16:04:423096] Info : Client disconnected
[12:16:04:454031] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
[12:16:04:454073] WARNING : In function ‘property_get_single_endpoint_state_and_reply_to_pending_open_callback’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
[12:16:04:454082] WARNING : In function ‘system_send_open_endpoint_ack’ in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #122 : Failed to acknowledge the open request for endpoint #12. Bad file descriptor
[12:16:04:558272] Info : New client connection using library v4.3.1.0

Mine died once more again. after Powerfailure in the house.
I fear that my Skyconnect has died. :frowning: