Unifi OS

The Hudu and UniFi OS integration automatically syncs your UniFi network data into Hudu using Ubiquiti's official API, helping keep device inventories and infrastructure documentation accurate, organized, and up to date.

    Visit Understanding Integrations for basic concepts and useful tips before setting up this integration.

   UniFi OS is a separate integration from UniFi (legacy). Use UniFi OS to connect through Ubiquiti's API with an API key. If you manage a locally hosted UniFi Network controller, use the UniFi (legacy) integration instead.

What you'll need

  • One or more UniFi API keys, generated from your Ubiquiti account.
  • An Admin or Super-Admin user role within Hudu.

   You can return to your Hudu admin area → IntegrationsUniFi OS at any time to make changes to the integration.

What this integration syncs

The UniFi OS integration can sync the following into Hudu:

  • UniFi-provided devices — pulls device information from UniFi into an asset layout.
  • Client devices — pulls client device information from UniFi into an asset layout.
  • Guest devices — pulls guest device information from UniFi into an asset layout.
  • Networks — syncs each network and adds it to the IPAM component of the matched company.

   Client and guest devices are related to the network they belong to. UniFi-provided devices are synced as assets but are not related to the network.

Setting up the integration

To enable the integration, navigate to the Hudu admin area (Admin → Integrations) and select UniFi OS from the list.

Step 1. Enter your credentials

  • Enter your UniFi API key. This field is required and cannot be left empty.
  • To sync data across more than one UniFi account, add additional API keys. Keys can be added, saved, and removed at any time.
unifios_add_api_key.png

Step 2. Test the Connection

  • Once the test connection is successful, you will automatically be moved to the next step to activate and sync the integration.

Step 3. Activate and Sync

  • Activate and sync the integration to begin pulling over companies. 
    • Sync time may vary, depending on the amount of data.
  • You may navigate away from this page while sync is in progress.
unifios_activate_and_sync.png

 

Step 4. Options

In the Options section, customize which items you'd like to sync, what information you'd like Hudu to update, and how you'd like Hudu to match assets.

Options:

  • Auto-update names of assets — automatically sync asset names from UniFi to keep them current.
  • Do not update basic company details — this includes company type, sync status, and the company active/inactive state.
  • Match assets on primary serial — if checked, assets will only be matched if both the asset name and primary serial number match.

Skip the following

  • Check any data type you don't want to bring into Hudu:
    • Inactive companies (will be checked by default)
    • UniFi provided devices
    • Client devices
    • Guest devices
    • Networks
  • Click Save Options to move to the next step.
    Enabling client and guest devices can pull in a large number of assets (phones, laptops, and other connected devices). If you only need infrastructure devices, skip client and guest devices to keep your documentation focused.

Step 5. Device Types

The Device Types section lets you skip specific device types. The device types listed reflect what's found in your UniFi data.

  • Skip the following UniFi provided device types — for example, accessPoint, gateway, and switching.
  • Skip the following client/guest device types — for example, teleport, vpn, wired, and wireless.
  • Click Save Device Types to move to the next step.
unifios_skip_device_types.png

Step 6. Match your companies

  • Match at least one company, then select Sync Now to complete the set up.
    • Companies are organized under Unmatched and Matched tabs, and can be filtered by All match types, Suggested matches, and No suggested matches.
    • Match each UniFi company to an existing or new Hudu company. Companies left unmatched, along with their data, are not imported.
    • Hudu recommends matching one company first to confirm data imports correctly before matching the rest.
unifi_os_match_companies_sync_now.png

   Re-sync the integration any time you make changes in the Companies section.

Step 7. Asset Layouts

  • Select the asset layouts you'd like Hudu to use for each category below, then re-sync the integration to complete set up.
    • In the Asset Layouts section, select a default asset layout for each category: UniFi Devices, Client Devices, and Guest Devices. Each is required.
    • Use Add Sort Rule to create additional rules that better organize your configurations or create exceptions to the defaults above.
    • Click Save Asset Layouts when you're done.
