Frequently Asked Questions

Is there a more detailed set up guide?

Danny at Smart Home Pursuits has written a great guide providing step-by-step instructions for setting up a TeamTracker sensor including how to pull in information on upcoming games beyond what is available via the ESPN API from Google Calendar.

And here's another one by SHS at Smart Home Scenes. It goes into more detail on Custom API Configurations and how to exclude your sensors from the Recorder to keep your database size under control.

Will you add support for my favorite soccer team/league?

Chances are it is already supported, just not natively. ESPN has APIs for hundreds of soccer leagues. I have chosen to support only the top leagues natively. The rest can be added using a Custom API Configuration. There are just too many leagues. Their abbreviations vary by language and they overlap with each other as well as league abbreviations in other sports. Including the top leagues natively and allowing anyone to add whatever other ones they want to via a configuration seemed like the best way to handle all of the variations.

Why is the state of the sensor NOT_FOUND?

See the NOT_FOUND Troubleshooting section of the Wiki

Why is the state of the sensor unavailable?

See the unavailable Troubleshooting section of the Wiki

Does the sensor support sports such as rugby and water polo?

It might, but I haven't tested them to confirm.

The integration supports games between two competitors. As long as an ESPN API exists, it should be possible to set up a Custom API configuration to call it. If so, please update the Custom API Configuration portion of the Wiki with the information.

There may be sport-specific variances that cause it to fail. If you run into problems, please report them in the Issues section.

Does the sensor support sports such as tennis, golf, MMA, racing, etc?

Support of these sports is in beta.

The integration supports games between two competitors. Events with multiple competitors (i.e. golf, racing) or involving multiple competitions (i.e. tennis tournaments, MMA events) are only in beta at this time.

Why is my homeassistant_v2.db file growing since I started using the teamtracker integration?

By default, Home Assistant saves the prior states of sensors for 10 days. Because the team_tracker sensor updates every 10 seconds while a game in going on, all of these updates are saved. This can cause the database to grow significantly.

See the section on Turninng Off the Recorder to change the default functionality.

Where can I go if I need help?

This thread on the Home Assistant Community Forums has a number of people who can help you if you have questions. I check in pretty regularly.

I am also on r/homeassistant on Reddit and a member of the Home Assistant group on Facebook. You can also open up an issue or start a discussion and I will eventually see it, but the other places have a better chance of getting additional eyes on it and a quicker response.