I decided against the use of a reflective surface

Includes

MMM-PIR-Sensor
MMM-Nest
MMM-Remote-Control
MMM-Teslalogger
worldclock
MM-DarkSkyForecast
iFrame

3 iFrame modules to display Roon, the car location Map and the house power display

These 3 use homemade Javascript modules to grab data from the Roon API, Teslamate and EmonCMS respectively

Below from the pm2 log

0|MagicMir | [2025-09-21 16:44:59.284] [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.
0|MagicMir | Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js to a dynamic import() which is available in all CommonJS modules. 

See https://stackoverflow.com/questions/70541068/instead-change-the-require-of-index-js-to-a-dynamic-import-which-is-available

@sdetweil

Redid the install using

npm install

No errors during install

Same problem

I removed the Remote-Control installation using

rm -r -f  MMM-Remote-Control/

Installed it using the instructions on the github repository

cd ~/MagicMirror/modules
git clone https://github.com/Jopyth/MMM-Remote-Control
cd MMM-Remote-Control
npm ci --omit=dev

I now get the following - which doesn’t seem fatal at first glance -

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: react-inspector@6.0.2
npm warn Found: react@19.1.1
npm warn node_modules/swagger-ui/node_modules/react
npm warn   react@">=16.8.0 <20" from swagger-ui@5.29.0
npm warn   node_modules/swagger-ui
npm warn     swagger-ui@"^5.29.0" from the root project
npm warn   2 more (react-dom, react-immutable-pure-component)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^16.8.4 || ^17.0.0 || ^18.0.0" from react-inspector@6.0.2
npm warn node_modules/swagger-ui/node_modules/react-inspector
npm warn   react-inspector@"^6.0.1" from swagger-ui@5.29.0
npm warn   node_modules/swagger-ui
npm warn
npm warn Conflicting peer dependency: react@18.3.1
npm warn node_modules/react
npm warn   peer react@"^16.8.4 || ^17.0.0 || ^18.0.0" from react-inspector@6.0.2
npm warn   node_modules/swagger-ui/node_modules/react-inspector
npm warn     react-inspector@"^6.0.1" from swagger-ui@5.29.0
npm warn     node_modules/swagger-ui

@sdetweil

I’ve now changed it to

var config = 
{
  address: '0.0.0.0',
  ipWhitelist: [],
  modules: [




    {
      module: 'MMM-Remote-Control',
      config: {
        secureEndpoints: false
      }
    },

Same problem with Canot GET /remote.html

http://10.0.1.87:8080/ works fine and I see the MM display
http://10.0.1.87:8080/remote.html leads to the error

@sdetweil

Interesting

I’ve had that on an instance of MM I’ve been running for 5-6 years with Remote -Control and it’s always worked fine.

I’ve been able to access the display and remote from anywhere on the network.

So I just copied it over to the new one

On a new installation

var config = 
{
  address: '0.0.0.0',
  ipWhitelist: [
    '127.0.0.1',
    '::ffff:127.0.0.1',
    '::1',
    '10.0.1.1/24'
  ],
  modules: [



    {
      module: 'MMM-Remote-Control',
      config: {
        secureEndpoints: false
      }
    },

The entire section is copied from another instance of MM where Remote-Control is working fine.

On this new install I get

Cannot GET /remote.html

Help!

@sdetweil

Thanks for your help with this, Much appreciated

I’m now away from the mirror for the weekend. I’ll give it a shot when I return on Tuesday

@sdetweil

The video appears on both pages.

The page with index 0 and the hidden page

@sdetweil

Yes, using your fork

@evroom said in MMM-pages - how to know which page index my module has?:

As a workaround, I will make it a requirement to put the MMM-Player on the first page (page index 0).
When I receive 0, then I will start streaming, otherwise I will stop streaming.
That seems to work.

@sdetweil Maybe something to do with this?