Peaqev ev-charging
Peaqev ev-charging is an attempt of charging an ev without breaching a preset monthly max-peak energy level. In order for this integration to function, you will need to have a sensor/device that reads your current power-draw with good resolution examples below. You will also have to disable any other smart-charging capability you may have, such as scheduled charging or energy-price-aware charging, the latter will come as parameter here in a future update.
This integration does not communicate with any properitary API's, everything is handled locally in your Home Assistant. However, the chargers selected will use the integrations set for them, and may include cloud polling of data.
While this integration will try to not break your monthly energy peak hour, there is off course no guarantee. Various factors beyond control of this logic do occur, so for those aiming at staying below their threshold, I do suggest you think about the non-hours, caution-hours etc in the setup. These hours should be set when you commonly utilize a lot of extra energy in your home, such as cooking, doing laundry etc.
Installation
Required to install is Home Assistant version 2022.4.5 or higher.
If you have HACS installed, you can add peaqev as a custom integration.
Otherwise you may:
- Copy
custom_components/peaqevfolder to<config_dir>/custom_components/peaqev/ - Restart Home assistant
- Go to Configuration > Devices & Services > Add integration
Config setup:
Search for peaqev in your integrations setup. Fill in the following parameters:
Power sensor- The already existing power sensor in your setup. This is required to get the reading to work. Examples of devices sending such data is Tibber Pulse/Watty, Shelly DIN-mounted devices or similar.Power sensor includes car- Check this option if the above sensor includes your car's power draw. The calutions will be altered accordinglyCity, or Grid owner company- Chose your city from the list. The characteristics differ in how peak hours are stored and measured. If you don't live in a supported location but just want to test the integration, or lower your peaks for other reasons, you may check "Other, just want to test"Charger type- Pick the installed ev-charger you have. Currently Chargeamps and Easee are supported. Check links for required custom components per charger-type: Chargeamps, Easee
Config options:
Non hours- Click to select the hours (if any) where you do not wish to charge.Caution hours- Click to select the hours (if any) where you want the charger to be extra cautious to not break the peak.Price aware charging- Check this to calculate the cheapest hours from Nordpool (requires Nordpool). Above Non- and Caution-hours will be ignored.Absolute top price- The limit (if any) where your charger should be stopped, regardless of the hour-algorithm.Monthly allowed peak- Needs to be set in order to determine a minimum allowed peak. In the beginning of each month this is necessary to be able to charge at all. Format is in kW. See examples belowCaution-hour type- Choose to what extent you would like Peaqev to hold back during caution-hours. Suave > Aggressive
These are two (quite restrained) examples of monthly start peaks, for 1-phase and 3-phase charging respectively. This option is always up to your house and it's other appliances. The below are made for a modern house with installed heat pump.
| Month | 1-phase charge | 3-phase charge |
|---|---|---|
| Jan | 2.0 | 4.0 |
| Feb | 1.8 | 3.6 |
| Mar | 1.8 | 3.6 |
| Apr | 1.5 | 3.0 |
| May | 1.5 | 3.0 |
| Jun | 1.5 | 3.0 |
| Jul | 1.5 | 3.0 |
| Aug | 1.5 | 3.0 |
| Sep | 1.5 | 3.0 |
| Oct | 1.5 | 3.0 |
| Nov | 1.8 | 3.6 |
| Dec | 2.0 | 4.0 |
| Locale | Characteristics |
|---|---|
| Gothenburg, Sweden | The average of three max peak hours from different days is what your are charged for. The algorithm tries to stay below the minimum value of these three peaks. |
| Partille, Sweden | Single monthly peak hour is what is being avoided by the algorithm |
| Nacka, Sweden (Normal tariffe) | The average of three max peak hours is what your are charged for. The algorithm tries to stay below the minimum value of these three peaks. |
| Sala, Sweden (SHE ab-customer) | The average of three max peak hours, that do occur Mon-Fri, between 07-19. Other hours are non-observed. |
| Skövde, Sweden | Single monthly max peak. Observed Nov-Mar, Mon-Fri between 06-22. Other hours are non-observed. |
| Karlstad, Sweden | single max peak |
| Kristinehamn, Sweden | for Nov-Mar, max peak during Mon-Fri 07-17. Other months, single max peak |
| Malung-Sälen, Sweden | Average of five peaks on different days. Peaks are calc between 07-19. Other hours are free-charge. |
| Other, just want to test | Single monthly peak hour is what is being avoided by the algorithm |
More cities will come in future updates
Usage
- To start and stop, I suggest you create automations that call the services
peaqev.enableandpeaqev.disable. - Make sure to not exclude the created sensors from your recorder, as this would conflict with the monthly peaks.
Example of basic automations to enable/disable the charging. Your states here may differ from the example which is a Chargeamps Halo:
- id: '111111'
alias: Peaq - Charge
trigger:
- platform: state
entity_id: sensor.your_chargersensor
from: Available
to: Connected
- service: peaqev.enable
data: {}
mode: single
- id: '222222'
alias: Peaq - Disconnected
trigger:
- platform: state
entity_id: sensor.your_chargersensor
to: Available
condition: []
action:
- service: peaqev.disable
data: {}
mode: single
Tested with Chargeamps Halo 11kw and Easee. Both setups with one single charger per household. Currently will not function where multiple chargers have been installed ,2022-04-23
4 Jan 17, 2022
2.5k Jan 18, 2022
48 Dec 24, 2021
3 Oct 25, 2021
578 Feb 09, 2022
12 Jan 09, 2022
2 Dec 19, 2021
15 Dec 28, 2021
8 Jan 20, 2022
485 Jan 27, 2022
6 Jul 24, 2021
1 Nov 26, 2021
22 Jan 20, 2022
12 Nov 14, 2021
3 Dec 22, 2021
5 Jan 24, 2022
3 Dec 27, 2021
429 Jan 23, 2022
1 Jan 13, 2022
1 Oct 28, 2021