addons: issue with Silicon Labs Multiprotocol Add-on and Sonoff Zigbee Dongle plus E : Failed to connect, secondary seems unresponsive
Describe the issue you are experiencing
I’ve flashed the Sonoff Zigbee Dongle plus 3 according https://dialedin.com.au/blog/sonoff-zbdongle-e-rcp-firmware, and have then installed Silicon Labs Multiprotocol Add-on with the configuration below, but get continuous error in the log “Failed to connect, secondary seems unresponsive”
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?
2.4.3
Steps to reproduce the issue
- upgrade firmware of Dongle according https://dialedin.com.au/blog/sonoff-zbdongle-e-rcp-firmware with latest Zigbee firmware
- Install Silicon Labs Multiprotocol Add-on version 2.4.3
- Run the add on according confirguration attached above …
System Health information
System Information
| version | core-2024.1.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.6 |
| os_name | Linux |
| os_version | 6.1.63-haos-raspi |
| arch | aarch64 |
| timezone | Europe/Paris |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 4572 |
| Installed Version | 1.33.0 |
| Stage | running |
| Available Repositories | 1378 |
| Downloaded Repositories | 48 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | September 10, 2024 at 02:00 |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | true |
| google_enabled | false |
| remote_server | eu-central-1-4.ui.nabu.casa |
| certificate_status | ready |
| instance_id | 96b650674c4d4b979fc74636bf614237 |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 11.4 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.12.0 |
| agent_version | 1.6.0 |
| docker_version | 24.0.7 |
| disk_total | 916.2 GB |
| disk_used | 31.4 GB |
| healthy | true |
| supported | true |
| board | rpi4-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Samba share (12.2.0), File editor (5.7.0), motionEye (0.20.0), Home Panel (2.7.0), Grafana (9.1.2), Node-RED (17.0.2), Advanced SSH & Web Terminal (17.0.3), Home Assistant Google Drive Backup (0.112.1), Z-Wave JS UI (3.1.0), InfluxDB (5.0.0), Studio Code Server (5.15.0), RTSP Simple Server Add-on (v0.17.6), Mosquitto broker (6.4.0), Frigate (0.12.1), SQLite Web (4.1.0), eufy-security-ws (1.7.1), eWeLink Smart Home (1.4.3), Zigbee2MQTT (1.35.1-1), Silicon Labs Multiprotocol (2.4.3) |
Dashboards
| dashboards | 2 |
|---|---|
| resources | 19 |
| views | 22 |
| mode | storage |
Recorder
| oldest_recorder_run | January 8, 2024 at 20:03 |
|---|---|
| current_recorder_run | January 14, 2024 at 14:14 |
| estimated_db_size | 168.61 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
Anything in the Supervisor logs that might be useful for us?
Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:584
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 14:24:42 (8 occurrences)
Last logged: 14:42:30
Timeout on /addons/core_silabs_multiprotocol/start request
Anything in the add-on logs that might be useful for us?
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 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
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.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 11.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.1.3
Home Assistant Supervisor: 2023.12.0
-----------------------------------------------------------
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
[15:09:33] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[15:09:34] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[15:09:35] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #187 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[2024-01-14T14:09:35.151125Z] Info : [CPCd v4.4.0.0] [Library API v3] [RCP Protocol v5]
[2024-01-14T14:09:35.151284Z] Info : Git commit: 1fcaa81347466165f81e4533ee4471e9c3b6db0a / branch:
[2024-01-14T14:09:35.151288Z] Info : Sources hash: 1e938c77bacd9c9d6d8fe7b457208a3a8a2435bd6374a1918605ffb864bf1ebe
[2024-01-14T14:09:35.151309Z] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #187 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[2024-01-14T14:09:35.151535Z] Info : Reading cli arguments
[2024-01-14T14:09:35.151549Z] Info : /usr/local/bin/cpcd
[2024-01-14T14:09:35.154978Z] Info : Reading configuration
[2024-01-14T14:09:35.154992Z] Info : file_path = /usr/local/etc/cpcd.conf
[2024-01-14T14:09:35.154995Z] Info : instance_name = cpcd_0
[2024-01-14T14:09:35.154997Z] Info : socket_folder = /dev/shm
[2024-01-14T14:09:35.155000Z] Info : operation_mode = MODE_NORMAL
[2024-01-14T14:09:35.155002Z] Info : use_encryption = false
[2024-01-14T14:09:35.155004Z] Info : binding_key_file = /etc/binding-key.key
[2024-01-14T14:09:35.155007Z] Info : stdout_tracing = false
[2024-01-14T14:09:35.155009Z] Info : file_tracing = false
[2024-01-14T14:09:35.155011Z] Info : lttng_tracing = false
[2024-01-14T14:09:35.155013Z] Info : enable_frame_trace = false
[2024-01-14T14:09:35.155014Z] Info : traces_folder = /dev/shm/cpcd-traces
[2024-01-14T14:09:35.155017Z] Info : bus = UART
[2024-01-14T14:09:35.155019Z] Info : uart_baudrate = 460800
[2024-01-14T14:09:35.155022Z] Info : uart_hardflow = false
[2024-01-14T14:09:35.155024Z] Info : uart_file = /dev/ttyACM1
[2024-01-14T14:09:35.155026Z] Info : fu_recovery_pins_enabled = false
[2024-01-14T14:09:35.155029Z] Info : fu_connect_to_bootloader = false
[2024-01-14T14:09:35.155031Z] Info : fu_enter_bootloader = false
[2024-01-14T14:09:35.155033Z] Info : restart_cpcd = false
[2024-01-14T14:09:35.155035Z] Info : application_version_validation = false
[2024-01-14T14:09:35.155037Z] Info : print_secondary_versions_and_exit = false
[2024-01-14T14:09:35.155039Z] Info : use_noop_keep_alive = false
[2024-01-14T14:09:35.155041Z] Info : reset_sequence = true
[2024-01-14T14:09:35.155043Z] Info : stats_interval = 0
[2024-01-14T14:09:35.155045Z] Info : rlimit_nofile = 2000
[2024-01-14T14:09:35.155048Z] Info : ENCRYPTION IS DISABLED
[2024-01-14T14:09:35.167953Z] Info : Starting daemon in normal mode
[2024-01-14T14:09:35.182677Z] Info : Connecting to Secondary...
[2024-01-14T14:09:37.183482Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:37.183522Z] Info : Connecting to Secondary...
[2024-01-14T14:09:39.184054Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:39.184087Z] Info : Connecting to Secondary...
[2024-01-14T14:09:41.184554Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:41.184595Z] Info : Connecting to Secondary...
[2024-01-14T14:09:43.185133Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:43.185174Z] Info : Connecting to Secondary...
[2024-01-14T14:09:45.185446Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:45.185472Z] Info : Connecting to Secondary...
[2024-01-14T14:09:47.185812Z] Info : Failed to connect, secondary seems unresponsive
[2024-01-14T14:09:47.185854Z] Info : Connecting to Secondary...
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 6 months ago
- Reactions: 2
- Comments: 21 (9 by maintainers)
I havent updated it due to the Zigbee2MQTT breakage. It would recommend using the multipan flasher addon to get latest multipan firmware if you are using ZHA!
There is a fix now in Zigee2MQTT Dev branch, so it should be released soon.
@MYanello As a general rule you always need to use the same 4.x version as the Silabs Multiprotocol addon is using. Twice now, this has been downgraded back to 4.3.1. As a one-off 4.3.2 also has some stability issues so that is the reasoning for going back to 4.3.1 instead.
Just keep an eye on the release notes, whenever they bump to a new major 4.x version you need to update firmware. https://github.com/home-assistant/addons/blob/master/silabs-multiprotocol/CHANGELOG.md