addons: Skyconnect Problem with Silicon Labs Multiprotocol

Describe the issue you are experiencing

I got my Skyconnect adapter today and wanted to set it up. Unfortunately there are problems with the Multiprtocol support.

Silicon Labs Multiprotocol 0.12.0


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
[17:22:38] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 23 2023 22:46:33) 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
cont-init: info: running /etc/cont-init.d/config.sh
[17:22:38] INFO: Generating cpcd configuration.
cont-init: info: /etc/cont-init.d/config.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: 0.12.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.2.0b9
 Home Assistant Supervisor: 2023.01.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
[17:22:39] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa
[17:22:39] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (baudrate 115200)
2023-02-01 17:22:39 core-silabs-multiprotocol universal_silabs_flasher.flash[219] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.1.4'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>)
2023-02-01 17:22:39 core-silabs-multiprotocol universal_silabs_flasher.flasher[219] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-02-01 17:22:41 core-silabs-multiprotocol universal_silabs_flasher.flasher[219] INFO Probing ApplicationType.CPC
2023-02-01 17:22:45 core-silabs-multiprotocol universal_silabs_flasher.flasher[219] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type
2023-02-01 17:22:50 core-silabs-multiprotocol concurrent.futures[219] ERROR exception calling callback for <Future at 0x7f9e2fb1e9d0 state=finished returned NoneType>
Traceback (most recent call last):
  File "/usr/lib/python3.9/concurrent/futures/_base.py", line 329, in _invoke_callbacks
    callback(self)
  File "/usr/lib/python3.9/asyncio/futures.py", line 398, in _call_set_state
    dest_loop.call_soon_threadsafe(_set_state, destination, source)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 791, in call_soon_threadsafe
    self._check_closed()
  File "/usr/lib/python3.9/asyncio/base_events.py", line 510, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
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.
prog: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Jan 23 2023 22:46:33) 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
[17:22:50] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Silicon Labs Multiprotocol

What is the version of the add-on?

Silicon Labs Multiprotocol

Steps to reproduce the issue

Flash via laptop to the System -> firmware from https://github.com/NabuCasa/silabs-firmware/blob/main/EmberZNetAndOpenThreadRCP/beta/NabuCasa_SkyConnect_EZSP_OpenThread_RCP_v4.1.3.0_ncp-uart-hw_230400.gbl
Plugin in the System (VM)
System -> Hardware-> Home Assistant SkyConnect -> start configuration

System Health information

Derzeit sind keine Reparaturen verfügbar

Currently no repairs are available

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: closed
Created a year ago
Reactions: 3
Comments: 20 (3 by maintainers)

Most upvoted comments

I have exactly the same issues as you described. Hopefully they fix it soon. Don’t want to flash firmware manually.

DiaboloVampire on Feb 6, 2023

The problem looks exactly the same for me. With 230400 or with 115200 run1.txt run2.txt

ALutz273 on Feb 5, 2023

I’ve found it to be the Automatically flash firmware option. If it is enabled, I get the same error:

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
[21:18:01] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 23 2023 22:46:33) 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
cont-init: info: running /etc/cont-init.d/config.sh
[21:18:03] INFO: Generating cpcd configuration.
cont-init: info: /etc/cont-init.d/config.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: 0.12.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.2.1
 Home Assistant Supervisor: 2023.01.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
[21:18:05] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa
[21:18:05] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (baudrate 230400)
2023-02-04 21:18:07 core-silabs-multiprotocol universal_silabs_flasher.flash[217] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.1.4'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>)
2023-02-04 21:18:07 core-silabs-multiprotocol universal_silabs_flasher.flasher[217] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-02-04 21:18:09 core-silabs-multiprotocol universal_silabs_flasher.flasher[217] INFO Probing ApplicationType.CPC
2023-02-04 21:18:13 core-silabs-multiprotocol universal_silabs_flasher.flasher[217] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type
2023-02-04 21:18:18 core-silabs-multiprotocol concurrent.futures[217] ERROR exception calling callback for <Future at 0x7fd7ab246910 state=finished returned NoneType>
Traceback (most recent call last):
  File "/usr/lib/python3.9/concurrent/futures/_base.py", line 329, in _invoke_callbacks
    callback(self)
  File "/usr/lib/python3.9/asyncio/futures.py", line 398, in _call_set_state
    dest_loop.call_soon_threadsafe(_set_state, destination, source)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 791, in call_soon_threadsafe
    self._check_closed()
  File "/usr/lib/python3.9/asyncio/base_events.py", line 510, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
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.
prog: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Jan 23 2023 22:46:33) 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
[21:18:19] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

