Danalock?

[gibby]

@flyveleder

[quote=“gibby, post:18, topic:178187”]Basically I am going to have it where the lock will relock after 2-5 minutes(going to have to test) and I want to make sure the state will be properly reported in Vera. That is why I thought about sending lock command every so often, but I hope that is not the case. I don’t have an open/close sensor on the door that Vera can talk to or I could just make it assume locked when door is closed. But we will see when it gets here.

Open/close state is properly reported in Vera (apart from when using manual interaction). If you are using Bluetooth to lock, it’s instantly reported in Vera.

/Martin[/quote]

Yeah I am worried about when the lock is operated manually…

[flyveleder]

As I said it does NOT change state in the lock, and therefore no matter how many times you poll it, it will not show correct state.

This will be fixed in the next firmware update though.

/Martin

[ntk]

@gibby

[quote=“sdholden, post:14, topic:178187”]I’ve just installed my Danalock, and so far, well, I’m not sure yet. It is mounted, and it functions. I had quite a bit of trouble getting it added to my vera lite, but that was finally accomplished, and after adjusting some settings, its working well. The bluetooth is another story. I have a Galaxy s4, running Android 4.3 w/BTLE. I run the setup on the app, add the lock, it finds it, then sits on “negotiating with danalock” forever. Never goes past it. I’ve seen another review in the play store saying the same thing, and it looks like there’s one here as well, where danalock replied that the android device was unsupported. I could kind of go with that, while it still would be a very very dificult thing to stomach, considering the S4 is so prevalent. However, I have a bone stock iphone5 also, that exhibits EXACTLY the same behavior, and the iphone5 is clearly listed as being supported, and I am running the latest IOS. I have reset the device by pressing the center button until i get 5 beeps, and I’ve even cycled power completely by removing the batteries. No change. I left the iphone on “negotiating with danalock”, literally sitting on the lock itself, and checked it this morning. Still on screen, “negotiating with danalock”. There’s no other bluetooth settings I’m aware of that I can adjust. So what do I do? I’ve done all the phone specific things, powered off, rebooted, cycled bluetooth on and off. Even performed a factory wipe of the iphone, no difference. Defective unit? How do I proceed? I’ve emailed danalock, but their email responses are a little slow, and I see perhaps a danalock employee in this thread so I thought I’d drop a line here.

I just noticed in their FAQ it states “Android: Please check the specs for your phone to be sure it supports Bluetooth Smart. Most new Android phones supports Bluetooth Smart/BLE.
Newest Android 4.4 KitKat must be supported by the Smartphone.”

I don’t remember seeing KK as a requirement before but it looks like it is now.[/quote]

i have the same problem and i use nexus v2 and android 4.4.2

also android support BLE from 4.3 and not 4.4

i send them an email and did not get a respond

also i have problem with sending alert when locking/unlocking the door, there is no option for “status of the lock change” there is only option for unlock or unlock in trigger in the vera GUI, so instead of receiving alert only when lock/unlock the door, i receive alert every time vera poll the node, they need to add option in the trigger to send alert when status change and no only when state is lock/unlock

[animalhouse]

Any experience/ideas on how to do a Factory Data Reset on the Danalock? I paired it to a different controller at first, and need to switch it over to my new VeraLite, but everything I had to re-pair required a factory data reset. I can’t figure out how to do it with the Danalock. I’m open to other ideas–it’s trying to communicate, but won’t pair. I checked and confirmed that I have the US version.

I emailed them, just haven’t heard back yet.

THANKS!!!

[flyveleder]

Please don’t hang me for this if it’s wrong - but I THINK you should hold the finger on the button untill you hear 5 beeps; Then let go.

Try to include on the new network.

/Martin

[sdholden]

@ntk

[quote=“gibby, post:19, topic:178187”][quote=“sdholden, post:14, topic:178187”]I’ve just installed my Danalock, and so far, well, I’m not sure yet. It is mounted, and it functions. I had quite a bit of trouble getting it added to my vera lite, but that was finally accomplished, and after adjusting some settings, its working well. The bluetooth is another story. I have a Galaxy s4, running Android 4.3 w/BTLE. I run the setup on the app, add the lock, it finds it, then sits on “negotiating with danalock” forever. Never goes past it. I’ve seen another review in the play store saying the same thing, and it looks like there’s one here as well, where danalock replied that the android device was unsupported. I could kind of go with that, while it still would be a very very dificult thing to stomach, considering the S4 is so prevalent. However, I have a bone stock iphone5 also, that exhibits EXACTLY the same behavior, and the iphone5 is clearly listed as being supported, and I am running the latest IOS. I have reset the device by pressing the center button until i get 5 beeps, and I’ve even cycled power completely by removing the batteries. No change. I left the iphone on “negotiating with danalock”, literally sitting on the lock itself, and checked it this morning. Still on screen, “negotiating with danalock”. There’s no other bluetooth settings I’m aware of that I can adjust. So what do I do? I’ve done all the phone specific things, powered off, rebooted, cycled bluetooth on and off. Even performed a factory wipe of the iphone, no difference. Defective unit? How do I proceed? I’ve emailed danalock, but their email responses are a little slow, and I see perhaps a danalock employee in this thread so I thought I’d drop a line here.

