Hi,

Can you tell why you need them? Because maybe you dont i.e. there could be another more “OPC UA way” to do whay you want? For example, if you just want to monitor all alarms on a server you simply make a MonitoredEventItem and give the Server NodeId (Identifiers.Server)

Anyway, if you really do need the nodes the only way is to literally recursively Browse the entire tree below Objects. The inverse references “trick” you mentioned should be ignored, that only works with our SDK due to how we have implemented them and it is in fact something we should disable as it is more of a problem if you have any larger amount of nodes. Plus you need to check as you noted that are they subtypes of the AlarmConditionType. If you use the UaNodes via client.getAddressSpace().getNode it is somewhat easy to do, but I’ll return to this if you really needed this. In general it would not be the “OPC UA way”, but it basically doesn’t have one good way (there is Query, but as far as I’m aware no server implements that, nor our own nor the SDK).

Also since you say “names” I should note that the index/namespace on the BrowseNames matter, any other information model can reuse the names in different namespaces (e.g. I could make a new type called AlarmType, just in a different namespace).