Release 5.0.0
Version 5.0.0 of the Home Assistant Glow is here 🌟! This major release brings a configurable internal filter to reduce ghost pulse detections, alongside a breaking change: all entity names have been cleaned up to follow the modern ESPHome naming convention.
Entity Name Changes
ESPHome now recommends using bare entity names without a device name prefix. Home Assistant automatically shows entity names in the context of their device, making the prefix redundant. All entities in the Glow firmware have been updated accordingly.
The following entities have been renamed:
| Old name | New name |
|---|---|
{device} - Power Consumption | Power Consumption |
{device} - Total Energy | Total Energy |
{device} - Daily Energy | Daily Energy |
{device} - ESPHome Version | ESPHome Version |
{device} - IP Address | IP Address |
{device} - Connected SSID | Connected SSID |
{device} - WiFi Signal | WiFi Signal |
Glow - Installed version | Installed Version |
Restart - Glow | Restart |
Renaming entities changes their entity IDs in Home Assistant. After updating, the old entities will show as unavailable and new ones will be created. You will need to update any automation flows, dashboards, or Energy dashboard configurations that reference the old entity IDs.
Migration Guide
After updating to 5.0.0, take the following steps:
- Open Home Assistant and go to Settings > Devices & Services > ESPHome
- Open the Glow device page and verify the new entity names appear
- Remove the unavailable (old) entities via Settings > Devices & Services, selecting each old entity and deleting it
- Update any automation flows or dashboard cards that referenced the old entity IDs
- If you use the Energy dashboard, re-select the correct entities under Settings > Energy
Configurable Internal Filter
Based on a community request, this release exposes the internal filter of the pulse meter as a configurable entity in Home Assistant. Previously, users experiencing ghost pulses (false detections that cause unrealistic power spikes) had no way to adjust the filter without modifying the firmware directly.
The Internal Filter entity appears in the configuration section of the Glow device page in Home Assistant. It accepts values in microseconds (µs), with a default of 1000 µs (1 ms) and a maximum of 100000 µs (100 ms). The value is persisted across reboots, so you only need to set it once.
If you are experiencing sudden power spikes in the thousands of kilowatts, try increasing the internal filter value gradually. A value between 1000 µs and 10000 µs is a good starting point for most setups.
Setting the internal filter too high can cause real pulses to be missed at high power consumption. See the Internal Filter page for guidance on choosing the right value for your setup.
If you previously used !extend sensor_energy_pulse_meter with internal_filter in your YAML configuration, this will no longer have any effect. The Internal Filter entity always takes precedence after boot. You can remove the !extend block and set your desired value via the UI instead.
Pulse Rate Entity Fix
ESPHome warns that entity names containing / are reserved as URL path separators and will become an error in ESPHome 2026.7.0. The Pulse Rate entity was previously named Pulse rate - imp/kWh and is now simply Pulse rate, with imp/kWh set as a proper unit_of_measurement.
Upgrading to 5.0.0
Via Home Assistant: If your Glow is connected to Home Assistant, you'll receive an update notification automatically. Simply click update from the device page, the easiest option.
Via the Web Interface (OTA): Download the correct firmware binary from the Firmware Updates page, open the Glow's web interface, and upload it via the OTA Update section.
Via USB: Head to the Getting Started page, select your variant, and flash via USB.
Wrap up
This release is a significant step in keeping the Home Assistant Glow aligned with current ESPHome best practices, while also making the firmware easier to use for those dealing with noisy meter environments. The entity renaming requires some manual steps after upgrading, but the result is a cleaner and more consistent device experience in Home Assistant.
If you would like to support the project, you can do so through GitHub sponsors or Ko-fi. If you have any questions, you can ask them via the discussions, and if you encounter problems with the Home Assistant Glow, you can indicate this in the issues.
./Klaas
