cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Daveiw100
Aspiring Contributor
315 Views
Message 1 of 3

Intermittently unable to connect to HKC alarm system

I have recently had HKC alarm system installed, and have HKC SecureComm app installed on iPone and iPad.

Most of the time I am unable to connect to the system, but sometimes I connect OK, and can successfully control the alarm system

My alarm installer informed me that this a common problem with connection via BT Home Hub  (I have Home Hub 6)

Rounter Event log shows following on unsuccessful connection:

18:16:31, 26 Dec.

BR_LAN:The DHCP options that are offered by the device (id:171): DiscoverOptions: 53,55,57,61,51,12 | DiscoverOption55: 1,121,3,6,15,114,119,252 | RequestOptions: 53,55,57,61,50,54,12 | RequestOption55: 1,121,3,6,15,114,119,252 | HostName: iPad-3 | VendorId:

18:16:31, 26 Dec.

:DHCP Confirmation of Request

Any ideas how to resolve this issue?

0 Ratings
Reply
2 REPLIES 2
Keith_Beddoe
Distinguished Sage
Distinguished Sage
308 Views
Message 2 of 3

Re: Intermittently unable to connect to HKC alarm system

@Daveiw100 

You might be better off using a third party router, its likely to give you a lot less trouble than the HH6.

This one is very popular, and works with all BT services.

https://www.tp-link.com/uk/home-networking/dsl-modem-router/archer-vr400/v2/

If you only want 2.4GHz then there is a cheaper option, about £35.

https://www.tp-link.com/uk/home-networking/dsl-modem-router/td-w9970/

They are both very easy to configure.

0 Ratings
Reply
Daveiw100
Aspiring Contributor
263 Views
Message 3 of 3

Re: Intermittently unable to connect to HKC alarm system

Been doing some further investigation.......

BT HomeHub Event log always shows successful connection from polling every few minutes.......

-------------

12:53:49, 02 Jan.

eth2:[Device Connected] MAC Address:70:B3:D5:F1:F7:7D Host Name: IP Address: 192.168.0.245, lease duration is 86400 seconds.

12:53:49, 02 Jan.

BR_LAN:The DHCP options that are offered by the device (id:174): DiscoverOptions: 53,61,51,55 | DiscoverOption55: 1,3,6 | RequestOptions: 53,61,54,50,51,55 | RequestOption55: 1,3,6 | HostName: | VendorId:

12:53:49, 02 Jan.

eth2:DHCP Lease issued 192.168.0.245 to 70:B3:D5:F1:F7:7D

12:53:49, 02 Jan.

:DHCP Confirmation of Request

---------------

So why cannot I not always successfully ping the device?

Most of the time,  I get response "Destination Host unreachable", or "Timed Out".  Sometimtes I can successfully ping the device

0 Ratings
Reply