Securifi Community Forum
Securifi Products => Almond+ => Topic started by: jbell77 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
-
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.
-
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. :(
-
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+.
-
Ahh, understandable. Must I be online for said pairing? (I'm imagining it's not necessary)
Thanks!
J
-
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.
-
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)?
-
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.
-
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?
-
@ jbell77,
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.
-
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!
-
@ 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!
-
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...
-
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?
-
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.
-
You are kidding me.
You had to bring the router to the lock? Well I haven't tried that, but I did finally manage to get a factory reset done.
(For those following the helpful instruction video Schlage has online, the key is to completely ignore it. The video is wrong. Follow the reset to default procedure in the user guide - the video indicates holding down interior Schlage button to during battery reconnection, while manual tells you to hold down exterior Schlage button. If you thought you were going nuts, it isn't you.)
Trying to rejoin the Almond's zwave network has been ridiculous. Screen UI times out, webUI times out.
So I'll wait for a quiet time in the household to shutdown the router, unplug everything, haul it over to the lock, reboot it and attempt to re-pair the lock, hope that works, shut down, return to the thing to my WAN wire, reboot and hope it continues working.
Am I the only one who finds this procedure for pairing a WIRELESS DEVICE patently RIDICULOUS? Particularly given that it USED TO FUNCTION CORRECTLY.
Q. for Ashok. Is this being dealt with in any of the beta firmwares in the pipeline, or worked on at all?
Perhaps I should just buy a Wink?
-
You had to bring the router to the lock?
Most instructions on pairing zwave is to bring them within a few feet of the controller before installing. Someone with more expertise can correct me where needed.
Zwave as we all know is a mesh network. If device A is too far from my controller, I can bounce a message from device D through C,B and then to A. There is a chicken and egg issue here, before I can do that device A needs to be part of the network, but it won't pair if it is too far. Once joined, I can then install it and reach it through the mesh. By bringing the controller to the device did the same only in reverse.
-
I was able to join it successfully upon initial install without all this nonsense, but alright.
Q. Is it enough to bring the router right up to it and power it without any Internet access or do I need to run an ethernet cable all the way there too so the A+ still has cloud access?
-
A+ still has cloud access?
My understanding, the A+ does not need cloud access. That was why I picked it over ST. I am new and learning, but to move the A+ closer to a device my guess is all you need is power and the A+.
I was able to join it successfully upon initial install
What I hear you saying is, it worked the first time why not now. This makes me think you have had it for sometime. Do you maybe the battery was down just a hair and that was why the A+ had to be closer this time? Again, just guessing?
-
I had already changed out the batteries after it stopped responding.
-
@ Shazster,
You are kidding me.
You had to bring the router to the lock? Well I haven't tried that, but I did finally manage to get a factory reset done.
(For those following the helpful instruction video Schlage has online, the key is to completely ignore it. The video is wrong. Follow the reset to default procedure in the user guide - the video indicates holding down interior Schlage button to during battery reconnection, while manual tells you to hold down exterior Schlage button. If you thought you were going nuts, it isn't you.)
Trying to rejoin the Almond's zwave network has been ridiculous. Screen UI times out, webUI times out.
So I'll wait for a quiet time in the household to shutdown the router, unplug everything, haul it over to the lock, reboot it and attempt to re-pair the lock, hope that works, shut down, return to the thing to my WAN wire, reboot and hope it continues working.
Am I the only one who finds this procedure for pairing a WIRELESS DEVICE patently RIDICULOUS? Particularly given that it USED TO FUNCTION CORRECTLY.
Q. for Ashok. Is this being dealt with in any of the beta firmwares in the pipeline, or worked on at all?
Perhaps I should just buy a Wink?
The Z-wave protocol is designed in such a way that, whenever, a Z-wave sensor is in pairing mode it runs a very low power and which is why controller has to be with in 1 mt distance and it has nothing to do with what Z-wave controller we are using.
-
@ Shazster,
I was able to join it successfully upon initial install without all this nonsense, but alright.
Q. Is it enough to bring the router right up to it and power it without any Internet access or do I need to run an ethernet cable all the way there too so the A+ still has cloud access?
As mentioned by penright, we don't need the Cloud access for adding any sensors. In your case, please do move the Almond+ near the Lock and then first follow a proper removal process and then try pairing it.
Removing:
Tap on Add sensor-->Remove (not remove all) --> Follow the removal process on Lock.
-
Sensor removed a looooong time ago.
Lock is currently set to factory defaults as per Schlage manual.
Almond powered down, uncabled from my network, brought within 6 INCHES of Schlage lock, repowered on.
Tried pairing.
Red X indicating failure to pair on lock.
Pair process never completes at the Almond.
What else have you got?
-
@ Shazster,
Sensor removed a looooong time ago.
Lock is currently set to factory defaults as per Schlage manual.
Almond powered down, uncabled from my network, brought within 6 INCHES of Schlage lock, repowered on.
Tried pairing.
Red X indicating failure to pair on lock.
Pair process never completes at the Almond.
What else have you got?
From the Connected sensors, if we remove the lock that won't get the network to be removed from the lock and it would only be removed from the Almond+. Hence, please do follow the process and we should get the message on the LCD "Unknown sensor removed" only then, we can add it or else we would not be able to add it at all. Resetting the lock to the factory defaults also, would not allow the existing network to be removed from the lock.
Removing:
Tap on Add sensor-->Remove (not remove all) --> Follow the removal process on Lock.
-
That would have been useful information before I disconnected everything.
1- How about Securifi up their game with documentation a bit?
2-The enroll/unenrollment process at the lock is IDENTICAL (Do once to enroll, do again to unenroll). There is nothing on the lock that indicates its current state ie. Whether it is in fact enrolled, thus I need to undo it, or unenrolled, in which case I can just proceed to enroll with the Almond+.
But regardless, I did the procedure over and over and over, never receiving anything but a big red X. So here is what I will try:
1 Factory default reset at lock (Again).
2 unenrollment/enrollment procedure under the assumption the lock is still enrolled.
3 begin Almond+ pairing.
4 unenrollment/enrollment procedure under the assumption the lock is now cleared of enrollment.
5 hope to finally see a green checkmark.
Here's a question: should the Almond+ be completely powered down during attempts at unenrollment?
-
The step you are missing is putting the lock into pair mode and selecting remove (not remove all) from the Almond. This is what actually resets the z wave network information on the lock. This is the same for all z wave devices every where and again none of this is Almond exclusive.
-
Ok..so where in this list am I missing that step? (Bearing in mind that sensor was previously removed from the Almond)
1 Factory default reset at lock.
2 UNENROLLMENT/enrollment procedure under the assumption the lock is still enrolled. (Ext. Schlage button + programmer code + 0)
*****REMOVE (NOT REMOVE ALL) FROM ALMOND******here?
3 begin Almond+ pairing.
4 unenrollment/ENROLLMENT procedure under the assumption the lock is now cleared of enrollment. (Ext. Schlage button + programmer code + 0)
5 hope to finally see a green checkmark.