There needs to be a way to override autodetection to specify which fields to use for the cases where the autodetection doesn't work correctly.
On Envoy's that have it, the auto detect will use production[1].wNow, which in many (most) cases is measured using the Envoy's production CTs if it has them. However, on some Envoy's that value either doesn't exist, or is incorrect.
production[0].wNow is a measurement from the inverters. This appears to be what Enlighten uses when the meters aren't configured.
Detecting that production[1].wNow doesn't exist and falling back to production[0].wNow may solve issue #14. That would make the code a little more robust.
However, when the production CTs aren't set wired, or have been wired to read something different, it can't be auto-detected. So a manual configuration will be needed.
There needs to be a way to override autodetection to specify which fields to use for the cases where the autodetection doesn't work correctly.
On Envoy's that have it, the auto detect will use
production[1].wNow, which in many (most) cases is measured using the Envoy's production CTs if it has them. However, on some Envoy's that value either doesn't exist, or is incorrect.production[0].wNowis a measurement from the inverters. This appears to be what Enlighten uses when the meters aren't configured.Detecting that
production[1].wNowdoesn't exist and falling back toproduction[0].wNowmay solve issue #14. That would make the code a little more robust.However, when the production CTs aren't set wired, or have been wired to read something different, it can't be auto-detected. So a manual configuration will be needed.