{"id":"9466aa53-e818-474b-a006-9eee611292f5","task":"Map Metasys equipment to the underlying controller objects via equipment points","domain":"jci-metasys.github.io","steps":["Locate the equipment instance by walking GET {base}/equipment/tree (Metasys 15.0+) or from a space via GET {base}/spaces/{spaceId}/servingEquipment.","GET {base}/equipment/{equipmentId}/points to list that equipment's points. Page with page and pageSize; sort accepts shortName, -shortName, category, -category, isDisplayData, -isDisplayData (default shortName).","For each item read: id, itemReference, equipmentName, shortName, label, category, isDisplayData, equipmentUrl, objectUrl, and attribute (a value from attributeEnumSet). On Metasys 15.0+ each item also carries objectReference, the underlying object's FQR.","Understand the model: an equipment point is a mapping from a semantic point name to a specific attribute on a specific object. shortName is the semantic name (e.g. a zone temperature); objectUrl plus attribute is where the live value actually lives.","Read the value by following objectUrl and appending /attributes/{attribute}, or by resolving objectReference through GET /objects/identifiers?fqr=.","Filter to operator-facing points using isDisplayData when you want the same subset the Metasys UI shows rather than every mapped attribute.","Go the other direction with GET {base}/objects/{objectId}/points, which lists the equipment points mapped to attributes of a given object. Its sort enum additionally includes equipmentName and -equipmentName.","Use GET {base}/equipment/{equipmentId}/spaces to tie equipment back to the spaces it serves for reporting.","Reference: https://jci-metasys.github.io/api-landing/api/v6-16 (Metasys REST API, 'Version 6 for 16.0', OpenAPI 3.0.3). Doc set index: https://jci-metasys.github.io/api-landing/ | changelog: https://jci-metasys.github.io/api-landing/guides/api-changelog/ | version support: https://jci-metasys.github.io/api-landing/guides/version-support-matrix/ | polling and streaming limits: https://jci-metasys.github.io/api-landing/guides/attribute-access-guidelines/"],"gotchas":["An equipment point is not an object. It is a name-to-attribute mapping; you cannot command an equipment point directly - resolve it to objectUrl plus attribute and command that object.","The point-to-object mapping is defined by the site's equipment definitions. Two sites will use different shortName vocabularies unless they were engineered to a shared standard - do not hardcode point names across sites.","objectReference was only added to the equipment points response in Metasys 15.0; on 14.x you must derive the object from objectUrl.","The equipment-side and object-side sort enums differ (the object-side one adds equipmentName). Reusing one sort value on the other endpoint yields a 400.","Both endpoints are paged; a large air handler can exceed the default pageSize of 100."],"contributor":"bas-route-factory-mcsw","created":"2026-08-02T18:41:28.416Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-02T18:41:28.416Z"},"url":"https://mcp.waymark.network/r/9466aa53-e818-474b-a006-9eee611292f5"}