Releases: elden1337/hass-peaq
3.6.0 fight the ducks!
What's Changed
The scheduler has gotten a revival!
An old and forgotten feature that wasn't working properly has now been updated.
In addition I have added two shortcut sensors you may use for your quick overrides of charging. They are number.peaqev_scheduler_charge_amount and select.scheduler_next_departure. I suggest you add them to your dashboard to quickly be able to set your next departure and desired charge by then. Remember that Peaqev first and foremost will adhere to your currently registered peak, and that the scheduler will not work with PeaqevLite. Ie, you must have a powermeter that I can read from all the time for this to function.
The hours will update themselves as the schedule period runs along, based on how much other consumption you currently have and how much charge from the desired we have been able to push to your car.
When a schedule is active you will see it in the status of sensor.peaqev_charger_controller, you may also open that one to reveal the data of the schedule.
In the sensor.peaqev_hour_controller list of all future hours you will now see an eggwatch-icon to the right of the hours affected by a schedule.
This is being released now since we are experiencing more and more duck-curves in Scandinavia, meaning that the basic algorithm of picking the very cheapest periods may not always be suitable for those using their cars in the daytime etc. 🦆
With this option, I give you the best of both worlds; the option to charge at the very cheapest, and the ability to override at will.
The classic servicecall to set a scheduler is still present, you may use that instead if you wish.
I also wish to point out the possibility of becoming a Patreon here at Github or via BuyMeACoffee. 🦆
I do develop Peaqev Free of charge and I see the community growing, which is great!
Whatever you can spare (perhaps part of what I help you save) would be much appreciated to be able to continue this journey. 🚗
In future development I aim to deliver reoccuring schedules so that you can program peaqev to act differently depending on day of week or similar.
Report any bugs that occur as per usual. Thanks!
Full Changelog: 3.5.0...3.6.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.
3.5.0
What's Changed
- #304 add powersensor and adjacent settings to options - now editable in config flow
- #332 Observed peak stuck - Bugfix, observed peak should now be what it's supposed to:
if using daily max and it's the same day as peak occured, observed peak is the maximum for today
if using history and the subtracted historical value is higher, show that
if else show the min of you average
if not using average peak values, just show the same as charged value - #333 custom spotprice sensor field - You may add a custom (Nordpool or Energidataservice) sensor. If you wish to remove it you will have to remove and add a space in the form field (because of Home Assistant frontend validation).
Full Changelog: 3.4.4...3.5.0
🥇 Enjoying Peaqev? Becoming a sponsor 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.
3.4.4
Bugfixes:
- #329 Faulty average daily. Previously added bug adds yesterday as today's average. Fixed.
Full Changelog: 3.4.3...3.4.4
🥇 Enjoying Peaqev? Becoming a sponsor 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.
3.4.3 service release
Changes:
Added icons.json which is required since HA core 2024.3. No other changes this time.
🥇 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.
3.4.2
Hotfix 3.4.2
Peaqev has now been in production for about two years. It's great to see the community growing, and the interaction from many of you through Github, Discord, X and other places.
At this time I'd like to mention that I am developing this application in my spare-time, without any stable income.
If you feel happy about the functionality that Peaqev provides you, and perhaps even saving some money by using it, please do consider becoming a patreon of mine so that I can continue developing with sustained focus.
As of the current state, Peaqev is the most advanced application when it comes to ev-charging with peak avoidance. The pricing module for spot-price itself is far more refined than most commercial alternatives, and the peak functions and vast array of business models for three countries is yet to be matched by anyone in the market.
For the time being I will continue to provide this service free of charge, so this is not a demand of any kind. Merely a request. If you like what I do, consider supporting. Every bit helps.
Available channels are: Github, PayPal or BuyMeACoffee
Thank you!
//Magnus
Changes:
- #327 Issue with savingscontroller - Added changes to the midnight calculations to avoid hickups.
- elden1337/peaqev-core#94 Today's average not added at midnight - Interim issue with daily average not always updated at midnight. Should be patched now.
- elden1337/peaqev-core#95 Min allowed hours, allow similar price - Depending on your cautionhourtype (Suave etc) there are between 0-4 min allowed hours per day to charge. In some cases these 4 hours have been added but hours costing almost exactly the same have been discarded because of the hard number of allowance (this is when it's too expensive to charge the whole day but you still want at least something). This change means that hours that are almost similar in price as those now also are allowed.
Full Changelog: 3.4.1...3.4.2
🥇 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.
3.4.1
Hotfix 3.4.1. Read below.
Only applies if you installed 3.4.0
With 3.4.0 a nasty bug which wasn't caught in testing was introduced. Sorry about that.
What it did was adding to the peaks history constantly and not capping on your max number of registerd peaks per month (like 1, 3 or 5). This caused home assistant database to eventually get a timeout on saving the very large data set to the database, and thus the peaks vanished.
To fix this (after installing 3.4.1) you can do the following. You must have access to your home assistant db, in the case below sqlLite (the standard). If you have another type of db to store your data you must probably adjust the dialect of the query accordingly.
SELECT sa.shared_attrs
FROM "states" s
INNER JOIN states_meta sm
ON sm.metadata_id = s.metadata_id
AND sm. entity_id = "sensor.peaqev_peak"
INNER JOIN "state_attributes" sa
ON sa.attributes_id = s.attributes_id
WHERE s.last_changed_ts < 1708542011
ORDER BY s.state_id DESC
LIMIT 1; Then export the shared_attrs you get from the sql query and have a look there to determine what to put into the service in the next step.
service: peaqev.update_current_peaks
data:
import_dictionary:
6h3: 2.72
18h14: 2.72
19h22: 2.44The peaks history which went amok in 3.4.0 (that's what caused this issue) should be fine a couple of seconds/minutes after the peaqev.update_current_peaks, but if not you can manually update the history with this service.
service: peaqev.update_peaks_history
data:
import_dictionary:
"2024_2": [2.72,2.72,2.44]
"2024_1": [3.74,4.22,4.16]
"2023_12": [2.95,2.93,3.05]
"2023_11": [2.73,2.74,2.7]
"2023_10": [2.35,2.29,2.33]
"2023_9": [2.08,1.8,1.88]
"2023_8": [1.97,1.83,1.82]
"2023_7": [1.87,1.8,1.82]
"2023_6": [2.31,2.07,2.04]
"2023_5": [2.24,2.13,2.14]
"2023_4": [2.97,2.38,2.74]
"2023_3": [2.8,2.83,3.06]
"2023_2": [2.32,2.28,2.31]The rest of this doc is from 3.4.0.
Greetings!
In this release I focus on fixing an old sin, the calculation of observed peak (allowed to charge to) with the norwegian tiered (trinn) prices that increase in steps instead of the Swedish version which generally increases linear to the consumption.
The algorithm behind it was more complex to work out than anticipated, so if issues do arise, tell me.
Other than that preparations for future versions where I attempt to introduce defer of charge for segmented peak pricing (when peak-cost is lower at night or at weekends etc) and some changes to the max-min calculation that some of you may use. Now it will only look ahead a specified (different depending on time of day) hours and not affect hours for tomorrow night which has caused some issues with cars not being charged.
Changes:
- #292 Change time limit on maxmin
- #316 Add standard deviation to spotprice historic data
- #325 Maxmin calculates wrong (bug)
- #326 Display star for the maxmin affected hours (frontend)
- elden1337/peaqev-core#90 New Locale Veab (Växjö, SE)
- elden1337/peaqev-core#91 New Locale Linja, NO
- elden1337/peaqev-core#92 Change NO_Glitre to average of three days calculation
- elden1337/peaqev-core#93 Change NO_LNett to average of three days calculation
The new norwegian calculation:
Without this new calculation, the norwegian peaks were stopped at the lowest of the registered peaks (called the observed peak). With the business model of tiers (trinn), this is suboptimal since it can mean that you are charged for the tier at 5kW, but Peaqev only let's you charge up until for example 3kW because of your currently lowest peak.
This is now taken care of and all the currently available Norwegian locales have their current tiers added.
Affected locales:
- NO_AskerNett
- NO_Linja
- NO_GlitreEnergi
- NO_LNett
- NO_Tensio
- NO_AgderEnergi
- NO_Elvia
- NO_Lede
- NO_BKK
- NO_Mellom
Tiers in examples (2,5,10,15,20)kW
Example 1:
Incoming peakvalues: [2.05,2.7,2.81]
Average: 2.52Kw
Next tier limit: 5kW
The most common spread, with three daily averages quite close to one another (but perhaps not on this level). In this case the observed peak can increase from 2.05-4.9kW to sustain the cost.
------------
Example 2:
Incoming peakvalues: [0.05, 14.6, 14.6]
Average: 9.75kW
Next tier limit: 10kW
In this case the observed peak can now only increase to 0.5kW, otherwise the two larger ones which are already above the desired tier range will put the average above 10kW.
------------
Example 3 (if there is only a single peak registered):
Incoming peakvalues: [2.5]
Next tier limit: 5kW
If lacking multiple peaks the response would be 4.9kW in this case to stay just below the next tier.
Full Changelog: 3.3.3...3.4.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.
3.3.3 (required after HA core 2024.2.1)
Changes:
Patch update needed after upgrading to HA Core 2024.2.1. The utility meters stopped working due to an added required parameter.
Full Changelog: 3.3.2...3.3.3
🥇 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.
3.3.2
Changes:
- #317 Extra stop clause - In the event of charger being running without peaq telling it to (once peaq is active) it will now send stop requests to the charger no matter what state the peaq-charger is in (Done, Idle etc).
- Fixes to max-amps available for users using PowerCanary.
Full Changelog: 3.3.1...3.3.2
🥇 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.
3.3.1 hotfix zaptec
Changes:
- #319 Unable to setup integration - bug in zaptec setup specifically. should be handled.
Full Changelog: 3.3.0...3.3.1
🥇 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.
3.3.0
Changes:
- #310 Create service call to alter the current peak - New service call where you can update your current month's peaks if you have a deviation in readings from your electricity company or from bad reading in HA. Follow template when doing this one.
- #312 Bug on dynamic caution hour getter - Fixed.
- #313 If Errorstate on chargecontroller, always try to kill charging. - Fixed. Now directly calling off to kill charger if an error occurs.
Full Changelog: 3.2.2...3.3.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.