Skip to content

v2.5.0 - Power Canary

Compare
Choose a tag to compare
@elden1337 elden1337 released this 20 Dec 10:03
· 969 commits to main since this release

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.
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

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

馃挰 Join my Discord-server to interact with other peaq-users.

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