Heya I just noticed that my node-red keeps crashing all day long.
Inside the logs I could find that node-red seems to have a problem after a function node tries to get an undefined variable.
here an example on how I defined those variables in the past:
var test = flow.get("test") || false;
In the past this worked like "Set the value to flow.test and if that is undefined the variable was set to false".... but this doesn't seem to work anymore. Did I miss a changelog for this behaviour?
I know what nuki is (smart lock) but that error is just there because the module is recharging right now... You can ignore those errors because it is just for small amount of time there, the error for crashing persists if nuki works as expected.
@Colin sry did miss your question but @Steve-Mcl maybe I have to correct myself... I just stopped the link to the nuki node and now it seems to work, but I tested it only 30 minutes for now... the recharging is done and the error isn't appearing anymore o_O
it is now all the same except the connection to the API node from nuki... but it wasn't happening before.... mhhh will take care of it for future and will report back if that will happen again! ty for now!
Are you calling the nuki module from code you have written yourself? A function node for example? If so then you should catch errors from nuki and take appropriate action then it would not crash node-red.