addons: Silicon Labs Multiprotocol Broken with version 1.0.0

After upgrade it does not work. broke Z2MQTT as well

[12:29:39] 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
[12:29:39] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Mar  1 2023 17:42:59) starting
Default: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
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
cont-init: info: /etc/cont-init.d/check-cpcd-shm.sh exited 0
cont-init: info: running /etc/cont-init.d/config.sh
[12:29:40] 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: 1.0.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.3.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
[12:29:40] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[12:29:40] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (baudrate 115200)
2023-03-04 12:29:41 core-silabs-multiprotocol universal_silabs_flasher.flash[237] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.2.1'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>)
2023-03-04 12:29:41 core-silabs-multiprotocol universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-03-04 12:29:43 core-silabs-multiprotocol universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.CPC
2023-03-04 12:29:47 core-silabs-multiprotocol universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type
2023-03-04 12:29:52 core-silabs-multiprotocol concurrent.futures[237] ERROR exception calling callback for <Future at 0x7f2ce1d35550 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.
/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) (Mar  1 2023 17:42:59) 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
[12:29:52] 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?

Almond

What is the version of the add-on?

1.0

Steps to reproduce the issue

1upgraded to the latest version 2. 3. …

System Health information

There are currently no repairs available

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

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:124
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 12:05:57 PM (12 occurrences)
Last logged: 12:29:35 PM

Failed to to call /addons/core_silabs_multiprotocol/stats - Container addon_core_silabs_multiprotocol is not running
Failed to to call /addons/45df7312_zigbee2mqtt/stats - Container addon_45df7312_zigbee2mqtt is not running
Failed to to call /addons/core_silabs_multiprotocol/stats - 404 Client Error for http+docker://localhost/v1.41/containers/addon_core_silabs_multiprotocol/json: Not Found ("No such container: addon_core_silabs_multiprotocol")

Logger: homeassistant.config_entries
Source: config_entries.py:1244
First occurred: 12:05:10 PM (1 occurrences)
Last logged: 12:05:10 PM

Config entry 'Open Thread Border Router' for otbr integration not ready yet: Unable to connect; Retrying in background

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: 1
  • Comments: 17

Most upvoted comments

I’ll add a cross reference https://github.com/home-assistant/addons/issues/2899#issuecomment-1454146967 as I am also having issues with zigbee2mqtt with multiprotocol. Multiprotocol version 0.13.1 worked for the most part (but not always), but v1.0.0 I can’t get to work.

Before all the updates day before everything was working with skyconnect wilth multi and Zigbee2MQTT as well. After all the updates yesterday its been crazy.

[21:52:13] INFO: Preparing to start… [21:52:13] INFO: Socat not enabled [21:52:14] INFO: Starting Zigbee2MQTT… Zigbee2MQTT:info 2023-03-05 21:52:15: Logging to console and directory: ‘/config/zigbee2mqtt/log/2023-03-05.21-52-15’ filename: log.txt Zigbee2MQTT:info 2023-03-05 21:52:15: Starting Zigbee2MQTT version 1.30.2 (commit #unknown) Zigbee2MQTT:info 2023-03-05 21:52:15: Starting zigbee-herdsman (0.14.96) Zigbee2MQTT:error 2023-03-05 21:52:28: Error while starting zigbee-herdsman Zigbee2MQTT:error 2023-03-05 21:52:28: Failed to start zigbee Zigbee2MQTT:error 2023-03-05 21:52:28: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2023-03-05 21:52:28: Exiting… Zigbee2MQTT:error 2023-03-05 21:52:28: Error: Connection not initialized at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:540:19) at Ezsp.version (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:338:35) at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:141:25) at processTicksAndRejections (node:internal/process/task_queues:96:5) at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:165:16) at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29) at Zigbee.start (/app/lib/zigbee.ts:58:27) at Controller.start (/app/lib/controller.ts:101:27) at start (/app/index.js:107:5)

Ah right. You have to remove Zigbee2MQTT and install Dev version. Zigbee2MQTT Edge.