Interesting. I don't remember removing the ghosts I created to be particularly onerous.
I had a number of failed pairings/leftovers as I was paring the 100+ devices.
Most removed in 1 try, but on a few of them I had to re-try the remove 3-5 times before they would remove. But they all DID remove in the end.
3 Likes
The only "major" issue I've had with the upgrade is, none of my battery powered devices would work until I pulled their batteries and forced a refresh from Hubitat (and yes, I updated the ZW FW first).
Ah - I created 2 or 3 non-LR ghosts and 2 LR ghosts. I think everything was removed on the first or second try.
I experienced the same thing on a few of my old z-wave contact sensors. Pulling battery fixed them. Maybe if I would have waiting they'd eventually come online once they "woke" up but I'm impatient 
1 Like
But, is getting rid of 10 long range ghosts worth the cost of a C8 pro?
They are annoying……………………
No, not to me as they are completely cosmetic only. 
1 Like
Looking for a justification.
2 Likes
My ASD/ADHD wouldn’t let me ignore them …. 
1 Like
The answer is of course yes… 
How long should we wait before we start to take additional steps to get battery devices online.
Pretty much everything of mine is working except for 4 device types
- 6 (about a third of them) Ring Gen2 contact sensors
- Four Zooz Zen 34 remote switches.
- An Aeotec Aerq sensor
- A Zooz Vibration/Tilt Sensor for Garage Door
I invested in a Z-wave USB stick last month to banish the ghosts I didn't know I created when setting up the hub. How are you supposed to know if they are impacting performance if you never had an HE before?
Stick did the trick but perhaps if I had procrastinated till this month it wouldn't have been necessary! Oh well 
1 Like
Since battery stuff can have 12-hour (maybe even longer?) wake-up periods, I'd give it a solid day or so if you decide to avoid a manual wakeup.
I was impatient when I first moved to JS and did manual wakeups just to ensure everything was communicating OK, but since then, whenever I've messed with stuff and reset the device-level activity clocks, I've just let everything check in on its own timeframe -- they all eventually have every time (so far 
)
2 Likes
Say, hypothetically, if one were to purchase a C8Pro now, from the Hubitat website, would it have the latest ZW version?
edit: Not a hypothetical anymore.
I would expect some lag, just based on my modest understanding of contract electronics manufacturing. Expect weeks or months to update production and work through inventory. Thankfully the update process is fairly painless.
3 Likes
If you buy a C-8 Pro not very long, but if you keep your existing hub you'll wait forever for the C-9. I'm in the same boat; I'd love a C-8 Pro now so that I can have Z Wave JS, but don't want to buy one only to get model envy when a new hub does get announced.
2 Likes
That ship has sailed.
2 Likes
So, I now understand what Zwave js is, but I'm still not fully understanding the benefit of updating the firmware and switching to js as an end user. I see that it now can remove ghosts, but what other benefit will it have to the everyday use of a c8 pro? Faster response times to nodes? Increased battery life for battery powered devices?
Sorry if its been answered already, I just haven't found it yet in my (admittedly limited) seaching though the JS threads.
1 Like
On zipgateway I had 1 device, garage door, that would regularly have to be sent multiple commands before it would work. After updating to ZWaveJS it works every time on the first command. Likely due to much better handling of supervision for S2 devices.
7 Likes
Not really faster, nor better battery/power support (that's on the endpoint, side, not the controller).
My sense is several short & long term gains:
Short Term:
1 - Biggest gain is better support around radio backups around "HE Cloud Protect" stuff - The Z/IP gateway definitely has issues when the radio backups are done/complete in that sometimes the radio goes down, and doesn't come back.. I believe SiLabs acknowledged this as a problem, that they didn't plan to fix (their answer was to move to their new communications approach (Unify SDK)) - I believe using ZWaveJS resolves this issue.
2 - Much better support in removing ghosts, and removing S2 ghosts - Basically, network cleanup shouldn't require a Z stick (never say never) for the average user - This was a much improved area in found in the beta.
Long Tem:
2 - ZwaveJS is OpenSource - A bunch of the following is my speculation and "tea leaf readings", but Z/IP gateway is open source, and HE staff can look at the code, and make PRs and internal fixes if needed (as they can see the actual code) - Using the SiLab libraries, HE is somewhat chained to the direction of SiLabs, as the dropping of future development around Z/IP, with outstanding bugs, I'm sure was problematic for them - So there isn't any "immediate gain to users" here, but it makes HE a bit more 'in control of their own destiny" around future ZWave upgrades/fixes. - And ideally makes them more responsive to some issues, versus where they were with SiLabs software libraries. - There are reasons that lots of other companies choose to use ZWaveJS. - The last ZIP gateway release was in Aug 2024, and the product is in "maintenance mode" per SiLabs
Finally, there is still SiLabs firmware running on the radios, and that software can STILL have issues - but it's not just HE that has to deal with it. - Hence the optional firmware upgrade that appears once ZWJS is enabled. - There are STILL some issues with the V7.22 radio firmware versus V7.23 ("jammed" comes to mind)
See below:
https://www.silabs.com/documents/public/release-notes/SRN14930-7.23.0.0.pdf - See "Fixed Issues" in section 2.3
2 - ZwaveJS will the future standard for HE (SiLabs is going the Unify SDK path), given ZIP is dying - On an older, memory limited - ZIP does what it does and works - but future adds (ZWave LR for EU frequencies, and other features may just come out on ZWaveJS supported platforms, as SiLabs will stop (or has stopped) development on the ZIP gateway.
3 Likes
