Thanks @petro, I have had some problematic nodes in the past which has shown as “dead” in HA, but it never stopped my network from showing anyway. There may be some kind of problem in my zwave mesh, because it has been rather slow at times and occassionally nodes have died or not reported back. That is why I would now like to rebuild my whole zwave network, but it seems hass.io won’t let me do that easily. Maybe it will be easier in the end to just do a fresh install of hass.io (or upgrade to hassos) to make sure I get rid of every remnant of the old zwave network. Or, will it suffice to just remove the core.device_registry and core.entity_registry let hass.io rebuild them?
I am starting to feel that maybe zwave isn’t the way to go with lights and switches in the future because of some of its inherent weaknesses. But I have invested a lot of time and money to make it work with a large number of entities in HA, so I am reluctant to invest in something else unless it proves to be really superior to zwave. Unfortunately I am now at a point where my whole HA setup seems like a big mess because of a zwave network not working as it should.
I will look into getting a proper neighbor map of the mesh when I have the time. I have seen posts about it, but not found any easy to implement solution to it yet.