Monitor

What it is

Monitor shows what each battery last reported and keeps its history. A battery that has never reported is Registered. Once it reports it is Monitored, and it shows as quiet after 60 minutes without a reading.

You write alert rules. A rule watches your whole fleet and rings once when a battery crosses it, not on every reading while it stays across. It rings again if the battery recovers and crosses again.

A battery that stops reporting stops being charged. See pricing for the terms.

Who it is for

• Fleet operators who need to know when a pack degrades or goes silent.
• Owners who must act before a warranty ends.

How it works

1. Readings arrive. Batteries report through a gateway. The latest figures appear on screen and update live.
2. Choose a rule. There are three conditions: state of health below a figure, no update for a number of days, and warranty ending within a number of days.
3. Choose where it rings. Send the alert to a webhook, an email address or Slack. Every attempt is logged, including failures, so you can see whether you were told.

What it does not do yet

• The three conditions are all there are. There are no rules on voltage, temperature or current.
• A webhook or Slack address must be reachable on the public internet. Addresses inside private networks are refused.
• State of health in an alert is the figure the battery reports. The independent estimate is described under Proof and is not built.

Related services

• Ingest — The door that device data comes in through. Frames from your gateways arrive over MQTT and are kept as received before they are read.
• Proof — In development: an independent state-of-health estimate for a battery, with a stated uncertainty and the measurements behind it.
• Gateway — Register the devices that report for your batteries. Each gets its own credentials and can publish only on its own topics.