Read the statement by Michael Teeuw here.
MMM-UkNationalRail - stops updating on mirror
-
@randomnoise The mm_error_log file is not something I’ve come across, I assume it is the failure report generated by PM2 that lists all the times it has had to restart a service.
npm start dev displays the mirror, but also has a full JS console output running down the side of the screen. The “No departure info” message in my previous post is an example of that output.
-
Still running without issue this morning, although I’m now getting emails about hitting my daily API usage allowance from the Transport API.
The only errors I’m getting are ones that the module generates when it doesn’t get the expected train info from Transport API - generally around 02:00 when no passenger trains are actually running.
Sorry to say that without being able to replicate the issue, there is very little more I can do.
-
@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.
-
@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, Well after a full rebuild I still have never been able to get to the bottom of why it locks up. Still does it on occasion (Although it seems to be less frequent these days).
I have a new weird bug with the train times for you now though! Recently (may have been since the clocks changed, although I only noticed it the other day as I was checking time on a train I was going to catch) I seem to be showing times an hour behind! It’s bizarre as I don’t think there are any settings anywhere in the mirror for adjusting times other than the PI config settings (mine is showing correct time & UTC if I run a ‘date’ command in putty).
Any thoughts on what this could be?
-
I’ve expanded to show 8 results here as well…
-
Hmm, weirdly York station works ok.
Maybe something is up with the api data for STN.
-
It’s definitely not just that those trains being late in my earlier example either-
-
Ok, think I’ve figured this one out by manually loading the api json in my browser. The earlier train which is late is showing as being over 1 hour late (even though that’s not what it shows on the estimated departure time).
This means that the trains following are still in the list even though they have departed.
Either this has been happening every day atm, or there’s something screwy in the transport api database.
0 mode "train" service "23540003" train_uid "G81206" platform null operator "SR" operator_name "Scotrail" aimed_departure_time "12:56" aimed_arrival_time "12:56" aimed_pass_time null origin_name "Aberdeen" source "Network Rail" destination_name "Glasgow Queen Street" category "XX" service_timetable status "LATE" expected_arrival_time "12:58" expected_departure_time "12:58" best_arrival_estimate_mins -54 best_departure_estimate_mins -54 1 mode "train" service "23541003" train_uid "G80279" platform null operator "SR" operator_name "Scotrail" aimed_departure_time "13:25" aimed_arrival_time "13:24" aimed_pass_time null origin_name "Aberdeen" source "Network Rail" destination_name "Edinburgh Waverley" category "XX" -
I suggest your best bet is to log an issue with TransportAPI as they might be able to identify if the issue lies with them or with the info coming through from the train operator.
