Thanks Anthony. That had occurred, but as you point out requires at least a 1% change to register. Given I had to drop the polling down to 5† seconds when checking the sensor was plugged in, and throwing an error if not, I am pretty sure that the time required to wait for the 1% change would be beyond the project lead’s patience. So didn’t even suggest it. What he doesn’t know about won’t hurt him (or me)
Seems an odd oversight in the SDK, given the other charge related values you can get.
† Looking like this may have to go down to 2 seconds, to give him the required level of instant feedback