Open Interface, Open Firmware

Your charger, wired into your own system.

Mirror publishes MQTT v5 topics, protobuf payloads, telemetry fields, and datasheets, and its firmware is open source. The device serves Prometheus and JSON metrics locally alongside a cloud MCP server — use the official cloud, your own broker, Grafana, scripts, or AI tools.

Read the MQTT reference

Everything Published

Datasheets, topics, payloads — even the firmware is on the table.

Many chargers keep their internals a black box. Mirror does the opposite: datasheets are published, MQTT v5 topics, protobuf payloads, and telemetry fields read directly, and the firmware is open-sourced at go.ifanr.com/ionbridge-open-source. You can send commands by topic, subscribe to port power and temperature, and wire the whole charger into your own system.

MQTT topics separate end-user request, admin request, end-user response, admin response, and telemetry, so clients can see message direction and permission domain at a glance. Command payloads use public CommandRequest / AdminCommandRequest schemas, with explicit fields for power, ports, display, Wi-Fi, OTA, telemetry subscription, resources, licenses, and scheduled tasks.

The interface covers what actually gets used: device state, Wi-Fi, power strategy, port priority, PD status, port power, compatibility settings, custom PDO, cable compensation, display, OTA, resource management, licenses, scheduled tasks, and diagnostics.

The official cloud works out of the box; for full control, point MQTT at your own broker and Home Assistant, Node-RED, scripts, a local database, or a personal dashboard can all drive it. Local Prometheus / JSON and cloud MCP read the same device facts, so dashboards, scripts, and AI tools do not diverge.

Desk System

Open interfaces, open to your own desk.

MQTT, telemetry, and local dashboards wire the charger into the computers, scripts, and automations you already use every day.

Cloud Or Local

Official cloud and local automation both work.

Use the official cloud, or connect MQTT to your own broker and send power, temperature, and port state into scripts, dashboards, or Home Assistant; for local recording, Prometheus and JSON metrics feed Grafana directly.

MQTT

MQTT Topics

device/<psn>/enduser/request/<cmd>
device/<psn>/admin/request/<cmd>
device/<psn>/enduser/response/<cmd>
device/<psn>/admin/response/<cmd>
device/<psn>/telemetry/<cmd>

Command Domains

Interface coverage

Device + Wi-Fi

Association, reboot, reset, serial, uptime, Wi-Fi scan, status, and records.

Power + Ports

Strategy, priority, PD status, port state, compatibility, PDO, and cable compensation.

Display + OTA

Intensity, mode, rotation, display state, app OTA, SW3566/FPGA resource upgrades.

Advanced + Tasks

Resource management, machine config, system time, license, scheduled tasks, and diagnostics.

Integration Hooks

Published interfaces for third-party integrations

Typed Protobuf

CommandRequest / AdminCommandRequest use oneof fields for service parameters, so commands and responses integrate by field.

Structured Telemetry

Status, port history, allocation, PD pcap, config reports, and task results can be subscribed to continuously.

Custom Broker

MQTT can point to the user’s own broker, so home automation and local scripts can connect directly.

Public Datasheets

Interfaces, capabilities, and key product specs are published for verification and development.

Open By Design

Published datasheets, MQTT topics, and open firmware are part of the product.

Mirror's open interfaces come from a straightforward call: you should be able to see what your charger is doing and wire it into your own systems. Published datasheets, MQTT topics, protobuf payloads, telemetry fields, and open-source firmware form an interface contract that can be checked against the code.

Get CoCan Mirror