Node-RED fails to start with `Cannot find thing: 404: Not Found`

[freaktechnik]

My node-red currently is in a restart loop due to a device being offline, which leads to it erroring with "Cannot find thing: 404: Not Found" as an unhandled rejection. It seems to me that this shouldn't fail node-red startup and instead just lead to broken nodes. I'm pretty sure that's what happens with property set nodes, for example.

[freaktechnik]

This might be a nodered 3.0 thing?

[bewee]

Unfortunately, I did not manage to reproduce your issue with the latest Node-RED release (3.0.2)