Home Assistant Daily: Tesla Tracker Updates and MQTT Protocol Migration
Home Assistant merged 18 pull requests on May 29th, 2026, featuring breaking changes to Tesla device trackers and automatic MQTT protocol version 5 migration. Several stability fixes addressed crash conditions across multiple integrations.
Duration: PT1M55S
Transcript
Good morning, this is Home Assistant Daily for May 29th, 2026.
Brett Adams merged two breaking changes for Tesla integrations. Both Teslemetry and Tesla Fleet device trackers no longer display route destination names as their state - instead showing proper zone-based locations like "home" or "not_home". The destination information has moved to new dedicated sensors that are disabled by default.
Jan Bouwhuis merged a significant MQTT improvement that silently migrates to protocol version 5 when brokers support it, eliminating the previous repair flow requirement. This streamlines the upgrade process with automatic fallback handling.
Several crash fixes landed today. Frenck addressed a Volvo lock crash when API fields are missing, fixed Shelly repairs failing on uninitialized RPC devices, and corrected BraviaTV's missing SSDP dependency. Zach Wolf improved Roborock's network error handling during setup, while Paul Bottein fixed Yoto's OAuth flow with cloud credentials.
The development team also merged quality-of-life improvements including a state-based icon for Hue grouped lights, reduced Wyoming satellite disconnect logging to debug level, and better error handling for Immich file uploads.
Additional housekeeping included Bluetooth library updates, test improvements for notify domains, and StrEnum refactoring for the Renault integration.
What's next: These Tesla tracker changes align with Home Assistant's architecture standards for location entities. The MQTT protocol migration should improve performance for users with compatible brokers.
That's your Home Assistant development update. Back tomorrow with more changes from the core repository.