but its been quiet, so i am not sure if there are other changes, or if ive got the functionality right

any feedback welcomed

http://mm_address:mm_port/configure

both main and better_repo_url branches

can you show

in the MMM-Config folder

do
git branch

ls module_url_hash.json

in the module_installer folder

ls module_selector_schema.json

just posted another update for better handling of the repo readme (in most cases)
and handles readme’s for repo ADDs to the 3rd party list list, deletes worked ok before

and for the readme during config, use the file in the installed module folder, instead of trying to get the github repo version

same process

git pull
git checkout better_repo_url  # if already there not needed
npm install     # <--- required.. added another library and copies a template file

the copy fixes a bug in the readme list file

and if this is first time using, make sure to add
MMM-Config to your config.js

{
      module:"MMM-Config"
       position:"...", // only for qrcode if you use that
        config:{
        }
}

its on a different branch again

git pull
git checkout better_repo_url
npm install     # <--- required.. added another library and copies a template file

everything else is the same, except there is a button to open the module readme

an example from the installer page, exactly the same on the config page

still have some trouble with our own docs site, gitlab

the readme window will open at the button position

he had most of my changes and seemed to catch that error… maybe

https://github.com/Jopyth/MMM-Remote-Control/issues/303

which one of the 10 or 12 ways does it try to turn monitor off??

which OS is different
which window compositor is different x11/wayland/labwc is different

I know MMM-PIR has been working hard on making it woirk thru all the choices

did it work before and doesn’t now??

I don’t know the module internals…

 {
        module: 'MMM-ModuleScheduler',
        config: {
            notification_schedule: [
                // TURN THE MONITOR/SCREEN ON AT 07:30 EVERY DAY
                {notification: 'REMOTE_ACTION', schedule: '30 7 * * *', payload: {action: "MONITORON"}},
                // TURN THE MONITOR/SCREEN OFF AT 22:30 EVERY DAY
                {notification: 'REMOTE_ACTION', schedule: '01 14 * * *', payload: {action: "MONITOROFF"}},
                // RESTART THE MAGICMIRROR PROCESS AT 2am EVERY SUNDAY
                {notification: 'REMOTE_ACTION', schedule: '0 2 * * SUN', payload: {action: "RESTART"}}
            ]
        }
    },

are you using my remotecontrol repo?

i would disable the updatenotification module

I am getting update notifications for both the MMM-Config module and MMM-Remote-Control.
MMM-Config says its 3 commits behind the with_installer branch. Not sure whats happening with that
MMM-Remote-Control s 8 commits behind on the master branch i get the following error when trying to use the update script though

mdwebb@raspberrypi:~ $ cd ~/MagicMirror/modules/MMM-Remote-Control # adapt directory if you are using a different one
git pull
npm install # install (new) dependencies
Updating 76c0859..5c39b06
error: Your local changes to the following files would be overwritten by merge:
	modules.json
	package-lock.json
	package.json
Please commit your changes or stash them before you merge.
Aborting

up to date, audited 340 packages in 3s

103 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

updated what module?

at /home/mdwebb/MagicMirror/modules/MMM-Remote-Control/node_helper.js:271:26

I bet this is the remote-control error…

shouldn’t stop anything
but, if you want to try my fork, which captures that error

https://github.com/sdetweil/MMM-Remote-Control

just remove the existing folder and git clone mine in its place
no functional code change or parms… just trapping this error

[ERROR] ReferenceError: HTMLElement is not defined

This error message seems to be caused by some JS validator trying to check the browser-oriented syntax on the nodeJS environment.

@MDWEBB
You’d better start from a clean configuration and then add one by one to find what was wrong.

I made significant changes to the weather form layout, using select lists and custom field sets per weather provider.
updated the schemas MMM-Config ships to add the view readme button

BUT… just for the sake of testing something… MMM-Config saved the prior config.js

so if you

cd~/MagicMirror/config
#rename this one out of the way
mv config.js save-config.js
ls config -laFt config.*
#and copy the top one back to config.js
#mark the filename, right click mouse
cp -rightclick-paste config.js

and then restart MagicMirror

do you still get the error??