MMM-Pages module all showing on one page

hahawoooooo

Hello!

I am having a strange issue where all of the modules are loading onto the first page and not rotating through pages while using the MMM-Pages module. I’ve worked through the suggested uninstall/reinstalling the module process outlined in the issue brought up here, but it hasn’t resolved it.

Magic Mirror version: 2.33.0

The pages config is below. Thanks for the help!

module: "MMM-pages",					// flip between pages - goal was to set full page calendar on one page, rest on other
        config: {
			timings: {
				default: 10000,			// rotate every 10 seconds
				0: 20000                  // page 0 rotates every 20 seconds
			},
			animationTime: 2000,
            modules: [
                [                         // page 0
					'weather',
					 'alert', 
					 'clock'
					 ],                
                [
					'MMM-CalendarExt3'
					],        // page 1
			],
			fixed: [
				['MMM-page-indicator'],						// what to show on every page
			],
			hiddenPages:{					// modules to not show, or to hide in specific pages 
				"hidden": [
					'calendar', 
					'updatenotification'
					],      //calendar module only needed to feed into MMM-CalendarExt3 and associated modules, but setting "disable = true" breaks this connection
			}

			   	}

sdetweil

@hahawoooooo as pages is done all in browser, can you open the developers window, ctrl -shift-I, select the console tab,
And enter page is the filter field

plainbroke

@sdetweil
Sam,
MMM-Adventskalendar, causes Your Pages to load all 50 of my modules on one page. I removed it and installed MMM-MyTeams-Adventskalendar and it works fine, now… Could not figure out what was actually causing it. Something about picture not having naming text. Didn’t know that would cause it to freak out.

hahawoooooo

@sdetweil : Thanks for the help! Here’s what I copied from the dev console after filtering for “Page”:

Failed to load resource: the 8080/modules/MMM-page-indicator/MMM-page-indicator.js:1 server responded with a status of 404 (Not Found)
Refused to execute script from ‘http://localhost:8080/modules/MMM-page-indicator/MMM-page-indicator.js’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
Refused to apply style from ‘http://localhost:8080/modules/MMM-pages/pages.css’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.

sdetweil

@plainbroke thx… will look at it
I added it with example params and it works with pages just fine…

{
    module: "MMM-Adventskalender",
    classes:"page1",   // on my pages def
    position: "top_center",
    config: {
        backgroundImage: "/modules/MMM-Adventskalender/images/background.jpg",
        doorMargin: 30,
        moduleWidth: 800,
        moduleHeight: 600,
        autopen: true,
        autoopenat: "10:00",
    },
},

sdetweil

@hahawoooooo weird… none of those make sense…

not found, then not executable
and css… typically that means not found

is this on a synology nas, and docker for MM??

hahawoooooo

@sdetweil I was a bit flummoxed myself, honestly. It’s on a raspberry pi, and I’m not using docker.

sdetweil

@hahawoooooo can you do

cd ~/MagicMirror/modules
ls -laF

hahawoooooo

@sdetweil Sure thing:

total 32
drwxr-xr-x 8 dtraindisplay dtraindisplay 4096 Dec 2 21:36 ./
drwxr-xr-x 16 dtraindisplay dtraindisplay 4096 Dec 2 21:15 …/
drwxr-xr-x 10 dtraindisplay dtraindisplay 4096 Dec 2 21:08 default/
drwxr-xr-x 7 dtraindisplay dtraindisplay 4096 Dec 2 21:36 MMM-CalendarExt3/
drwxr-xr-x 5 dtraindisplay dtraindisplay 4096 Dec 2 21:37 MMM-LINQConnectCalendar/
drwxr-xr-x 4 dtraindisplay dtraindisplay 4096 Dec 2 21:30 MMM-mmpm/
drwxr-xr-x 7 dtraindisplay dtraindisplay 4096 Dec 2 21:34 MMM-page-indicator/
drwxr-xr-x 5 dtraindisplay dtraindisplay 4096 Dec 2 21:34 MMM-pages/

I also tried doing a fresh install using the install script in a new folder, and I’m running into the same issue, but the console logs (ctrl+shift_I) is now showing a different output:

loader.js:179 Load script: modules/MMM-pages/MMM-pages.js
module.js:489 Module registered: MMM-pages
loader.js:152 Bootstrapping module: MMM-pages
loader.js:156 Scripts loaded for: MMM-pages
loader.js:195 Load stylesheet: modules/MMM-pages/pages.css
loader.js:159 Styles loaded for: MMM-pages
loader.js:162 Translations loaded for: MMM-pages
loader.js:179 Load script: modules/MMM-page-indicator/MMM-page-indicator.js
module.js:489 Module registered: MMM-page-indicator
loader.js:152 Bootstrapping module: MMM-page-indicator
loader.js:156 Scripts loaded for: MMM-page-indicator
loader.js:195 Load stylesheet: modules/MMM-page-indicator/page-indicators.css
loader.js:159 Styles loaded for: MMM-page-indicator
loader.js:162 Translations loaded for: MMM-page-indicator
MMM-page-indicator.js:138 [MMM-page-indicator]: MMM-pages detected. Will ignore PAGE_INCREMENT and PAGE_DECREMENT as it is already handled by MMM-pages
MMM-pages.js:117 [MMM-pages] received that all objects are created; will now hide things!
MMM-pages.js:331 [MMM-pages] resuming rotation
MMM-page-indicator.js:106 [MMM-page-indicator]: Changing maximum pages to 2
MMM-page-indicator.js:131 [MMM-page-indicator]: Setting page to 0
main.js:527 Uncaught (in promise) TypeError: searchClass.toLowerCase is not a function
at main.js:527:38
at Array.filter ()
at modulesByClass (main.js:523:31)
at Array.exceptWithClass (main.js:508:11)
at Class.animatePageChange (MMM-pages.js:234:8)
at Class.notificationReceived (MMM-pages.js:121:14)
at sendNotification (main.js:101:12)
at main.js:70:4

