Verify a controller
Check your unit against its file
Most of this library comes from manuals. Nobody can say a number is right until someone moves that control on a real unit, and that takes one person, one unit and a few minutes.
- Pick your model and connect it.
- The page lights one control at a time. Move it.
- What matches is ticked. What differs shows both values and a fix.
- Download the updated JSON, or send it as an issue or a pull request.
Start
Simulator: click the lit control on the faceplate. Nothing from this run can mark a control as verified.
The file says
Heard –
| The file says | |
|---|---|
| Your unit sent | |
Result
| Control | Result | The file says | Your unit sent |
|---|
Check the lights
For a pull request: copy the JSON, open the file on GitHub, paste it over the old text and press Propose changes. GitHub makes the fork for you. For an issue, the link fills in the report; attach the JSON or paste it there.
What the marks mean
- Checked on hardware
- A person moved this control on a real unit and the message matched. The file says who, when, and on which firmware, OS and browser.
- From a source
- The number comes from a cited manual or tool. Nobody has checked it on a unit yet.
- Unverified
- Our best reading. A note says why.
A check through a virtual port or the simulator shows that this page works, not that a device does, so it can never mark a control as verified. The format is in the package README ↗.