Is the resolution ok? Might be running a lower resolution. Check in the gui or with xrandr (or wlr-randr if running Wayland) remotely.

Connecting an Echo dot is not easy. You probably have to create a custom skill in the Alexa developer console, connect it to a Lambda function which in turn calls your mirror by http. A web service has to receive the parsed response and react properly.

This is how it is done it with FHEM. It provides code for the local web service and templates for the Lamda function.

Has the station ID based data source been dropped by search.ch? Connections are not so convenient as station departure times. I have a bus stop nearby and want do display all departures, one particular connection is not informative enough.

@Gamble said in Newbie . Pi + Mirror thus far. Some basic questions:

One thing I haven’t figured out is how do you set MM to open by itself?

https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

For changing the password type “passwd”. But it would be better to post the message output first.

Glad you found it.

German users maybe can get answers for a provider in the FHEM post concerning the FHEM Departure module: https://forum.fhem.de/index.php?topic=60046.0 since this module has been in use for some time already.

@sindbad6 Added the “flicker” issue to the tracker, have just noticed the effect.

@sindbad6 That’s not debug output, that’s a problem in the code.

Can you post it as an issue in github and add your configuration, if possible? Looks as if your config triggers an error mine doesn’t.

@sindbad6 Can you paste some of the output? I can see general output from all modules but no debug from mine (and I checked with absoluteTime: false too ;). And the part of the configuration with the debug turned off.

@lucallmon maybe a suitable provider can be found, here https://oeffi.schildbach.de/ I can see a general “USA (local and regional, e.g. Philadelphia, Chicago)”. Maybe Washington DC is supported? Since there are so many providers I don’t know in detail what is provided.

Here in Switzerland the main provider aggregates national and local information for train, bus and tramway, so there is no city specific provider.

@sindbad6 I refactored part of the main routine into a subroutine. A variable which was defined in the moved part was also used in the main routine, in the part for absolute time calculation.

Great, that helped, problem found and fixed!

I have added more debugging output, and an error output on the system console if a call to the web service fails.

And: most debugging output appears in the browser console. Hit F12 to open the development panel (Firefox or Chrome), and switch to the tab “Console” if not initially active.

I added a global config option which will give some output to the browser console:

    {
      module: 'MMM-Departures',
      position: 'bottom_left',
      config: {
        debug: true,
      ...

Results should look like this:

Processing station Aazopf
- Departures found: 5
-- Processing departure: NFB21,Arth-Goldau, Bahnhof,333
-- Processing departure: NFB21,Arth-Goldau, Bahnhof,374

Well, should…

No idea yet. I just upgraded to 2.1.1 and have no issues.

Do you see any error messages in the browser console?

I can only guess, but I don’t think the module will need changes. The providers data is fetched through the REST wrapper initially provided for a FHEM home automation module, and I thankfully may use it too. As I understand, behind the wrapper runs a instance of https://github.com/schildbach/public-transport-enabler which is actively maintained by Andreas Schildbach. And this enabler is the core unifier for the different providers.

Description:

I started a module for public transport data which uses the same data as the popular Oeffi smartphone app. Data sources from 13 cities and almost 20 countries are available, see https://oeffi.schildbach.de/ for an overview of available data providers.

• no API key needed
• no realtime information provided
• can display several stations

Read the documentation on how to determine the provider name and station id’s you want to use.

Download:

[card:BenGig/MMM-Departures]

Version

Version 0.2.1 (Fixed problem when using relative time)
Version 0.2 (Options to limit lines and output width)
Version 0.1 (Initial release)

Screenshots: