Known Defects in the ESPN API

Defects in the ESPN API cannot be corrected by the sensor. It will simply report the incorrect information provided by ESPN.

The following defects in the ESPN API are known:

Defect	Description	Manifestation
timeouts not updated for NCAAF games	ESPN always reports that each team has 3 timeouts for NCAAF games. This information is not updated throughout the game.	The sensor will always report team_timeouts and opponent_timeouts as being 3. If desired, timeout information can be hidden in the ha-teamtracker-card by including show_timeouts: False in the card definition.
win_probability and timeouts not returned for basketball games	The API does not return win_probability or timeout information for basketball games.	win_probability and timeouts has a value of null and are not displayed on the card
Tennis API behaves inconsistently	The tennis API behaves extremely inconsistently across matches and devices/locations.	There is often a significant delay in status updates, both during and after matches. At other times it works fine. These variations have been observed even for different matches in the same tournament. The API also does not consistently translate into some languages supported by the other APIs, and even returns different results from different devices/locations when passed the same paraments.
NASCAR does not populate until after qualifying is complete	The NASCAR API does not return competitor information until after event qualifying is completed	The sensor will return a state of NOT_FOUND until qualifying is completed and the field is set. This means you generally will get a status of NOT_FOUND until less than 24 hours before the start of the race.
NASCAR does not consistently update lap data	NASCAR does not provide timely updates to lap information during the race.	The lap information returned in team_total_shots is updated sporadically during a NASCAR race. The sensor may display out of date lap information.
NASCAR start time is broadcast start	The API returns the start time as the start of the broadcast, not the start of the race.	If the race starts within 20 minutes of the broadcast start, everything will work as expected. If the race does not start within 20 minutes of the broadcast start, the sensor will shift from 5 second polling back to to 10 minute polling. This means, it could another 10 minutes after the race starts before the sensor detects it.
Cricket API Limitations	There are a number of limitations in the cricket API	See this wiki entry for details.

Defect	Description	Manifestation
shots_on_target not always updated for NHL games	The API generally returns Saves statistics (which is used to calculate shots_on_target) for NHL games, however an instance was caught where the information was not returned by the API until midway through a pre-season game.	shot_on_target has a value of null
opponent_logo not always returned for NBA games	The API generally returns opponent_logo information for NBA games, however for a preseason game against a non-NBA opponent, no logo was supplied.	opponent_logo set to a logo indicating an error
team_logo and opponent_logo may be outdated	The API generally returns team logos, however for a specific soccer team in a minor league, it was reported that the API returned an old logo that was recently replaced.	The old logo is returned instead of the new logo