Problem with MMM-ResRobot, it wont start(?)

[Eburkis]

@atd08001
now i want to completly give up… now with the new site id its still does not work. now it’s just black with no info at all.
what should i do ?

{
		module: "MMM-ResRobot",
		position: "left",
		header: "Departures",
		config: {
			from: "740024784",		// ResRobot Station ID (or a comma-separated string of IDs)
			to: "740046172",			// ResRobot Station ID of destination (or a comma-separated string of IDs)
			skipMinutes: 0,		// Skip departures that happens within the next  minutes.
			maximumEntries: 6,	// Number of departures to show on screen
			truncateAfter: 5,	// A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
			apiKey: "key here"		// Your ResRobot apiKey
			}
		},

[Nybbe67]

@Eburkis I sent you my config via PM. If you use that with your AKIKey it should work. Otherwise there must be a error with your key.

Hm…could it be something with your router, could it block sites? I had a similar problems once and I had a familly filter active on my router.

[Eburkis]

@Eburkis said in Problem with MMM-ResRobot, it wont start(?):

yeey somthing works now
now when the MM boots it says Fetching data for almost 3 sec then it goes black and now its just “departures” and under that its empty. so its almost that it is no departures at all

[Alvinger]

@Eburkis et al
I’ve just pushed a long-overdue update to MMM-ResRobot to github.

This new version has a completely reworked updating logic which should result in less “frozen” updates and also less API calls to Trafiklab/ResRobot over time.

Note that there is a breaking change to the configuration as I’ve changed the way routes are defined.
Previous configuration:

from: "from1,from2,from3",
to: "to1,,to3"

New configuration:

routes: [
  {from: "from1", to: "to1"},
  {from: "from2", to: ""},
  {from: "from3", to: "to3"},
]

Sorry for not pushing the update sooner but my mirror project has been delayed due to other things. Will try to update more frequently in the future. Please drop me a note if you encounter issues!

[ajomannen]

@Alvinger

Hi there,

I fail to get the new config format to work.

I use the following block:

{
	module: "MMM-ResRobot",
	position: "top_left",
	header: "Departures",
	
	config: {
		routes: [
			from: "740015972", to: "740061189",
		]
		skipMinutes: 0,
		maximumEntries: 6,
		truncateAfter: 5,
		apiKey: "xxxxx"
	}
},

but MagicMirror2 fails to start with following message:

WARNING! Could not validate config file. Please correct syntax errors. Starting with default configuration.

(If I use the old config syntax for routes, the system starts up as before, but I get departures from some default location that seems like Stockholm C.)

What could I have done wrong?

[ajomannen]

@ajomannen

I got it to work by adding an extra level of curly brackets and a comma after the closing square bracket:

{
	module: "MMM-ResRobot",
	position: "top_left",
	header: "Departures",
	
	config: {
		routes: [
			{
				from: "740015972", to: "740061189"
			}
		],
		skipMinutes: 0,
		maximumEntries: 6,
		truncateAfter: 5,
		apiKey: "xxxx"
	}
},

Is the example config on https://github.com/Alvinger/MMM-ResRobot incorrect?

[Alvinger]

@ajomannen sorry, the curly braces got lost in my copying. I have updated my previous post.

[Gailby]

I can not get it working either, says fetching for quite some time now. I get a “MMM-ResRobot : Error: got 400 response” on starting server… strange. Anyone recognize the same output?

            {
                    module: "MMM-ResRobot",
                    position: "top_right",
                    header: "Departures",
                    config: {
                            routes: [
                                    {from: "740021656", to: "740020749"},   // ResRobot Station IDs of starting and destination station(s). At least one route must be defined.
                                    {from: "740000765", to: "740000284"},   // "from" is required but "to" is optional (set "to" to empty string to indicate all destinations)
                            ],
                                    skipMinutes: 0,         // Skip departures that happens within the next  minutes.
                                    maximumEntries: 6,      // Number of departures to show on screen
                                    truncateAfter: 5,       // A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
                                    apiKey: "1c01e8b8-92d0-4e05-86dc-a112d743ba5a"  // Your ResRobot apiKey
                    }
            },

[Gailby]

Ok, seems it didn’t want to handle several departures like previous post but only one:

            {
                    module: "MMM-ResRobot",
                    position: "top_right",
                    header: "Departures",
                    config: {
                            routes: [
                                    {from: "740000765", to: "740000284"}    // "from" is required but "to" is optional (set "to" to empty string to indicate all destinations)
                            ],
                                    skipMinutes: 0,         // Skip departures that happens within the next  minutes.
                                    maximumEntries: 6,      // Number of departures to show on screen
                                    truncateAfter: 5,       // A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
                                    apiKey: "1c01e8b8-92d0-4e05-86dc-a112d743ba5a"  // Your ResRobot apiKey
                    }
            },

Still get error response:
node_helper for MMM-ResRobot received a socket notification: CONFIG - Payload: {“updateInterval”:300000,“animationSpeed”:2000,“fade”:true,“fadePoint”:0.25,“apiBase”:“https://api.resrobot.se/v2/departureBoard?format=json&passlist=0",“apiKey”:“1c01e8b8-92d0-4e05-86dc-a112d743ba5a”,“routes”:[{“from”:“740000765”,“to”:“740000284”}],“skipMinutes”:0,“maximumEntries”:6,“truncateAfter”:5,“iconTable”:{“B”:"fa fa-bus”,“S”:“fa fa-subway”,“J”:“fa fa-train”,“U”:“fa fa-subway”,“F”:“fa fa-ship”}}
Fetching new departure data for module: MMM-ResRobot
[…]
node_helper for MMM-ResRobot received a socket notification: CONFIG - Payload: {“updateInterval”:300000,“animationSpeed”:2000,“fade”:true,“fadePoint”:0.25,“apiBase”:“https://api.resrobot.se/v2/departureBoard?format=json&passlist=0",“apiKey”:“1c01e8b8-92d0-4e05-86dc-a112d743ba5a”,“routes”:[{“from”:“740021656”,“to”:“740020749”}],“skipMinutes”:0,“maximumEntries”:6,“truncateAfter”:5,“iconTable”:{“B”:"fa fa-bus”,“S”:“fa fa-subway”,“J”:“fa fa-train”,“U”:“fa fa-subway”,“F”:“fa fa-ship”}}
MMM-ResRobot : Error: got 400 response

[Alvinger]

@Gailby I copied your first config but used my API key and it worked with no issues at all.
Verify that you are using the correct API key.
The 400 status code is usually because you are using the wrong key.