Always store the charge data

It has higher resolution information on ranges which we can use to do a better
job estimating energy used; the current method occurs too many accumulative
rounding errors as it gets only integer precision kWh used / regenerated every
quarter second; with this data we should also be able to track vampire losses
much more closely. And given the total amount of data we store, this really
doesn't make much difference.

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Also store vehicle state at start so we have firmware version

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Keep map centered on car

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Merge pull request #25 from arthurblake/master

in streaming.js, change most console.log statements to util.log
Merge pull request #26 from dirkhh/charging

Added charging data and vehicle state into database. Keep map display centered on the car.