v0.36.1

0.36.1

A single fix, for vehicles metered in engine hours rather than distance.

Fixed

• A vehicle set to track engine hours has its readings treated as hours rather
  than as a distance. Its consumption is worked out in litres per hour, its
  running cost per hour, and a charged machine's energy use per 100 hours.
  None of those figures change any more when the vehicle's (distance-only)
  odometer unit is switched between km and miles, which used to scale 50
  engine hours into 80.5 as though they were miles. Vehicles tracked by
  mileage are unaffected. (#323)

Changed

• A vehicle's tracking unit can no longer be changed once anything has been
  logged against its odometer. Switching it would have reinterpreted every
  existing reading — 50 miles becoming 50 engine hours — so the rest of the
  edit saves and that one field is refused with a message.
  (#323)

Documentation

• The README describes the tracking unit and is candid about the remaining
  gap: the figures for an hours-tracked vehicle are correct, but the labels
  beside them still read in distance terms ("L/100km", "Cost per mi"). That
  is being corrected separately.
• The API documentation says the same about total_distance and
  average_consumption, and records that the tracking unit is neither
  exposed nor settable over the API. The vehicle response example also now
  includes secondary_fuel_type, which the API has returned since 0.36.0.

Thanks to whoever reported #323
— it was a quiet fault that only showed up on plant and machinery.