core Tractive Sensors are all reporting Unavailable since a few days

The problem

Hello, Everything used to work perfectly, but since a few days, all the Tractive sensors report Unavailable . All the Diagnostic part work great though.

I tried deleting and reinstalling the Device but the problem remains. Thanks for your help!

What version of Home Assistant Core has the issue?

System Information version | core-2025.8.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true container_arch | amd64 user | root virtualenv | false python_version | 3.13.3 os_name | Linux os_version | 6.12.41-haos arch | x86_64 timezone | America/Toronto config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.5 Stage | running Available Repositories | 2172 Downloaded Repositories | 33

AccuWeather
can_reach_server | ok -- | -- remaining_requests | 45

Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor
host_os | Home Assistant OS 16.1 -- | -- update_channel | stable supervisor_version | supervisor-2025.08.3 agent_version | 1.7.2 docker_version | 28.3.3 disk_total | 234.0 GB disk_used | 52.7 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | AdGuard Home (5.3.2), Plex NAS (1.42.1.10060-4e8b05daf-ls278), Prowlarr NAS (2.0.5.5160-ls125), Sonarr (4.0.15.2941-2), qBittorrent (5.1.2-7), Radarr (5.26.2.10099), Get HACS (1.3.1), Studio Code Server (5.19.3), Tailscale (0.25.0), Hydroqc Add-on (v2.0.0-1), Mosquitto broker (6.5.1), Overseerr (1.34.0), changedetection (0.50.11), Advanced SSH & Web Terminal (21.0.2), Home Assistant Google Drive Backup (0.112.1), Music Assistant Server (2.5.8), Cloudcommander (18.7.3), Spotify Connect (0.15.0), Notifiarr (0.8.3), Samba share (12.5.2), FTP (5.3.2), Nextcloud (31.0.8), Portainer (2.33.0), Sabnzbd (4.5.3), SABnzbd (0.5.0), Newt Add-on (1.4.2), Cloudflared (5.3.8), OpenSpeedTest (v2.0.6), ngrok Client Installer (Unofficial) (15.0.5.3.0), Lidarr NAS (2.13.3.4711), eufy-security-ws (1.9.3), Frigate (0.16.0), HassOS SSH port 22222 Configurator (0.9.3), Glances (0.21.1), Rclone Backup (3.3.4), Tautulli (4.2.1), Filebrowser (2.42.5), Home-Assistant-Matter-Hub (3.0.0-alpha.87)

Dashboards
dashboards | 4 -- | -- resources | 21 views | 2 mode | storage

