On Jan 26, 3:25*pm, solar penguin
wrote:

Even when you don't time out at an OSI, Oyster can still get them
wrong and overcharge you! (Why am I not surprised!?!)

According to London Reconnections, Hackney Central/Hackney Downs is
supposed to be an OSI. But when I used it this morning, I got charged
for two different journeys: one going to Hackney Central, and another
one starting at Hackney Downs.

Any idea what could've caused this? *(Apart from the usual problems of
whole Oyster fares concept being seriously flawed, of course!)

Interesting. When I've used the Hackney Central/Downs OSI in the past
it's worked fine, but I haven't used it this year yet.

I'm tempted to ask for your journey details, but it shouldn't really
make any difference whatever they were, unless I'm overlooking
something.

You could always send some feedback to the Oyster people using the
online form available on the TfL website he
http://www.tfl.gov.uk/contact
I dare say this is less painful than calling up the helpline, and
perhaps more likely to result in the message getting through to the
right people who could investigate and sort out any problem there may
be with the configuration of this OSI.