Trafficmaps

wscheer

execute the following command from the MagicMirror folder: “node serveronly”. This will start the server, after which you can open the application in your browser of choice.

Jeff

@wscheer
oh okay, I already did that and the command line said my page was created correctly.
But in teh browser it said page not found.

I think that’s a different problem and I have to handle that first…

Jeff

Now I can open the MM in the webbrowser.

What should I do now?

wscheer

@Jeff Ok so now if you load the page and you still see the broken image, the browser can help you find out what the problem is.

If you use firefox, hit F12 and reload the magic mirror page you can see if there are any errors being reported. When I was first testing mine, I had an typo in the api string and I couldn’t really see it until I looked at it in the browser.

Let me know if that helps, or post some screenshots of any errors and hopefully I can help :)

Jeff

@wscheer

I’ve installed Firefox:

Initializing MagicMirror.  logger.js:17:4
Loading core translation file: translations/de.json  logger.js:20:4
Loading core translation fallback file: translations/en.json  logger.js:20:4
Load script: modules/default/alert//alert.js  logger.js:20:4
Module registered: alert  logger.js:20:4
Bootstrapping module: alert  logger.js:17:4
Load script: modules/default/alert//classie.js  logger.js:20:4
Load script: modules/default/alert//modernizr.custom.js  logger.js:20:4
Load script: modules/default/alert//notificationFx.js  logger.js:20:4
Scripts loaded for: alert  logger.js:20:4
Load stylesheet: modules/default/alert//ns-default.css  logger.js:20:4
Styles loaded for: alert  logger.js:20:4
alert - Load translation: translations/de.json  logger.js:20:4
alert - Load translation fallback: translations/en.json  logger.js:20:4
Translations loaded for: alert  logger.js:20:4
Load script: modules/maproute//maproute.js  logger.js:20:4
Module registered: maproute  logger.js:20:4
Bootstrapping module: maproute  logger.js:17:4
Scripts loaded for: maproute  logger.js:20:4
Styles loaded for: maproute  logger.js:20:4
Translations loaded for: maproute  logger.js:20:4
Load stylesheet: css/custom.css  logger.js:20:4
Starting module: alert  logger.js:17:4
All modules started!  logger.js:17:4
maproute received a system notification: ALL_MODULES_STARTED  logger.js:20:4
maproute received a system notification: DOM_OBJECTS_CREATED  logger.js:20:4
GET 
http://dev.virtualearth.net/REST/v1/Imagery/Map/Road/40.4406,-79.9959/12 [HTTP/1.1 401 Unauthorized 108ms]

I think I have a wrong API access, but I think I did everything as described…

wscheer

@Jeff Ok now we are getting somewhere.

Try this:
In your browser, paste this url but add your bing maps api key at the end. Mine looks like this (i replaced some characters with #)
######ss9ZpK9lZjPRNo78Xp######xM_zjDmyQ2M5GmkzcOUhW2BYmO######-2

http://dev.virtualearth.net/REST/v1/Imagery/Map/Road/40.4406,-79.9959/12?mapSize=500,500&ml=TrafficFlow&key= ADD YOUR API KEY HERE

When you do that, you should see the map all by itself. That would tell you if it was an issue with your api key itself.

If that works, double check the api key was copied right in the config section
“api_key: ‘123456789’, // Your Bing maps api key”

Let me know what you find

Jeff

@wscheer

Okay your link with my API worked…

I put my API key in the maproute.js file as the default key. Maybe that is the problem.

How should the config.js file look?
Like this?

                latitude: '40.4406', // City latitude. Use google to get these coordinates
                longitude: '-79.9959', // City longitude
                map_zoom: '12', // 1 - 21
                map_layer: 'TrafficFlow', 
                map_size: '500', // Using this for both length and width
                api_key: 'xxxxx', // Your Bing maps api key
                updateInterval: 300000 // 5 min refresh

wscheer

@Jeff yeah. Just replace the xxxx with your API key.

Jeff

@wscheer
That’s what I did.

I really don’t know what’s going on.

Maybe I should just implement it as a final picture

wscheer

@Jeff ok Jeff I have an idea.

Can you look at your magic mirror page in server only mode again? Then if you right click and “inspect” the broken image you should see the url its trying to reach.

Compare that to the url I had you copy paste in with your API that worked.

Then if there is some sort of difference we should be able to track it down.