I found a pws nearby and everything is working great now. Thanks for the help!!

You’re welcome. :thumbsup:

This might sound really ignorant but do I actually need PWS equipment to run this module? Can I not just receive and not transmit? My PWS is KTNMADIS13

No, you don’t need your own PWS equipment. I meant the pws that you chose from WeatherUnderground. It would be cool to have your own though.

The PWS that you gave me (KTNMADIS13) is either down, or not valid. I tested it and it does not work. As soon as I returned mine to my config, it fired right up.
You can try mine as a test. This is the whole line from the config:
pws: 'pws:KNYNEWYO103',
In any case, you’ll have to choose another pws from the WunderMap at WeatherUnderground because yours is not working. If you can’t manage that then I can get one for you and test it. I would need the name of your country, city, town, neighborhood if that is the case. Or the name of your nearest airport. They all have weather stations.

That usually means one or more of the following:

Your API key is entered incorrectly.
Your API key is not valid.
Your pws is entered incorrectly.
Your pws is down. Choose another.

I’ll test your pws on my machine if you tell me which one you are using.

{
module: ‘MMM-Traffic’,
position: ‘bottom_right’,
classes: ‘bright small’,
config: {
api_key: ‘api key redacted’,
mode: ‘driving’,
origin: ‘origin redacted’,
destination: ‘destination address redacted’,
arrival_time: ‘’,
route_name: ‘Home to Work’,
changeColor: true,
showGreen: false,
limitYellow: 5,
limitRed: 20,
traffic_model: ‘pessimistic’,
interval: 120000,
showWeekend: true,
allTime: false
}
},
{
module: “newsfeed”,
position: “bottom_bar”,
config: {
feeds: [

I copied my API key from Google directly but Iĺl register for another one and give that a shot.

So, just to be sure: After removing unnecessary properties you have a config.js that looks something like this minimal example

var config = {
  port: 8080,
  
  modules: [
		{
			module: "alert",
		},
		{
			module: "updatenotification",
			position: "top_bar"
		},
		[...]
		{
			module: 'MMM-Traffic',
			position: 'top_left',
			config: {
				api_key: 'your_apikey_here',
				origin: '4 Pennsylvania Plaza, New York, NY 10001',
				destination: '1 MetLife Stadium Dr, East Rutherford, NJ 07073'
			}
		},
  ]

};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}

with some content from the default config.js at the “[…]” places, your API-key instead of " ‘your_apikey_here’ " and possibly some lines commented out by prepending “//”, correct?

The fact that the MM2 starts without error message about config.js indicates, that the issue is within the properties you set, i.e. the origin/destination or the API key.
Some suggestions:

1. Did you try to run it with default properties of the MMM-Traffic module (the ones I copied above)? Of course you have to input your own API key.
2. Did you check whether your API key is valid?
   2.a Is your API key configured correctly? As far as I know you have to login into google account and there assign the key to a project and get the access restrictions right.
   2.b In case you didn’t copy the key: have you checked for typos?

If you use default config.js parameters and example parameters from MMM-Traffic module it should run. From there, you can incrementally add your changes and figure out, which property leads to the issue.

Also, do I need to do anything to the MMM-Traffic.js file defaults like adding the api_key or changing values to match my selections on the config.js file?

No. To include the MMM-Traffic module you just have to include it in your config.js (providing all the required settings).

@joeytuck said

Turns out that if you put Drive, instead of Dr, it won’t recognize it.

Where do you put Drive or Dr? In the readMe, possible values for “mode” are described to be ‘driving’, ‘walking’, ‘bicycling’, ‘transit’.

I suggest to delete or comment (adding // before the line) all not-required settings of MMM-Traffic at first to minimize possible sources for errors.

Do I need to add ’ ’ around numeric values as well?

Usually you don’t. It distinguishes between (for example) the NUMBER 5 and the TEXT containing “5”. To be sure, you should look at the default values and just do it in the same way. For example, arrival_time seems to require " " even though the given example “1445” also could have been a plain number (I guess the reason is the leading 0 at for example “0800” which gets ignored when inputting as number)

Also, you got some strange quotation marks ´ ´. Until now I thought, only " " and ’ ’ were valid.

pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.1.1 start /home/pi/MagicMirror
sh run-start.sh

Starting MagicMirror: v2.1.1
Loading config …
WARNING! Could not validate config file. Please correct syntax errors. Starting with default configuration.
Loading module helpers …
Initializing new module helper …
Module helper loaded: updatenotification
No helper found for module: helloworld.
All module helpers loaded.
Starting server on port 8080 …
Starting server op port 8080 …
Server started …
Connecting socket for: updatenotification
Sockets connected & modules started …
Launching application.

you are missing a , after showWeekend: true,

}
},
]

};

		module: "newsfeed",
		position: "bottom_bar",
		config: {
			feeds: [
				{
					title: "New York Times",
					url: "http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml"
				}
			],
			showSourceTitle: true,
			showPublishDate: true
		}
	},

{
		module:´MMM-Traffic´,
		position: ´bottom_right´
		classes: ´dimmed medium´,
		config:  {
			api_key: ´

´,
mode: ´driving´,
origin: ´´,
destination: ´´,
arrival_time: ´´,
route_name: ´Home to Work´,
changeColor: true,
showgreen: false,
limitYellow: 5,
limitRed: 20,
traffic_model: ´pessimistic´,
interval: 120000,
showWeekend: true
allTime: true
}
},
]

};

Okey first of, when in your terminal typ cd MagicMirror/modules/ this will get you directly to your modules folder.

after that you should type git clone https://github.com/SamLewis0602/MMM-Traffic.git
This command will create a new folder called MMM-Traffic and copy all files for the module.
When that is done you typ
cd MMM-Traffic to enter the MMM-Traffic folder.

When you have done that and are in the folder you type npm install, this will install all dependencies, i e stuff that is needed for the traffic module to work.

Then open your config.js file and find the last ]

Before that ] you add

{
	module: 'MMM-Traffic',
	position: 'top_left',
	classes: 'dimmed medium', //optional, default is 'bright medium', only applies to commute info not route_name
	config: {
		api_key: 'your_apikey_here',
		mode: 'driving',
		origin: '4 Pennsylvania Plaza, New York, NY 10001',
		destination: '1 MetLife Stadium Dr, East Rutherford, NJ 07073',
		arrival_time: '0800', //optional, but needs to be in 24 hour time if used.
		route_name: 'Home to Work',
		changeColor: true,
		showGreen: false,
		limitYellow: 5, //Greater than 5% of journey time due to traffic
		limitRed: 20, //Greater than 20% of journey time due to traffic
		traffic_model: 'pessimistic',
		interval: 120000, //2 minutes
		showWeekend: false,
		allTime: false
	}
},

Now you need to change the api key above where it says api_key: 'your_apikey_here',

replace your_apikey_here with the needed api key and make sure not to remove the ' around the api key.