elden1337 / hass-peaqhvac Goto Github PK

Like when offset is lowered because of high peak

Should only be on service on

Today [0,76, 0,57, 0,59, 0,64, 0,97, 1,5, 1,97, 2,22, 2,16, 1,93, 1,72, 1,55, 1,53, 1,5, 1,48, 1,52, 1,5, 1,79, 2,16, 2,59, 2,58, 2,08, 1,81, 1,43]
Tomorrow [1,42, 0,8, 0,61, 0,59, 0,6, 1,4, 1,64, 2,17, 1,97, 1,77, 1,51, 1,44, 1,41, 1,38, 1,36, 1,37, 1,4, 1,55, 1,84, 2,28, 2,14, 1,94, 1,62, 1,47]

Water 46.6
Trend -0.9
Time 23:05
Next start 23:47.
Expected 03:47

To lower jumpy strain on hvac

If hour 1 - 3
hour 2 - 1
hour 3 - 3

Then average all three hours to 2

To calculate perceived temperatures

Deviation from mean doesnt seem to be good enough

If all day tomorrow is expensive, heat some extra water before the increase to possibly avoid expensive heating

Try to wait for minute > 30 to lower peaks

Boost water if daytime is x cheaper than evening if home.

Nibe api is too slow. Change it to ~95%

this is to lower max-peak. listen to current set temperatures if possible. could be a problem with scheduled water stop.

should be an input_number in HA.
this data should be taken into account when measuring offset-steps and demand

Should be a restoreentity-sensor that survives reboots
On hitting limits it should make sure to heat water all the way to max temp.

Would be nice if you could add support for this https://github.com/MTrab/energidataservice

As per discord discussion.

Wants to start at :59 regularly which is wrong for future hours.

Also seems to forget to recalc, perhaps not getting tomprrows prices at 13h as it should?

Temp trend outside drops down by x

Either with a maxprice in setup or if current price is rolling30avg * x

If noone is home,lower temp to start heating water (calc if there's a gain here)

Inherrit to ventilationmodule heatmodule and watermodule

Today = 0,29, 0,29, 0,28, 0,26, 0,27, 0,26, 0,29, 0,51, 1,95, 1,64, 0,82, 0,51, 0,41, 0,32, 0,31, 0,31, 0,32, 0,33, 0,31, 0,28, 0,26, 0,25, 0,21, 0,17

Tomorrow = 0,21, 0,21, 0,21, 0,2, 0,2, 0,19, 0,21, 0,23, 0,24, 0,27, 0,27, 0,27, 0,26, 0,25, 0,25, 0,26, 0,27, 0,28, 0,29, 0,28, 0,27, 0,25, 0,23, 0,21

Groups tomorrow should be all cheap.

1, change threshold for operations from offset > 0 to >= 0
2. Alter tempthreshold and time threshold so that they play nicer with a lower peak.

As is now set temp is restored but state back to normal, which causes set temp to be -2 from desired

Ignore current temp.
Never boost water.
Check that peak is single hour or max x hours long

At 8:58 the booster started right when water passed 40c.
It should have waited sccording to the prices:

0,24, 0,27, 0,27, 0,27, 0,26, 0,25, 0,25, 0,26, 0,27, 0,28, 0,29, 0,28, 0,27, 0,25, 0,23, 0,21

It's 0.9 above set and trend is -0.4. Temp trend offset still claims -1. Which adds to the delay of preheating

Check algo. Should not call -10 unless diff is > 20%

if current hour has an offset above 0 (limit), but coming hours are decreasing even more, consider waiting. this pattern is espescially useful during the night when a few hours more rarely make a difference for comfort.

Take indoor temp, outdoor temp and vent into account. Possibly also forecast.

For instance, 20c indoors feels much colder when its 0 outside than when its 12c outside.
Sometimes indoor temp might have to be slightly increased to add comfort.

If locale etc. Has already been set up, take existing sensors

System

• HAOS 11 (tested both public and private access, right now it's set to be public) - installed like 1 week ago fresh, didn't touch anything except allowing trusted_proxies in configuration.yaml
• Nibe integration
• peaq-hvaq 2.0.2
• Nibe F750
• Subscription to "Change Settings" in Nibe:

Debuggning

The real sensor names are:
Indoor temp
sensor.nibe_15XXXX_40033

Outdoor temp:
sensor.nibe_15XXXX_40004

Tried using them as well, but first tried with only numbers since that's what the documentation says.

Is it here that I enable debuggning? Done in that case.

Sensors are working, but some of them are unavailable in the Nibe integration - don't know if that related?

use same enum and make a diff-tool to compare which one needs more attention now.

Lower for the hour if breaching peak. Like for the car

On peak lower for degree min and waterboost

If we have heated the pipes to x, and a couple of expensive hours are approaching, take next cheap period into account (with weather forecast) to possibly not lower entirely.

Higher diff if large stdev, flatter if flatter

Set temp = temp-2
Set high = 0.1
Set low = 0.5

Regular should be
High = 0.3
Low = 0.2