Releases: elden1337/hass-peaq
Servicecall to override non-hours
Changes
- #124 "Servicecall for price-override"
This new servicecall is called peaqev.override_nonhours. It takes an int-parameter hours. In this release you will have to call with parameters. Later I'll fix a default setting.
What happens when calling this is that non-hours, either blocked by smart-pricing or by yourself in the config, are overriden til the timer has passed.
If you are using price-awareness you will see the remainder of the override on your sensor sensor.peaqev_hour_controller as "Nonhours ignored until 13:48"
Note: this setting does not survive rebooting, so if you reboot, the override is disabled again.
Bugfixes to charger-module and top-up function
Bugfixes:
#116 Pause on chargeamps will not resume
#123 Make sure peaq doesn't stop charger when disabled
elden1337/peaqev-core#30 Top-up allows hours that are over the price-limit
elden1337/peaqev-core#28 Hourselection calculates hours for tomorrow despite lacking prices
Top-up as setting
Highly recommended update if you are using the price-awareness in Peaqev
Features:
#114 - Top-up is now a setting in your config. It's sitting on the same page as price-awareness.
Bugfixes:
elden1337/peaqev-core#25 errors in calculation for top-up.
Removal of SQL-sensors, v1.0.0
We cannot rely on the sql-sensors to work. You as users are using different sql-installations in HA, and we've already noticed one major hickup after HA-releases of the sensor type.
There is also a business driven decision for this. With this change, Peaq can provide it's locales to other applications than Home Assistant. The logic now resides in the pypi-package.
Breaking change:
Your currently set peak-sensor(s) (depending on your locale) will stop to work. You may remove those sensors after installing this version.
The new sensor is called sensor.peaqev_peak, and is a single sensor regardless (the secondary sensor for those locales that need it is now an attribute on this sensor).
Please note that your peak will be reset when installing this, the current month will be reverted to it's base-state (what you chose when installing peak) and go from there. If you do not wish for this, please wait with installing til the end of a month.
You must include this sensor (sensor.peaqev_peak) in your recorder for this to work.
Stories for this epic:
Other Features:
-
elden1337/peaqev-core#25 Allow for "top-up" today if expensive tomorrow
This feature will alter the hourselection (if you are using price aware charging) to allow for a top-up either today, or tomorrow.
The terms for this feature to kick in is that the day ahead prices on average must be larger than the max for the rest of today, or vice versa.
This is an attempt of looking ahead and not just do price-logic per isolated calendar date.
There is currently no setting for this, I want to try it as a standard feature. Should the request come in, I might add a switch for it in the future.
This change will mean that the scheduled stops can be overriden when tomorrow's prices come in. -
QA on Easee:
Easee finally seems to be working. QA has been testing out along side my changes and I now have reports from many that it is starting/stopping and updating max current as it should.
needless to say, any new bugs should be reported
A big thanks to @mejje and @reinestenberg for helping out with qa for this release!
Contributors
Assets 3
Zaptec charger type (alpha-version)
Changes
- Zaptec charger type
Note that this is an alpha-version and might not even start. Report issues you encounter.
Before you install this alpha-version it's highly recommended that you add this in your configuration.yaml to get the debug-logs that I will need when error-searching.
logger:
default: warning
logs:
custom_components.peaqev: debug