Sam, Yes, it was the file content. I had copied it from the git example but obviously did something wrong.

@sdetweil yes, and that is how I started, but it didn’t work.

Thanks Sam. I had it as schedules but it has to be notification_schedule. This works now.

Thanks for the replies. I did make a spelling error in config.js;, MMM-WallPaper where it should have been MMM-Wallpaper. Thanks.

Sam, thanks for your help.

@sankum i use mmm-pages, and 3 instances of MMM-Calendarext3 one for current month, next and after. some have added swipe to that, so you can wave a hand, with the right sensor page-indicator module can give you on screen buttons for direct page access too (assuming you have touch support, built in or ir frane)

@sankum i use this guide for selector clause https://www.w3schools.com/cssref/css_selectors.php used to be all one page, now in different sections you can combine all kinds of elements

@rts58 Thanks. I did figure out what to do. I forked the module in github and then it all worked fine withe second ID. Not very elegant as it may cause issues when the original module is updated. I dont know any other way, so for now will do.

@sankum just for discussion on a couple points from your image above [image: 1747663143318-1746897279242-screenshot-at-2025-05-10-12-14-08-resized-resized.png] in the css stack pane on the right, you see .CX3 .weekend has a couple styles, specified in MMM-CalendarExt3.css, line 385 and one of those styles has a strikethru, color an item higher up in the stack list, also shows a DIFFERENT class .CX3 .weekend_1 that ALSO specifies the same style, from the same file but line 394 (further down is processed later, so it overrides stuff set ABOVE this line…(cascading) so you can see the style(and where its set) , see it is overridden(and from where) and the element selected (left side of element view) shows BOTH classes applied NOW , this second style setting/weekend_1 demonstrates a problem, as you MODIFIED the module shipped file of css settings… and next time the module wants to update, it will FAIL as you changed one of ITS files… MM is designed to avoid this problem, you place ALL ‘custom’ (local to you) css in the file MagicMirror/css/custom.css we load this file LAST, so it overrides ANYTHING set before it was loaded… base, module, or anything higher in custom.css too…

Thank you,