Retrieve alarms and ingest external point values in Siemens Building X
domain: developer.siemens.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET .../partitions/{partition}/devices/{deviceId}/events to list current and past events/alarms for a device
To push readings, POST .../partitions/{partition}/points/{pointId}/values with a JSON:API array of PointValue objects (timestamp + value), 1-100 values per batch
Expect HTTP 204 if no timestamp conflicts occurred, or 202 with a list of 0-based indices for any dropped duplicate-timestamp values
Add ?overwrite=true to the POST to force-overwrite values colliding on timestamp
Known gotchas
Only one pointValue per millisecond is stored — later values for a timestamp that already exists are silently dropped unless overwrite=true is set
The events endpoint is scoped per device, not per point or partition-wide — you must already know the deviceId
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?