OPC Quick Client doesn't show nodes from a custom Device-API driver (8.3.3)

rm.severs1 · July 24, 2026, 3:46am

Following up on the earlier thread about Quick Client returning in 8.3.1/8.3.2 — it's back on my 8.3.3 gateway, but it doesn't seem to render nodes from a custom driver built on the Device/DeviceExtensionPoint API (the newer AbstractDeviceModuleHook style, not a legacy driver).

Repro:

Confirmed via logging that the node is created with a valid NodeId and the reference to Devices is added, no exceptions anywhere in the device lifecycle.
In Designer's View > OPC Browser, the node shows up correctly as a sibling entry under Devices (e.g. [MyDevice]), fully populated with children.
In the Gateway's Config > OPC UA > Quick Client, browsing the same Ignition OPC UA Server connection and expanding Devices shows nothing for this driver — not even the empty root folder. Full gateway restarts don't change this.

Is this a known gap in the 8.3 Quick Client reimplementation, or should I be doing something differently in the driver to make it visible there? Happy to share more of the driver code if useful.

bmusson · July 24, 2026, 4:14am

My SNMP driver doesn't have any issues with the Quick Client (in 8.3.6, at least):

github.com/mussonindustrial/embr

main/modules/snmp/gateway/src/main/kotlin/com/mussonindustrial/embr/snmp/agents/opc/DiagnosticAddressSpace.kt

8.3

package com.mussonindustrial.embr.snmp.agents.opc

import com.mussonindustrial.embr.snmp.agents.devices.SnmpAgentDevice
import com.mussonindustrial.embr.snmp.opc.DeviceContextManagedAddressSpaceFragment
import com.mussonindustrial.embr.snmp.utils.removeAllNodes
import org.eclipse.milo.opcua.sdk.core.Reference
import org.eclipse.milo.opcua.sdk.server.AddressSpaceComposite
import org.eclipse.milo.opcua.sdk.server.Lifecycle
import org.eclipse.milo.opcua.sdk.server.nodes.UaFolderNode
import org.eclipse.milo.opcua.sdk.server.nodes.UaVariableNode
import org.eclipse.milo.opcua.sdk.server.nodes.filters.AttributeFilter
import org.eclipse.milo.opcua.sdk.server.nodes.filters.AttributeFilters
import org.eclipse.milo.opcua.stack.core.NodeIds
import org.eclipse.milo.opcua.stack.core.types.builtin.DataValue
import org.eclipse.milo.opcua.stack.core.types.builtin.LocalizedText
import org.eclipse.milo.opcua.stack.core.types.builtin.NodeId
import org.eclipse.milo.opcua.stack.core.types.builtin.Variant

class DiagnosticAddressSpace(val device: SnmpAgentDevice, composite: AddressSpaceComposite) :
    DeviceContextManagedAddressSpaceFragment(device.context.deviceContext, composite) {

This file has been truncated. show original

rm.severs1 · July 24, 2026, 5:50am

Hmmm, thanks for that. Gave me a couple things to try, but no luck yet.

Starting to look like this is an issue with my docker instance. Tried making a simulated device and even thats not showing up in Quick client.

Kevin.Herron · July 24, 2026, 11:07am

Do you have a reverse proxy in front of it or anything?

The QC had, or still has, a bug with URL encoding or something that causes symptoms like this, and it was more prevalent when a reverse proxy is in front.

Going from memory here so the details are fuzzy