Hi MagicMirror builders!

I programmed, or better said configured, a module that gets the traffic data from TomTom. The result is my module called MMM-TomTomTrafficIncidents. Please feel free to comment. This module displays traffic load and information where you don’t need a Google/MS account or leave Credit Card information. The traffic can be displayed absolute like other services commonly do. Or on a relative basis. Meaning if traffic has a speed limit of 50 km/h it will be marked green when people are driving 40-50. It will be red when it congested. Do you want to know where to drive fast? Use the absolute option. Very nifty option from TomTom.

Example in Beervana where I placed a marker on a brewery :
Absolute (slow and fast traffic):

Relative traffic (slower than normal):

Relative delay (showing only the differences with normal flow)

I’ve chosen to keep the code simple to make it clear that it is a wrap around the TomTom’s Maps SKD for Web. No things like new object().setThing().color().

The settings you can make:

• Location, size, and zoom level
• Type of traffic: absolute, relative of relative delay.
• Showing traffic reports and incidents
• Showing a marker (and size)
• Refresh rate
• Get the scripts and css local or from TomTom’s website.

I am very happy that TomTom offers the WebAPI. It is barely programming at all. I would recommend to make your own module with their MapSDK for the Web. The best part is that there is no credit card needed! A username with email address is enough. If you run out of data, you’ll get an error back. For personal use, it is very hard to reach this limit. Assuming hat you don’t refresh every 5 minutes of a very large area.

If you want to use your own map and only use the GEO information from TomTom, I would recommend to look at their other APIs on [https://developer.tomtom.com/#](TomTom Developer Portal)

Cheers, George!

Hello,

I’ve created a second module called MMM-NLDepartureTimes. This module shows the departure time at hubs and or group of stops where the departure time is grouped by destination in the Netherlands. Ideal if you use a hub that has multiple lines to your destination.

Here you see the hub Leidschenveen with the departures time of light-rail 3 and 4, Metro E, and street car 19. You can directly see when a light-rail or metro to Den Haag, or the street car to Leidschendam leaves.

Configuration opions
You can configure of which stops a hub exists and which lines to group on wich order.

A hub is what you define as a hub. You select the stops in an area you want to use and give it a name. In this example line 3,4 to Den Haag, line 3,4 to Zoetermeer, line E to Den Haag, and line E to Rotterdam are 4 stops on different locations.

The destination is also what you want. You can give the destination a name you like and select the lines that you want to see there. Here the stop for line 3,4 and the stop for line E to Den Haag are grouped. Even though all 3 lines have a different end point, they have a stop around Den Haag Centraal. Line E to Slinge is grouped in Rotterdam alone.

I think I managed to write down how to find your proper codes called TPCs. Configuration is very quirky because the data supplied is raw and extended.

Any feedback is welcome!

Cheers,
George

@robertybob
The strangest thing is that the module refers to /modules/MM-TomTomTrafficIncidents!!//!!MM-TomTomtrafficincidents.js.

On the TomTom forum we saw that you used sudo to read files. Don’t use root privileges to edit or view files. Alle the files in MM are from the user pi in the group users. To avoid potential user right issues, I asked to delete the whole moduel and clone a new one. Just sdetweil told you.

Because the module sees two slashes, I start think that a config in the module is not working. Did you test any other module for the MM? To see if these works. It could be that a small user handling goes wrong, but perhaps there is in deed an issue in my code. Although I tested it on a new MM installation.

I was thinking about this abbreviation as well. The reason why I choose for ‘voelt als’, is that it is a complete phrase. This makes it quicker to recognize for a small peek and first time readers.

Hello,

I’ve made a pull to change the Dutch text for ‘feels like’ from ‘gevoelstemperatuur’ to ‘voelt als’. The reason is that ‘voelt als’ is a lot shorter, which makes it a better fit and better to alligne. ‘Gevoelstemperatuur’ makes the line forecast module quite a bit wider. ‘Voelt als’ has a bonus for a quicker to read. The official term used by KNMI (Dutch Weather Service) is ‘gevoelstemperatuur’. A counter argue could be to stick to the official terms.

@MichMich suggested to start a poll to see what other people feel about it.

Hello,

I’ve created a second module called MMM-NLDepartureTimes. This module shows the departure time at hubs and or group of stops where the departure time is grouped by destination in the Netherlands. Ideal if you use a hub that has multiple lines to your destination.

Here you see the hub Leidschenveen with the departures time of light-rail 3 and 4, Metro E, and street car 19. You can directly see when a light-rail or metro to Den Haag, or the street car to Leidschendam leaves.

Configuration opions
You can configure of which stops a hub exists and which lines to group on wich order.

A hub is what you define as a hub. You select the stops in an area you want to use and give it a name. In this example line 3,4 to Den Haag, line 3,4 to Zoetermeer, line E to Den Haag, and line E to Rotterdam are 4 stops on different locations.

The destination is also what you want. You can give the destination a name you like and select the lines that you want to see there. Here the stop for line 3,4 and the stop for line E to Den Haag are grouped. Even though all 3 lines have a different end point, they have a stop around Den Haag Centraal. Line E to Slinge is grouped in Rotterdam alone.

I think I managed to write down how to find your proper codes called TPCs. Configuration is very quirky because the data supplied is raw and extended.

Any feedback is welcome!

Cheers,
George

Hi MagicMirror builders!

I programmed, or better said configured, a module that gets the traffic data from TomTom. The result is my module called MMM-TomTomTrafficIncidents. Please feel free to comment. This module displays traffic load and information where you don’t need a Google/MS account or leave Credit Card information. The traffic can be displayed absolute like other services commonly do. Or on a relative basis. Meaning if traffic has a speed limit of 50 km/h it will be marked green when people are driving 40-50. It will be red when it congested. Do you want to know where to drive fast? Use the absolute option. Very nifty option from TomTom.

Example in Beervana where I placed a marker on a brewery :
Absolute (slow and fast traffic):

Relative traffic (slower than normal):

Relative delay (showing only the differences with normal flow)

I’ve chosen to keep the code simple to make it clear that it is a wrap around the TomTom’s Maps SKD for Web. No things like new object().setThing().color().

The settings you can make:

• Location, size, and zoom level
• Type of traffic: absolute, relative of relative delay.
• Showing traffic reports and incidents
• Showing a marker (and size)
• Refresh rate
• Get the scripts and css local or from TomTom’s website.

I am very happy that TomTom offers the WebAPI. It is barely programming at all. I would recommend to make your own module with their MapSDK for the Web. The best part is that there is no credit card needed! A username with email address is enough. If you run out of data, you’ll get an error back. For personal use, it is very hard to reach this limit. Assuming hat you don’t refresh every 5 minutes of a very large area.

If you want to use your own map and only use the GEO information from TomTom, I would recommend to look at their other APIs on [https://developer.tomtom.com/#](TomTom Developer Portal)

Cheers, George!

I think I was a bit unclear. The thing is that every module uses its own variable names for longitude and latitude. By moving the variable out the config object as a variable, every module still requires their own variable to be set. While longitude and latitude are ‘global’ settings for the MagicMirror like language, and are not module specific like an API code.

I think it would be better to make long and lat a default config and document it.

Hello,

I am using and testing quite a few modules on my mirror that require longitude and latitude. Each module has written their own solution for this in the config section of the module. That is perfectly done.

Wouldn’t it be a good idea to add them to the core config? It sounds to me that longitude and latitude are regular setting like time format, language, a.s.o. Then add in documentation that you can find the latitude and longitude via https://www.latlong.net/ or another site.

I am willing to write text if needed.

George