Jev sensor diagnostic role

Distinguish device diagnostics from household measurements

Read the sensor's described purpose to separate device or connection diagnostics from household and consumable measurements. Preserve unclear roles instead of using the unit or name alone.

sensor diagnostic roleLive API
Try an example

The reading concerns the bridge’s connection.

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.

Classify the described sensor: Diagnostic for the device or connection itself, such as network identity, signal strength, firmware, memory or uptime; Primary for the home or a monitored consumable, such as room temperature, energy use or filter life.

Decision rules and labels
DiagnosticPrimaryUnclear
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

A diagnostic reading explains the device or its connection. A primary reading explains a household condition or monitored consumable. The same device can expose both kinds.

The distinction is an organizational suggestion. A diagnostic entity can still matter to a person or an automation, so this label is not permission to hide it, stop recording it or disable it.

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 diagnostic roles.

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

    Add the information to check

    Read the sensor's described purpose to separate device or connection diagnostics from household and consumable measurements.

  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 Diagnostic, Primary, 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
Network signalDiagnostic100%
Room temperaturePrimary100%
Device uptimeDiagnostic100%
Filter lifePrimary100%
Phone batteryDiagnostic78.0%
Undefined statusDiagnostic63.0%

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. 4 of 6 results matched the authored fixture expectations. For Phone battery, the expectation was Unclear; the observed choice was Diagnostic. For Undefined status, the expectation was Unclear; the observed choice was Diagnostic.Verified

Understand the results

Sensor diagnostic roles: 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 entity organization
  • Separating device status from room conditions
  • Preserving ambiguous metadata

Outside this demonstration

  • Disabling or hiding entities
  • Deciding what is safe to ignore
  • Diagnosing physical equipment
Example FAQ

Using this example

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

Does Diagnostic mean unimportant?

No. Signal strength and uptime may be useful. The label describes the information’s subject, not its importance or retention policy.

Why is filter life Primary?

This disclosed contract treats consumable life as a household reading someone may monitor. It differs from the device’s firmware or network status.

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.