[quote=“flyveleder, post:25, topic:178187”]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[/quote]
5 beeps after each other - or 5 small beeps in a row?
this ?#&%?&? Lock does not want to include… or exclude
Edit: the BT Device has to be removed from the web gui to be able to factory reset.
But it does not look like factory reset sets z-wave settings back to default, at least i am not able to add it to my vera again
Edit again: removing battery for a while right after factory reset did the trick… useless manual… i think i for some reason manged to disable the entire Lock by setting the variables stated in their manual by some way. the procedure is absolutely identical as last time, just except variables
2 beeps after each other to include and exclude. 5 beeps after each other to factory reset (will play a melody once you let go of the button and reset is successful)
I also had the same issue you describe. Removing the battery and plugging it back in solved the issue.
[quote=“idefix, post:42, topic:178187”]2 beeps after each other to include and exclude. 5 beeps after each other to factory reset (will play a melody once you let go of the button and reset is successful)
I also had the same issue you describe. Removing the battery and plugging it back in solved the issue.
Sent from my Nexus 10 using Tapatalk[/quote]
this time i added to z-wave first since that was where i had problem last time, this worked… But not able to add the Device as a New Lock With BT - and the kids iphone4s does not detect the other Lock at all… i`ve sendt a mail to support, probably just have to wait… >:(
Still no answer from danalock, even not after numerous Messages and posts on facebook either -but at the end i manged to fix this myself.
using a custom BLE scanner I where able to detect the New Lock. the ID for the Lock is the last digits of the MAC adress, so if you have multiple Locks you can use their webpage to exclude known Locks.
After using the scanner to find my “New” Lock, i knew it where avaliable just not for my Phones (tried several suported iphones) and went Ahead and started my BLE diagnostic tool. imidiately it found my unpaired Lock, and tried to read setting. As soon as i started the read, i could see that the lights on the Locks was turned on. Grabbed my phone again and tried to add a New Lock - and it worked…
It looks like it had been into some sort of sleep (the BT part) and had Incredible low rssi rate. did not look like the a factory actually did anything…The Lock came up as "New Lock at the end, but all custom settings like CCW, turn degrees was as i set it the first time.
But i am “happy” for now - but used almost 12 hours to get two Locks up running. Alot of the time could be avoided With proper manuals…
Interesting. Do you by any chance have a android to test with? Would love to know where in the inclusion process the problem occurs as I can see the light in the lock come on and off after some time when I connect the S4 or Nexus 7 but never get the final inclusion confirmation.
Any idea how we are to receive and install this new firmware? The lock doesn’t appear to have a USB connector on it.[/quote]
I was thinking the same thing, maybe through a special feature in the bluetooth app. Hopefully this weekend I will have time to play with the Z-Wave variables 0-8 and map them to the Bluetooth App settings.
The ability to not update the status when the lock has been operated manually is putting a hinder on using this to its current full potential. If it takes much longer, I might have to come up with a magnetic detection for the dead bolt.
I haven’t been able to include it even. It included once but Vera gave an error about security settings and prompted me to exclude-re-include it. I could not exclude it and deleted the device, and did a factory reset on the lock. Since then it fails to even begin the inclusion process.
does anyone else have problem With the range on this Lock, and random dropouts from z-wave?
today i experienced the Lock on the back door refused to unlock after several retries. the Lock started to blink, and had a LED blink every 2 Seconds… - battery remove and insert fixed it.
And my other Lock, is not able to comunicate, the closest node is around 10m away, that should make my Lock on two hops from the gateway, but i am just not able to comunicate With it on z-wave
If i dismount and bring it closer it Closer to Gateway, everything work again.
I had some issues with that while testing mine near the intended location and changing parameters a few times. Just disappeared. I went the long route: factory reset, included it again and did all the settings from scratch
- The BT + Zwave model needs to be configured via BT at least once. Otherwise it will remain open for any BT user with the Dana app approaching your front door. :o Important for Android users who can not get access to the lock yet
Firmware upgrade: The Z-Wave version 300 can not be field upgraded, since it is a secure device, and all memory are used. We are working on a future option, going to the 500 series.
A new Android app is planned for this week which (hopefully) will allow non iPhone users to configure the lock
I spwnloaded the new update from Google play, I have nexus 7 v2 with android 4.4.2, before the update the bluetooth did not work, but after the update the lock sync with my tablet in 2 sec finally
I hope they will find a way to update the firmware, don’t understand why they did not think about it before
Yes, works much better but still looses connection when i configure it. Waiting till the light in the lock goes off before issuing the next command solves the issue.