In the early days of MagicMirror,
i got a module, that was able to fetch data from OpenHAB and displays it in place (instead of the compliment section)
If the string is empty, the comments won’t be hided.

Is it possible to bring this to the current version of MagicMirror?

https://raw.githubusercontent.com/Dom1n1c/Smartmirror/master/js/openhab/openhab.js

mine is also freezing after the update.
No difference if i connect via vnc or using the monitor.

The only thing that does work, is opening the mirror in another browser (http://magicmirror:8080)

@Hein-Jan I got the same issue.
A few minutes, the monitor could be controlled, but then “tvservice -p” fails to power on the monitor.

@lavolp3 i missed the most recent MMM-Updated.
I did a backup and reinstalled MagicMirror.
It’s working again.

Hey,

Some time ago, I was able to access the Mirror from my local Intranet by calling http://10.0.0.10:8080
The mirror itself is still showing content. But this refers to the localhost.

How can I adjust the ipWhiteList in order to access the mirror?

Maybe you can get in touch with the MVV developers. They might be able to tell you, which api endpoint you can use.
Using the vrr endpoint might be a workaround since vrr and mvv worked together with mentz in the past.
Regarding the mvv, there were some changes on the webpage. Changing the URL parameter to the one used by vrr will redirect you to the ‘mobile’ homepage of the mvv.
Regarding the invisible stop ID:
mvv seems to work with cookies, so you are not able to find your stop id, since the conversion is done in the background.
I’m not sure if the mvv offers real time data, so if you are happy with the scheduled departures, you can consider using the vrr endpoint.

@Hawking I Think, that the API Endpoint is not correct.
You can try using:
http://efa.mvv-muenchen.de/mobile/XSLT_DM_REQUEST //seems to be wrong
http://efa-alt.mvv-muenchen.de/mvv/XSLT_DM_REQUEST

I can find the following stop-ID and line-IDs when using the VRR endpoint.

80000760

lines:

DDB:92M01: :H
DDB:92M01: :R
DDB:92M02: :H
DDB:92M02: :R
DDB:92M03: :H
DDB:92M03: :R
DDB:92M04: :H
DDB:92M04: :R
DDB:92M06: :H
DDB:92M06: :R
DDB:92M08: :H
DDB:92M08: :R

@Hawking I run the EFA departure monitor in the browser and then have a look in the source, this could easily be done with chrome (view-source:url)

Then you have the station and line ids, without running the crawler.

@Klizzy i modified the Code and now the EFA system seems to work for several locations.
This includes delays and changes to the schedule.

You might have a look on:

https://github.com/Dom1n1c/MMM-EFA-departures

Feel free to participate.

Hey All,

As you might have seen, i added MMM-EFA-departures to the module overview.
I can display real-time data and is now well formatted.
But, i need your help to improve it.

-replace the Destination name using key/value pairs in config.js, so everyone could use it, depending on their scenario.
-change the default view, when toogling is disable. (switch between absolute and relative time)
-display delay in a seperate column (realtime-departure is nice, but some might prefer to display the scheduled departure and the delay)

https://github.com/Dom1n1c/MMM-EFA-departures/issues

Thanks :smile:

@Sandy2503 You might have a look at the module again,
it seems to display connections now.
What does not work right now is including delays to the departure time.

Thanks to @joda92
Now the indentation works as expected.

Feel free to pull the Module from GitHub:
https://github.com/Dom1n1c/MMM-EFA-departures

There are a few who want to use the MMM-EFA Module (a local Transport departure Monitor, including real-time data)
https://github.com/Dom1n1c/MMM-EFA-departures

Maybe there is someone who can help me to avoid the overwritten section:

or you could use the mentz api, this should also work in the “forbidden city” / cologne :smile:

I requested support for Düsseldorf and so on:

https://forum.magicmirror.builders/topic/1904/mmm-efa-elektronische-fahrplanauskunft-mentz

Thank you @strawberry-3-141
Currently it’s a bit messed up, but it shows some departures:
https://github.com/Dom1n1c/MMM-EFA-departures

(Delays seems not to be displayed)

Like already discussed in other topics:
https://forum.magicmirror.builders/topic/763
https://forum.magicmirror.builders/topic/1719
https://forum.magicmirror.builders/topic/632/mmm-wienerlinien/9

There is an API for several Transportation companies called:
EFA (Elektronische Fahrplanauskunft) which means electric departure monitor in German.

This is a list of API endpoints i know so far:

VRR / Verkehrsverbund Rhein-Ruhr
http://efa.vrr.de/standard/XSLT_DM_REQUEST

VVS / Verkehrs- und Tarifverbund Stuttgart
http://www2.vvs.de/vvs/XSLT_DM_REQUEST

MVV / Münchner Verkehrs- und Tarifverbund
http://efa.mvv-muenchen.de/mobile/XSLT_DM_REQUEST

DING - Donau-Iller-Nahverkehrsverbund
http://www.ding.eu/mobile/ding2/XSLT_DM_REQUEST

traveline south east: Journey Planner
http://www.travelinesoutheast.org.uk/se/XSLT_DM_REQUEST

This one is already the right module (but it does not work right now):
https://github.com/gefangenimnetz/MMM-EFA-departures/

The Station IDs can be found here:
http://www.eg-blog.de/?p=822

Those are other regions, with the EFA, too.

You could use a provider which uses the Mentz System:
Short overview (not complete, there are a few more: http://www.fahrplanauskunftssysteme.de)

Verkehrs- und Tarifverbund Stuttgart GmbH
http://www2.vvs.de/vvs/XSLT_TRIP_REQUEST2
Verkehrsverbund Rhein-Ruhr
http://efa.vrr.de/standard/XSLT_TRIP_REQUEST2
Verkehrsverbund neckar-alb-donau
http://efa.naldo.de/naldo/XSLT_TRIP_REQUEST2
traveline south east: Journey Planner
http://www.travelinesoutheast.org.uk/se/XSLT_TRIP_REQUEST2
Salzburg Verkehr
http://efa.svv-info.at/svv/XSLT_TRIP_REQUEST2
MVV
http://efa.mvv-muenchen.de/mobile/XSLT_DM_REQUEST
Ding.EU
http://www.ding.eu/mobile/ding2/XSLT_DM_REQUEST

There are a few implementations of this system, like:

https://github.com/michiwend/goefa

EDIT: Maybe this one is already the right module:
https://github.com/gefangenimnetz/MMM-EFA-departures/

The Station IDs can be found here:
http://www.eg-blog.de/?p=822

You could use the API by the local organization unit, which is VRR for instance.
I wrote something about the VRR-Routing, which possibly may work for other Locations (At leat in NRW):
https://forum.magicmirror.builders/topic/1281/deutsche-bahn-list-of-connections-with-delays/3

Is it possible to access values from openhab?

The syntax of the rest interface in OH is:

IP:8080/rest/items/specificitem
And to get the ‘Raw’ result/value:

IP:8080/rest/items/specificitem/state

I saw that there were a few Addons (for my smartwatch) that could use both FHEM and OpenHAB

Thanks