How to filter AddOn entries?

How to filter AddOn entries?

avatar

Hi,

I need to fetch all entries of type "Mikrotik Winbox" using PowerShell. I noticed that they have ConnectionType equal to AddOn. But then, how do I filter AddOn of specific type? I can reverse-engineer the GUID in the ConnectionSubType to be 59c4de6b-864c-4dbc-8183-489f40233004 for Mikrotik. But there are 2 questions:

  • Is this the right way of filtering them?
  • Is there a dictionary of the ConnectionSubTypes that I could use, and not do the guesswork? For example if I need to filter specific entries that might not (yet) exist, how can I determine its subtype other than by tedious work of creating a sample entry, and then doing the above again?


Thanks.

All Comments (3)

avatar

Hello,

Using the ConnectionSubType is the way to filter specific types of AddOns.

There isn't currently an existing dictionary or documentation listing all Add-on IDs, but I’ll look into whether we can add a documentation page or provide a way to access them—possibly through a cmdlet. In the meantime, if you have specific Add-on types in mind, let me know and I’ll do my best to find the corresponding IDs for you.

Best regards,
Maxime

avatar

Thank you. For now it's only about Mikrotik, so I'm fine as you confirmed the way of filtering them.
For the future a pre-filled dictionary would be great (so that it doesn't need to be constructed on every invocation). It may be a cmdlet, or an enum type, just cache the data if possible.

For now I'm trying to understand differences between entries obtained via Get-RDMEntry and Get-HubEntry. They don't seem to be compatible, and that can possibly make working with them more troublesome than necessary, but it's another topic. If I find issues, I'll post separate report.


avatar

Hello,

Starting from version 2025.2.6 of the module, the Get-RDMAddOnId cmdlet allows you to retrieve the connection subtype value for an add-on.

Note: the prefix (e.g., RDM, Hub) refers to the subset the cmdlet belongs to. These prefixes help organize cmdlets based on their associated feature set or product scope. Cmdlets from different prefixes are not interchangeable.

Best regards,
Maxime