I’m afraid that is beyond my capabilities, do you have any pointers please?

OK, so worked out how log to browser:

This data was grabbed 2021:01:29 and is 2 x days old, although when I grab from CURL command data is up to date:

Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-27T09:58:33Z, 116, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-27T10:07:26Z, 649, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-27T10:18:07Z, 1290, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 463, Coulsdon, Purley or Roundshaw, 2021-01-27T10:01:12Z, 275, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 463, Coulsdon, Purley or Roundshaw, 2021-01-27T10:18:28Z, 1311, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, S4, Coulsdon, Purley or Roundshaw, 2021-01-27T10:17:42Z, 1265, bus
MMM-TFL-Arrivals.js:88 {data: Array(6), timestamp: "January 29, 2021 2:40 PM", message: null}
MMM-TFL-Arrivals.js:200 (6) [{…}, {…}, {…}, {…}, {…}, {…}]
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-28T09:34:13Z, 1743, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-28T09:09:56Z, 286, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-28T09:25:15Z, 1205, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 127, Coulsdon, Purley or Roundshaw, 2021-01-28T09:16:38Z, 688, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, 463, Coulsdon, Purley or Roundshaw, 2021-01-28T09:23:07Z, 1077, bus
MMM-TFL-Arrivals.js:218 Woodcote Green, S4, Coulsdon, Purley or Roundshaw, 2021-01-28T09:19:04Z, 834, bus

Thanks for your reply.
Actually, I think I’ve posted in the wrong place. I’m not developing a module, I’m using MMM-TFL-Arrivals, perhaps I should post in the “Troubleshooting” Category?

But yes CURL data is correct.

I’m trying to look at the log for MMM-TFL-Arrivals, having set logging to “true” but I can’t see where that is saved?

Re: MMM-TFL-Arrivals - Real time TfL arrival predictions for bus/tube/etc stops

I have one bus stop namely 490014138S which evey other time it polls the tfl data returns the same list of buses and times. It is as if there is some data stuck in a cache somewhere. Also intermittently the “correct” data is often stale.
The data is correct on my Android bus app.

I have tried a different browser, reinstalling module and changing refresh rate down to 30secs (and up to 2mins in case tfl getting upset).

Bus stop 490014138N, works perfectly.

Has anyone got any suggestions please?