Cheers ronski for the suggestion - appreciated.
Ive been fighting code for months to get this working with the BTw API. It really doesnt seem to like non BTw based data. I've even alerted Sam but his checker is also having the same issue. In fact its worse than mine as it will give you false results for LLU lines
Try using
https://www.samknows.com/broadband/broadband_checker for a non BTw based line.
If you put in a non-BTw phone no
OR postcode and non-BTw phone no... it will tell you.
FTTC is not yet available in your area
I did actually try calling a separate address based request to the API for non FTTC lines, but it still only returns a generic "FTTC is available in your area" and no actual FTTC line speed data. I have a basic unpretty one which returns nothing useful only xml data array containing no speeds
Again look how Sam's wont return anything either. We have both hit the same issue
It literally has taken months to get it doing what it does. I saw no point in coding a separate front page for address based system that still wont play properly.
The 'hack' I implemented is actually doing quite a lot in the background to ensure that it doesn't send back false results. No joke there's hundreds of lines of code just to catch the LLU lines and force separate requests to get DSL data and not throw false FTTC results, thats what the second call is hiding and why there is now the additional step to complete.
Ive been playing with this on and off for well over a year without any success so the option was do what Sam has and still get no line info and let it send false results for PostCode and Tel.... or the hack that I finally settled on which doesnt give false info and still only returns the same result. I saw no point in holding off any further and just released what I could.