Facilities BMS feed

Phase 1 preview — pages render fixture data only; no changes are saved.

Facilities BMS feed

Needs configuration

Switched on but not ready. Missing: Source ID path. It is skipped until these are set.

The last sync reported 1 error. Stopped: source ID path is not set, so records cannot be matched.

Connection

Type: Custom HTTP
Label: Facilities BMS feed
Address key: facilities-bms-feed
Company: Shared
Switched on: Yes
Push to vendor: Supported
Server: bms.example.test
Created: 2026-09-20 10:00 Alex Kim

Only the host of the server address is shown. Credentials are stored encrypted and never leave the server.

Credentials and settings

Field	Value	Details
Authentication	bearer	Required
Bearer token	Configured	—
Basic username	—	—
Basic password	Not configured	—
API key header	—	—
API key value	Not configured	—
Pull path	/api/devices	—
Records path	data.items	—
Source ID path	—	Required

A secret is write-only: a blank input keeps the stored value.

Sync options

Asset tag pattern: TC-{serial}
Default category: Discovered Hardware
Default status: Pending
Match people by: Username, then email
Create assets that don't exist: Yes
Adopt an existing asset by serial number: Yes
Fetch details per device: Yes
Suppress notifications: Yes
Check in when the vendor has no user: No
Push is a dry run: No
Push note template: —

Field mapping

Vendor field	Stored in	Direction
Hostname	name	Vendor → asset
Serial number	serial	Vendor → asset
Asset tag	asset tag	Skipped
Model	model	Vendor → asset
MAC address	primary mac	Vendor → asset
IP address	primary ip	Vendor → asset
Operating system	os	Vendor → asset
OS version	os version	Vendor → asset
Last seen	last seen	Vendor → asset

Last sync

Last sync: 2026-09-30 03:00
Devices seen: 0
Skipped: 0
Errors: 1
Result: Stopped: source ID path is not set, so records cannot be matched.

Legacy keeps only the latest result as free text: there is no run history.

Linked assets (0)

No linked assets

Devices appear here after a sync links them to assets.

Each asset links to at most one device per instance. Deleting an instance leaves these rows behind, and a new instance with the same address key picks them up again.