Jev device room match

Match a device to a room you already have

Provide device metadata and the existing room list. Choose a clearly stated kitchen, office or garage, keeping unknown and conflicting locations unmatched.

device room matchLive API
Try an example

The device name explicitly identifies a listed room.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original metadata-matching exercise adapts the area-choice question in ha-gutcheck, linked by the source post. The rooms and devices are fictional. It does not locate hardware, create rooms or change Home Assistant assignments.

Match the device description to the supplied existing rooms, choosing Kitchen, Office or Garage only when that room is clearly identified.

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

An area assignment should use the installation’s actual room list. A clear Bedroom label does not justify mapping to Office just because Bedroom is missing from that list.

This demonstration reads naming metadata, not location sensors. It leaves portable or ambiguously named devices unresolved and never writes the selected label into a real registry.

This original metadata-matching exercise adapts the area-choice question in ha-gutcheck, linked by the source post. The rooms and devices are fictional. It does not locate hardware, create rooms or change Home Assistant assignments.

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 device room matching.

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

    Add the information to check

    Provide device metadata and the existing room list.

  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 Kitchen, Office, Garage, None. 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 uncertain or unexpected results 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
Named kitchen deviceKitchen55.0%
Office workspaceNone96.0%
Garage sensorGarage88.0%
Model aloneNone100%
Unlisted bedroomNone100%
Conflicting namesNone100%

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 Office workspace, the expectation was Office; the observed choice was None.Verified

Understand the results

Device room matching: 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 unassigned device names
  • Checking existing-room candidates
  • Finding metadata that needs clarification

Outside this demonstration

  • Locating physical devices
  • Creating new rooms
  • Operating or reconfiguring equipment
Example FAQ

Using this example

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

Can a device type establish the room?

Not under this rule. Supply a room-bearing description; common product use is not evidence of this installation’s location.

What if the correct room is missing?

The result is None. An application can ask the user to create or select the right room separately, with permission to update the registry.

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.