Toyota: fall back to evRange when evRangeWithAc is unusable

[Copilot]

Toyota status responses can now omit a usable evRangeWithAc, which caused range parsing to fail with unsupported unit type. This updates the Toyota provider to keep using the AC-adjusted range when valid, but fall back to the standard EV range when that field is missing or malformed.

• Provider fallback

  • Keep evRangeWithAc as the preferred source.
  • Fall back to evRange if evRangeWithAc cannot be converted.
  • Return the fallback conversion error when both range fields are unusable.

• Regression coverage

  • Add focused Toyota provider tests for:
    • normal evRangeWithAc handling
    • fallback when evRangeWithAc is absent/empty
    • error propagation when neither range field is usable

rng, err := res.Payload.EvRangeWithAc.ValueInKilometers()
if err == nil {
	return rng, nil
}

fallback, fallbackErr := res.Payload.EvRange.ValueInKilometers()
if fallbackErr == nil {
	return fallback, nil
}

return 0, fallbackErr

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}