Reference · built on requestConnectorBuilding management platforms

Carrier i-Vu

Alarm queries, the geographic and network tree, trend exports, and MQTT point data from Carrier i-Vu, with BACnet schedule writes.

Request accessPricing ↗

About

i-Vu is Carrier's web-based building automation system for HVAC, sold as i-Vu Pro (CIV-OPNPR) and related editions. Its v9.0 release added stateless REST APIs served by providers on the server, each under https://<server>/<provider>/api/<version>/, and self-documented with Swagger at /_alarm_serviceprovider/dist/index.html and /_system_serviceprovider/dist/index.html. Add-ons extend it with MQTT publishing, trend export, BACnet scheduling, OpenADR, LDAP, and weather.

Through Fibric, an operator counts and pages alarm records by location, state, category, and date, walks the system tree, and reads trend exports. Where the BACnet Scheduling Interface add-on is licensed it proposes schedule writes for events. You approve; the receipt keeps the prior schedule.

This is a reference listing. It documents what Fibric would read from Carrier i-Vu and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Alarm counts through POST /_alarm_serviceprovider/api/v1/alarm/count with a JSON filter such as location, toStates, fromDate, toDate, and includeCategories
  • Alarm records through the alarm query endpoint, paged with a limit and the returned next and previous filter records
  • Alarm categories, the alarm configuration of a single source, and counts by location, microblock, and state
  • The geographic and network tree through /_system_serviceprovider/api/v2/structure/tree/{treereferencename}/nodetree, nodedetails, and accessibleroots
  • Trend history exported by the Trend Export add-on as .CSV, daily, hourly, or on demand, up to two years back
  • Points published to an MQTT broker in Sparkplug B format with Project Haystack tags by the MQTT Connector add-on

Proposed actions

  • Target capability: propose a BACnet schedule write through the BACnet Scheduling Interface add-on, using BIBBs SCHED-A, SCHED-AVM-A, and SCHED-VM-A

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Trace a comfort complaint to its alarms

    A complaint names a room. The operator queries alarms for that location with byReturnToNormalPending true, reads the tree node details, and proposes the next step with the open alarms attached.

    With Comfort Complaint

  • Find equipment running outside its events

    Exported trends show runtime; the events calendar shows intent. The operator matches the two and proposes a schedule correction through the BACnet Scheduling Interface for the events that changed.

    With Schedule Leak

  • Time filter changes from real runtime

    Fan runtime from Trend Export accumulates per air handler. The operator proposes the filter change when runtime crosses your threshold and cites the count of alarms in that period.

    With Filter Change

Requirements

  • i-Vu v9.0 or later on the server; the alarm query API is licensed under /_alarm_serviceprovider/api/v1/*
  • An administrator to create API keys with a reference name, expiry time, and the exact endpoint paths and verbs each key may call
  • i-Vu Pro 6.5 or later with the latest cumulative update for the BACnet Scheduling Interface add-on (ADD-SCH-BACNET)
  • i-Vu Pro v8 with cumulative patch 5 or later plus an ADD-MQTT_CLIENT license for the MQTT Connector
  • The Trend Export add-on (ADD-TRNDEXP) on i-Vu Pro v6.5 or later for scheduled .CSV history
Authentication
HTTP Basic authentication with an operator account holding the Remote Data Access privilege, or an API key created on the API Keys page and sent as a cj-api-key header or as Basic credentials; authentication must use HTTPS unless the server allows SOAP applications over HTTP.

Limits

  • The alarm service has no API to configure alarm sources or manage alarm records; queries only
  • Alarm record queries are capped at 1000 records per page, and large queries can affect system performance
  • Only tree-retrieval calls of the system service provider are licensed; attaching equipment and editing source trees are not
  • Date filters are local time in ISO 8601 without a zone offset; a trailing comma in the JSON filter returns HTTP 500

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Carrier i-Vu ↗

Questions and answers

What does an API key allow?
Only the endpoints and verbs listed when it was created, for example GET on /_alarm_serviceprovider/api/v1/*. A key is not tied to an operator or privilege set, has an expiry date, and can carry an administrator flag that Carrier recommends avoiding. Send it as cj-api-key: reference:CJAPIKEY...
How do I page through alarm records?
Supply a limit with the query. When more records match, the payload carries a next filter record with nextPageId and the original criteria; post it back to continue. The system limit is 1000 records per query, and a limit of zero is treated as 1000.
Which BACnet revision does schedule writing need?
BACnet protocol revision 4 or later. The BACnet Scheduling Interface add-on supports the SCHED-A, SCHED-AVM-A, and SCHED-VM-A interoperability building blocks, so third-party event software writes schedules that i-Vu operators can still review and adjust in the i-Vu interface.
Ask about Carrier i-Vu

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Carrier i-Vu through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy