agners
commented
8 months ago @darkxst can you have a look at this?
Closed Kri72 closed 6 months ago
agners
commented
8 months ago @darkxst can you have a look at this?
darkxst
commented
8 months ago @Kri72 Which version firmware did you flash? You need 4.4.0 to work this version of silabs multiprotocol, but I havent updated my webflasher, (or that blog post yet) which are still at 4.3.2.
You can install directly this firmware: https://github.com/darkxst/silabs-firmware-builder/raw/main/firmware_builds/zbdonglee/rcp-uart-802154-v4.4.0-zbdonglee-460800.gbl
Or use my multipan flasher add-on which is updated with 4.4.0 https://github.com/darkxst/multipan_flasher
yalec38
commented
8 months ago Hello, I think Kri72 should downgrade the version of Silicon Labs Multiprotocol to version 2.4.2 or earlier because the version installed by Kri72 (2.4.3) is incompatible with zigbee2mqtt. But there is no link to 2.4.2 version on github.
thenoid
commented
8 months ago but I havent updated my webflasher,
for those of us who are lazy and willing to buy a cup of coffee any eta on updating the webflasher =}
Kri72
commented
8 months ago Hello to all!! thanks for youor feedback.. In fact i have flashed latest version from the webflasher, which is : SDK version 4.3.1, EZSP Version 7.3.1.0 Build 176. I'll try in the coming days to 4.4.0, and will keep you informed!
darkxst
commented
8 months ago for those of us who are lazy and willing to buy a cup of coffee any eta on updating the webflasher =}
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.
chrizstone
commented
7 months ago I have flashed the firmware with your
@Kri72 Which version firmware did you flash? You need 4.4.0 to work this version of silabs multiprotocol, but I havent updated my webflasher, (or that blog post yet) which are still at 4.3.2.
You can install directly this firmware: https://github.com/darkxst/silabs-firmware-builder/raw/main/firmware_builds/zbdonglee/rcp-uart-802154-v4.4.0-zbdonglee-460800.gbl
Or use my multipan flasher add-on which is updated with 4.4.0 https://github.com/darkxst/multipan_flasher
I flashed the firmware via the multipan flasher add-on. Sadly I still get the error when trying to start the Zigbee2Mqtt add-on:
Error: {"address":0,"clusterId":32770,"sequence":2} after 10000ms at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7)
darkxst
commented
7 months ago I flashed the firmware via the multipan flasher add-on. Sadly I still get the error when trying to start the Zigbee2Mqtt add-on:
You the time being you will need to install Zigbee2MQTT Edge add-on, which includes initial support for the updated EZSP protocol that comes with 4.4.0...
chrizstone
commented
7 months ago I flashed the firmware via the multipan flasher add-on. Sadly I still get the error when trying to start the Zigbee2Mqtt add-on:
You the time being you will need to install Zigbee2MQTT Edge add-on, which includes initial support for the updated EZSP protocol that comes with 4.4.0...
Oh yes, that works :) And if the fix is in stable version, I am able to just switch to the stable add-on?
Kri72
commented
7 months ago eed 4.4.0 to work this version of silabs multipro
Hello @darkxst , that's it, I could update my dongle to 4.4.0 thanks to you multipan flasher!
However, it doesnz't work any better.. I still get from Zigbee2mqtt
[19:52:05] INFO: Preparing to start...
[19:52:06] INFO: Socat not enabled
[19:52:09] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2024-01-21 19:52:16: Loaded state from file /config/zigbee2mqtt/state.json
Zigbee2MQTT:info 2024-01-21 19:52:16: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-21.19-52-16' filename: log.txt
Zigbee2MQTT:debug 2024-01-21 19:52:16: Removing old log directory '/config/zigbee2mqtt/log/2024-01-21.19-28-00'
Zigbee2MQTT:info 2024-01-21 19:52:16: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-21 19:52:16: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:debug 2024-01-21 19:52:16: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[25],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"ezsp","path":"tcp://core-silabs-multiprotocol:9999"}}'
Zigbee2MQTT:error 2024-01-21 19:52:37: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-01-21 19:52:37: Failed to start zigbee
Zigbee2MQTT:error 2024-01-21 19:52:37: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-01-21 19:52:37: Exiting...
Zigbee2MQTT:error 2024-01-21 19:52:37: Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:172:16)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:60:27)
at Controller.start (/app/lib/controller.ts:98:27)
at start (/app/index.js:107:5)And from Silicon Lab Multiprotocol
[2024-01-21T18:56:06.193196Z] Info : New client connection using library v4.4.0.0
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
[19:56:06] INFO: OTBR firewall teardown completed.
[19:56:06] WARNING: otbr-agent exited with code 1 (by signal 0).
WARNING in function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #132 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #152 : 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 https://www.silabs.com/about-us/legal/master-software-license-agreement.
[19:56:08] INFO: zigbeed ended with exit code 1 (signal 0)...
[19:56:08] INFO: Setup OTBR firewall...
[2024-01-21T18:56:07.995085Z] WARNING : In function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #132 : Property-get::PROP_ENDPOINT_STATE aborted
[2024-01-21T18:56:07.995131Z] WARNING : In function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #152 : Could not read endpoint state on the secondary
[2024-01-21T18:56:07.997393Z] Info : Client disconnected
[19:56:08] INFO: Starting otbr-agent...
otbr-agent[33248]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[33248]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[33248]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[33248]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[33248]: [NOTE]-ILS-----: Infra link selected: end0
[19:56:09] INFO: Starting zigbeed...
[2024-01-21T18:56:08.276452Z] Info : New client connection using library v4.4.0.0
WARNING in function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #132 : Property-get::PROP_ENDPOINT_STATE aborted
WARNING in function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #152 : Could not read endpoint state on the secondary
otbr-agent[33248]: 49d.17:34:43.224 [C] Platform------: CPC endpoint open failed
otbr-agent[33248]: 49d.17:34:43.224 [C] Platform------: mCpcBusSpeed = 115200
otbr-agent[33248]: 49d.17:34:43.224 [C] Platform------: Init() at radio_spinel.cpp:125: Failure
close cpc endpoint: Success
[19:56:10] 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
[2024-01-21T18:56:09.995136Z] WARNING : In function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #132 : Property-get::PROP_ENDPOINT_STATE aborted
[2024-01-21T18:56:09.995226Z] WARNING : In function 'is_endpoint_opened_reply_v5' in file /usr/src/cpc-daemon/server_core/core/protocol_v5.c at line #152 : Could not read endpoint state on the secondary
[2024-01-21T18:56:09.999349Z] Info : Client disconnected
[2024-01-21T18:56:10.190504Z] Info : New client connection using library v4.4.0.0
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
[19:56:10] INFO: OTBR firewall teardown completed.
[19:56:10] WARNING: otbr-agent exited with code 1 (by signal 0).[C] Platform------: mCpcBusSpeed = 115200
Check Baud rate setting, it should be 460800
Z2M needs to connect to the silabs-multiprotol addon, so not going to work until that is working!
darkxst
commented
7 months ago And if the fix is in stable version, I am able to just switch to the stable add-on?
yes, once 1.36 is release you can just switch back. Probably worth taking a backup of the z2m config folder, but it should work just fine
chrizstone
commented
7 months ago I just updated the Silicon Labs Multiprotocol to version 2.4.4 and now getting this error:
*** ASSERT *** : FATAL in function 'protocol_version_check' in file /usr/src/cpc-daemon/server_core/server_core.c at line #729 : Secondary Protocol v5 doesn't match CPCd Protocol v4 [21:10:35:527823] Info : Daemon exiting with status EXIT_FAILURE Logger buffer size = 28672, highwater mark = 2439 : 8.51%. Lost logs : 0 [21:10:35] INFO: CPC ended with exit code 1 (signal 0)... when trying to start it? What could be the probem here?
darkxst
commented
7 months ago I just updated the Silicon Labs Multiprotocol to version 2.4.4
You need to downgrade back to Multipan 4.3.1 again. Seems 4.4.0 hasn't been working out so well.
MYanello
commented
7 months ago I just updated the Silicon Labs Multiprotocol to version 2.4.4
You need to downgrade back to Multipan 4.3.1 again. Seems 4.4.0 hasn't been working out so well.
So with this advice what should we be using? z2mqtt edge and multipan 4.3.1? If so, how do we get past the original issue since the fix for that seemed to be run 4.4.0? Apologies, I'm getting lost a bit in the different advice but came here for the issue that was in the original post.
Which version firmware did you flash? You need 4.4.0 to work this version of silabs multiprotocol, but I havent updated my webflasher,
tl-sl
commented
7 months ago @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
MYanello
commented
7 months ago Thanks. I can confirm it is working now with z2m 1.35.3; silabs multiprotocol 2.4.4; multipan flasher 0.2.1; and sonoff 3.0 e version 4.3.1.
Kri72
commented
7 months ago Thanks. I can confirm it is working now with z2m 1.35.3; silabs multiprotocol 2.4.4; multipan flasher 0.2.1; and sonoff 3.0 e version 4.3.1.
Hello @MYanello does this mean I need to reflash my Sonoff back from 4.4 to 4.3.1? I also need to revert Multipan flasher from 0.2.2 to 0.2.1?
MYanello
commented
7 months ago Thanks. I can confirm it is working now with z2m 1.35.3; silabs multiprotocol 2.4.4; multipan flasher 0.2.1; and sonoff 3.0 e version 4.3.1.
Hello @MYanello does this mean I need to reflash my Sonoff back from 4.4 to 4.3.1? I also need to revert Multipan flasher from 0.2.2 to 0.2.1?
If it ain't broke, don't fix it. But I couldn't get z2m up when I was running 4.4.
darkxst
commented
7 months ago If it ain't broke, don't fix it.
Its not optional. Firmware must match what the multiprotocol addon is using 4.4.x firmware will not work with 4.3.x multiprotocol addon. Or vise versa. For now run 4.3.1, when the multiprotocol changelog mentions upgrading to 4.4.x again then you need to update firmware again.
github-actions[bot]
commented
6 months ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
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
System Health information
System Information
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 | 48Home 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 | okHome 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 | storageRecorder
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.2Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response