Security Solutions - Midches.com

MQTT Explained: How Bosch and IQSIGHT Cameras Share Intelligent Events With Other Systems | Pro Services Tech Tips by MidChes - #0001

Written by Matt Golueke | Nov 20, 2026, 6:05:22 PM

MQTT Explained: How Bosch and IQSIGHT Cameras Share Intelligent Events With Other Systems

A security camera can do far more than capture video. Modern IP cameras can detect movement, identify objects, count people, recognize activity, and generate alerts based on what they see.

But what happens when that information needs to reach another system?

Perhaps a camera detects someone entering a restricted area, and a security team wants that event delivered to another application. Maybe a facility wants to use people-counting information to monitor occupancy, or a security operations center needs analytics events from multiple cameras without constantly requesting information from each one.

This is where MQTT becomes valuable.

In the first installment of Chesapeake & Midlantic Marketing's Pro Services Tech Tips, David Brent introduces MQTT as "Three Easy Pieces."

He explains the basic communication process and demonstrates how an IQSIGHT camera, formerly part of Bosch Video Systems, can send events through an MQTT broker to another application.

The technology is relatively simple to understand, but its potential applications extend well beyond traditional video surveillance.

 

 

What Is MQTT, and Why Does It Matter?

MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol that allows connected devices and applications to exchange information using a publish-and-subscribe communication model.

In plain English, MQTT allows one device to announce that something has happened while other systems receive that information automatically.

It was developed for machine-to-machine (M2M) communication and is widely used in the Internet of Things (IoT), where sensors, equipment, and software applications exchange information across IP networks.

Unlike communication methods that require a receiving application to continually ask a device for updates, MQTT uses a messaging broker to distribute information to interested subscribers.

This makes it particularly useful when many devices need to exchange relatively small amounts of data efficiently.

For physical security, the benefit is significant. A camera can analyze activity at the edge, generate an event, and make that event available to other applications without requiring every receiving application to establish its own event-monitoring connection to the camera.

Importantly, MQTT carries messages and metadata, not the camera's live video stream. Video management systems (VMS) still handle video viewing, recording, playback, and related functions. MQTT provides another method for communicating the information generated by intelligent cameras.

 

Understanding MQTT: Three Easy Pieces

David simplifies MQTT into three essential components: the publisher, the broker, and the subscriber.

1. The Publisher: Where Information Originates

The publisher is the device or application that generates and sends a message.

In a physical security application, an IQSIGHT camera can serve as the publisher.

For example, the camera's Intelligent Video Analytics (IVA) may detect someone crossing a virtual line. Once the configured analytics rule is triggered, the camera can publish an MQTT event describing what happened.

The camera does not need to know which applications will ultimately use the information. It simply publishes the event to the designated broker.

2. The Broker: The Message Distribution Center

The broker receives messages from publishers and distributes them to applications that have subscribed to the corresponding topics.

Think of the broker as a sorting and delivery service.

A camera publishes an event, and the broker determines which connected applications should receive it based on their subscriptions.

One publisher can serve multiple subscribers without maintaining separate application-specific delivery connections.

In David's demonstration, Eclipse Mosquitto serves as the MQTT broker. Mosquitto is an open-source broker that supports standard MQTT messaging and can operate on Windows, Linux, and other platforms.

3. The Subscriber: The System That Receives the Information

A subscriber is an application or device that listens for MQTT messages matching its subscriptions.

Subscribers might include monitoring software, building automation applications, integration platforms, or custom security applications.

In the demonstration, David uses MQTT Explorer, a graphical application that connects to the broker and displays incoming topics and messages.

MQTT Explorer makes it possible to see what the camera is publishing, examine the message structure, and confirm that communication is working.

Together, these components form a straightforward communication path:

IQSIGHT camera (publisher) → Mosquitto (broker) → MQTT Explorer (subscriber)

Once this basic relationship is understood, the next step is identifying the information that a camera can publish.

 

What Information Can Bosch and IQSIGHT Cameras Send Through MQTT?

Many Bosch and IQSIGHT cameras support intelligent analytics that identify activity directly at the camera, often referred to as edge analytics.

Instead of transmitting video to another computer for every detection decision, the camera performs supported analytics locally and generates events that other systems can consume.

Depending on the camera model, firmware, installed analytics capabilities, and configuration, MQTT messages may include several categories of information.

