Community · E2 · artifact verified

Turn Home Assistant state into automation signals

A Home Assistant integration exposes Jev probabilities, choices, and scores as entities and action responses that automations can use.

01 · Role in the system

What Jev does here

Jev evaluates selected entities, devices, areas, floors, labels, or templates and returns typed answers. The integration handles configuration, update triggers, batching, daily token budgets, thresholds, and entity creation. Automations can then branch on the resulting values without parsing model prose.

Judgments that arrive as Home Assistant entities

The integration's contribution is plumbing: Jev's probabilities, choices, and scores appear as ordinary Home Assistant entities and action responses, so an automation can branch on a sensor crossing a threshold instead of parsing model prose. Configuration, update triggers, batching, daily token budgets, and thresholds all stay in the integration's code.

That shape moves the risk conversation to familiar ground. A homeowner edits an existing automation with typed signals; nothing in the critical path asks a model to compose an action, and the worst case is a wrong sensor value, not a hallucinated command.

Calibration is the open problem

The author's own guidance draws the boundary clearly: do not point this at locks, heaters, or smoke alarms, and treat published confidence values as uncalibrated until they are checked against your own home. Both caveats are recorded in the limitations rather than buried in a README footnote.

As a pattern, this record shows where typed judgments fit in consumer automation: sensing and classification that feed deterministic rules. The missing evidence is calibration data — how often the scores are right in a lived-in house — and no published metric exists yet.

02 · Control boundary

Where Jev sits

Home state to typed Jev questions; the integration maps answers to sensors and automation response variables.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

  • The author advises against using the integration for safety-critical locks, heaters, or smoke alarms.
  • Answers contain no reasoning and published confidence values require local calibration.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

The public artifact behind this record — Turn Home Assistant state into automation signals — as captured by an editor on 2026-10-08
Editor capture of the public artifact, 2026-10-08. Repositories and demos change — the live source ↗ is authoritative.