Read the statement by Michael Teeuw here.
MMM-UKNationalRail - Rail departure info for specific UK Railway stations
-
Hello, i have the module working, i just cant get it to display the title.
{
module: ‘MMM-UKNationalRail’,
position: ‘bottom_left’,
header: ‘Whittlesford Parkway’, //Optional - delete this line to turn OFF the header completely
config: {
stationCode: ‘WLF’, // CRS code for station
app_id: ‘xxxxxxxx’, // TransportAPI App ID
app_key: ‘xxxxxxxxxx’, // TransportAPI App Key
maxResults: 5, //Optional - Maximum results to display.
showOrigin: false //Optional - Show the origin of the train in the table
}any ideas?
-
@dawookie1979 u mean the header?
-
yes the header is not showing
-
Hello,
Does anyone have a multi-station configuration working? I also do not get any headers showing - anyone managed to solve that one?
Thanks in advance
-
Headers have been broken for a while now. Happened after MM version update. Not sure if @nwootton is still working on this or not though.
Also not been able to get multi-station working. The fix I used was just to have 2 modules listed one after each other (ie, duplicate the code in the config file, including API etc). That seems to work fine.
-
Hi Bob,
Thanks for the information. I’ve been playing and have fixed up the header not being shown and in addition have added column headings such as "Platform, To, From, Planned, Actual and Status to the displayed table.
I have seen in the forums elsewhere you do have to have multiple modules in order to get multiple stations which I suppose is OK, but a bit awkward. I may have a look to see if this can be all rolled into one config section.
One other feature I would like to work on is this: My partner travels home eveyday and says what train she is on, but never knows what time it will arrive at our home station - I want to see if it is possible to have a a listing of the possible trains with the departue and arrival times. As I’m very new to all this, it’s going to hurt my head coding it I suspect.
-
Hi Tenpin,
Sounds like me and you want the same thing!
I’m currently having issues with my module updating after a refresh though, don’t know what is going on there! Essentially after I restart the Mirror, the module will work for a couple of hours, then when I get up the next day it will still be showing last nights times, almost like it’s frozen.
How did you get the Header sorted and column headings?I am also using MMM-ModuleScheduler to display the specific Trains at different times.
I have three modules running see below, where my app id and app key I have replaced with xxx.
One for my partner, Monday to Friday from Home to Work in the morning. Stirling - Dundee (See Station Code is Stirling, calling_at: Dundee)
One for my partner, Monday to Friday from Work to Home in the evening. Dundee - Stirling (See Station Code is Stirling, called_at: Dundee)
One for me, Tuesday to Thursday from Home to Work in the morning. Stirling - Glasgow (See Station Code is Stirling, calling_at: Glasgow){ module: 'MMM-UKNationalRail', position: 'bottom_left', header: 'Stirling - Glasgow', //Optional - delete this line to turn OFF the header completely classes: 'scheduler', config: { module_schedule: {from: '0 7 * * 2-4', to: '0 9 * * 2-4' }, stationCode: 'STG', // CRS code for station calling_at: 'GLQ', app_id: 'xxx', // TransportAPI App ID app_key: 'xxx', // TransportAPI App Key maxResults: 3, //Optional - Maximum results to display. showOrigin: true //Optional - Show the origin of the train in the table } }, { module: 'MMM-UKNationalRail', position: 'bottom_left', header: 'Stirling - Dundee', //Optional - delete this line to turn OFF the header completely classes: 'scheduler', config: { module_schedule: {from: '0 7 * * 1-5', to: '0 9 * * 1-5' }, stationCode: 'STG', // CRS code for station calling_at: 'DEE', app_id: 'xxx', // TransportAPI App ID app_key: 'xxx', // TransportAPI App Key maxResults: 3, //Optional - Maximum results to display. showOrigin: true //Optional - Show the origin of the train in the table } }, { module: 'MMM-UKNationalRail', position: 'bottom_left', header: 'Dundee to Stirling', //Optional - delete this line to turn OFF the header completely classes: 'scheduler', config: { module_schedule: {from: '0 17 * * 1-5', to: '30 19 * * 1-5' }, stationCode: 'STG', // CRS code for station called_at: 'DEE', app_id: 'xxx', // TransportAPI App ID app_key: 'xxx', // TransportAPI App Key maxResults: 3, //Optional - Maximum results to display. showOrigin: true //Optional - Show the origin of the train in the table } },
This is my partner’s trians for coming home
https://imgur.com/a/OGflgLi
See it doesn’t list Stirling. It lists end destination and origin station. -
@tenpinmark Any chance you can post the code you used to fix it ? (or submit a fork to switch to instead)
@Glass92 I had similar problems (and only with this module). My solution was to create a cron job to reboot the mirror after midnight, which restarted the code. It’s not ideal, and actually introduces other issues with the HDMI port (will sometimes fail to initialise the display). I’ve since removed the cron job, and now just manually reboot if needed (usually once every couple of days)
-
Is there a way to make it work?
-
Getting emails from transportapi.com saying I’m over my call limit. Anyone else?