Motion and Intrusion Detection

A camera can report motion alarms or events triggered by configured analytics rules.

These can include line crossing, entering or leaving a defined area, and loitering.

For example, a camera monitoring a secured loading dock could publish an event when someone crosses a virtual boundary after hours.

A subscribed application could then use that event to initiate a notification or another configured workflow.

Object Detection and Counting

Intelligent Video Analytics can identify certain types of object activity, including objects that remain idle or have been removed from a monitored area.

Supported counting rules can also generate information related to line crossings and occupancy.

These capabilities may be useful for understanding how people and vehicles move through a facility.

For example, a facility-management application could consume people-counting events to help maintain an occupancy dashboard.

Camera Tampering and Image Conditions

A camera can also report conditions that may interfere with its ability to monitor an area.

Depending on the implementation, these can include significant changes in the camera's field of view, image obstruction, insufficient illumination, or excessive brightness.

These events can provide operational awareness beyond traditional intrusion alarms.

Physical Inputs and Outputs

Cameras equipped with supported digital inputs or relay outputs can publish changes in those states.

This creates additional integration opportunities involving connected physical devices, provided the relevant hardware and event interfaces are supported.

Recording Status

The documented MQTT implementation can publish a recording-start event. However, the referenced Bosch implementation does not generate corresponding messages when recording stops or when recording errors occur.

That distinction matters. MQTT recording-start notifications should not be mistaken for comprehensive recording-system health monitoring.

The key takeaway is that MQTT makes selected camera-generated events available to other systems. The information actually published depends on the camera's capabilities, firmware, analytics configuration, and supported MQTT event topics.

 

How ONVIF Profile M Supports Camera Integration

MQTT becomes especially interesting in physical security when combined with ONVIF Profile M.

ONVIF develops interoperability specifications for IP-based physical security products. Profile M addresses analytics metadata and event handling, including interfaces for communicating events through MQTT when the relevant functionality is supported.

This helps connect intelligent cameras with applications that need to consume analytics information.

Rather than relying exclusively on proprietary integrations, developers can work with standardized event structures.

Bosch implemented MQTT support associated with ONVIF Profile M across supported camera platforms, and that functionality continues to be relevant to IQSIGHT products.

The documented implementations can provide JSON-formatted event information that applications can interpret.

JSON, or JavaScript Object Notation, is simply a structured way to organize information using recognizable fields and values.

An MQTT message may identify when an event occurred, which camera or video source generated it, and what triggered the event.

For advanced integrations, newer firmware also supports additional object properties for selected IVA Pro events. Depending on the analytics package and configuration, these may include object classification, speed, location information, or snapshots.

These extended capabilities are not universal across all cameras. Integrators should verify the exact model, firmware version, IVA package, and supported MQTT functions before designing an integration around them.

 

Setting Up MQTT With a Bosch or IQSIGHT Camera

With the basic concepts established, David moves into a practical lab demonstration.

The objective is to configure an IQSIGHT camera to publish events through Mosquitto and verify receipt using MQTT Explorer.

The example uses three components:

  • Publisher: A compatible IQSIGHT camera.
  • Broker: Eclipse Mosquitto, installed on a computer.
  • Subscriber: MQTT Explorer, connected to the Mosquitto broker.

The following procedure summarizes the demonstration and adds important implementation considerations from the manufacturer's documentation.

Step 1: Confirm Camera Compatibility

Before beginning, verify that the selected camera and firmware support MQTT event publishing.

The manufacturer's documentation identifies MQTT support for specific Bosch camera platforms and firmware releases. A current, compatible version of Configuration Manager is also required for the demonstrated configuration workflow.

The official configuration guidance identifies Configuration Manager 7.50 or newer as a baseline, although particular camera platforms and firmware releases may require later versions.

The camera should already be operational on the network, accessible through Configuration Manager, and configured with an analytics event that can be triggered during testing.

Step 2: Install and Configure Mosquitto

Download and install Eclipse Mosquitto on the computer that will operate as the MQTT broker.

In David's Windows demonstration, Mosquitto is installed under:

C:\Program Files\Mosquitto

Open the mosquitto.conf configuration file with a text editor.

For the isolated lab demonstration, David configures Mosquitto to accept connections on TCP port 1883 by enabling a listener:

listener 1883

He also enables anonymous connections:

allow_anonymous true

