I've updated thousands of devices firmware, and this is among the most needlessly extensive installs to accomplish such a simple function. Thank you for this easy walkthrough video.
Hey I don't comment too often on videos but this saved my tail! I can't confirm for the rest of you guys reading the comments of this does work on 800 Zwave usb stick zeus (ZST39 LR) Keep up the good work with these videos it's helping us newbies learn home assistant!
Great video, Mark! I made the change from the old z-wave integration to Z-wave JS a while back and in the process, I upgraded the firmware on my Aeon Labs Z-Stick Gen 5, and I don't see the warning in the UI, so I must be go there. I actually had a Z-Stick 7 at the time, but I wanted to get up and running with my several Z-wave devices as soon as possible, so I didn't install that new stick then. I'm going to have some time in the near future to make the upgrade from the Z-stick Gen 5 to the Z-Stick 7, so I'm wondering if you might have, or do, a video that covers that process??? Thanks ~Frank
I wish I had found this video two hours ago, as I wasted an hour of my life figuring all this stuff out myself (after the built-in HA FW update didn't work at all).... Did the 7.17.x to 7.18.3 update, so hoping it solves all my dead node issues in HA. AT least so far (
Im on 7.19.2 and still getting dead nodes. Im now using an automation to ping nodes as soon as the are dead to revive them. This automation really helped
@@31biga 7.18.3 didn't completely solve my dead nodes problem, but it helped a ton. The zwave network is much "snappier" (devices respond faster), CPU usage on my Nuc dropped by 2/3's, and now I get dead nodes at a rate that is *maybe* 5% as often as it used to be (and they tend to solve themselves). In fact, just to see how often it's happening, I turned off my "ping nodes" that was pinging the nodes every 20 seconds to keep them alive. Now I get a 'dead node' *maybe* once per day, and usually it resolves itself within a few minutes. Not sure why it didn't help you, but it helped me a ton
When I updated, It borked my whole z-wave network. I spent WAY to long diagnosing it before I figured it out: it was set to Europe frequencies by default. As soon As I set it to US in the ZWave-JS UI, everything immediately came back. I guess that's the downside of only having 1 firmware version for all regions. I've never even had to think about it trying the wrong frequencies before.
What version was it? I know it was a problem on 7.19.1 but it should be fixed in 7.19.2. This is the reason why Aeotec did not made 7.19.1 available to download from their website, you had to ask their help desk to get it and the TS agent was supposed to inform you of the possibilities of region change when sending you the firmware file.
I’m yet to test out the 800 series. The issue mentioned is tied specifically to the original 700 series firmware. I would assume they don’t have the issue on the 800 series :)
Mark you did a video on the boundary alarm a while back and one on the alarmo integration, I've got a boundary system which I'm having issues with, I can't get customer support as the company have ceased trading. I know the boundary system uses z wave and I wondered if I could use my boundary sensors and bell boxes via a dongle and create my own system in alarmo, just wondered if this is possible?
Hey Paul. You can add the boundary devices directly to your Z-wave. You will need to reset each device before use. I have done this with the siren, contact sensors and motion sensors. One issue with doing this is that some of the device entities don’t name themselves(e.g the siren has a toggle and other information without a description). You can’t add the boundary control panel to HA which is a shame.
@@MarkWattTech thanks for that Mark I think I'll give it a go, I've been unable to use my boundary alarm for a while now as its had a number of issues flag up on the panel but there's no longer any support so if I can at least utilise the sensors and the sirens that's something and not all my money will have been wasted, the hardware seems to be very good quality, it would have been a shame to junk it.
Is there a reason you don’t use the upgrade option which is visible in your video in the standard Zwave-JS addin to apply the firmware file rather than using the Simplicity Studio 5 option? Great video thanks
I wonder the same thing. I'm on the 7.17.2 and I saw the option on HA to do the update. I wonder if it will work? Does the mesh continue working after the update? Or do i need to pair everything again?
first time I updated I also used pc controller. Second time, I updated using Z-waveJS UI (formerly zwavejs2mqtt) and it worked fine. Take note that the 7.19.x firmwares might change your stick region after updating. You can set it back to the correct region in pc controller or also in Z-waveJS UI
I'm not using the UI. I'm with the default Addon, which also have a button to update firmware. Does it work too and, if frequency is changed, does the zwave js addon allow to change it back?
If using ZWave-JS UI, the Windows software is no longer necessary. [edit: also, I still had network instability with the 7.19.2 firmware and finally dropped back to my 500 series stick. Which, again, was easy thanks to ZWave-JS UI backup/restore.]
![[#59] Z-Wave лучше Zigbee? - тест на дальность работы и обзор устройств](http://i.ytimg.com/vi/dO14dhpVIdk/mqdefault.jpg)
I've updated thousands of devices firmware, and this is among the most needlessly extensive installs to accomplish such a simple function. Thank you for this easy walkthrough video.
Hey I don't comment too often on videos but this saved my tail! I can't confirm for the rest of you guys reading the comments of this does work on 800 Zwave usb stick zeus (ZST39 LR) Keep up the good work with these videos it's helping us newbies learn home assistant!
Great video, Mark! I made the change from the old z-wave integration to Z-wave JS a while back and in the process, I upgraded the firmware on my Aeon Labs Z-Stick Gen 5, and I don't see the warning in the UI, so I must be go there. I actually had a Z-Stick 7 at the time, but I wanted to get up and running with my several Z-wave devices as soon as possible, so I didn't install that new stick then. I'm going to have some time in the near future to make the upgrade from the Z-stick Gen 5 to the Z-Stick 7, so I'm wondering if you might have, or do, a video that covers that process??? Thanks ~Frank
I wish I had found this video two hours ago, as I wasted an hour of my life figuring all this stuff out myself (after the built-in HA FW update didn't work at all).... Did the 7.17.x to 7.18.3 update, so hoping it solves all my dead node issues in HA. AT least so far (
Im on 7.19.2 and still getting dead nodes. Im now using an automation to ping nodes as soon as the are dead to revive them. This automation really helped
@@31biga 7.18.3 didn't completely solve my dead nodes problem, but it helped a ton. The zwave network is much "snappier" (devices respond faster), CPU usage on my Nuc dropped by 2/3's, and now I get dead nodes at a rate that is *maybe* 5% as often as it used to be (and they tend to solve themselves). In fact, just to see how often it's happening, I turned off my "ping nodes" that was pinging the nodes every 20 seconds to keep them alive. Now I get a 'dead node' *maybe* once per day, and usually it resolves itself within a few minutes. Not sure why it didn't help you, but it helped me a ton
When I updated, It borked my whole z-wave network. I spent WAY to long diagnosing it before I figured it out: it was set to Europe frequencies by default. As soon As I set it to US in the ZWave-JS UI, everything immediately came back. I guess that's the downside of only having 1 firmware version for all regions. I've never even had to think about it trying the wrong frequencies before.
What version was it? I know it was a problem on 7.19.1 but it should be fixed in 7.19.2. This is the reason why Aeotec did not made 7.19.1 available to download from their website, you had to ask their help desk to get it and the TS agent was supposed to inform you of the possibilities of region change when sending you the firmware file.
@@31biga I never updated to 7.19.1, just straight to 7.19.2 from whatever it was before that, I think it was 7.19.0. Maybe that's why?
What about the 800 series controllers? Should they be upgraded as well? I currently have the Zooz ZAC93
I’m yet to test out the 800 series.
The issue mentioned is tied specifically to the original 700 series firmware. I would assume they don’t have the issue on the 800 series :)
Mark you did a video on the boundary alarm a while back and one on the alarmo integration, I've got a boundary system which I'm having issues with, I can't get customer support as the company have ceased trading. I know the boundary system uses z wave and I wondered if I could use my boundary sensors and bell boxes via a dongle and create my own system in alarmo, just wondered if this is possible?
Hey Paul. You can add the boundary devices directly to your Z-wave. You will need to reset each device before use. I have done this with the siren, contact sensors and motion sensors.
One issue with doing this is that some of the device entities don’t name themselves(e.g the siren has a toggle and other information without a description).
You can’t add the boundary control panel to HA which is a shame.
@@MarkWattTech thanks for that Mark I think I'll give it a go, I've been unable to use my boundary alarm for a while now as its had a number of issues flag up on the panel but there's no longer any support so if I can at least utilise the sensors and the sirens that's something and not all my money will have been wasted, the hardware seems to be very good quality, it would have been a shame to junk it.
Is there a reason you don’t use the upgrade option which is visible in your video in the standard Zwave-JS addin to apply the firmware file rather than using the Simplicity Studio 5 option? Great video thanks
I wonder the same thing. I'm on the 7.17.2 and
I saw the option on HA to do the update. I wonder if it will work?
Does the mesh continue working after the update? Or do i need to pair everything again?
@Cristian Dorbesi really good point. Same here. Can we update from within HA and does it maintain the existing mesh.
first time I updated I also used pc controller. Second time, I updated using Z-waveJS UI (formerly zwavejs2mqtt) and it worked fine. Take note that the 7.19.x firmwares might change your stick region after updating. You can set it back to the correct region in pc controller or also in Z-waveJS UI
I'm not using the UI. I'm with the default Addon, which also have a button to update firmware. Does it work too and, if frequency is changed, does the zwave js addon allow to change it back?
I tried the UI and I didn't work. Just sat there with the Spinning Ring of Nothingness and never did anything.
If using ZWave-JS UI, the Windows software is no longer necessary. [edit: also, I still had network instability with the 7.19.2 firmware and finally dropped back to my 500 series stick. Which, again, was easy thanks to ZWave-JS UI backup/restore.]
Very easy with Z-Wave JS UI!
Although I don't think you can run UI and the standard Z-Wave JS addon in HA (correct me if I'm wrong 🙂 )
@@MarkWattTech hearing that I feel sad for those that can't