Reported in the General Fault category anonymously at 18:12, Tuesday 7 July 2020
Sent to TfL less than a minute later. TfL ref: FMS2190201.
The beeping noise from the pedestrian crossing is extremely loud (Landsdowne Way + Wandsworth Road intersection). This is particularly invasive during summer months when windows must be open, and this disrupts my sleep as I often work nights and need to sleep during the day.
According to my neighbour, this issue was logged (ref 14453530) and an engineer was sent out to reduce the volume level on 2020-Jan-02. Unfortunately I detect no improvement since then, and the noise level is still disturbing and distressing me.
I also reported this to Lambeth council but they have not replied to my queries since last year (I am following up with them again now.)
I would be most grateful if an engineer could be sent out to reduce the volume further.
Many thanks and regards.
Thank you for your report. This will now be investigated by our team, where possible and appropriate action will be taken. We will still try to update on the progress within 10 days, however in the current circumstances it may not be possible to do so while we focus on keeping our roads safe for critical workers as they to continue to support London
State changed to: Investigating
Posted by TfL at 21:14, Tuesday 14 July 2020
Your report has been investigated and we can confirm that there is a non urgent fault at these traffic lights. We have passed this to our contractors and you should see an improvement within 28 days. Thank you for taking the time to report this to us. Should you need anything else or have any questions please contact customer services on 0343 222 1234
State changed to: Fixed
Posted by TfL at 18:17, Wednesday 29 July 2020
Thanks for your response but I find it a little confusing. What "non urgent fault" has been found through your investigations? Can you explain what precisely the contractors have been contracted to do - presumably lower the volume settings? I would appreciate it if you were a bit more specific about how you intend to resolve this issue. And I am also a bit concerned that the status of this query has now been set to "fixed" despite nothing having actually been fixed. Is there a "pending", or equivalent status, that would fit more appropriately to the circumstances? Many thanks and regards.
Posted anonymously at 22:04, Saturday 1 August 2020
Provide an update