TPW Integration¶

N-Hub integrates with Actility's ThingPark Wireless (TPW) platform to ingest LoRaWAN device data and sync base station information.

Overview¶

The integration provides two capabilities:

Device data ingestion — LoRaWAN uplink messages are forwarded from TPW to N-Hub via HTTP webhooks
Base station sync — Gateway status, location, and health data is periodically synced from the TPW API

How It Works¶

LoRaWAN Device
      │
      ▼ (radio)
Base Station (Gateway)
      │
      ▼
ThingPark Wireless (Network Server)
      │
      ├──── Webhook ────▶ N-Hub (device data)
      │
      └──── API sync ───▶ N-Hub (base station status)

Device Data Flow¶

A LoRaWAN device transmits a message
One or more base stations receive the radio signal
ThingPark Wireless deduplicates and forwards the message to N-Hub's webhook endpoint
N-Hub processes the message through its data pipeline

Base Station Sync¶

N-Hub periodically queries the TPW API to:

Discover base stations associated with your organization
Update connection status (online, offline, alarm)
Sync geographic coordinates for site mapping
Track gateway health metrics

Enterprise Mapping¶

Your organization in N-Hub is linked to your TPW supplier account. This mapping determines which base stations and devices are synced.

To enable the integration, provide your platform administrator with:

Your TPW Supplier ID (visible in the ThingPark Wireless console)
Optionally, your TPW Subscriber ID for subscriber-level access

Site Assignment¶

When a base station has GPS coordinates in TPW, N-Hub can automatically create a site for it:

Scenario	Behavior
No existing site assignment	Site created from TPW coordinates
Existing site (from TPW sync)	Coordinates updated
Existing site (manually assigned)	Manual assignment preserved — TPW data does not overwrite

Manual site assignments always take precedence over automatic assignments from TPW.

What You See in N-Hub¶

Once the integration is active:

Base Stations page shows your gateways with live status
Sites page includes auto-created sites from gateway coordinates
Devices receive data through the standard pipeline

Setup¶

TPW integration is configured by your administrator during onboarding. To request setup or changes, contact your platform administrator with:

Your TPW account details (supplier ID)
The webhook URL for your N-Hub environment (provided by your administrator)
Any custom parsing requirements for your device types

Error Handling¶

The TPW integration includes automatic retry logic:

Scenario	Behavior
TPW API temporarily unavailable	Retry with exponential backoff (up to 3 attempts)
Rate limited (429)	Retry after the period specified by TPW
Authentication expired	Token refreshed automatically
Unknown base station	Logged for investigation, no data loss