---
title: "TomTom"
description: "TomTom is a Marketplace integration for Home Assistant. It has 50 installs sharing analytics, needs the vendor's cloud and was last updated November 15, 2026."
canonical: "https://vulpo.app/integrations/marketplace/somansch-tomtom"
url: "https://vulpo.app/integrations/marketplace/somansch-tomtom.md"
last-updated: "2026-11-21"
version: "1.4"
---

# TomTom

> TomTom is a Marketplace integration for Home Assistant. It has 50 installs sharing analytics, needs the vendor's cloud and was last updated November 15, 2026.

From the [repository description](https://github.com/somansch/tomtom):

> TomTom integration for Home Assistant - traffic reports and your commute's travel time, with a dashboard card

[Open in My Home Assistant](https://my.home-assistant.io/redirect/marketplace_repository/?owner=somansch&repository=tomtom&category=integration)

On Home Assistant 2026.10 or older? [Open it in HACS](https://my.home-assistant.io/redirect/hacs_repository/?owner=somansch&repository=tomtom&category=integration)

## Supports

- **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor.
- **From the Marketplace**: Installed through the Marketplace, formerly HACS.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

### TomTom Setup

- **Display name**
- **Search mode**

### TomTom API key

- **API key**

### Defaults for new routes

- **Start for routes planned on the card (optional)**
- **Also create the way back**: A second entry, destination to start - on a motorway the way back is the other carriageway, and a jam on one is not one on the other. Named after this entry, with "return" added.
- **Days the route is kept up to date**
- **From**
- **Until**
- **From (way back)**
- **Until (way back)**
- **Look up the reports' details**: A route names what it runs through - kind, place and delay. With this on, Incident Details is asked for the rest of a new report: the whole stretch, where it starts and ends, the road numbers, TomTom's wording and its times - one request per five new reports, of 2,500 free a month. Only reports this entry shows are looked up. Off, the route costs no Incident Details request at all.
- **Minutes between detail lookups (empty = with every poll)**: How often the details are asked for, apart from how often the route itself is polled. With 30, a new report shows at once as the route tells it, and its details follow within half an hour - several reports in one request, and none for a jam that has gone again meanwhile.
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**

### Area (radius)

- **Area**
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **Only reports TomTom is sure of**: TomTom rates every report: certain, probable, risk\_of or improbable. A jam measured from moving cars is certain, a roadwork from a road authority probable, a driver's single report a risk. On, the first two are kept; off, the uncertain ones come along too.
- **Jam from this delay (minutes, 0 = every jam)**: A jam is reported once TomTom's figure for the delay it costs reaches this many minutes. 0 reports every jam, a few seconds' as well; 5 keeps the ones worth a detour. A jam TomTom sends no delay for counts as none.
- **Number of reports**
- **Update interval (minutes, 0 = manual only)**
- **Counts as new for (minutes, 0 = off)**

### Device tracker (radius)

- **Device tracker**
- **Radius (meters)**
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **Only reports TomTom is sure of**: TomTom rates every report: certain, probable, risk\_of or improbable. A jam measured from moving cars is certain, a roadwork from a road authority probable, a driver's single report a risk. On, the first two are kept; off, the uncertain ones come along too.
- **Jam from this delay (minutes, 0 = every jam)**: A jam is reported once TomTom's figure for the delay it costs reaches this many minutes. 0 reports every jam, a few seconds' as well; 5 keeps the ones worth a detour. A jam TomTom sends no delay for counts as none.
- **Number of reports**
- **Update interval (minutes, 0 = manual only)**

### Start: zone

- **Zone**

### Start: point on the map

- **Start**

### Start: address

- **Address**

### After setup

- **Start for routes planned on the card (optional)**
- **Also create the way back**: A second entry, destination to start - on a motorway the way back is the other carriageway, and a jam on one is not one on the other. Named after this entry, with "return" added.
- **Days the route is kept up to date**
- **From**
- **Until**
- **From (way back)**
- **Until (way back)**
- **Look up the reports' details**: A route names what it runs through - kind, place and delay. With this on, Incident Details is asked for the rest of a new report: the whole stretch, where it starts and ends, the road numbers, TomTom's wording and its times - one request per five new reports, of 2,500 free a month. Only reports this entry shows are looked up. Off, the route costs no Incident Details request at all.
- **Minutes between detail lookups (empty = with every poll)**: How often the details are asked for, apart from how often the route itself is polled. With 30, a new report shows at once as the route tells it, and its details follow within half an hour - several reports in one request, and none for a jam that has gone again meanwhile.
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Warn when the month's requests run low or will not last**
- **Warn from this share of the month's requests**: The first warning comes when the projection reaches this share; a second one when it reaches 100 %.
- **Incident Details requests a day, at most (0 = no limit)**: All entries together, counted from midnight to midnight UTC. Once the day's limit is reached no more are sent until the next day: areas and trackers show no TomTom reports meanwhile, and a route's new reports come without their details. 80 a day makes the 2,500 free requests last the month.
- **Warn when the day's requests run low or out**
- **Warn from this share of the day's requests**: The first warning comes at this share; a second one when all are used.
- **blitzer.de**
- **Lufop**
- **Lufop API key**: Checked when it is given and when Lufop is switched on; one already saved is kept by leaving the field empty.
- **Lufop: country**: The one country every entry asks Lufop for - the free plan allows France, Belgium and Switzerland.
- **API key**
- **Area**
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **Only reports TomTom is sure of**: TomTom rates every report: certain, probable, risk\_of or improbable. A jam measured from moving cars is certain, a roadwork from a road authority probable, a driver's single report a risk. On, the first two are kept; off, the uncertain ones come along too.
- **Jam from this delay (minutes, 0 = every jam)**: A jam is reported once TomTom's figure for the delay it costs reaches this many minutes. 0 reports every jam, a few seconds' as well; 5 keeps the ones worth a detour. A jam TomTom sends no delay for counts as none.
- **Number of reports**
- **Update interval (minutes, 0 = manual only)**
- **Counts as new for (minutes, 0 = off)**
- **Device tracker**
- **Radius (meters)**
- **Reports**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **blitzer.de**
- **Lufop**
- **Only reports TomTom is sure of**: TomTom rates every report: certain, probable, risk\_of or improbable. A jam measured from moving cars is certain, a roadwork from a road authority probable, a driver's single report a risk. On, the first two are kept; off, the uncertain ones come along too.
- **Jam from this delay (minutes, 0 = every jam)**: A jam is reported once TomTom's figure for the delay it costs reaches this many minutes. 0 reports every jam, a few seconds' as well; 5 keeps the ones worth a detour. A jam TomTom sends no delay for counts as none.
- **Number of reports**
- **Update interval (minutes, 0 = manual only)**
- **Zone**
- **Start**

Texts from the code of [somansch/tomtom](https://github.com/somansch/tomtom).

## Entities

- **Binary sensors**: Quota at risk
- **Numbers**: New for
- **Sensors**: Reports, All speed cameras, New speed cameras, Travel time, Traffic delay, Route length, TomTom requests this month, All requests this month, Incident Details this month, Routing this month, Geocoding this month, Reverse Geocoding this month, and 4 more

## Actions

- **Refresh**: Immediately fetch the latest reports for one TomTom area, route or tracker, instead of waiting for its next scheduled poll - and, for a live route, the route itself first. Returns the reports.
  Fields: Area, route or tracker

## Troubleshooting

- **Repair notices**: Notices it can show in Settings, Repairs:
  Is not delivering, Is not answering, The day's Incident Details requests are used

## From the README

> Unofficial. Not affiliated with, endorsed by or supported by TomTom. "TomTom" and its logo are trademarks of TomTom International B.V.
>
> Available languages: English, Deutsch, Français, Español, Italiano, Nederlands, Polski, Português, Čeština, Dansk, Eesti, Suomi, Ελληνικά, Magyar, Bahasa Indonesia, 日本語, 한국어, Lietuvių, Latviešu, Norsk bokmål, Română, Русский, Slovenčina, Svenska, ไทย, Türkçe, Català, 繁體中文, العربية, עברית - AI-translated apart from English and German; corrections are welcome as pull requests.

From the README of [somansch/tomtom](https://github.com/somansch/tomtom#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened.

## At a glance

- Kind: Marketplace integration
- Category: [Vehicles and transport](https://vulpo.app/integrations/category/vehicles-and-transport.md), Cars and EVs
- Number: 50 installs sharing analytics; 9 GitHub stars
- Connection: Needs the vendor's cloud
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: v1.3.1, last updated November 15, 2026
- Domain: `tomtom`
- Source: <https://github.com/somansch/tomtom>
- Issues: <https://github.com/somansch/tomtom/issues>
- Screenshot: https://vulpo.app/integrations-img/a0cd367d6b38eed3.webp (from somansch/tomtom's README)
- Screenshot: https://vulpo.app/integrations-img/7db0e27f1055e2fd.webp (from somansch/tomtom's README)
- Screenshot: https://vulpo.app/integrations-img/8345a023df7e470e.webp (from somansch/tomtom's README)

In Vulpo: Chart card, Apple Watch

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-11-21. Source: https://vulpo.app/integrations/marketplace/somansch-tomtom

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/somansch-tomtom
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml
