Should they also bring it with a red bow around it 
Hi guys!
There’s someone that was able to do a gen5-gen7 stick comparison about real range?
Looking to tech specs, especially for the EU version, seems that gen7 are not able to reach the same area coverage of gen5.
But this appear to be not so clear… so… any direct experience?
For me the coverage is so important, because I’ve some far devices outdoor that I’m able to reach (at limit) with my actual controller (zipato zipabox that I want to abandon to move to HA that now is running in parallel), and a less coverage area could risk to create issues.
Gen7 features are not available I don’t believe are available until Z-Wave JS suppports S2. S2 has far lower overhead in transmission packet size.
The security protocol is downgraded to the original Z wave plus version (S0), which has far greater overhead, and the range is likely influenced as well. (See the silicon labs white paper on Z-Wave security)
https://zwave-js.github.io/node-zwave-js/#/getting-started/sponsoring?id=roadmap
Someone correct me if I’m wrong please, but that’s my understanding of it. Consequently, it doesn’t matter what stick you get if you’re using Z-Wave JS.
@FreelancerJ : out of curiosity, what controller software are you running that you have HA connect to via WebSockets?
Z-WaveJS now, since I’ve not got anything too complex going on. Working well all this time 
1 Like
Update:
Besides being less efficient and more congested with network latency, Z-Wave networks Running on controller software not utilizing a S2 controller’s S2 capability are susceptible to network joining key theft which is rather trivial to implement (“Key Reset” attack).
Described in detail at my post:
Gen 7 / 700 series z-wave chip has far, far greater range if the controller is gen 700, The controller software running a gen 7 chip controller is supporting S2 v2 (so definitely not Z-Wave JS or openzwave-based controller software), and most or all of the devices in the Z-wave network are gen 7 as well.
That’s my understanding of it
Nice. Doing it separately from Home Assistant seems like it has its advantages.
Out of curiosity have you looked into doing the same but from a Z-Ware box / Pi so you can have S2 support with all the speed / reduced network latency advantages that that brings (+ security vulnerability fixes)?
I think if you’re willing to share a tutorial on how to do so, this would be advantageous to a lot of folks.
Hi, I was thinking to buy one from popp.to mid of August, but was a little bit afraid about customs to France…
I have been able to buy one directly from Domotique-Store (I’m not sure I can put the link) in France an received it in few days, through Colissiomo (La Poste).
Hope it can help …
Regards
FYI, Z-Wave JS now supports S2 and enables it by default on new installations if you set a security key.
Support for S2 is still very new in ZWave JS and each release after v8.1.0 has contained S2 bug-fixes:
Z-Wave JS also support Z-Wave 700 Controller like Silabs UZB-7 stick, Aeotec Z-Stick 7 and Z-Pi 7:
3 Likes
I might do this, if I get around to setting up from scratch to include everything with S2. Won’t be super soon though, sorry. Too much else on (as shown by the lateness of toy reply here 
This, all of this is goodly news to me. Thank you!
1 Like
Aeotec now posted a ‘how-to’ upgrade firmware and they also provide direct download links with a copy of unmodified Silabs GBL FW files used for OTW firmware upgade that comes with Simplicity Studio:
https://help.aeotec.com/support/solutions/articles/6000252296-update-z-stick-7-sdk-7-15
FYI; blhoward2 also confirmed OTW FW upgrade bootloader + xmodem procedure in Linux on Silabs UZB-7 stick reference HW as posted here [Feature Request] Ability for Z-Wave JS to perform OTW firmware updates of Z-Wave 700 series USB sticks like the Silabs UZB-7, Aeotec Z-Stick 7, and Zooz USB 700 Series Z-Wave Plus S2 Stick · Issue #2545 · zwave-js/node-zwave-js · GitHub
Confirmed manual process to upgrade working in Linux. Credit to cpw:
- installed minicom
- figured out where device was (/dev/ttyUSB0 for me)
- unplugged/plugged in device
- in a shell: stty 115200 cs8 -cstopb -F /dev/ttyUSB0
- then in same shell: printf ‘\x01\x03\x00\x27\xDB’ >/dev/ttyUSB0
- configure minicom: minicom -s important: turn hw flow control OFF here, set baud etc
- run minicom: minicom -D /dev/ttyUSB0
- press enter a bunch of times, you’ll see menu as demoed. (may need to replug stick to get this to happen)
- select 1 in menu to flash. in minicom, use ctrl shift S, select xmodem, and specify path to file. Upload should proceed (it’ll take a minute)
- press 2 once upload is complete in minicom to “run” the new firmware.
Again, more discussion available here → Aeotec Z-Stick 7 USB stick (ZWA010) and Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025) Z-Wave 700 Controllers with Z-Wave JS · zwave-js/node-zwave-js · Discussion #2549 · GitHub
is the upgrade to FW 7.15 mandatory?
Also the controller itself is shown with secure: no per default. is that a problem?
Hi. I am a new user of z-wave and I would like to use it for Home Assistant. I have purchased an Aeotec Z-stick 7 to use it as a Z-wave gateway for all my z-wave device. I have installed tha HA on an RPI4 and it recognizes the device but security and z-wave plus protocol shows as disabled. I can add or remove z-wave device but only without security. However the datasheet claims it supports S2 security and z-wave plus also. I have checked the firmwave of the stick and it looks like it was 7.11 version. I have found in other topics that a FW upgrade is needed for this to 7.15 version. I could successfully upgrade it to 7.15 via Simplicity Studio. However it has not really changed anything regarding to Security. It still shows Security Disabled. I have tried to reinstall HA from scratch on the RPI4 but it has not changed anything.
I am running these on the RPI4. core-2021.11.5, supervisor-2021.10.8, ZST10-700 stick by Silicon Labs Firmware: 7.15
Have you got any idea how this issue can be fixed?
Hi, the stick itself show Secure: No - see my post above. Also, not all devices support S2 Security. Can you name a few devices of your Z-Wave setup. Sometimes they also have different routines to trigger secure implementation.
All of the included z-wave devices shows as not secure. But here are some examples:
Aeotec Temperature and Humidity Sensor (ZWA039)
Fibaro Wall Plug (FGWP102)
Zipato Smart Bulb 2 (RGBWE2)
My understanding is that each of these device should support some kind of security. I do not know if the stick itself is insecure any other device can be configured as secure. In the Z-wave JS menu Security shows disabled for all of them. Z-wave Plus shows disabled for the Stick only. All the other unit show either 1 or 2 in this section.
The “Secure” field for the USB controller does not mean anything. You can ignore it. All 700-series controllers support S2 security.
The Aeotec supports S2. Only some versions of the Fibaro wall plug support S2, you’ll need to be more specific. The Zipato bulb only supports S0. You don’t want to use use S0 for anything that doesn’t require it because it’s very slow.
When you include a device it will attempt to use S2 if supported. If that inclusion fails for some reason, you’ll get a warning about Low Security. Did you see such a warning? If that happens you need to exclude and try including again.
Yes, I have seen such a warning message regarding Low Security. No matter if I exclude and include again. Everything runs without security. 
I have added an Aeotec Range Extender 7 to the network and I was able to Switch on S2 Security for this device. I have excluded my Temp Sensor and reincluded again via the Range Extender and was able to succesfully add S2 Security to it. 
The weird thing why was it unsuccessfull via the Aeotec stick itself. No one knows… After some research I have found the Fibaro Wall plug and the Zipato bulb ineed does not support S2 Security so it is normal they show as unsecure devices. All seems to be working as expected. Thanks for the replies.