My display so far...

j.e.f.f

@Chiumanfu I haven’t tried to do that. This is a fork of MMM-WunderGround, and the data pull mechanism is unchanged. My changes are only in the formatting. I suspect that the two instances are sharing a single node-helper module, and as such, you’ll see the same data for both.

Can you try a test for me? Configure one instance using MMM-MyWeather, and the second using MMM-WunderGround. If you get different data sets for the two, then there’s likely a way to address this. Otherwise, what might be happening is the API recognizes two requests from the same machine, and isn’t allowing multiple locations. Might be a limitation of the free API.

Chiumanfu

@j.e.f.f Yes, it works as expected when using MMM-Wunderground to display the second location. It would be nice to have them display both in MMM-MyWeather but if the fix is difficult, I can live with it this way. Thanks.

j.e.f.f

@Chiumanfu I took a look at the way node_helper.js behaves for this module. It will take a considerable amount of re-engineering to get it to support multiple instances, and given that I am in the middle of a couple of other modules, I don’t think I’ll try to address this any time soon.

What you can do is instead of specifying two instances of the MMM-MyWeather module, make a copy of the module folder, name it, say, MMM-MyWeather2. rename MMM-MyWeather.js to MMM-MyWeather2.js. Then modify MMM-MyWeather2.js and change the first line of code from

Module.register("MMM-MyWeather", {

to

Module.register("MMM-MyWeather2", {

Now you have two distinct modules that do exactly the same thing. Make a second entry in your config.js file for MMM-MyWeather2. That should give you exactly what you are looking for.

The downside here is that you’ll need to redo the above steps if you ever update the module source code. I don’t see it changing all that much in the near future unless something breaks, so you should be good for a while.

RamblingGeekUk

This looks really nice… is the temp read out from Nest?

j.e.f.f

@RamblingGeekUk yeah. It logs in to your nest account via the API to get the current temp and state of the Nest.

RamblingGeekUk

@j.e.f.f Awesome… I was going to write all of this myself until I found this site yesterday, this is amazing. :-)

Chiumanfu

@j.e.f.f Thanks! I’ll try it.

j.e.f.f

@Chiumanfu I just realized that this will mess up the styles in you copied version of the module. You’ll need to do a search and replace in the copied version’s style sheet: in MMM-MyWeather.css, replace all instances of MMM-MyWeather with MMM-MyWeather2.

rudibarani

@j.e.f.f Dear j.e.f.f.,
I am trying your fork of MMM-Wunderground and like your additions a lot.
Is there a way to completely hide the current weather and only use the forecast-table (or vice versa only the current weather)? I would like to split both parts to different sections of the screen. So far, I have not found or overlooked options to hide today’s weather or the table completely.
Also, would it be possible to use the 24h timeformat in the forecast-table as well? I have set the global variable and it works fine for e.g. the clock - but MMM-MyWeather uses am/pm times.

j.e.f.f

@rudibarani It turns out there was an undocumented parameter to hide the current conditions display. I pushed an update to also add a similar one for the forecast table.

You can configure it like follows:

  {
    module: 'MMM-MyWeather',
    position: 'top_right',
    config: {
      ... //other config options omitted for clarity
      currentweather: 1, // 0 to hide
      forecasttable: 1, // 0 to hide
    }
  },