---
title: "Viertelstunden-Wächter"
description: "Viertelstunden-Wächter is a Marketplace integration for Home Assistant. It has 57 installs sharing analytics, works locally and was last updated November 15, 2026."
canonical: "https://vulpo.app/integrations/marketplace/mobilewhatelse-viertelstunden-waechter"
url: "https://vulpo.app/integrations/marketplace/mobilewhatelse-viertelstunden-waechter.md"
last-updated: "2026-11-15"
version: "1.4"
---

# Viertelstunden-Wächter

> Viertelstunden-Wächter is a Marketplace integration for Home Assistant. It has 57 installs sharing analytics, works locally and was last updated November 15, 2026.

Viertelstunden-Wächter keeps the highest quarter-hour average of grid import below a set limit, for power-based grid tariffs. It estimates every 20 seconds where the running quarter hour will end, lowers the wallbox charging current if needed, and pauses other devices in a chosen order. Once there is room again, devices are given back step by step, and each decision is logged with its reason. It works locally and can take the grid import from evcc or read a car planner's charge plan to anticipate charging. Entities include sensors for quarter-hour energy, forecast, allowed import and peaks, plus switches, numbers and selects for limit, margin and mode. An observe-only mode logs what would happen without switching anything, and actions cover a generated dashboard, CSV export and peak history import.

Automatic summary of the README and code of mobilewhatelse/viertelstunden-waechter. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/support)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/marketplace_repository/?owner=mobilewhatelse&repository=viertelstunden-waechter&category=integration)

