Lambent Spaces Source
Lambent Spaces estimates how many people are in a space from the building's Wi-Fi. This connector brings Lambent's buildings, levels and zones into Mapped as Buildings, Floors and Spaces. Every 15 minutes it then records the occupancy Lambent measured for each of them.
Each place keeps its own readings at its own level. A building, a floor and a zone each carry the mean and peak occupancy Lambent reports for that level. They also carry utilization as a percentage, which fills in wherever Lambent knows the place's capacity.
Use Cases
- Set back HVAC in empty spaces: Find buildings, floors and zones that are unoccupied, so Active Control can apply setbacks during those periods.
- Find under-used space: Compare utilization across buildings, floors and zones to inform consolidation and space planning.
- Put occupancy next to everything else: Lambent's readings land on the same places as your other systems, so occupancy can be queried alongside energy, equipment and work orders.
Configuration
Auth Requirements
Lambent issues credentials on request from [email protected]. Enter an API key, or turn on Use OAuth client credentials on the Authentication tab to enter OAuth client credentials instead; only the fields for the chosen method are shown and saved.
| Field | Required | Description |
|---|---|---|
| API Key | For API key | A Lambent API key. It starts with lsk_. |
| OAuth Client ID | For OAuth | The client id of a Lambent machine-to-machine (client credentials) app. |
| OAuth Client Secret | For OAuth | The matching client secret. |
Notes:
- The credentials are checked against Lambent when you save. They are rejected if Lambent does not accept them.
- API keys expire on a date Lambent sets when it issues them. Ask Lambent for a new key before then and save it here; Lambent can keep the old and new keys valid together, so there is no gap.
- The credentials decide which buildings you see. Lambent returns only the buildings they have been granted, and capacity and utilization only for buildings with capacity access.
Connector Entities
Lambent is the source of its own space hierarchy, so you choose which of its places to bring into Mapped. Three tabs appear after authentication. Complete them in order, because each level attaches to the one above it:
| Tab | Contents | Saved as | Fields you complete |
|---|---|---|---|
| Buildings | Every Lambent building | Buildings | Name, Postal Address |
| Levels | Every Lambent level | Floors | Name, Floor Level, Building |
| Zones | Every Lambent zone | Spaces | Exact Type, Name, Space Code, Floor |
The tabs use Lambent's names; the tables inside use Mapped's.
Notes:
- Postal Address is required and has no default, because Lambent does not publish addresses. The address is what lets a building match the same building from another connector.
- Building and Floor are filled in for you once the Lambent parent has been saved. Save your buildings, then import levels, and each level arrives with its Lambent building selected; the same goes for zones and their levels. If the parent has not been saved, the column is blank: pick a parent in the grid or set it with a rule. The read-only @buildingName and @levelName columns show Lambent's own parent.
- A row you have already saved keeps the parent it was saved with.
- Floor Level is read from the level's name: "Level 1" is the ground floor, which is level 0 in Mapped. A name with no level number arrives blank for you to set.
- Exact Type of a zone starts as Space. A Lambent zone can be anything from one meeting room to a whole open-plan desk area, so set each zone to what it really is. You can choose a kind of Space (Room, Office, Open Office, Enclosed Office, Conference Room, Common Space, Break Room, Cafeteria, Lobby, Laboratory) or Zone and any kind of Zone, such as Occupancy Zone, Workspace or HVAC Zone. A zone set to a Zone type is saved as a Mapped Zone rather than a Space.
- Space Code is empty. A Lambent zone usually covers several rooms, so the connector does not guess a room code. Set one for a zone that is a single room, so it can match that room from other systems.
- Lambent's capacity for a place, when it has one, is shown in the read-only @capacity column and saved as the place's maximum occupancy.
Backfill
Run the Backfill Occupancy job from Jobs to load historical occupancy for a date range onto the places you have saved, at the same 15-minute intervals as the regular sync. Each run's progress and result appear under Jobs. A long range takes a few minutes.
Advanced Config
| Option | Type | Default | Description |
|---|---|---|---|
pollWindowHours | Number | 3 | How many hours back each sync re-reads. Lambent publishes occupancy 30–60 minutes late, so recent intervals are re-read until they fill in. |
batchSize | Number | 250 | How many records are saved per request when you save buildings, floors or spaces. |
Mapped Concepts
API to Mapped Entities
| Lambent Concept | Mapped Entity | exactType | Description |
|---|---|---|---|
| Building | Building | Building | A Lambent building. |
| Level | Floor | Floor | One floor level in a building. |
| Zone | Space or Zone | Space by default; any Space or Zone type you choose (Room, Conference_Room, Occupancy_Zone, Workspace, …) | The area covered by one or more Wi-Fi access points; often several rooms. |
Lambent regions are not imported. They are not exposed through Lambent's API.
Relationships:
- Each Building hasPart its Floors, and each Floor hasPart its Spaces.
- Each Building, Floor and Space hasPoint its occupancy points.
API to Mapped Points
Every saved building, floor and space has its own points. Each value covers one 15-minute interval and is timestamped at the start of that interval.
| Point Name | exactType | Datatype | Unit | Description |
|---|---|---|---|---|
| Occupancy Count | Occupancy_Count_Sensor | DOUBLE | NUM | Mean estimated number of people during the interval. |
| Peak Occupancy Count | Occupancy_Count_Sensor | INT | NUM | Most people estimated at once during the interval. |
| Occupancy Utilization | Occupancy_Utilization_Sensor | DOUBLE | PERCENT | Mean occupancy as a percentage of capacity. Empty while Lambent has no capacity for the place. |
| Peak Occupancy Utilization | Occupancy_Utilization_Sensor | DOUBLE | PERCENT | Peak occupancy as a percentage of capacity. Empty while Lambent has no capacity for the place. |
Notes:
- Lambent publishes occupancy 30 to 60 minutes after the fact, sometimes later, so the newest intervals appear with that delay.
- An interval where Lambent has no data is left empty, not recorded as zero. A recorded zero means Lambent measured the space as empty.
Heartbeats
This connector does not currently implement heartbeats.
Graph Diagrams
Sample Code
The latest occupancy reading for every point, with the place it belongs to
{
points(filter: { connectedDataSourceId: { eq: "your-connector-id" } }) {
id
name
exactType
unit {
name
}
isPointOf {
... on Space {
id
name
maxOccupancy
}
... on Floor {
id
name
}
... on Building {
id
name
}
}
series(latest: true) {
timestamp
value {
float64Value
}
}
}
}
Hourly average occupancy for one space over a day
{
points(filter: { id: { eq: "PNT4ZqV8nKs2HdRw7XcLmT9aB" } }) {
name
aggregation(
startTime: "2026-05-20T04:00:00Z"
endTime: "2026-05-21T04:00:00Z"
period: HOUR
periodIncrement: 1
) {
timestamp
avg
max
}
}
}
Changelog
2026-11-17
- Added: Bring Lambent buildings, levels and zones into Mapped as Buildings, Floors and Spaces. A floor or space is linked to its saved Lambent parent automatically.
- Added: Mean and peak occupancy every 15 minutes for each building, floor and space, plus utilization where Lambent knows the capacity.
- Added: Backfill historical occupancy for a date range.
- Added: Sign in with a Lambent API key or OAuth client credentials.