Read the statement by Michael Teeuw here.
Transit module stopped working
-
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.
-
@Elaniobro glad I found the cause. sure makes for a deep dive into the stuff we use when something changes…
-
I’m running into this exact issue today. New install has not resolved. Neither has requesting a new API key. Any suggestions?
-
@nneuland I would post an issue to the module github for the developer
-
@sdetweil
Hi Sam. Yes, I did. Unfortunately because I am on a Pi4 they are unable to troubleshoot…I reinstalled the module fresh and retrieved a new API from api.mta.info, not clear on the error
socketNotificationReceived: “TRAIN_TABLE”:
Array(2)
MMM-nyc-transit.js:332 Uncaught TypeError: Cannot read property ‘fadeSpeed’ of undefined
at Class.socketNotificationReceived (:8080/modules/MMM-ny…-nyc-transit.js:332)
at module.js:245
at Socket. (socketclient.js:38)
at Socket…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
at Socket.emit (socket.io.js:1544)
at Socket.emitEvent (socket.io.js:1161)
at Socket.onevent (socket.io.js:1135)
at Socket.MMSocket.socket.onevent (socketclient.js:32)
at Socket.onpacket (socket.io.js:1089)
at Manager…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
