Question 1

Will this wake my house up on every state change and quietly drain the account?

Accepted Answer

It only costs you what you make it call, and it reports the bill. The integration tracks calls, input tokens and estimated cost per day against a daily token budget, and stops evaluating once that budget is spent. A conversation agent for Assist routes spoken commands through the same model and counts against the same budget. There is no local model path; it calls the hosted API.

Question 2

Is it in HACS already, or do I have to add a custom repository?

Accepted Answer

Custom repository. It is not in the HACS default list, so you add it once as an Integration-type repo, download it through HACS and restart Home Assistant. Copying custom_components/jev into your config directory also works, but HACS does not update a manually copied install. It requires Home Assistant 2026.9 or newer plus an API key.

Question 3

Can I point it at OpenRouter or my own proxy instead of TypeSafe?

Accepted Answer

Yes. The install page documents every option, including pointing it at a proxy. For OpenRouter you set the address field to the OpenRouter API and the model to ~typesafe/jev-latest. The address box already ships pre-filled with the TypeSafe API, so switching means editing the address and model on the same integration rather than adding a second one.

Question 4

Is this a chat model I can hold a conversation with, or only a decision surface?

Accepted Answer

Only a decision surface. Every question returns a probability, a chosen option with its distribution, or a number that can land between levels, which is what sensors and the four automation actions consume. It is not affiliated with TypeSafe and keeps a Limitations page for what it cannot do. Whether a given probability justifies firing an automation is a threshold you set.

Question 5

What can I build on top of a question?

Accepted Answer

More than sensors. There are 25 importable blueprints, seven of which start from your own question and 18 each handle one situation such as a forgotten washing machine or a window open while the heating runs. There is also an AI Task entity that answers ai_task.generate_data, where a boolean, select, or number field becomes the matching question type, and a house check that opens a Repairs card.

Question 6

What does the house check actually catch?

Accepted Answer

It looks for entities unavailable for a week, low batteries, and, in a single request, states that look like a mistake. A light left on can be turned off from its card and put back afterwards. It is a heuristic sweep over your own state history rather than anything Jev-specific, and it is what turns the integration into a maintenance tool rather than only a decision surface.

Question 7

How is this tested, and where does the API client live?

Accepted Answer

204 tests run the integration inside a real Home Assistant with the API client replaced, so the suite spends nothing. That client is a separate repository, jevclient, rather than a folder inside this one. Development needs Python 3.14 because the pinned pytest-homeassistant-custom-component fails to install on 3.13.

Jev for Home Assistant

About this project

Highlights

Questions about this entry

Reactions & coverage

From the Jev guides

From the Jev AI model community