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

Screenshots From the README of azogue/eventsensor.

step 1step 2step 3

About

Event sensor is a Home Assistant integration that creates sensors tracking and storing specific events. It was written to give entities to ZigBee switches that only produce events when pressed, and it can follow any other event as well. Each sensor listens for a named event, can filter on key and value pairs inside the event data, and takes its state from a chosen event field. Nested event data can be reached with dot notation, both in filters and for the state. A custom state mapping can turn raw values into readable states, and presets exist for Friends of Hue remotes through Hue or deCONZ. Setup runs through a wizard in the UI, and existing sensors can be edited later without a restart. Legacy YAML configuration is still read but logs a deprecation warning.

Automatic summary of the README and code of azogue/eventsensor. 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.

EventSensor - New

  • Integration firing events to listen for
  • Name for the new sensor tracking events

EventSensor - Generic definition

  • Event name to listen to
  • Filter with key: value pairs inside the event data
  • Event field to use as sensor state
  • Desired mapping for the sensor states

EventSensor - Listener for FoH remote

  • Unique identifier for device firing events (leave empty for all devices)
  • Select one of the pre-configured state mappings, or define a generic one
  • Select the identifier field used to filter events for a specific remote

EventSensor - Custom state mapping

  • Desired mapping for the sensor states as raw_data: pretty_state, pairs.

After setup

  • Event name to listen to
  • Optional event filter with key: value pairs inside the event data
  • Name of the sensor
  • Event field to use as sensor state
  • Optional custom state mapping

Texts from the code of azogue/eventsensor.

From the README

Custom integration to create sensors that track, represent and store specific Home Assistant events.

Created to assign HA entities for ZigBee switches that only generate events when pressed, but could be useful in other scenarios where some specific event needs to be tracked.

From the README of azogue/eventsensor, MIT License. Shortened.

Shows in Vulpo

Chart card, Apple Watch.

Information

Installs
128 sharing analytics
GitHub stars
94
Connection
Works locally
Upkeep
Updated in the last 6 months
Version
v3.3.1,
Category
Sensors
Kind
Marketplace integration
Needs
Needs the Marketplace (HACS on 2026.10 and older)
Domain
eventsensor

You might also like

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