Battery cell chemistry affects battery maintenance activities and a few defaults (like temperature ranges). E.g., an Li-NMC battery has a higher risk of thermal runaway than LFP batteries, so we might have tighter temperature bounds for Li-NMC batteries.
Since we do not have a way of specifying cell chemistries anywhere in the API, we cannot do cell-checmistry-specific operations on the batteries if we just rely on the Common-API specs.
Proposed solution
One solution could be to extend the BatteryType enum with additional variants, like LI_ION_NMC, LI_ION_LFP, etc.
What's needed?
Battery cell chemistry affects battery maintenance activities and a few defaults (like temperature ranges). E.g., an Li-NMC battery has a higher risk of thermal runaway than LFP batteries, so we might have tighter temperature bounds for Li-NMC batteries.
Since we do not have a way of specifying cell chemistries anywhere in the API, we cannot do cell-checmistry-specific operations on the batteries if we just rely on the Common-API specs.
Proposed solution
One solution could be to extend the
BatteryType
enum with additional variants, likeLI_ION_NMC
,LI_ION_LFP
, etc.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response