Remove one Axis Data Hub subscription without stopping the others

Bottom line: Retire a Data Hub subscription by its recorded identifier. Keep the remaining subscriptions explicit so removing one consumer’s data selection does not become an unexplained shutdown of the entire shared connection.

Source fact: documented behavior

Axis’s Device Data Hub WebSocket API supports several subscriptions in one session, with separate filters and a distinct subscriptionId for each.

The documented unsubscribe operation removes the subscription named by its ID; the other subscriptions on that connection continue operating.

A topicSample notification identifies its subscription and topic and includes sample data and a timestamp.

What the source does not establish

Do not infer missed-sample recovery or application-level continuity from this removal behavior. Keep a session-close or reconnect procedure separate from removing one subscription. Confirm the device’s interface support and the actual client’s subscription handling before sharing a connection between operational consumers.

Applicability questions

• Which component owns each subscription identifier?
• Which topic and filter selection belongs to the subscription being retired?
• Which other subscriptions must remain on the same session?
• What permitted sample will demonstrate each retained consumer’s required data path?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.

1. List the intended consumers and assign each an identifiable subscription record in the integration. Preserve the ID returned or accepted by the documented workflow with its filter and owning component. Avoid choosing a removal target from a topic name alone when the design permits several filtered subscriptions. Record which consumers are deliberately unaffected by the requested retirement.
2. Prepare a proposed pilot with two harmless supported topic selections and distinct subscription IDs. Label the selections as fixtures rather than actual site requirements. Establish each subscription through the supported interface and capture permitted sample observations before removal. Keep the connection and each subscription’s state as separate entries in the client’s diagnostic record.
3. Remove only the selected ID and retain the operation outcome. Check the remaining subscription with an appropriate approved input and reconcile its sample identifier with the registry. If the client closes the session or loses another required subscription, treat that as an integration result to investigate. Restore the approved arrangement before expanding the change to operational consumers.

Verification and evidence

Retain the session identity, sanitized subscription definitions, selected removal ID, response and before-and-after sample observations. Have another reviewer match each observed sample to its intended subscription. Exclude credentials and unnecessary payload content from shared diagnostic records.

For the proposed exercise, include a client-side selection review in which the wrong ID belongs to the consumer that must remain. Require the operator to reject that removal before sending it. Record actual results after execution; this article does not report a completed subscription test or guarantee that an application received every sample.

Official references

• Device Data Hub WebSocket API — Axis Communications; official VAPIX documentation.

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.