COV (Change of Value) - Knowledge Base

BACnet Change of Value subscription overview covering COV vs polling, increment configuration, and interoperability.

Categories:

What COV Is

Change of Value (COV) is a BACnet subscription service. Instead of polling a device at fixed intervals, a subscribing client asks the server device to report a property value only when it changes by more than a configured increment.

COV reduces network traffic and provides faster response to value changes compared to periodic polling.

COV vs Polling

AspectCOVPolling (ReadProperty)
Network trafficOnly on changeEvery poll interval
LatencyNear real-timeUp to one poll interval
Device supportOptional — not all devices implement COVUniversal
ConfigurationRequires subscription + increment tuningSimple — just set interval

Key Concepts

  • COV Increment — the minimum change in value that triggers a notification. Set too low = excessive traffic. Set too high = missed changes.
  • Subscription lifetime — COV subscriptions expire and must be renewed. If the subscriber doesn’t renew, notifications stop silently.
  • Confirmed vs Unconfirmed — confirmed COV requires acknowledgment from the subscriber; unconfirmed does not.

[!NOTE] COV support varies widely between devices. Always verify COV capability in the device’s PICS (Protocol Implementation Conformance Statement) before designing a COV-based integration.

Common Issues

  • Device doesn’t support COV → falls back to polling
  • Subscription expires without renewal → values stop updating silently
  • COV increment mismatch → either too many notifications or missed changes

Need more help?

If this page does not resolve the issue, contact Chipkin support with the product model, protocol details, and any diagnostics you have already captured.

Open Chipkin Support