Two issues with module installation:
[1] The 4 day forecast icons do not display. A prior response to a user with this issue suggested the fix would be to ensure all the images are in the images folder. The forecast for each of the next several days is mostly sunny, so I have verified the relevant image for ‘mostlysunny.png’ is in the images folder. I also tried deleting and reinstalling the entire module, and also ensuring this module is not inadvertently addressed in my custom.css file. No change…

I’m not sure I should include the following in this post or create a separate post, as it feels like a separate installation issue. As such, if a moderator sees fit to separate them - that’s fine.

[2] The AQI value displays as ‘undefined’, which I suspect is an API issue. I do have an API from airvisual - but my notes tell me it expired a few months ago. I went to the airvisual site to renew the API key. The site does show the key identifier and shows it to be expired, but the site does not appear to support renewing a key after the initial one year period. Is a free user just out of luck after one year?

@sdetweil - Great, good to know.

@sdetweil – BTW, it this also true for all modules? That is, also for non-default modules? [Somehow I had internalized that even if default modules could be addressed this way, others required something like the following]:

.module.MMM-WeatherAlerts header {text-align: left;
}
.module.MMM-WeatherAlerts {  background-color:rgba(255,255,255,0.2); 
}

@sdetweil - Thanks! I will clean up my code some, when I get a chance. I appreciate the input.

You can try the following in your custom.css file. The first 3 lines are comments, explaining what is happening. Next the background is applied to the clock module. Finally it is applied to the calendar module, with a different transparency - it produces a dark grey background.

// background-color: rgba(red, green, blue, alpha)
// red, green, blue: 0 - 255
// alpha: 0 -1 (0=transparent, 1=opaque)
.module.clock {
  background-color:rgba(0,0,0,0.4);
  border-radius:8px;
  padding:8px;
}
.module.calendar {
  background-color:rgba(0,0,0,0.6);
  border-radius:8px;
  padding:8px;
}

@Gjones93 - Humm, this is interesting. Thanks for the update. While I might just try moving the alert module to the bottom of the stack of weather modules, the core issue I have with it is it appears to also hold on to horizontal real estate when not actively displaying an alert - with the effect of carrying all the modules in that region with it. In my case, I have the weather modules down the right side of the display, narrowed to 82% in custom.css. Sadly, when running your alerts module, I cannot get custom.css to narrow it using the same code, and it also pads out the other modules from the side of the monitor… FWIW, I also tried controlling the alert module width using an absolute number of pixels, but that also had no effect.

The weather css code follows:

.module.weather {
  background-color:rgba(255,255,255,0.1);
  border-radius:8px;
  padding:8px;
  text-align: left !important;
  width: 82%;
  max-width: 82%;
  min-width: 82%;
}

@Gjones93 - I am unable to replicate this today, too. It appears to be working as designed today. [There is no active alert at my location, so I changed the lat/lon to the same location in Alaska as before, and a Winter Weather Advisory displays. Both the local and Alaska work on the display and when accessing via a browser at port 8080 on my desktop.] For completeness, no - I did not set or change alertDateFormat from the default in the config.js.

Related but separate query: Does the module take up any space or affect existing modules when it is not actively displaying an alert? I ask because I have several instances of the default weather module stacked in the top_right region, and this module appears to affect their placement.

@Gjones93: BTW, when I set alertTimeFormat to absolute [overriding the default ‘relative’] - I get a black screen on the display, and the web page won’t load on the remote machine. I haven’t done any troubleshooting on this yet, but it has the feel of a module using an old library that is no longer supported…

@Gjones93: I do have it working now [I think the original issue was bad installation on my part]. FWIW, I also moved it up from the bottom bar to the top bar, and it is displaying the current wind alert at my location just fine. Thanks again.

@Gjones93 Thanks for the module - it should be very useful. Can you tell us what constitutes an ‘alert’ that will trigger the module? I have installed the module and have no output. My location is currently under a NWS ‘Wind Advisory’, but I get no output from the module. I have also input the lat and long for a place in Alaska that currently has a blizzard warning in effect - and that still does not trigger the module. Below is the configuration I am using.

{ module: "MMM-WeatherAlerts",
      position: "bottom_bar", // top_right
      header: "Weather Alerts",
      config: {
      // See 'Configuration options' for more information.
        lat: "62.037360", // Alaska
        lon: "-163.272301", // Alaska
        apiKey: "bc95bfa26f5d55522eb3d2cd0cdc7580",
        colored: true
},
},

@sdetweil Sam-thanks. It does load now. I’ll have to go back and [re-]learn some css to get it to fit in with the other modules, as it is way too tall, but this is progress. Thanks again

@cowboysdude Did you intend to call this module “WWW-WOTD” instead of the standard “MMM-…” ??

I downloaded it, it installed itself as “WWW-WOTD” and it does not run. I did not delve into the code, but suspect the non-standard name may be spread through the code.

Any thoughts?

@N6NG Did you manage to figure out how to do what you need? I see you got very low response to your query, which may be because you are referencing ‘widgets’ and Magic Mirror uses ‘modules’ as its base parts.

Did you mean to ask whether there are Magic Mirror modules that will display a web site? If so, I suspect there such [though I don’t have first-hand experience, it would be something I might be interested in the coming future…].

@sdetweil Thanks, Sam. I may take a look at that Ecobee API and/or the charting. The Ecobee is currently not in use in my new house, but this may give me the added incentive to get going on that. Thanks again.

@sdetweil : Sam, it sounds like you are integrating your Ecobee with your MagicMirror - true? If so, can you tell us how you get the data out of the Ecobee? I looked at it some time ago, and it appeared Ecobee uses [used?] a wireless band separate from basic WiFi, and I saw no way to tap into the information stream. I would be tempted to take another look at integrating data from the Ecobee into MagicMirror if feasible.

@sdetweil - Thanks Sam. That is what I had done, and so knew there were two instances running. I appreciate the tip and reminder.

@sdetweil - thanks! I figured it just had to be something straightforward. I appreciate you pointing me to the right place.

I have a new MM instance for development and testing in an Ubuntu VM. My goal is to have MM autostart when the VM starts, and run in serveronly mode, since the VM has no console display…

I ran Sam’s script to install the instance, then went back and ran the autostart script, but it appears to start a regular MM instance and not a serveronly. I have uncommented the serverOnly command in config.js, set it to “true” and rebooted. It appears the regular instance of MM starts, but not the serveronly. I CAN manually start MM with ‘node serveronly’, but then it looks like two instances are running.

Where am I going wrong?

@bkeyport and Sam: thanks for the inputs. I went through my logs and the referenced thread, and now do have DynamicWeather working. Much appreciated!

@sdetweil - the documentation indicates ‘It does not do recursive search of image folders’, which I would prefer. The author also indicates he cut out features from the module he forked, but didn’t specify what features. As I said, time will tell whether I stick with it, or give another a try.