Skip to content

Integrations

Configure integrations in Settings → Integrations. All credentials are stored server-side in config.yaml and never sent to the browser.

Media & Downloads

Plex

FieldDescription
URLhttp://192.168.1.10:32400
TokenFound in Plex Web → Account → XML API (in the URL)
yaml
web:
  plexUrl: "http://192.168.1.10:32400"
  plexToken: "xxxxxxxxxxxxxxxxxxxx"

Radarr

FieldDescription
URLhttp://192.168.1.40:7878
API KeyRadarr → Settings → General → API Key

Sonarr

FieldDescription
URLhttp://192.168.1.40:8989
API KeySonarr → Settings → General → API Key

Prowlarr

FieldDescription
URLhttp://192.168.1.40:9696
API KeyProwlarr → Settings → General → API Key

Jellyfin

FieldDescription
URLhttp://192.168.1.10:8096
API KeyJellyfin → Admin Dashboard → API Keys → New Key

qBittorrent

FieldDescription
URLhttp://192.168.1.40:8080
UsernameqBittorrent Web UI username
PasswordqBittorrent Web UI password

The Web UI must be enabled: qBittorrent → Tools → Options → Web UI.


Networking

Pi-hole

FieldDescription
URLhttp://192.168.1.53
API TokenPi-hole admin panel → Settings → API

Works with Pi-hole v5 (legacy ?summaryRaw API) and v6 (new REST API). NOBA detects the version automatically.

UniFi

FieldDescription
URLhttps://192.168.1.1 (controller URL)
UsernameLocal admin username
PasswordLocal admin password

NOBA uses a dedicated httpx client with cookie persistence for UniFi authentication.

AdGuard Home

FieldDescription
URLhttp://192.168.1.53:3000
UsernameAdGuard admin username
PasswordAdGuard admin password

Storage & Infrastructure

TrueNAS SCALE

FieldDescription
URLhttp://192.168.1.30
API KeyTrueNAS → Settings → API Keys → Add

Surfaces pool health, apps, alerts, and VMs.

Proxmox VE

FieldDescription
URLhttps://192.168.1.200:8006
Token IDuser@pam!token-name
Token SecretSecret from PVE → Datacenter → API Tokens

Synology DSM

FieldDescription
URLhttp://192.168.1.25:5000
UsernameDSM admin username
PasswordDSM admin password

Monitoring

Uptime Kuma

FieldDescription
URLhttp://192.168.1.20:3001

Enable Prometheus metrics in Kuma: Settings → Security → "Enable Prometheus metrics endpoint". No API key required.

Grafana

FieldDescription
URLhttp://192.168.1.20:3000
API KeyGrafana → Administration → Service accounts → Add token

InfluxDB

FieldDescription
URLhttp://192.168.1.20:8086
TokenInfluxDB → API Tokens → Generate
OrgOrganisation name
BucketTarget bucket for NOBA metrics

Smart Home & IoT

Home Assistant

FieldDescription
URLhttp://192.168.1.100:8123
Long-Lived TokenHA → Profile → Long-Lived Access Tokens

ESPHome

FieldDescription
URLhttp://192.168.1.100:6052
API Key(optional) ESPHome dashboard API key

Containers & Orchestration

Kubernetes

FieldDescription
KubeconfigUpload ~/.kube/config or paste contents

Or use in-cluster credentials if NOBA runs inside Kubernetes.

Portainer

FieldDescription
URLhttp://192.168.1.20:9000
API KeyPortainer → My account → Access tokens

Version Control & CI/CD

Gitea

FieldDescription
URLhttp://192.168.1.20:3000
TokenGitea → Settings → Applications → Generate token

Forgejo

Same as Gitea — the API is compatible.

GitHub Actions / GitLab CI

Connect via webhook: configure your CI pipeline to POST run status to NOBA's automation webhook endpoint.


Network Configuration

Radar Targets (Ping Monitor)

Enter a comma-separated list of hosts in Settings → Integrations → Radar IPs:

192.168.1.1, 8.8.8.8, google.com, my-nas.local

Monitored Services

Enter a comma-separated list of systemd service names:

nginx, docker, postgresql, sshd

Bookmarks

Format: Name|URL|FontAwesomeIcon (comma-separated):

Router|http://192.168.1.1|fa-network-wired, Pi-hole|http://192.168.1.53|fa-shield-alt

Released under the MIT License.