I also

sdetweil

@hahawoooooo interesting
Can you do

cd ~/MagicMirror/modules/MMM-pages
grep version package.json

Latest is 1.3.0
If not 1.3.0
git pull

The restart MagicMirror

plainbroke

@sdetweil
I think I found my answer, I was on version 1.0.0 of MMM-pages.
We will see what happens with Version 1.3.0 in the morning.
I did the git pull.

hahawoooooo

@sdetweil Good catch on that one - there are two MMM-Pages listed in the third party module website, and I was using your fork which is at 1.0.0. I uninstalled that version and installed the 1.3.0 version, but still having the same issue with all modules on one page.

I need to get a bit more sleep and look again just to make sure I did everything correctly after the changes.

One thing I noticed is I’m getting socket.io connection errors in the logs. where it repeatedly tries connecting and then fails. I can grab the log texts when I get back home tonight if that’s anywhere related to the problem.

sdetweil

@hahawoooooo I think this is a totally different problem…

are you using node 22.18.0 on the system?
node inside this electron version is 22.18

are you using a browser or is this the electron page started by npm start?

hahawoooooo

Node version is 22.18.0, and I’m using pm2 to start it. I changed the mm.sh file to open it via firefox.

sdetweil

@hahawoooooo so you are doing npm run server and then launching firefox…
or is this my runstart.sh and u set the env variable for firefox as the browser over server

hahawoooooo

@sdetweil To be honest, I need to get a bit smarter about the difference between the different start options (npm, pm2, mmpm, running over server). I’m currently just running pm2 start locally and not running a server.

sdetweil

@hahawoooooo

MM is a server with a browser auto started (npm start, electron is the browser), and with any browser connecting too
or
MM can be a server (npm run server) with any browser connecting from anywhere

MM is just an app…

you can configure the system to start an app on boot multiple ways

you can edit the system startup settings,
different on window, mac, linx (and diff linux versions)

OR you can run ANOTHER app, that does all that work for you
pm2 (node process manager v2)
it can start many different apps (mm , mmpm, and any other tool you like,

I have a spotify plugin on another mirror app, it can use the spotify api to play, pause, blah blah
if I install and start the spotify player daemon… (librespot or raspotify on pi)
I use pm2 to launch that too , and I can play on this machine.

the cool thing about pm2 is YOU don’t need to know HOW the system autostart works,
pm2 handles all that for you…

hahawoooooo

@sdetweil Thanks for the explainer! That really helps to clarify things a bit.

I am using pm2 to start, and it is running with the electron browser, with the MM running directly on the Raspberry Pi. Your explanation made me realize I can open the magic mirror from any browser in the house while I’m troubleshooting, which is really helpful!

I still haven’t figured out why the page timing rotation doesn’t work at all. Even if I set modules on different pages (page 0 and page 1, for instance), they all load in when I start up the MM. It’s like the pages aren’t loaded in, so they’re nothing to switch between.

Here are the logs on firefox from a separate computer while the server is running on the Pi:

[CX3] Module is not prepared yet, wait a while. MMM-CalendarExt3.js:396:11
[CX3A] Module is not prepared yet, wait a while. MMM-CalendarExt3Agenda.js:186:11
Uncaught (in promise) TypeError: searchClass.toLowerCase is not a function
    newModules http://192.168.1.180:8080/js/main.js:526
    modulesByClass http://192.168.1.180:8080/js/main.js:522
    exceptWithClass http://192.168.1.180:8080/js/main.js:507
    animatePageChange http://192.168.1.180:8080/modules/MMM-pages/MMM-pages.js:220
    notificationReceived http://192.168.1.180:8080/modules/MMM-pages/MMM-pages.js:117
    sendNotification http://192.168.1.180:8080/js/main.js:101
    createDomObjects http://192.168.1.180:8080/js/main.js:70
main.js:526:38
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. 2 main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. 5 main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. 2 main.js:678:9
module tries to update the DOM without being displayed. 3 main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9
module tries to update the DOM without being displayed. main.js:678:9

sdetweil

@hahawoooooo

Please use code block around logs, code or config

Uncaught (in promise) TypeError: searchClass.toLowerCase is not a function
newModules http://192.168.1.180:8080/js/main.js:526
modulesByClass http://192.168.1.180:8080/js/main.js:522
exceptWithClass http://192.168.1.180:8080/js/main.js:507
animatePageChange http://192.168.1.180:8080/modules/MMM-pages/MMM-pages.js:220
notificationReceived http://192.168.1.180:8080/modules/MMM-pages/MMM-pages.js:117

Can you post your pages config

hahawoooooo

@sdetweil Sure thing!

{  //MMM-Pages
        module: "MMM-pages",					// flip between pages - goal was to set full page calendar on one page, rest on other
        config: {
			timings: {
				default: 5000			// rotate every 5 seconds
			},
			modules: [
                                ['weather',                          // page 0	
				'MMM-CalendarExt3',
				'MMM-CalendarExt3Agenda',
				'MMM-Chores',
				'MMM-Dad-Jokes'
			   ],        				                
               ['MMM-TitanSchoolMealMenu'],        // page 1
				],
			fixed: [
					['MMM-page-indicator',						// what to show on every page
					'MMM-SmartTouch',
					'clock',
					'MMM-MagicMover',
					'MMM-Wallpaper']
				],
			hiddenPages:{					// modules to not show, or to hide in specific pages 
				"hidden": [
					'calendar', 
					'updatenotification',
					'MMM-Remote-Control'
					],      
				}
			}