v2.5.0-beta.2
Pre-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
📔 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.