Mike Bishop

If you're able to call (or expose) the policyIsGreen() function, the three fields might be as simple as: - If policyIsGreen() - Else If charge_amps > 0 - Else...

@ngardiner, this is for communicating with the legacy Web UI on port 80, isn't it? Is it time to just get rid of the legacy UI anyway?

> I have recently come across a reason not to remove it outright - it seems a project (openWB) uses that legacy webui in an interesting way (by calling the...

Note that the general goal is to stay _below_ the amount of available solar, so the truncation is deliberate. If 9.6A is available, it might be better to export 0.6A...

Wouldn't setting the Non-Scheduled Charging rate to the max value / a value you select be what you're asking for? Then just don't schedule anything and don't use solar tracking.

Looks like something that `/api/setSetting` could handle -- POST something like `{"setting": "nonScheduledAmpsMax", "value": 48}`.

A good question. From a cursory read of the code, I don't see why it would get stuck on the previous value; there's not anything obvious that should cache the...

This can be implemented with policy restrictions, if you're using an EMS module that exposes properties. For example, "restrictions":{ "Track Green Energy":{ "match": [ "modules.TeslaPowerwall2.generatedW" ], "condition": [ "gte" ],...

Maybe add the restriction comparing to a config variable that defaults to `-1`? Then it's functionally the same as now -- generation will never return a negative number, even if...

Looking at this again, I think I see the right way to configure what you're trying to achieve: - `greenEnergyAmpsOffset` set to your export limit as a negative number; or...