When it is disabled, it starts, except it loops with Failed to connect to Secondary... filling up the log:

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[21:24:58] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd: starting
[21:24:58] INFO: Starting cpcd...
[21:24:58:910] Info : [CPCd v4.1.4.0] [Library API v2] [RCP Protocol v2]
[21:24:58:910] Info : Git commit: 5df3ef9fb8891987b623b623694ec4c435ea5644 / branch: 
[21:24:58:910] Info : Sources hash: 2606b603ff85938a832e691804f2d1fcf86745370d236a1a9c47f03bdf95898e
[21:24:58:910] Info : Reading cli arguments
[21:24:58:910] Info : /usr/local/bin/cpcd 
[21:24:58:929] Info : Reading configuration
[21:24:58:929] Info : file_path = /usr/local/etc/cpcd.conf
[21:24:58:929] Info : instance_name = cpcd_0
[21:24:58:929] Info : socket_folder = /dev/shm
[21:24:58:929] Info : operation_mode = MODE_NORMAL
[21:24:58:929] Info : use_encryption = false
[21:24:58:929] Info : binding_key_file = /etc/binding-key.key
[21:24:58:929] Info : binding_method = 
[21:24:58:929] Info : stdout_tracing = false
[21:24:58:929] Info : file_tracing = false
[21:24:58:929] Info : lttng_tracing = false
[21:24:58:929] Info : enable_frame_trace = false
[21:24:58:929] Info : traces_folder = /dev/shm/cpcd-traces
[21:24:58:929] Info : bus = UART
[21:24:58:929] Info : uart_baudrate = 230400
[21:24:58:929] Info : uart_hardflow = true
[21:24:58:929] Info : uart_file = /dev/ttyUSB0
[21:24:58:929] Info : spi_file = /dev/spidev0.0
[21:24:58:929] Info : spi_bitrate = 1000000
[21:24:58:929] Info : spi_mode = SPI_MODE_0
[21:24:58:929] Info : spi_bit_per_word = 8
[21:24:58:929] Info : spi_cs_chip = gpiochip0
[21:24:58:929] Info : spi_cs_pin = 8
[21:24:58:930] Info : spi_irq_chip = gpiochip0
[21:24:58:930] Info : spi_irq_pin = 22
[21:24:58:930] Info : fu_reset_chip = gpiochip0
[21:24:58:930] Info : fu_spi_reset_pin = 23
[21:24:58:930] Info : fu_wake_chip = gpiochip0
[21:24:58:930] Info : fu_spi_wake_pin = 24
[21:24:58:930] Info : fu_recovery_enabled = false
[21:24:58:930] Info : fu_connect_to_bootloader = false
[21:24:58:930] Info : fu_enter_bootloader = false
[21:24:58:930] Info : fu_file = 
[21:24:58:930] Info : fu_restart_daemon = false
[21:24:58:930] Info : board_controller_ip_addr = 
[21:24:58:930] Info : application_version_validation = false
[21:24:58:930] Info : print_secondary_versions_and_exit = false
[21:24:58:930] Info : use_noop_keep_alive = false
[21:24:58:930] Info : reset_sequence = true
[21:24:58:930] Info : uart_validation_test_option = 
[21:24:58:930] Info : stats_interval = 0
[21:24:58:930] Info : rlimit_nofile = 2000
[21:24:58:930] Info : ENCRYPTION IS DISABLED 
[21:24:58:930] Info : Starting daemon in normal mode
[21:24:58:952] Info : Connecting to Secondary...
[21:25:00:952] Info : Failed to connect to Secondary.
[21:25:00:952] Info : Connecting to Secondary...
... etc ....

Moqume on Feb 4, 2023

Hey, I’m having the same issues as listed here but even when I try to manually flash I’m hit with “Error: failed to probe application type”. Any advice? This fails when trying to probe ApplicationType.EZSP

miniminne on Feb 6, 2023

If automatic firmware updating is enabled (by default), with the recent versions of this add-on the baudrate configuration is always taken from the firmware metadata (since we know the firmware communicates at this baud rate). The user configuration is not really doing anything in that case. It doesn’t hurt to update the baudrate, but it also doesn’t change anything really.

So if changing the baudrate helped, then it is because you had to restart the add-on due to that.

agners on May 16, 2023