MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

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

    Scheduled Pinned Locked Moved Troubleshooting
    31 Posts 7 Posters 18.5k Views 7 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • AlvingerA Offline
      Alvinger @Eburkis
      last edited by 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!

      A 1 Reply Last reply Reply Quote 0
      • A Offline
        ajomannen @Alvinger
        last edited by

        @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?

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          ajomannen @ajomannen
          last edited by

          @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?

          AlvingerA 1 Reply Last reply Reply Quote 0
          • AlvingerA Offline
            Alvinger @ajomannen
            last edited by

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

            1 Reply Last reply Reply Quote 1
            • G Offline
              Gailby
              last edited by

              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
                                  }
                          },
              
              1 Reply Last reply Reply Quote 0
              • G Offline
                Gailby
                last edited by 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

                AlvingerA 1 Reply Last reply Reply Quote 0
                • AlvingerA Offline
                  Alvinger @Gailby
                  last edited by 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.

                  G 1 Reply Last reply Reply Quote 0
                  • G Offline
                    Gailby @Alvinger
                    last edited by

                    @Alvinger Thanx a lot, that did it! I got confused about the english translation of “ResRobot - Pole Schedules 2” and used ResRobot - Reseplanerare. My Bad :/

                    AlvingerA 1 Reply Last reply Reply Quote 0
                    • AlvingerA Offline
                      Alvinger @Gailby
                      last edited by

                      @Gailby
                      Great to hear! (Jag dokumenterade på engelska så alla kunde förstå men då blir ju svenskar lite förvirrade! :-)
                      Maybe I should add the swedish name of the API key to the documentation as well.

                      A 1 Reply Last reply Reply Quote 0
                      • A Offline
                        ayeball @Alvinger
                        last edited by ayeball

                        @Alvinger

                        Re: [Problem with MMM-ResRobot]

                        I have also problem with MMM-Resrobot . I use API-Key ResRobot - Stolptidtabeller 2. !
                        I got it to work now but i get stockholm stations … And i have use “ejdergatan"740025622” to redbergsplatsen" 740025673" Göteborg .

                        any idea? Kan svara på svenska också ;) Mvh

                        AlvingerA 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 3 / 4
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy