Integration seventeentrack is get packages action throws error

[regevbr]

The problem

seventeentrack.get_packages errors all the time

What version of Home Assistant Core has the issue?

core-2025.5.1

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

seventeentrack

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

action: seventeentrack.get_packages
data:
  config_entry_id: 291f0b247043d13d5e687f3f0b1eb95c

Anything in the logs that might be useful for us?

Logger: homeassistant.components.seventeentrack
Source: helpers/update_coordinator.py:380
integration: 17TRACK ([documentation](https://www.home-assistant.io/integrations/seventeentrack), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+seventeentrack%22))
First occurred: May 12, 2025 at 09:57:31 (143 occurrences)
Last logged: 10:30:39

Unexpected error fetching seventeentrack data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/seventeentrack/coordinator.py", line 61, in _async_update_data
    summary = await self.client.profile.summary(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        show_archived=self.show_archived
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/pyseventeentrack/profile.py", line 111, in summary
    for kind in summary_resp.get("Json", {}).get("eitem", []):
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'

Additional information

No response

[home-assistant[bot]]

Hey there @shaiu, mind taking a look at this issue as it has been labeled with an integration (seventeentrack) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of seventeentrack 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 seventeentrack 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)}}

---

seventeentrack documentation seventeentrack source _{^{(message by IssueLinks)}}

[kedar-calangutkar]

+1. Seeing the same issue.

[SmallScreenDesign]

Same here

[moryoav]

Same here. Seems like get_packages is broken in latest version. Now that the attributes were removed, I guess that's the correct way we're supposed to use to get the package details?

[jarooij]

Same issue here. You need to restart Home Assistant to get it running again, but after a while the same error(s) occure.

[ChrisThomas42]

Same issue, for me a restart doesn't clear the issue even temporarily.

[rapiqui]

Same problem here. HS 2025.5.2

[shaikedem]

same issue

[kellyatkinson]

Glad to see others with this issue - but commenting "same here" just bloats all our notifications. Follow this thread instead by subscribing (up there on the right sidebar).

[miguellandre]

Here in version 2025.5.3 the same error continues

[jarooij]

Delete your account in the integration, restart Home Asistant and then login with your credentials in 17Track again. That did the trick for me. Pay attention that you get a new config_entry_id. This is e.g. needed for this solution https://smarterkram.de/community/postid/1585/

[IoSonoAndreaZ]

Delete your account in the integration, restart Home Asistant and then login with your credentials in 17Track again

thank you, now the service works!

[kellyatkinson]

Delete your account in the integration, restart Home Asistant and then login with your credentials in 17Track again. That did the trick for me. Pay attention that you get a new config_entry_id. This is e.g. needed for this solution

This tactic did not work for me; I have now (several times) deleted the integration, restarted, and created a new 17Track integration. I still end up with a sensor for each status that contains the number of packages, but no attributes that provide any information about specific packages.

[decompil3d]

I still end up with a sensor for each status that contains the number of packages, but no attributes that provide any information about specific packages.

Those attributes were removed in 2025.5.0. You'll need to make a trigger template to get that back. There's another issue tracking how to do that here. This issue was about the action call failing. Seems to work now (and I didn't have to do the remove and re-add workaround).

[spanzetta]

It seems that now there is another issue..

The result from the API call using this integration, is different from results from mobile App..

2 examples..

• not found in HA but in transit in the 17TRACK app
• Italy (as location) in HA but more detailed info (Bologna Hub Espresso) in 17TRACK app

Why this difference?

[davux]

The only person not having anyrhing to say about the issue is @shaiu.

Dear @homeassistant team, it really feels like this integration is not actively maintained. Maybe time to remove it?

[SmallScreenDesign]

it seems 17track added a CAPTCHA for the web login so I suppose this broke the integration?

[IoSonoAndreaZ]

the interface on website is completely changed and the integration does not work anymore, at least for me

[spanzetta]

the interface on website is completely changed and the integration does not work anymore, at least for me

I noticed the web interface change.. but in my case the integration is still working.. (action 17TRACK: Get packages returns all my packages)

[spanzetta]

I spoke too early.. I updated Core to just released 2025.6 and .. it stopped working! Error is "Failed setup, will retry: 'NoneType' object has no attribute 'get'"

[hamanolo]

It doesn't work for me either! I deleted everything and now it gives me a login error but the credentials are correct...

[IoSonoAndreaZ]

guys, just go to 17track website... it's completely renewed, they surely changed everything even on API side... the integration probably must be rewritten, hopefully not from scratch....

[shaiu]

The only person not having anyrhing to say about the issue is @shaiu.

Dear @homeassistant team, it really feels like this integration is not actively maintained. Maybe time to remove it?

I don't work for Home Assistant. I do this on my own time (which is not a lot). This is open source and you are very welcome to do anything you want

[spanzetta]

Dear @shaiu you are right that since it's open source in theory anyone could make changes.. but I suspect that this will not happen (otherwise someone would have already jumped in) .. with the result that your very nice job will become no longer usable from many people.

[shaiu]

Dear @shaiu you are right that since it's open source in theory anyone could make changes.. but I suspect that this will not happen (otherwise someone would have already jumped in) .. with the result that your very nice job will become no longer usable from many people.

I agree, it was more to make a point. Hopefully I'll look into it in the next week or so.

[davux]

I don't work for Home Assistant. I do this on my own time (which is not a lot). This is open source and you are very welcome to do anything you want

Everyone's free of course. Which is why being the maintainer of an official HA integration is opt-in.

The concept of Quality Scale comes from HA, not from me, precisely to account for each maintainer's level of availability. With no intention to insult anyone, the integration probably isn't meeting Bronze. No emotions there. HA has support for local integrations, HACS etc. so I'm just suggesting that path.

Edit: The integration isn't marked as Bronze, so not sure what the expectation is.

[IoSonoAndreaZ]

I don't work for Home Assistant. I do this on my own time (which is not a lot). This is open source and you are very welcome to do anything you want

Everyone's free of course. Which is why being the maintainer of an official HA integration is opt-in.

The concept of Quality Scale comes from HA, not from me, precisely to account for each maintainer's level of availability. With no intention to insult anyone, the integration probably isn't meeting Bronze. No emotions there. HA has support for local integrations, HACS etc. so I'm just suggesting that path.

Edit: The integration isn't marked as Bronze, so not sure what the expectation is.

Nobody claimed it was bronze or gold or whatever and I don't see the point in criticizing the maintainer... it is true that 17track is a bit of a mess by itself and they also changed some code. We have few choices I suppose, not using the integration, wait that someone fixes it, fix it by ourselves. This place should be for reporting bugs, well it was done, and every day I receive some notification by someone complaining for the issue already reported.... it's pointless.

[davux]

I wasn't criticizing the maintainer but saying the integration looks like it's not actively maintained. It can happen, and you can have a different perception but either way it's not a dirty word.

[IoSonoAndreaZ]

I wasn't criticizing the maintainer but saying the integration looks like it's not actively maintained. It can happen, and you can have a different perception but either way it's not a dirty word.

it's maintained by one person at best effort... i'm not able to help, maybe you too... that's all

[issue-triage-workflows[bot]]

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.