ipWhitelist: [],

you will also have to open up the address block

address: [] or [0.0.0.0]

otherwise it means ONLY the same machine can talk to the mirror…

ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"], // Set [] to allow all IP addresses
	                                                       // or add a specific IPv4 of 192.168.1.5 :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
	                                                       // or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],

Its supposed to display the default webpage in the center of the screen. I dont see that . Just black in that area.

Here is the config.js

code_tvar config = {
	address: "localhost", // Address to listen on, can be:
	                      // - "localhost", "127.0.0.1", "::1" to listen on loopback interface
	                      // - another specific IPv4/6 to listen on a specific interface
	                      // - "", "0.0.0.0", "::" to listen on any interface
	                      // Default, when address config is left out, is "localhost"
	port: 8080,
	ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"], // Set [] to allow all IP addresses
	                                                       // or add a specific IPv4 of 192.168.1.5 :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
	                                                       // or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
	                                                       // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],
	
	language: "en",
	timeFormat: 12,	
	units: "imperial",
	// serverOnly:  true/false/"local" ,
			     // local for armv6l processors, default 
			     //   starts serveronly and then starts chrome browser
			     // false, default for all  NON-armv6l devices
			     // true, force serveronly mode, because you want to.. no UI on this device
	
	modules: [
		 {
        		module: 'MMM-Remote-Control',
        		// uncomment the following line to show the URL of the remote control on the mirror
        		// position: 'bottom_left',
        		// you can hide this module afterwards from the remote control itself
        		config: {
            		apiKey: '56cab4b5d5e24cfea8c436ac591d722c'
        	}
    		},

			
		{
			module: "alert",
		},
		{
			module: "updatenotification",
			position: "top_bar"
		},
		{
			module: "clock",
			position: "top_left"
		},
		{
			module: "calendar",
			header: "US Holidays",
			position: "top_left",
			config: {
				calendars: [
					{
						symbol: "calendar-check",
						url: "webcal://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics"					}
				]
		}
		},
		
	]

};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}

ext

I need to add some custom commands to control MMM-RTSPStream streams like if they were tv channel buttons, but I am not skilled enough to understand the interested readme section. :smiling_face_with_open_mouth_cold_sweat:

@shbatm could you please help me adding one stream button (as example for all the others to add)?

All I need is to run a combo of ‘RTSP-STOP all’ first (I am using OMXplayer therefore I prefer to kill any running stream first) and ‘RTSP-PLAY streamX’ immediately after.

It looks like @shbatm is not following this forum since many months.

Therefore @bolish or someone else could you please post your custom menu entries code so that I can better figure out how to enter that MMM-RTSPStream code?

The related README section didn’t make so much sense to me. :man_shrugging_medium_skin_tone:

I need to add some custom commands to control MMM-RTSPStream streams like if they were tv channel buttons, but I am not skilled enough to understand the interested readme section. :smiling_face_with_open_mouth_cold_sweat:

@shbatm could you please help me adding one stream button (as example for all the others to add)?

All I need is to run a combo of ‘RTSP-STOP all’ first (I am using OMXplayer therefore I prefer to kill any running stream first) and ‘RTSP-PLAY streamX’ immediately after.

@shbatm you there mate please? :smiling_face_with_halo:

@shbatm could you please help me adding one stream button (as example for all the others to add)?

All I need is to run a combo of ‘RTSP-STOP all’ first (I am using OMXplayer therefore I prefer to kill any running stream first) and ‘RTSP-PLAY streamX’ immediately after.

reinstalled twice the module without luck.

when i first installed this module the entries was there .

my config.js

{
      module: 'MMM-Remote-Control',
      position: 'bottom_left',
      config: {
        customCommand: {},
        customMenu: 'custom_menu.json',
        showModuleApiMenu: true,
        apiKey: ''
      }
    },

Well in my case Newsfeed is showing up by default without having to enable manually something. :man_shrugging_light_skin_tone:

