@Eli

In my case, some modules that I use stopped working on the previous version of MM, so I had no choice but to upgrade. There are likely other modules that have similar requirements. If that wasn’t the case I would have happily kept the older version. I don’t regret my decision as the 3B+ is much faster when it comes to booting up and starting, stopping, or restarting MM.

After upgrading MM awhile ago my Zero 2W started having issues where MM would intermittently freeze or not start at all after a reboot. I tried a bunch of different things but nothing improved the situation.

I had an old Pi 3B+ lying around and decided to try that. It was solid for over a week in testing so I replaced the Pi in my mirror with the 3B+ and it’s been great.

@sdetweil I have a spare Zero2W. Would it make sense to run MM server on that one and have the one on the mirror in brower mode? Do you think that would make a difference in performance?

@sdetweil
I’m using a USB drive. This is so weird. Sometimes it works and sometimes it doesn’t. Right now everything looks good. Even MMM-Jast is working even though there was a warning that it required Node 20.0.0. Sometimes when I reboot it locks up at the GUI screen and I can’t connect remotely.

I have a spare Pi 4 I could use but I’m reluctant because the mirror is in a tiny bathroom and the sound of the cooling fan in noticeable when placed behind the mirror. I guess I could run it without the fan and monitor the temp.

               total        used        free      shared  buff/cache   available
Mem:             426         206          28          52         191         115
Swap:           2047         194        1853

@sdetweil I’m running Bullseye (Raspbian 11)

I ran the setup browser script and selected Surf.

My swapfile size is 2048. Does that need to be increased?

I ran the update script a few days ago after seeing PM2 error messages about the MMM-Jast module requiring Node 22.0.0. I saw posts about issues with node on the Pi 0, but didn’t see a workaround, or at least didn’t understand a workaround.

My current branch is Master
I tried “git checkout -b oldbranch tags/v2.30”

If Pi Zero2w is no longer viable, would a 3B+ work?

@JohnGalt My mirror was sometimes stalling - falling to update even the clock.

@sdetweil

Got it!

In the user crontab:

30 2 * * * /usr/local/bin/node /usr/local/bin/pm2 restart mm

Restarts the mirror every day at 2:30 am local time.

As always, thanks for your quick response!

Bill

Hi,

I’m trying to restart my mirror nightly with “pm2 restart mm” using a cron job. I’ve tried everything I can think of or find online but nothing works. I’ve created python and bash scripts, used the system crontab and the user crontab. I’ve tried it with and without “sudo” and also running it under the “pi” user. It always works interactively at the command line but not via crontab. Any suggestions?

Also, I saw the warning post about the April 1st upgrade and Pi Zero W. Does that also apply to the Zero 2W?

@KristjanESPERANTO Yes, thanks again.

@KristjanESPERANTO Perfect! Thanks. I had tried the performance hints but they didn’t really help. This is a good alternative.

@KristjanESPERANTO I updated to the latest MM and the horizontal scroll works but it stutters badly on a Zero2W. I’ve tried changing the settings but none of them give an acceptable appearance. I have a request for an enhancement of the Vertical scrolling feature.

The ticker scrolls up until it gets to the last instrument, then scrolls in the opposite direction. This is fairly ugly. Can it be made to continually scroll in one direction?

@KristjanESPERANTO I’m running an old version of MM and this update just killed it completely. The reason I stayed with Version 1 was because I’m using a Pi Zero2W and the MMM-Jast ticker was painfully slow when scrolling. I guess I have no choice now.

I saw another post about issues with Yahoo Finance which is the source for MMM-JAST. Has anyone seen a fix or workaround?

@wyovino The current temperature displaying is now correct. I’m guessing this was an issue at the source.

@sdetweil

The default value is 10 minutes, so it should never go above the free limit.

@sdetweil Do you know how frequently MM reaches out to pull down the weather data? I’d rather not exceed the daily free limit.

@sdetweil
I appreciate your efforts. The reason I’m using a Zero2W is that my mirror is in a tiny bathroom and when I used a Pi4 I could hear the hum of the fan. The Zero2W worked well except for the stock ticker which became very jerky. For the weather module, maybe I need a new API key. I’ll give that a try.

@sdetweil

The MMM-Jast module doesn’t work properly on a Zero2W with more recent versions which is why I did a fallback to this version. Is this related to the Weather API change I saw in the pinned post? Here’s my config. The “current” doesn’t work properly but the “forecast” does.

{
module: “weather”,
position: “top_right”,
config: {
weatherProvider: “openweathermap”,
type: “current”,
location: “Rockville Centre”,
locationID: “5134203”,
apiKey: “{myAPIKey}”
}
},
{
module: “weather”,
position: “top_right”,
header: “Weather Forecast”,
config: {
weatherProvider: “openweathermap”,
type: “forecast”,
location: “Rockville Centre”,
locationID: “5134203”,
apiKey: “{apikey}”,
fade: false
}
},