Read the statement by Michael Teeuw here.
MMM-Departures - Public transport departures based on Oeffi data
-
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.
-
@BenGig I know the repository from Andreas, if your module use this code, I suppose his changes will also work on your module. In between, I installed your module and it works perfect for my home town, what else could I need. It’s great.
-
After updating of MM to 2.1.1 and updating your module I get no data anymore. I get only the information “Lade” means load or wait. Any idea why this happens?
Both was installed with
git hub && npm install
Anything I have to do? -
No idea yet. I just upgraded to 2.1.1 and have no issues.
Do you see any error messages in the browser console?
-
@BenGig No, there are no messages belonging your module.
-
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…
-
@BenGig I tried the debug mode. The only things I get is
Module helper loaded: MMM-Departure
and
Connecting socket for: MMM-Departure
nothing else to see. Sorry! :disappointed_relieved: -
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.
-
@BenGig Find out, that the error only occurs if I set
absoluteTime: false,
If the parameter is set to true or the parameter is commented out the module works fine. Before the updates this setting works fine.
-
Great, that helped, problem found and fixed!