New module installer

sdetweil

I added the default modules to have links to their config doc too… (in configuration)

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

MMRIZE

@MDWEBB said in New module installer:

[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.

sdetweil

@MDWEBB said in New module installer:

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

MDWEBB

@sdetweil Apologise for slow reply i was able to remove the node modules file and run the update for the module and now my calendar is working again.

sdetweil

@MDWEBB no apologies required

updated what module?

MDWEBB

@sdetweil update MMM-Remotecontrol.

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

sdetweil

@MDWEBB yes there are updates to mmm-config

are you using my remotecontrol repo?

i would disable the updatenotification module

MDWEBB

@sdetweil i am using your remote control module yes very handy, however having issues utilising the MMM-Module-Scheduler to to turn my monitor on and off via Remote-Control. i can see in the developer window its trying to send the notification however my monitor isn’t turning off. Am i missing something?

 {
        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"}}
            ]
        }
    },

sdetweil

@MDWEBB issue on remotecontrol
is not MY remote control, I just fixed the error trap that was misleading
no other code change

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…

sdetweil

@MDWEBB I just resynced my fork with his latest remote-control

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