---
title: "Powercalc"
description: "Powercalc is a Marketplace integration for Home Assistant. It has 14.6k installs sharing analytics, works locally and was last updated October 27, 2026."
canonical: "https://vulpo.app/integrations/marketplace/bramstroker-homeassistant-powercalc"
url: "https://vulpo.app/integrations/marketplace/bramstroker-homeassistant-powercalc.md"
last-updated: "2026-10-22"
version: "1.4"
---

# Powercalc

> Powercalc is a Marketplace integration for Home Assistant. It has 14.6k installs sharing analytics, works locally and was last updated October 27, 2026.

Powercalc is a custom integration that estimates power consumption for lights and other appliances without a smart plug. It creates virtual power sensors, with lights estimated from brightness, color and temperature, and fans from speed. Other devices can use a fixed power value, a daily energy value or measured profiles from a built-in library. It also adds energy, standby energy and cost sensors, utility meters, and group sensors that combine devices or rooms into one total. Cost can be based on a fixed price or a price sensor, with an optional surcharge and multiplier. Actions cover calibrating and resetting energy and cost sensors, running playbooks, and switching a profile's sub profile. It runs locally and is set up in the UI.

Automatic summary of the README and code of bramstroker/homeassistant-powercalc. 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=bramstroker&repository=homeassistant-powercalc&category=integration)

On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=bramstroker&repository=homeassistant-powercalc&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.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

### Assign to group

- **Select group(s)**
- **New group**: Fill in a custom group name to create a new group

### Availability entity

- **Availability entity**: When this entity is unavailable, the powercalc sensor will be unavailable as well

### Create a daily fixed sensor

- **Create utility meters**
- **Daily energy value**
- **Name**
- **On time**: When left empty defaults to 1 day. always on
- **Start time**
- **Unit of measurement**
- **Update frequency**: time in seconds between state updates of the sensor
- **Value**
- **Value template**

### Energy options

- **Integration method**
- **Unit prefix**
- **Filter outliers**: Enable filtering of outlier values in the energy sensor
- **Outlier filter max step**: Maximum expected step in power values (in watts) for the outlier filter

### Create a domain based group sensor

- **Name**
- **Create energy sensor**
- **Create cost sensor**
- **Create utility meters**
- **Entity domain**
- **Exclude entities**

### Fixed config

- **Power value**: Power value in Watts when the entity is ON

### Global configuration

- **Power sensor name pattern**
- **Power sensor friendly name pattern**
- **Power sensor category**
- **Power sensor precision**
- **Follow device name**: Use the assigned device name for generated entities of supported virtual power sensors configured in the UI. Entity IDs and custom entity names stay unchanged. Turning this off restores the configured names. Custom display-name patterns, including global patterns, take precedence: affected entries keep their configured names.
- **Create energy sensors**: Whether powercalc needs to create kWh sensors
- **Create cost sensors**: Whether powercalc needs to create cost sensors. Requires an energy price to be configured in the next steps
- **Create standby group**: Create group which sums all standby power consumption and self-usage of IOT devices
- **Create utility meters**: Let powercalc create utility meters, which cycle daily, hourly etc.
- **Enable anonymous analytics**: Allow Powercalc to send anonymous, aggregated usage statistics to help improve the integration
- **Ignore unavailable state**: Keep Powercalc sensors available, even when the source entity is unavailable
- **Include non powercalc sensors**: Control whether you want to include non powercalc sensors in groups
- **Disable extended attributes**: Disable all extra attributes powercalc adds to the power, energy and group entity states. This will help keep the database size small
- **Disable remote library download**: Disable the Powercalc library download feature

### Cost options

- **Fixed energy price**: A fixed price per kWh in your local currency
- **Energy price multiplier**: Multiplier applied after the surcharge. Use this for percentage-based taxes or fees, for example 1.21 for 21%
- **Energy price sensor**: A sensor which provides the current energy price per kWh (e.g. from a dynamic tariff integration). Leave the fixed price empty to use this sensor
- **Energy price surcharge**: Additional fixed amount per kWh added to the fixed price or price sensor value
- **Cost sensor friendly name pattern**: Pattern for the friendly name of the cost sensor. The source name is inserted at the placeholder position
- **Cost sensor name pattern**: Pattern used to build the cost sensor name and entity id. The source name is inserted at the placeholder position

### After setup