Network Configuration
adapters | lo (disabled), enp2s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth87cc3ac (disabled), vethcad6720 (disabled), vetha5077c0 (disabled), veth6573f0e (disabled), veth0a60a72 (disabled), vethd95be71 (disabled), veth4c90ff6 (disabled), veth20a4004 (disabled), vethe5288d1 (disabled), vethe4bee7a (disabled), veth2c5d6b6 (disabled), veth1bba40e (disabled), veth8caec6f (disabled), vethcaef93f (disabled), vethd04cc7d (disabled), vethc059d7c (disabled), vethb8d27ee (disabled), vethc9cd1f2 (disabled), vethde1ac5b (disabled), veth09aa42f (disabled), vetheebba0a (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), enp2s0 (192.168.2.10/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth87cc3ac (), vethcad6720 (), vetha5077c0 (), veth6573f0e (), veth0a60a72 (), vethd95be71 (), veth4c90ff6 (), veth20a4004 (), vethe5288d1 (), vethe4bee7a (), veth2c5d6b6 (), veth1bba40e (), veth8caec6f (), vethcaef93f (), vethd04cc7d (), vethc059d7c (), vethb8d27ee (), vethc9cd1f2 (), vethde1ac5b (), veth09aa42f (), vetheebba0a () ipv6_addresses | lo (::1/128), enp2s0 (fd1b:c992:9b6a:208b:7f87:b6d5:93a1:6490/64, fe80::cf6d:e585:b8f8:8919/64), docker0 (fe80::e0bc:9aff:fe4e:e27/64), hassio (fe80::3046:a9ff:febd:ff75/64), veth87cc3ac (fe80::3419:c3ff:febc:9c/64), vethcad6720 (fe80::f87b:abff:fed3:e972/64), vetha5077c0 (fe80::7c31:9bff:fee6:1d9f/64), veth6573f0e (fe80::4bc:f5ff:fe49:d221/64), veth0a60a72 (fe80::20b3:9fff:fe02:4ef8/64), vethd95be71 (fe80::9837:edff:fe5e:4493/64), veth4c90ff6 (fe80::5c5e:bcff:fe38:6bd7/64), veth20a4004 (fe80::4f:1dff:fecb:6e7d/64), vethe5288d1 (fe80::5053:32ff:feb4:c72a/64), vethe4bee7a (fe80::5887:7ff:fe41:d963/64), veth2c5d6b6 (fe80::684a:c3ff:fe72:1af2/64), veth1bba40e (fe80::45a:31ff:fed7:ca4e/64), veth8caec6f (fe80::ecda:88ff:fee0:5ec1/64), vethcaef93f (fe80::6c82:bdff:fec4:dd6/64), vethd04cc7d (fe80::dc92:3eff:fe81:655d/64), vethc059d7c (fe80::7819:6aff:fe8e:7f7e/64), vethb8d27ee (fe80::14bd:5bff:fe8d:f9ee/64), vethc9cd1f2 (fe80::387a:84ff:fed8:638d/64), vethde1ac5b (fe80::9098:81ff:fe64:377/64), veth09aa42f (fe80::c888:a4ff:fe5e:46f9/64), vetheebba0a (fe80::bc5d:67ff:fe1d:e908/64) announce_addresses | 192.168.2.10, fd1b:c992:9b6a:208b:7f87:b6d5:93a1:6490, fe80::cf6d:e585:b8f8:8919

Recorder
oldest_recorder_run | August 23, 2025 at 12:57 PM -- | -- current_recorder_run | September 1, 2025 at 5:57 PM estimated_db_size | 162.59 MiB database_engine | sqlite database_version | 3.48.0

SpotifyPlus
integration_version | v1.0.156 -- | -- clients_configured | 1: François (premium) api_endpoint_reachable | pending

What was the last working version of Home Assistant Core?

No response

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

config_entry-tractive-01K493YXPD9KMDJ1766THJGE9V.json

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

Sep 04 '25 01:09 Peskinator

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)}}

Sep 04 '25 01:09 home-assistant[bot]

I can confirm that, Tractive has stopped sending "wellness" data through its API. If this situation persists, these entities will need to be removed.

Sep 04 '25 07:09 bieniu

It's a shame they removed it without informing the users. :(

Sep 04 '25 13:09 EdKo66

Bummer about the removal. It's a shame. :(

Sep 04 '25 13:09 deltamikeromeo

Maybe it's just an error on their side? I can try to contact them if this is still the case in a few days. I am pessimistic because the data are still working in the app itself. For what it worth: I stopped receiving data from those sensors on September 1st, around 4am EST.

Sep 04 '25 14:09 Peskinator

Mine went offline at that exact time as well.

On Thu, Sep 4, 2025 at 8:39 AM Peskinator @.***> wrote:

Peskinator left a comment (home-assistant/core#151651) https://github.com/home-assistant/core/issues/151651#issuecomment-3254053360

Maybe it's just an error on their side? I can try to contact them if this is still the case in a few days. I am pessimistic because the data are still working in the app itself. For what it worth: I stopped receiving data from those sensors on September 1st, around 4am EST.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/151651#issuecomment-3254053360, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOTSSYMD7WQ3BDBJFSEYBMD3RBFI7AVCNFSM6AAAAACFSJ6R2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJUGA2TGMZWGA . You are receiving this because you commented.Message ID: @.***>

Sep 04 '25 14:09 deltamikeromeo

I have contacted them through a form, but not sure if they will respond the way we hope for.

On Thu, Sep 4, 2025 at 4:39 PM Peskinator @.***> wrote:

Peskinator left a comment (home-assistant/core#151651) https://github.com/home-assistant/core/issues/151651#issuecomment-3254053360

Maybe it's just an error on their side? I can try to contact them if this is still the case in a few days. I am pessimistic because the data are still working in the app itself. For what it worth: I stopped receiving data from those sensors on September 1st, around 4am EST.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/151651#issuecomment-3254053360, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4G7II5T7OMCUKVNLMPPFT3RBFI7AVCNFSM6AAAAACFSJ6R2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJUGA2TGMZWGA . You are receiving this because you commented.Message ID: @.***>

Sep 04 '25 14:09 EdKo66

It's a shame they removed it without informing the users.

The integration does not use the official Tractive API (because it does not exist) but their internal one, they do not have to inform anyone about changes.

Maybe it's just an error on their side?

The integration uses the same API used on the https://my.tractive.com/#/map website. This website doesn't currently display "wellness" information, so I assume this is an intentional change and not a bug.

I am pessimistic because the data are still working in the app itself.

The mobile app likely uses a different API or has different permissions.

Sep 04 '25 19:09 bieniu

Unfortunately I think it is intentional, as now this is on their website:

Some features such as Wellness Monitoring, Augmented Reality and Power Saving Zones are only available in the mobile app.

Sep 05 '25 02:09 xpucu

That's a shame -- they have a premium product, it should have premium features.

Sep 05 '25 22:09 mcblum

The change is intentional as confirmed by the feedback i got today from a ticket with Tractive. The message was politically correct but sounded like “we’ll consider you feedback when pigs will fly”. So i guess this is it.

Sep 07 '25 07:09 leonardpitzu

Could we just use the mobile API's? I can help document them.

Sep 08 '25 08:09 Wolfhound905

Could we just use the mobile API's?

Of course, if we can document this API. But this isn't a matter of integration, but of backend library https://github.com/zhulik/aiotractive

Sep 08 '25 09:09 bieniu

That was too good to continue, they had to destroy that. Why keeping something nice & convenient when we can just make our customers life miserable?

Sep 08 '25 20:09 philippe44

Could we just use the mobile API's?

Of course, if we can document this API. But this isn't a matter of integration, but of backend library https://github.com/zhulik/aiotractive

I am making the necessary changes to aiotractive. I'll post a comment here once I am done.

Sep 08 '25 23:09 Wolfhound905

@bieniu the aiotractive hasn't been updated in a year, I did make a PR. Here is my fork if you would like to test! I am also going to add a few more functions for the new features like Low battery.

/activity/day_overview response

{
	"progress": {
		"achieved_minutes": 191,
		"goal_minutes": 160,
		"current_streak": 1
	},
	"hourly_distribution": [ 0, 0, 0, 1, 2, 0, 0, 33, 17, 14, 24, 52, 30, 8, 13, 6, 2, 0, 0, 0, 0, 0, 0, 0],
	"best_day": false,
	"activity_distribution": [
		{
			"category": "active",
			"current": 191.0,
			"average": null
		},
		{
			"category": "calories",
			"current": 252.0,
			"average": null
		},
		{
			"category": "resting",
			"current": 6.3,
			"average": null
		}
	],
	"benchmarks": {
		"minutes_active": null,
		"ranking_percentage": null,
		"distribution": {
			"values": [
				0.0281, 0.0241, 0.0502, 0.0181, 0.0301, 0.0301, 0.0402, 0.0321, 0.0502, 0.0482, 0.0723, 0.0763, 0.0803, 0.0863, 0.0562, 0.0643, 0.0703, 0.0602, 0.0321, 0.0221, 0.012, 0.008, 0.0, 0.008
			],
			"bin_size_minutes": 20
		},
		"breed_id": null,
		"age_group": "ADULT"
	}
}

Sep 09 '25 00:09 Wolfhound905

I have created my own PyPi package for this. It's a drop in replacement called pytractive. While I did not make a pr for Homeassistant, I did test local development and made sure the package didn't break anything.

PyPi Repo Homepage

Sep 09 '25 16:09 Wolfhound905

@Wolfhound905 Thanks for your work. From what I can see, your fork of the library is working. Unfortunately, the API doesn't push events with "wellness" data, so a change will be necessary on the integration side. However, I encourage you to open a PR in the aiotractive repository with your modification. At this time, we don't have a real need to change the backend library. If your PR is ignored or rejected, then we can consider migrating to your fork.

Sep 09 '25 18:09 bieniu

Frustrating isn't it :-( - I used the data quite a bit through the HA integration and Grafana.

According to the HA Tractive page, there are 1695 people using the integration - maybe we should all raise a ticket with Tractive requesting access to the API.

My concern is they block the mobile API to any requests not coming from their own mobile app.

Sep 12 '25 13:09 happy-chap

I use this integration to make sure my SD is getting enough activity on our quiet days. So let me know what I can do to help any I will. It's important that I keep her active and happy; I don't always have the cognitive capacity to remember to check the app for that information.

Sep 12 '25 15:09 chicknlil

I use this integration to make sure my SD is getting enough activity on our quiet days. So let me know what I can do to help any I will. It's important that I keep her active and happy; I don't always have the cognitive capacity to remember to check the app for that information.

Same, amongst other sensors. Also is "SD" for Significant Dog ? If this is the case this is brilliant :)

Sep 12 '25 15:09 Peskinator

I received the following response from Tractive:

"We are currently reviewing this internally. I will get back to you with more information early next week."

Sep 12 '25 15:09 tim-99

Also is "SD" for Significant Dog ? If this is the case this is brilliant :)

