@Ob018 , yeah but it’s tricky, you have to duplicate the module once installed and change the config/code file to call it MMM-RATP2 for instance. Not clean but whenever I try to do on module, several lines, node.js loses its mind and mixes the results

@jeremy_fr for that you need that SNCF exposes an API which was not the case six months ago.

@dementia, be sure that the config is correct. it the URL is good (test in a browser, it should work). Send me a PM, we can search for the issue

@ninja, same issue than before. doing the module is ‘easy’, but you need a server where the times of the train are available and it was not the case for SNCF.

if the heise feed is broken on server side, it will not work :)

Description

With the help of @strawberry-3-141, I created my first transit module to get the schedule of the next trains/bus/night bus/rer/tramway of any station of any line all around

Changelog

[21/04/2017] v 1.1

• UI revised
• Module is now multi-instance

Screenshot

Download

[card:lgmorand/MMM-Ratp]

http://www.heise.de/security/news/news-top-atom.xml
=> 404 error

http://www.n-tv.de/rss
=> working fine on my config

{
			module: 'newsfeed',
			position: 'bottom_bar',
			config: {
				feeds: [
					{
						title: "News",
						url: "http://www.n-tv.de/rss"
					}
				],
				showSourceTitle: true,
				showPublishDate: true
			}
		}

could worth a try ?
https://github.com/sintaxi/nhl-api

http://api.football-data.org/v1/competitions/430/leagueTable

=> it is a REST api and it does NOT return a RSS feed.

edit the files and in a browser, you open the URL to MM (localhost:8080 in my case) and you refresh whenever.

BTW, you don’t have to stop it, it seems that running the command again (pm2 start mm) does a “restart”

I’m ashamed…

thanks!

position: 'lower_third'
comma seems missing at the end of the line

When you get an error like this, remove everything and add module config one by one, it helps to find the issue

ps: and yes, this comma mistake happens to everyone :)

Hi,

I’m getting crazy with this, read stackoverflow, articles and still I cannot success to do a simple timeout.
In the last version of my plugin,
this code is called once and in the console I’ll see only one “boo”

setTimeout(function () {
  console.log('boo')
}, 100);

Then nothing in the console, others modules work fine, but not mine (it works but never refreshs)

here is the full code

const NodeHelper = require("node_helper");
const forge = require('node-forge');
const unirest = require('unirest');

module.exports = NodeHelper.create({

		updateTimer:"",
		start: function () {
	    		this.started = false;
			console.log("MMM-Ratp- NodeHelper started");
	  	},


		socketNotificationReceived: function(notification, payload) {
			
			
setTimeout(function () {
  console.log('boo')
}, 100);

		}

what could causes this ? I tried everything, started from scratch but always the same issue