Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tractive integration fails to create entities for one tracker (no errors, no entities) #141109

Open
guychozaicho opened this issue Mar 22, 2025 · 3 comments

Comments

@guychozaicho
Copy link

The problem

I have two Tractive trackers on the same account, same subscription (Premium), and both are active and reporting correctly in the Tractive app.

In Home Assistant:

  • Only one tracker creates sensor entities (activity, sleep, etc.)
  • The second tracker appears in core.device_registry but has no entities at all in core.entity_registry
  • All sensors show as "Unavailable" in the UI
  • No errors in logs, even with debug logging enabled for both custom_components.tractive and homeassistant.components.tractive

I have tried:

  • Removing/re-adding the integration
  • Manually cleaning up stale registry entries
  • Restarting HA
  • Forcing sync via toggling live tracking in Tractive app

The issue persists and seems like the integration is silently skipping or failing to create sensor entities for this tracker.

Would love help troubleshooting or adding debug hooks. Happy to provide logs, registry JSON snippets, or test any fixes.

What version of Home Assistant Core has the issue?

core-2025.3.3

What was the last working version of Home Assistant Core?

core-2025.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tractive

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tractive/

Diagnostics information

home-assistant_tractive_2025-03-22T12-09-40.216Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Image Image
@home-assistant
Copy link

Hey there @Danielhiversen, @zhulik, @bieniu, mind taking a look at this issue 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 issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign tractive Removes the current integration label and assignees on the issue, 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 issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


tractive documentation
tractive source
(message by IssueLinks)

@bieniu
Copy link
Member

bieniu commented Mar 22, 2025

Please enable debug logging for Tractive integration, restart HA, wait 20 minutes, disable debug logging and attach here a log file.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants