Refactor metrics to telemetry to support vehicle differences.

kezarjg commented 1 year ago

Complete refactoring of the metrics to telemetry portion of the script.

Drop getOvmsMetrics() - metrics are now fetched as they are needed.
Created getOVMSMetric(parameter) - This function checks to see if the vehicle module supports the parameter, then pulls it in to the telemetry object. Resolves #16
Added the capacity parameter to Resolve #17. However, the nominal voltage metrics is not yet added to the OVMS framework, so it won't function until that occurs.
Replaced mapMetricsToTelemetry() with createTelemetry() to implement the new framework. Resolves #14
Updated info() to only log metrics that are contained in the telemetry object.

Note: This script relies on a new function in OVMS that is currently in the dev branch.

jason-abrp commented 1 year ago

This looks fantastic! When you're ready to merge, and the requisite OVMS updates are live, ping me so I can merge your work.

kezarjg commented 1 month ago

This function in question has been published;

2024-03-23 - 3.3.004 OTA release New DukTape function OvmsMetrics.HasValue -- Returns true if the metric has a valid value.

iternio / ovms-link