Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Silabs emberznet 7.4.4.0 and 8.0.0 versions #123

Open
IgnacioHR opened this issue Sep 12, 2024 · 24 comments
Open

Support for Silabs emberznet 7.4.4.0 and 8.0.0 versions #123

IgnacioHR opened this issue Sep 12, 2024 · 24 comments

Comments

@IgnacioHR
Copy link

It looks like there is a new version 7.4.4 (and there is also an 8.0.0) available.

Should they be added to firmware_build folder?

https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-7.4.4.0.pdf
https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-8.0.0.0.pdf

Rgds

@Xploder
Copy link

Xploder commented Sep 14, 2024

7.4.4 is available in the 4.4.4 branch and currently in testing
https://github.com/darkxst/silabs-firmware-builder/tree/4.4.4

8.0.0 had a serious showstopping bug causing instability that was supposedly fixed with 8.0.1 (https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-8.0.1.0.pdf)

@darkxst
Copy link
Owner

darkxst commented Sep 14, 2024

I will add 8.0.1 builds in the next week

@Xploder
Copy link

Xploder commented Sep 20, 2024

New version 8.0.2 seems to have fixed LQI!

https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-8.0.2.0.pdf

@Xploder
Copy link

Xploder commented Sep 29, 2024

In the meantime we can grab a 8.0.2 based firmware here https://github.com/Nerivec/silabs-firmware-builder/releases

@IgnacioHR
Copy link
Author

I updated my coordinator to 8.0.2 yesterday and everything works the same as before. Means, AFAICS nothing is broken with 8.0.2

@MSL-DA
Copy link

MSL-DA commented Oct 10, 2024

I updated my coordinator to 8.0.2 yesterday and everything works the same as before. Means, AFAICS nothing is broken with 8.0.2

Same experience here

Zigbee2MQTT docker> 1.40.2-dev
Home Assistant > 2024.10.1
ZBDongle-E > 8.0.2

@darkxst
Copy link
Owner

darkxst commented Oct 20, 2024

I have uploaded v8.0.2 build here for all supported adapters:
https://github.com/darkxst/silabs-firmware-builder/releases/tag/v20241020-beta

@Nosnahc
Copy link

Nosnahc commented Oct 20, 2024

@darkxst
{C36617A7-F8E8-4603-A2E4-C2CE0099A439}
Don't work for me with zbdonglee_zigbee_ncp_8.0.2.0_sw_flow_115200.gbl
(but work if I flash 7.4.4)
I'm maybe doing this wrong.

@darkxst
Copy link
Owner

darkxst commented Oct 20, 2024

Web flasher needs to be updated to be able to read the installed v8 firmware details (universal-silabs-flasher cli tool can read it though). You should just try test it Z2M etc

@dspalu32
Copy link

v8.02 working well for me on two separate z2m setups. (zb-gw04-1v2_zigbee_ncp_8.0.2.0_115200.gbl)

The "Silicon Labs Flasher" HA add-on doesn't accept the v8 .gbl as a custom firmware file - where v7.x used to work - but a manual update using your webflasher works as expected. The python silabs flasher was OK for v8 also. The error from the HA add-on related to the firmware having v2 manifest format, where the add-on only supports v1. Presumably it does a cross-check of the target rather than flashing blindly, and will itself need an update.

Thanks!

@darkxst
Copy link
Owner

darkxst commented Oct 20, 2024

Yes, Silabs flasher will also need an update to deal properly with v8 firmware

@wastez
Copy link

wastez commented Oct 22, 2024

You can use ember-zli to flash the firmware, i have done this for my dongle-e because the silabs flasher doesn’t work.

@darkxst
Copy link
Owner

darkxst commented Nov 2, 2024

Updated builds for 8.0.2 here:
https://github.com/darkxst/silabs-firmware-builder/releases/tag/20241102

@lyonelf
Copy link

lyonelf commented Nov 3, 2024

which file i must use for the dongle E in coordinator mode inside Jeedom ?

@MSL-DA
Copy link

MSL-DA commented Nov 3, 2024

which file i must use for the dongle E in coordinator mode inside Jeedom ?

https://github.com/darkxst/silabs-firmware-builder/releases/download/20241102/zbdonglee_zigbee_ncp_8.0.2.0_sw_flow_115200.gbl (Zigbee)

@tootla
Copy link

tootla commented Nov 4, 2024

Updated builds for 8.0.2 here: https://github.com/darkxst/silabs-firmware-builder/releases/tag/20241102

@darkxst Based on your practical experience, what are the differences between Gecko SDK and Simplicity SDK?

@darkxst
Copy link
Owner

darkxst commented Nov 4, 2024

Simplicity SDK is just the evolution of Gecko SDK, essentially just a name change but also dropping support for older chips (only Elelabs devices affected, of the device I build for). However that resulted in lots of changes in itself, so its hard to pick out actual practical improvements in v8.

Otherwise usual applies if you want the latest and greatest install v8.0.2, if you just want something stable stick with v7.4.x series for now as that is relatively stable and mature at this point.

@IgnacioHR
Copy link
Author

Closing as completed! Thanks everyone

@acommuni
Copy link

acommuni commented Jan 16, 2025

