watchdog has a problem… removing… have not crashed since increase swap space… will close for now as I work on the watchdog socket problem

@mieserwicht yeh, had to escape the - on -dpms… try again adding again, yes, it got an empty result due to the error

I have submitted this script as part of pull request 1789

@Socrates note that without adding a parameter The script does nothing. It only tests the ability to update the base MagicMirror Update is two pass process Test. Make no changes Do. Apply the changes (with the parameter apply) Many users have modified MagicMirror base code not knowing about the config and css file design. These changes block the ability to update normally Over time they forget that they changed the files and what they actually changed. The force way to install is to wipe all changes, but now the result doesn’t work like it used to. Adding a lot of frustration.

nice article for connecting Apple retina displays to SBC like Raspberry pi https://blog.hackster.io/connect-apples-retina-displays-to-a-single-board-computer-using-an-edp-adapter-25e0881f961

see my post containing link to the new script https://forum.magicmirror.builders/topic/10859/new-upgrade-script-ready-for-testing

@sdetweil Ok, copied the node_modules/electron folder tree from the good working install to replace the bad… and now the bad behaves…

@sdetweil oh thx for the fast answer ….

there is a new alexa skill to view the live feed from a ring (doorbell, floodlight) camera… on an Echo Show… I’d like to put that on my MM…

SO, the workaround… NEVER call updateDom() without a minimum count of 2 (as the code divides by 2 inside) it does a hide/update/show) (hide/show each get 1/2 the time specified, ie 2/2 =1 each.

SO… the problem is the calculation uses the local hour to determine from now… but users see days… so the fix is to truncate NOW to the start of the day…, then the comparison is start of day to start of day… instead of this // uses hours/mins/seconds of now.. timeWrapper.innerHTML = this.capFirst(moment(event.startDate, “x”).fromNow()); do this // uses only date, time is 00:00:00, fullday events also start at 00:00:00 timeWrapper.innerHTML = this.capFirst(moment(event.startDate, "x").from(moment().format("YYYYMMDD")));

@sdetweil I am aware of that, but somehow I just ignored it as I was “on auto-pilot”. :grinning_face_with_sweat:

@lavolp3 i do not… there are tons of options, which I guess you would expect.

we see a LOT of new users having trouble with unintended syntax errors in config.js. they don’t know, and MM is running happily without their changes… so, I want to propose adding the call to tests/configs/check_config.js as part of the error handling… this was easy, except… MM keeps running with the default config… which it shouldn’t… I’ve tried all kind of things… process.exit(0); is quick death… except the output of the tests/configs/check_config.js isn’t flushed, so the messages don’t show up… they took out process.stdout.flush() a long time ago… none of the workarounds appear to work… anyone got any ideas? thanks…

@mykle1 there is no better thought motivator than posting on a live forum…!!

My mobile does not have block popups turned on

Using the fullscreens.above class for the div makes this a lot easier. No modification of the std css is required

@sdetweil well, that was easy and works great!.. gotta figure out how to have a div with a fill color to replace the black edges when the pics are not fulls screen. also the bottom edge of the pic is clipped by the bottom of the screen somehow… half the newsfeed line is over the clip line

I’d recommend trying to do it again using the description by MichMich https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror It is crystal clear from what I see, also describes what to do. "the doc for ‘pm2 startup’ doesn’t help me… ‘will give you the command u need to execute’ execute when, how? if unattended, who is ‘you’?" No offense, but btoh the doc and your terminal will show you exactly what to do. Copy a line of text the terminal throws out and execute it again. That’s the reason I’d suggest to do it again with a bit more patience. :-)

well, i found a solution… I modified the ImagePhotos.js to create the div once. instead of each time. this reduces the flash. added an onload handler for the image in the div., start with the image hidden the onload handler changes the just loaded image to the required opacity and transitions this over 1.25 seconds. also getting current image size, and size of screen and adjusting to not clip or zoom it then checks to see if there is more than ONE image in the div (current and just loaded)… if so, it hides the old image, and then deletes that image from the div. repeat for next image.