leg-specific power

[kwindrem]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

add load balancing for each leg of the power system

Describe the solution you'd like

I wrote my own load management system before home assistant was well known and before there were many WiFi sensors and control devices available. One thing I needed was to insure the power consumed on each leg while on generator was not exceeded. So I configured each load with its connection (leg 1, leg 2 or between leg 1 and 2), then ran calculations for adding/shedding loads based on each leg and the total power. (mine was a 120/240 volt split-phase service but could also apply to 3-phase systems).

Describe alternatives you've considered

none

Additional context

none

[chicco-carone]

I could try but i'm not sure i can pull it off, here its just one phase so i couldn't really test it. maybe a snippet of code from your own solution could be useful to better understand the issue and then maybe implement it here.

[kwindrem]

Just getting back to considering this for my load management.

Here is some pseudo-code that may help to illustrate the concept:

average power needed ????

for load in AllLoads:
compute10secAverage (load)

for phase in allPhases:
margin [phase] = MaxPhasePower - activePower[phase]

# wait for power readings to stabilize after shedding or adding loads
if now () > valildPowerOkTime:
	for load in AllLoads (low priority first):
		if margin [phase] > 0:
			break

		# overload and load is consuming - shed load
		if load.power [phase] > IsConsumingPowerThreshold:
			margin [phase] += load.power [phase]	# use average power if greater ??
			turnOff (load)
			valildPowerOkTime = now () + LoadShedDelay

# wait for power to stabilize after load shedding
#	and for any previous load addition to activate
# loads will turn on whether they will consume or not
if now () > valildPowerOkTime and now () > loadAddOkTIme:
	for load in AllLoads (high priority first):
		if margin [phase] > load.expectedPower [phase]:
			valildPowerOkTime = now () + LoadAddDelay
			loadAddOkTime = now () + load.AddDelay
			# only add one load at a time, then wait for things to settle
			break

This code assumes that each load has its own power monitor and on/off switch, and the expected load power for each phase. Loads often take some time to start drawing power after they are turned on so the AddDelay is included in the config for the load.

I first shed loads if there is an overload detected, starting at the lowest priority. I adjust the margin as I identify loads to turn off and stop shedding when there is sufficient available power ( margin > 0) again. If no loads are shed, I look for ONE load that can be turned back on. After one load is turned on the system waits until load has a chance to turn on(AddDelay) and the power readings stablize before adding another. I think this logic is similar to what you are already doing, just that you need to look at power for each phase.

I can certainly beta test any changes you come up with. I have a 120/240 volt system so just 2 phases.