I just noticed in their FAQ it states “Android: Please check the specs for your phone to be sure it supports Bluetooth Smart. Most new Android phones supports Bluetooth Smart/BLE.
Newest Android 4.4 KitKat must be supported by the Smartphone.”

I don’t remember seeing KK as a requirement before but it looks like it is now.[/quote]

i have the same problem and i use nexus v2 and android 4.4.2

also android support BLE from 4.3 and not 4.4

i send them an email and did not get a respond

also i have problem with sending alert when locking/unlocking the door, there is no option for “status of the lock change” there is only option for unlock or unlock in trigger in the vera GUI, so instead of receiving alert only when lock/unlock the door, i receive alert every time vera poll the node, they need to add option in the trigger to send alert when status change and no only when state is lock/unlock[/quote]

I do have a custom rom on my S4, and I did notice the 4.4 requirement that seems to have been added late. The trouble with all of that is that I have a bone stock iphone 5, on ios 7, that gives me the EXACT same results. Never gets past “negotiating with lock”. So while I might give a bit of a pass on the S4 due to various factors, the iphone 5, which is explicitly supported, performs exactly the same, which causes me worry.

[sdholden]

Has anyone adjusted the variables via z-wave?
The published documentation:

“The variables indicates:
Variable 0 = Turning the DanaLock clockwise or counter clockwise.
Set the values to 1 if it should turn the opposite way.
Variable 1 = The value indicates the timeframe specified below
DanaLock, the time the lock should be turning when you press unlock
Variable 2 = The value indicates the timeframe specified below
DanaLock: The time the lock should be turning when you press lock
Variable 3 = how much torque/power will you need? Less torque = lower power
consumption
DanaLock: 1 = max torque
2 = average torque
3 = minimum toque, minimum power consumption.
Variable 4 = Indicates what kind of lock you have in your door.
The parameter shall only be set if you want the DanaLock to operate a magnetic door
lock or door strike, then you have to set this parameter to 3”

This is completely incorrect, at best. So far, there is no variable zero. Variable 1 is definitely the toggle between clockwise and counterclockwise operation. I’ve verified it. With the other settings, I’m getting very mixed results, even changing one variable at a time. At this point, I can’t reliably say what any of them do. For instance, according to the docs, variable 1 and 2 should be changed together, right? Well, variable 1 is the toggle. So lets say the variables are off by 1, making 2 and 3 the lock/unlock timing. I can change one of them, either one, and it has an effect, in either speed or duration, on both lock and unlock. So it appears that the ideas published in the manual are completely wrong. This is crazy.

[gibby]

Had a surprise today when I got home from the office. My lock showed up. Fedex guy actually came by twice. Took a little bit to install due to my dead bolt but once I got it assembled I was able to add it via the Android app but could not configure it. Added it to Vera with no issues. However the documentation is contradicting on the Variables in Vera. It took about 2 hours to configure via bluetooth but I will say that might be my ROM. On my Note 2 I am running CM KK, my wife’s is stock and can not even download app. Definitely looking forward to the keypad!

[gibby]

[quote=“sdholden, post:27, topic:178187”]Has anyone adjusted the variables via z-wave?
The published documentation:

“The variables indicates:
Variable 0 = Turning the DanaLock clockwise or counter clockwise.
Set the values to 1 if it should turn the opposite way.
Variable 1 = The value indicates the timeframe specified below
DanaLock, the time the lock should be turning when you press unlock
Variable 2 = The value indicates the timeframe specified below
DanaLock: The time the lock should be turning when you press lock
Variable 3 = how much torque/power will you need? Less torque = lower power
consumption
DanaLock: 1 = max torque
2 = average torque
3 = minimum toque, minimum power consumption.
Variable 4 = Indicates what kind of lock you have in your door.
The parameter shall only be set if you want the DanaLock to operate a magnetic door
lock or door strike, then you have to set this parameter to 3”

This is completely incorrect, at best. So far, there is no variable zero. Variable 1 is definitely the toggle between clockwise and counterclockwise operation. I’ve verified it. With the other settings, I’m getting very mixed results, even changing one variable at a time. At this point, I can’t reliably say what any of them do. For instance, according to the docs, variable 1 and 2 should be changed together, right? Well, variable 1 is the toggle. So lets say the variables are off by 1, making 2 and 3 the lock/unlock timing. I can change one of them, either one, and it has an effect, in either speed or duration, on both lock and unlock. So it appears that the ideas published in the manual are completely wrong. This is crazy.[/quote]

I concur, Var 3 seemed to disable the lock for me.

[sdholden]

Gibby, tell me about your bluetooth experience. You say it took two hours. Was that multiple attempts, or it took that long to configure itself?

[gibby]

@sdholden

