npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

homebridge-esphome-hv2

v1.4.0

Published

Modernized ESPHome plugin for Homebridge with Encryption Key support

Readme

Homebridge ESPHome HV2

npm version verified-by-homebridge

Developed and maintained by Brau Cadena.

This plugin integrates the ESPHome platform into Homebridge so that you don't have to go through Home Assistant if you don't want to. It makes use of the native API of ESPHome so that you can expect instant updates for all your accessories.

🚀 Why HV2?

This version was specifically refactored to solve modern connectivity issues:

  • API v1.14+ Compatibility: Fixes the outdated API 0.0 error found in older plugins when connecting to recent ESPHome firmware.
  • Noise Encryption Support: Adds the encryptionKey field for secure communication (Noise protocol), which is now the standard for ESPHome.
  • Node.js Optimized: Designed for modern environments, supporting Node.js 18, 20, and 22.

Supported Components:

  • Lights: Including dimmable and RGB.
  • Switches: Standard switches and restart buttons.
  • Binary Sensors: Motion, window, door, smoke, and leakage.
  • Sensors: Temperature, humidity, and Ultrasonic/Water Level (rendered as percentage).

Installation

Unless you haven't done so already, make sure to install Homebridge first. See instructions here. Once you have done this, you can install this plugin by typing:

npm install -g homebridge-esphome-hv2

Getting Started

Add the following to your Homebridge config.json or use the Configuration UI:

{
    "platform": "esphome-hv2",
    "devices": [
        {
            "name": "Tinaco Sensor",
            "host": "192.168.68.113",
            "encryptionKey": "YOUR_32_CHAR_ENCRYPTION_KEY",
            "port": 6053,
            "retryAfter": 60000 
        }
    ],
    "discover": true,
    "debug": false
}

Configuration Fields:

host: (Mandatory) The IP address of your ESP device (e.g., 192.168.1.50 or my_esp.local). encryptionKey: The Noise encryption key found in your ESPHome YAML under api: encryption: key:. password: (Legacy) Only use if you are still using the old plaintext password method. port: Default is 6053.

Blacklisting

If you want to exclude a specific component, add its name (as defined in ESPHome) to the blacklist array:

{
    "platform": "esphome-hv2",
    "devices": [...],
    "blacklist": [
        "Internal Status LED",
        "Restart Button"
    ]
}

Troubleshooting

  1. Check your YAML: Please make sure to add the api: entry to your ESPHome configuration!
  2. Connection Issues: If you see outdated API 0.0 or Connection Refused, ensure you have copied the encryptionKey exactly as it appears in your YAML and that your Homebridge can ping the device IP.
  3. Debug Mode: Before opening a ticket, set "debug": true in your config. This will:

Output the raw data received from your ESP device to the Homebridge console.

Write individual log files for each device under /tmp (or your OS temp folder).

Note: Writing debug files occupies space. Turn off this option once you don't need it anymore.

Contributing

This project is an open effort to keep the ESPHome-Homebridge ecosystem alive. If you find a bug or want to suggest a feature, please open an issue on the official GitHub repository:

https://github.com/BrauCadena/homebridge-esphome-hv2

License

Licensed under the GPL-3.0 License.