Thank you very much for all the job done.
Oh lordy lordy - it’s Summer ! and I still have an eye on this thread. So…
Testing of the Z2M firmware has been full on since my last post. My optimism back in April was short lived as everything collapsed soon after so it was back to the drawing board and back to Texas Instruments for their input once again. A few more iterations of the Firmware and I think it’s sorted. I have a version of Firmware that’s been running for over two weeks now, rock solid and no device drop-offs.
And perhaps more importantly for this thread - The BRT-100 TRV’s seem to be responding correctly at last !
It’s not my call as to when this Firmware will go on general release but it if things continue to stable then it must be soon!
I will post back here when I have a release date.
Keep the faith !
1 Like
At least it’s still summer ! - I have news !
With massive thanks to @koenkk as it is he who has worked tirelessly to get us to this point. He has re-written about 30 (yes 30) versions of the Z2M firmware which we have jointly tested over the last few months.
The new FW is now published as a testing release and barring any issues between now and then will go live on 24th August 2024.
You can download the FW here:
https://github.com/user-attachments/files/16203584/20240710.zip
Bear in mind the FW was not re-written to specifically fix any issues with the BRT-100-TRV but I can confirm my issues with these devices has literally vanished since I updated.
If you want to get involved with the discussions regarding this FW please take a look here:
Thanks for bearing with us over this protracted period and I hope it works for you too !
Good Luck !
Sorry for long delay in responding. I don’t know if it Open Source as I’m not the author. Have a look at my other recent post and follow the Git Hub thread link. You may be able to find out from there.
Hey all, can I just say it’s a relief to find this post and see I’m not the only one suffering this issue. I’ve had the Moe TRVs two years and had exactly the same random POST unresponsiveness.
I see there is/will be a new Z2M firmware, has it been released yet as I’ve not seen it in OTA.
I see the GitHub link. Is it safe to flash and stable?
Many thanks for all your hard work on this as reliable TRVs is the ultimate dream!
Hey James, welcome to the club !
Yes, I too suffered to the point of taking a large heavy implement to these units at one point.
I was involved for literally months of testing with the author to get this firmware sorted although
bear in mind it wasn’t re-written to specifically fix this issue but it does seem to have done just that.
My advice would be to upgrade to this FW right now ! - Yes, it’s officially released, it’s safe and stable (from my personal experience)
One thing I note (apologies if I appear to be doubting you): You mention OTA ? - This is FW is nothing to do with OTA. It’s a Z2M FW to be flashed onto your Zigbee stick). Don’t go anywhere near upgrading the TRV’s themselves with OTA - there is a very good chance you’ll end up with lots of pretty little white bricks !
Hope that helps.
1 Like
Hi Nick,
Arh thank you clarify, I did question myself about what the firmware was for, especially as I’d read OTA for this TRV had been disabled due to rogue FW and bricked devices. I’ve read the post wrong.
I actually use the Skyconnect (now know as the Home Assistant Connect ZBT-1) with Z2M. Do you know of a fix for me?
One temporary fix I have which seems to work for me, is restart the Z2M service.
Many thanks for the reply, much appreciated
Hi James,
Apologies for the delay, I have been away on vacation.
I’m sorry I don’t know of a fix for the ZBT-1. The new FW I’ve been involved with is only for the Z-Stack based dongles - i.e. those with a Texas Instruments chipset. I think yours has a Silicon Labs chipset.
I also found a reboot of Z2M or drop out the batteries of the BRT-100 would temporarily fix the issue - not exactly fun though.
Your issue seems so similar to mine I can’t believe there isn’t a common thread running though this problem, across many types of coordinators.
The only useful pointers I can give you is to have a trawl through GitHub and see if you can locate anything similar to your issues. You might want to try contacting @koenkk via GitHub as he is the author and guru of all things Z2M.
Hope that helps !