It seems that with OpenDayLight running the newer Swagger introduced in Aluminum, all mounted devices show up in the drop down list as "topology-netconfnode".

When using OpenDayLight "Magnesium", mounted devices appear in the swagger under a "Mounted" tab. Each mounted node is listed and can clearly be identified.

After Magnesium,  the swagger has changed to "OpenApi3". Now the mounted devices appear in a dropdown list in from the upper right hand side of the swagger. We see this when running Aluminum SR4 and Silicon 14.0.0.

From the drop down list in the upper right corner of the swagger, every mounted device from the dropdown shows up as:

   - topology-netconfnode resources - RestConf RFC 8040

   - topology-netconfnode resources - RestConf draft02

If there are 20 devices mounted then these two entries appear on the list 20 times.. there is no way to find the mounted node you are looking for without clicking on each selection on the list. 

A jpg is included that shows the drop down values with two device simulators connected running Aluminum SR4. 

This is duplicated by running Aluminum SR4 and Silicon 14.0.0 with the following features installed:

feature:install odl-mdsal-model-inventory odl-netconf-mdsal odl-restconf odl-netconf-topology odl-netconf-connector-all 

Device simulators are added using a basic API such as this:

PUT http://<IP>:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=myTestDevice

Body:

{
"node": [
{
"node-id": "myTestDevice",
"netconf-node-topology:reconnect-on-changed-schema": false,
"netconf-node-topology:concurrent-rpc-limit": 0,
"netconf-node-topology:password": "netconf",
"netconf-node-topology:username": "netconf",
"netconf-node-topology:tcp-only": false,
"netconf-node-topology:max-connection-attempts": 0,
"netconf-node-topology:keepalive-delay": 60,
"netconf-node-topology:schemaless": false,
"netconf-node-topology:schema-cache-directory": "myTestDevice",
"netconf-node-topology:default-request-timeout-millis": 60000,
"netconf-node-topology:sleep-factor": 1.1,
"netconf-node-topology:port": 17830,
"netconf-node-topology:connection-timeout-millis": 22000,
"netconf-node-topology:host": "172.0.1.2",
"netconf-node-topology:actor-response-wait-time": 300,
"netconf-node-topology:between-attempts-timeout-millis": 2000
}
]
}