Are we supposed to be able to say have one deployment mode connect to an OCP UA server with different endpoint than say in production?
If I wanted to have “Dev”-mode mean that a certain connection goes to a simulated PLC OPC server, while the “Prod” is setup to connect to the real PLC, it doesn’t seem to be possible as the endpoint isn’t something I can change in the overrides for the OPC connections.
In theory it should be possible but I think the way the config UI/UX for OPC UA connections currently works won't allow you to get there. I'd bet you can make it happen via the API or the appropriate modifications on disk, though...
Probably deserves a ticket to figure out how it might work.
Makes sense. I would think that more people than me would like to connect to different OPC servers in dev and prod..
I also wanted to test this, and for the Dev mode I prepared such modes. When I want to change the device address to a different one in Dev mode, I don’t have that option. It looks like an underdeveloped module, or I don’t understand its philosophy.
The web UI probably doesn't work 'correctly', as Kevin mentioned above.
That doesn't mean the underlying functionality isn't working. Again, as Kevin mentioned, if you make the appropriate modifications on disk or via the config API directly to duplicate your 'core' connection configuration into your other deployment modes, it will work.
This was actually the primary reason I was looking forward to this feature - I haven’t had a chance to test 8.3 beta yet but hopefully someone figures out a way to do this
I’m no longer able to replicate this in the latest builds of 8.3.2. If anyone encounters this while using a nightly build of 8.3.2 after (b2025110718), please reach out via this thread or message me directly, otherwise we will consider this issue resolved.
This still isn’t implemented in the UI.
Currently on build 8.3.3 (b2026012009)
The override is still missing the option to edit the endpoint.
The original posting was for an inability to edit endpoints for OPC Connections configured in other deployment modes. This was fixed as part of 8.3.1. That fix, however, exposed a different issue where the Endpoint menu item is not displayed if the “active” definition (the Dev definition in the above screenshot) is something other than core. This secondary bug was fixed as part of 8.3.4, though that release is still in the RC phase.
In the following screenshot, my Gateway is deployed in the QA deployment mode, but you can see the Endpoint menu item is now available.
