@Davepre

The issue is with TransportAPI and I’ve contacted their support with the following info:

Using ‘https://transportapi.com/v3/uk/bus/stop/490013443E/live.json?app_id=a111aa11&app_key=1a11111a1111aaa11a1a1111a11111a1&group=route&nextbuses=no’

I get the following info (snippet):

departures: 
{
44: 
[
{
mode: "bus",
line: "44",
line_name: "44",
direction: "Victoria",
operator: "LONDONBUS",
date: "2017-07-25",
expected_departure_date: "2017-07-25",
aimed_departure_time: "09:18",
expected_departure_time: "09:18",
best_departure_estimate: "09:18",
source: "Countdown instant",
dir: "inbound",
id: "https://transportapi.com/v3/uk/bus/route/LONDONBUS/44/inbound/490013443E/2017-07-25/09:18/timetable.json?app_id=a111aa11&app_key=1a11111a1111aaa11a1a1111a11111a1",
operator_name: "London Buses"
},

If I use ‘https://transportapi.com/v3/uk/bus/stop/490013443E/live.json?app_id=a111aa11&app_key=1a11111a1111aaa11a1a1111a11111a1&group=no&nextbuses=no’

I get the following info (snippet):

{
mode: "bus",
line: "44",
line_name: "44",
direction: "Victoria",
operator: "TFL",
date: "2017-07-25",
expected_departure_date: "2017-07-25",
aimed_departure_time: "00:45",
expected_departure_time: "09:18",
best_departure_estimate: "09:18",
source: "Countdown instant",
dir: null,
id: null,
operator_name: null
},

Same bus, same info except the aimed_departure_time that is now 00:45. This means that when I calculate the delay, I get hundreds of minutes and the bus never drops out of the results.

So the issue appears to be with the ‘group=no’ URL variable.

Hopefully they will address this or at least get back to me. In the meantime I will see what I can do to remove these ghost buses.

@Davepre said in MMM-UKLiveBusStopInfo - Arrivals & Departures from a UK Bus Stop:

490013443E

Can you send me the config you are using - I can see weird things happening with the feed - e.g. 08:45 seems to become 00:45 for some reason, but I’d like to make sure that I’m setup the same way as you.

@Davepre I’ll have a look and see what I can do. Can you tell me all the bus stop codes you are using?

It’s possible that TfL (or whoever) is not passing the info across to Transport API or that Transport API are not passing it down to the module correctly.

The more common error is that the bus operators don’t actually send anything and this was breaking the module.

Nick

Description :
Retrieves information about bus services running through a specific UK bus stop. Built on the Transport API .
See documentation in the README and on the TransportAPI developer portal.

Screenshot:

GitHub:
https://github.com/nwootton/MMM-UKLiveBusStopInfo

@randomnoise Thanks for that, glad you like it. There’s a bus version as well if you want it!

Can you stick a link to the Reddit post up here if you get a chance, would be nice to see one in the wild so to speak!

@arjunrao87 I’m trying to figure this out myself - did you get anywhere?

I can find lots of information about the MM Test Suite, but I just want to write tests against a specific module I’m developing. Normally I’d use Mocha, but that just throws error after error when I try to get it to do anything against my own module.

New version release - better layout, more display options and ability to run multiple station configs.

Please provide feedback either here, or by opening an issue on GitHub here.

Thanks.

@soqueen TBH I rolled the master branch back to an earlier version that worked and branched the version with the bus stop name as the header.

Once I get the last couple of issues in that branch version sorted I’ll role it back into the master. If you want to try it and give me feedback, the branch is called HeadersIssue.

@soqueen I’ve just noticed some weird behaviour this end while trying to fix this. Did you update your Mirror to 2.1.1? If so did you then do a new npm install afterwards?

I ask because on one box the departures now shows no header at all, while the other now shows both departures AND the bus stop name…

@soqueen I’ve just hacked a fix together. Give it a try and let me know.