Skip to content

Conversation

@bieniu
Copy link
Member

@bieniu bieniu commented Sep 6, 2025

Breaking change

Proposed change

The Tractive website https://my.tractive.com/#/map states that it is not possible to turn on LED/Buzzer/Live tracking if the tracker is in the energy saving zone, so the switch entities should be unavailable in such a situation.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link

home-assistant bot commented Sep 6, 2025

Hey there @Danielhiversen, @zhulik, mind taking a look at this pull request as it has been labeled with an integration (tractive) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tractive can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign tractive Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes an issue where Tractive switch entities (LED, buzzer, live tracking) remain available even when the tracker is in energy saving mode, despite the Tractive API not allowing these operations in that state.

  • Marks switch entities as unavailable when tracker is in "POWER_SAVING" state
  • Updates the event handling to track power saving status
  • Adds comprehensive test coverage for the unavailable state scenario

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
homeassistant/components/tractive/__init__.py Adds power saving status detection to switch event payload
homeassistant/components/tractive/switch.py Updates availability logic to check power saving state
tests/components/tractive/test_switch.py Adds test for switch unavailability during power saving mode

@bieniu bieniu added this to the 2025.9.2 milestone Sep 6, 2025
@edenhaus edenhaus merged commit e5f99a6 into home-assistant:dev Sep 7, 2025
34 checks passed
@bieniu bieniu deleted the tractive-switches-unavailable branch September 7, 2025 14:09
@github-actions github-actions bot locked and limited conversation to collaborators Sep 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tractive Configuration Switches not working

5 participants