After saving the configuration, restart the Mosquitto service to apply the changes.

Important security distinction: This configuration is appropriate only for an isolated, controlled demonstration environment. Anonymous connections allow clients to connect without authentication and should not be used as the default configuration for an operational security network.

Production systems should use appropriate authentication, access restrictions, and encrypted connections wherever supported.

Step 3: Connect MQTT Explorer to the Broker

Next, install and launch MQTT Explorer.

MQTT Explorer provides a visual method for examining MQTT communication without developing a custom application.

In the demonstration, David creates a connection using these values:

Connection name: TestLab

Protocol: mqtt://

Host: The IP address of the computer running Mosquitto

Port: 1883

He also uses BoschCam1 as the topic identifier in his lab configuration.

MQTT topics organize messages into a hierarchy. For example, a camera may publish an event under a topic beginning with BoschCam1/onvif-ej/.

To subscribe to all topics beneath that camera's prefix, the manufacturer's documentation provides this subscription filter:

BoschCam1/#

The # wildcard matches the remaining levels in the topic hierarchy.

Once the connection is configured, select Connect.

If successful, MQTT Explorer will establish communication with Mosquitto. At this point, the subscriber and broker are connected, but the camera has not necessarily begun publishing.

If the connection fails, verify the broker's service status, IP address, listener configuration, and authentication settings. In David's example, an inbound Windows Firewall rule permitting the required traffic on port 1883 may also be necessary.

Any firewall exception should be restricted to trusted network sources rather than exposing the MQTT broker broadly.

Step 4: Configure MQTT on the IQSIGHT Camera

The next step connects the camera to the broker.

Open Bosch/IQSIGHT Configuration Manager, select the camera, and navigate to:

Network > MQTT

Select Add broker.

David's lab uses the following configuration:

Protocol: mqtt://

Address: The IP address of the Mosquitto server, with port 1883

Topic prefix: BoschCam1

Save the configuration.

The topic prefix should be unique for each camera so that applications can distinguish one camera's messages from another's.

In a larger deployment, consistent identifiers are particularly helpful. A naming convention could incorporate the building, camera location, or device identifier.

The camera now has the information it needs to connect to the MQTT broker and publish its supported events.

Step 5: Trigger an Event and Verify Communication

With Mosquitto running, MQTT Explorer connected, and the camera configured, generate an analytics event.

For example, a configured intrusion rule may detect movement across a virtual line.

When the event is triggered, the camera publishes the corresponding MQTT message. Mosquitto receives it and distributes it to subscribed applications, including MQTT Explorer.

David's demonstration shows the camera's analytics event alongside the MQTT Explorer interface, illustrating how a detected event appears as a published message.

This verifies that the camera is generating an event, the broker is receiving the publication, and the subscriber can access the information.

It is also an opportunity to examine the event structure before attempting to integrate the data with another application.

 

Understanding MQTT Topics and Event Data

For more technical integrations, understanding the structure of MQTT messages is essential.

A topic acts as the routing identifier for a published message.

For example, the manufacturer's documentation identifies a motion-alarm topic with this structure:

BoschCam1/onvif-ej/VideoSource/MotionAlarm/&1

Here, BoschCam1 identifies the camera using its configured prefix, while the remaining elements identify the event category and source.

The associated JSON message can contain fields such as UtcTime, Source, and Data.

These fields help receiving applications determine when an event occurred, where it originated, and what state or information the event represents.

A software developer can use that information to build an automated response, populate an operational dashboard, or correlate camera events with information from another system.

MQTT also supports different Quality of Service (QoS) levels, which determine the protocol's delivery guarantees. Depending on the application, messages can be delivered at most once, at least once, or exactly once under the corresponding QoS mechanisms.

The appropriate choice depends on the broker, camera implementation, subscriber capabilities, and consequences of missed or duplicate messages.

For instance, an application processing repeated events should be designed to recognize duplicates when using delivery mechanisms that permit them.

MQTT is a transport mechanism, not a complete alarm-management system. Applications still need suitable logic for interpreting messages, validating events, maintaining operational records, and determining what actions should occur.

 

Where MQTT Can Add Value to Physical Security

The immediate benefit of MQTT is improved communication between systems, but the broader value comes from what organizations can accomplish with the information.

Perimeter security: A camera detects someone crossing a restricted boundary and publishes an event that a compatible monitoring or integration application can consume.

