@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.