v2.8.0b3

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: debug

known issues in beta3:

• #209 - Excessive calling to stop charger
• #212 - Chargecontroller doesn't update states properly
• #213 - Delay start if powersensor is not showing numbers yet
• #215 - Log spamming of non-started utility-sensors for day and month
• #218 - Cheaper hour is blocked, more expensive is in cautionhours.
• #221 - Wrong hours for tomorrow
• #220 - Error on price calc

---

Changes:

• #208 - Add gain/loss sensors
• #210 - Error on broadcasting with parameters
• #211 - Update setup in init (HA requires this change from 2023.3)
• #214 - Block Nocturnal charging (optional)
• elden1337/peaqev-core#72 - Refactor aggressive-type
• elden1337/peaqev-core#73 - Change dynamic top-price logic
• #222 - Retry attempt to get max-amps (for easee)

Full Changelog: v2.7.0...v2.8.0b3

Refactor aggressive-type:

There is now a fourth option for caution-hour types; "Scrooge".
What Scrooge does is act like Aggressive in terms of which hours to determine as caution vs non, but on top of that, he will steal from your eligable hours so that you never have more than 8 hours per 24hr-cycle available for charging. By this, you get a cheaper charging overall, but a more narrow window.

Activate through the options-flow if desired

Change dynamic top-price logic:

This change is for those with price-aware charging and the option to use the monthly average as top-price.
Previously this option ignored your static top-price alltogether.
Now it will take the min-value of the two (monthly average and your set top-price).

Block nocturnal charging:

Should you wish to block out nocturnal charging (23-06) but still get the cheapest hours possible from the rest of the hours, this is the option for you.
If you are not using price-awareness you can just control your non-hours as per usual, this has no effect for you.

Activate through the options-flow if desired

Gain/loss-sensors:

These sensors are aimed at gamify your savings. They will only appear if you have regular peaqev-installation with powermeter (ie not Lite), and will continously show you how your purchased kWh compare percentage-wise to the daily or monthly average from your Nordpool-setup/settings.

They do fluctuate more in the beginning of a period, and later stabilize. However, if you chose to visualize them you can get a hint of how your day or month is going and act accordingly.

In order for the data to be correct you will need to have this version installed over the limit between two days (daily sensor) or month (monthly sensor)

---

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

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

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

v2.8.0b2

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: debug

known issues in beta2:

• #218 - Cheaper hour is blocked, more expensive is in cautionhours.
• #209 - Excessive calling to stop charger
• #212 - Chargecontroller doesn't update states properly
• #213 - Delay start if powersensor is not showing numbers yet
• #215 - Log spamming of non-started utility-sensors for day and month

---

Changes:

• #208 - Add gain/loss sensors
• #210 - Error on broadcasting with parameters
• #211 - Update setup in init (HA requires this change from 2023.3)
• #214 - Block Nocturnal charging (optional)
• elden1337/peaqev-core#72 - Refactor aggressive-type
• elden1337/peaqev-core#73 - Change dynamic top-price logic

Full Changelog: v2.7.0...v2.8.0b1

Refactor aggressive-type:

There is now a fourth option for caution-hour types; "Scrooge".
What Scrooge does is act like Aggressive in terms of which hours to determine as caution vs non, but on top of that, he will steal from your eligable hours so that you never have more than 8 hours per 24hr-cycle available for charging. By this, you get a cheaper charging overall, but a more narrow window.

Activate through the options-flow if desired

Change dynamic top-price logic:

This change is for those with price-aware charging and the option to use the monthly average as top-price.
Previously this option ignored your static top-price alltogether.
Now it will take the min-value of the two (monthly average and your set top-price).

Block nocturnal charging:

Should you wish to block out nocturnal charging (23-06) but still get the cheapest hours possible from the rest of the hours, this is the option for you.
If you are not using price-awareness you can just control your non-hours as per usual, this has no effect for you.

Activate through the options-flow if desired

Gain/loss-sensors:

These sensors are aimed at gamify your savings. They will only appear if you have regular peaqev-installation with powermeter (ie not Lite), and will continously show you how your purchased kWh compare percentage-wise to the daily or monthly average from your Nordpool-setup/settings.

They do fluctuate more in the beginning of a period, and later stabilize. However, if you chose to visualize them you can get a hint of how your day or month is going and act accordingly.

In order for the data to be correct you will need to have this version installed over the limit between two days (daily sensor) or month (monthly sensor)

---

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

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

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

v2.8.0b1

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: debug

known issues in beta1:

• #209 - Excessive calling to stop charger
• #212 - Chargecontroller doesn't update states properly
• #213 - Delay start if powersensor is not showing numbers yet
• #215 - Log spamming of non-started utility-sensors for day and month

---

Changes:

• #208 - Add gain/loss sensors
• #210 - Error on broadcasting with parameters
• #211 - Update setup in init (HA requires this change from 2023.3)
• #214 - Block Nocturnal charging (optional)
• elden1337/peaqev-core#72 - Refactor aggressive-type
• elden1337/peaqev-core#73 - Change dynamic top-price logic

Full Changelog: v2.7.0...v2.8.0b1

Refactor aggressive-type:

There is now a fourth option for caution-hour types; "Scrooge".
What Scrooge does is act like Aggressive in terms of which hours to determine as caution vs non, but on top of that, he will steal from your eligable hours so that you never have more than 8 hours per 24hr-cycle available for charging. By this, you get a cheaper charging overall, but a more narrow window.

Activate through the options-flow if desired

Change dynamic top-price logic:

This change is for those with price-aware charging and the option to use the monthly average as top-price.
Previously this option ignored your static top-price alltogether.
Now it will take the min-value of the two (monthly average and your set top-price).

Block nocturnal charging:

Should you wish to block out nocturnal charging (23-06) but still get the cheapest hours possible from the rest of the hours, this is the option for you.
If you are not using price-awareness you can just control your non-hours as per usual, this has no effect for you.

Activate through the options-flow if desired

Gain/loss-sensors:

These sensors are aimed at gamify your savings. They will only appear if you have regular peaqev-installation with powermeter (ie not Lite), and will continously show you how your purchased kWh compare percentage-wise to the daily or monthly average from your Nordpool-setup/settings.

They do fluctuate more in the beginning of a period, and later stabilize. However, if you chose to visualize them you can get a hint of how your day or month is going and act accordingly.

In order for the data to be correct you will need to have this version installed over the limit between two days (daily sensor) or month (monthly sensor)

---

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

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

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

v2.7.0

Changes:

• elden1337/peaqev-core#44 - New locale, Jukkasjärvi (JBF), Sweden
• elden1337/peaqev-core#70 - New locale, Ellevio, Sweden
• #70 - Add event listeners to reload integration after options change
• #193 - Block too short charging windows because of upcoming nonhour
• #194 - Faulty chargecontrollerstate-bug from 2.6.1
• #198 - Allow chargerless implementation description below
• #199 - avoid setting up power canary when using peaqev-LITE
• #200 - Option to allow dynamic top-price based on monthly Nordpool average description below

As always, keep an eye out and report any issues you may encounter. Thanks and enjoy.

198 Allow chargerless implementation

This feature allows for a new charger-type "No charger". What the aim is is to let users get the peaqev-sensors without any of the allowed chargers. The user can then fix automations themselves.
This setting will ignore if you pick "powersensor includes car", it will always be on by default (since peaq is not aware of the car's power draw)
It will not setup the session-sensors for you, and it cannot act on threshold-breaches. That will be up to you.

200 Option to allow dynamic top-price based on monthly Nordpool average

This option overrides the optional absolute-top-price setting over which no charging should ever be allowed.
What it does instead is to look at the gathered average Nordpool for this month, and never let you charge above that amount.
If you wish to use this and still sometimes override, you may use the override-service call.

Full Changelog: v2.6.1...v2.7.0

---

📔 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.7.0 beta2

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: debug

Changes:

• elden1337/peaqev-core#44 - New locale, Jukkasjärvi (JBF), Sweden
• elden1337/peaqev-core#70 - New locale, Ellevio, Sweden
• #70 - Add event listeners to reload integration after options change
• #193 - Block too short charging windows because of upcoming nonhour
• #194 - Faulty chargecontrollerstate-bug from 2.6.1
• #198 - Allow chargerless implementation description below
• #200 - Option to allow dynamic top-price based on monthly Nordpool average description below

Beta2-fixes:

• #199 - avoid setting up power canary when using peaqev-LITE
• #201
• #202
• #203
• major refactor to #198

Full Changelog from beta1: v2.6.1...v2.7.0b2
Full Changelog from latest major: v2.7.0b1...v2.7.0b2

198 Allow chargerless implementation

This feature allows for a new charger-type "No charger". What the aim is is to let users get the peaqev-sensors without any of the allowed chargers. The user can then fix automations themselves.
This setting will ignore if you pick "powersensor includes car", it will always be on by default (since peaq is not aware of the car's power draw)
It will not setup the session-sensors for you, and it cannot act on threshold-breaches. That will be up to you.

200 Option to allow dynamic top-price based on monthly Nordpool average

This option overrides the optional absolute-top-price setting over which no charging should ever be allowed.
What it does instead is to look at the gathered average Nordpool for this month, and never let you charge above that amount.
If you wish to use this and still sometimes override, you may use the override-service call.

---

📔 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.7.0 beta

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: debug

Changes:

• elden1337/peaqev-core#44 - New locale, Jukkasjärvi (JBF), Sweden
• elden1337/peaqev-core#70 - New locale, Ellevio, Sweden
• #70 - Add event listeners to reload integration after options change
• #193 - Block too short charging windows because of upcoming nonhour
• #194 - Faulty chargecontrollerstate-bug from 2.6.1
• #198 - Allow chargerless implementation description below
• #200 - Option to allow dynamic top-price based on monthly Nordpool average description below

Full Changelog: v2.6.1...v2.7.0b1

198 Allow chargerless implementation

This feature allows for a new charger-type "No charger". What the aim is is to let users get the peaqev-sensors without any of the allowed chargers. The user can then fix automations themselves.
This setting will ignore if you pick "powersensor includes car", it will always be on by default (since peaq is not aware of the car's power draw)
It will not setup the session-sensors for you, and it cannot act on threshold-breaches. That will be up to you.

200 Option to allow dynamic top-price based on monthly Nordpool average

This option overrides the optional absolute-top-price setting over which no charging should ever be allowed.
What it does instead is to look at the gathered average Nordpool for this month, and never let you charge above that amount.
If you wish to use this and still sometimes override, you may use the override-service call.

---

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

It went a bit too fast yesterday with 2.6.0. Sorry about that! This hotfix should rectify the issue with chargecontroller being unavailable.

Changes:

• Fix faulty states based on private method
• Added this month's Nordpool average price to money_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.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: debug

---

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.

---

📔 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: debug

---

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