Gibby, tell me about your bluetooth experience. You say it took two hours. Was that multiple attempts, or it took that long to configure itself?

Multiple attempts, make sure your wifi is off and toggle bluetooth before opening app. Should only take 10 seconds or so to communicate when working. Does take about a minute to reconnect after making a configuration change. I found going into Android apps and force stopping helped too.

[ntk]

anyone can see the status of the battery in vera ? i always get 0%

[gibby]

@ntk

anyone can see the status of the battery in vera ? i always get 0%

Yeah it takes a few times but it should report.

[sdholden]

Here’s what I’ve discovered pertaining to z-wave variables only. This knowledge is from real world trial and error.
Variable 0 - does not appear to exist. Vera reports it as undefined, and I have not been able to successfully change its value.
Variable 1 - definitively the direction toggle. Default is zero, which moves the unit clockwise on lock. Change to 1 for the reverse.
Variable 2 - default is 3, which turns the lock for approximately 3 seconds.
Setting this value to 1 turns the lock for approximately 6 seconds, but a much slower rate, effectively moving the
lock the same distance.
Setting this value to 4 turns the lock for approximately 2.5 seconds, but at a faster rate.
So it appears that variable 2 controls the speed of the lock. Values of 1-4, at least, are viable.
Variable 3 - This variable does appear to be the torque control as the manual states. For me, anything higher than 1, which the
manual states is max torque, renders the lock unable to move.
Variable 4 - Default is 9. This variable appears to be the duration the lock moves, in either direction. The higher the number, the longer it
turns and the farther it moves the lock. I cannot tell if the number equates to degrees of rotation or time of rotation.
My measurements aren’t accurate enough to say for sure, so if you need it to move further, increase the number, or
vice versa. For me, a value of 13 stopped the lock just before it stalled due to no room for further movement. 14 caused a
momentary bind just at the end. Seems to me thats what you should be going for.
Variable 5 - I’m going to assume this variable is the “magnetic lock variable” mentioned in the manual. I don’t need it, and I’ve found
what I needed in the other variables to set it properly, so I don’t care.

Hopefully this will help someone, and HEY DANALOCK, REWRITE THE INSTALLATION GUIDE!!! You have my permission to use this info if you like, just let me know where to send the invoice for R&D.

[sdholden]

P.S. danalock I’ll PM you the address to send the free set of batteries and a new tailpiece adapter. Since I have subjected my unit to extreme usage, figuring out the details of YOUR product, I believe its the least you can do.

[sdholden]

And I was finally, finally able to pair the lock with my iphone 5. Still no luck with the S4, but at least the lock does not appear to be faulty. Guess I’ll start looking for a 4.4 rom.

[idefix]

Received mine today and managed to get it to connect to vera after a few tries (had to factory reset once - would be nice if it is mentioned in the manual how to do that btw) and got it connected after that.

Android no joy so far.
S4 on latest 4.4 as well as a Nexus 7 on latest 4.4 both find the lock but are unable to “negotiatiate” the connection. Stuck forever on that screen.
Interesting is that the S4 shows multiple entries for the same lock when searching and the nexus 7 only one.
Wifi off, BT toggle countless times did not help either.
Looks like a lot more work needs to go into the Android support for this product

Next issue was mounting it. I have a Schlage deadbolt and the Danalock (square version) came with no adapter plate (unlike what is show on the webpage). As the large deadbolt screws will never fit the Danalock directly (plus holes are at a different position) and as the Danalock will not cover the Deadbolt hole in any case the plate is absolutely crucial.
Mailed the company to check whether it was accidentally left out of the box.
For now it sits on the shelf looking “pretty”

[robertmm]

Since I started the thread: I ended up sending mine back. They shipped the wrong version (EU instead of US), promised a replacement PCB which never arrived, emailed a UPS label, and then went silent. Some of the features important to me don’t work yet (keyless proximity entry with Bluetooth), and the installation isn’t as smooth as the web video would make you believe (I have a Schlage B60 deadbolt). Overall, it’s just not ready for prime time, in my opinion.

The initial response from their support was great, and they apologized profusely, but then they inexplicably went completely silent about 20 days or so ago, on three different email addresses. Now this could be because they’re a small company (hope everyone is doing alright) – I don’t want to have to fight for my refund.

The one thing I had zero trouble with was the Bluetooth link to my iPhone. It just worked.

[gibby]

So I did some testing for the z-wave variables. I went to device options and added variables up to 20 and set them to monitor only. Looks like 0-8 are valid.

[idefix]

The lock is now connect to my Vera and at least the zwave part works.
Pending the mounting issue (plate missing) I’m wondering what will happen if I mount this BT & Zwave lock at my door without ever accessing it via BT for the initial setup (no apples in the house)?

Question is: is the lock open till first time successful setup via BT? Means can anyone with an iPhone and the Dana app simply walk up to my door, pair via BT, run the initial, never used setup and open my door?

Waiting on a reply from the manufacturer on that (and the missing parts)…

Sent from my Nexus 10 using Tapatalk