USB extension cable (Nice to have so you can work with the stick farther from the USB port)īackup up the external NVM (network and node info)ĭownload the Z-Stick Gen5 Backup software and run zwave_500.exe Stiff small guage wire to short reset pin #Reset aeon labs z stick Pc#PC Controller - Can be used for nvm backups and/or to verify new firmware version Z-Stick Gen5 Backup Software - Used to backup external NVM Z-Wave Programmer - Backup and flash new firmware Z-Wave SDK - Contains controller firmware hex files #Reset aeon labs z stick upgrade#Even if this is not the case, you could manage your own backups yourself using PC software.Īny NVM backups taken before the upgrade seem to restore just fine to the new version, so you can keep your network/node settings when upgrading. Bruce had mentioned that the stick was missing functionality that would allow this to work, and this appears to be it. #Reset aeon labs z stick serial#If Hubitat ever opens up manual radio backup/restores within the UI using the raw nvm files, the new serial api would potentially allow backups/restores to this stick. 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. 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.Transaction report information on received frames.The api and format of the backup are different though vs using the official api method here. 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. I have successfully cloned a stick using this method. A side note: you can backup the stick already with tools like Z-Stick Gen5 Backup Tool, or the ZMESerialUpdater tool.Again, unless Hubitat adds support, these will be no good to you unless you run this on a different platform such as the Z-Wave official PC controller, or a project like OpenZwave. This opens up a number of features to the stick. After you upgrade you will be on version 6.82 which is the latest available. I couldn't find anyone that had attempted to upgrade the Z-Wave portion of this stick before, so I did some research into the datasheet for the SD3503 that powers the Z-Wave portion of the stick, and successfully found a way to upgrade it. The Nortek stick runs a Z-Wave library version from SDK version 6.51.06 from 2014-2015. While unlikely, the hardware could fail while flashing rendering it useless. If you click on an erase button by accident in the programmer, you will lose your calibration data for the stick and render it useless, unless you took an internal NVM backup (this is different from external NVM backups from tools like the Z-Stick Gen5 tool or ZMESerialUpdater). While the firmware is backwards compatible, and I haven't had any issues running it, Hubitat will not support any issues as a result of modifications done. Once you upgrade, you can't downgrade the chip to the previous firmware version as I haven't been able to source a firmware hex file from sdk version 6.51.06 and the chip has read protection enabled. If you touch a different part of the board you could short it out and destroy the chip. To flash the firmware you have to source a pin on the chip to ground with a free wire. No new features will be added to Hubitat unless they open up support to them in the older Z-Wave stack which they have said is end of life. Most people don't need to do this, and should not attempt this. This is only for the Nortek combined Z-Wave/Zigbee stick. Note: If you want to just backup/restore/clone the stick, just use the ZStick G5 tool from the Sofware Prep Sectionįor flashing, if you have a non-us Hubitat that came with two separate sticks, this will not work for you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |