Jev unavailable entity triage

Review why a home entity is unavailable

Provide the noncritical entity's role, current condition and device history. Separate expected inactivity from unexpected loss and a stale restored record without controlling devices or deleting entries.

unavailable entity triageLive API
Try an example

The optional attribute is not expected while idle.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Review an unavailable noncritical home entity.

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

Entity meaning matters. An optional playback attribute can disappear when a player is idle even while the device itself is working. A continuously reported status has a different expectation.

A stale-record suggestion requires explicit removal history. Time since the last update alone does not prove that a device was retired or that its data should be deleted.

The linked Home Assistant helper reviews unavailable entities with model and deterministic checks. This page is a fictional text adaptation for noncritical devices and performs no device control or configuration changes.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of routing a message into one of several label groups
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 unavailable entity triage.

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

    Add the information to check

    Provide the noncritical entity's role, current condition and device history.

  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 Expected, Investigate, Stale record, Review. 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 Review 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
Optional playback detailExpected97.0%
Expected reporter missingInvestigate100%
Removed demo deviceStale record77.0%
Another expected idle detailExpected98.0%
Unknown roleReview99.0%
Conflicting removal notesReview97.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. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Unavailable entity triage: 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

  • Explaining an unavailable flag with supplied entity context.
  • Distinguishing an optional idle attribute from an expected reporter.
  • Reviewing historical entries after a documented device removal.

Outside this demonstration

  • Using this example for alarms, medical devices or other life-safety systems.
  • Deleting an entity based on the model label alone.
Example FAQ

Using this example

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

Is this connected to my Home Assistant?

No. It reads the fictional role and status facts you enter. It has no connection to a home network or device registry.

Does Stale record authorize removal?

No. It identifies a record for review under the supplied history. Verify dependencies and backups before any real configuration change.

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.