--- title: "Entity Controller" description: "Entity Controller is a Marketplace integration for Home Assistant. It has 131 installs sharing analytics and was last updated May 4, 2024." canonical: "https://vulpo.app/integrations/marketplace/danobot-entity-controller" url: "https://vulpo.app/integrations/marketplace/danobot-entity-controller.md" last-updated: "2026-10-22" version: "1.4" --- # Entity Controller > Entity Controller is a Marketplace integration for Home Assistant. It has 131 installs sharing analytics and was last updated May 4, 2024. Entity Controller is an integration that runs timed "when this, then that" automations for lights and other entities. It uses a finite state machine, so these basic automations do not interfere with the rest of a Home Assistant setup. Common automation scenarios are packaged into a controller that is configured once and reused for each instance, instead of duplicating traditional automations. Any entity can serve as an input or an output, so it is not limited to motion sensors and lights. Its description also lists scripts and sun-based time restrictions among the features. Setup is done through YAML configuration after installing from the Marketplace. Automatic summary of the README of danobot/entity-controller. 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=danobot&repository=entity-controller&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=danobot&repository=entity-controller&category=integration) ## Supports - **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 > Entity Controller (EC) is an implementation of "When This, Then That for x amount of time" using a finite state machine that ensures basic automations do not interfere with the rest of your home automation setup. This component encapsulates common automation scenarios into a neat package that can be configured easily and reused throughout your home. Traditional automations would need to be duplicated for each instance in your config. The use cases for this component are endless because you can use any entity as input and outputs (there is no restriction to motion sensors and lights). From the README of [danobot/entity-controller](https://github.com/danobot/entity-controller#readme), [GNU GPL v3.0](https://spdx.org/licenses/GPL-3.0.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Lighting](https://vulpo.app/integrations/category/lighting.md) - Number: 131 installs sharing analytics; 319 GitHub stars - Connection: Connection not stated - Upkeep: No update in over 18 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v9.7.6, last updated May 4, 2024 - Domain: `entity_controller` - Source: - Issues: - Screenshot: https://vulpo.app/integrations-img/98748ef83790e4a7.webp (from danobot/entity-controller's README) 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/danobot-entity-controller --- - HTML version of this page: https://vulpo.app/integrations/marketplace/danobot-entity-controller - 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