unifios_save_asset_layouts.png

   Changes in the Asset Layouts section only apply to new data that has not already been synced into Hudu.

 

Step 8. Run a sync

After matching your companies and setting your asset layouts, click Sync Now to bring in your devices and networks. Networks are added to the IPAM component of their matched company.

    Active integrations re-sync automatically every 3 hours. You can also trigger a manual re-sync from the integration settings page or the re-sync button in the top right of an asset card.

How Hudu names your UniFi sites

When you connect UniFi OS, Hudu imports your sites so you can match them to companies in Hudu. The name Hudu displays for each site depends on how the console is set up.

Consoles with more than one site — Hudu shows the site name as it appears in UniFi.

Consoles with a single site — Hudu shows the console name instead.

The reason for the difference is that UniFi only offers a site rename option when a console has more than one site. On a single-site console, the site is always named "Default" and there is no way to change it. If Hudu displayed that name, every single-site console in your account would appear as "Default" with no way to tell your clients apart. Using the console name — the name you already gave it in UniFi — keeps each one identifiable.

Changing the name Hudu displays

For a single-site console, rename the console in UniFi Site Manager under Control Plane → Console. Keep in mind that this also renames that device in your UniFi device list.

For a console with multiple sites, rename the site itself in the UniFi Network application.

Either way, the updated name appears in Hudu after the next sync.

Renaming is safe

Hudu tracks each site by a permanent internal ID rather than by its name. Renaming a site or console in UniFi will not break an existing match or interrupt device syncing — the name shown in Hudu simply updates on the next sync.

FAQ

What is the difference between UniFi OS and UniFi (self-hosted)?

UniFi OS connects to UniFi through Ubiquiti's API using an API key, and supports multiple accounts. UniFi (self-hosted) connects directly to a locally hosted UniFi Network controller using a domain, username, and password. Controllers running UniFi OS are not supported by the self-hosted integration, which is why UniFi OS exists as a separate integration.

How often does the integration sync?

Native integrations automatically re-sync every 3 hours. You can also run a manual re-sync at any time from the integration settings page or with the re-sync button in the top right.

Can I connect more than one UniFi account?

Yes. In the credentials step you can add multiple API keys. Keys can be added, saved, and removed at any time.

Where do my synced networks appear?

Each synced network is added to the IPAM component of its matched company.

Why aren't my UniFi-provided devices linked to a network?

This is expected. UniFi-provided devices are synced as assets but are not related to a synced network. Client and guest devices are related to the network they belong to.

Troubleshooting

My test connection is failing with a 401 Unauthorized error

This almost always means the wrong type of API key was entered. UniFi has two different key types, and only one works with this integration.

Site Manager API key (correct) — generated at unifi.ui.com under Profile > API. This is the key the UniFi OS integration requires.

Local Network Integration key (incorrect) — generated from within a local console under Network > Control Plane > Integrations. This key only works with a local console URL and will always return a 401 when used here.

To fix this, log in to unifi.ui.com, go to Profile > API, and generate a new Site Manager API key. Copy it once, then paste it directly into the API key field in Hudu with no extra spaces or line breaks, and re-test the connection.

If you manage more than one UniFi account, each account needs its own Site Manager API key. Confirm you're generating the key while logged into the same UniFi account that owns the sites you expect to see in Hudu.

I don't see a Device Types section during setup

During initial setup, the Device Types section only appears when at least one device category is kept in the Options step. If you skipped UniFi provided, client, and guest devices, the section is skipped and you're taken directly to the Companies step. Un-check one of those device categories under "Skip the following" to bring it back. Note that when you edit an existing integration, the Device Types section stays visible even if all types are skipped.

Too many client devices were synced in

Client and guest devices can add a large number of assets. Disable those categories in the Options step to stop syncing them going forward, then archive or clean up the assets that were already brought in.

Was this article helpful?
0 out of 0 found this helpful