You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request]: Assign battery chemistry to INA sensor to track alternate battery types #30
Instead of tracking alternative battery discharge curves in the firmware and the requisite complexity I propose adding it to the app.
Already under the power config section you can assign the INA_2xxx i2c address for measuring the battery voltage externally to the onboard battery gauge. I think we could easily add toggle/selector to choose a battery type that would then re-graph the battery percentage display in the app ONLY. No firmware changes are required.
The 3 most used battery types that i think should be added are: Li-ion, LiFePO4, LTO (sodium ion is also getting more popular). To keep things simple this would be just for parallel battery configurations, so the standard curves could be used.
This info would be helpful to the many people that are using external charge controllers with different chemistries to still get a valid battery percentage on the device metrics log.
This info would/could be stored in the persistent node database the app now has. No info/changes are sent over the mesh or stored in the firmware. This also allows random users who take an educated guess on the chemistry of a mountain node in their town to be say LTO based, could update their app to match as well.
In the example below channel-2 is measuring the LTO battery voltage. You could hold down the channel-2 to have a popup give you the option to select the battery type for this channel.
A small battery icon could be appended to the channel name to indicate that channel is being used.
Status (August 2026): no implementation on any client. The proposal (per-sensor battery-chemistry assignment living app-side, mapping INA voltage to percentage via chemistry curves) is still coherent, but it needs a design decision first: where the chemistry setting persists (app-local per node? synced via module config?) so all clients read the same assignment. A small spec here would make it implementable.
Closing: no client has picked this up, and where the chemistry setting would be stored was never decided. Happy to reopen with a short spec if someone wants to own it.
Activity
garthvh commentedon May 15, 2025
Needs to be looked at from a cross platform perspective.
b8b8 commentedon May 15, 2025
Agreed, could get messy quickly if not, and should be accessible to all apps.
garthvh commentedon Aug 12, 2026
Status (August 2026): no implementation on any client. The proposal (per-sensor battery-chemistry assignment living app-side, mapping INA voltage to percentage via chemistry curves) is still coherent, but it needs a design decision first: where the chemistry setting persists (app-local per node? synced via module config?) so all clients read the same assignment. A small spec here would make it implementable.
garthvh commentedon Nov 8, 2026
Closing: no client has picked this up, and where the chemistry setting would be stored was never decided. Happy to reopen with a short spec if someone wants to own it.