How to resolve UISP Link Import Issues

Sometimes MeshDB is unable to automatically convert links in UISP into the appropriate MeshDB Link object. When this happens the symptoms can be any of the following:

• Incorrect data in MeshDB
• Manually corrected data in MeshDB, but it gets modified each hour to be incorrect again
• Spamming of messages in #meshdb-alerts on Slack

In order to resolve this, it can help to give MeshDB a "hint" about what is going on in UISP. We can achieve this by manually creating/editing the MeshDB Link object and specifying the UISP UUID value manually.

Finding the UISP Link UUID

Unfortunately Ubiquiti doesn't make it easy to see what the UUID for a given link is in the UISP UI, so there is a somewhat roundabout method for determining it. These instructions assume the use of Google Chrome, but there's proably a way to do the same thing Firefox/Safari/Edge. First, open the topology view for the link that you are trying to import (but don't select the link yet):

Next, open the Chrome dev tools by pressing F12 or going to View -> Developer -> Developer Tools. Open the "Network" tab.

While the network tab is open, select the link you want to identify in the UISP topology UI, and wait a few seconds for the interface data to populate:

Selecting the link will cause UISP to make a network request which includes the "datalink" UUID. To find it, use the network search feature by clicking the magnifying glass:

Search dataLinkId to find the correct request:

Use the UISP Link UUID in MeshDB

Next, go to MeshDB and create/edit the Link object so that the data looks accurate. Set the UISP Id to the value we identified above and Save the Link

Monitor for Changes

Come back in after more than an hour or keep an eye on the #meshdb-alerts slack channel to make sure the UISP importer has correctly understood your changes