Home Assistant custom component to help ev-chargers stay below peak hourly energy levels.

Overview

Validate with hassfest Peaq_downloads hass-peaq_downloads Buy me a coffee

Peaqev ev-charging

Peaq logo

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/peaqev folder 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 accordingly
  • City, 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 below
  • Caution-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.enable and peaqev.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

Comments
  • Peaq not adjusting Easee charger limit

    Peaq not adjusting Easee charger limit

    Eventually got Peaq installed but seems like its not able to control Easee dynamic charger limit. Peaq allowed current is adjusting, but not the charger. Charger is responding to manual service call: easee.set_charger_dynamic_limit

    Peaq

    bug 
    opened by rabakaas 32
  • Setup failes with error on energy sensor

    Setup failes with error on energy sensor

    I get different errors with different sensors, see log below. My asumption is that eithere the naming, or attributes on them do not match up. Or simply that i have miss judge what sensors that should be provided.

    image

    At setup it accepts my input and configuration steps. But then gives error that it cant be set up. Full log below with modified entity due to adress (for the Tibber Pulse) First i thought it was about that i have local production so some sensors goes negative, however tested during over consuption with same error.

    Let me know what data i can collect and what assistans i can give/help out with

    2022-04-19 10:16:08 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.total_power_total_mqtt for peaqev File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry File "/config/custom_components/peaqev/peaqservice/hub.py", line 105, in init File "/config/custom_components/peaqev/peaqservice/hub.py", line 133, in init_hub_values File "/config/custom_components/peaqev/peaqservice/util/hubmember.py", line 30, in value 2022-04-19 10:20:02 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.power_XXXadressXXX for peaqev File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry File "/config/custom_components/peaqev/peaqservice/hub.py", line 80, in init File "/config/custom_components/peaqev/config_flow.py", line 77, in async_step_user File "/config/custom_components/peaqev/config_flow.py", line 56, in validate_input_user File "/config/custom_components/peaqev/config_flow.py", line 38, in _check_power_sensor 2022-04-19 10:31:51 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.power_XXXadressXXX for peaqev File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry File "/config/custom_components/peaqev/peaqservice/hub.py", line 80, in init

    bug 
    opened by nsimb 11
  • Cant set up the Peaq in integration, still getting Aborted

    Cant set up the Peaq in integration, still getting Aborted

    closed the last ticket, after clean install, and trying to figure out what could be wrong with my setup. image

    Guessing it got somthing with how to with the additional of the Nordpool, since this started to hapen when the priceaware beta got released.

    Not really sure how to debugg or find the logs when it comes to custom integration setup throu gui. Let me know if its just my installation and what i can do.

    v0.5.3 core-2022.4.7 supervisor-2022.04.0 Home Assistant OS 7.6

    bug 
    opened by nsimb 8
  • trying to set up a HomeWizard energy sensor into peaq but not getting further then this ...

    trying to set up a HomeWizard energy sensor into peaq but not getting further then this ...

    2022-12-29 22:43:43.556 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.kwh_meter_3_phase_3c39e7253780_active_power for peaqev File "/config/custom_components/peaqev/init.py", line 58, in async_setup_entry File "/config/custom_components/peaqev/peaqservice/hub/hub.py", line 43, in init File "/config/custom_components/peaqev/peaqservice/chargertypes/chargertypes.py", line 26, in init File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months File "/config/custom_components/peaqev/config_flow.py", line 227, in async_step_hours File "/config/custom_components/peaqev/config_flow.py", line 262, in async_step_months 2022-12-29 22:47:34.743 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.kwh_meter_3_phase_3c39e7253780_active_power for peaqev File "/config/custom_components/peaqev/init.py", line 58, in async_setup_entry File "/config/custom_components/peaqev/peaqservice/hub/hub.py", line 43, in init File "/config/custom_components/peaqev/peaqservice/chargertypes/chargertypes.py", line 26, in init

    bug 
    opened by dsmagghe 4
  • Help with setup

    Help with setup

    Hello,

    Thanks for the addon, it sounds really useful!

    During the setup, I have added my glow sensor that measures power usage in real time along with my status of the Easee charger (sensor.carport_status - the one that says charging, ready_to_charge) as Charger id.

    When I enable the on the peaq charge nothing happens. Am I missing something?

    No nordpool pricing is selected or limited hours of operation. I am on version 2022.11.1 and 2.1.0 installed through HACS

    opened by kirilldem 4
  • get_average_kwh_price_core could not be calculated: division by zero

    get_average_kwh_price_core could not be calculated: division by zero

    Found this warning flooding my logs every 5 seconds. Known issue?

    This error originated from a custom integration.

    Logger: peaqevcore.services.hourselection.hoursselection Source: custom_components/peaqev/sensors/money_sensor.py:41 Integration: peaqev ev-charging (documentation, issues) First occurred: 07:03:40 (5542 occurrences) Last logged: 13:13:11

    get_average_kwh_price_core could not be calculated: division by zero

    bug 
    opened by rawrgit 3
  • Chargepoint ID

    Chargepoint ID

    I feel really stupid but i cant get it to work, my guess is that i give the wrong Chargepoint ID Tried all kind of stuff related to device and entitys

    Checked out the code to see what it could be related to and tested. Sadly no luck

    Easee charger, device is called 42 but i tried with different entitys aswell without luck I asume that the power sensor should the the full entity name and mesure in W since power. Have a few but so far no luck

    image

    bug 
    opened by nsimb 3
  • Overload (current) protection in PeaqEv

    Overload (current) protection in PeaqEv

    Discussed in https://github.com/elden1337/hass-peaq/discussions/170

    Originally posted by nidingen November 4, 2022 Hi, I currently have an AmpGuard load monitor in addition to my ChargeAmps Halo. It monitors the total power draw of my house (through measurement of current and voltage) and modulates the Halo if the total power draw risks exceeding the limit (25A in my case). I think this function should be possible to include in PeaqEv as well if data sampling is fast enough by the load moniotor. A margin could be included as a user set parameter.

    I think that in most cases the power peak limiting algorithm or the smart charging algorithm would modulate the wall charger (downwards) before risking exceeding the limit, but just in case it would be nice to have.

    It would solve the problem of not being able to current control the ChargeAmps Halo, i.e. using PeaqEv, when the load monitor AmpGuard is installed without function loss when disconnecting the AmpGuard and using it to supply Home Assistant instead of the ChargeAmps cloud.

    feature 
    opened by elden1337 2
  • Unable to load hass-peaq

    Unable to load hass-peaq

    I have added the integration through HACS, restarted HA and can find the integration in the normal HA integration add, but get an error trying to load it: This integration does not support configuration via the UI. If you followed this link from the Home Assistant website, make sure you run the latest version of Home Assistant.

    Here are the relevant parts of the log:

    2022-10-08 18:28:05.584 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.peaqev.config_flow
    Traceback (most recent call last):
      File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 681, in get_platform
        cache[full_name] = self._import_platform(platform_name)
      File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 698, in _import_platform
        return importlib.import_module(f"{self.pkg_path}.{platform_name}")
      File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
        return _bootstrap._gcd_import(name[level:], package, level)
      File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
      File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
      File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
      File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
      File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
      File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
      File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
      File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
      File "<frozen importlib._bootstrap_external>", line 790, in exec_module
      File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
      File "/home/homeassistant/.homeassistant/custom_components/peaqev/__init__.py", line 10, in <module>
        from custom_components.peaqev.peaqservice.hub.hub import HomeAssistantHub
      File "/home/homeassistant/.homeassistant/custom_components/peaqev/peaqservice/hub/hub.py", line 10, in <module>
        from peaqevcore.hub.hub import Hub
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/hub/hub.py", line 1, in <module>
        from ..services.hourselection.hourselectionfactory import HourselectionFactory
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/hourselectionfactory.py", line 1, in <module>
        from .price_aware_hours import PriceAwareHours
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/price_aware_hours.py", line 3, in <module>
        from .hoursselection import Hoursselection as core_hours
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/hoursselection.py", line 153
        match listtype:
              ^
    SyntaxError: invalid syntax
    2022-10-08 18:28:05.591 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration peaqev: Exception importing custom_components.peaqev.config_flow
    2022-10-08 18:30:21.713 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.peaqev.config_flow
    Traceback (most recent call last):
      File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 681, in get_platform
        cache[full_name] = self._import_platform(platform_name)
      File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 698, in _import_platform
        return importlib.import_module(f"{self.pkg_path}.{platform_name}")
      File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
        return _bootstrap._gcd_import(name[level:], package, level)
      File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
      File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
      File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
      File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
      File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
      File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
      File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
      File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
      File "<frozen importlib._bootstrap_external>", line 790, in exec_module
      File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
      File "/home/homeassistant/.homeassistant/custom_components/peaqev/__init__.py", line 10, in <module>
        from custom_components.peaqev.peaqservice.hub.hub import HomeAssistantHub
      File "/home/homeassistant/.homeassistant/custom_components/peaqev/peaqservice/hub/hub.py", line 10, in <module>
        from peaqevcore.hub.hub import Hub
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/hub/hub.py", line 1, in <module>
        from ..services.hourselection.hourselectionfactory import HourselectionFactory
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/hourselectionfactory.py", line 1, in <module>
        from .price_aware_hours import PriceAwareHours
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/price_aware_hours.py", line 3, in <module>
        from .hoursselection import Hoursselection as core_hours
      File "/srv/homeassistant/lib/python3.9/site-packages/peaqevcore/services/hourselection/hoursselection.py", line 153
        match listtype:
              ^
    SyntaxError: invalid syntax
    2022-10-08 18:30:21.727 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration peaqev: Exception importing custom_components.peaqev.config_flow
    
    opened by anoteng 2
  • switch.peaqev_charger_enabled turns off when HA is restarted

    switch.peaqev_charger_enabled turns off when HA is restarted

    switch.peaqev_charger_enabled seems to turn off after restarting Home Assistant.

    The logs show these warnings:

    2022-10-07 07:45:46.897 WARNING (MainThread) [peaqevcore.models.hub.chargerobject] Chargerobject-state not found in given state-list. Value was: None
    2022-10-07 07:45:46.900 WARNING (MainThread) [peaqevcore.models.hub.chargerswitch] Chargerobject state was None while getting current. Updatecurrent will still process but you may see a missmatch in frontend.
    2022-10-07 07:45:46.991 WARNING (MainThread) [custom_components.peaqev.peaqservice.hub.hub] ['hours', 'chargerobject_switch', 'chargerobject'] has not initialized yet.
    2022-10-07 07:45:47.168 WARNING (MainThread) [custom_components.peaqev.peaqservice.hub.hub] ['chargerobject_switch', 'chargerobject'] has not initialized yet.
    

    After these messages switch.peaqev_charger_enabled is unknown for about 45 seconds before it is off (it was on) until the time of the warnings above.

    bug 
    opened by uphillbattle 2
  • Unable to setup integration; cannot import name 'PredictionBase'

    Unable to setup integration; cannot import name 'PredictionBase'

    When trying to setup the integration the following exception is thrown at console

    hast_1          | 2022-08-12 11:24:36 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration peaqev: cannot import name 'PredictionBase' from 'peaqevcore.services.prediction.prediction' (/usr/local/lib/python3.10/site-packages/peaqevcore/services/prediction/prediction.py)
    

    hass-peaq: 1.6.1 hass: 2022.7.7

    Should this be Prediction @ https://github.com/elden1337/peaqev-core/blob/main/Peaqevcore/services/prediction/prediction.py#L7 and https://github.com/elden1337/hass-peaq/blob/main/custom_components/peaqev/peaqservice/prediction/prediction.py#L3?

    bug 
    opened by jkaberg 2
  • Integration is using deprecated `DEVICE_CLASS_*` constants

    Integration is using deprecated `DEVICE_CLASS_*` constants

    This custom integration uses deprecated DEVICE_CLASS_* constants in its codebase.

    The DEVICE_CLASS_* constants have been deprecated and replaced in Home Assistant Core 2021.12 (over a year ago). I would highly suggest updating/migrating this integration to the new enums.

    For example, for the device classes supported by the sensor platform, there is now a SensorDeviceClass enum. So if a sensor previously used the DEVICE_CLASS_ENERGY constant, it should now use SensorDeviceClass.ENERGY. Other platforms (like binary_sensor, and number) provide similar enumerations for their supported device classes.

    The migration thus only consists of replacing constants with an enumeration member and is, therefore, very low impact and should be fairly straightforward.

    If I can help resolve any questions regarding this change or migration, feel free to ask or respond to this issue. I'm happy to help!

    Kindest regards,

    ../Frenck

    task maintenance 
    opened by frenck 1
  • Wait for cheaper hours with time-diffed tariffe

    Wait for cheaper hours with time-diffed tariffe

    When a peak-tariffe has cheaper hours between certain hours (or days), consider awaiting those hours like we are doing with elprice. This would lower the cost of the peak-charging for consumers.

    Also, logic must be added in core to accommodate different levels of peak within different hours.

    feature 
    opened by elden1337 0
  • Handle duplicate scheduler-periods

    Handle duplicate scheduler-periods

    When trying to create a secondary scheduler-period that overlaps an existing one This check is after the create-scheduler call If there is a conflict, log and send HA-notification, don't override the existing schedule

    task 
    opened by elden1337 0
