Releases: elden1337/hass-peaq
v2.6.0
Changes:
- #192 - Lessen load on system from PowerCanary
- #184 - restructure zaptec (not done)
- #188 - rounding of nordpool-averages (they got too distinct after latest nordpool-update)
- #189 - Configflow validation (for the power sensor right now)
- #190 - Refactor Chargertypes into Enum
- elden1337/peaqev-core#66 - attempt to fix jumpy charge-allowance (short bursts of changes sometimes)
- elden1337/peaqev-core#65 - remove duplicate const for hourselection
- #185 - update DEVICE_CLASS consts to enum
- Refactor more types into enums for Locale Chargecontroller and Charger
Full Changelog: v2.5.1...v2.6.0
We will have to re-visit Zaptec later on. The beta-testing and fixes are lingering and I don't want to delay other necessary updates.
📔 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.
v2.6.0-beta.3
beta.3-changes:
- #192 - Lessen load on system from PowerCanary
- #184 - restructure zaptec
- Refactor more types into enums for Locale Chargecontroller and Charger
Previous changes:
- #188 - rounding of nordpool-averages (they got too distinct after latest nordpool-update)
- #189 - Configflow validation (for the power sensor right now)
- #190 - Refactor Chargertypes into Enum
- elden1337/peaqev-core#66 - attempt to fix jumpy charge-allowance (short bursts of changes sometimes)
- elden1337/peaqev-core#65 - remove duplicate const for hourselection
- #185 - update DEVICE_CLASS consts to enum
Full Changelog: v2.6.0-beta.2...v2.6.0-beta.3
If you are beta-testing it is suggested that you turn on debug-logs for peaqev in your configuration.yaml:
logger:
default: error
logs:
custom_components.peaqev: debugThe main event of this beta is make a 2nd attempt at getting Zaptec working.
Please report if you cannot install still, and provide me with logging if possible.
📔 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.
2.6.0-beta 2
beta.2-changes:
- #184 - restructure zaptec
- #188 - rounding of nordpool-averages (they got too distinct after latest nordpool-update)
New additions:
- #189 - Configflow validation (for the power sensor right now)
- #190 - Refactor Chargertypes into Enum
Full Changelog: v2.6.0-beta...v2.6.0-beta.2
If you are beta-testing it is suggested that you turn on debug-logs for peaqev in your configuration.yaml:
logger:
default: error
logs:
custom_components.peaqev: debugv2.6.0-beta info
The main event of this beta is make a 2nd attempt at getting Zaptec working.
Please report if you cannot install still, and provide me with logging if possible.
Changes:
- elden1337/peaqev-core#66 - attempt to fix jumpy charge-allowance (short bursts of changes sometimes)
elden1337/peaqev-core#65 - remove duplicate const for hourselection- #184 - restructure zaptec
#185 - update DEVICE_CLASS consts to enum- Refactor chargertypes
Refactor misc CONST to enum
📔 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.
2.6.0-beta
The main event of this beta is make a 2nd attempt at getting Zaptec working.
Please report if you cannot install still, and provide me with logging if possible.
Changes:
- elden1337/peaqev-core#66 - attempt to fix jumpy charge-allowance (short bursts of changes sometimes)
- elden1337/peaqev-core#65 - remove duplicate const for hourselection
- #184 - restructure zaptec (hopefully works)
- #185 - update DEVICE_CLASS consts to enum
- Refactor chargertypes
- Refactor misc CONST to enum
Full Changelog: v2.5.1...v2.6.0-beta
📔 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.
v2.5.1 - Hotfix for Zaptec setup
Changes:
- #184 - Zaptec setup unavailable
📔 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.
v2.5.0 - Power Canary
🎅 🤶🏼
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.
v2.5.0-beta.2
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.
v2.5.0-beta
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.
v2.4.0 (Zaptec in beta-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
📔 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.
Contributors
Assets 3
v2.3.1 (only affects Swedish users)
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.
📔 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.