Securifi Community Forum
Sensors and Home Automation => Home automation => Topic started by: govee on August 08, 2014, 06:19:38 pm
-
I took a number of exclusion/joins but It finally joined. I can lock and unlock from the web ui. Android app shows it but does nothing.
-
I have this lock, but my A+ hasn't arrived yet to pair/test it out. I'll add my experiences when it arrives.
-
I installed the lock first. Join and exclusion was done from 20'.
-
We're aware of the not so great support for locks in the Android app and we'll get that fixed.
We've also improved the lock support in the most recent firmware that will be out shortly.
-
I finally got my hands on my A+ on Tuesday. Did the "Remove Sensor" step first (since there seem to be many reports of success) and then added the sensor from about 15 feet away. I was surprised that it took from that far, but I'm not complaining!
WebUI and Screen UI report that it's unlocked, regardless of the physical state of the lock. Trying to lock/unlock the unit from either UI tells me that it's processing.
-
We have a new firmware coming on Friday that includes some additional fixes for locks. Hopefully this will fix your problem.
If not, let us know.
-
Yup! Saw the heads up on the new firmware and looking forward to Friday. Just adding some notes!
-
I can confirm the same behavior. I hope the new firmware helps.
-
I can happily report that with R065, both WebUI and LCDUI can both control and correctly report the current state of this lock.
At first, it was stuck on "Unlocked" as in previous versions of the firmware, but after trying to lock/unlock from either UI, the state of the lock is now correctly shown.
Now, to figure out what the "UserNo" and "PIN" settings do without messing up the current codes I have in there.
Also, would this topic be a better fit if moved to the "Almond+ tested sensors/devices" Category?
-
User pin is so you can set a pin code if your lock has a key pad and that pin can then be used to unlock the door from the outside.
We have support for up to 20 users (user no), but your lock might not support that many.
Good to hear the new firmware sorted out your issues.
We still have a fair bit of work to do with regards to locks, so feedback is welcome.
I also moved this thread based on your suggestion.
-
I can happily report that with R065, both WebUI and LCDUI can both control and correctly report the current state of this lock.
At first, it was stuck on "Unlocked" as in previous versions of the firmware, but after trying to lock/unlock from either UI, the state of the lock is now correctly shown.
Now, to figure out what the "UserNo" and "PIN" settings do without messing up the current codes I have in there.
Also, would this topic be a better fit if moved to the "Almond+ tested sensors/devices" Category?
Hi, could you help me to connect Schlage BE469 lock to my A+, I have installed my locks 2 months ago and got mine A+ yesterday. I have no clue how to register them with A+. Thanks!
-
Tap on Add sensor in the LCD UI, if the locks have been associated with a different gateway, tap on Remove and proceed to adding the locks according to the supplied instructions. This will reset the locks back to factory default.
Now tap on add and repeat the procedure of adding the locks again, they should now pair and work with the Almond+.
-
Thanks, but does that mean locks will appear on LCD when click on "add a sensor" button or do I have to do something on locks?
-
You have to follow the Schlage instructions on how to associate the lock, just disregard from the "gateway" part, since all you have to do is to follow my instructions for the Almond+ part.
I honestly don't know exactly what you have to do on the locks.
-
I can chime in!
--------------------
On the A+, tap "Add Sensor" (Screen 1, lower left) and tap "Add"
On the Scalage BE469NX:
1) Extend the deadbolt
2) Press the Schlage button, keys will light up
3) Enter your 6 digit programming code (see your Schlage manual), orange light will light up and be steady.
4) Press "0" and the orange light will start blinking. If your A+ is still in Add sensor mode, the two devices will start communicating to pair.
5) The Schlage will beep and show the green checkmark if successful.
At this point, the A+ will say adding sensor, then getting sensor info, then it will prompt for a name and location.
------------------
-
Notes on Pairing:
Documentation for many Z-Wave devices say that during the pairing process, the two have to be within 3-6 feet of each other. From my personal experience, the first time I paired my Schlage and the A+, they were about 15' from each other with a cabinet between them. I recently had to relocate my cable modem and A+, and now the lock and the A+ are about 25'-30' between first and second floors, and they still pair.
There are some reports that Removing/Unpairing/Excluding the lock as the first step before adding/pairing/including is more successful, but since R065 and factory resets, I haven't had to do this.
Notes on controlling remotely:
The first time I paired the two on pre-R065 firmware, the A+ constantly reported the Schlage as unlocked and no controls were possible.
After updating to R065, both the LCD, Web UI (NutsOS), and connect.securifi.com showed the correct status of the lock and was able to lock/unlock.
At some point, I wanted to factory reset the A+. I unpaired the lock, then reset and set the A+ up again for routing. For some reason, I could pair but not control the lock anymore. After numerous pairing/unpairing attempts, it suddently started working again.
-
Thanks for big help, I'll try it today.
-
So I was able to add sensors to router, thanks.
Before doing that I upgraded to latest R065 and it worked fine. I have tried adding two of the schlage locks BE469, to register I had to take closer router to locks and was able to add both of them successfully. Now whenever I look at the sensor status it shows both of the locks always unlocked and does not affect on locks no matter how many time I have tried locking them, after showing refresh icon every time it says "please refresh and try again".
I have tried web UI, NUTS OS in browser etc, nothing seems to be changed, I have also tried looking at router LCD it show there are two sensors connected and unlocked.
Could you please help me to and let me know how to fix this issue.
Thanks,
-
So I was able to add sensors to router, thanks.
Before doing that I upgraded to latest R065 and it worked fine. I have tried adding two of the schlage locks BE469, to register I had to take closer router to locks and was able to add both of them successfully. Now whenever I look at the sensor status it shows both of the locks always unlocked and does not affect on locks no matter how many time I have tried locking them, after showing refresh icon every time it says "please refresh and try again".
I have tried web UI, NUTS OS in browser etc, nothing seems to be changed, I have also tried looking at router LCD it show there are two sensors connected and unlocked.
Could you please help me to and let me know how to fix this issue.
Thanks,
These are actually the locks I was looking at getting potentially. I know they're not listed in the xml file I mentioned in another thread. Not sure if that might be having an effect on things or not.
-
So I was able to add sensors to router, thanks.
Before doing that I upgraded to latest R065 and it worked fine. I have tried adding two of the schlage locks BE469, to register I had to take closer router to locks and was able to add both of them successfully. Now whenever I look at the sensor status it shows both of the locks always unlocked and does not affect on locks no matter how many time I have tried locking them, after showing refresh icon every time it says "please refresh and try again".
I have tried web UI, NUTS OS in browser etc, nothing seems to be changed, I have also tried looking at router LCD it show there are two sensors connected and unlocked.
Could you please help me to and let me know how to fix this issue.
Thanks,
This is the behavior that I was describing where I could pair the two, but could not control locking/unlocking functions. Each of the UIs would always say processing or that it couldn't read the sensor data.
I tried to exclude/include several times, and even factory resetting the A+. Somewhere along the way, the controls started working and has been since then. The way I can tell if it's working by refreshing the sensor data on Web UI (NutsOS) or on connect.securifi.com and NOT getting an error.
Keep in mind that even though I can currently control the lock, sometimes the UI will show "Unlocked" even though it's locked. I always make it a priority to Refresh the data before I try to lock/unlock.
-
thanks, I have refreshed both of the UIs multiple times and also tried shutdown router too. Behavior seems to be same no change in status and no effect when click on lock/unlock icons on both of the locks.
-
I know it can be frustrating when you know the capability is there, but it's not working as expected. I'm not sure what step allowed the setup to work with controls, but when it started working for me again, I decided not to mess with the sensor portion at all anymore.
Also, I noticed that the connect.securifi.com site was updated this morning, and it correctly shows the state of the lock when first loading the sensor tab, without having to refresh first.
-
We have a new Android app coming as well with a lot of lock related improvements.
-
I have updated to the latest firmware version R065. I have been able to enroll the lock the Almond+ but it is always showing the status as "unlocked". Also, it will not send a "lock" or "unlock" command the the deadbolt. Basically, it has no functionality at all. This lock worked perfectly with the Nexia bridge.
Please Help!
-
I don't have Android device to try it. I was hoping to get iOS app soon.
Tha19th and Lars: Last night I was trying things to get schlage locks work, and tried different option, all these things I did when I placed A+ Router to within 2-3 feet of door locks:
1) I removed all the sensors from router and then tried adding locks again, but some how this time lock would not register to router. After orange light beep on lock it was showing red cross light which probably mean did not registered. On the router it was not detecting any lock. I tried this on both locks, both shows the same red cross light.
2) Then I tried resetting locks to factory setting and tried it again, it did not detected/registered, shows the same red cross light.
3) Then I though of restoring the backup which I took 2 days ago from router. After restoring (archive/.tar file) I could see locks were there in Sensor section (all the UI were displaying both locks), but did not do any effect when refresh or try to lock. In fact both locks were show they were unlocked but they were not.
I contacted Securifi support via phone and tried different activities on router and locks for 45-60 minutes but it did not help at all, I was assigned a case which they will work on or research.
Is there any way I could unlink locks from z-wave controller (A+ or similar), because it might be possible that lock are still registered to router, since router I have already removed sensors but somewhere in locks memory it is still there?
-
Topics merged
-
Can you guys that are having problem with the locks do one thing for me?
Add the lock fresh, go to help, send logs and send a log. Type the model of the lock in the text box provided.
This will allow the software team to take a look at what's going on, as these should be no different from the other Schlage locks we support.
Restoring a backup will NOT fix sensor issues, as once you've unpaired a sensor, the unique key which is used when it's paired is lost and the sensor/device will not work with the old key.
To remove a sensor/device, simply go to Add Sensor, remove and follow the instructions from the device/sensor manufacturer. Usually removing something is done the same way as adding something. This can also be done with a sensor/device that have not previously been paired to the Almond+, but to another gateway/controller, but wasn't removed properly from it.
-
arckal:
Keep in mind that while the "Remove All Sensors" option on the A+ makes the sensors disappear from the A+, the sensors/locks are still paired from their side.
From the sensor's point of view, it is still paired and will continue to try to connect with the controller, even though the controller no longer tries to communicate with them. This is the whole point of doing a "Remove" (NOT "Remove All Sensors") because it causes the sensor/lock to mututally dissociate with whatever controller they may have been linked to before.
The manual from Schlage (http://www.schlage.com/content/dam/sch-us/documents/pdf/installation-manuals/24060857.pdf) differs slightly from my printed one that came with my lock, but has more generic Z-wave info.
The manual from Amazon (http://ecx.images-amazon.com/images/I/E127XNY2ZsS.pdf) looks like mine, but talks about Nexia Home Intelligence.
Both of them talk about how to do a Factory Reset on the lock, but I'm not sure if that clears any Z-Wave associations.
----------------------
Lars:
Does this info about Z-Wave programming from Schlage's website help the software team?
http://www.schlage.com/content/dam/sch-us/documents/pdf/installation-manuals/24352403.pdf
If needed, is there a way to capture logs from a working system (such as my current pairing)? For example, can I send a "lock" command and then an "unlock" command and then send the logs?
-
A factory reset of locks does not clear the Z-Wave settings.
I'll pass on the info, but not sure if an already paired lock well help or not, I'll check tomorrow though.
-
So if sensors were already removed from Router then how do we unenroll locks?
-
arckal: As long as you're in "Remove" sensor mode on the A+ and you put the sensor/lock in inclusion/exclusion mode, they will unpair. You can remove a sensor even if the A+ doesn't list it, it just reports "Unknown sensor removed". I've gone through the "Remove" process several times even if it's not listed on the A+ to ensure the lock has been excluded.
Again:
On the A+
From home screen, go to the "Add Sensor" option, then select "Remove"
On the Schlage:
Lock the deadbolt
press the schlage button
enter the programming code
press 0
If you get the green check, it's successfully removed. If you get the red X, the lock still considers itself paired.
-
My lock was able to pair. But the android app, router, and webui shows the wrong lock state. I can't save my user code.
System log has been sent.
-
Thanks The19th you are the savior. I was able to unenroll both of the locks, and also able to enroll them back in router. But status remain same, it shows unlocked all the time and does not change when lock gets locked or unlocked or even try to lock from any of the UIs.
Lars: it seems firmware R065 has a bug related to z-wave locks.
-
We'll have an updated Android app out shortly that will address the lock issues.
R065 does not have a bug when it comes to locks, it works with all other types of locks, but it might be that we're missing something specific to this model from Schalge.
-
I think there should be an unenroll command on the lock itself.
If that doesn't exist, you could try adding the lock back to the Almond, then doing a remove.
-
There is no "unenroll" command on the lock. You can put the lock in enroll/unenroll mode, but the lock just sits there with a blinking orange light until a controller (such as the A+) continues the add/remove process.
-
Is there a way to automate my entry into my home. Afterall, that's the whole point of home automation (least human interaction). I'd like the Schlage lock to "sense" my presence at the door and unlock it for me. I know this lock does not have bluetooth functionality in it but there has to be a way for the A+ to know I'm home now, or at the door and (with my iPhone being in my pocket) unlock the door for me. I wish there was a door lock with z-wave and bluetooth functionality. Other locks like Lockitron, August, Goji seem to gimmicky and plastic build. Any pointer from someone in the process to map out there home automation schematic. Thanks.
-
It's coming, we're expecting the automation stuff to launch towards the end of September.
-
Any other suggestion to make this Lock working and update correct status.
-
Any updates on getting the lock to work? I just got my Almond+ and have paired and unpaired the lock 3-4 time but am unable to control the lock. When I try to lock or unlock it via the lcd it just says processing.
-
The lock works mostly with R065. Does your A+ recognize the lock after the join? I can lock and unlock from the lcd ui, web, and Android App. If it is not being recognized then before attempting another join do a remove before the next join.
-
It does recognize it but it shows it as unlocked regardless of the locks actual status. And when I try to lock or unlock it it says processing... But the lock doesn't move.
I've removed and rejoined multiple times.
-
We've reached out to Schlage to get some help from them, so let's see if we can't make all of this a lot smoother soon.
-
I purchased one of these locks and have install and successfully paired with the A+, however! there is not functionality.
When clicking on the wrench, it just states the following:
Sensor Settings
Name --- Front Door Lock
Located at --- Default
-
I forgot to add that I'm connecting using the iOS app running 7.1.2 on my iPhone 5.
-
The iOS app is a bit behind in terms of functionality at the moment, so please be patient, we're working on adding better support for all the various devices to the iOS app.
-
Using R066 the manual close/open indication is now resolved on the LCD UI as well as the Android App. :)
-
R066 has not resolved the issues for me. Still unable to lock or unlock and status is always unlocked.
-
After updating to R066 my lock has the same non functionality (lock/unlock status doesn't change and lock/unlock actions do nothing).
-
Can you remove and re-add the lock?
We have this working without any problems, so this is the only thing I can think of.
-
Sorry I forgot to mention that's the first thing I did. I actually unplugged the almond and plugged it in right next to the door to make sure it was within range. The Almond didn't have internet connectivity, but I don't think that should affect it's ability to control the lock via the LCD.
-
Indeed not. This is very strange indeed and I'm afraid I don't have any solution at the moment.
-
Paired the lock from about 30' away. Locking and unlocking works mostly (times out sometimes and need to refresh and try again).
-
Haven't seen this posted, but http://www.schlage.com/content/dam/sch-us/documents/pdf/installation-manuals/24352403.pdf is the documentation from Schlage on how to set the various z-wave parameters.
Also, from googling, it seems the Vera folks also had trouble getting the be469nx locks to work until Schlage updated their firmware (> v5.7).
-
That last part about the firmware is interesting, it's possible that this is causing some of the issues being seen here. It would be worth contacting Schlage about this, since I'm pretty sure we have a newer model as we only got it this year.
-
I cam a across the firmware issue that Vera users where encountering in my previous research. I purchased my lock in April of this year and it's FW is 5.8. I don't know if that is the most recent, but it's past the 5.7 that fixed the problem that Vera users had. FYI there you can fine the firmware version installed when you bought the lock by unscrewing inside part of the lock and looking the back panel. There's a sticker with the programing code and FW version.
-
Is there any plan to modify the current pin codes in the lock?
Also, maybe create a temporary pin that would expire in 24 hrs.
These are two features that were available on Nexia Home that I found very useful.
-
Is there any plan to modify the current pin codes in the lock?
Also, maybe create a temporary pin that would expire in 24 hrs.
These are two features that were available on Nexia Home that I found very useful.
I don't really understand the first question, but you can edit the pin codes now.
Temporary pins, not right now, but it'll be possible to delete pins for sure.
-
I'm saying that the current codes programmed into the lock do not show up and are not able to be changed. When I access the pin code drop down all of the codes are blank.
There is no way for me to edit them.
Also, I am only able to remotely lock and unlock from the Android app. These functions do not work from the touch screen or the "connect" site. The touch UI and Connect site also do not display the correct lock status.
-
Has anybody tried iOS app with latest firmware to lock/unlock these locks, may be it will work from iOS app.
As jcodyn mentioned it's working only from Android app and not on other UIs.
-
No change in the new version of the iOS app that was released today?
-
I'm saying that the current codes programmed into the lock do not show up and are not able to be changed. When I access the pin code drop down all of the codes are blank.
There is no way for me to edit them.
Also, I am only able to remotely lock and unlock from the Android app. These functions do not work from the touch screen or the "connect" site. The touch UI and Connect site also do not display the correct lock status.
Hmmm... that doesn't sound right.
Admittedly I don't have a Schlage lock in the office, all I have is a Danalock, but it works to lock and unlock from the cloud and local UI's just fine and it's displaying the correct status in all UI's.
It doesn't support pin codes, so I haven't really tried that, maybe someone else can verify it.
-
No change in the new version of the iOS app that was released today?
Here is what I see after today's iOS app updated.
-
I was seeing the same issue as arkal in the latest iOS app update with the RE66 firmware -- it just says "Could not update your sensor data" even though the Almond+ was able to control the lock and retrieve the status from both the router screen and the web UI.
As often recommended on this forum, I unpaired the lock from the Almond+ (which seemed to work fine) and tried reconnecting. The re-pairing failed for some reason and now my Schlage lock will not pair, it only flashes the red "X" when I enter the programming code and press "0" which is the pairing method.
I've already tried removing all sensors from my Almond+ and did a factory reset on the Schlage lock. No luck. Anyone got any ideas?
-------
UPDATE: I was able to remove my Schlage lock and reconnect it properly to my Almond+. However, now the Almond+ router screen and web UI are no longer able to get the correct status of the lock or control it. Also, on the iOS app, there is now both the original instance of the lock (which should have been removed when I unpaired the lock) and the new instance [see the attached screenshot]. The lock was working just fine before -- not quite sure what changed.
-
Today I did a reset on the Almond from the software tile and cleared out all the sensors (the reset didn't do this) and then added back the sensors I have (one wall plug, one door lock). The plug added fine, but the the door lock is the same as it's always been for me. I get a green check mark on the lock but the Almond doesn't update it's status and the lock/unlock buttons just hang at processing. The IOS app looks the same as the previous posters.
-
My bad about the iOS app, I thought they'd fixed the locks.
I'm surprised all of you are having issues now, since this lock was working fine before, or?
I can't do anything until Monday now, but this is obviously not good. :-\
-
Lars, I'm surprised you're surprised.
I have mentioned I am currently able to extend/retract the deadbolt remotely only via WebUI and LCD UI. Given the number of posts on this topic, it feels that I'm one of the few that were able to get this combination to work in this way. While the situation is functional, it's far from "working fine". I'm so tired of the process that I don't want to try changing -any- settings on the A+ fearing that I lose this ability again. To note, I have only gotten to this state twice on R065, and less than a handful on R066 (mainly because I've been using it longer).
--------------------------------
This is my typical experience with the pairing process for the A+/469NX combination:
1. A+ LCD UI: Add sensor mode
2. Walk to lock, enter programming code (which requires the deadbolt to be extended) and go into include/exclude mode. Hope for Green Checkmark.
3. Walk back to A+ to see if it's prompting for a name/location combo. At this point, the LCD UI shows the current status as "Unlocked" (maybe by default?). This does not match the current state of the lock (remember, it needs to be extended to be in include/exclude mode). Save name/location.
4. WebUI also shows "UNLOCKED". At this point, I either click Refresh or the Lock icon, hoping the WebUI updates to show "LOCKED" (like it actually is) instead of the dreaded "Could not communicate with sensor. Please Refresh and Retry" message.
A. If the status reflects the actual state, then I try to lock and unlock via WebUI a few times before I'm satisfied.
B. If I get the "could not communicate" message, then I put the A+ in Remove Sensor mode, walk to the lock and enter the programming code, walk back to the A+ to verify the sensor has been removed, then go back to step 1 above.
Keep in mind that when I say "walk", I'm talking about a flight of stairs. If the Add sensor process does not work, I can only handle the above steps two or three more times before I run out of patience with the stairs and give up for the day.
--------------
"Working fine" is if I can go through the Add Sensor process a single time and be able to control the Schlage remotely.
- The Jasco/GE 45609 was awesome. I installed the hardware, used the A+ to add sensor, and there it was! Working ever since.
- The Honeywell TH8320ZW1007/U took two tries (user error) and it paired. I can even remove and re-add it as a sensor without worry.
- The Schlage-A+ pairing is like a house of cards. I tried the above steps several times a day for several days before I could remotely lock/unlock. If I have to remove the sensor from the A+, who knows how long before I can get the two to talk to each other again. Once they talk though, they seem to continue to talk–This is where I currently am.
-
I'm really sorry, I wasn't aware it was this bad :-\
I've already emailed the software team and told them that this simply isn't good enough, as these things should be working flawlessly by now.
I was even assured that R066 should've fixed the lock related problems with the only exception being Kwiksets, but I guess that's really not the case.
Let me discuss this internally on Monday, as it's simply just not good enough that things are working like this.
-
I'm in the same boat as The19th and sykocus. I did have the Schlage BE469NX lock working at one point but only controllable via the web UI or router screen. Now I don't have that either -- I'm seeing the same result as sykocus where the status shows "Unlocked" (even though its actually locked" and when I try to lock it, it just gets stuck at "Processing".
Plus, I have stairs just like The19th so I hear you there buddy ;)
Thanks for looking into this Lars!
-
Everything seems to be working fine in terms of unlock\lock within the Android app.. However, I can't program any codes - each time I try I just get a timeout.
-
Have you tried programming codes via the LCD UI? Just want to try to figure out if it's an app issue or something else.
-
Have you tried programming codes via the LCD UI? Just want to try to figure out if it's an app issue or something else.
I have tried both and neither are working.
-
I have updated to R067 and the issues with the pin codes not saving is still present.
Every time I put in a pin and save and exit, then go back it is showing "unassigned".
Do you need a lock to test and make it work correctly?
If so, I have a spare that I might be willing to send to you to test with (as long as you send it back when you no longer need it).
-
Hi guys,
Newbie here. I don't have the BE469, but a BE369 instead. I paired the lock with A+ with no problem, but that was as far as it got...
On firmware R66, besides pin codes not being saved after assigning, every time I pressed Lock or Unlock, I heard the door mechanism clicking (1 click), but the dead bolt was not being turned. And on my A+ touchscreen, it seemed to be stuck on "processing..."
Any advice?
-
Hey Guys, any news on lock's working? I am still having same issues with the my BE469 locks. I have R66 firmware, tried setting locks from all the available UIs but no luck. Although UI does shows locks are paired in device/sensors list but does not work and also do not shows correct status.
-
We're going to release R069 in the new few days (which is technically a fixed version of R067/R068), but I don't think it'll have any lock specific fixes, at least none that I'm aware of. We're going to put a guy on figuring out what's going wrong with the locks though, as we understand that this is a serious issue and locks is one of those things that simply have to work.
-
We're going to release R069 in the new few days (which is technically a fixed version of R067/R068), but I don't think it'll have any lock specific fixes, at least none that I'm aware of. We're going to put a guy on figuring out what's going wrong with the locks though, as we understand that this is a serious issue and locks is one of those things that simply have to work.
Has R069cb addressed any of the lock issues? More specifically, the inability to add\remove\view codes via the app?
-
Has R069cb addressed any of the lock issues? More specifically, the inability to add\remove\view codes via the app?
No, nothing was fixed for the locks in R069.
-
Not sure to be honest, I didn't see anything in the internal release notes, but you can give it a try as I know some things are missing in the release notes. Sloppy, yes I know, and I've been pushing for better internal release notes.
-
Has R069cb addressed any of the lock issues? More specifically, the inability to add\remove\view codes via the app?
I just tried pairing and unparing the lock about 5 times and wasn't able to get it working. I did notice that the setting for editing the codes was missing from the LCD UI and the web interface.
-
Sometimes it takes a little bit of time before the the code option shows up in the LCD UI, I noticed that here at CES.
We got another Schlage lock and I'll test that when I get back to Taiwan.
-
Well now it's the next morning and there's still no code options.I was just addressing Inimical's question. Personally I just want the thing to lock and unlock the lock.
-
Hi,
I have the BE469NX and am running release R069. I was able to pair over 20ft away. However, the status is incorrect and I cannot lock/unlock (iOS, on the A+, from the web). I do see the code options, however changing them does not work (I even tested on the lock itself to see if it was just a visualization issue). I moved the A+ 5ft away, changed the lock batteries, and re-paired the lock, but nothing changed. The status is always "unlocked" even though it is really locked. So the sensor is detected but the information is incorrect and A+ is unable to change anything. Is there anything else I can do or try? I too am looking to lock/unlock.
Thanks!
-
Pairing the A+ and the 469 has always been hit or miss. I've noticed that if the A+ isn't able to remotely lock/unlock the device then I just unpair and re-pair the two, sometimes having to do it multiple times. Since If you get a "hit" then the A+ can control it, even after restarts/reboots/fw upgrades
-
Well, we bought a BE469NX and as soon as our VP of software is back from CES, he'll be handing it over to our software team to have them investigate.
It's odd that it's only this specific lock that's causing serious problems though.
-
Thanks for having the team look into this Lars. I'm in the same boat as dahwong; I'm on the R069cb firmware and I'm able to pair the A+ and BE469NX just fine. However, the status is always incorrectly detected as "unlocked", the A+ can't lock the Schlage and the A+ can't change the PIN codes. Hope to see more progress in the future!
-
Just want to throw in my +1 on this. Exact same issues, locks paired, incorrect status, and no functionality.
-
Just wanted to throw some more input in. Im running R069 and my schlage 469 has firmware 5.7
I was able to pair the lock but that was it.
When trying to control the lock via the app or router it just sits on processing.
Also read through all posts so i knows its a wip just wanted to add another affected lock to the list.
-
I just updated to R70 and the user codes will save and work, but you can't see them or delete them once they are added.
Come on guys, this is frustrating.
-
I just updated to R70 and the user codes will save and work, but you can't see them or delete them once they are added.
Come on guys, this is frustrating.
So is R70 now registering the proper state of the lock? Allowing you yo use it as trigger and lock/unlock it ? I installed R70 last night, but haven't had a chance to try pairing the locks to A+ yet. The one thing I miss with A+ is the ability to use lock as a trigger to turn on lights when coming home.
-
After R070 update I am still seeing the same issue... locks pairs, incorrect status, no functionality. Did R070 make things better for anybody?
-
I've paired, re-paired, tried all sorts of things. I cannot seem to get it to lock or unlock -- actually nothing works. 1 out of about 100 attempts actually worked, but when I tried to increase the PIN length I was never able to get it to work again -- despite numerous un-pairing and factory resets. I updated to R070 (and the beta prior to it) and it seems to be the same -- state is incorrect and am unable to lock/unlock, I haven't tried a factory reset on the lock yet. Some other people have gotten lock/unlock functionality to work, am I missing something?
-
Thanks for the updates, saves me from wasting my time playing with it :D
-
I've paired, re-paired, tried all sorts of things. I cannot seem to get it to lock or unlock -- actually nothing works. 1 out of about 100 attempts actually worked, but when I tried to increase the PIN length I was never able to get it to work again -- despite numerous un-pairing and factory resets. I updated to R070 (and the beta prior to it) and it seems to be the same -- state is incorrect and am unable to lock/unlock, I haven't tried a factory reset on the lock yet. Some other people have gotten lock/unlock functionality to work, am I missing something?
I had the exact same issue as you for quite some time. I installed fresh batteries into the lock and for whatever reason, that made it work. Just something else you could try.
-
We're aware of the not so great support for locks in the Android app and we'll get that fixed.
We've also improved the lock support in the most recent firmware that will be out shortly.
Lars - Any update on this? It's been some time, and the issues are still present. Primarily the inability to store, and view the codes.
-
Sorry, I'm away at MWC and I won't be back for another week and a half and won't really be able to follow up on this until then.
-
I had the exact same issue as you for quite some time. I installed fresh batteries into the lock and for whatever reason, that made it work. Just something else you could try.
Tried another round with fresh batteries without any luck. I even moved the unit right next to the lock. One thing I noticed is that even if unpair the lock, the lock says successful. But when I do a factory reset on the lock it still thinks it's paired.
-
Sorry, I'm away at MWC and I won't be back for another week and a half and won't really be able to follow up on this until then.
Any update?
-
They claim it's been fixed, new firmware next week.
-
I can verify that the Schlage 469 is indeed now working in R070as, showing proper state ( most of the time) and working in rules. ie: if door unlocks, then turn on hall lights, if door locks then wait 60 seconds turn off hall lights.
Even if showing the wrong state ( unlocked after it locks ) the lights still shut off after the time delay set in the rules and then it shows the proper lock state.
-
They claim it's been fixed, new firmware next week.
Still broken in 72.. Cannot create\modify\view codes >:(
-
Still broken in 72.. Cannot create\modify\view codes >:(
I couldn't check the lock codes, simply because Almond "requires" a minimum 5 digit , and we use all 4 digit codes. I was just happy to have it reading the proper state 95% of the time ( I figured out a 254 error is ( somebody did not close the door all the way ,so ) the bolt did not fully engage) . I really see no reason I would ever need to add/remove, change an access code remotely.
The lock codes is NOT strictly an Almond issue. We have been through 4 different hubs and NONE of them have ever been able to change the lock codes or register which one was used to open the door reliably (if at all). Maybe that function worked with the Nexia hub, but that is one that we never had, so I can't say if it did or not.
I will say that I do wish I could get into the lock memory and see all the active codes and a log of which code was used.
-
Using firmware 72 and lock connects but will not show proper locked/unlocked status on LCD and when I try to lock or unlock, it just hangs at "Prossesing". The iOS app shows the lock, but it says "could not update sensor"
-
I just purchased BE469WK, same model but wink compatible that has same issue as previous post. Lock gets recognized on R072 but will not show current status(shows unlock symbol) or allow for change in status in Android App and could not update status in IOS app. Web gui shows unlocked and will not lock/unlock. I can manage codes outside of Almond+, atleast want 100% accurate lock/unlock. It is a lock after all. Please prioritize getting these Locks working good as it is a security issue :) Thanks.
-
I just changed the batteries in the lock. Moved the almond within 5ft of the lock and after 3-4 rounds of unpairing and re-pairing I'm still having the same issue I had in August of last year: lock doesn't show correct lock/unlock status, pin codes don't take and when you try to lock/unlock remotely it hangs at "processing". >:(
-
I'm curious what firmware your locks have. What you have happening is exactly what I had prior to updating almond to fw 72. On 72/,the only issue with the locks is the inability to add/delete access codes. While I would love the ability to access the codes from my desktop, I really don't see a reason that I would ever need to add/delete a lock code from my phone/tablet. I would like a log of who unlocked the door, but again, I don't need it on my phone.
-
My lock came with few 5.8 what's yours?
-
While I would love the ability to access the codes from my desktop, I really don't see a reason that I would ever need to add/delete a lock code from my phone/tablet.
Actually, doing exactly that was one of the coolest things I've done yet with my A+. I have the Yale lock which they currently support a bit better. My nephew was coming in to town unexpectedly, and I was able to set a code for him before he showed up, so he didn't have to wait around for someone to get home, and I didn't have to worry about unlocking it for him when he arrived.
-
Wanted to add my experience here too. I am at R072 and have the same issues as others:
- Can lock/unlock from A+ touchscreen
- Status of lock always unlocked on A+
- Cannot lock/unlock from Android app
- Android app lock status never changes - always shows unlocked
- Have not tried editing codes from A+ or Android
I don't mind not being able to edit or view the codes from the Android app, or even from the A+. That would be great, I know there's an issue with reading the codes being supported on the Schlage side.
Really I want at least the basics work though - have the status of the lock correct and be able to lock/unlock from mobile app. That's the entire reason I bought the thing.
My Schlage firmware is "MAIN_6.8"
-
I just tried things again today and now the lock/unlock works fine!
From A+ web, A+ touchscreen, and Android app the status of the lock is correct, and I'm able to make it lock or unlock. I had the batteries out of the lock for over a week, but did not have to pair with the A+ again and everything just started working properly.
I think i remember an Android update to the app, but cant say for sure. The version of the Android app I'm currently running is 0.3.15b
-
+1 to confirm this is still not working, more than a year later and still hasn't been fixed, same issues as day one.
Schlage Firmware - 5.8
-
Right, so you two clearly have a massive difference in terms of firmware. Can those of you with older firmwares please contact Schlage to see what they have to say about it? As there's nothing we can do about it, as we don't have access to older firmwares from them. We can only get hold of what we can purchase in retail.
-
I just installed my BE469 and was able to get it paired if the A+ was within a few feet.
When I move my A+ to its normal location it can get the correct status but I cannot 'connect' to it if i try to lock/unlock.
If I move my A+ back to within a few feet of the BE469 I can lock/unlock from the A+.
What am I doing wrong?
-
I just installed my BE469 and was able to get it paired if the A+ was within a few feet.
When I move my A+ to its normal location it can get the correct status but I cannot 'connect' to it if i try to lock/unlock.
If I move my A+ back to within a few feet of the BE469 I can lock/unlock from the A+.
What am I doing wrong?
You're probably not doing anything wrong. The BE469 is not yet a supported device, and only has very limited functionality. According to Securifi, they are working on getting it added in the next firmware release.
-
l also have a 469NX that doesn't work. I currently hangs by "processing" anytime I try to lock/unlock the door. My book says I have firmwear version 6.8.
What really sucks is that it worked fine for the first month or so I had it and then a couple months ago it stopped working. Think I was after an update, just don't remember which. Hopefully, Securifi can dig back into this and get it working again.
-
Any updates on the PIN codes? I still cannot see prior assinged PIN codes to users and therefore cannot delete them