Edit Metasys object attributes safely with PATCH /objects/{objectId}

Documented steps

1. Authenticate and resolve the object id.
2. GET {base}/objects/{objectId}/attributes?attributeFilter=writableBasic to see which attributes are actually writable; use prioritizedBasic to identify attributes that are written through the priority array instead.
3. GET {base}/objects/{objectId}?includeSchema=true and read the schema for each attribute you intend to change, noting its metasysType.
4. PATCH {base}/objects/{objectId} with Content-Type: application/json and body {"item":{"name":"ZN-T","description":"Zone Temperature"}}. Only the 'item' wrapper is permitted at the top level.
5. For any attribute whose metasysType is struct, array or object, send the complete value. Partial updates to structured attributes are undefined behavior in this API.
6. Expect 200 on success. Verify with a follow-up GET of the object or the specific attribute.
7. Check effectivePermissions.canModify on the object before attempting the PATCH - a user without it gets 403 rather than a validation error.
8. For present-value writes on commandable points, use PUT /objects/{objectId}/commands/{commandId} instead of PATCH so the write lands at a defined BACnet priority.
9. 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/