On Home Assistant 2026.10 or older? [Open it in HACS](https://my.home-assistant.io/redirect/hacs_repository/?owner=mobilewhatelse&repository=viertelstunden-waechter&category=integration)

## Supports

- **Works locally**: Talks to your devices on your own network. No vendor cloud in between.
- **From the Marketplace**: Installed through the Marketplace, formerly HACS.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

### Set-up 1 of 4: grid import

- **Name**
- **Grid import power**: Sensor with the power drawn from the grid (W or kW). Negative values (export) count as 0. Optional if you enter evcc.
- **Grid import energy counter**: Optional but recommended: the meter's import counter. Makes the quarter-hour energy exact after restarts.
- **Limit**: The quarter-hour average that must not be exceeded.
- **Safety margin**: The guard aims at limit minus margin.
- **Address of evcc (optional)**: Optional: take the grid import from evcc (for example http://192.168.1.20:7070). Your own sensor above always wins. If evcc runs on the same machine as Home Assistant (add-on), the address is suggested; clear the field if you do not want it.
- **Password of evcc**: Only if evcc asks for a password.
- **evcc as a reserve for the grid import**: While your sensor has no usable value (missing or too old) the guard uses evcc instead of giving everything back. It changes back by itself.

### Set-up 2 of 4: is the sign right?

- **Turn the sign round**: On = the sensor counts import as negative (e.g. a meter that shows export as positive).

Also asked when at the set-up 2 of 4: is the sign right? step and at the set-up 2 of 4: is the sign right? step.

### Set-up 3 of 4: the limit

- **Limit**: The quarter-hour average that must not be exceeded.
- **Safety margin**: The guard aims at limit minus margin.

### Which evcc loadpoint?

- **Loadpoint**

### evcc loadpoint

- **Name**
- **Priority**: 1 = restricted first, 10 = only when nothing else helps.
- **Address of evcc**: For example http://192.168.1.20:7070 (reachable from Home Assistant).
- **Loadpoint number**: 1 = the first loadpoint in evcc.
- **Password of evcc**: Only if evcc asks for a password (administrator password).
- **Minimum current**
- **Maximum current**: The ceiling the guard gives back to evcc afterwards is the one evcc had before.
- **May switch to 1 phase**: Only works if the charger can switch phases. Off = only throttled.
- **Charging power (optional)**: Optional sensor, for example from the evcc integration of the community. Without it the guard reads the power from evcc.
- **Intervention only while**: Optional. Only while this entity is on.
- **Observe only**: The guard only writes to the log what it would do with this device. Nothing is sent to it and it does not count as a lever. Good for trying a new device first.
- **Turn the sign round (power sensor)**: On = the power sensor counts consumption as negative.

### Wallbox

- **Name**
- **Priority**: 1 = restricted first, 10 = only when nothing else helps.
- **Charging power**
- **Charging current setting**: A number in A or a list like "6 A", "8 A" … (e.g. Anker SOLIX V1). With a list the guard picks the matching entry, never a higher one.
- **Minimum current**
- **Maximum current**
- **Phase selection**: Optional. Without it the wallbox is only throttled, never switched to 1 phase.
- **Option for 1 phase**: Exact option text of the phase selection for 1 phase, e.g. 1 Phase.
- **Phases in use**: Optional sensor with the number of phases currently used.
- **Intervention only while**: Optional. Only while this entity is on.
- **Observe only**: The guard only writes to the log what it would do with this device. Nothing is sent to it and it does not count as a lever. Good for trying a new device first.
- **Turn the sign round (power sensor)**: On = the power sensor counts consumption as negative.

### After setup

- **Grid import power**: Sensor with the power drawn from the grid (W or kW). Negative values (export) count as 0. Optional if you enter evcc.
- **Grid import energy counter**
- **Only needed while**: Optional. The guard only intervenes while this entity is on (e.g. a template that is on when the car may charge from the grid). Off: everything is given back.
- **Block active mode while**: Optional. While this is on, active mode is refused and the guard only observes (e.g. an older guard that is still running).
- **Notify services**: Optional, comma-separated, e.g. notify.mobile\_app\_phone. Used when the limit cannot be held.
- **Mode after a restart**: Restore = the mode it had before the restart.
- **Mains voltage**: Voltage of one phase (230 V in Europe). Used to convert amps into kilowatts.
- **AI task for the explainer**: Optional: the AI task entity (Settings \> Devices \> AI tasks) the explainer uses. You choose the model; the guard has no key of its own.
- **Weather entity for the forecast**: Optional: a weather entity. With it the load forecast follows the expected outdoor temperature (heating in winter, air conditioning in summer). Without it nothing changes.
- **Outdoor temperature sensor**: Optional: an outdoor temperature sensor. More exact than the weather entity for learning, and its history lets the correction start at once instead of after some weeks.
- **Other charge plan sensors**: Only for another source: charge plan sensors by hand (attributes windows and departure). Not needed when you chose the car planner.
- **Car planner**: Choose the car planner (for example Plugwhen) and the guard finds the charge plans of all its vehicles by itself, also vehicles added later. Until the departure the forecast then knows when each car really charges instead of using the learned wallbox pattern. Without it nothing changes. Suggested automatically if exactly one is installed.
- **Maximum age of the grid reading**: A grid reading that was not written for longer than this counts as missing: no interventions, everything is given back after 90 seconds. Protects against stale values (a sensor that only updates every few minutes cannot be used for control). 0 = never.
- **Address of evcc (optional)**: Optional: take the grid import from evcc (for example http://192.168.1.20:7070). Your own sensor above always wins. If evcc runs on the same machine as Home Assistant (add-on), the address is suggested; clear the field if you do not want it.
- **Password of evcc**: Only if evcc asks for a password.

Texts from the code of [mobilewhatelse/viertelstunden-waechter](https://github.com/mobilewhatelse/viertelstunden-waechter).

## Entities

- **Buttons**: Send feedback
- **Numbers**: Limit, Safety margin, Demand charge up to the threshold, Demand charge above the threshold, Price threshold
- **Selects**: Mode, Strategy
- **Sensors**: Status, Quarter-hour energy so far, Quarter-hour forecast, Allowed import now, Last quarter hour, Peak today, Peak this month, Interventions today, Relief now (estimate), Demand charge this month, Demand charge without the guard (estimate), Savings this month (estimate), and 7 more
- **Switches**: Use peak already reached, Message on intervention, Calculate cost and savings, Learn and show the load forecast, Calculate the charge plan, Also carry out the charge plan, Early warning before an intervention, Weekly report, Throttle ahead using the forecast, Battery reserve before a peak, AI explainer, Weather correction of the forecast, and 1 more
- **Texts**: Feedback

## Actions

- **Create dashboard**: Builds a ready-made dashboard (overview, statistics and forecast) with this installation's entities. The YAML is returned and shown as a notification; paste it into a new dashboard (three dots \> Edit \> Raw configuration editor). The service never writes into an existing dashboard. Administrators only.
- **Import history**: Seeds the day and month peaks from an earlier measurement (a spreadsheet, an older script). Only raises values; values from hourly data are lower bounds.
  Fields: Days, Months
- **Send the weekly report**: Sends the report of the last full week (or the running week) as a message.
  Fields: Running week, Send the message
- **Export as CSV**: Writes the quarter-hour load profile or the daily peaks to config/viertelstunden\_waechter/export/ (not a public folder).
  Fields: What, Days, Format
- **Explain today**: Asks the AI task for a short explanation of today's interventions (without interventions no AI is asked).
  Fields: Send the message
- **Correct a quarter hour**: Replaces a quarter-hour value that was recorded wrong with the value from the meter and works out the day's and the month's peak again. Only for administrators.
  Fields: Start, Value
- **Send feedback**: Sends your feedback to the author of the Viertelstunden-Wächter (aiwhatelse.eu). With 'include setup' an overview goes along: which kinds of devices and from which integrations, no names, entity ids or values.
  Fields: Text, Contact (optional), Include setup

## Troubleshooting

- **Diagnostics**: Downloads a diagnostics file to attach to a bug report.
- **Repair notices**: Notices it can show in Settings, Repairs:
  Share anonymous data? (a request)

## From the README

> A Home Assistant integration that keeps the highest quarter hour of your grid import below a limit. It throttles the wallbox and pauses devices, only as long as needed.
>
> Deutsch: docs/ANLEITUNG.md · Full manual (English): docs/MANUAL.md · FAQ: English, Deutsch

From the README of [mobilewhatelse/viertelstunden-waechter](https://github.com/mobilewhatelse/viertelstunden-waechter#readme), [GNU AGPL v3.0](https://spdx.org/licenses/AGPL-3.0.html). Shortened.

## At a glance

- Kind: Marketplace integration
- Category: [Energy](https://vulpo.app/integrations/category/energy.md), Energy prices
- Number: 57 installs sharing analytics; 7 GitHub stars
- Connection: Works locally
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: v0.14.4, last updated November 15, 2026
- Domain: `viertelstunden_waechter`
- Source: <https://github.com/mobilewhatelse/viertelstunden-waechter>
- Issues: <https://github.com/mobilewhatelse/viertelstunden-waechter/issues>

In Vulpo: Quick Toggle card, Button card, Select card, Chart card, Apple Watch, Control Center

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-11-15. Source: https://vulpo.app/integrations/marketplace/mobilewhatelse-viertelstunden-waechter

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/mobilewhatelse-viertelstunden-waechter
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml
