Read the statement by Michael Teeuw here.
MMM-Flights Not Working
-
@KI6UVE
Your config.js should be as follows{ module: “MMM-Flights”, position: “middle_center”, config: { laMin: 33.183537, laMax: 32.849596, loMin: -117.204895, loMax: -116.790161, } },
Note the } without the comma closes off the config part. (With the comma, closes the module)
-
@KI6UVE it was only in the paste above
Here is the section in my config.js file: { module: “MMM-Flights”, position: “middle_center”, config: { laMin: 33.183537, laMax: 32.849596, loMin: -117.204895, loMax: -116.790161, },
you would have had a fatal startup error otherwise…
did u npm install in the module folder?
your config looks ok
-
@sdetweil said in MMM-Flights Not Working:
Got it working. Thanks to all!!
-
@KI6UVE what was it?
-
I was missing the } to close out the flights module.
My coordinates do not include the ocean, but my map extends the width of the entire screen to include areas outside my area of interest. Do you know if there is a way to constrain it to just the area of interest?
-
you may should choose another (smaller) module position,
middle_center
uses the whole screen.You can see the area of your coordinates in the map, there are small arrows in the area corners.
The map size can be controlled with css.
-
Thanks, bottom center is much better. I just compared the map to my iPad version of Flightradar and the MM module doesn’t seem to be showing any air traffic.
-
and the MM module doesn’t seem to be showing any air traffic.
I already mentioned the fix for this:
@karsten13 said in MMM-Flights Not Working:
laMin and laMax should be switched