Target Timeframes for Home Assistant (Marketplace integration)

Installs: 403 sharing analytics
GitHub stars: 24
Connection: Works locally
Upkeep: Updated in the last 6 months
Version: v1.5.2, May 30, 2026
Category: Helpers, Calculate a value
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: target_timeframes
Source: github.com/BottlecapDave/HomeAssistant-TargetTimeframes
Issues: Report an issue

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

Target Timeframes finds the best time periods in a day based on values from external data sources. It adds binary sensors that turn on during the lowest or highest value periods, plus sensors, and it works locally. The values can stand for anything, such as energy prices, carbon emissions on the grid, or solar generation. It was extracted from the Octopus Energy integration, where the values were energy costs and the cheapest periods were found. Each data source gets a name and a unique id that appears in the related entity names, and the sensor behavior can be configured in several ways. It also raises events for automations and includes services and blueprints, and it is set up in the UI.

Automatic summary of the README and code of BottlecapDave/HomeAssistant-TargetTimeframes. Something wrong, or are you the maintainer and want your own text here? Get in touch

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.

Provides

Sensors

Setting it up

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

Add Data Source

The name of the source
The id of the sourceThis must be unique across all sources. This is used in all related entity names.

Reconfigure Data Source

The name of the source
The id of the sourceThis must be unique across all sources. This is used in all related entity names. Changing will create new entities.

Texts from the code of BottlecapDave/HomeAssistant-TargetTimeframes.

From the README

Target timeframes was a feature that has been extracted out of the Octopus Energy integration. The idea is you can configure binary sensors that will find and turn on during the most optimal time periods based on external data sources, targeting either the lowest or highest values. What these values represent can be anything. In the original integration, the values represented cost of energy, and so the cheapest periods were discovered. But it could represent other things like
How the sensors behave is configurable in a number of ways and explained further in the docs.

From the README of BottlecapDave/HomeAssistant-TargetTimeframes, MIT License. Shortened.