Skip to content

Releases: vasqued2/ha-teamtracker

v0.14.9

22 Apr 12:52
41b86dd

Choose a tag to compare

  • Expand API limit to support college sports that do not have conference ID's
  • Update documentation

v0.14.8

19 Apr 00:28
03a8869

Choose a tag to compare

  • Added attributes for sport_path, league_path, team_conference_id, opponent_conference_id, and api_url

v0.14.8-beta

16 Apr 00:04

Choose a tag to compare

v0.14.8-beta Pre-release
Pre-release
  • Add attributes for sport_path, league_path, conference_id, and api_url

v0.14.7

09 Mar 04:56
15ac15f

Choose a tag to compare

  • Add season attribute to indicate pre-, regular, and other season types.

v0.14.6

25 Jan 22:39
691a214

Choose a tag to compare

Add team long names to sensor attributes

v0.14.5

16 Nov 18:09
a10b438

Choose a tag to compare

  • Use long name for MMA events

v0.14.4

05 Oct 12:29
f1aed24

Choose a tag to compare

  • Update functionality deprecated in HA 2024.10

v0.14.3

28 Aug 00:04
8ff4087

Choose a tag to compare

  • Minor fixes
  • Tutorial section in Readme (thx senbei123)

v0.14.2

28 Jul 17:39
c2815fc

Choose a tag to compare

  • Adds support for Doubles matches in Tennis for the Olympics

See README.md for an example using regular expressions in the team_id field to find the roster of a doubles match.

v0.14.1

27 Jul 00:09
a107aef

Choose a tag to compare

  • Added programmatic control of the sensor with the service call_api (beta)
  • This enables the dynamic retrieval of information for different teams without the need to create multiple sensors. It will simply reuse the same sensor. This is expected to be of value to meet the needs of dynamic voice requests.
  • Accepts four input parameters: sport_path, league_path, team_id, and conference_id (optional)
  • Service will dynamically change the sensor to the input parameters and refresh the sensor
  • Sensor will revert to original configuration on reboot

NOTE: This does not allow a single teamtracker sensor to support multiple teams at the same time. It simply allows the single supported team to be changed programmatically.

NOTE: The functionality and input parameters of the call_api service are subject to change as new uses emerge. If you have ideas or suggestions for specific use cases, open an Issue so they can be tracked.

Thanks to @dinki for the suggestion