Skip to content

Getting Started

This guide walks through the steps to onboard your organization onto the N-Hub IoT Platform.

Prerequisites

Before you begin, confirm the following with your platform administrator:

Onboarding checklist

  • [ ] Your organization has been created in N-Hub
  • [ ] Your email domain has been registered as an allowed domain
  • [ ] Your identity provider (Azure AD, Google Workspace) has been configured — or local user accounts have been created
  • [ ] You have received confirmation of your environment URL

Step 1: Sign In

  1. Navigate to the portal: https://dev-au-03.nnnco.io
  2. Click Sign In
  3. Authenticate with your corporate credentials (Azure AD, Google) or the local credentials provided by your administrator
  4. On first login, your account is automatically linked to your organization based on your email domain

Step 2: Explore the Portal

After signing in, you will see:

  • Dashboard — Overview of your devices, sites, and recent activity
  • Devices — List of registered devices and their latest readings
  • Sites — Geographic locations where your devices are deployed
  • Base Stations — LoRaWAN gateways (if applicable, synced from ThingPark Wireless)

Step 3: Register Devices

Devices can be registered through:

  • Portal — Add devices manually through the web interface
  • API — Programmatically register devices via the REST API
  • Network Server Sync — Devices are automatically discovered when data arrives from configured network servers

Step 4: Configure Data Ingestion

Depending on your device connectivity:

Connectivity Setup
LoRaWAN (via TPW) Your administrator configures the ThingPark Wireless webhook. See TPW Integration.
HTTP Webhook Configure your system to POST device data to the webhook endpoint.
MQTT Connect your MQTT client to mqtt.dev-au-03.nnnco.io on port 8883. See MQTT Streaming.

Step 5: Set Up Parsers

If your devices send raw payloads that need decoding, you'll need a parser. See the Parser Guide for instructions on writing and deploying parsers.

Step 6: Access the API

The REST API allows you to:

  • Query device data programmatically
  • Manage device registrations
  • Retrieve readings for analysis or integration with your own systems

Explore the API

Next Steps