What Neat Pulse syncs into Offision
See how Offision polls Neat Pulse for spaces, device inventory, and room sensor readings across Neat models, how reading timestamps and freshness work, and what stays managed in Neat Pulse.
Offision connects to Neat’s management cloud (Neat Pulse) with an API key and retrieves your Neat rooms, devices, and environmental or occupancy sensor readings through automatically paced polling. Nothing is installed on your Neat hardware, and Offision never connects directly to the devices on your local network.
Offision polls Neat Pulse automatically and routes sensor readings to linked rooms, calendars, and signage; polling does not guarantee a new measurement on every request.
Spaces, devices, and network addresses
Neat Pulse organises devices by room, and Offision preserves that hierarchy during sync:
- Each selected Neat room becomes an IoT space in Offision.
- A Neat device syncs only when its parent room is also selected. Devices in unselected rooms are skipped.
In the sync dialog, Link to controls where each room’s sensor readings go:
- Create new IoT space: Creates a standalone IoT space.
- Existing space: Merges readings into an IoT space you already have.
- Bookable resource: Links readings directly to a bookable room so sensor data appears on the booking calendar, room panel, and signage.
Clearing a room later removes only the records created by this Neat Pulse connection. Shared IoT spaces that also receive data from another platform remain intact.
When you run Sync or Resync, Offision also imports the IP address and MAC address that Neat Pulse reports for each device, populating the IP address column in your device list. Background sensor polling does not update IP or MAC addresses.
Each model brings a different sensor suite
Every synced endpoint appears in Offision as a Neat Device and displays sensor tiles only for the measurements that hardware model supports. Unsupported sensors are hidden rather than shown as zero.
| Neat model | Supported readings |
|---|---|
| Neat Pad, Neat Pad Pro | Temperature, humidity, CO2, TVOC |
| Neat Bar, Neat Board | Temperature, humidity, CO2, TVOC, light level, people count, occupancy |
| Neat Bar Pro, Neat Frame, Neat Board 50, Neat Board Pro, Neat Board 32 | Temperature, humidity, VOC index, light level, people count, occupancy |
| Neat Bar Gen 2 | Light level, people count, occupancy |
| Neat Center | People count, occupancy |
Keep two measurement differences in mind when comparing models:
- VOC index versus CO2 and TVOC: Newer models report a relative VOC index instead of absolute CO2 and TVOC concentrations.
- Derived occupancy: Neat cameras report people count, and Offision marks the room as occupied whenever the people count is greater than zero.
Sensor reading freshness and timestamps
A successful poll can still return an older measurement from Neat Pulse. Offision preserves Neat’s sample timestamp when available and skips samples whose timestamp has not advanced, so a displayed people count or environmental value can be older than one poll interval.
Offision paces sensor requests automatically within Neat Pulse’s API request budget. The connection form’s Poll interval (minutes) field does not guarantee a maximum reading age. API rate limits, failed requests, or a device that stops reporting to Neat Pulse can all delay new readings. Always check both the reading’s timestamp and whether the device is Online before treating a displayed count as current.
What Neat Pulse does not sync
Neat Pulse provides room sensing and device status only, not calendar scheduling:
- No bookings, meetings, or directory users: Sync room calendars and users separately from Microsoft 365 or Google Workspace.
- Limited device actions: From Offision, you can reboot a Neat device or run Resync. All other device settings remain managed in Neat Pulse.