Project information

• Category: IoT
• Client: INSTAR Deutschland GmbH (Waletech) Shenzhen, China
• Project date: 01 March, 2019
• Project URL: forum.instar.com

The problem:INSTAR cameras had no native smart-home interface. I designed and joined the embedded system team to implement two complementary protocols directly in the firmware:

What I did: Designed and implemented two complementary protocols directly in the firmware:

• HTTP/S webhooks – every major automation platform that exposes a webhook endpoint (Home Assistant, openHAB, ioBroker, custom Node-RED flows) can now receive camera events as GET/POST pulses. Extended with URL-query parameters so the payload carries structured data: detected object classes, confidence scores, and AI-module annotations.
• MQTT broker (Mosquitto 2) – embedded directly in the camera firmware, giving every subscribed client (Home Assistant, openHAB, Node-RED, custom scripts) a push-model feed of state changes. Includes MQTT Autodiscovery so a camera appears in Home Assistant and OpenHab the moment it joins the network — no manual YAML. Camera-to-camera event chaining is possible because each unit acts as both publisher and broker.

To my knowledge, INSTAR remains the only surveillance-camera manufacturer that exposes its full control interface over MQTT. This single decision is what made the product drop-in compatible with the entire open-source smart-home ecosystem — and laid the groundwork for the MCP server that turned those same MQTT topics into AI-agent tools.