If you can find firmware, then yes, new firmware is really essential as the firmware in these devices is now very old and it will not support many of the newer devices on the market (ie Zigbee 3.0 devices). You may find devices join the network, then leave again a few seconds later as a result of this.
I dont have one of these but some time back someone here told me there was no bootloader installed - if that’s incorrect then flashing newer firmware would be highly desirable.
Great find! I too was under the impression that this coordinator couldn’t be upgraded. I’m off to upgrade as well. I like they provide a docker container to do the upgrade. Definitely saves some effort.
My zigbee network is small right now and doesn’t do much where I would notice a difference. It’s basically five smart plugs, three of which are not even in use, one drives a humidifier when the humidity drops too low (which doesn’t often happen in the summer) and the other controls a lamp which is automated. I don’t see anything different in the logs.
I didn’t really expect the performance to improve with the flashing. I did it more to support newer devices and such.
I would not in general expect reliability to change. The big reason to flash to a newer version is compatibility with newer devices. The old firmware will not work with many new devices being sold now - otherwise there is nothing really wrong with the older firmware.
This link suggested a much easier pad on the stick to short and it was still fiddly, but doable.
I now am running a much more current Z-Wave firmware on my HUSBZB-1 stick
According to the guide, the specific Z-Wave features mentioned as enabled are
Updated Z-Wave Library features
New Serial API features (tested)
Official NVM backup/restore functions
A side note: you can backup the stick already with tools like Z-Stick Gen5 Backup Tool, or the ZMESerialUpdater tool. I have successfully cloned a stick using this method. There is also a method to backup the zigbee portion with a different tool, which I’ll probably make a guide for in the future. The api and format of the backup are different though vs using the official api method here.
Transaction report information on received frames
RSSI info, routes taken, latency
SmartStart (untested)
S2 encyption (untested)
Can flash different Z-Wave firmwares
Official Bridge/Static firmwares
The stick could be used with Z/IP gateway projects as that requires a bridge firmware, and series 700 chips only have bridge firmware available to them. This is/was the go forward for certified Z-Wave controllers, but I’ve heard rumors that the serial api could be certified for use with 700 series chips in the future.
Zniffer firmware.
Allows you to sniff z-wave packets
So… are any of these features implemented or interesting in OH3?