Read the statement by Michael Teeuw here.
Problem with MMM-ResRobot, it wont start(?)
-
-
hmm i have not make the same typo as you did but something i still not working for me.
{ module: "MMM-ResRobot", position: "left", header: "Avgångar", config: { from: "2023", // ResRobot Station ID (or a comma-separated string of IDs) to: "1138", // 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: 2, // A value > 0 will truncate direction name at first space after characters. 0 = no truncation apikey: "KEY HERE " // Your ResRobot apiKey },
-
@Eburkis Hi,
It looks like the Station ID is wrong. My “From station ID” for “Gubbängen” is 740021699.
You can create a API for “ResRobot - Reseplanerare” and then type in this URL in the browser: https://api.resrobot.se/v2/location.name?key=YOURE API KEY&input=SEARCH WORD
Replace the bold parts, whit API-key and search word for exampel T-centralen
You will get a XML response with all the possible results and the differnet ID (Stations ID)And then make sure you use the service “ResRobot - Stolptidtabeller 2” in the config.
Good luck
Andreas -
if i use the api for “platsuppslag” then i get the answer that 2023 is Rudboda torg and when i look for gubbängen Tbana is 7956 so I wonder where you get your number from.
and i get access denied with your link so that dont work for me sry
-
@Eburkis
You should use “ResRobot - Reseplanerare" and create a API for that service instead of “platsuppslag”.
i get ID: 740024784 and name “Lidingö Rudboda torg” when i search for Rudboda torgBR
Andreas -
i will try. tnx for the help, have a nice evening
-
@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 } },
-
@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 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 -
@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!