Turn off automatic removeal from Z-Wave (on low battery...)

So I just had another node being removed, “ping failed - removed”. Why? The battery on the node was below 30%. It worked like a charm when I grab it. So the node was in no problem, yet Z-Wave removed it due to ping failure or something. The end result: I had to re-include this node AGAIN, with new node number just because the battery is low. It re-included perfect with that old battery - no problems at all. Yet it was erased frm Z-Wave JS.

I need a switch to turn off this automatic garbage handling. I need to be in controll of my system, no AI stuff or what ever. I know the battery is low - but removing it? Come on!!!

My system doesn’t do that. The zwave node just goes dead, and almost immediately after replacing the battery it shows back up.
All I use is Zwave JS and the battery state card, no other modifying mods.

I find that battery zwave devices are unreliable under 40% (no scientific testing but true for me.

I think this is mostly because my devices are 2 category. Heavy use and rare use

Heavy use devices battery discharge and below 40% they quickly get to point of too low battery

Rare use device battery almost never get below 90% i feel. Like last forever but of course this not true

Is this message showing in HA or zwavejsui?