2024-10-08
Dear Peaquser,
After three years of open source in these projects, I am about to set sail on the next leg of my journey. I will soon start a job where I will work with adjacent technology, and thus will seize to update the repos with new features. This is to not be questioned regarding IP going forward.
For the time being I want to let the codebases stay online, and will accept pull requests and occasionally do patch updates and bug fixes to > keep the solutions running. However, I will not take part in general feature discussions any longer, starting from 2024-12-01.
If you wish you may fork the projects and create features that you send me as pull requests. That way we can keep the flow going without > my direct interference in the inventions. For any usage not covered by the general download by hacs, look towards the license on the repos for guidance. Here's a snapshot of what > the licenses on my code requires: https://creativecommons.org/licenses/by-nc-nd/4.0/deed.en
Thanks for all engagement and happy to have helped a bunch of people with this spare time invention of mine. //Magnus
PeaqHvac is a custom component for Nibe F-series users. As of 2022-12-20 the tested versions are exhaust-air pumps F730 and F750, but it probably works fine with other similar ones as well. In future releases other brands might be added.
Because of the slow response from the Nibe Uplink-api, calls are made somewhat prematurely to try and correct for this lag. If peakshaving is active (requires PeaqEv) this means that peaks sometimes cannot be avoided completely, but rather lessened in their emphasis.
Nibe clients will need to have an uplink premium subscription in order to be able to manipulate the Hvac remotely.
It is required to have at least this setup in your configuration.yaml
:
nibe:
systems:
- system: 1234567890
sensors:
- 40995
- 40997
- 47206
Required to install is Home Assistant version 2023.10.5 or higher.
Preferred if you have HACS installed is to search for Peaqhvac there.
Otherwise you may:
custom_components/peaqhvac
folder to <config_dir>/custom_components/peaqhvac/
There are a few options when configuring PeaqHvac:
Name | Description |
---|---|
Hvac systemid |
The provided system-id from your vendor. For Nibe F-series this is often a five digit number. |
Temp sensors indoors |
Your indoor temp sensor(s). Added as sensor. my_sensor. Comma-separated if many. |
Temp sensors outdoors |
Your outdoor temp sensor(s). Added as sensor. my_sensor. Comma-separated if many. |
Stop heating temp |
The outside temp where you never want Peaqhvac to start heating |
Very cold temp |
A very cold outside temp in your area, where Peaqhvac should start acting differently to save energy. Not recommended to put value below -10C here. |
Nonhours waterboost |
A selectable list of hours where you never wish to have a water-boost conducted (not operational) |
Low DM-value |
A number somewhere in between your Compressor-start and Electric addon start. Lower than this and Peaqhvac will take extra steps to conserve energy |
PeaqHvac works with the common peaqevcore-library which is also used by PeaqEv to calculate good and bad hours of operation. What comes out of that is a set of offsets for today (and tomorrow if available) that are used to tune your hvac up/down accordingly. After this calculation several things do happen, depending on the number of temperature-sensors used, if you want peak-shaving or not and if you have set up weather integration.
The included logic for water heating temp is not self learning, but is adjusting to a number of factors. Should you require water at a specific time, you may override the boost with the myuplink service calls. The boost may require multiple runs to heat to your desired temp depending on your current peak energy level. The boost signals when it is about to start both in the frontend, and through the HA servicebus to warn other integrations if they are listening (such as PeaqEV).
climate.peaqhvac_climate_control
Set your desired temperature with this climate-control, in steps of half-degrees from 15-27C. There are presets available in this sensor that you may set by automations or manually. They have different characteristics:
None
- Normal operationEco
- Reduced tolerance for increased temperatures before lowering offset. Will also reduce temperature by 0.1C per 1.5C if below -5CAway
- Set temperature is lowered by 1C. Heavily reduced tolerance for increased temperatures before lowering offset. Will also reduce temperature by 0.1C per 1.5C if below -5Cnumber.peaqhvac_tolerance
- The number set here determines how well the offsets will align with the daily price-curve. Integers 1-10. Remember that the higher the number, the higher the risk of electrical addon-usage and/or peak-energy hours.sensor.peaqhvac_calculated_hvac_offset
- This sensor will give you information on the currently calculated offset (which is pushed to the Hvac if control heat is enabled). The attributes shows you the different calculation-steps to override a specific hourly offset based on the price. Here you may also retrieve the offsets for today, tomorrow plus the "raw" offsets for today that are without weather prognosis-interference.sensor.peaqhvac_average_temperature_indoors
| sensor.peaqhvac_average_temperature_outdoors
- The average temperatures based on the sensors you provide in setup.sensor.peaqhvac_temperature_trend_indoors
| sensor.peaqhvac_temperature_trend_outdoors
- The current temperature trends registered as C/h. switch.peaqhvac_enabled
- This is the main switch to turn PeaqHvac on/off from your system.switch.peaqhvac_control_heat
- If on, the heating will be controlled as described aboveswitch.peaqhvac_control_water
- If on, the water supply will be controlled as described above