@mohace huh?
I don’t have those menu’s entries at all.
Are you using a custom version of the module or? :confused_face:

Not at all. You can see same pic in shbatm second post, after the first one you replyed.

@shbatm said in [MMM-Remote-Control](v2-dev) Extensible REST API, Dynamic Menus, and Socket Communications, plus other updates:

Additional Features Added:

• Dynamic Module Control menu – uses the new API to create a Module Control menu on the remote page to control other modules via notifications.
• Custom Menu – ability to specify your own custom menu items from a file (for advanced users)
• Use PM2 API to control restarts/stops of MM. Can also support starting/stopping other PM2 scripts by passing processName: “scriptToUse” in the query payload.

Example Dynamic Menu for MMM-Carousel w/ Navigation

It seems that you need activate some features in modules to show them in this menu. But I don’t know what needs Newsfeed, for to have active his entry.

After let’s say 1 minute the TV turned ON by itself (can’t say really…) and there’s now no signal on the (proper) HDMI port.

I have the feeling the module is still sending monitor commands and NOT cec-utils package ones! :thinking_face:

            if (["MONITORTOGGLE", "MONITORSTATUS", "MONITORON"].indexOf(action) !== -1) {
                screenStatus = exec(monitorStatusCommand, opts, (error, stdout, stderr) => {
                    if (stdout.indexOf("power status: standby") !== -1 || stdout.indexOf("false") !== -1) { // MODIF DONE HERE
                        // Screen is OFF, turn it ON
                        status = "off";
                        if (action === "MONITORTOGGLE" || action === "MONITORON") {
                            exec(monitorOnCommand, opts, (error, stdout, stderr) => {
                                this.checkForExecError(error, stdout, stderr, res, { monitor: "on" });
                            });
                            this.sendSocketNotification("USER_PRESENCE", true);
                            return;
                        }
                    } else if (stdout.indexOf("power status: on") !== -1 || stdout.indexOf("true") !== -1) { // MODIF DONE HERE
                        // Screen is ON, turn it OFF
                        status = "on";
                        if (action === "MONITORTOGGLE") {
                            this.monitorControl("MONITOROFF", opts, res);
                            return;

Do you mind doing please a pastebin of your edited node_helper.js so that I can try it out?

The one you mention into your post (extract of node.js) are the default ones, don’t modify them.

What you need to modify into node.js are the ouput conditions as I posted above because the way the node.js is written (and how it’s explained on git) those commands will only work if your ouput are :

customCommand: {
        monitorOnCommand: 'shell command to turn on your monitor',
        monitorOffCommand: 'shell command to turn off your monitor',
        monitorStatusCommand: 'shell command to return status of monitor, must return either "HDMI" or "true" if screen is on; or "TV is Off" or "false" if it is off to be recognized'
    }

That’s why we need to replace those conditions into the node.js by the one we get with our TV’s (which are different than the “true” / “flase” “TV is on” etc… but are “power status : stand by” and “power status: on”).

Clear now??

I thought that was the part to edit by replacing monitor commands with HDMI CEC ones like mines?

        monitorControl: function(action, opts, res) {
            let status = "unknown";
            let monitorOnCommand = (this.initialized && "monitorOnCommand" in this.thisConfig.customCommand) ?
                this.thisConfig.customCommand.monitorOnCommand :
                "echo on 0 | cec-client -s -d 1";
            let monitorOffCommand = (this.initialized && "monitorOffCommand" in this.thisConfig.customCommand) ?
                this.thisConfig.customCommand.monitorOffCommand :
                "echo standby 0 | cec-client -s -d 1";
            let monitorStatusCommand = (this.initialized && "monitorStatusCommand" in this.thisConfig.customCommand) ?
                this.thisConfig.customCommand.monitorStatusCommand :
                "echo pow 0 | cec-client -s -d 1";