Sorry for your loss.
The device is coming from the integration but do you still need it?
I mean, can’t you remove the integration?
If you can and you try, if it fails, it will most probably gives you a reason (like used in this or that automation what so ever)
Otherwise there is the hard way but before going into this, lets try it soft.
Ok, did you try to remove it and add it again?
Sometimes it cleans the data.
Otherwise, you can go to .storage/ and look after a file name core.device_registry.
Just tell me if you can locate it. If it is needed, I’ll guide you then to remove what is needed but it is risky.
I know how to do it but only by modifying internal core files in the .storage folder.
And I don’t know if you want to take that risk.
Isn’t it better to backup your configuration, remove the integration, add it back and see?
At worst, you’ll restore the backup.
If you’re not sure, copy the automation.yaml file somewhere safe. It will be as easy as putting it back after your attempt.
Even more if it is in Node-RED, there no strong link between the 2.
In HA you could be scared that some part could have been automatically modified by removing the integration, like unique_id, but that will never happen with Node-RED.