About
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
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.
Assign to group
- Select group(s)
- New groupFill in a custom group name to create a new group
Availability entity
- Availability entityWhen 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 timeWhen left empty defaults to 1 day. always on
- Start time
- Unit of measurement
- Update frequencytime in seconds between state updates of the sensor
- Value
- Value template
Energy options
- Integration method
- Unit prefix
- Filter outliersEnable filtering of outlier values in the energy sensor
- Outlier filter max stepMaximum 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 valuePower 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 nameUse 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 sensorsWhether powercalc needs to create kWh sensors
- Create cost sensorsWhether powercalc needs to create cost sensors. Requires an energy price to be configured in the next steps
- Create standby groupCreate group which sums all standby power consumption and self-usage of IOT devices
- Create utility metersLet powercalc create utility meters, which cycle daily, hourly etc.
- Enable anonymous analyticsAllow Powercalc to send anonymous, aggregated usage statistics to help improve the integration
- Ignore unavailable stateKeep Powercalc sensors available, even when the source entity is unavailable
- Include non powercalc sensorsControl whether you want to include non powercalc sensors in groups
- Disable extended attributesDisable all extra attributes powercalc adds to the power, energy and group entity states. This will help keep the database size small
- Disable remote library downloadDisable the Powercalc library download feature
Cost options
- Fixed energy priceA fixed price per kWh in your local currency
- Energy price multiplierMultiplier applied after the surcharge. Use this for percentage-based taxes or fees, for example 1.21 for 21%
- Energy price sensorA 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 surchargeAdditional fixed amount per kWh added to the fixed price or price sensor value
- Cost sensor friendly name patternPattern for the friendly name of the cost sensor. The source name is inserted at the placeholder position
- Cost sensor name patternPattern used to build the cost sensor name and entity id. The source name is inserted at the placeholder position
After setup
- Calculation enabled conditionThe 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 stateToggle this setting when you want the power sensor to stay available even if the source entity is unavailable
- Multiply factorMultiplies the calculated power by this ratio. Can be useful for light groups
- Multiply factor standbyWhether to also apply multiplication factor to standby power
- Unavailable powerPower in W to record when the source entity has an unavailable state
- Create energy sensorWhether powercalc needs to create a kWh sensor
- Create standby energy sensorWhether Powercalc should create a kWh sensor that tracks only standby consumption
- Create cost sensor
- Create utility metersLet powercalc create utility meters, which cycle daily, hourly etc.
- Source entityEntity the virtual power is based on, the power sensor will listen to state changes of this entity to be updated
- NameLeaving blank will take the name from the source entity
- Standby powerDefine the amount of power the device is consuming when in an OFF state
- Daily energy value
- Name
- On timeWhen left empty defaults to 1 day. always on
- Start time
- Unit of measurement
- Update frequencytime in seconds between state updates of the sensor
- Value
- Value template
- Integration method
- Unit prefix
- Filter outliersEnable filtering of outlier values in the energy sensor
- Outlier filter max stepMaximum expected step in power values (in watts) for the outlier filter
- Fixed value
- Self usage includedWhether 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 nameUse 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 sensorsWhether powercalc needs to create kWh sensors
- Create cost sensorsWhether powercalc needs to create cost sensors. Requires an energy price to be configured in the next steps
- Create standby groupCreate group which sums all standby power consumption and self-usage of IOT devices
- Create utility metersLet powercalc create utility meters, which cycle daily, hourly etc.
- Enable anonymous analyticsAllow Powercalc to send anonymous, aggregated usage statistics to help improve the integration
- Ignore unavailable stateKeep Powercalc sensors available, even when the source entity is unavailable
- Include non powercalc sensorsControl whether you want to include non powercalc sensors in groups
- Disable extended attributesDisable all extra attributes powercalc adds to the power, energy and group entity states. This will help keep the database size small
- Disable remote library downloadDisable the Powercalc library download feature
- Fixed energy priceA fixed price per kWh in your local currency
- Energy price multiplierMultiplier applied after the surcharge. Use this for percentage-based taxes or fees, for example 1.21 for 21%
- Energy price sensorA 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 surchargeAdditional fixed amount per kWh added to the fixed price or price sensor value
- Cost sensor friendly name patternPattern for the friendly name of the cost sensor. The source name is inserted at the placeholder position
- Cost sensor name patternPattern used to build the cost sensor name and entity id. The source name is inserted at the placeholder position
- Apply to existing sensorsUpdate every existing GUI powercalc sensor to match the new cost sensors setting
Texts from the code of bramstroker/homeassistant-powercalc.
Entities
- SensorsMeasure session status, Power, Energy, Standby energy, Cost
Actions
- Activate playbookStart execution of a playbook.Fields: Playbook
- Calibrate energy sensorSets the energy sensor to a given kWh value.Fields: Value
- Calibrate cost sensorSets the cost sensor to a given monetary value.Fields: Value
- Calibrate utility meterCalibrates a utility meter sensor.Fields: Value
- Change GUI configBatch change configuration of all Powercalc config entriesFields: Value, Value
- Debug groupGet a debug overview of a group power or energy sensor including current member values.
- Get active playbookGet current running playbook
- Get group entitiesRetrieve all entity id's of a group energy or power sensor
- Increase daily energy sensorIncreases the sensor with a given amount.Fields: Value
- ReloadReload Powercalc configuration and entities
- Reset energy sensorReset an energy sensor to zero kWh.
- Reset cost sensorReset a cost sensor to zero.
- Stop playbookStop currently active playbook.
- Switch to another sub profileSome profiles in the library has different sub profiles. This service allows you to switch to another one.Fields: Sub profile
Troubleshooting
- DiagnosticsDownloads a diagnostics file to attach to a bug report.
- Repair noticesNotices it can show in Settings, Repairs:Powercalc YAML configuration has moved, YAML configuration changed
Shows in Vulpo
Select card, Chart card, Apple Watch.Information
- Installs
- 14.6k sharing analytics
- GitHub stars
- 1.6k
- Connection
- Works locally
- Upkeep
- Updated in the last 6 months
- Version
- v1.26.1,
- Category
- Energy, Meters and monitoring
- Kind
- Marketplace integration
- Needs
- Needs the Marketplace (HACS on 2026.10 and older)
- Domain
powercalc- Issues
- Report an issue












