Does anyone know how to get the Description attribute to populate in Ignitions OPC UA server with the tag's description or tooltip value?
I am connecting to Igntions OPC UA server with a 3rd party client app and see that the description field is empty. I would love this attribute to be populated with the Tooltop property in Ignition Tag Editor. (see images)
There's no configuration for this, we're not mapping anything onto the OPC UA Description attribute.
If we did implement this at some point it would likely be the Documentation tag property, not the Tooltip.
Bummer, this would be really helpful for anyone using an external historian or database systems to get a little more context around the items. Appreciate the response. I will throw a suggestion on the ideas board for this.
Unfortunately this is a bigger issue than I originally thought because it prevents me from custom adding descriptions in PI Tags. The Adapter keeps overwriting them because they expect the Description field to be populated.
During my time at AVEVA, I worked the support ticket(s) that led to this KB article being created (or whatever they're called now).
I was just about to write up a rant about how this is a common and very frustrating issue for AVEVA adapter users, but it looks like it may have been fixed in AVEVA Adapter for OPC UA version 1.6.0.296 Allow the PI Point description to | AVEVA™ PI System™ Feedback Portal
Have you tried the new config option in the adapter?
Thanks Cody,
Unfortunately, when I updated to v1.6 of the adapter, AVEVA also updated the OPC UA SDK version to the latest (4.1.0) which created a new issue.
Knowledge
So, it looks like now the ball is back in Inductive’s court to resolve the mismatch of endpoints returned by GetEndpoints and CreateSession.
Additionally, I am getting an error on the OPC UA server certificate:
2025-08-18 16:39:28.608 -05:00 [Debug] OPC UA server certificate with Thumbprint: {ID Number} has invalid domain name specified. The certificate domain name '{IP Address}, 127.0.0.1' doesn't match domain name from the endpoint URL: opc.tcp://{hostname}:62541
I removed the Thumbprint ID, IP Address and hostname for security.
The endpoint is currently configured as…
We've already received a Wireshark capture and punted this back to Aveva. Not sure if that was your ticket or if your capture would look the same. The ticket we received it on was getting the error even with security disabled, so we were able to see it clearly in Wireshark.
You can probably fix this by regenerating the Ignition OPC UA server certificate and making sure to provide the public IP / hostname that external clients see. It's probably not preventing the connection from happening, though.
Ya, I did the wireshark capture and sent into them on a ticket. I did it with security turned off, but still looked encrypted. I added None to the security policies above and then restarted the OPC UA module, so I am not sure why the packets still appeared encrypted. I was still connecting with user/pw.
I don’t think it is security related. The error in the logs says security on Aveva’s end, but they said that is inaccurate and it is the mismatch between the endpoint name and session url? I think it may be related to the URN style paths. They didn’t support that before.
If I regenerate the server certificate, will all OPC UA connections be broken and need new certificate? I am ingesting OPC UA data (Ignition is client) and don’t have a scheduled downtime in production to do this…so maybe I will wait.
The logic their client uses to compare the endpoints from discovery vs the ones returned in the CreateSessionResponse incorrectly includes the certificate as part of the comparison, when it explicitly should not be included: UA Part 4: Services - 5.7.2.2 Parameters.
It's actually a bug in the SDK they use. It's a configurable check in the SDK that they could turn off until it's fixed. It looks like the KB even quotes the SDK docs that mention it.
Yeah, you should wait, then.
