Transit module stopped working

[elliob]

@sdetweil how did you get to error message? What’s the CLI?

[sdetweil]

@elliob it was in the pm2 log in the 1st post of this topic

[nipper2000h]

@elliob I’m using pm2 to start MM so from the root directory:

pm2 logs mm

[sdetweil]

@nipper2000h the logs are stored in the users .pm2 folder. doesn’t matter where I issue the pm2 commands

[Elaniobro]

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]

@Elaniobro how does it use this.updateDom()

[Elaniobro]

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

[sdetweil]

@Elaniobro where is self set.? and fadeSpeed?

[Elaniobro]

@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]

@Elaniobro are u debugging w the developers window?
you can walk thru the code as it executes
ctrl-shift-i and select the sources tab, use the tree on the left to find your module, and it’s source

then click the left edge of a line of code u want to examine, and a stop will be added.

usually a problem like this is because the ‘this.’ pointer doesn’t point where u think it does.

sorry, I am in hospital for a few more days and cannot debug from here