Balcony power plant or PV system surplus
Not always, but every now and then - my balcony power plant delivers a surplus of electricity on sunny days. So that I don't give it away, I start the pool pump when there is a surplus and stop it again when there is no more surplus power available.
Trigger
Trigger | Description |
---|---|
When meter_power is below -200 for 20:00 |
meter_power reflects the data of the smart meter: negative values (-) mean a power surplus ID: surplus |
When meter_power is above 0 | meter_power = 0: no surplus |
Actions
Execute 'Switch PoolPump Switch on' if 'When triggered by surplus' otherwise 'Switch PoolPump Switch off'.
|
I use the smart meter's excess power entity (meter_power) as the trigger for turning on: once for turning on, once for turning off. When the meter_power entity provides a power surplus of more than 200 watts for 20 minutes (-200watts), the trigger fires and starts the pump in the actions. The 200 watts is approximately the power consumption of the pump. To allow the automation to react in the actions between no surplus and a surplus, the When query decides whether the pump should be switched on or off. The trigger "When meter_power is below -200 for 20:00" has the ID "Surplus" for this purpose, this can be used as a condition for the if-query. Thus, the threshold value for switching on (-200Watt) must be defined only once in the trigger and not additionally also in the if-query.
Automation as YAML
alias: Sureplus PoolPump
description: ""
trigger:
- platform: numeric_state
entity_id: sensor.meter_power
for:
hours: 0
minutes: 20
seconds: 0
below: -200
id: Sureplus
- platform: numeric_state
entity_id: sensor.meter_power
for:
hours: 0
minutes: 0
seconds: 0
above: 0
condition: []
action:
- if:
- condition: trigger
id:
- Sureplus
then:
- type: turn_on
device_id: ???
entity_id: switch.poolpump_switch
domain: switch
else:
- type: turn_off
device_id: ???
entity_id: switch.poolpump_switch
domain: switch
mode: single
{{percentage}} % positive