Open christophwrann opened 3 years ago
Hi @christophwrann,
Seems the Recording node contains a bug here. I cannot fix that in at least 2 months, since I'm recovering from a surgery...
The only thing you can do now is remove that node b410f9ca.9c715 from your flow. If you can't start Node-red, then you will need to start it in safe mode ( Add --safe mode flag to the startup command to allow starting without flows running).
The reason why I haven't published thes nodes yet on NPM, is a lack of time to finish it ... Bart
Hi Bart, thanks for your quick response. I disabled the particular flow in the flows.json file. Luckily I could start node-red again. Yes, at the last deployment I used the recording node which apparently caused the issue. All the best for your recovery. Christoph
Christoph, Thanks! Nice to hear that Node-RED starts again. I will leave this issue open, so I can fix it afterwards when I'm back into developing...
Hi @christophwrann, Sorry for the late response! Are you still interested in testing this? If so I will try to fix this node. But then you would need to test it and give me feedback, because my camers don't offer recordings... Bart
Hi, I have used the onvif nodes with a reolink camera. It was working fine. After a deployment I lost the connection to node-red. Since then Node-red is not starting anymore.
Any ideas? Tried to uninstall nodes with: npm uninstall bartbutenaers/node-red-contrib-onvif-nodes But doesn't work.