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: