We can close this issue, it was resolved on github. The module itself never broke, it was an upstream service that did. A module that I was using, was using deprecated endpoints. I spoke with the developer and the MTA and we were able to isolate and resolve it.

In addition, not only did the endpoints change but any API keys generated on their old site, datamine.mta.info will no longer work.

You will need to create a new one via api.mta.info moving forward.

Thank you for your assist and feed back.

We can close this issue, it was resolved on github. The module itself never broke, it was an upstream service that did. A module that I was using, was using deprecated endpoints. I spoke with the developer and the MTA and we were able to isolate and resolve it.

In addition, not only did the endpoints change but any API keys generated on their old site, datamine.mta.info will no longer work.

You will need to create a new one via api.mta.info moving forward.

Thank you for your assist and feed back.

@sdetweil Welcome to assist, you can find the repo here: https://github.com/Elaniobro/MMM-nyc-transit

I do have it cleaned up a bit locally, but I am thinking my API key is no longer valid and or something changed upstream that I am not aware of. The mirror is doing what it should and returning results array, but the array is empty.

@sdetweil Thank you for your feedback. I am/was already debugging in the manner you mentioned. I was able to resolve the bug(s), but now I am still not seeing any data. My best guess is somewhere along the fetch of the data something changed or broke. The application is returning data, but the response is empty.

payload = [{ downTown: [] }, { upTown: [] }]

For some reason, just not getting any data

I am still digging in.

@sdetweil They aren’t, they can be removed. Issue I am seeing is the payload is not populated indo the getDom()

I am setting this.result = payload which on intitial load/start of the module is undefined, which is expected, since the API promise has not been fulfilled. Later on, the socketNotificationReceived() recieves a payload which is set to this.result but in the getDom() var data = this.result is never updated.

I am unsure of where/what caused this breakdown, as last time I touched the code was Apr 30. This is leading me to believe something changed in Core, but I am unaware of what that might be.

@sdetweil Its called in the socketNotificationReceived() here:
https://github.com/Elaniobro/MMM-nyc-transit/blob/master/MMM-nyc-transit.js#L358-L360

The module is getting the data, but its not updating with the this.updateDom method. I am not sure if this was deprecated or not. Looking into it.

@sdetweil what makes you think the API changed? ( I am the author, and am looking into it now)

Sreen shot:

Made a rather robust Magic Mirror Module that will track any MTA Subway train’s departure from any NYC Subway station. It is pretty configurable, allowing you to display as a marquee or list and gives you the option to pad the departure time with walking time to the train station as well as letting you select multiple trains/stations and choose which direction for each train!

Any and all feedback is welcome, it is written in vanilla JavaScript with little ES6 syntax because of mirror limitations on a raspberry pi0w

https://github.com/Elaniobro/MMM-nyc-transit

I myself wrote one if you want to check it out. Feedback is welcome:
https://github.com/Elaniobro/MMM-nyc-transit