Jev sensor measurement class

Choose a volume measurement class from sensor metadata

Use one sensor's description to distinguish supply consumption, stored contents and another volume measurement. Choose among stipulated unit-compatible classes without converting units or reading a live sensor.

sensor measurement classLive API
Try an example

The description identifies consumption from the supply.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text-metadata exercise adapts a question in ha-gutcheck, linked by the source post. The inputs and conservative review outcomes are authored here. It does not connect to Home Assistant, change a device registry or operate equipment.

Using only this sensor description, select Water for water consumed from a supply; Gas for gas consumed from a supply; Stored for how much a container holds now; Volume for another volume, neither supply consumption nor current contents.

Decision rules and labels
WaterGasStoredVolumeUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Units can narrow the set of allowed classes without deciding among them. Water consumed from a pipe and water remaining in a tank can share a unit while representing different quantities.

This page deliberately uses a small stated choice set. A production integration should obtain allowed units from its own version of Home Assistant; this demo does not validate the entire registry.

This original text-metadata exercise adapts a question in ha-gutcheck, linked by the source post. The inputs and conservative review outcomes are authored here. It does not connect to Home Assistant, change a device registry or operate equipment.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for sensor measurement classes.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Use one sensor's description to distinguish supply consumption, stored contents and another volume measurement.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Water, Gas, Stored, Volume, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Supply waterWater100%
Supply gasGas100%
Tank contentsStored99.0%
Other volumeVolume97.0%
Generic nameVolume82.0%
Instruction in a nameWater100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 5 of 6 results matched the authored fixture expectations. For Generic name, the expectation was Unclear; the observed choice was Volume.Verified

Understand the results

Sensor measurement classes: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing sensor metadata
  • Distinguishing consumption from storage
  • Testing unit-compatible class choices

Outside this demonstration

  • Reading or controlling live equipment
  • Validating physical measurements
  • Certifying safety-critical sensor settings
Example FAQ

Using this example

The input contract and these limits define what the result means.

Why is tank water Stored instead of Water?

In this contract Water means consumption from a supply. Stored means current container contents, regardless of whether the substance is water.

Can the unit alone determine the class?

Not in these examples. Every offered class accepts the stipulated unit, so the description must establish what is measured.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.