Healthcare and large facilities: Camera-generated counting or occupancy information can be made available to other authorized operational applications.

Transportation and logistics: Vehicle detection, line-crossing events, or supported traffic analytics can supply information for dashboards and business processes.

Security operations centers: Event data from multiple compatible cameras can be gathered through an MQTT broker and delivered to applications designed to correlate, prioritize, or visualize that information.

Building automation: A supported camera event can become an input to an integration platform that coordinates an appropriate action elsewhere in the building.

These are potential application designs, not automatic functions of MQTT itself. The receiving software must be capable of consuming the event format and performing the desired action.

 

Security Considerations for Production MQTT Deployments

Because MQTT can carry security-related events, protecting the messaging infrastructure is as important as establishing connectivity.

David's demonstration intentionally keeps the setup simple. The use of unencrypted MQTT on port 1883, together with anonymous access, makes the initial lab configuration straightforward.

Operational deployments require a more controlled approach.

MQTT supports encrypted communication using TLS, commonly associated with port 8883. Supported Bosch/IQSIGHT camera implementations can use secure MQTT connections, subject to their firmware and configuration capabilities.

Production designs should evaluate authenticated broker access, topic-level permissions, network segmentation, firewall restrictions, certificate management, and appropriate monitoring of broker availability.

It is equally important to determine what happens when the broker or network connection is interrupted.

A successful lab demonstration confirms event delivery under the tested conditions. It does not, by itself, establish redundancy, guaranteed end-to-end processing, or suitability for life-safety or mission-critical operations.

Those requirements belong in the overall system design.

 

The Bigger Picture: Turning Camera Intelligence Into Useful Information

As IP cameras become more intelligent, the information they produce becomes increasingly valuable outside the video management system.

Traditional video surveillance focuses heavily on capturing, viewing, and recording what happens.

Intelligent analytics adds another dimension by identifying specific activities and converting them into structured information.

MQTT provides a practical way to move selected information from its source to applications capable of using it.

And, as David demonstrates, the fundamentals do not require an unusually complex infrastructure. A compatible camera, an MQTT broker, and a subscribing application are enough to begin exploring the possibilities.

The real work begins when an organization identifies which events matter, where those messages should go, and how receiving systems should respond.

That is where MQTT can become an important component of a larger, more connected physical security environment.

 

Need a hand?

For assistance with camera configuration, firmware compatibility, system integration, or implementation planning, contact us at support@midches.com.

 

Frequently Asked Questions About MQTT and Security Cameras

What is MQTT used for in security camera systems?

MQTT allows compatible cameras to publish events and analytics metadata to other applications. It can support intrusion alerts, counting information, operational dashboards, and integrations with other systems without transmitting the camera's live video through MQTT.

Can Bosch and IQSIGHT cameras communicate using MQTT?

Yes. Supported Bosch and IQSIGHT camera models can publish MQTT events using implementations associated with ONVIF Profile M. Compatibility and available event types depend on the specific model, firmware, and configuration.

Does MQTT replace a video management system?

No. MQTT transports messages and event data. A VMS provides functions such as live video viewing, recording, playback, and video management. MQTT can complement a VMS by making selected camera events available to other systems.

What is an MQTT broker?

An MQTT broker is software that receives messages from publishers and distributes them to subscribers based on topics. Eclipse Mosquitto is one example of an MQTT broker used in security-camera integration testing.

What is MQTT Explorer used for?

MQTT Explorer is a graphical application for connecting to an MQTT broker, examining available topics, and viewing published messages. It is particularly useful for verifying connections and troubleshooting event delivery.

What is ONVIF Profile M?

ONVIF Profile M defines interfaces for analytics metadata and events in IP-based systems. It supports interoperability between compatible devices and applications, including event communication over MQTT when that feature is implemented.

Is MQTT secure enough for enterprise security applications?

MQTT can be used securely when supported encryption, authentication, permissions, and network protections are properly implemented. Unauthenticated, unencrypted lab configurations should not be used for production security systems.

Does every camera event automatically appear in MQTT Explorer?

No. The camera must support MQTT, be connected to the broker, and be configured to generate and publish the relevant event. MQTT Explorer must also be connected to the correct broker and subscribed to the appropriate topics.

 

Technical References and Additional Watching & Reading

The implementation concepts described here are supported by the following resources:

 

Contact us for system design assistance >>