After firmware update (Sonoff Dongle E -> NCP 8.0.2.0 | HomeAssistant with Z2M) there were some errors with OTA requets but after a switch off/switch on, no more issues with OTA requets but errors with interviews requests (see logs below). Switch back to 7.4.5.0 : https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.5.0-zbdonglee-115200.gbl

[2025-01-16 09:43:35] error: z2m: Request 'zigbee2mqtt/bridge/request/device/interview' failed with error: 'interview of 'E1 4 Bureau Sondes' (0x44e2f8fffe1a9c32) failed: Error: Interview failed because can not get active endpoints ('0x44e2f8fffe1a9c32')'
[2025-01-16 09:43:35] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/interview', payload '{"data":{},"error":"interview of 'E1 4 Bureau Sondes' (0x44e2f8fffe1a9c32) failed: Error: Interview failed because can not get active endpoints ('0x44e2f8fffe1a9c32')","status":"error","transaction":"1id0m-1"}'
[2025-01-16 09:44:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/E1 4 Prise Accessoires', payload '{"child_lock":"UNLOCK","countdown":0,"current":0.05,"energy":6.88,"indicator_mode":"off/on","linkquality":164,"power":0,"power_outage_memory":"restore","state":"ON","update":{"installed_version":192,"latest_version":192,"state":"idle"},"voltage":236}'
[2025-01-16 09:44:07] error: zh:ember:uart:ash: Received ERROR from adapter, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2025-01-16 09:44:07] error: zh:ember:uart:ash: ASH disconnected | Adapter status: ASH_NCP_FATAL_ERROR
[2025-01-16 09:44:07] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2025-01-16 09:44:07] error: zh:ember: Adapter fatal error: HOST_FATAL_ERROR
[2025-01-16 09:44:07] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Total frames: RX=150, TX=213
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: DATA frames : RX=137, TX=62
[2025-01-16 09:44:07] info: zh:ember:uart:ash: DATA bytes : RX=3253, TX=1089
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Retry frames: RX=11, TX=1
[2025-01-16 09:44:07] info: zh:ember:uart:ash: ACK frames : RX=0, TX=149
[2025-01-16 09:44:07] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: CRC errors : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Comm errors : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Length < minimum: RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Length > maximum: RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Bad controls : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Bad lengths : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Out of buffers : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Retry dupes : RX=11
[2025-01-16 09:44:07] info: zh:ember:uart:ash: Out of sequence : RX=0
[2025-01-16 09:44:07] info: zh:ember:uart:ash: ACK timeouts : RX=1
[2025-01-16 09:44:14] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/E1 4 Prise Accessoires', payload '{"child_lock":"UNLOCK","countdown":0,"current":0.05,"energy":6.88,"indicator_mode":"off/on","linkquality":164,"power":0,"power_outage_memory":"restore","state":"ON","update":{"installed_version":192,"latest_version":192,"state":"idle"},"voltage":236}'
[2025-01-16 09:44:17] error: zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=60 Len=10].

@acommuni
Copy link

@darkxst
Copy link
Owner

darkxst commented Jan 17, 2025

8.1.0 release is buggy, likely will wait for 8.1.1 before releasing this.

@acommuni
Copy link

acommuni commented Feb 9, 2025

@darkxst
Copy link
Owner

darkxst commented Feb 11, 2025

Initial builds... I have had to disable software flow control on all devices that lack hw flow control.

https://github.com/darkxst/silabs-firmware-builder/releases/tag/20250211-Next

@acommuni
Copy link

acommuni commented Feb 23, 2025

With 8.0.2, It works well for OTA update which takes more than 15mn whereas it does not works with firmware 7.4.5.0 or 7.4.4.0. But interview is not working for some devices (Sonoff SNZB-02D), it is better than previously because no interview was working. This time, reconfigure is not working for Sonoff SNZB-02D. (It is working working with 7.4.5)

The only log is the following for interview :

[2025-02-23 18:43:16] error: z2m: Request 'zigbee2mqtt/bridge/request/device/interview' failed with error: 'interview of 'XXXXXXXXXXXXXXX' (0xYYYYYYYYYYYYYYYYYY) failed: Error: Interview failed because can not get active endpoints ('0xYYYYYYYYYYYYYYY')'

For reconfigure :

[2025-02-23 18:48:19] error: z2m: Failed to configure 'XXXXXXXXXXXXXXX', attempt 1 (Error: Bind 0xYYYYYYYYYYYYYYY/1 genPowerCfg from '0x7cc6b6fffefb44df/1' failed (Delivery failed for '33960'.)
at EmberOneWaitress.deliveryFailedFor (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31)
at EmberAdapter.onMessageSent (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:457:42)
at Ezsp.emit (node:events:524:28)
at Ezsp.ezspMessageSentHandler (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5055:14)
at Ezsp.callbackDispatch (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:746:26)
at Ezsp.onAshFrame (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:396:22)
at UartAsh.emit (node:events:524:28)
at Immediate. (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1171:45)
at processImmediate (node:internal/timers:491:21))
[2025-02-23 18:48:19] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{},"error":"Failed to configure (Bind 0xYYYYYYYYYYYYY/1 genPowerCfg from '0xZZZZZZZZZZZZZZZ/1' failed (Delivery failed for '33960'.))","status":"error","transaction":"b4qax-5"}'

How can I help ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants