MM & Google Maps Traffic

strawberry 3.141

@birdy you are missing quotes around the drivin mode, should be mode: 'driving'

devtech8

@Mirrorolentia - I was thinking of trying this too, but looks like you have made some progress. I hope to dig into what you have later this week. I had seen some further customization I would like to add when time allows. Thanks for the work on this!

Mirrorolentia

@devtech8
Sure that would be great! Thanks!

birdy

@Mirrorolentia - wow, thx!! I will test it later :) can’t await

birdy

so, as a complete noobie, I just pasted the code (adding Google Api key) in both files.

I can see, there is a gap in the corner (I hope for the map) and if I get you correctly, the map will load “soon”(?).

Thank you one more time and will keep u posted.

Cheers
Birdy

Mirrorolentia

@birdy
Yes that is correct. You will need to copy the lines from /global module**/ all the way till end…somehow the comments didn’t embed the code correctly

birdy

somehow it’s not working:

Mirrorolentia

@birdy
Seems like the MM system didn’t initialize the module itself :(
Are you seeing any errors on the console from where you run “node serveronly” or on the chromium browser i.e from More Tools–> Developer Tools–>Console.

birdy

you mean like this:

Connecting socket for: MMM-Traffic
MMM-Traffic helper started ...
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:8080
Whoops! There was an uncaught exception...
{ Error: listen EADDRINUSE :::8080
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1258:14)
    at listen (net.js:1294:10)
    at net.js:1404:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:389:7)
    at startup (bootstrap_node.js:149:9)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

Mirrorolentia

@birdy
Sorry for the delayed response. Got caught with stuff :(
By any chance do you have some other server running in parallel which is also listening on 8080 and using any available IPv6 address. Ideally you should have only “node” running with the specified port
You can check this with netstat.

netstat  -nalp | grep 8080

tcp6       0      0   ::: 8080                 ::: *                    LISTEN      2350/node
tcp6       0      0 ::1:43558               ::1:8080                ESTABLISHED 2103/libpepflashpla
tcp6       0      0 ::1:8080                ::1:43558               ESTABLISHED 2350/node

You can try killing that service (In the last column i.e 2350/node, 2350 represents PID. You can use "kill -9 ") and then probably restart the Magic Mirror.
Also this may not be related to the actual problem.
Please see if you can post your config.js.