Get CoCan Mirror

Shopping opens soon.

Scan with WeChat to buy CoCan Mirror
CoCan
中文

Every Watt Visible

Charging is something you should be able to watch.

Telemetry turns charging from a black box into data. See what is happening at a glance; dig deeper and port, protocol, power, temperature, and system events are all laid open to feed your own dashboards and automation.

Symptoms With Receipts

Only 45W on that port? The data tells you why.

A port stuck at 45W, a phone quietly slowing after a laptop plugs in, power shifting the moment you swap a cable — one number on a screen cannot explain these. You need port, protocol, power, temperature, and system events side by side, and Mirror folds all of them into telemetry.

Telemetry covers boot info, firmware versions, memory, temperature, network, MQTT, historical power, live allocation, port statistics, PD pcap, OTA progress, config sync, task results, and alerts. One dataset explains what is happening right now and gives you enough to trace it to root cause.

That transparency makes every FluxAI® scheduling decision traceable and third-party integration smoother. Build your own dashboard, write automation rules, keep a charging log — and when something goes wrong, tell whether it came from the device, the cable, the protocol, temperature, or strategy.

AI CoCan Mirror ingBar showing charging status
Visible State Status lives on the device, not only in the app.

ingBar keeps key state on the desk, while telemetry sends deeper data to dashboards, scripts, and automation.

Telemetry Streams

From boot to power curves

01

Device Status

Boot info, firmware versions, memory, temperature, network, MQTT, and uptime.

02

Power Data

Historical power, live allocation, port statistics, and PD pcap streams.

03

System Events

OTA progress, task results, config sync, alerts, and programmer status.

For The Curious

An interface for curiosity.

You can see whether the charger is online, which port is busiest, when temperature rises, and which device changes its power request. The device's local Prometheus and JSON metrics feed straight into Grafana, turning charging from guesswork into data you can chart over time.

Debug Surface

Turn charging symptoms into evidence.

01

PD pcap

PD packet streams help analyze negotiation, requests, and device capability.

02

Cable Intelligence

Cable VID/PID, EPR capability, current, voltage, and eMarker data can enter diagnostics.

03

Allocator State

Live allocation and historical power show how FluxAI® uses the 160W budget.

04

System Events

OTA, config sync, task execution, memory, and temperature alerts become traceable events.

State becomes events

Won't charge, wrong wattage — first turn it into data you can check.

Charging trouble is hard to judge by eye. A device short of expected power could be the cable, the protocol, the battery temperature, the system load, the port priority — or the whole-unit budget. Mirror breaks those possibilities into data: device state, port state, power history, live allocation, PD pcap, temperature, and alerts, laid out one by one.

Boot info and device stats show firmware version, uptime, memory, and network state; power history traces a device moving from a high-power stage into a low one; live allocation says where the 160W budget flows right now; port statistics show which port is busiest. A vague 'feels a bit slow' becomes a string of concrete numbers.

PD pcap keeps the evidence at the protocol layer. Negotiation, requests, and device-capability data can all be pulled, with Source_Capabilities, Request, and Accept reconstructed clearly. The murky symptoms — 'won't charge,' 'wrong wattage,' 'a cable swap made it faster' — become evidence you can put on the table.

The same telemetry explains the present, too. FluxAI® and the screen read it to tell you whether a device is near full, a cable is limiting, a thermal strategy kicked in, or another device took the budget. It supports local Prometheus and JSON output, so data lands on your own machine, there to check whenever you want.

Into your own workflow

Observable charging can plug into your own dashboard.

Read the screen, pipe to a dashboard, or trigger automation — telemetry serves all three from the same set of facts without clashing.

A few concrete cases: log daily charging curves for a laptop and phone to see whether a cable holds high power steadily; switch to a thermal mode when the temperature climbs; dim the display at night; favor the laptop port on weekday mornings. None of these rest on guesswork — all build on data the device actually reports.

Scheduled tasks and telemetry results also close a loop: the device runs commands on a schedule and reports execution state back through task results. Config sync keeps multi-surface control from clashing — port config and charging strategy can be uploaded, applied, retried, and debounced, so settings changed from several places never overwrite one another.

A transparent product pays off in concrete ways: no studying protocols every day, data to check when something's off, interfaces to connect when you want to extend, and real state behind every FluxAI® decision. What you can see, you can manage.

Symptoms made analyzable

The same laptop sits at 60W today? The data finds the reason.

The symptoms users hit are usually specific: the same laptop sits at 60W today and speeds up with a different cable; a phone drops power after a laptop plugs in; the temperature runs higher at night. Without telemetry, these can only be guessed from experience. With it, each one traces to a cause.

Mirror records the key states separately. Port state explains the connection and protocol, power history the course of change, live allocation where the budget flows, thermal alerts the protection strategy, config reports the current mode and port settings. Whichever link went wrong becomes clear by comparison.

PD pcap leaves evidence at the protocol layer. It reconstructs negotiation steps like Source_Capabilities, Request, and Accept, and shows whether the device actually asked for a given tier. For real troubleshooting, this beats a single wattage number on screen.

FluxAI®, apps, scripts, and dashboards all share this telemetry. Explanation, logging, and automation draw on the same set of facts, so the experience stays consistent — what you see on screen, what a script reads, and what an agent decides from are always one truth.

A curve beats a single number

Tie an alert to the scene around it, and it can point to the next move.

A single live wattage number on the screen only describes this instant. Pull up a week of curves and you can see the whole arc — a device dropping into thermal throttle and climbing back — which device always sags at a certain stage, which port carries the main load long-term, which cable wavers at high power. All of it needs a time axis to judge.

Alerts are the same; one popping up alone tells you nothing. Mirror's telemetry binds it to the scene: at the moment of a thermal warning, which ports were working, how power was split, whether a device had just been plugged in — recorded as a structured event that can enter history, dashboards, FluxAI®'s explanations, and automation rules.

With context, an alert becomes an action: wait for cooldown, change mode, check a cable, inspect port occupancy, or replay the task just run.

Tester sign-up

Leave a message