@payno4 that typically means there is some config problem for a module, that causes MM to fail, and then pm2 starts it back up again…

we need to see the output of

pm2 logs --lines=100

u can look at an example of how to connect the two to insure correct connection,

see my two posts starting here
https://forum.magicmirror.builders/topic/12021/making-my-first-module-issue-with-notifications/7

modulename.js creates a random number on startup (per client)
and that is appended to the module identifier (per module: in config.js on server)
to create a unique module/client pair, and that is passed in/out on any requests to/responses from the node_helper

@peterbarlow2000 the node_helper file gets executed on the server, (one instance for all clients)
and the file in the module folder that matches the module name (modulename.js we call it)
runs on the client (one instance for each client)

I would change this

code needs to be executed on the client (by electron?).

to

code needs to be executed on the client (in the browser?).

@RoadRunnr1469 ok, YOU have to actually update the fileUrl file with new contents.

it loads the SAME fileUrl over and over and over and over
it adds a fake timestamp to the URL to force the browser cache to see a different file
which loads a new instance into the cache…

so somehow you have to do

cp  whatever_source_path/new_logo_to_display.jpg  ~/MagcMirror/modules/MMM-SimpleLogo/public/Amc.JPG

I have tested this and it works

also I think
the content of the new logo image TYPE must match the file extension… it is expecting jpg
so cannot change to gif/png for next ones to load

@RoadRunnr1469 cool… can u mark this as resolved now?

@BKeyport sorry, not quite sure what you said

@BKeyport try this syntax instead ip:port/remote?action=xxxxx&parms=???&parms2=???

see
https://forum.magicmirror.builders/topic/9941/mmm-remote-control-cannot-get-api/7

@lavolp3 it is/was installed as part of the original install script raspberry.sh, I didn’t change that except to
add some logging

# Check if plymouth is installed (default with PIXEL desktop environment), then install custom splashscreen.
echo -e "\e[96mCheck plymouth installation ...\e[0m" | tee -a $logfile
if command_exists plymouth; then
	THEME_DIR="/usr/share/plymouth/themes"
	echo -e "\e[90mSplashscreen: Checking themes directory.\e[0m" | tee -a $logfile
	if [ -d $THEME_DIR ]; then
		echo -e "\e[90mSplashscreen: Create theme directory if not exists.\e[0m" | tee -a $logfile
		if [ ! -d $THEME_DIR/MagicMirror ]; then
			sudo mkdir $THEME_DIR/MagicMirror
		fi

		if sudo cp ~/MagicMirror/splashscreen/splash.png $THEME_DIR/MagicMirror/splash.png && sudo cp ~/MagicMirror/splashscreen/MagicMirror.plymouth $THEME_DIR/MagicMirror/MagicMirror.plymouth && sudo cp ~/MagicMirror/splashscreen/MagicMirror.script $THEME_DIR/MagicMirror/MagicMirror.script; then
			echo
			if [ "$(which plymouth-set-default-theme)." != "." ]; then
				if sudo plymouth-set-default-theme -R MagicMirror; then
					echo -e "\e[92mSplashscreen: Changed theme to MagicMirror successfully.\e[0m" | tee -a $logfile
				else
					echo -e "\e[91mSplashscreen: Couldn't change theme to MagicMirror!\e[0m" | tee -a $logfile
				fi
			fi
		else
			echo -e "\e[91mSplashscreen: Copying theme failed!\e[0m" | tee -a $logfile
		fi
	else
		echo -e "\e[91mSplashscreen: Themes folder doesn't exist!\e[0m" | tee -a $logfile
	fi
else
	echo -e "\e[93mplymouth is not installed.\e[0m" | tee -a $logfile
fi

@RoadRunnr1469 and you installed the “MMM-OnScreenMenu” module too, right?

@RoadRunnr1469 I installed the module, and modified one of mine to send the notification, and it worked as expected.