---
title: "Schedule State"
description: "Schedule State is a Marketplace integration for Home Assistant. It has 64 installs sharing analytics, works locally and was last updated February 20, 2026."
canonical: "https://vulpo.app/integrations/marketplace/aneeshd-schedule-state"
url: "https://vulpo.app/integrations/marketplace/aneeshd-schedule-state.md"
last-updated: "2026-10-22"
version: "1.4"
---

# Schedule State

> Schedule State is a Marketplace integration for Home Assistant. It has 64 installs sharing analytics, works locally and was last updated February 20, 2026.

Schedule State is a Home Assistant integration that creates sensors whose value follows a defined daily schedule. It handles only the timing side of automations, so the sensor state can trigger standard automations or serve as a condition in them. Each sensor has a default state, and layered events with start and end times switch it to other state names. Start and end times can be shifted by an offset in minutes, events can wrap past midnight, and a new event that overlaps an older one resizes the older one. Events can also depend on conditions, which allows separate schedules for weekends or holidays, and each state can carry its own icon. It runs locally and is configured in YAML.

Automatic summary of the README of aneeshd/schedule\_state. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=aneeshd&repository=schedule_state&category=integration)

On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=aneeshd&repository=schedule_state&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.

## Setting it up

Install it from the Marketplace and restart Home Assistant. It is then set up in configuration.yaml.

## From the README

> A custom component for Home Assistant that simplifies the creation of schedule-based automations.
>
> It takes a very different approach from other projects of this type, because it only provides scheduling functionality. It does not try to replace the powerful automations framework that Home Assistant provides.

From the README of [aneeshd/schedule\_state](https://github.com/aneeshd/schedule_state#readme), [Apache License 2.0](https://spdx.org/licenses/Apache-2.0.html). Shortened.

## At a glance

- Kind: Marketplace integration
- Category: [Helpers](https://vulpo.app/integrations/category/helpers.md), Store a value
- Number: 64 installs sharing analytics; 52 GitHub stars
- Connection: Works locally
- Upkeep: No update in 6 to 18 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: 0.20.4, last updated February 20, 2026
- Domain: `schedule_state`
- Source: <https://github.com/aneeshd/schedule_state>
- Issues: <https://github.com/aneeshd/schedule_state/issues>

In Vulpo: Chart card, Apple Watch

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-10-22. Source: https://vulpo.app/integrations/marketplace/aneeshd-schedule-state

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/aneeshd-schedule-state
- 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