zigbeeFirmware
zigbeeFirmware copied to clipboard
xsp1989
EmberZNet 7.3.2.0/7.4.0.0 firmware
@xsp1989 do you expect to compile new version with 7.3.2 or 7.4.0?
Just a small apart dunno if this is the correct place to post it... this new versions working together with last z2m should support completely zgp devices?
Thanks
@xsp1989 +1 but for newer Zigbee EmberZNet 7.3.3.0 (GSDK 4.3.3.0) and EmberZNet 7.4.1.0 (GSDK 4.4.1.0) respectivly:
https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.3.3
https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-7.3.3.0.pdf
https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.4.1
https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-7.4.1.0.pdf
MattWestb has summarized the included fixes for Zigbee EmberZNet NCP and RCP here:
https://github.com/zigpy/zigpy/discussions/894#discussioncomment-8782766
https://github.com/zigpy/zigpy/discussions/894#discussioncomment-8686629
He mentions there that his guess is EmberZNet 7.3.3.0 might be the last bug fix for and then it will only get EmberZNet 7.3.3.x security updates. While the EmberZNet 7.4.x.x will continue to get new bug fix releases.
@estimadarocha FYI, you can also get newer unofficial firmware releases here:
https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds
Personally, I like to use the old version. The new version usually has new functions, and the new functions usually bring new bugs. Then the next few versions are to fix the bugs for this version. Of course, it is also possible It is to add new features, fix bugs, and add new bugs at the same time (joke: coding bug).
In terms of usage, a specific version may have a known problem, and you will know how to solve or circumvent the problem, so the problem may not be a problem. If a new problem arises, you may need to reanalyze the problem in order to solve it, or you can just complain.
A reason for updating is that they drop support for older versions in zigbee2mqtt
https://github.com/Koenkk/zigbee2mqtt/discussions/21462
I have an issue with Tims Firmware there
https://github.com/darkxst/silabs-firmware-builder/issues/84#issuecomment-2090962854
A reason for updating is that they drop support for older versions in zigbee2mqtt
I've not seen anything that they have dropped ezsp backend, however the new ember backend is currently only available with 7.4.x firmwares.
I can confirm @sstidl's comment from my logs
[2024-05-05 17:55:49] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
after chaing and attempting start i get
[2024-05-05 18:17:33] info: z2m: Starting Zigbee2MQTT version 1.37.0 (commit #46f34c8)
[2024-05-05 18:17:33] info: z2m: Starting zigbee-herdsman (0.45.0)
[2024-05-05 18:17:34] info: zh:ember: ======== Ember Adapter Starting ========
[2024-05-05 18:17:34] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-05-05 18:17:34] info: zh:ember:uart:ash: ======== ASH NCP reset ========
[2024-05-05 18:17:34] info: zh:ember:uart:ash: Socket ready
[2024-05-05 18:17:34] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-05-05 18:17:35] info: zh:ember:uart:ash: ======== ASH connected ========
[2024-05-05 18:17:35] info: zh:ember:uart:ash: ======== ASH started ========
[2024-05-05 18:17:35] info: zh:ember:ezsp: ======== EZSP started ========
[2024-05-05 18:17:35] error: z2m: Error while starting zigbee-herdsman
[2024-05-05 18:17:35] error: z2m: Failed to start zigbee
[2024-05-05 18:17:35] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-05-05 18:17:35] error: z2m: Exiting...
[2024-05-05 18:17:35] error: z2m: Error: NCP EZSP protocol version of 8 does not match Host version 13
at EmberAdapter.emberVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1651:19)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:802:9)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2660:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:124:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:108:27)
at start (/app/index.js:107:5)
Using '/app/data' as data directory
I did manage to switch to Tims firmware: https://github.com/darkxst/silabs-firmware-builder/issues/84#issuecomment-2094078288
Ahhhh @sstidl i'm using a one of these https://templates.blakadder.com/ewelink_ZB-GW03.html not sure how i'd go about flashing it
Ahhhh @sstidl i'm using a one of these https://templates.blakadder.com/ewelink_ZB-GW03.html not sure how i'd go about flashing it
Same here. I got this one from AliExpress https://a.aliexpress.com/_EGwHi11
Not sure about flashing procedure and which new firmware I have to choose to fix the error
using a one of these https://templates.blakadder.com/ewelink_ZB-GW03.html
I believe this requires signed firmware, so I am unable to include in my firmware builder.
I built a 7.4.3.0 firmware today. There are still some problems. If there are no problems, I will release it as soon as possible.
@jonny190 If you purchased the tasmota version, you need to use the signature firmware to refresh the zigbee firmware. If it is the ewelink version, you need to use the serial port to flash it. For details, please see https://thehelpfulidiot.com/a-wired-sonoff-zigbee-alternative
A reason for updating is that they drop support for older versions in zigbee2mqtt
I've not seen anything that they have dropped
ezspbackend
Z2M have not dropped the support for it but they marked ezsp adapter as deprecated, see -> https://github.com/Koenkk/zigbee-herdsman/pull/1039
Deprecated means it will no longer maintained and that users now have a grace period to migrate to the new ember adapter.
Their new ember adapter is suppose to fully replace old ezsp adapter but it does require EmberZNet 7.4.0.0 or later firmware.
- https://github.com/Koenkk/zigbee-herdsman/pull/918
- https://github.com/Koenkk/zigbee2mqtt/discussions/21462
PS: Note that all Silicon Labs based adapters are still "experimental" in Z2M -> https://www.zigbee2mqtt.io/guide/adapters/
Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released
https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware
Hi, thank you for updated this. Any chance for router firmware get update? I'm using it with https://github.com/digiblur/Tasmota/tree/development/zigbee_router
Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released
https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware
@xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks
Hi, thank you for updated this. Any chance for router firmware get update? I'm using it with https://github.com/digiblur/Tasmota/tree/development/zigbee_router
There are no plans to update the router at the moment. For the router, updating the firmware will not gain any new features.
Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware
@xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks
If you are connecting to Z2M or ZHA through TCP, you need to switch the IO configuration to Zigbee RX and Zigbee TX.
make sense, but would it be possible to revert the IO configuration later to TCP to be used as before or would this cause any issue?
El mar, 28 may 2024 a las 9:53, xsp1989 @.***>) escribió:
Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware
@xsp1989 https://github.com/xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks
If you are connecting to Z2M or ZHA through TCP, you need to switch the IO configuration to Zigbee RX and Zigbee TX.
— Reply to this email directly, view it on GitHub https://github.com/xsp1989/zigbeeFirmware/issues/49#issuecomment-2134568421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEGEO7NDAFBURA6FVSIR7TZEQZYZAVCNFSM6AAAAABC7L3IGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU3DQNBSGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Z2M have not dropped the support for it but they marked
ezspadapter as deprecated, see -> Koenkk/zigbee-herdsman#1039Deprecated means it will no longer maintained and that users now have a grace period to migrate to the new
emberadapter.Their new
emberadapter is suppose to fully replace oldezspadapter but it does require EmberZNet 7.4.0.0 or later firmware.
FYI, some more information on this as no longer listed as experimental in Zigbee2MQTT:
As I understand, you need to have upgraded to at least EmberZNet 7.4.x firmware version or later to use the new ”ember” driver/adapter in Zigbee2MQTT, but from what I read it is suggested to first upgrade to EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter as it sounds like a migration to the new ”ember” driver will go smoother if already have had the old ”ezsp” driver/adapter working EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter in Zigbee2MQTT.
Again, recommend read and ask more specific questions in Zigbee2MQTT’s own community forum on GitHub after you done more research. The multi-step process you need to do depends on your specific setup and you need to ask in the Zigbee2MQTT community if you need step-by-step that applies to your setup. The process for actually updating firmware version will not be different.
Suggest start by reading and try following this article regarding migrating Zigbee2MQTT from the ezsp adapter to the new ember adapter:
- https://smarthomescene.com/guides/how-to-use-ember-driver-with-efr32mg21-zigbee-adapters/
Summery; ezsp adapter is now deprecated in Zigbee2MQTT’s zigbee-herdsman library, which means that the Zigbee2MQTT developers are by doing so strongly recommending users to upgrade and migrate to ember adapter, and that migration might require a multi-step process depending on what EmberZNet firmware version you are using today. Users that continues to use the ezsp adapter will for now simply get a warning in their logs that they are using a deprecated adapter, however it will not stop working.
Note! If you have a EFR32MG12/MGM12 series, EM35x/EM35xx or ETRX35x based adapter then you need to buy a newer adapter. If you want to migrate to newer Silicon Labs based Zigbee Coordinator today then you should consider getting an EFR32MG2x (EFR32MG21 or EFR32MG24) based USB radio dongle, (though technically you can even upgrade EFR32MG13):
- https://www.zigbee2mqtt.io/guide/adapters/
- https://www.zigbee2mqtt.io/guide/adapters/emberznet.html
For reference see:
- https://github.com/Koenkk/zigbee-herdsman/pull/918
- https://github.com/Koenkk/zigbee2mqtt/discussions/21462
- https://github.com/Koenkk/zigbee2mqtt/discussions/21462#discussioncomment-8510320
- https://github.com/Koenkk/zigbee-herdsman/pull/1039
PS: "Deprecated" does not mean that the ezsp adapter will be removed yet, instead it means you are discouraged from using it as it is being phased out and replaced by the newer ember adapter (which is not compatible with older firmware or all hardware).
- https://en.wikipedia.org/wiki/Deprecation#Software
- https://techterms.com/definition/deprecated
- https://www.baeldung.com/cs/deprecated-vs-obsolete
As I understand, you need to have upgraded to at least EmberZNet 7.4.x firmware version or later to use the new ”ember” driver/adapter in Zigbee2MQTT, but from what I read it is suggested to first upgrade to EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter as it sounds like a migration to the new ”ember” driver will go smoother if already have had the old ”ezsp” driver/adapter working EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter in Zigbee2MQTT.
@xsp1989 any chance you can also release a 7.3.x version to make migrating smoother for Zigbee2MQTT users? They are recommending to first upgrade to a 7.3.x version before upgrading to 7.4.x version as otherwise backup and restore will not fully work
Thanks but after switching IO config to Zigbee TX/RX I got the same outcome....invalid signature :(
El mar, 28 may 2024 a las 9:53, xsp1989 @.***>) escribió:
Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware
@xsp1989 https://github.com/xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks
If you are connecting to Z2M or ZHA through TCP, you need to switch the IO configuration to Zigbee RX and Zigbee TX.
— Reply to this email directly, view it on GitHub https://github.com/xsp1989/zigbeeFirmware/issues/49#issuecomment-2134568421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEGEO7NDAFBURA6FVSIR7TZEQZYZAVCNFSM6AAAAABC7L3IGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU3DQNBSGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Thanks but after switching IO config to Zigbee TX/RX I got the same outcome....invalid signature :( El mar, 28 may 2024 a las 9:53, xsp1989 @.>) escribió: … Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware @xsp1989 https://github.com/xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks If you are connecting to Z2M or ZHA through TCP, you need to switch the IO configuration to Zigbee RX and Zigbee TX. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEGEO7NDAFBURA6FVSIR7TZEQZYZAVCNFSM6AAAAABC7L3IGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU3DQNBSGE . You are receiving this because you are subscribed to this thread.Message ID: @.>
I have tested it and it can be updated normally. ZB-GW03 should use signed firmware. If it still doesn't work, you can try to restore Tasmota to factory settings and then upgrade.
As I understand, you need to have upgraded to at least EmberZNet 7.4.x firmware version or later to use the new ”ember” driver/adapter in Zigbee2MQTT, but from what I read it is suggested to first upgrade to EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter as it sounds like a migration to the new ”ember” driver will go smoother if already have had the old ”ezsp” driver/adapter working EmberZNet 7.3.x firmware version while still using the old ”ezsp” driver/adapter in Zigbee2MQTT.
@xsp1989 any chance you can also release a 7.3.x version to make migrating smoother for Zigbee2MQTT users? They are recommending to first upgrade to a 7.3.x version before upgrading to 7.4.x version as otherwise backup and restore will not fully work
The unsigned firmware was released as 7.3.1.0. Today I updated the signed version for ZB-GW03.
I have tested it and it can be updated normally. ZB-GW03 should use signed firmware. If it still doesn't work, you can try to restore Tasmota to factory settings and then upgrade.
Experiencing the same problem, with a clean Tasmota installation.
Any specific steps which I might have missed?
@robvanoostenrijk, I was able to upload the firmware on my https://templates.blakadder.com/ewelink_ZB-GW03.html following the steps below:
1 - Make a configuration backup 2 - Reset Tasmota configuration 3 - Upload the new firmware: https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/ZigbeeBridge_SM-011-signed/ncp-uart-sw_7.4.3.0_115200.ota 4 - Restore the backup configuration file
Thanks but after switching IO config to Zigbee TX/RX I got the same outcome....invalid signature :( El mar, 28 may 2024 a las 9:53, xsp1989 @.>) escribió: … Firmware 7.4.3.0 has been updated, signed and unsigned versions have been released https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware @xsp1989 https://github.com/xsp1989 thanks for that. I've tried to upgrade the firmware for a GW03, however it prompt invalid signature. Is there any specific process to upgrade this firmware in this device? Any info would be appreciated. Thanks If you are connecting to Z2M or ZHA through TCP, you need to switch the IO configuration to Zigbee RX and Zigbee TX. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEGEO7NDAFBURA6FVSIR7TZEQZYZAVCNFSM6AAAAABC7L3IGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU3DQNBSGE . You are receiving this because you are subscribed to this thread.Message ID: _@**.**_>
I have tested it and it can be updated normally. ZB-GW03 should use signed firmware. If it still doesn't work, you can try to restore Tasmota to factory settings and then upgrade.
@xsp1989 Just to confirm, the problem in my case was how I downloaded the ota file as it was 407kB. Just downloaded it again and it is 247,8kB and I upgraded it without reset tasmota configuration and after switch to ember driver, everything was up without issues, so THANKS!
For others with the same issue, pls validate the size of your downloaded file as an additional check.
Update for others facing my issue. I was running my ZB-GW03 using the tasmota-zbbrdgpro build for a number of months using TCP bridge (which worked just fine, since Zibee2MQTT was communicating with the EZSP controller directly).
However, turns out it is not the correct Tasmota build with EZSP support built in, so Tasmota was not able to communicate with the EZSP controller to execute an upgrade.
I was able to upgrade to the new EZSP firmware successfully after flashing Tasmota tasmota32-zigbeebridge from
https://github.com/tasmota/install/blob/firmware/firmware/unofficial/
RSL: RESULT = {"ZbState":{"Status":1,"Message":"EFR32 EZSP booted","RestartReason":"Power-on","Code":2}}
RSL: RESULT = {"ZbState":{"Status":55,"Version":"7.4.3.0","Protocol":13,"Stack":2}}
@robvanoostenrijk , quick question, I was able to update the bridge into V13 as you pointed out (I had to first enable Zigbee2Tasmota mode as module was disabled in TCP mode and then flash the zigbee firmwares) but I am not able to use the latest version of the bridge with z2m because of many errors. How did you sort it out?
I am not able to use the latest version of the bridge with z2m because of many errors. How did you sort it out?
Such questions about Z2M usage be posted to the Zigbee2MQTT commmunity, see:
https://github.com/Koenkk/zigbee2mqtt/discussions
And
https://github.com/Koenkk/zigbee2mqtt/issues/
I am coming from z2m repository which asks me to reset nvm from this repository and I failed.
Moreover, I am asking a specific person, let's see.