Securifi Community Forum
Securifi Products => Almond+ => Topic started by: abooker on February 20, 2015, 11:03:30 am
-
Hi,
I'm considering buying an Almond+ for a vacation home that we rent. A critical feature to me is the ability to add/delete user codes remotely. I have a Wink Hub now, and have found support to be good, but this feature is missing from their *featured* Schlage support. >:(
Have any of you used the user code feature in R70? Is it worth making the move to the Almond+?
Aaron
-
I have the schlage and have not been successful in adding additional lock codes from the UI. The option is there, but ultimately changing or adding a code via the web has not worked for me. I did NOT try in R70, but will when I get home.
-
Okay so I haven't tried it in the latest firmware ( 70 ) but let me add to the last reply.
For me, the codes to work. Have worked since day one but the issue is that it will not save your assignment. Let me clarify-I can go in to the UI and tell it :
User1 = 1111
User 2= 2222
User 3= 3333
It will not let me change the user name.....and after I hit save, I can go to my lock and the codes work. BUt if you go back into the UI, it appears that you have not assigned user1 any code....so it doesn't do a good job in telling you with users already have assigned codes and which ones don't. So you have to remember what users you assigned.
Makes sense?
Im going to redo my codes tonight with the new firmware and hope the support has imporved
-
For whatever it's worth, I have a Schlage BE469NX and I still cannot get it to work with any firmware, including the latest R70. It will pair but there is zero functionality.
When you pair, the deadbolt is in the locked position, on the Almond it says it is unlocked. Attempting to lock/unlock results in "processing" until you intervene the process. As a result, the router has been almost useless to me since this one of the main reasons I purchased.
-
For whatever it's worth, I have a Schlage BE469NX and I still cannot get it to work with any firmware, including the latest R70. It will pair but there is zero functionality.
When you pair, the deadbolt is in the locked position, on the Almond it says it is unlocked. Attempting to lock/unlock results in "processing" until you intervene the process. As a result, the router has been almost useless to me since this one of the main reasons I purchased.
I have the same lock. Works fine for me through the UI and sometimes gives me the correct status of the lock. Paired no problem from a pretty good distance away actually but anything past opening and closing the lock is not working.
-
Aside from the obvious shortfalls of the Almond+ firmware, another issue is the disparity between the firmwares on the lock. If you have a newer firmware, then you should be able to pair and control the lock (Still can't really program codes).
Unfortunately according to Schlage the only way to get a new firmware is to get a new lock, and even then you have no idea how long the one you're purchasing has been sitting on the shelf. I spoke with Schlage support and apparently there is no way to upgrade the firmware, or even know what version you're at... Which is pretty infuriating considering the cost of the lock. But as far as I know there is no viable alternative, so we're stuck with it.
-
Aside from the obvious shortfalls of the Almond+ firmware, another issue is the disparity between the firmwares on the lock. If you have a newer firmware, then you should be able to pair and control the lock (Still can't really program codes).
Unfortunately according to Schlage the only way to get a new firmware is to get a new lock, and even then you have no idea how long the one you're purchasing has been sitting on the shelf. I spoke with Schlage support and apparently there is no way to upgrade the firmware, or even know what version you're at... Which is pretty infuriating considering the cost of the lock. But as far as I know there is no viable alternative, so we're stuck with it.
I also have the FE469NX, which was purchased new in April 2014. The Schlage has what I understand to be the latest firmware, which is 5.8. My Almond+ is on R070. The lock will pair/unpair just fine and from a decent distance. However, I'm seeing the same behavior as happyj. When I try to trigger a remote lock/unlock from the Almond+, it does nothing, and the LCD constantly reports "unlocked" status. I could probably contribute more if there some documentation provided re: the best ways to look under the hood. I am not unfamiliar with Linux.
-
Our 469s have always paired with no issues, but as others have stated, that is all they do. Can not read lock state. So they are useless as a trigger and can not be controlled through UI or app.
-
Using the Kwikset Lock and Deadbolt. It works well. I believe the apps should have the ability to change codes, at least with Kwikset, soon.
-
I also have the FE469NX, which was purchased new in April 2014. The Schlage has what I understand to be the latest firmware, which is 5.8. My Almond+ is on R070. The lock will pair/unpair just fine and from a decent distance. However, I'm seeing the same behavior as happyj. When I try to trigger a remote lock/unlock from the Almond+, it does nothing, and the LCD constantly reports "unlocked" status. I could probably contribute more if there some documentation provided re: the best ways to look under the hood. I am not unfamiliar with Linux.
How were you able to tell which firmware the lock is on?
-
How were you able to tell which firmware the lock is on?
Unscrew the inside of the lock from the mounting plate and remove it from the door. You will find a sticker with the firmware listed on the face of the lock that is normally against the door.
-
Unscrew the inside of the lock from the mounting plate and remove it from the door. You will find a sticker with the firmware listed on the face of the lock that is normally against the door.
It is also on a sticker affixed to the printed insert included with each lock. See attached snippet from user guide.
-
I never thought to look in the book. :-\ Now that you mention it though it does make sense that both stickers would contain all the same info.
On a related note, there is no way to update the lock firmware yourself. If you have anything lower that 5.7 your only option is to contact Schlage and they will have you send the lock to them for FW update.
-
I have a newer Schage lock and I'm able to add new codes to my lock via the router.
However, the UI doesn't seem to show the codes. For example Code 1 is used by the lock already. You can plug in a new code in slot 1 and it basically just adds another code rather than overwriting the current code in slot one. Once you go to slot two to add another code, and switch back to code 1, it shows unspecified again.
The status of the lock isn't aways correct, but seems to fix itself. For example it open shows unlocked when it is actually locked. When you hit the lock button, it updates correctly to locked. Then you can unlock it if you need to.
-
I have a newer Schage lock and I'm able to add new codes to my lock via the router.
Which model of lock and which firmware version? I don't think good comparisons can be made without those details.
-
Which model of lock and which firmware version? I don't think good comparisons can be made without those details.
So far no one has reported being able to view the stored codes, regardless of firmware.
-
it may be the lock, I recently bought the one from monoprice.com and I can see the codes I've added.
-
it may be the lock, I recently bought the one from monoprice.com and I can see the codes I've added.
I have a Yale YRD240, and codes I add or change via the web UI show up and behave consistently, so I'm sure the experience varies from lock to lock. The only major issue I have is that I can't delete codes. With R70as the lock state in the web UI seems to keep sync with the actual lock pretty well.
-
I have the Schlage also. It used to work fine with the almond, until a couple weeks ago. Now it just sits there "processing".
-
I have the Schlage also. It used to work fine with the almond, until a couple weeks ago. Now it just sits there "processing".
Which Schlage, and which firmware?
-
I have the Schlage BE469NX deadbolt. It pairs up and on the Almond+ I get the ability to lock and unlock the deadbolt. The codes don't work because it insists the code has to be 6 digits long and doesn't show any existing codes, but the options shows up to enter codes. From the app the lock shows up but does nothing. I get an unlocked icon which seems like it should lock the door when pressed, but it does nothing.
So my home automation controller allows me to lock and unlock my door with only 5 presses to a touch screen on front of it. That is it. Pretty pointless.
-
i just installed a BE469 lock.
Was able to get it paired and use the app to lock/unlock.
Do need to refresh to make sure one gets the current status.
I can add/remove user codes even though the app says it didnt connect. When I go and try the codes they do work.
My main issue is I am using the A+ as a router and when the A+ is on the other side of the house I couldnt get the app or UI to work. Once I moved the A+ very close to the BE469 I can control the lock/unlock.
My sticker stated it was v6.8
-
Okay so I haven't tried it in the latest firmware ( 70 ) but let me add to the last reply.
For me, the codes to work. Have worked since day one but the issue is that it will not save your assignment. Let me clarify-I can go in to the UI and tell it :
User1 = 1111
User 2= 2222
User 3= 3333
It will not let me change the user name.....and after I hit save, I can go to my lock and the codes work. BUt if you go back into the UI, it appears that you have not assigned user1 any code....so it doesn't do a good job in telling you with users already have assigned codes and which ones don't. So you have to remember what users you assigned.
Makes sense?
Im going to redo my codes tonight with the new firmware and hope the support has imporved
Firmware 72 has not corrected the problem above. I understand that rules and automation are low in the priority list but it seems like being able to save and view the different codes you have assigned for the lock is a fundamental requirement. In addition, if I assign a temp code and then want to delete it, I don't think I can because I cant see the codes I previously assigned and when I go to the user, its blank already so how does one delete a user with no code? Is there any chance that this could be fixed for firmware 73?
-
Bump
-
BUMP BUMP
-
After couple tries or so I was able to add one lock! But can't do anything with it since it gets stuck on processing and doesn't go anywhere, lock works fine with a winkhub so I doubt the problem is with the locks firmware, looks more like some compatibility issue with Almond