Choose style:
« previous next »
Pages: [1] 2   Go Down

Author Topic: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619  (Read 12773 times)

0 Members and 1 Guest are viewing this topic.

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« on: December 14, 2016, 11:11:56 am »
https://www.amazon.com/gp/product/B00AGK9KJQ/ref=oh_aui_search_detailpage?ie=UTF8&psc=1

Hi all,

Anyone have luck getting this connecteted?  When I try, it'll take a really long time for the A+ to get the sensor info, then see it as "DoorLock #x" yet after adding it, it cannot be found.  I tried removing and readding it several times too.

Can support for this be requested for the next firmware update if need be?

Thanks!
Jason
Logged

Offline d.kiran

  • Backer
  • *
  • Posts: 500
  • Thanks: 0
    • Registered : 11/09/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #1 on: December 14, 2016, 01:00:41 pm »
I had exactly the same problem. What you can do is try to remove and add another device and then add the lock again. Also, the almond has to be very close to the lock. I kept it about 6 ft apart. After putting them 1 ft apart, it started pairing much better.
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #2 on: December 14, 2016, 01:27:56 pm »
Thanks for the tip. I just tried that (removed a GE lighting plug in) then re-added the lock -- same thing.  DoorLock23 now (from I think 19 when I first started ) :(  I didn't mess with the distance any though as that'll be a real PITA (it's about 15ft away currently).  Not sure how it appears to add, but actually doesn't (though seemingly does to a degree based on the increasing number per attempt).

I swear I'm contemplating SmartThings more and more lately. :(
Logged

Offline mparadis

  • Backer
  • *
  • Posts: 1765
  • Thanks: 3
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #3 on: December 14, 2016, 03:27:58 pm »
Most devices must be within 3 feet to pair. For door locks it is a requirement for security reasons. Your best bet is to move the Almond + over to it for the install and then move the Almond + back. This is a protocol issue not Almond+.
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #4 on: December 14, 2016, 09:23:40 pm »
Ahh, understandable.  Must I be online for said pairing?  (I'm imagining it's not necessary)

Thanks!
J
Logged

Offline mparadis

  • Backer
  • *
  • Posts: 1765
  • Thanks: 3
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #5 on: December 14, 2016, 09:28:43 pm »
Not at all, all HA functions work without being online, but are only accessible from in the house. You can certainly pair without being connected. For this reason I use a POE adapter with my wall mounted A+ so I can take it down and move it around easier as needed without having to worry about the power supply being wired into the wall.
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #6 on: December 14, 2016, 09:36:29 pm »
Thanks for the info, and good idea!!  DIdn't think about POE (only considered it for cameras before).  You can just use a POE adapter and not give up a port (other than maybe speed limitation)?
Logged

Offline mparadis

  • Backer
  • *
  • Posts: 1765
  • Thanks: 3
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #7 on: December 15, 2016, 10:13:39 am »
I do not use the Poe Ethernet cable for my connection to the router, I only use it to run the power so I have a second Ethernet cable for my router connection. So I run two cables total.
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #8 on: December 15, 2016, 12:45:19 pm »
I just about give up.  I moved the A+ over to within 1 foot of the lock and have the same exact experience.  I removed it first (to which I'll see "removing unknown sensor") then when I re-add it, after like 90 seconds of "getting sensor info" it'll let me add it as "DoorLick#XX" but doesn't list at all.  I even removed and re-added a different sensor before trying this again (tried several times).  Not sure what else it could be?
Logged

Offline Ashok

  • Securifi Staff
  • *
  • Posts: 2770
  • Thanks: 3
    • Registered : 25/07/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #9 on: December 15, 2016, 03:32:24 pm »
@ jbell77,

Quote from: jbell77 on December 15, 2016, 12:45:19 pm
I just about give up.  I moved the A+ over to within 1 foot of the lock and have the same exact experience.  I removed it first (to which I'll see "removing unknown sensor") then when I re-add it, after like 90 seconds of "getting sensor info" it'll let me add it as "DoorLick#XX" but doesn't list at all.  I even removed and re-added a different sensor before trying this again (tried several times).  Not sure what else it could be?

Log files would be more helpful to understand the issue and update you the status.
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #10 on: December 15, 2016, 04:41:59 pm »
Dec 15 16:30:37 AlmondPlus kern.warn kernel: FWLOG: [14392093] vap-0 AP PS: AID=3 detected out-of-sync now=14392093 tx_waiting=14382070 txq_depth=1
Dec 15 16:30:38 AlmondPlus kern.warn kernel: FWLOG: [14392357] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:30:41 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:30:52 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:02 AlmondPlus kern.warn kernel: FWLOG: [14417309] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:31:07 AlmondPlus kern.warn kernel: FWLOG: [14422213] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:31:09 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:10 AlmondPlus user.info sysinit: The source address 10.10.10.98 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:20 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:37 AlmondPlus user.info sysinit: RECV Membership query   from 10.10.10.254    to 224.0.0.1
Dec 15 16:31:38 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.114    to 239.255.255.250
Dec 15 16:31:38 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:31:38 AlmondPlus user.info sysinit: The source address 10.10.10.114 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:40 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:41 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.255.255.250
Dec 15 16:31:41 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:31:43 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 224.0.0.2
Dec 15 16:31:43 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:31:44 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.0.0.250
Dec 15 16:31:44 AlmondPlus user.info sysinit: Updated route entry for 239.0.0.250 on VIF #1
Dec 15 16:31:47 AlmondPlus user.info sysinit: addGroup: node 30 group 1 n 0
Dec 15 16:31:47 AlmondPlus user.info sysinit: addGroup: node 30 group 2 n 0
Dec 15 16:31:55 AlmondPlus user.info sysinit: addGroup: node 30 group 1 n 0
Dec 15 16:31:55 AlmondPlus user.info sysinit: addGroup: node 30 group 2 n 0
Dec 15 16:31:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:10 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:41 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:14 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:20 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:40 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:42 AlmondPlus user.info sysinit: RECV Membership query   from 10.10.10.254    to 224.0.0.1
Dec 15 16:33:44 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 239.255.255.250
Dec 15 16:33:44 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:33:44 AlmondPlus user.info sysinit: The source address 10.10.10.254 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:46 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.0.0.250
Dec 15 16:33:46 AlmondPlus user.info sysinit: Updated route entry for 239.0.0.250 on VIF #1
Dec 15 16:33:46 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.128    to 239.255.255.250
Dec 15 16:33:46 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:33:46 AlmondPlus user.info sysinit: The source address 10.10.10.128 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:47 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 224.0.0.2
Dec 15 16:33:47 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:33:48 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.199    to 239.255.255.250
Dec 15 16:33:48 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:33:48 AlmondPlus user.info sysinit: The source address 10.10.10.199 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:14 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:20 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Dec 15 16:34:20 AlmondPlus user.info sysinit: Svc Disc: Starting discovery for cluster 0x0019^M
Dec 15 16:34:20 AlmondPlus user.info sysinit: Svc Disc: Waiting 2 sec for discovery to complete^M
Dec 15 16:34:22 AlmondPlus user.info sysinit: Svc Disc: complete.^M
Dec 15 16:34:22 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Dec 15 16:34:25 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:25 AlmondPlus user.info sysinit: entered receive thread
Dec 15 16:34:39 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.


System Log ^^^ During that timeframe I removed and readded the lock.

I get a lot of this in the Kernel log:Dec 15 16:30:37 AlmondPlus kern.warn kernel: FWLOG: [14392093] vap-0 AP PS: AID=3 detected out-of-sync now=14392093 tx_waiting=14382070 txq_depth=1
Dec 15 16:30:38 AlmondPlus kern.warn kernel: FWLOG: [14392357] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:30:41 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:30:52 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:02 AlmondPlus kern.warn kernel: FWLOG: [14417309] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:31:07 AlmondPlus kern.warn kernel: FWLOG: [14422213] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Dec 15 16:31:09 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:10 AlmondPlus user.info sysinit: The source address 10.10.10.98 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:20 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:37 AlmondPlus user.info sysinit: RECV Membership query   from 10.10.10.254    to 224.0.0.1
Dec 15 16:31:38 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.114    to 239.255.255.250
Dec 15 16:31:38 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:31:38 AlmondPlus user.info sysinit: The source address 10.10.10.114 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:40 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:31:41 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.255.255.250
Dec 15 16:31:41 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:31:43 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 224.0.0.2
Dec 15 16:31:43 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:31:44 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.0.0.250
Dec 15 16:31:44 AlmondPlus user.info sysinit: Updated route entry for 239.0.0.250 on VIF #1
Dec 15 16:31:47 AlmondPlus user.info sysinit: addGroup: node 30 group 1 n 0
Dec 15 16:31:47 AlmondPlus user.info sysinit: addGroup: node 30 group 2 n 0
Dec 15 16:31:55 AlmondPlus user.info sysinit: addGroup: node 30 group 1 n 0
Dec 15 16:31:55 AlmondPlus user.info sysinit: addGroup: node 30 group 2 n 0
Dec 15 16:31:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:10 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:41 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:32:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:14 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:20 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:29 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:40 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:42 AlmondPlus user.info sysinit: RECV Membership query   from 10.10.10.254    to 224.0.0.1
Dec 15 16:33:44 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 239.255.255.250
Dec 15 16:33:44 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:33:44 AlmondPlus user.info sysinit: The source address 10.10.10.254 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:46 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.225    to 239.0.0.250
Dec 15 16:33:46 AlmondPlus user.info sysinit: Updated route entry for 239.0.0.250 on VIF #1
Dec 15 16:33:46 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.128    to 239.255.255.250
Dec 15 16:33:46 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:33:46 AlmondPlus user.info sysinit: The source address 10.10.10.128 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:47 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 224.0.0.2
Dec 15 16:33:47 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Dec 15 16:33:48 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.199    to 239.255.255.250
Dec 15 16:33:48 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Dec 15 16:33:48 AlmondPlus user.info sysinit: The source address 10.10.10.199 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:33:59 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:14 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:20 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Dec 15 16:34:20 AlmondPlus user.info sysinit: Svc Disc: Starting discovery for cluster 0x0019^M
Dec 15 16:34:20 AlmondPlus user.info sysinit: Svc Disc: Waiting 2 sec for discovery to complete^M
Dec 15 16:34:22 AlmondPlus user.info sysinit: Svc Disc: complete.^M
Dec 15 16:34:22 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Dec 15 16:34:25 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.
Dec 15 16:34:25 AlmondPlus user.info sysinit: entered receive thread
Dec 15 16:34:39 AlmondPlus user.info sysinit: The source address 10.10.10.225 for group 239.255.255.250, is not in any valid net for upstream VIF.


Thanks!


Logged

Offline Ashok

  • Securifi Staff
  • *
  • Posts: 2770
  • Thanks: 3
    • Registered : 25/07/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #11 on: December 16, 2016, 08:00:26 am »
@ jbell77,

As  per the log files, it seems like Door lock is sending the proper information, please remove the Door lock and then reset it to the defaults first and then try adding it. Thank you!

Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #12 on: December 16, 2016, 09:42:26 am »
See, this is what I am not understanding.  I have been doing that constantly, to no avail.  Everytime I do so, it will add the doorlock with an incremental number, e.g: DoorLock#21, DoorLock#22, DoorLock#23. 
And each and every time it is "added" it doesn't show up in my list of devices.   

Also, when I try removing the lock, the A+ will report it removed the "unknown sensor".

Any further insight?  there's something else up here...
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #13 on: December 16, 2016, 12:02:33 pm »
And interestingly, if I try it via the WebUI, I'll get "Device found. Processing..."  followed by a "Sorry. The device has times out"  Every time.  Perhaps the timeout interval could/should be adjusted?
Logged

Offline jbell77

  • Backer
  • *
  • Posts: 10
  • Thanks: 0
    • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Help: Schlage Connect Century Touchscreen Deadbolt BE469 CEN 619
« Reply #14 on: December 16, 2016, 02:24:22 pm »
Got it working.  After the advice here as well as reviewing other threads, I found this method worked for me:

1) Factory reset the lock
2)Moved Almond+ within ~1ft from the lock (hung it carefully on door handle via the power cable)
3) Removed the dock lock via the WebUI
4) Added the lock via the WebUI.

Thanks all for the help.
Logged
Pages: [1] 2   Go Up
« previous next »
 

Page created in 0.048 seconds with 16 queries.