Dead node, resumed in zwcp but still dead in HA

Configuration Z-Wave
1

Hi.
A year ago i’ve added a second fibaro rolleshutter to the zwave network, configured into HA and then leaved off because not wired to the blind motor.
Now i’ve connected it to the blind, but HA marked it as dead (cache load).
Into zwavecp i’ve deleted the dead node and then readded it (with zwave inclusion) successfully, i’m able to set level, optiins … All works ad expected , then i’ve saved config…
But when i’ve restarted HA, the node still dead…
If i come back into zwavecp, the node is dead again

2

Solved.
I’ve changed the Raspberry location and both rollershutters become alive… I’ve found some new entries into zwave_config yml, like “ignore dead node true” or similar… Will post when i can open the file

3

I would be interested in the new entries as I have problems with dead nodes.

4

Here is the zwave_device_config.yml file content:

cover.fibaro_system_fgrm222_roller_shutter_control...
  invert_openclose_buttons: false                  
cover.fibaro_system_fgrm222_roller_shutter_control...
  invert_openclose_buttons: false                  
  ignored: false                                   
  polling_intensity: 0

The ignored and polling-intensity entries where automatically inserted into the file under the dead node entry (the second rollershutter)

5

I’ve not solved the problem, the node still go into dead status, after few time it goes ready, then dead…
It’s not a signal strength problem, i presume, the controller is inside the house, about only 10mt far away from the node, that is outside, near the sunshade motor.

I’ve read about that using a network key can solve the problem … will try…