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.
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.
Read the documentation on how to determine the provider name and station id’s you want to use.
[card:BenGig/MMM-Departures]
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)
