You should look at your NR log to see why it cannot be initialized.
When your NR start does it have access to the network? HE is up?
There is a fallback mechanism if device node is not initialized. When a new message will be received by NR and forwarded to the device (uninitialized), then this device will try to re-initialized itself before consuming the event
You can also use this mechanism to add a inject node with a delay (e.g. the time the network goes up) connected to your device nodes ...
But a better alternative is to use the systemStart (originally sent when HE goes up) event to resynchronize all hubitat nodes. e.g. Use inject node to trigger an event with HTTP node. ex:
![]()


But again, figure out why you have this issue by looking at logs