Do we require to purchase SSL or CA Certificate for testing Groov EPIC data into Node Red through PAC Read or PAC Write node?
Is there any way for testing without purchasing that certificate? so we can test that thing. Can anybody provide the steps?
I have attached screenshots of my configurations and errors for reference.
Thanks & Regards,
Is Node-RED and groov running on the same device?
If so, is it an AR1 or an EPIC PR1?
It is a Epic AR1.And we are using node red of Epic AR1
AR1 is groov, EPIC is PR1… so I am not sure which you are using when you say EPIC AR1…
For a groov AR1 (The red box) to a groov Data Store Node.
Open up your groov View project, go into Build mode. Click on Configure > Accounts.
Copy the API key for an Admin user.
Go into Node-RED and select http, Enter ‘localhost’ and then paste in the API you copied from groov Build.
For an EPIC PR1 (The black box) to a groov Data Store Node.
Go into groov Manage, select Accounts, then select a system wide Admin account.
Copy the API key at the bottom of the groov Manage screen for that user.
Go to Node-RED, put in localhost for the IP address.
Then paste in the API key you copied.
For a PAC node on the EPIC PR1 (the black box - what I think you have based on the screen shots).
Go into groov Manage, select Accounts, then select a system wide Admin account.
Copy the API key at the bottom of the groov Manage screen for that user.
Go to Node-RED, select https, put in localhost for the IP address.
For the API key name you MUST enter apiKey
Then paste in the API key you copied.
In all cases you use ‘localhost’ rather than the IP address of the box because groov and Node-RED are running on the same box and are in effect talking to itself. Hence localhost.
Beno,
Sorry its a typing mistake.
I am using Epic PR1.
And its ip is 192.168.56.108 and connected to the PC.
The last of the set of three instructions should get you up and running.
I am using node red of EPIC.
Did i put localhost or IPaddress?
Localhost. Just as the instructions and screen shots mention.
thank you so much.
i have tested the things and i am really happy because its working now.
Thanks a lot.
Hi, Beno, the “apiKey” in the name field solved a big deal of troubleshooting for me, the guides at http://developer.opto22.com says to leave it blank.
I’d like to get that fixed, can you link or screen shot to where it says to leave it blank.
Thanks.
Same issues. Another frustrating scenario, with faulty documentation. The direct link to dashboard in NR is also a nothing link (bad gateway request). You MUST enter the URL manually as “localhost/IP”/node-red/ui/, in my case “192.168.1.22/node-red/ui/”…the URL must include “/” after “/ui”…not sure how this was not caught before release…but my list of these scenarios is a mile long at this point…a shame, as the epic has world class i/o (lots of bench time with the scope confirms the quality and stability of most i/o modules)…
Sorry to hear you hit some snags along the way.
Hard to say for sure, but it seems that only a very small handful of customers are using the Node-RED dashboard nodes. Most people test it and then come back to groov View for one reason or another.
The URL issue is reviewed here;
It is important to keep in mind that both Node-RED and Ignition are not Opto software. They are downloaded from the web and installed (embedded) into EPIC.
We contribute as much as we can, but like all software, bugs sneak in. With each release of EPIC firmware we strive to make our software better and upgrade the versions of third party software.
