@Eburkis
I haven’t been active for a while due to other things than magic mirrors.
Let me take a look and see if I can find out what’s wrong.

@jonaswadsten
MMM-ResRobot funkar med SL och andra, inklusive Västtrafik.
Den sorterar avgångar på tid.

@infamoustiggr
Try installing wtf-8 module by running the command npm install wtf-8 from the MagicMirror directory.

@wizz
It’s automatic and already there! Try it and you’ll see.
Icons are selected based on mode of transport, it’s going to be one of bus, metro, rail or ferry.

@Advokaten
Do you mean that the name of the bus stop is misnamed on screen? Then you have to contact ResRobot to change it.

@Advokaten
Strange, my mirror is running flawlessly. I’ll put in your config and see what happens.

@MobbareKurtZ
By adding them as a comma-separated list, e.g.

from: "12345,12346,12347",
to: "54321,64321,74321"

where each from and to pair specify an id for the departure and destination stops. If destination is not needed for a departure station, simply leave it empty like this:

from: "12345,12346,12347",
to: "54321,,74321"

@MobbareKurtZ
It all depends on the underlying ResRobot API but it sounds reasonable that ResRobot needs to know in what direction you are travelling.

As the module only shows departures there is no need to specify a destination unless you want to limit the displayed departures to the ones going in that specific direction. In that case I would suggest to enter not the ultimate destination but rather the next “logical” stop such as point of transit between modes of transport.

@infamoustiggr
I didn’t fiddle that much with the mirror pi. But ahead of that I’ve been doing quite some fiddling with Pis in general so I didn’t start from scratch.

To help you with troubleshooting:

After installing DietPi and rebooting you are presented with the dietpi-software screen:

Look under “Software Optimized” and “Software Additional” and make sure that NONE of the options are selected, you want an install that is as clean as possible.

Under DietPi-Config make sure that Autostart is set to option 0 (default):

Change directory to /root and install MagicMirror according to instructions in the README.

Following my instructions above to install all systemd scripts and their helpers. My /root contains the following:

Stop magicmirror service (just to make sure it isn’t running) with the command:

systemctl stop magicmirror.service

Start the magicmirror interactively by running node serveronly from the MagicMirror directory. You should see something similar to this:

root@mirrortest:~/MagicMirror# node serveronly
Starting MagicMirror: v2.1.1
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: MMM-Remote-Control
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
Initializing new module helper ...
Module helper loaded: MMM-WunderGround
Initializing new module helper ...
Module helper loaded: newsfeed
Initializing new module helper ...
Module helper loaded: MMM-ResRobot
Initializing new module helper ...
Module helper loaded: MMM-NetworkScanner
All module helpers loaded.
Starting server op port 80 ... 
Server started ...
Connecting socket for: MMM-Remote-Control
Starting node helper for: MMM-Remote-Control
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: MMM-WunderGround
MMM-WunderGround helper started ...
Connecting socket for: newsfeed
Starting module: newsfeed
Connecting socket for: MMM-ResRobot
Starting node_helper for module: MMM-ResRobot
Connecting socket for: MMM-NetworkScanner
Starting module: MMM-NetworkScanner
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:80

If any errors are shown, investigate them.

Now that MagicMirror is running it’s time to move on to the browser part.
Stop MagicMirror with ctrl+C and start the service with systemctl start magicmirror.service.

Make sure browser and matchbox are stopped by running the commands:

systemctl stop kioskbrowser.service
systemctl stop matchbox.service

Start matchbox with the command systemctl start matchbox.service. Check that it started ok with systemctl status matchbox.service. If not investigate.

Once you get this far the “only” thing left to check is the midori browser. As you don’t have an X Display on the console it is slightly trickier. Let me know if/when you made it this far and we’ll take it from there.

@johnnyboy
That’s technology development for you. Of course, in this case @infamoustiggr has the luxury of having someone with the exact same equipment already having the solution running.

As to the speed issue, apart from taking a few extra seconds on boot, I have no issues whatsoever with speed for functionality on my Pi 1. But I must admit it took me a number of tries to get there! Doing it with little to no experience with Linux is really tough.