It is newer IKEA device firmware updates that are known to cause issues so just do not update firmware on your IKEA devices unless you are already having major problems with them, (you really should not try to fix what is not broken, at least not when it comes to IKEA devices Zigbee firmware as IKEA’s newer firmware is known to have problems), but that is enough discussion about that in this thread, (please start a new thread if you want to discuss that more).
As for this Zigbee Coordinator adapter (which is what this thread is only about), as long as you follow other best practices then the latest Z-Stack Zigbee Coordinator version from Koenkk’s master branch is generally what is recommend for all CC2652/CC2652P based radio adapters, see → Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin at master · Koenkk/Z-Stack-firmware · GitHub
Again, first also make sure that you do your best to try to follow follow all other best practice tips as per this guide as it tella how to avoid the root causes for most issues and problems most users have if they do not optimize their Zigbee setup. Please start a new thread if you want to discuss that further:
FYI, there is a new experimental Z-Stack 20240710 firmware build available for those with issues in previous release who want to test + preferably also give feedback to the Z-Stack firmware developers:
Other testers have been testing it for three weeks now and most look to be reporting it as stable so far.
If no one reports it as troublesome then that version will likely soon become the next “master” version.
Note! Always remember to do a Zigbee network backup to file before upgrading firmware for restoring.
FYI, Koenkk’s community build of Z-Stack_3.x.0 coordinator 20240710 firmware version has now officially been released as the new “master” which means that is the latest cutting-edge release image available:
While this version now being the new “master” implies that it is mature enough for everyone to start using, but be aware that it does cutting-edge so it has still not been proven to be stable in the long-run, therefore if you stumble into issues you might need to revert to an older firmware version and restore your Zigbee network from a backup (thus you always remember to do a full Zigbee network backup to file before upgrading firmware for restoring!). Not sure how well it has been tested with the ZHA integration and zigpy-znp as Koenkk himself only test it with Zigbee2MQTT (because he is the leas developer of that project).
Note! Regadless of which Zigbee gateway software application that you are using it is common that zstack firmware flashing restore the adapter to factory default and therefore it is generally recommended and best practice to always do a full backup before flashing firmware and then restore that backup directly after flashed the adapter. Personally I always temporary stop/disable my Zigbee gateway software application use zigpy-cli as a stand-alone tool on a other computer for external backup and restore:
As always, flash at your own risk and be prepared to revert to older firmware if not working well for you with your specific devices (and then needing to restore backup from file so save that in a good place).
Again, post feedback on Z-Stack_3.x.0 coordinator 20240710 firmware specific issues on GitHub here: