Skip to content

3.1.0

Choose a tag to compare

View all tags
@elden1337 elden1337 released this 11 Sep 09:55
3.1.0
9ad01e3

Downloads for this release

Fixes:

  • #277 - Bugfix caution hours - since 3.0.1 the caution hours were not cared for. This is now handled better.
  • #288 - Peaks history
  • #289 - Nonhours with price-awareness

Peaks history

As the seasons change, I've noticed that certain months are harder to predict the start-value (peak start value) for than others. For instance, where I live, September and October start off with way less consumption than they end with, since the weather is getting colder.
In order to give a more lean experience and don't have to set up a too low start peak (that you will probably break later that month anyway) I've introduced a peaks-history dataset.
Peaqev now logs your historic peaks for you in an attribute. You may also use the new service service: peaqev.update_peaks_history to import your previously registered peaks. A call could look something like this:

service: peaqev.update_peaks_history
data:
  import_dictionary:
    "2022_9":
      - 1.64
      - 1.57
      - 1.58
    "2022_10":
      - 1.84
      - 1.86
      - 2.29

This is registering historic peaks for me. I have three peaks that are added each month to get average from my provider (Gothenburg Energy AB). You add whatever is calculated in your locale. One, three, five peaks.
In the options menu on the page of start-peaks, you can now select to utilize last year's peaks as start peak. If you do this, a 90% of it will be used as start peak to slightly lower your peak each year (and hopefully stay below this).

Nonhours with price-awareness

Since I introduced the price-awareness (spot-pricing) 18 months ago, I have not cared for manually added non-hours. That feature has been reserved for the users not using spot-price.
However. In my research I've found that the pattern for most common peak-breakage occurs during certain schedulable hours in many households, and have thus added them back. You can set it up through the options and during these hours Peaqev will not allow charging despite the price being cheap enough.
The hours you should select are those where you notice a high risk of breaking the peak due to cooking or other consumption being high, to assist the algorithm further.
In the future this might be changed when next generation peaq-algorithms are ready, but for now this should suffice.

Full Changelog: 3.0.8...3.1.0

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

Assets 3
Loading