Connect Neat Pulse
Create an API key in Neat Pulse, add the connection in Offision, and sync your rooms and Neat devices. Allow about 10 minutes for setup, then check sensor values and timestamps on a synced device.
Connect Neat Pulse by creating an API key in Neat’s admin console, adding that credential in Offision, and choosing which rooms and Neat devices to sync. Offision then polls Neat Pulse automatically for sensor data.
What to prepare
- A Neat Pulse organisation with your Neat devices enrolled and reporting.
- A Neat Pulse administrator sign-in with access to organisation settings.
- A password manager or secure vault to store the API key and Organization ID.
- About 10 minutes for setup. Sensor readings appear in Offision after Neat supplies measurements and Offision retrieves them.
1. Create an API key in Neat Pulse
Sign in at signin.pulse.neat.no, open Settings in the left menu, and select API keys near the bottom of your organisation settings.
Neat Pulse organisation settings showing API keys near the bottom.
Select Create API key and enter a clear name such as Offision. Under Scope, select both Read and Write:
- Read allows Offision to sync rooms, devices, and sensor readings.
- Write allows Offision to reboot a Neat device remotely.
Leave Api.Rotate unselected, then choose Create.
Select both Read and Write under Scope, then choose Create.
Neat shows the API key only on the confirmation screen. Copy both the Key and the Organization ID shown above it before closing the dialog, because Offision requires both values.
Copy both the API Key and the Organization ID before closing the confirmation screen.
2. Open Neat Pulse in Offision
Open Marketplace and select the Neat Pulse tile under IoT monitoring. You can also open the same dialog from Devices › Platform integration.
The Neat Pulse tile under IoT monitoring in Marketplace.
3. Add the Neat Pulse connection
Select Add connection. The dialog opens on Guidelines, which includes step-by-step instructions and a downloadable PDF for your Neat Pulse administrator. Switch to Setup and fill in the connection fields:
| Field | What to enter |
|---|---|
| Name | A descriptive name for this connection, such as your Neat organisation name |
| Organization unit | The organisation unit in Offision that owns the synced devices |
| API Base URL | Keep the default URL unless Neat instructs you to use a different endpoint |
| Organization ID | The Organization ID copied in step 1 |
| API Key | The Key copied in step 1 |
| Poll interval (minutes) | Keep the default value. Sensor requests are paced automatically, and this field does not guarantee the maximum age of a reading |
The Add Neat Pulse Platform form with masked API Key input.
Save the form. Your new connection appears under Connections with a green status indicator.
4. Sync spaces and devices
Open the connection and choose Sync. The dialog lists everything visible to your API key in two sections:
- Spaces: Neat’s rooms.
- Devices: Neat endpoints with their model, Serial, Room, and Online status. Syncing also imports each device’s IP address and MAC address.
Select each room you want to import and choose a destination under Link to:
- Create new IoT space: Creates a standalone IoT space.
- Existing space: Merges readings into an existing IoT space.
- Bookable resource: Links the room’s sensor readings directly to a bookable room in Offision.
Next, select the devices in those rooms and choose Sync.
The Neat Pulse sync dialog with Spaces on top, Devices below, and Link to targets.
5. Verify synced devices and sensor readings
Open Devices in the dialog’s left navigation and select a synced device. Confirm that the device status shows Online. Open its Status tab and check that the Sensor data tiles display both values and timestamps for the sensors supported by that model. An Online device can still display an older measurement; see Sensor reading freshness and timestamps.
The Status page of a synced Neat device showing its sensor data tiles.
Select Open in Neat Pulse on the same page to confirm that the link opens the matching device in Neat’s console. To see where synced readings appear across rooms, calendars, and signage, read See Neat sensor data around Offision.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| Sync preview fails to load | The API key has Write scope only. Create a new key in Neat Pulse with both Read and Write selected. |
| Nothing appears under Spaces or Devices | The Organization ID is wrong and points to a different or empty Neat organisation. Check and update the Organization ID. |
| Selected devices are reported as skipped | Their parent room was not selected under Spaces. Select both the room and its devices, then sync again. |
| Connection status shows Suspended | Repeated polls failed, usually because the API key was revoked in Neat Pulse. Choose Edit, paste a valid API key, save, and choose Resume. |
| API Key field looks blank when editing | Existing keys are hidden for security. Leave blank to keep the current key. keeps your saved key unchanged. |
| Device is Online, but an expected sensor tile is missing | That Neat hardware model does not include that sensor. Check Sensor readings by Neat model. |
| Sensor tiles are empty or stop updating | Confirm that the device is reporting in Neat Pulse and the Offision connection is active. A successful poll may return no newer sample, so inspect measurement timestamps rather than waiting a fixed interval. |