@Johannes I wanted my startup to be as ‘clean’ as possible so I did the following:

1. Get rid of all the boot text by following https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie
2. Set my desktop background to be completely black (so you don’t see anything before mm starts
3. Hide the taskbar (only appears back if the mouse is moved to the bottom of the screen).
4. remove wastebasket from desktop (just right click on it to get option).

By following this now I only see the the ‘acer’ logo which comes from my monitor & can’t be removed, followed by a completely black screen (barring a few small squares as pi boots) then it goes straight in to mm.

Regarding your issue about multiple instances- I think the install script now adds a ‘MagicMirror’ instance to pm2. Then by following the instructions & adding another instance called ‘mm’ I ended up with 2. Think the guide needs to be updated to reflect this. I removed it by using ‘pm2 delete 0’ to remove the 1st instance & then ‘pm2 save’. Hope that is of some help.

Re: MMM-Hive
@mongo116 Recently I seem to be getting ‘Error loading data’ for the hive module. Sometimes it loads (although the outside temperature is ‘null’).

Enabling debug gives me the message:
“MMM-Hive received notification: UNKNOWN_ERROR - Payload: Error found within get postcode data: undefined Body: undefined”

Tried to change postcode, put in a blank one etc but still get the issue.

I did note that if I manually go to the outside url that it throws a SSL cert error so maybe that’s related?

Any ideas what the issue could be? Is yours running ok?

@nwootton after running since Sunday with no errors & console open, today train times finally crashed around 10:30am… then the entire mirror seems to have fallen over tonight just before I came home… the clock had stopped, all modules not updating and even the dev console was gone!

Hard reset of mirror, but of course nothing to see in pm2 logs as I didn’t start it with pm2…

unless the dev console also logs to a file somewhere then this exercise was in vain.

I think I’ll just try a full reinstall at the weekend & see if it behaves itself. I wish I’d taken a note of all the other tweaks I added to get the pi running as I liked.

@nwootton no worries, I’ll be home again on Sun so will try the dev console & see if anything stands out. As you say it may be electron related so I might just do a full pi + mm rebuild / reinstall.

Thanks for having a look in to it.

BTW does the npm dev start give any detail beyond what is logged to the mm_error_log file seen when running using pm2?

@nwootton not sure what version of node I’m running atm (I’m away for work)… I’ll try the npm start dev when I’m back & see if anything stands out.

I run the mirror standalone so, yes I guess it could be an issue with something in the pi browser, but it is a fairly standard mm build installed following the instructions from mm git page.

I’ll report back once I’ve tried the dev start.

@nwootton Hmm, that’s weird. I guess it could be an issue specific to my mirror. What os do you use? Have you also upgraded to 2.1.3 of mm as well?

I might try a rebuild & see if that improves it.

Is there any way to add in debug logging to text file? Perhaps when it updates the data from transport api & refreshes the screen.

What I found strange was that even while it’s stopped updating on my actual mirror, it will work fine in a browser on another machine on my network (does this actually run another version of node helper etc or is the mirror still fetching the data?)

@nwootton Mainly going with defaults, but here is what I’m using.

{
		module: 'MMM-UKNationalRail',
		position: 'top_left',
		config: {
			stationCode: 		'[My 3 letter station code]', 		// CRS code for station
			app_id: 			'[My ID]', 	// TransportAPI App ID
			app_key: 			'[My api key]', // TransportAPI App Key
			maxResults: 		4,  //Optional - Maximum results to display.
			showOrigin: 		false   //Optional - Show the origin of the train in the table
			}
		},

No worries, let me know if I can do anything to give you any further info to assist with troubleshooting. Cheers.

@nwootton thought I’d check to see if you have any ideas what could be causing an issue I’ve been having with the UK train times… When its been running for a while I often notice that it seems to have stopped updating itself so will be frozen showing train time in the past. This happens every couple of days, no specific time it can happen mid day or at night (when there are no trains scheduled so nothing to see ‘No departure info found’). It has kind of always done this, although it used to go the best part of a week before requiring a restart.

When it occurs I can confirm that all the other modules on my mirror are still happily updating. Also if I fire up the mirror webpage on my laptop it has the correct up to date info.

No errors logged in PM2 error & as far as teh pm2 out log looks everything still working ok.

I restart mm & it fires up as normal. Any thoughts? Any further steps I should take to troubleshoot?

I’m fairly certain its gotten worse since updating to MM 2.1.3, seems like I’m rebooting every other day now.