@DDE12 yes

@neo_anderson you can try it out See https://forum.magicmirror.builders/post/123306 There is more info before that post, but this gets you the latest version

@sdetweil OK, tanks anyway. It seems there is something special in my mirror. Not that magic but unfortunate…

@Old_Death I do not know this module specifically But some things At the top you have two module: In js this is allowed, but the last one wins This means you have two instances of the schedule module About MagicMirror , this is called a single page web application We can only show or hide content. Pages, carousel, voice reco, profile switcher and module scheduler hide and show modules for different purposes As I understand it the scheduler module looks at the individual modules for a property to describe when it should be shown ( from-to) Scheduler has no ui of its own. So all info about images etc belong to the module that can display them. So all those parms need to move And the targeted modules do not KNOW anything about Scheduler, they will be shown or hidden Any properties added to be used by another module are unknown

@pclark2 woohoo!!

@jpmiller25 what does that mean saved events? we just ask the calendar provider to give us the calendar data, we have no info on how they got the way they are @MMRIZE in the config above, Ext3 is configured for one calendarset but there are two sources what does Ext3 do with the events from extra source? throw them away? refresh, the module has a refreshInterval value any faster than that requires restarting MagicMirror

@cheminge there are three scenarios day event repeats for 5 days, m-f you drag one of those someplace out of sequence, tuesday to saturday. it STILL MUST BE FULL DAY, it STILL has same uid (part of event collection) AND a recurrence id (in case you move it back) 5 day(full) event, not repeating you drag tuesday to saturday same UID (part of the event collection) it can have a different time scale hours vs day, not repeating if you modify it. and drag it back, its a new event in the middle of old range it lost its tuesday identity on drag out 5 single full day events covering m-f, one per day different uid each, anything is game yours is every other week, recurring or a particular day of week which of the events did you move? in each of the 1st two, if you delete the base event, all uid attached events go away too (event family is deleted) second one the outside event is no longer tuesday modified but it is still part of the family (uid)

@Johanba see https://forum.magicmirror.builders/post/123380

@sforza my response is that os is trash. don’t waste time using it. no idea what might work from the module perspective , i know there have troubles with RTSP streams in the later os versions

@Gnardar replied net, you attempted upgrade manually, and got caught be the node upgrade requirement now MagicMirror code is 2.30, node is downlevel npm install fails then you ran upgrade script, but it will not upgrade same version (without extra step) so it made no change, stuck in same spot to force upgrade in this situation, change the word apply to force on the upgrade command

Does anyone use this module? It shows up but I think I need more information to get it to work. Here is what I have put in my config.js { module: "MMM-edgerouter-throughput", position: "middle_center", header: "Unifi", config: { gateway: "https://192.168.1.1", user: "Plainbroke", pwd: "HIDDEN INFORMATION", title: "Unifi", interface: "USG Pro3" } }, And this is the output from my USG router [image: 1738035411122-screenshot-2025-01-27-213512.png]

@sdetweil can you enlighten me how I can use the provided different faces in the modules’ faces folder ? (face-001.svg - face-013.svg) found by myself… sorry. Parameter analogFace …

@MarcLandis cool! Thanks a lot. I keep an additional copy on my files … Warmest regards, Ralf

@Splashed no idea. unless you didn’t get into the module folder before the git pull cd ~/MagicMirror/modules/module_name

@rkorell awesome

@plainbroke awesome i should have remembered the path problem

@kusselin did you get forecast to work?

@rmcon thanks, but no wizardry a little info we use a source code repository, that keeps track of every file change, add, delete, rename, whatever. on linux there is no hidden file attribute, like on Windows… but by convention, if a file or folder starts with a dot(.) then it is not shown unless explicitly requested git is the source code repository we all use (MM and the modules) it is called a distributed scm (source code mgmt) system, because whenever you have some of a repo, you have ALL of it from its start to now… you git clone to make a local copy (linked to the source of the clone) on linux that is stored in the .git folder (notice the .) it knows about every little change to any of the files… oh when you see them, that is called the ‘working copy’… may match the repo, might not so, we asked git, tell me the status of the working copy as compared to the repository (in the .git folder) and it said some file hadchanged and some file had been deleted. neither of those files (package.json or package-lock.json) affect the actual running of the module, they are part of the housekeeping, setup, installation… now, you said you were going to UPDATE cause the module had changed, so you don’t NEED those files as they exist(or don’t) , cause you are going to PULL a NEW copy of the repo to your system (repo and working copy) git provides commands to do lots of things, you can look thru the history of the repo, with git log and git history an important idea, is a pointer to the top of the last incorporated (committed) changes that term is called HEAD, the HEAD of the change tree… so, we asked git, please restore our working copy (and any potential additions (commits) to the repo BACK to the HEAD position AND reset all the working copy files too… git reset --hard HEAD –hard means and working copy ok, so NOW we have the working copy matching the repo state of the clone you did now lets ask to refresh the local repo with the repo copy that has changed that action is PULL the repo to us, and resynch (it doesn’t like it when the working copy doesn’t match its expectations, so we ‘forced’ it back to HEAD) now the PULL updates the repo, AND the working copy… phew… and it updated the two files it was unsure about before but who knows what the impact of the change are (the module author, did we look at any comments he might have made (no… not me!)…) so, lets just redo the node package managers view of the system npm install will recheck any locally added libraries (in node_modules folder) and do any pre/post install tasks defined in the package.json NOW we are file level up to date with the latest official repo AND we are runtime up to date

@osnapus cool, but be ready because you added request at the MagicMirror folder you have modified the package.json and package-lock.json which will block the next upgrade for MagicMirror you will have to discard those changes to do the MagicMirror upgrade, but then Solaredge wont work again you should npm install request in the Solaredge module folder if you use my upgrade script it will ask if you want to keep these changes (no) but it will fix Solaredge for you you could run the upgrade script now with force as a parameter instead off apply to cleanup now next MagicMirror version release is April 1

@kasperb awesome!