I have just migrated this to the WeatherBit API as Wunderground are cancelling the free service :( This forces an update of the module and a new config! I’ve updated the read me in GitHub, so please take a look.

@twosquirrels I’m so sorry. Fortunately I got it right in the git-hub docs!!

@fwood04 hi, you may be seeing errors for this module, the FAA changed stuff and broke the module, I’ve just fixed it so you should be good to update.

@twosquirrels you may be seeing that the MMM-FAA-Delay module is broken, the FAA changed their code and did not let anyone know or put a proxy/web forward in place :( I have updated the code and added a flag displayWeather to the config so that when you update you don’t have to go in and hack the new code again.

The FAA have update their API and as a result broke this module. There is an updated version now in the git repository. This update has two features:

• It handles the new API correctly.
• It now has a flag to block the display of the airport weather.

On your magic mirror go into the MMM-FAA-Delay directory in the modules and run the following commands:

git pull
npm install

This should update the MMM-FAA-Delay code then update it’s dependancies.

@twosquirrels Glad you sorted it out. I figured the weather is useful if you are monitoring airports some distance away but if you live close to the one you track then I can see it’s redundant information.

@MattSharp Hi, from what you describe the error is happening because the node_helper is not getting a response to the call to get the weather status in the first place. That’s where it expect the simpleforcast to be a part of the response. Can you post a version of your config to verify the call is happening ok?

@rak I’m also seeing this issue, I have entries showing on added in the calendar that are no longer part of the news feed online. It seems it’s ‘filling up’ then not refreshing :(

@soqueen sorry I thought the site supported PMs, my bad. Looking at the config you have you have the tube status set to show across the bottom of the screen:

position: 'bottom_bar',

If you move it to show in something like 'bottom_center' then it will restrict the width of the module. Check out the MM2 Read Me for the valid location settings. Hopefully this will correct the issue you are seeing, let me know if it remains a problem.

@soqueen probably best to send me he whole thing just in case it’s an interaction thing, just remove any private api keys and any personal urls (e.g. calendar).