Hello
I'm still new to node red - i have such a problem.
I've created the flow that is working fine but - after power restart of my revice( raspberry ) im automatically starting the nodered but then im in such a state :
So the first part of the flow is in keeaplive / subscribe state
While the second part ( there's no connectiong between thoose parts) is all the time in connecting phase.
For both parts im using the same injects and same settings.
If i deploy the flow - its starts to work , but in the end i want to have the flow running automatically after power reset
Do you need help with node-red auto starting on your pi or the flow to start automatically when node-red starts?
I would highly recommend you use PM2 to start and watchdog node-red, this will restart node-red if it becomes unresponsive or crashes
as far as your flow it looks like your starting it on node-red start but if you can post a copy of your flow into the post with the </> to embed your flow into the forum post that would be helpful.
Hi leftymuller,
thank you
Node red is already autostarting.
But the problem is as on the screentshot - first OPC-UA client is in keepalive / active subsribed if i press the button 2 that is connected.
But OPC UA Client underneeth is all the time in connecting mode . If i click button 1 nothing changes.
I need to make some changes in the flow, click deploy and its working then.
But after power reset - again im able to open the flow automatically but its in the same state.
For the PM2 i was trying to install it using npm install -g pm2 but i have an error : EACCES : permision denied, mkdir 'usr/lib/node_modules/pm2
I suspect the problem may be that node red is up and running before the OPC-UA server is ready, so the initial connection fails, and that the node is not able to recover from that situation. I seem to remember previous reports of that.
Are there any relevant messages in the node-red log?
thank you, but i quess thats not the thing. i use the same OPC_UA server for both connections.
In the meantime i've found on Issues · mikakaraila/node-red-contrib-opcua
similar case and solution was to use single client and switch function. It works, but ...
i have also in that flow OPC_UA client in write mode. And that i cannot connect to the same OPC_UA client ( here i'm just subsrcibing) and for that OPC_UA client in write mode i again have a problem with that it's still in connecting , not keep alive
thank you,
yes you're right.
There are some errors in the log.
The opcUAnode1237.... is the not that is in the connecting .
At the sceond screenshot there's some other error - im not really sure weather its related to also those nodes, but perhaps yes. I cannot set the clock / clock server at my opc_ua server - it's not online
