EFM broker connection to upstream EFM server is failing. You have confirmed that the IP connectivity to the destination port number (tcp/8448 by default) is open, yet the connection does not establish from the EFM broker to the EFM server.
You have verified that both the broker and the server have their time synchronized.
Upon log inspection you can see a message "Verification of certificate failed" and "X509 verification result: certificate has expired and depth 0". It might be that when the certificate was created your system time was not correct.
Log in to EFM server as user "efm", and enter the directory where the EFM server SSL certificate is stored:
First we need to generate a new server key, remember the passphrase used to encrypt that key:
Hi there, did one of you ever get the OPC link up and running?Currently my small demo consists of a EFM 1.5 installed locally on Windows and a simulated OPC-UA server running on a separate Windows machine.The documentation on github describes the fol...
I have devices registered in Actility ThingPark Wireless (NS in the cloud) and I have several ways to send my data, but I don't know exactly how to configure that in Actility neither in EFM.
On Actility side i have the following possibilitie...
We have observed something weird in dataflow while using "insert row" node api of parstream dslink as a block in dataflow:
In case we used insert row block to insert data into parstream, it keeps on duplicating table fields in "insert row" block.