Pair your load with the right power.

How do I send you a measurement I took myself?

By filling in the fields below and delivering the block they produce. There is no “submit” button here, because there is nothing on the other end of one: WattPair is a static site with no server, and a form that posted into the void would be the worst possible answer to a reader who took the trouble to measure something.

Why a block of text instead of a form

The block is the submission. It carries its own format version, so a log written today is still readable when it is reviewed; it survives a clipboard, an issue thread and a copy-paste out of one; and it is diffable line by line against the next log of the same pairing, which is the whole point of the rule below. Nothing is uploaded, measured or remembered by this page — it formats what you typed and hands it back to you.

What happens to it

  1. It goes into a review pool, not onto a page. Nothing you send is published by being sent. PRD rules for this site put reader data behind review, and that is not a formality: a wrong figure with a source stamp on it is more damaging than no figure.
  2. It is checked against what is already published. A log that contradicts the manufacturer’s own specification is interesting, not disqualifying — but it is read against it, and the reasoning is written down.
  3. A pairing is labelled user-verified only once 3 independent logs of that same pairing agree. One log is one data point. Two that agree could be one person twice. Three is where this site is willing to put a number in front of a stranger.
  4. It stays labelled as a reader log. Source tier travels with the figure for as long as the figure exists, with the date it was verified. A reader log never becomes a specification.

The user tier holds 0 figures today — this channel has just opened, and the site claims no reader data until some arrives.

Build your block

Fill in what you actually observed. Leave anything you did not measure empty — a blank is a fact about the run, and a guess is not. Required to review a log: which power station, which load, how many hours it ran, how the run ended, the date you measured it.

All 29 records in the library — US and EU versions are separate machines.

All 30 load profiles. Pick the closest one and describe yours in the notes.

Leave empty if you had no meter. The log is still useful.

From a full charge, in hours. 90 minutes is 1.5.

A number of hours means nothing without this. “Still running” is a perfectly good answer — it makes the figure a floor rather than a total.

Battery capacity moves with temperature; a runtime with no temperature cannot be compared.

Every figure on this site carries the date it was verified. Yours will too.

“The station’s own display” is an answer, and a useful one — it says which instrument the number came from.

0 / 600  · plain text, and it travels inside the block.

Your block, and how to send it

SUBMISSION BLOCK Format wattpair/user-log/1.0 — copy all of it, keys included. 

# WattPair user log — paste the whole block, keys and all.
schema: wattpair/user-log/1.0
station:
appliance:
running_watts:
runtime_hours:
ended_because:
ambient_c:
ambient_f:
meter:
measured_on:
notes: |
Open a prefilled GitHub issue →

The issue route needs a free GitHub account, and the issue is public — post nothing you would not put on a forum. It opens in a new tab at lhlhome/wattpair, this site’s own repository. No account, and no wish for one? Keep the block: it carries its format version, so it stays valid until the email route opens.

The email route

hello@wattpair.com is the address, and it is not accepting mail yet — it is being set up alongside the site. It is printed as text rather than as a link on purpose: a clickable address that bounces would waste a measurement someone spent an evening taking. Until it opens, the two routes above are the working ones, and a block written today stays valid because it carries its own format version.

A filled-in example

This is what a complete submission looks like. It is an example, not a record — no figure in it is stored anywhere on this site, and nothing on any page is based on it.

EXAMPLE — NOT A STORED RECORD 

# WattPair user log — paste the whole block, keys and all.
schema: wattpair/user-log/1.0
station: bluetti-elite-100-v2--us
appliance: refrigerator-full-size
running_watts: 92
runtime_hours: 9.5
ended_because: battery_empty
ambient_c: 22
ambient_f:
meter: "Kill A Watt P4400 at the wall"
measured_on: 2026-07-28
notes: |
  Fridge alone on the outlet, nothing else plugged in.
  Compressor cycled about 15 minutes on, 30 minutes off.
  Station started at 100% and shut off on its own.

Read as: a full-size fridge on an Elite 100 V2 drew 92 W while its compressor ran, and the station went from full to shutdown in 9.5 hours at 22 °C, measured with a plug-in meter on 2026-07-28. Every one of those clauses is a field, and the review depends on all of them.

What a reviewer does with it

1 · Read the block Field names are checked against the format version in the block itself, so a log written against an older format is read against the rules it was written under, not today’s.
2 · Sanity-check against the engine The same computation the site publishes is run for that pairing. A log inside the expected band corroborates it; a log far outside is not thrown away — it is the one that gets read hardest, because either the log or the published figure is wrong and both matter.
3 · Hold it in the pool The submission is stored with its source tier set to user, its status pending, and its test conditions written from the temperature, the instrument and how the run ended. Pending means it is not on any page.
4 · Promote only at 3 agreeing logs Same pairing, independent submitters, figures that agree within the tolerance the review manual sets out. Then, and only then, the pairing carries a user-verified figure — still labelled as a reader log, still dated.
What gets a log rejected A pairing with no station or no load; a runtime with no termination condition; figures copied from a retail listing or a review video rather than measured; and anything a submitter cannot say how they observed. A rejection is recorded with its reason.

How your figure would be labelled

Official spec A number the manufacturer publishes, with the document it came from and the date it was checked. It is not evidence that the machine behaves that way in your kitchen.
Lab measurement A figure measured on a bench under stated conditions. There is no test bench behind this site, so the library holds none; the tier exists in the data model and is empty, and nothing here claims one before there is one.
User log What this page collects. It is the only tier this project can currently grow, it is labelled as reader data wherever it appears, and it never quietly becomes one of the other two.

Questions

Does my measurement appear on the site straight away?

No. Every reader log goes into a review pool first. A pairing is only shown as user-verified once 3 independent logs of that same pairing agree, and it stays labelled as a reader log after that.

Do I need a GitHub account to send a log?

Filing the prefilled issue needs a free GitHub account. If you do not have one and do not want one, copy the block and keep it — the email route opens when the mailbox does, and the block stays valid because it carries its own format version.

What if I did not measure the watts?

Send it anyway. A timed run with no wattmeter is still evidence about runtime; it is reviewed as runtime evidence only. What a log cannot be reviewed without is the pairing, the hours, how the run ended, and the date.

Will my log replace the manufacturer specification?

No. Official spec, lab measurement and user log are three separate source tiers, and a reader log is published as a reader log with its date. It never overwrites a published specification; where the two disagree, the page says so.

What do you do with my personal details?

This page collects none. It runs entirely in your browser, sends nothing anywhere, and stores nothing between visits. If you file a GitHub issue, GitHub knows who filed it and the issue is public — that is GitHub’s account, not this site’s.

My exact model is not in the list.

The library covers 29 station records — a US and an EU version of one machine are two of them — and 30 load profiles. If yours is not among them, pick the closest load, leave the station unselected, and say what you actually used in the notes. A log for a machine the library does not carry yet is how that changes.