Releases(v2.5.1)
  • v2.5.1(Dec 30, 2022)

  • v2.5.0(Dec 20, 2022)

    Downloads for this release

    :santa: 🤶🏼 Two changes introduced in this release, to allow for faster charging when necessary, and to try and protect your main fuses if possible. Happy holidays!

    Power Canary (#179): 🐦

    Power canary is a software alarm function to let peaqev know when it's time to stop charging or lower the amps to not break the main fuses. This is by no means a hardware fuse-protection device, but rather an attempt of not letting peaqev push charging to levels too close to the main fuses. The functionality should be similar, but for legal reasons I will not call it an amp-guard or fuse-protector.

    • Remember, peaqev communicates with your charger through apis. Therefore there are delays.
    • Peaqev cannot know your true fuse-limitations and thus, this feature is purely for alarming, not safe-guarding your fuses against physical failure.
    • There is no phase-balancing included in this at all, it's just the total power measured.

    Function:

    The power canary will, if enabled only allow amp-adjustments that do not risk breaching the limitations you set. If an anomaly is detected it will try to lower the amps of your charger, and if nothing else works, turn it off. You have a new device and sensors for the power-canary available.

    Due to the delays in API-communication, the threshold is at 90% of the basic 3-phase calculation of your fuses.

    Enable it through the integration-options where you choose your set fuses. If you miss yours, please open a PR or add an issue requesting that type to be added. When picked, Power Canary is always on and cannot be disabled. The only way to disable it is to go back to options and choose "Not set"

    Dynamic amp-list (#183):

    Allow amps 16-32 if available on your charger. Currently we can only detect this from Easee. You should now see a new attribute "Allowed current-list" on the sensor sensor.peaqev_allowed_current. When you are not charging, the attribute "Peaqev phase-setting" should return "unkown" and you should see 6-16. But when you are charging, if your chargertype has been able to push a higher than 16 max-amps you should see a different list of amps there. The handling of what amps to use is still the same automation as before, just that it occasionally could go above 16A now.

    🎄 🎄 🎄 🎄 🎄 🎄 🎄 🎄 🎄 🎄 🎄

    Changes:

    • #179 - Overload (current) protection in PeaqEv
    • #183 - Allow dynamic amp-list based on Easee max-amp sensor

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(51.00 KB)
  • v2.5.0-beta.2(Dec 16, 2022)

    Downloads for this release

    Update from previous beta:

    • Fixed bad amp-increase if power canary is set.

    Two changes introduced in this release, to allow for faster charging when necessary, and to try and protect your main fuses if possible:

    Power Canary (#179):

    Power canary is a software alarm function to let peaqev know when it's time to stop charging or lower the amps to not break the main fuses. This is by no means a hardware fuse-protection device, but rather an attempt of not letting peaqev push charging to levels too close to the main fuses.

    Remember, peaqev communicates with your charger through apis. Therefore there are delays. The authors of peaqev cannot know your fuse-limitations and thus, this feature is purely for alarming, not safe-guarding your fuses against physical failure.

    Function:

    The power canary will, if enabled only allow amp-adjustments that do not risk breaching the limitations you set. If an anomaly is detected it will try to lower the amps of your charger, and if nothing else works, turn it off. You have a new device and sensors for the power-canary available.

    Dynamic amp-list (#183):

    The idea is to allow amps 16-32 is available on your charger. Currently we can only detect this from easee. You should now see a new attribute "Allowed current-list" on the sensor sensor.peaqev_allowed_current. When you are not charging, the attribute "Peaqev phase-setting" should return "unkown" and you should 4-16. But when you are charging, if your chargertype has been able to push a higher than 16 max-amps you should see a different list of amps there.

    Changes:

    • #179 - Overload (current) protection in PeaqEv
    • #183 - Allow dynamic amp-list based on Easee max-amp sensor

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(51.01 KB)
  • v2.5.0-beta(Dec 15, 2022)

    Downloads for this release

    Two changes introduced in this release, to allow for faster charging when necessary, and to try and protect your main fuses if possible:

    Power Canary (#179):

    Power canary is a software alarm function to let peaqev know when it's time to stop charging or lower the amps to not break the main fuses. This is by no means a hardware fuse-protection device, but rather an attempt of not letting peaqev push charging to levels too close to the main fuses.

    Remember, peaqev communicates with your charger through apis. Therefore there are delays. The authors of peaqev cannot know your fuse-limitations and thus, this feature is purely for alarming, not safe-guarding your fuses against physical failure.

    Function:

    The power canary will, if enabled only allow amp-adjustments that do not risk breaching the limitations you set. If an anomaly is detected it will try to lower the amps of your charger, and if nothing else works, turn it off. You have a new device and sensors for the power-canary available.

    Dynamic amp-list (#183):

    The idea is to allow amps 16-32 is available on your charger. Currently we can only detect this from easee. You should now see a new attribute "Allowed current-list" on the sensor sensor.peaqev_allowed_current. When you are not charging, the attribute "Peaqev phase-setting" should return "unkown" and you should 4-16. But when you are charging, if your chargertype has been able to push a higher than 16 max-amps you should see a different list of amps there.

    Changes:

    • #179 - Overload (current) protection in PeaqEv
    • #183 - Allow dynamic amp-list based on Easee max-amp sensor

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(50.99 KB)
  • v2.4.0(Dec 5, 2022)

    Downloads for this release

    Zaptec charger has been added. Consider this an early beta. I have no possibility of testing out this charger myself, and thus need your help.

    If you are a Zaptec-owner and want to use Peaqev, please install and see how far you get in the setup and hopefully also in the charging (it might not even let you install though). Create issues for obvious bugs, or contact through the Discord-server or discussions on Github for brainstorming etc. At the moment the Zaptec-integration can only start/stop/pause/resume, not update amps. It is therefore suggested that you lock your amps on a lower setting before starting to use Peaqev to not stress the charger by turning on/off all the time.

    When this PR is merged we can add amp-update capabilities as well. Thanks to @gustafssone for helping out with the conception of this chargertype!

    Changes:

    • #33 - Zaptec

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(45.26 KB)
  • v2.3.1(Dec 2, 2022)

    Downloads for this release

    Update for Swedish users only:

    Svenska kraftnät (svk) has announce the critical peak hours for this winter when they desire the Swedish users to lower their consumption. As a peaqev-user in Sweden you will automatically contribute by stopping charging during peak hours. The hours are Mon-Fri 8,9,10 and 16,17,18 from Now until 31st of March 2023.

    I hope all users feel the need to lower consumption during these hours. Should you completely disagree you may disable peaqev and charge regularly during these hours.

    https://www.svk.se/press-och-nyheter/nyheter/allmanna-nyheter/2022/timmarna-dar-forbrukningen-ar-hogst-i-vinter/


    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(43.65 KB)
  • v2.3.0(Nov 28, 2022)

    Downloads for this release

    This version brings a better calculation for the interim-days (the fake day in Peaqev from 14:00 - 13:00 to take advantage of the nightly averages), as well as an attempt of improving the overall average price for hours:

    It will take a week from installing before it starts using the averge (needs seven running days), and in many cases you will not see any difference from now in terms of non-hours. But sometimes you will, and I mean that this calculation is more sane. Example is a very expensive week with a cheap Sunday. With the improved calculation more hours on the Sunday would be allowed than the legacy calculation.

    The data used can be viewed as new attributes on sensor.peaqev_hour_controller.

    The algorithm in peaqev to determine eligible hours is far more complex than a simple average, so this solution can be hard to understand, but the idea is to give more hours when cheaper than it used to be, and less when it's more expensive.

    Changes:

    • #177 - Add average-nordpool-pricing sensor
    • elden1337/peaqev-core#62 - Improve price-calculation for interim-days
    • elden1337/peaqev-core#54 - Create running average price
    • elden1337/peaqev-core#63 - Rebuild hourselectionservice

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(42.86 KB)
  • v2.3.0-beta(Nov 22, 2022)

    Downloads for this release

    This version brings a better calculation for the interim-days (the fake day in Peaqev from 14:00 - 13:00 to take advantage of the nightly averages), as well as an attempt of improving the overall average price for hours:

    It will take a week from installing before it starts using the averge (needs seven running days), and in many cases you will not see any difference from now in terms of non-hours. But sometimes you will, and I mean that this calculation is more sane. Example is a very expensive week with a cheap Sunday. With the improved calculation more hours on the Sunday would be allowed than the legacy calculation.

    The data used can be viewed as new attributes on sensor.peaqev_hour_controller.

    The algorithm in peaqev to determine eligable hours is far more complex than a simple average, so this solution can be hard to understand, but the idea is to give more hours when cheaper than it used to be, and less when it's more expensive.

    Changes:

    • #177 - Add average-nordpool-pricing sensor
    • elden1337/peaqev-core#62 - Improve price-calculation for interim-days
    • elden1337/peaqev-core#54 - Create running average price

    :notebook_with_decorative_cover: First time here? Do check the getting-started wiki for the most common questions

    :speech_balloon: Join my Discord-server to interact with other peaq-users.

    :1st_place_medal: Has Peaqev helped you save money? Sponsoring me on Github, PayPal or BuyMeACoffee would be much appreciated.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(42.86 KB)
  • v2.2.1(Nov 11, 2022)

    Downloads for this release

    Minor hotfix release

    Our Discord-server is now online. Come join the community if you want to talk to other peaq-users or having issues you need to share.

    Bugfixes:

    • elden1337/peaqev-core#60 - Min price is not taken into account
    • elden1337/peaqev-core#61 - Session stats reset after ha-reboot Under testing, not finalized
    • #175 - Session energy stats calc-errors Under testing, not finalized

    First time here? Do check the getting-started wiki for the most common questions

    :cherries: Has Peaqev helped you save money? If so, please consider sponsoring me on Github, PayPal or BuyMeACoffee.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(42.29 KB)
  • v2.2.0(Nov 9, 2022)

    Downloads for this release

    Changes

    • #163 - Terminate charger if powersensor goes missing
    • #167 - Retain state of switch peaq_enabled after reboot this means that the options-setting of "turn peaq on by default" is now gone. The switch will now be in the same state as you left it before reboot, much easier.

    New locales

    • elden1337/peaqev-core#58 Eskilstuna elnät, Sweden
    • elden1337/peaqev-core#59 Tekniska verken Linköping, Sweden

    Bugfixes:

    • #164 - Remove core logs from session statistics
    • #165 - Make sure repeated logs only log once
    • #166 - Charger does not call charger off in 2.1.0
    • #173 - Make sure non price aware works in > 2.0

    First time here? Do check the getting-started wiki for the most common questions

    :cherries: Has Peaqev helped you save money? If so, please consider sponsoring me on Github, PayPal or BuyMeACoffee.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(42.29 KB)
  • v2.2.0-beta.2(Nov 6, 2022)

    Downloads for this release

    Beta 2 adds a better setup for overtaking the charger, it will now only do it if peaqev is enabled with the switch. It also adds a smaller fix to #163 that made the killswitch warn you on booting home assistant (without any need for it)

    Changes

    • #163 - Terminate charger if powersensor goes missing
    • #167 - Retain state of switch peaq_enabled after reboot

    New locales

    • elden1337/peaqev-core#58 Eskilstuna elnät, Sweden
    • elden1337/peaqev-core#59 Tekniska verken Linköping, Sweden

    Bugfixes:

    • #164 - Remove core logs from session statistics
    • #165 - Make sure repeated logs only log once
    • #166 - Charger does not call charger off in 2.1.0
    • #173 - Make sure non price aware works in > 2.0

    First time here? Do check the getting-started wiki for the most common questions

    :cherries: Has Peaqev helped you save money? If so, please consider sponsoring me on Github, PayPal or BuyMeACoffee.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(42.30 KB)
  • v2.1.0(Nov 2, 2022)

    Downloads for this release

    Time for a mixed release. The main caveat with this one is that if you are an easee-user, you must update that repo to 0.9.46 or greater before installing this version of peaqev. You may also notice that the binary sensor for peaqenabled is now removed. It will not show up again so you may delete it from your HA, update all possible automations or scripts to use the switch switch.peaqev_charger_enabled instead (it always had the same state as that sensor anyway) Other tickets like #157 is more of a preparation. It might not feel that useful at the moment but it is in preparation of the larger #129 Scheduler 2.0 that I'm working on for later.

    That's it for now. Enjoy! (and report issues as they occur plz ;))

    Changes

    • #155 - Update easee.py to accommodate new service-calls. (Note: in order to use this release you must first upgrade Easee to v0.9.46)
    • #150 - Allow peaqev to turn off charger at all times when being enabled
    • #158 - Remove binary sensor for peaqenabled (Update your automations if needed!)
    • #142 - Override service should also override caution hour
    • #157 - Store session statistics on session sensor - part of larger feature so just in preparation of that

    :cherries: Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(41.96 KB)
  • v2.0.1(Oct 12, 2022)

  • v2.0.0(Oct 11, 2022)

    Downloads for this release

    Changes

    Breaking change

    the top-up funcionality has been retired. It didn't work as expected, and the newly released interim-day functionality is both cheaper on average and more stable and understandable.

    • #151 Enable three-phase charging. Changes have been made that should hopefully make the automatic detection of three-phase vs one-phase more stable. As per usual, report any issues

    New locales

    • "No peak shaving needed" - A new option to use Peaqev without any peak-shaving included. This option is for those wanting to use the pricing features etc, but who aren't charged for peak energy.
    • "Asker Nett, Norway" - by @kevinsch95 :beers:

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(41.48 KB)
  • v1.10.1(Oct 1, 2022)

    Downloads for this release

    Changes

    The new interim-day calculation added in latest 1.10.0 was faulty in two ways:

    • Min and Max-prices were ignored in the interim-calculation. Fixed.
    • The average was done backwards which caused wrong hours to be set as available/nonhours in certain conditions. Sorry about that ;).

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(41.58 KB)
  • v1.10.0(Sep 29, 2022)

    Downloads for this release

    Changes

    • In order to get a better best-price match peaqev is now calculating non-hours as an interim-day from 13h - 12h (when tomorrow's prices come in). This will sometimes affect the hours during the afternoon > evening > night > morning with shifting them to lower levels. In testing this has proven to lower the per kwh-average price. Be sure to give feedback on this as it is a core-component change and not a user-option.

    • General bugfixes

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(41.58 KB)
  • v1.9.3(Sep 8, 2022)

  • v1.9.2(Sep 7, 2022)

    Downloads for this release

    Changes

    • Stability fixes to not allow interim amp-updates when charger is about to stop
    • General stability and refactor

    Tip

    If you are using the scheduler, and awaiting the scheduler 2.0 (which will come, but it takes time), you may use an automation like this example to trigger your daily charge at the lowest hours possible (I should hope, report bugs if you find them). Since Peaqev doesn't know the SoC of a connected car, this is the way to let the system know how much you desire until a set time:

    alias: Peaqev - Create weekday scheduler
    description: "Set peaqev scheduler at 17 sun-thu, for departure at 0700 next day"
    trigger:
      - platform: time
        at: "17:00:00"
    condition:
      - condition: template
        value_template: "{{now().weekday() == 0 or now().weekday() < 4}}"
    action:
      - service: peaqev.scheduler_set
        data:
          charge_amount: 4
          departure_time: "{{(as_timestamp(now()) +50400)|timestamp_custom('%y-%m-%d %H:%M')}}"
    mode: single
    

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(41.45 KB)
  • v1.9.0(Aug 30, 2022)

    Downloads for this release

    There's a new chargertype in town!

    In order to help a broader crowd, I've started to implement support for smart plug/outlet as chargertype. This type requires a connected plug which can report power-usage and has an on/off switch. Both are added in the config-flow if you choose that type as charger.

    A few important things to note:

    1. Peaqev cannot control which outlet you use for this. Make sure to use a secure, outdoors compatible and reliable one, fit for more power than you intend to charge with
    2. Set your travel-charger to the lowest possible amps before connecting (peaqev obviously cannot update the amps for this chargertype, so in order to stay below peaks and charge when elprice is lowest, go as low as you can)
    3. You utilize all things here at your own risk. So once again, be sure to pick a secure outlet

    This type is considered beta, some initial function tests have been carried out, but it might not even start for you. Please report issues in the issues-section as you find them, and we'll try to make this one possible together.

    Changes

    • #144 - Smartplug chargertype
    • Misc fixes to hourselection to hopefully stabilize updates from Nordpool

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(39.92 KB)
  • v1.8.0(Aug 25, 2022)

    Downloads for this release

    Main point of this release is a large restructure where more things have been moved to the core-repo. This will increase the testability for the project and will hopefully bring a more stable release-cycle going forward. I have also made an effort to create a better calculation of the hourselection, scheduler (still funky so use with caution or help me out) and top-up functions as well as tried to fix a few reported and non-reported bugs.

    All in all it's a large release but without a lot of new stuff this time around. Make sure to report errors as soon as possible.

    Changes

    • #138 (hope this works now, we'll see in a few days)
    • #140
    • #141
    • elden1337/peaqev-core#53

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(38.02 KB)
  • v1.7.0(Aug 12, 2022)

    I Want to hear from you

    Peaqev community is growing, and I really want to hear your thoughts and ideas. Hit me up with issues, discussions or on twitter @elden1337

    Downloads for this release

    Changes

    • New sensors peaqev.session_energy and peaqev.session_cost
    • Structural changes between the HA-repo and Core-repo
    • General bug-fixes

    Since this is a larger release (for backend) and time to test has been scarce, please report any issues as soon as possible.

    Has Peaqev helped you save money? If so, please consider buying me a coffee or becoming a Github-sponsor. Every bit helps and is much appreciated!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(51.62 KB)
  • v1.6.1(Jul 29, 2022)

  • v1.6.0(Jul 27, 2022)

    Downloads for this release

    Changes

    • #135 Better disctinction between 1-phase and 3-phase charging detection
    • elden1337/peaqev-core#47 Tests implemented for Scheduler and Session
    • elden1337/peaqev-core#46 Scheduler auto-cancelation on certain events
    • Improvements to negative consumptions (in particular when using solar panels)
    • General stability improvements and logical re-structure to hourselection, top-up and scheduler

    New Locales:

    • elden1337/peaqev-core#43 Telge Energi (Sweden)
    • elden1337/peaqev-core#42 Mälarenergi (Sweden)
    • elden1337/peaqev-core#41 Mellom (Norway)
    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(51.40 KB)
  • v1.5.0(Jul 16, 2022)

  • v1.4.0(Jul 9, 2022)

    Downloads for this release

    Changes

    • #66

    Scheduler is now added as service-call. If set, the scheduler will create a plan for charging at the very lowest hours available til the set departure-time.

    Schedule is created through service-call:

    service: peaqev.scheduler_set
    data: {
      charge_amount: 9
      departure_time: '22-07-08 12:00'
    }
    

    the datetime inputs must be the format provided here. IE yy-mm-dd hh:mm You may add a parameter for schedule_starttime should you wish to pre-set a future schedule. If you do not provide this parameter, the starttime is at the time of the service-call. Your departure-time must of course be after the start-time.

    charge_amount is in kWh override_settings is a dormant setting which currently is always false. In future releases this bool-setting will allow you to override the min/max prices and also possibly the set peak.

    To cancel a schedule before it is ended (it will auto-cancel on completion) you may call peaqev.scheduler_cancel. No parameters needed there.

    This feature can be used to help Peaqev get you the very cheapest charging-hours. It is currently the cheapest way of charging we can offer, but is still of course combined with the peak-avoidance algorithm. The scheduler will also constantly re-evaluate itself, for instance if you override the hours meanwhile, or the projected charge is greater or smaller than the scheduler initally thought (it will calculate based on your peak and a new running 24h-average consumption). Therefore you may see that the non-hours shift during a schedule.

    Future updates will include possibilities to add multiple and re-occurring schedules.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(50.65 KB)
  • v1.3.0(Jul 2, 2022)

    Downloads for this release

    Changes

    Bugfixes:

    • #125
    • General fixes to the override nonhours-servicecall, which now works without parameters (adds one hour per call)

    Feature:

    • #127 - Setting to let Peaqev be enabled after reboot. You will find this setting in the integration-options.

    Maintenance:

    • #119 Moved Chargertypes-logic to peaqev-core
    • elden1337/peaqev-core#33
    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(48.51 KB)
  • v1.2.1(Jun 23, 2022)

    Downloads for this release

    Changes

    • #124 "Servicecall for price-override"

    This new servicecall is called peaqev.override_nonhours. It takes an int-parameter hours. In this release you will have to call with parameters. Later I'll fix a default setting. What happens when calling this is that non-hours, either blocked by smart-pricing or by yourself in the config, are overriden til the timer has passed.

    If you are using price-awareness you will see the remainder of the override on your sensor sensor.peaqev_hour_controller as "Nonhours ignored until 13:48"

    Note: this setting does not survive rebooting, so if you reboot, the override is disabled again.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(49.73 KB)
  • v1.1.1(Jun 22, 2022)

    Downloads for this release

    Bugfixes:

    #116 Pause on chargeamps will not resume #123 Make sure peaq doesn't stop charger when disabled elden1337/peaqev-core#30 Top-up allows hours that are over the price-limit elden1337/peaqev-core#28 Hourselection calculates hours for tomorrow despite lacking prices

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(48.72 KB)
  • v1.1.0(Jun 20, 2022)

    Downloads for this release

    Highly recommended update if you are using the price-awareness in Peaqev

    Features:

    #114 - Top-up is now a setting in your config. It's sitting on the same page as price-awareness.

    Bugfixes:

    elden1337/peaqev-core#25 errors in calculation for top-up.

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(48.52 KB)
  • v1.0.0(Jun 19, 2022)

    Downloads for this release

    We cannot rely on the sql-sensors to work. You as users are using different sql-installations in HA, and we've already noticed one major hickup after HA-releases of the sensor type. There is also a business driven decision for this. With this change, Peaq can provide it's locales to other applications than Home Assistant. The logic now resides in the pypi-package.

    Breaking change:

    Your currently set peak-sensor(s) (depending on your locale) will stop to work. You may remove those sensors after installing this version. The new sensor is called sensor.peaqev_peak, and is a single sensor regardless (the secondary sensor for those locales that need it is now an attribute on this sensor).

    Please note that your peak will be reset when installing this, the current month will be reverted to it's base-state (what you chose when installing peak) and go from there. If you do not wish for this, please wait with installing til the end of a month. You must include this sensor (sensor.peaqev_peak) in your recorder for this to work.

    Stories for this epic:

    • #81
    • #111

    Other Features:

    • elden1337/peaqev-core#25 Allow for "top-up" today if expensive tomorrow This feature will alter the hourselection (if you are using price aware charging) to allow for a top-up either today, or tomorrow. The terms for this feature to kick in is that the day ahead prices on average must be larger than the max for the rest of today, or vice versa. This is an attempt of looking ahead and not just do price-logic per isolated calendar date. There is currently no setting for this, I want to try it as a standard feature. Should the request come in, I might add a switch for it in the future. This change will mean that the scheduled stops can be overriden when tomorrow's prices come in.

    • QA on Easee: Easee finally seems to be working. QA has been testing out along side my changes and I now have reports from many that it is starting/stopping and updating max current as it should. needless to say, any new bugs should be reported

      • #68
      • #106
      • #107
      • #112

    A big thanks to @mejje and @reinestenberg for helping out with qa for this release!

    Source code(tar.gz)
    Source code(zip)
    peaqev.zip(48.37 KB)
Owner
Magnus Eldén
Magnus Eldén
Custom component for Home Assistant that integrates Candy/Haier Wi-Fi washing machines (also known as Simply-Fi).

Candy Home Assistant component Custom component for Home Assistant that integrates Candy/Haier Wi-Fi washing machines (also known as Simply-Fi). This

Olivér Falvai 61 Dec 29, 2022
SALUS THERMOSTAT Custom component for Home-Assistant

Home-Assistant Custom Components Custom Components for Home-Assistant (http://www.home-assistant.io) Salus Thermostat Climate Component My device is R

null 21 Dec 18, 2022
Windhager myComfort custom component for Home Assistant

Windhager myComfort custom component for Home Assistant

null 5 Apr 27, 2022
Custom component for MPC-HC for home-assistant

mpc_hc The current mpchc integration in homeassistant violates ADR0004, so it will be deleted from core. This is just the existing integration copied

null 3 Dec 15, 2022
This Home Assistant custom component adds support for controlling Midea dehumidiferes on local network.

This is a custom component for Home assistant that adds support for Midea dehumidifier appliances via the local area network. midea-dehumidifier-lan H

Nenad Bogojevic 97 Jan 8, 2023
Resmed_myair_sensors - This is a Home Assistant custom component to pull daily CPAP data from ResMed's myAir service using an undocumented API

resmed_myair This component will set up the following platforms. Platform Description sensor Show info from the myAir API. Installation Using the tool

Preston Tamkin 17 Dec 29, 2022
Historic weather - Home Assistant custom component for accessing historic weather data

Historic Weather for Home Assistant (CC) 2022 by Andreas Frisch github@fraxinas.

Andreas Frisch 1 Jan 10, 2022
Custom component for interacting with Octopus Energy

Home Assistant Octopus Energy ** WARNING: This component is currently a work in progress ** Custom component built from the ground up to bring your Oc

David Kendall 116 Jan 2, 2023
Home Assistant integration for energy consumption data from UK SMETS (Smart) meters using the Hildebrand Glow API.

Hildebrand Glow (DCC) Integration Home Assistant integration for energy consumption data from UK SMETS (Smart) meters using the Hildebrand Glow API. T

Aniket 153 Dec 30, 2022
emhass: Energy Management for Home Assistant

emhass EMHASS: Energy Management for Home Assistant Context This module was conceived as an energy management optimization tool for residential electr

David 70 Dec 24, 2022
Volkswagen ID component for Home Assistant

Volkswagen ID component for Home Assistant This folder contains both a generic Python 3 library for the Volkswagen ID API and a component for Home Ass

null 55 Jan 7, 2023
Component for deep integration LedFx from Home Assistant.

LedFX for Home Assistant Component for deep integration LedFx from Home Assistant. Table of Contents FAQ Install Config Performance FAQ Q. What versio

Dmitry Mamontov 28 Dec 13, 2022
Home Assistant component to handle key atom

KeyAtome Home Assistant component to handle key atom, a Linky-compatible device made by Total/Direct-Energie. Installation Either use HACS (default),

null 18 Dec 21, 2022
Home assiatant Custom component: Camera Archiver

Camera archiver Archive your ftp camera meadia files on other ftp with files renaming and event creation. Event can be used for send information to el

null 1 Jan 6, 2022
Home Assistant custom integration for e-distribución

e-Distribución is an energy distribution company that covers most of South Spain area. If you live in this area, you probably are able to register into their website to get some information about your power demand, energy consumption, or even cycle billing (in terms of consumptions).

VMG 17 Sep 7, 2022
Home Assistant custom integration for Yi cameras: yi-hack-MStar, yi-hack-Allwinner and yi-hack-Allwinner-v2

yi-hack Home Assistant integration Overview yi-hack Home Assistant is a custom integration for Yi cameras (or Sonoff camera) with one of the following

roleo 131 Jan 3, 2023
Nordpool_diff custom integration for Home Assistant

nordpool_diff custom integration for Home Assistant Requires https://github.com/custom-components/nordpool Applies non-causal FIR differentiator1 to N

Joonas Pulakka 45 Dec 23, 2022
Smart EQ connect - Custom Integration for Home Assistant

Smart EQ Connect platform as a Custom Component for Home Assistant.

Rene Nulsch 2 Jan 4, 2022
Home Assistant custom components MPK-Lodz

MPK Łódź sensor This sensor uses unofficial API provided by MPK Łódź. Configuration options Key Type Required Default Description name string False MP

Piotr Machowski 3 Nov 1, 2022