Thx a lot…. Updated yesterday . Until now , now dead nodes……
Du you habe the template for pinging dead nodes?
Greetz
I took this from another thread, don’t know yet if it works, I did not had dead node since I activated the automation. Make sure your node status sensor have the same naming pattern as its corresponding ping button else the action won’t work because its calling to replace ‘‘sensor’’ by ‘‘button’’ & ‘‘node_status’’ by ‘‘ping’’ so for example if ‘‘sensor.node_2_node_status’’ changes to dead/unknow/unavailable, the action will activate ‘‘buton.node_2_ping’’.
alias: Ping dead nodes
description:
trigger:
- platform: state
entity_id:
- sensor.node_2_node_status
- sensor.node_3_node_status
for:
hours: 0
minutes: 30
seconds: 0
to:
- dead
- unavailable
- unknown
condition: []
action:
- service: button.press
data: {}
target:
entity_id: >-
{{ trigger.entity_id | replace("node_status", "ping") |
replace("sensor.", "button.") }}
mode: parallel
I Finaly migrated my ZWAVE Aeotec z-stick 5 to the Aeotec z-stick 7
I tried it several times without any succes, until yesterday!
Yesterday it suddenly all worked…
I took following steps…
1 created a FULL backup of homeassistant.
zwave-js-ui: 8.10.1
zwave-js: 10.11.1
2 updated the firmware to FW: v7.19.1 SDK: v7.19.1
3 added the 7 stick to my raspberry next to the 5
4 created a NVM backup of the ZWAVE network
5 disabled WS-server under options → homeassistant (ZWAVE JS UI)
6 switched to the 7 stick in ZWAVE JS UI
7 restored the NVM backup from step 4 to the 7 stick
8 All my nodes came back and were still allive…
9 Monitored the system that everyting worked…
10 Under debug you can see the nodes that use lots of traffic, under the options of the specific device
i changed the energy report of those devices to report not so much which helps allot in traffic.
11 Enabled WS-server under options → homeassistant (ZWAVE JS UI)
Has been a day now and still works pretty good, NO dead nodes sofar and running smoothly. Watching the traffic and all looks still oke. Best I’ve had with the 7 stick…
Just for your info.
2 Likes
Firmware release 7.19.2 is available here. Does anyone has any experience with it? From Aeotec help desk they recommend to update to this release.
1 Like
It went through without any problems.
Update within ZWave JS UI in 1 min. 
All 97 Nodes still online.
I still have dead nodes.
However, too short a time to tell if it is better or the same as before.
FW: v7.19.2
SDK: v7.19.2
Have you tried healing it? Just curious.
Same here, nodes go dead.
I think it’s time to go back to a 500 series.
I went back to 500 and am perfectly happy with it. I used zwave-js to do a backup of my zstick-7. When I plugged in my old nortek stick, zwave-js did the NVM conversion and loaded it on the old stick. Process was flawless. Everything worked including the S2 devices. No regerts!
1 Like
Since I integrated the ‘‘ping dead nodes’’ automation, I can’t even notice the dead nodes anymore. They still go dead every now and then but they are coming back to life after 60 seconds. I reduced interval from 30 minutes to 1 minute in the automation I posted above. The only way I can tell I still have dead nodes is because I can see the automation was triggered in the history, last time was 4 days ago. Not the best solution but at least I feel like I’m ok to wait for a fix instead of going back to a 500 series stick.
I get it and I’m happy things are working for you. Someday, I might go back to a newer stick. However, right now, I have no special automations and no quirks to deal with. Everything just works and I don’t know of any features I’m missing out on. And for the work it took to migrate sticks (very little), I’m really satisfied with my choice. Haven’t had a single problem since I did the switch back in January. I guess we both got what we wanted. 
I have updated the stick to v7.19.2 using Z-Wave JS UI. So far no issues.
Some comments received from Aeotec HelpDesk
Regarding series 700 and latest firmware:
I do think 7.19.2 is the most stable currently and i have updated our articles to contain the new firmware update: Update Z-Stick 7 with Z-WaveJS UI
I would highly recommend updating as i hear that it’s much more stable and resolves an EU issue with the saw filter used in its antenna.
Regarding series 500 vs Series 700/800
Series 500 is proven and tried solution in this case. The Series 700/800 sticks i feel are still in a beta development process and is getting a bit more stable as things go on and hopefully will be at a point where series 700 and 800 optimizations on how they handle a mix of devices improves.
You could keep a Series 500 network utilizing the same network as the series 700 (now that ZWaveJS UI has a backup process, it is easy to move the network back and forth between series 500 and series 700). If you see failure in the new network, you can move back to your series 500 network, and upon a new update of the series 700, you can continue testing new updates until things have become stabilized (just a thought i have in this case).
Series 500 is still the most stable verison of Z-Wave currently.
2 Likes
Any progress with this?
I am sitting here with a Zooz 800 wanting to migrate from Aeotec Z-Stick 700, but need a way to use the 700 backup for the 800(?)
Got busy and figured I would let the experts iron out the migration issues before risking my network’s stability but… I need to check what progress was made now that you reminded me.
Well today must not be my day. Needed to upgrade my firmware and started following your guide (great write-up btw).
Sadly been stuck spinning like this for an hour or two:
[Edit]
Nvm, am dum-dum. Turns out my JS UI wasn’t actually connected to my stick, instead I had the base z-wave js (new install). Swapped and everything worked great!
1 Like
Hey,
Just wondering if some of you tried to re-include their z-wave devices without using S2. Chris from the Aeotec helpdesk told me the issue with dead nodes is probably caused by some bugs with S2 that are still present on 7.19.x and recommended to re-add my devices without using S2 to see if it helps. I have not tried yet since i’m not sure if unpairing/repairing my devices would cause any problem with my existing automations (if I’ll have to redo all my automation or not after re-adding my device).
I dont know what you think, but I started having dead nodes (well I started noticing it) after adding my first homeseer smart dimmer using S2. All my other devices (about 30) are not using S2 (old unsecured and/or S0 devices migrated from an old 300 series VeraLite).
yes i tried this, rebuilt my network without any S2 devices, no change, nodes drop dead as usual.
1 Like
@Alain_Raymond - Unless they are locks, avoid using S0 as it significantly increases traffic. As far as I recall S2 is ok but anything older can bog your network down. I got rid of all my zwave older than 500 series and things improved greatly.
1 Like
I only have one device using S0 and its my front door lock. All others devices are ‘‘no security’’ except for 2 homeseer wall swiches using S2 (one HS-WX300 on the 700 series chip, one HS-WX300 on the 800 series chip)
1 Like