In reply to a post by DYMO:

yes ggremlin i have swapped over with my daughters router both hh5 mine was a 5a hers is a 5b,i have read that there are better modems out there do you think that getting one would improve things

Getting a different modem is not necessary, the homehub does not drop 15 times in an hour unless there is a definite line fault / poor wiring internally (does not seem to be the case) / electrical interference in the property (again does not seem to be the case).

BT are very poor at accepting a fault and getting engineers out in my experience. Is the landline all clear or is there audible noise on the line. You stand a better chance reporting a voice fault a lot of the time, as this impacts the broadband, usually where there are broadband issues there is fuzz on the line which BT have to resolve.

Ahhh, in their 80s.

Maybe one of these.

(Note the icon on the post).

hi ukhardy07...the line is clear and as you say BT are very poor at accepting a fault and getting engineers out,the last time i contacted them they said there was a line fault and they would monitor it for 72hrs when questioned why as a fault was present he said it was procedure
so 72hrs later they said line was clear ?????

haha Robertos yes there is one next door but has been there for some time lol

A motor characteristic can suddenly change. If for example the brushes are wearing, when they get fully worn down there could be arcing, or if one partially break, the same can happen. Do not discount it, just because it has been there for years.

Hi anyone any idea what is happening here?

00:56:41, 04 Jun. (36505.330000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.100000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.090000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.080000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.070000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.060000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.050000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.040000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.030000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.020000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.010000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.000000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.990000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.980000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.970000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.960000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.950000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.940000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.930000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.920000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.910000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.900000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.890000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.880000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.870000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.860000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.850000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.840000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.830000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.820000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.810000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.800000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.790000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.780000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.770000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.760000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.750000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.740000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.730000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.720000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.710000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.700000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.680000) CWMP: Initializing transaction for event code 2 PERIODIC

the hub is sending a termination request ?

That's just a code 2 periodic session which is standard when the hub contacts the BT server, often to check for new firmwares etc.

As for the line, there does appear to be a significant issue.

ok thanks both