- **Calculation enabled condition**: The configured power calculation strategy will only be executed when this template evaluates to true or 1, otherwise the power sensor will display 0
- **Energy integration method**
- **Ignore unavailable state**: Toggle this setting when you want the power sensor to stay available even if the source entity is unavailable
- **Multiply factor**: Multiplies the calculated power by this ratio. Can be useful for light groups
- **Multiply factor standby**: Whether to also apply multiplication factor to standby power
- **Unavailable power**: Power in W to record when the source entity has an unavailable state
- **Create energy sensor**: Whether powercalc needs to create a kWh sensor
- **Create standby energy sensor**: Whether Powercalc should create a kWh sensor that tracks only standby consumption
- **Create cost sensor**
- **Create utility meters**: Let powercalc create utility meters, which cycle daily, hourly etc.
- **Source entity**: Entity the virtual power is based on, the power sensor will listen to state changes of this entity to be updated
- **Name**: Leaving blank will take the name from the source entity
- **Standby power**: Define the amount of power the device is consuming when in an OFF state
- **Daily energy value**
- **Name**
- **On time**: When left empty defaults to 1 day. always on
- **Start time**
- **Unit of measurement**
- **Update frequency**: time in seconds between state updates of the sensor
- **Value**
- **Value template**
- **Integration method**
- **Unit prefix**
- **Filter outliers**: Enable filtering of outlier values in the energy sensor
- **Outlier filter max step**: Maximum expected step in power values (in watts) for the outlier filter
- **Fixed value**
- **Self usage included**: Whether the power value includes the power consumed by the smart switch itself.
- **Power sensor name pattern**
- **Power sensor friendly name pattern**
- **Power sensor category**
- **Power sensor precision**
- **Follow device name**: Use the assigned device name for generated entities of supported virtual power sensors configured in the UI. Entity IDs and custom entity names stay unchanged. Turning this off restores the configured names. Custom display-name patterns, including global patterns, take precedence: affected entries keep their configured names.
- **Create energy sensors**: Whether powercalc needs to create kWh sensors
- **Create cost sensors**: Whether powercalc needs to create cost sensors. Requires an energy price to be configured in the next steps
- **Create standby group**: Create group which sums all standby power consumption and self-usage of IOT devices
- **Create utility meters**: Let powercalc create utility meters, which cycle daily, hourly etc.
- **Enable anonymous analytics**: Allow Powercalc to send anonymous, aggregated usage statistics to help improve the integration
- **Ignore unavailable state**: Keep Powercalc sensors available, even when the source entity is unavailable
- **Include non powercalc sensors**: Control whether you want to include non powercalc sensors in groups
- **Disable extended attributes**: Disable all extra attributes powercalc adds to the power, energy and group entity states. This will help keep the database size small
- **Disable remote library download**: Disable the Powercalc library download feature
- **Fixed energy price**: A fixed price per kWh in your local currency
- **Energy price multiplier**: Multiplier applied after the surcharge. Use this for percentage-based taxes or fees, for example 1.21 for 21%
- **Energy price sensor**: A sensor which provides the current energy price per kWh (e.g. from a dynamic tariff integration). Leave the fixed price empty to use this sensor
- **Energy price surcharge**: Additional fixed amount per kWh added to the fixed price or price sensor value
- **Cost sensor friendly name pattern**: Pattern for the friendly name of the cost sensor. The source name is inserted at the placeholder position
- **Cost sensor name pattern**: Pattern used to build the cost sensor name and entity id. The source name is inserted at the placeholder position
- **Apply to existing sensors**: Update every existing GUI powercalc sensor to match the new cost sensors setting

Texts from the code of [bramstroker/homeassistant-powercalc](https://github.com/bramstroker/homeassistant-powercalc).

## Entities

- **Sensors**: Measure session status, Power, Energy, Standby energy, Cost

## Actions

- **Activate playbook**: Start execution of a playbook.
  Fields: Playbook
- **Calibrate energy sensor**: Sets the energy sensor to a given kWh value.
  Fields: Value
- **Calibrate cost sensor**: Sets the cost sensor to a given monetary value.
  Fields: Value
- **Calibrate utility meter**: Calibrates a utility meter sensor.
  Fields: Value
- **Change GUI config**: Batch change configuration of all Powercalc config entries
  Fields: Value, Value
- **Debug group**: Get a debug overview of a group power or energy sensor including current member values.
- **Get active playbook**: Get current running playbook
- **Get group entities**: Retrieve all entity id's of a group energy or power sensor
- **Increase daily energy sensor**: Increases the sensor with a given amount.
  Fields: Value
- **Reload**: Reload Powercalc configuration and entities
- **Reset energy sensor**: Reset an energy sensor to zero kWh.
- **Reset cost sensor**: Reset a cost sensor to zero.
- **Stop playbook**: Stop currently active playbook.
- **Switch to another sub profile**: Some profiles in the library has different sub profiles. This service allows you to switch to another one.
  Fields: Sub profile

## Troubleshooting

- **Diagnostics**: Downloads a diagnostics file to attach to a bug report.
- **Repair notices**: Notices it can show in Settings, Repairs:
  Powercalc YAML configuration has moved, YAML configuration changed

## At a glance

- Kind: Marketplace integration
- Category: [Energy](https://vulpo.app/integrations/category/energy.md), Meters and monitoring
- Number: 14.6k installs sharing analytics; 1.6k GitHub stars
- Connection: Works locally
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: v1.26.1, last updated October 27, 2026
- Domain: `powercalc`
- Source: <https://github.com/bramstroker/homeassistant-powercalc>
- Issues: <https://github.com/bramstroker/homeassistant-powercalc/issues>

In Vulpo: Select card, 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/bramstroker-homeassistant-powercalc

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/bramstroker-homeassistant-powercalc
- 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
