You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UPDATE! FYI; Nerivec has now informed beta-test users of the Zigbee2MQTT Edge version (which tracks the dev branch of Zigbee2MQTT) that the EmberZNet 8.1.0 firmware looks to be buggy with zigbee-herdsman, where specifically software flow control does not seem to work properly when using EmberZNet 8.1.0 firmware with Zigbee2MQTT, (so their current recommendation for Zigbee2MQTT is to stick with 8.0.2 and newer 8.0.x releases for those who want to go with any EmberZNet 8.x.x version). He has posted more information in a bug-report to upstream here:
bellows support for EZSP protocol version incremented to EZSP v16 in Zigbee EmberZNet v8.1.0.0 (from Simplicity SDK 2024.12.0):
https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-8.1.0.0.pdf
Note! EZSP protocol version went from 0x0e (14) to 0x10 (16) with this EmberZNet v8.1.0.0 release, seems they jumped over v15?
Nerivec has experimental firmware builds ("release appears mostly centered around firmware bug fixing, very few protocol changes."):
https://github.com/Nerivec/silabs-firmware-builder/actions/runs/12538101751
Known issues:
Sonoff ZBDongle-E dongle is not working with Nerivec's firmware build of zigbee_ncp firmware according to Nerivec himself. See:
UPDATE! FYI; Nerivec has now informed beta-test users of the Zigbee2MQTT Edge version (which tracks the dev branch of Zigbee2MQTT) that the EmberZNet 8.1.0 firmware looks to be buggy with zigbee-herdsman, where specifically software flow control does not seem to work properly when using EmberZNet 8.1.0 firmware with Zigbee2MQTT, (so their current recommendation for Zigbee2MQTT is to stick with 8.0.2 and newer 8.0.x releases for those who want to go with any EmberZNet 8.x.x version). He has posted more information in a bug-report to upstream here:
The text was updated successfully, but these errors were encountered: