# Problems with OPCua and Node-Red

**URL:** <https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040>\
**Category:** General\
**Created:** [11 September 2018 13:23 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040 "2018-09-11T13:23:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mfurla8](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mfurla8/32/2482_2.png) [@mfurla8](https://discourse.nodered.org/u/mfurla8)\
**Post date:** [11 September 2018 13:23 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/1 "2018-09-11T13:23:11Z")

</div>

Hi to all...

I have a problem, when i am opening browser page with node editor, RPIs CPU is fully loaded and connection between OPCua and node-red is not workign anymore...

any suggestions?

i also get this warning and errors:

> Timeout .... waiting for response for PublishRequest { /_RequestHeader_/  
> authenticationToken /\* NodeId _/: ns=1;i=3  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:30:40.304Z  
> requestHandle /_ IntegerId _/: 2198 0x896  
> returnDiagnostics /_ UInt32 _/: 0 0x0  
> auditEntryId /_ UAString _/:  
> timeoutHint /_ UInt32 _/: 50000 0xc350  
> additionalHeader /_ ExtensionObject _/: null  
> };  
> Timeout .... waiting for response for PublishRequest { /RequestHeader/  
> authenticationToken /_ NodeId _/: ns=1;i=3  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:30:40.343Z  
> requestHandle /_ IntegerId _/: 2199 0x897  
> returnDiagnostics /_ UInt32 _/: 0 0x0  
> auditEntryId /_ UAString _/:  
> timeoutHint /_ UInt32 _/: 50000 0xc350  
> additionalHeader /_ ExtensionObject _/: null  
> };  
> Timeout .... waiting for response for PublishRequest { /RequestHeader/  
> authenticationToken /_ NodeId _/: ns=1;i=3  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:30:40.649Z  
> requestHandle /_ IntegerId _/: 2200 0x898  
> returnDiagnostics /_ UInt32 _/: 0 0x0  
> auditEntryId /_ UAString _/:  
> timeoutHint /_ UInt32 _/: 50000 0xc350  
> additionalHeader /_ ExtensionObject _/: null  
> };  
> Timeout .... waiting for response for PublishRequest { /RequestHeader/  
> authenticationToken /_ NodeId _/: ns=1;i=3  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:30:40.799Z  
> requestHandle /_ IntegerId _/: 2201 0x899  
> returnDiagnostics /_ UInt32 _/: 0 0x0  
> auditEntryId /_ UAString _/:  
> timeoutHint /_ UInt32 _/: 50000 0xc350  
> additionalHeader /_ ExtensionObject _/: null  
> };  
> Timeout .... waiting for response for PublishRequest { /RequestHeader/  
> authenticationToken /_ NodeId _/: ns=1;i=3  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:30:40.901Z  
> requestHandle /_ IntegerId _/: 2202 0x89a  
> returnDiagnostics /_ UInt32 _/: 0 0x0  
> auditEntryId /_ UAString _/:  
> timeoutHint /_ UInt32 _/: 50000 0xc350  
> additionalHeader /_ ExtensionObject _/: null  
> };  
> warning : ClientSessionKeepAliveManager#ping\_server ServiceFault returned by server { /ServiceFault/  
> responseHeader /_ ResponseHeader _/: {  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:32:06.071Z  
> requestHandle /_ IntegerId _/: 2203 0x89b  
> serviceResult /_ StatusCode _/: BadSessio nIdInvalid (0x80250000)  
> serviceDiagnostics /_ DiagnosticInfo _/: {  
> namespaceUri /_ Int32 _/: -1  
> symbolicId /_ Int32 _/: -1  
> locale /_ Int32 _/: -1  
> localizedText /_ Int32 _/: -1  
> additionalInfo /_ String _/: null  
> innerStatusCode /_ StatusCode _/: Good (0x0 0000)  
> innerDiagnosticInfo /_ DiagnosticInfo _/: {  
> }  
> }  
> stringTable /_ String _/: [] (l=1)  
> additionalHeader /_ ExtensionObject _/: null  
> }  
> };  
> warning : ClientSessionKeepAliveManager#ping\_server ServiceFault returned by server { /ServiceFault/  
> responseHeader /_ ResponseHeader _/: {  
> timeStamp /_ UtcTime _/: 2018-09-1 1T13:32:06.073Z  
> requestHandle /_ IntegerId _/: 40 0x28  
> serviceResult /_ StatusCode _/: BadSessio nIdInvalid (0x80250000)  
> serviceDiagnostics /_ DiagnosticInfo _/: {  
> namespaceUri /_ Int32 _/: -1  
> symbolicId /_ Int32 _/: -1  
> locale /_ Int32 _/: -1  
> localizedText /_ Int32 _/: -1  
> additionalInfo /_ String _/: null  
> innerStatusCode /_ StatusCode _/: Good (0x0 0000)  
> innerDiagnosticInfo /_ DiagnosticInfo _/: {  
> }  
> }  
> stringTable /_ String _/: [] (l=1)  
> additionalHeader /_ ExtensionObject \*/: null  
> }  
> };  
> 11 Sep 13:32:07 - [warn] Communication send error: Error: not opened  
> 11 Sep 13:32:07 - [warn] Communication send error: Error: not opened  
> 11 Sep 13:32:07 - [warn] Communication send error: Error: not opened  
> 11 Sep 13:32:07 - [warn] Communication send error: Error: not opened  
> warning : disconnection : closing pending sessions

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [11 September 2018 13:42 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/2 "2018-09-11T13:42:53Z")

</div>

Have you done the basics?  
Looked at the logs?  
Checked you have the latest versions etc?

---

<div class="post-metadata">

**Author:** ![mfurla8](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mfurla8/32/2482_2.png) [@mfurla8](https://discourse.nodered.org/u/mfurla8)\
**Post date:** [11 September 2018 14:00 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/3 "2018-09-11T14:00:45Z")

</div>

Basics?

I have last versions...  
I send what writes down...

Where are logs saved?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [11 September 2018 14:43 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/4 "2018-09-11T14:43:13Z")

</div>

The logs are saved in different places depending on what hardware you are running on and how you have configured Node-RED.

I'd also try googling the error to see if others have had the same issue...

---

<div class="post-metadata">

**Author:** ![mfurla8](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mfurla8/32/2482_2.png) [@mfurla8](https://discourse.nodered.org/u/mfurla8)\
**Post date:** [11 September 2018 15:01 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/5 "2018-09-11T15:01:58Z")

</div>

I google it but I didn’t find any solutions to this case. I found in logs same warnings as i wrote down up.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [11 September 2018 15:16 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/6 "2018-09-11T15:16:43Z")

</div>

Which node are you using? Is it this one? `node-red-contrib-opcua` This issue would appear to be what you are seeing [https://github.com/mikakaraila/node-red-contrib-opcua/issues/36](https://github.com/mikakaraila/node-red-contrib-opcua/issues/36)

---

<div class="post-metadata">

**Author:** ![mfurla8](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mfurla8/32/2482_2.png) [@mfurla8](https://discourse.nodered.org/u/mfurla8)\
**Post date:** [12 September 2018 04:53 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/7 "2018-09-12T04:53:05Z")

</div>

Similar yes... but still without solution. I am using node-red-contrib-opcua  
Here is also warning on node-red start.

`> [warn] [node-red-node-pi-sense-hat/sensehat] Error: Can't find Sense HAT python libraries. Run sudo apt-get install sense-hat`

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [12 September 2018 08:29 UTC](https://discourse.nodered.org/t/problems-with-opcua-and-node-red/3040/8 "2018-09-12T08:29:57Z")

</div>

so if you still have the problem, recheck that you have the latest version and then open an issue so that the developer is aware.

Your new issue is because you haven’t followed the instructions in the Nodes ReadMe. The message tells you what you need to do.