Alas, I'm not brilliant. SD is for Service Dog. And technically she's in training. We like to BORK at the cats.

Sep 12 '25 15:09 chicknlil

That is why I use tractive for my service dog (ptsd).

Op vr 12 sep 2025, 17:52 schreef chicknlil @.***>:

chicknlil left a comment (home-assistant/core#151651) https://github.com/home-assistant/core/issues/151651#issuecomment-3285816666

Also is "SD" for Significant Dog ? If this is the case this is brilliant :)

Alas, I'm not brilliant. SD is for Service Dog. And technically she's in training. We like to BORK at the cats.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/151651#issuecomment-3285816666, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4G7IIGYLPBHMI4D4CVGJD3SLT4JAVCNFSM6AAAAACFSJ6R2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBVHAYTMNRWGY . You are receiving this because you commented.Message ID: @.***>

Sep 12 '25 15:09 EdKo66

Also is "SD" for Significant Dog ? If this is the case this is brilliant :)

Alas, I'm not brilliant. SD is for Service Dog. And technically she's in training. We like to BORK at the cats.

Sorry! I didn't know that acronym!

Sep 12 '25 16:09 Peskinator

According to the HA Tractive page, there are 1695 people using the integration - maybe we should all raise a ticket with Tractive requesting access to the API.

The more people write to the support a request to restore wellness events and explain to them that they broke Home Assistant integration, the greater the chance that they will revert their change.

Sep 12 '25 16:09 bieniu

As Home Assistant isn't a native Tractive App, we're currently checking this - I'll come back to you beginning next week.

The response I got from Tractive

Sep 12 '25 19:09 EdKo66

I made a request to Tractive as well.

Sep 12 '25 19:09 philippe44

I did some pressure on them...

"Hello,

thank you for your efforts.

Please consider this: If you allow your superiors to make stupid decisions, Tractive will lose over 1,000 customers in one fell swoop. This cannot be in the company's best interests."

Sep 13 '25 02:09 tim-99

I sent such a message:

I'm one of the developers working on the Tractive integration for Home Assistant https://www.home-assistant.io/ The integration uses the Tractive API used on the website https://my.tractive.com/#/map This is not a public API, but I assume Tractive doesn't mind it being used since you provided us the Client ID https://github.com/zhulik/aiotractive/pull/16

For over a week now, we have been observing that wellness data is not available via this API (https://channel.tractive.com/3/channel endpoint), which means that a very important part of the integration with Home Assistant has simply stopped working.

Home Assistant usage statistics show that over 1,600 people are currently using the Tractive integration (considering that only a fraction of users enable statistics sending, this number should be multiplied by 3 or even 4) https://analytics.home-assistant.io/integrations/ So several thousand Tractive tracker users are unhappy that the Home Assistant integration has been broken.

Therefore, I kindly ask Tractive to reconsider this change and reverse it so that wellness data is once again sent via the aforementioned API endpoint. The Home Assistant community would be very grateful, and many users will remember which manufacturer to choose when choosing a new tracker.

Sep 13 '25 08:09 bieniu