EZSP current recommended and pending firmware updates for coordinators.

[MattWestb]

I have trying getting all adapters that is used by the community and putting them in one matrix in the wiki page with links to firmware resource for them so user can easy getting one over view of the status.

Some of our coordinators is having getting EZSP 6.7.8.0 firmware with critical bug fixes.

I have trying getting our firmware cooker upgraded firmware and some have successful being made and some is also in production in our systems.
Here is my current status in one matrix:

Coordinator vendor	Model	Hardware mod	Current Recommended	6.7.8.0 Staus
Telegesis	ETRX357USB	EM357	6.6.5.0	Working ✅
Telegesis	ETRX357USB	EM357-LRS	6.6.5.0	Pending 🔲
Telegesis	ETRX357USB	EM357-LRS+8M	6.6.5.0	Pending 🔲
Nortek	HUSBZB-1	EM3581	6.6.5.0	Working ✅
Elelabs	ELU013	EFR32MG13P	6.7.8.0	Working ✅
Elelabs	ELR023	EFR32MG13P	6.7.8.0	Working ✅
EByte	E180-Z120B	EFR32MG1B	6.7.8.0	Working ✅
Sonoff	Zigbee Bridge	EFR32MG21	6.7.8.0	Working ✅
DEFARO	SprutStick Pro	EFR32MG12P	6.7.6.0	Not known ❌
IKEA	Billy EZSP	EFR32MG1P	6.7.8.0	Working ✅
Tuya	TYGWZ01 Smart Gateway	EFR32MG1B	6.5.0.0 (Factory FW)	Working ✅
Elelabs	ELR022	EFR32MG1B	6.3.0	NK ❌
Elelabs	ELU012	EFR32MG1B	6.3.0	NK ❌
Elelabs	EZBPIS	EM357	6.0.0	NK ❌
Elelabs	EZBUSBA	EM357	6.0.0	NK ❌

🔲 = FW cooked / seen but no feedback from cooker / devs.
☑️ = FW being loaded and looks working OK but no OK from devs.
✅ = FW flagged OK from cooker / devs.
❌ = FW not cooked / status is not known.

Status in word:
EM357 One very brave user have flashing it and its looks working OK but its not enough for being recommended.

The rest of the EM35X famely is cooked but not loaded on devices and waiting for confirmation.

Sonoff having one signed and one unsigned firmwares that is loading OK and is flagged as "Relese candidate" from the tasmota devs and i have flageed it as pending.

My IKEA Billy EZSP is running OK for one week and its flagged as working from My.

The Elelabs and EByte have being cooked (of the community) but i dont flagging them as pending without the devs OK.

DEFARO / SprutStick Pro looks that they is coocking self but dont have 6.7.8.0 on the menue.
Its also not clear if they is using the gen 1 or 2 chips from there info.

EDIT: Have pinging the dev and asking if the HW is gen 1 or 2 and is ther have planed on 6.7.8.0 release for ther adapter.

If you is knowing more radio adapters being used with with EZSP plead putting in the wiki linked abow !!

And for ZHA devs: I do only marking my Billy as stabile with 6.7.8.0 and the rest must "someone" saying its OK to changing status to recommended for normal use.
Tasmota we can follow but in the end its ZHA devs that is flagging it OK for ZHA (Is now recommended of tasmota).

I changing the matrix with input from:
EM35X @walthowd if can being loaded OK and working status.
Elelabs and EByte with input from the coockers.

I do not flagging recommended befor @Adminiuga is saying its OK for all devices (Billy exluded) !!

More testing and input is more than welcome!

And large thanks to our devs and brave users that is making all this great thing happening with our systems !!

[MattWestb]

I also recommending putting more structured information in the wiki and then moving the most from the readme.mds from the zigpy and the radio libs and only saying "firmware requirements for running ZHA see wiki" and doing it with notations and not for every named devices than its looks like one large forrest at the moment.

[MattWestb]

Tasmot have changing Sonoff Zigbee bridge to Promote EZSP v6.7.8 as recommended firmware arendst/Tasmota#10695 and have redoing ther firmware upload because many users was having problems loading firmware on it.

Changing the ZHA Wiki to recommended or still waiting ?

I dont posting in our active thread for not making experience getting problems.

Edit: Changed status to recommended.

[MattWestb]

Looks like Gary and walthowd and some very brave users have getting the EZSP 6.7.8.0 up and running in both 57k6 and 115k2 software flow control on the HUSBZB-1 after struggling with all deleted / not updated parts in the SDK for the platform.

Still waiting to getting more positive reports for flagging it as working for not braking our users harts for there bellowed adapter hardware.

[MattWestb]

Tuya ZBGW is up and running on 6.7.8.0 but with software flow control that its little problematic then the hardware is using hardware flow control. I have requested one with HW for getting it working better with ZHA.

[MattWestb]

Flagged all EFR32 as working / stable. Waiting for report of the last EM35X being loaded and stable.

[MattWestb]

Tuya ZBGW have getting one HW flow control firmware (Gary a gen !!!) and running stable so its flagged stable.
But the "tuya app" is not liking the AHS ver 8 and dont like talking the the module as is only understanding AHS ver 7. Hope getting one EZSP 6.5.0.X firmware for getting the tuya app happy so user can going back to "original" state and using it with tuya cloud if they like.
As rescue i have dumped the original FW but its need SWD probe for being flashed.

Edit: Gary have cooked one 6.5.1.0 that working then being flashed with the bootloader then is on 6.7.8.0 and its looks like tuya app is accepting it and can doing its thing OK.

[MattWestb]

Then all large radio adapters is verified to working OK with 6.7.8.0 and only the EM357- LRS and LRS+8M is not verified to being loaded on devices OK and the DEFARO SprutStick Pro have not getting any reaction if they is planing one upgrade, i finding that most of the community radio adapters have successful getting there firmware upgraded to on new and stable version and closing this QA.

[MattWestb]

I have added the legacy Elelabs adapter to the list with known factory firmware version.

Coordinator vendor	Model	Hardware mod	Current Recommended	6.7.8.0 Staus
Elelabs	ELR022	EFR32MG1B	6.3.0	NK ❌
Elelabs	ELU012	EFR32MG1B	6.3.0	NK ❌
Elelabs	EZBPIS	EM357	6.0.0	NK ❌
Elelabs	EZBUSBA	EM357	6.0.0	NK ❌

I also posted on request of the hardware pins they is using in Elelabs update utility GIT.

If the EM357 is using the "Silabs standard" the EM357 version shall working out of the box but i dont like recommending trying it then we dont have any working backup for getting it back too life if its not working.
And its also very likely the EFR32MG1B is working with some of our cooked ones then we can getting the pinning confirmed from Elelabs or user.