v0.17.2

Changed

• Added country metadata for the supported account regions to meet HACS default-repository submission requirements.
• Required successful HACS and Hassfest validation before publishing a GitHub release.
• Clarified dedicated-account and PIN prerequisites, sign-in and refresh token troubleshooting, and vehicle-specific A/C restrictions in the README.
• Removed outdated migration and add-on guidance from the README.

v0.17.1

Fixed

• Fixed false errors when successful GWM cloud acknowledgements omit data, including climate settings, security-PIN checks, and remote commands in overseas regions.
• Corrected debug diagnostics to recognize these acknowledgements as successful while still reporting whether data is present.
• Added regression coverage for acknowledgement handling, malformed responses, required read payloads, and status values after accepted commands.

v0.17.0

Changed

• Breaking: Replaced the climate entity's cool mode and mainland-China heat mode with auto. The vehicle determines heating or cooling from the selected target temperature. Automations and scripts must change hvac_mode: cool or hvac_mode: heat to hvac_mode: auto; both old values are rejected without compatibility aliases.
• Stopped reporting active climate sessions as cooling when GWM provides only an on/off state. The underlying target-temperature and stop requests stay the same.

v0.16.21

Fixed

• Preserve overseas climate, lock, window, charging-plan, and command-result operation names in sanitized error logs instead of replacing them with unknown.

Added

• Add opt-in debug diagnostics that distinguish saving climate settings, checking the RU security PIN, submitting a command, polling its result, and prerequisite vehicle reads.
• Record HTTP status, bounded numeric API codes and their original JSON types, the presence/type of data, and fixed response-format reasons without logging raw responses, credentials, PINs, VINs, URLs, or command identifiers.
• Add regression coverage for diagnostic privacy, malformed responses, numeric codes, disabled logging, and unchanged transport and decoder behavior.

This is a diagnostics-only release for investigation of #28. Command sequencing, request payloads, PIN handling, retries, and strict response validation are unchanged. The underlying RU command failure still requires a fresh debug-log capture; this release does not claim to fix it.

v0.16.20

Fixed

• Switched mainland-China BeanTech status reads to API v3.0 so battery-pack voltage, current, and live charging power can populate.
• Calculated charging power from the v3 efficiency value in watts and exposed it in kilowatts, while retaining the legacy power fallback.
• Accepted sparse v3 battery-pack responses and added mapper, fallback, routing, and normalized-snapshot regression coverage.

Thanks to @tyj365888 for the protocol research and live testing on a Tank 300 Hi4-T.

v0.16.19

Added

• I added the captured NavInfo cabin-purge and force-refresh controls for mainland-China vehicles.

Fixed

• I corrected the NavInfo sunroof positions to use the official app's confirmed tilt, half-open, and fully-open angle values.
• I matched the official NavInfo climate start contract: every start or temperature change now uses the start function, command code 6, engine control enabled, and the confirmed 17 to 31 C range.
• I added the official app's signed companion climate-configuration request after each accepted NavInfo climate start. If that follow-up request fails, the integration preserves the already accepted provider command ID so Home Assistant can continue tracking the physical command safely.

v0.16.18

Fixed

• I corrected the overseas air-circulation request so its confirmed cabin-clean fields are sent directly under command flag 0x11. This removes the invalid extra wrapper that GWM rejected with API code 550002.
• I added privacy-safe service-call logging for the client error type, category, operation, API code, HTTP status, and retry delay. Request bodies, credentials, tokens, VINs, and provider descriptions remain excluded.

v0.16.17

Added

• I added BeanTech battery-pack current and voltage sensors using the read-only fields researched in the retired repository's PR #27. These values remain unknown when the vehicle does not report them, which is expected while some vehicles are parked and powered off.

Changed

• I now expose the existing BeanTech power value as an enabled measurement sensor in kilowatts. Battery current, voltage, and power remain isolated to mainland-China BeanTech vehicles.

v0.16.16

Added

• I added a capability-gated Front defroster switch for overseas vehicles that report front-defroster status. It uses the official app's 15-minute start request, supports an explicit stop request, and follows the existing restart-safe command journal and result polling.
• I added a capability-gated Start air circulation button for overseas vehicles that report the matching status. It runs the official app's fixed 60-second external-air cabin-clean action and follows the same command journal and result polling.

I covered both controls with offline protocol and integration tests. They still need live confirmation on each supported vehicle model, so please test them manually while the vehicle is parked before using them in an automation.

v0.16.15

Fixed

• I now prefer Home Assistant's supported public TrackerEntity API, with a compatibility fallback for older supported Home Assistant releases. This shared platform fix applies to every region and removes the warning about the deprecated alias being removed in Home Assistant Core 2027.6.