Cool. I download the latest one and try it out.
Glad I can help you keep improving your code! lol
Cool. I download the latest one and try it out.
Glad I can help you keep improving your code! lol
Most monitors are IPS panels while most TV’s are VA panels. IPS has wider viewing angles with consistent color. The VA panels have better refresh rates for motion (which is not commonly needed for something like a mirror).
TV’s can be an easy choice because they can be much more available and a remote could be useful. A monitor will generally make for a preferred screen by having better viewing angles and being lighter overall.
@raf Are you volunteering? :)
Seriously - You won’t be anywhere near as well-versed as if you can figure it out on your own. And documenting your learnings to help others is how all of this stuff grows and improves. I’ve pestered @sdetweil plenty about a lot - much of his input has been to help me understand where to look, but he has also done some coding and such on his side. I’ve offered back some things I learned along the way that he has then incorporated and I’m now going to look into helping to extend and enhance some work he has done by doing the coding myself. It take a village, as they say…
@raf So, figure out what’s incorrect and help get it updated. The doc you’re trying to work from was built in that same way at one point…
Update… 30 full days since my last post about stability and have not experienced a single crash on either mirror. So, Electron is definitely the source of the problem.
Thank you to @sdetweil for the assistance in swapping over to Chromium and getting things to a stable state.
UPDATE: At this point, I’m closing in on a full week of operating two mirrors without issue. I’ve changed to running Chromium instead of Electron and it’s working well all around. Here are some details of the operation in case it’s useful:
Prior to successfully switching over to Chromium, the devices would crash at least once every other day (at least one of them would crash during a 48 hour window), although it was much more common to see each one crash multiple times per day. There was no consistency to which one would crash, why, when, etc. The “crash” in question was a black screen on the mirror and no visible info being output although the mouse cursor would sometimes appear. I wrote a cron job that would run every five minutes, look up the location of the pm2 error logs, check to see if there was an “out of memory” error in the log, and do a restart of MM if there was (the restart consisted of shut down, log flush, and start). This job ran every five minutes and would silently exit if there was no error as the mirror was running ok.
Since the switchover, I have seen zero crashes on either device in almost seven days of operation.
Electron has been discussed ad nauseum as having a variety of shortcomings, bugs, issues, etc. - especially in the old version being used with MM. At this point, I have to wonder why it’s still not only the default but the ‘only’ browser that’s really discussed for use with MM. It would seem that it’s time to either forklift an upgrade to it within MM or switch to something else (at a minimum, at least provide a well-documented alternative).
I’m grateful to @sdetweil for his assistance with this, especially since it really took a calendar year almost to get to a point where it’s seemingly working as expected now.
Now I have to find something else to break… sigh… :)
@sdetweil Yeah… I should have said I updated to the latest version of Bullseye with all patches. I haven’t made the last step to Bookworm yet…
@thgmirror Not really an option for me.
How does the site admin not understand that this is counter-productive to the site?
@mumblebaj said in Ads are blocking site content - how to get rid of them?:
@ember1205 Easiest way for me was installing the Adguard plugin on Chrome
Thanks. I’ll give this one a try…
@sdetweil Yeah… I should have said I updated to the latest version of Bullseye with all patches. I haven’t made the last step to Bookworm yet…
Yeah, I actually did more troubleshooting and such over the weekend and ended up doing a full upgrade to the RPi OS and then updating MM on there as well.
My troubleshooting was showing that the server side “shouldn’t” have been the issue because launching a browser on just about any other device would result in the continual processing and rotating of photos and such. And, even though the photo processing seemed to be the only piece that would stop updating on the client, the fact that it worked everywhere else led me to take the leap and do all of the updates on the RPi.
After doing the full upgrade to the latest version of RaspiOS (Bullseye) and then updating MM to the latest (using your scripts), it seems to be working correctly again and hasn’t stopped rotating the photos since the upgrade.
@mumblebaj said in Ads are blocking site content - how to get rid of them?:
@ember1205 Easiest way for me was installing the Adguard plugin on Chrome
Thanks. I’ll give this one a try…
@thgmirror Not really an option for me.
How does the site admin not understand that this is counter-productive to the site?
This is getting frustrating as it makes it impossible to read certain posts / pages… How do I get rid of this intrusive content?
@sdetweil I’m not running on a Pi or its software… Full install of opensuse linux. And I keep it fully patched and at the current release level.
@sdetweil I keep the OS updated separately on its own. What kind of updates are you suggesting would be necessary here?
@sdetweil So what you’re saying is that maybe I wanna start by upgrading? lol
I’m running on a Linux virtual guest, so I can easily snapshot it before I try and upgrade. What’s the best option for me to get current?
@sdetweil Issue I see now is that the indicated lines to add the lines after do not exist in my versions of server or socketclient…