Jev for Home Assistant
HACS integration: Jev questions become sensors, jev.* actions, AI Task, Assist, house check repairs, cost budget, and 25 blueprints.
Overview
HA-Jev (github.com/AboveColin/HA-Jev, HACS custom integration, hassfest and HACS CI) brings TypeSafe Jev into Home Assistant as AboveColin's Jev (TypeSafe) integration. Each configured question becomes a sensor exposing noul probability, choice distribution, or score value. Services jev.noul, jev.choice, jev.score, and jev.ask return response variables inside automations. An AI Task entity answers ai_task.generate_data when called. A conversation agent routes Assist through the same model. House check opens Repairs for week-long unavailable entities, low batteries, and suspicious states with one-click fixes. Daily token spend and budget sensors sit beside entities. 25 blueprints and 15 examples ship in repo; full docs live at jev.cdevries.dev. API client is github.com/AboveColin/jevclient. README states not affiliated with TypeSafe. Public GitHub counts were 68 stars when this listing was drafted.
Problem: Home Assistant automations excel at sensors and scripts, but house-level judgments still get wedged into brittle template logic or a chat model with no calibrated entity to automate on.
Built for: Home Assistant 2026.9+ operators who want TypeSafe Jev questions as sensors, service actions, AI Task fields, Assist conversation, and blueprint-ready automations with daily cost visibility.
First indexed on Jev Directory: 2026-09-30
Creator and team
- Name
- Colin
- Handle
- @AboveColin
How Jev is used
- Role in the product flow
- Home entity sensors from standing questions, on-demand actions, AI Task and Assist conversation paths, and house-check repair prompts
- Primitives
- ChoiceScoreNoul
- State in
- Question text plus Home Assistant state context documented at jev.cdevries.dev/writing-questions/, including entity attributes the integration attaches per question type.
- Decision out
- Sensor state as probability, labeled choice with distribution, or numeric score; automation response variables from jev.* actions; AI Task typed fields; conversation agent replies.
- Install via HACS custom repository or copy custom_components/jev from latest release
- Config flow with TypeSafe API key; optional OpenRouter address and ~typesafe/jev-latest model per install docs
- Define questions in UI or YAML; integration polls or triggers updates per question config
- Automations call jev.noul, jev.choice, jev.score, or jev.ask, or trigger on binary_sensor.jev_* entities
- House check batches repair candidates; cost sensors aggregate calls and tokens against daily budget
This is the first Home Assistant integration on the directory: Jev is not generating chat prose, it is answering typed questions whose outputs become entities and service responses you can put in YAML automations. classifier-dev is the hosted API product when you only need HTTP gates outside HA. browser-use-jev-ultrafast shows Jev driving another automation surface (the browser) with different state. docjev classifies documents from rules, not house sensors. Cite jev.cdevries.dev (questions UI and YAML, actions, AI Task, conversation, house check, cost, measurements, limitations) and AboveColin/HA-Jev README. Not a TypeSafe official release.
Sourced performance claims
- jev.cdevries.dev documents 25 importable blueprints (7 question-driven, 18 situational) and 15 worked examples, 4 pairing Jev with an LLM.Source: jev.cdevries.dev blueprints and examples index
- README requires Home Assistant 2026.9 or newer; hassfest, tests, and HACS GitHub Actions badges on main.Source: github.com/AboveColin/HA-Jev README Installation
- Public GitHub repo AboveColin/HA-Jev had 68 stars when this listing was drafted.Source: GitHub API 2026-09-30
Features and stack
Features
- Question sensors for noul, choice, and score with confidence semantics
- jev.noul, jev.choice, jev.score, and jev.ask automation actions
- AI Task and Assist conversation agent integrations
- House check Repairs card with quick fixes
- Daily cost and token budget reporting
- HACS install path with 25 blueprints
Stack
- Python
- Home Assistant 2026.9+
- jevclient
- TypeSafe Jev API
- HACS custom integration
Pricing: Integration is open source; Jev API usage bills to your TypeSafe or OpenRouter key per jev.cdevries.dev/cost/ daily budget docs.
Links
FAQ
- Is this an official TypeSafe or Home Assistant integration?
- README and docs state it is not affiliated with TypeSafe. It is a community HACS custom repository maintained by AboveColin.
- What Home Assistant version is required?
- README: 2026.9 or newer, plus an API key from typesafe.ai or OpenRouter per install page.
- How do I add the first question?
- jev.cdevries.dev/first-question/ walks through UI or YAML after the config flow completes.
- Where is the Python client documented?
- README points to github.com/AboveColin/jevclient as the API client used by the integration.
Related learn guides
Original Jev guidance that pairs with this product pattern.
- Jev use cases
The patterns builders actually search for: moderation, routing, triage, RAG verify, and agent gates.
- Jev & TypeSafe
A primer for builders who need to know what Jev is, who it is for, and when TypeSafe docs should take over from this directory.
Related products
Hand-picked neighbors with rich profiles or overlapping tags.