I am not able to receive SSID / Network Site / VLAN / Parent Node / Parent Port through notifications

[SubBass100]

What installation are you running?

Production (netalertx) 📦

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://docs.netalertx.com/

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Edge
• Safari (unsupported) - PRs welcome
• N/A - This is an issue with the backend

Current Behavior

I am using unifi network application (selfhosted) I am able to receive notifications about MAC / IP / Hostname through ntfprcs (notification processing) however, I am not able to receive SSID / Network Site / VLAN / Parent Node / Parent Port through notifications. Actually per device all but Parent node are either blank or None. Is this exposed by the unifi API? I thought it was, is there some other setting I need to set somewhere else? Either way it would be great to have those values. Also thanks for this software it kicks ass!

Expected Behavior

I would expect connected SSID / Network Site / VLAN / Parent Node / Parent Port to be available through the notification processor.

Steps To Reproduce

1 I use unfimp plugin to get data from unifi network application (self hosted)
2 I have notification processor set to display variables on new device found
3 devices do show parent node but not parent node port, ssid, network site, or vlan
4 notifications leave those areas blank

Relevant app.conf settings

docker-compose.yml

Debug or Trace enabled

• I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.

Relevant app.log section

  PASTE LOG HERE. Using the triple backticks preserves format.

Docker Logs

  PASTE DOCKER LOG HERE. Using the triple backticks preserves format.

[jokob-sk]

Hey @SubBass100,

Thanks for the kind words about NetAlertX!

To answer your question about whether these fields are exposed by the UniFi API: some are, but others are blocked by hard limitations in UniFi's official public API schema.

Here is the exact breakdown of what is currently implemented, what isn't, and why:

Feature Implementation Status

Field / Feature	Status	Notes
Network Site	Implemented	Available via site name configuration mapping.
VLAN (ID & Name)	Implemented	Mapped from network configurations and client details (helpVal2 / helpVal3).
WAN Name	Implemented	Mapped from WAN configurations (helpVal4).
Parent Node	Implemented	Resolved via uplinkDeviceId mapping to the parent UniFi device MAC.
Connected SSID	Not Implemented (Official API)	The official public Integration API (/integration/v1/...) does not expose the active wireless SSID for clients. (Though it can be retrieved if pulling data directly from a local controller/legacy stat/sta endpoint).
Parent Port	Not Possible	Hard limitation of the official UniFi API. The public API integration tier does not expose switch port index mappings for connected clients (wired or wireless).

---

Technical Context

• Parent Nodes, VLANs, & WANs: Recent updates properly map site names, VLAN IDs, VLAN names, and WAN interfaces into tracking attributes so that notification processors (ntfprcs) can pick them up.
• The "Parent Port" & "SSID" Wall: While the UniFi UI web app clearly tracks switch ports and wireless SSIDs, that topology and client association data is hidden behind internal controller endpoints that aren't available in the official public API documentation. Until Ubiquiti exposes those fields in their public integration tier, physical port tracking and SSID reporting aren't feasible through standard public API integrations.

This should be available in the next release.

It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container (make sure you use a unique PORT and GRAPHQL_PORT if running instances concurrently) with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may revert the changes to avoid introducing bugs.

If you find NetAlertX useful, consider sharing the app on forums or socials, at your work, or share a quick review on Reddit or elsewhere to help support the project. See more ideas and how-to in the growth playbook.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[SubBass100]

I finally got around to testing this on (next_release) ! I am happy to report that {devSite} works and I can accurately see the unifi site which the device is connected. However,{devVlan} and {devSSID} still do not populate. On a side note Parent Node IS populating, I know this it out of scope but it IS populated correctly when you click on a device. It would be super useful if this is an option to display for new devices with Notification Processing. I hope this helps, I'll be reverting back to latest branch.

[jokob-sk]

Hi @SubBass100 ,

Thanks for testing.

As mentioned, regrettably devSSID is not available in the API so can't be populated automatically.

I also double checked and devVlan is not available in the API either, so the only additional data point available is devSite (the above table is incorrect, the Vlan and WAN values are not supplied by the API so thus I can't implement their retrieval.

[SubBass100]

devSite does work though Id call that a win! also Parent Node is working which is good also! Thanks for working on this. will you keep devSite and possibly parent node? Those are important to know which site the machine is connected to and which switch therein. Thanks again!

[jokob-sk]

Hi,

I will keep the devSite implementation, however I will think about the Parent node feature request as I feel the notification table is bubbling over a bit with information, so I will give it more thought before implementing it in a more UX friendly and maintainable way.