@tanvir586 no need to install Ext-Screen. You can use Ext-PIR on its own.

@DDE12 Could you share your config? Also be sure put your API key in quotes in the configuration. If you aren’t using quotes, this could be a reason why the module is giving you the 401 error

@sdetweil Yep! A rebuild on Buster made all the difference. Performance is back up to what I remember it being under Jesse.

Thanks for the tip!

@tanvir586 No need for google assistant. Works fine without it.

Also does installing Raspbian lite make a difference performance-wise or does it just save space?

I recently rebuilt my mirror and installed Raspbian Bullseye as the base OS. I’m finding the performance to be REALLY slow… when my PIR sensor picks up motion, it takes a good 5-10 seconds or so for the mirror to respond, and when it does the transition from my screensaver module to normal layout is nowhere near smooth. Like 2-3 FPS.

Am I expecting too much from a Pi 3B with running Bullseye? If so, what OS should I redo the build on that performs well, but is not so outdated to the point I’ll run into unsupported code problems?

I don’t really want to purchase a Pi4 for this, as the Pi3B was at one point in time fine for this project and I’m not demanding anything more from it than I originally did.

If you’re still looking for a working PIR sensor module, I’m using EXT-Pir and it has been great
https://github.com/bugsounet/EXT-Pir

@Wenike said in MMM-MyScoreboard:

@j-e-f-f This can definitely be a future improvement but is there a way to get support for some of the relatively recent expansion MLS teams or if I use their codes, would it just work without additional code (especially with the ESPN update)?

The recent update already includes all current 28 MLS teams. However any future additional teams will work provided you know the shortcode. MLS is provided by SportsNet, not ESPN, and if you can figure out the shortcode SportsNet uses for any new team, you can follow that team specifically. Otherwise, if you just follow the league, the new team will appear as it comes through the feed without any intervention on your part. I also changed MLS to pull the team logo images from the data feed, so there won’t be any missing logos either.

New update released. This is a big one. Addresses the following:

• Correction of SNET provider ticker URL
• Change of ESPN provider URL to HTTPS
• Replacement of deprecated library Request with Axios
• Addition of WNBA and NCAAW womens’ basketball leagues
• Team logo updates for North American leagues
• Correction of NCAA team shortcode for Wisconsin Badgers from WIS to WISC

As this has a replacement of a module, you’ll need to run npm install after doing a git pull in the MMM-MyScoreBoard directory

A note on ESPN’s feed. I have seen a number of posts reporting that the it sporadically stops working. As of right now the ESPN feed works properly for me, but I did notice over the course of the last couple of day’s testing that sometimes the request out to ESPN is not answered in a timely manner. Eventually ESPN will update, but sometimes it is slow. I have made a change so that the request is made over HTTPS instead of HTTP, and my testing since then has shown the feed to be more reliable. Of course, this could just be a complete coincidence, and it’s equally as likely that we’ll continue to see issues with ESPN-sourced scoreboard data.

Once again, sorry for the LOOOOOOONG delay in addressing this. My mirror has sat unattended to for quite some time, and I only recently got around to rebuilding things. A number of my modules had stopped working, not just this one. Hopefully, this gets everyone back up and running.

From my standpoint, the only thing that stopped working for me were any of the feeds that used the Sportsnet provider. But I am seeing some anecdotal reports of the ESPN provider also not working? Could anyone provide some examples of this? ESPN is working for me as-is.

Sorry folks that I haven’t been around to fix this. There URL for the ticker changed for the SportsNet provider. I’ll be publishing a fix in the cominn g days, but if you want to address it now, make a change in the file providers/SNET.js.

Change line #122 from

    var url = "https://d290qmen6zswb.cloudfront.net/ticker?day=" + this.gameDate.format("YYYY-MM-DD");

to

   var url = "https://mobile-statsv2.sportsnet.ca/ticker?day=" + this.gameDate.format("YYYY-MM-DD");

This should get you back up and running until I publish the official fix.

• Jeff

@plainbroke said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

When will Darksky fail to work anymore.
I have it running now and it works fine.
What am I missing?

I just received an email last week from Apple saying that Dark Sky API will stop working on March 31 2023.

So you have a while yet before it goes belly up. And who knows… Apple might extend this out past the deadline.

@airclown if you know what you’re doing with CSS this is certainly doable in your custom.css file. The module’s HTML is structured in such a way as to not restrict reordering through CSS

@rcberg3 sorry, the code doesn’t currently allow for this, nor do the units have their own CSS class that you can use to hide them.

You could instead increase the width of the module in order to give the forecast a bit more space to stop the wind units from wrapping to a second line. Instructions to do so are included in the readme.

@biebermann it’s something I can’t fix. It’s a problem with OpenWeather’s API. Someone previously mentioned that OpenWeather had acknowledged it was an issue and maybe it will be fixed in the future. But the alerts don’t have a language identifier associated with them so it’s not even like I could filter out the duplicates in the wrong language.

@biebermann There isn’t a solution. The alerts come through as-is. There seems to be no logic in place on OpenWeather’s side to return the alerts in the configured language.

@miniashman said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

@stoffbeuteluwe In the custom.css i added the following:

.MMM-OpenWeatherForecast .current-conditions-wrapper .current.temperature:after {
    content: "C";
}
.MMM-OpenWeatherForecast .extra-current-conditions-wrapper  . temperature-container . high-temperature:after,
.MMM-OpenWeatherForecast .extra-current-conditions-wrapper  . temperature-container . low-temperature:after {
    content: "C";
}
.MMM-OpenWeatherForecast .forecast-item.daily .high-temperature:after,
.MMM-OpenWeatherForecast .forecast-item.daily .low-temperature:after {
    content: "C";
}

