@sdetweil
This seems to have worked. Thank you so much!

@sdetweil

Just ran the script. Will advise if it works. Thank you.

After a few other reboots, this does seem to be working now.

Noted and thank you for the update. In absence of this bug fix, is the general consensus to migrate to newer hardware? If so, does the PI 4 have the headroom to comfortably do this, or are folks migrating to the PI 5?

I have an existing build that uses a 3B+. It has been running for years. I don’t recall the current OS I’m running, but can check it later on. What I’m finding is that the unit is really struggling to run. It takes quite a while to boot, and many of the modules aren’t refreshing. Is the 3B+ just not up to the task anymore with the newer OSs?

@Linas123 said in Compatibility with raspberry Pi 5 right now and in the future.:

@sdetweil
I want to upgrade my Magic Mirror from a Pi 3 to the new Pi 5 because my old one takes almost an hour to boot — it’s basically dead already.

A lot of the modules I use don’t really get updates anymore.
Do you think I could run into serious problems if I reinstall all of them on the new Pi 5?

When I set everything up last time, I had issues with almost every module because of Node.js versions and similar things.

I’m not a coder, so I’m not really able to tweak the modules myself to fix compatibility issues.

I have a unit with a 3B+ and I’m having much of the same issue. It seems to just hang and many modules are no longer updating.

@Lusbueb
apologies for the newbie question, but how did you implement this cron job? is it just a run once command or did you need to set it up as a recurring thing?

@alex2
The other odd thing, which is likely unrelated and I will need to touch base with the module developer, is that the Grove Gesture module suddenly no longer commands modules to appear/hide. I had it setup so a swipe would either hide all my modules or show all my modules, and another swipe would hide/show a specific module, and it randomly quit working as well. The module still runs and I get the feedback that it recognized the swipe, but the command to modify the view doesn’t process.

I have been running my mirror successfully for years. Started having issues when I did an update to a module (honestly don’t remember which one) and then went to update MM itself and found that it wasn’t working on my current Pi OS. I copied files and then did a fresh install of Bullseye on the pi. Installed MM and copied files over and all seemed to be working.

I’ve been having issues now where the network connection seems to drop pretty regularly when it was rock solid before. Not sure if there are issues with Bullseye and the RPI 3B+ or what the next step should be. getting pretty tired of having to regularly pull out a keyboard to reboot the Pi to get the mirror to run properly with internet connections.

@wishmaster270

haven’t tried EmbedURL to run two streams yet, but WebView did work, so that’s a huge plus.

@plainbroke
Thank you. running WebView and it appears to work. Much appreciated.

@BKeyport
So you’re saying this is related to the bullseye OS? Odd as in the native pi browser my links work. Also, to clarify, I do embed the user:pass into the url.

has anyone been able to get axis cameras to display on their mirror? I tried with a couple of the iFrame modules and had no success. Curious if anyone has had success. Ideally I can get it to rotate between two different camera streams. I’m currently using the smartwebdisplay module and I jut get a text readout saying “updated requested at…” and then it shows the interval. The two various url options I have used are the ones listed on this page. https://www.axis.com/support/faq/FAQ30473

I don’t get any errors, just nothing pulling up. I am considering trying the webview (https://github.com/Iketaki/MMM-WebView) or rtsp modules, but want to see if anyone has had success before I keep trying things to no avail.