You can change “C” to “F” if needed depending on which units you want to use.

There’s actually a slight bug in this. The CSS should be as follows (notice he removal of the sapce between the period and class names in a few places):

.MMM-OpenWeatherForecast .current-conditions-wrapper .current.temperature:after {
    content: "C";
}
.MMM-OpenWeatherForecast .extra-current-conditions-wrapper  .temperature-container .high-temperature:after,
.MMM-OpenWeatherForecast .extra-current-conditions-wrapper  .temperature-container .low-temperature:after {
    content: "C";
}
.MMM-OpenWeatherForecast .forecast-item.daily .high-temperature:after,
.MMM-OpenWeatherForecast .forecast-item.daily .low-temperature:after {
    content: "C";
}

@pwalsh2202 said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

I’m looking to see if I can get just a truncated text-based description of the upcoming weather.

I’d like to see this too. The DarkSky API had this and it’s the one thing I really miss with switching over to OpenWeather. My guess is that in order to do this I’d need to create a special formatter that generates a detailed summary based on the weather data available. Say the API returned a wind speed of over 10mph, gusts reaching 30mph… I could generate a phrase like “It’s windy today with gusts reaching 30mph.”

This looks like a significant time commitment that I just don’t have. I would need to come up with all of the thresholds of the weather data that would trigger such phrases, create phrase templates, choose how they should be ordered, and then worry about translation for all of the languages MM supports. As it is I barely have an hour or two on the weekend to dedicate answering forum questions on this module and fixing any bugs.

If anyone else is willing to do this, I’d gladly welcome the pull request into my code.

The best my module can currently do to address your ask is to configure the module to only show the current conditions and the extra current conditions (which give you the summary in icon/metric format). You can turn off the hourly and daily forecasts if you like. Take a look through the README.md file with outlines all of the configuration options for this module.

@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

What css do I do to change color of the slash in H/L in “extraCurrentConditions” ?

Yes:

.MMM-OpenWeatherForecast .temperature-container .temperature-separator,
.MMM-OpenWeatherForecast .forecast-container .forecast-item .temperature-container .temperature-separator {
  color: #FF0000; /* makes it red */
}

@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

And can I remove “Powered by OpenWeather”?

Yes.

.MMM-OpenWeatherForecast .attribution {
  display: none;
}

@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

Any way to change the order of the different extraCurrentConditions?

This is technically possible with CSS, but it’s likely more trouble than it’s worth for me to explain it here, and error prone. A better and easier option for you would be to modify the mmm-openweather-forecast.njk file to reorder these items as you like.

Starting on line 39 you’ll see the templates for the extra current conditions. The order in which they appear here is the order in which they appear in the module.

Here are the first several lines of that section:

{# -------------- Extra Current Conditions -------------- #}
    {% if config.showExtraCurrentConditions %}
      <div class="extra-current-conditions-wrapper small bright">

        {# -- High / Low Temp -- #}
        {% if config.extraCurrentConditions.highLowTemp %}
          <span class="temperature-container">
            <span class="high-temperature">{{ forecast.currently.tempRange.high }}</span>
            <span class="temperature-separator dimmed">/</span>
            <span class="low-temperature">{{ forecast.currently.tempRange.low }}</span>
          </span>
        {% endif %}

        {# -- Sunrise -- #}
        {% if config.extraCurrentConditions.sunrise %}
        <span class="sunrise-container">
          <img class="inline-icon sunrise-icon" src="{{ inlineIcons.sunrise }}" />
          {{ forecast.currently.sunrise }}
        </span>
        {% endif %}

        {# -- Sunset -- #}
        {% if config.extraCurrentConditions.sunset %}
        <span class="sunset-container">
          <img class="inline-icon sunset-icon" src="{{ inlineIcons.sunset }}" />
          {{ forecast.currently.sunset }}
        </span>
        {% endif %}

Say you wanted the Hi / Lo temps to display after sunrise / sunset, just move the whole block as follows:

{# -------------- Extra Current Conditions -------------- #}
    {% if config.showExtraCurrentConditions %}
      <div class="extra-current-conditions-wrapper small bright">

        {# -- Sunrise -- #}
        {% if config.extraCurrentConditions.sunrise %}
        <span class="sunrise-container">
          <img class="inline-icon sunrise-icon" src="{{ inlineIcons.sunrise }}" />
          {{ forecast.currently.sunrise }}
        </span>
        {% endif %}

        {# -- Sunset -- #}
        {% if config.extraCurrentConditions.sunset %}
        <span class="sunset-container">
          <img class="inline-icon sunset-icon" src="{{ inlineIcons.sunset }}" />
          {{ forecast.currently.sunset }}
        </span>
        {% endif %}

        {# -- High / Low Temp -- #}
        {% if config.extraCurrentConditions.highLowTemp %}
          <span class="temperature-container">
            <span class="high-temperature">{{ forecast.currently.tempRange.high }}</span>
            <span class="temperature-separator dimmed">/</span>
            <span class="low-temperature">{{ forecast.currently.tempRange.low }}</span>
          </span>
        {% endif %}

Keep in mind that doing this will make it a touch more difficult to update my module as I release updates. When you want to update, you’ll need to to the following:

1. Make a backup of your modified mmm-openweather-forecast.njk file (copy it to another location, for example)
2. Restore the original with git checkout mmm-openweather-forecast.njk
3. Update the code with git pull
4. Restore your modified version of mmm-openweather-forecast.njk from your backup