Danalock V3 (New FW 0.20.0) Losing Connection

I sent it over in private

Thank you

Feel free to post it here for others to enjoy :slight_smile:

1 Like

yes please :smiley: can we have the file?

Iā€™m not comfortable sharing it just yet, as I was sent it directly from Danalock and donā€™t want to upset them. So far so good though. This is day two and both locks are still connected and accessible. Both locks are connected through routers on my network too.

2 Likes

I think Dresden elektronik has it too.

1 Like

115C-0004-11020000-ZigbeeXM_101-029_E1_DanalockV3_17.2.0_20221021141932.ota (199.9 KB)

Feel free for testing!

1 Like

so far so good :thinking:

How do you install this update?

with the deconz OTA plugin

20.06 arrived. Lets see how it works

3 Likes

Let us know if it runs stable :slight_smile:

I have been using the new firmware for a few days with no issues. Previously, the lock would lose connection after about ten minutes.

So far, so good

2 Likes

Unfortunately, the lock disconnected after a few weeks and never came back on. I waited 24 hours then tried resetting the lock with no success.

I then removed the lock from the Danalock app, reset the lock again and pulled the batteries in an attempt to start from scratch.

The lock was immediately found in home assistant and I could get it to turn again.

The only problem I have now is that the Danalock app canā€™t find the lock again, which means that I canā€™t lock or unlock the lock since it is not calibrated. It turns really nice though when controlled by home assistant. Too bad I canā€™t lock or unlock.

I feel I have aged many years over the two months Iā€™ve owned this lock. Iā€™m now a resentful old man prone to fits of rage. To keep the little I have left of my sanity I have decided to trash the lock and buy a proper lock instead.

This lock has been the worst product I have ever owned. The screws didnā€™t fit my door so I had to get new ones. Zigbee didnā€™t work. Support asked me questions about my setup but stopped responding when I sent them the info. I installed the app on a raspberry pi to control it over home assistant. It worked but was too slow and the batteries drained after three weeks.

1 Like

I believe you can calibrate it using the click commands.

Thank you! Worked like a charm :grinning:

1 Like

Hey Guys hope you can help me with my Danalock Problem.

I have a Danalock V3 with actual Firmware 20.06.
After Pairing it shows an HEX-Name and not a ā€œrealā€ Name. It is also connected trough a link with a Lamp. I can control the Device in the deCONZ GUI ( for example Lock and Unlock) but it did not appear in my Phoscon Application, and even not in my IOBroker Instance.
Some more information about my System:

Conbee II directly connected to my raspberry
Version: 2.19.03 / 19.9.2022
Firmware: 26780700

Thank you !

After Pairing it shows an HEX-Name and not a ā€œrealā€ Name

It mean the device is not reconized by the API, but can be included and work in deconz.

I can see a DDF for the v3 Version

  "manufacturername": "Danalock",
  "modelid": "V3-BTZBE",

Else if you can share your manufacture name and model id (you can see them in the cluster 0x0000 on deconz) ? f I m right the legacy code just look for model id starting by ā€œV3ā€

Hello, thank you for your fast repsonse.
Hop I have found the Information you need.

Yes, you donā€™t have the same model ^^

Try this DDF, itā€™s the same with your model added.

{
  "schema": "devcap1.schema.json",
  "manufacturername": ["Danalock", "Danalock"],
  "modelid": ["V3-BTZBE", "V3-BTZB"],
  "product": "Danalock V3",
  "sleeper": true,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_DOOR_LOCK",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/swversion",
          "refresh.interval": 84000,
          "read": {"cl": "0x0000", "at": "0x0006", "ep": 1, "fn": "zcl"},
          "parse": {"cl": "0x0000", "at": "0x0006", "ep": 1, "eval": "Item.val = Attr.val", "fn": "zcl"}
        },
        {
          "name": "config/pending",
          "public": false
        },
        {
          "name": "config/checkin",
          "awake": true
        },
        {
          "name": "state/alert",
          "default": "none"
        },
        {
          "name": "state/reachable"
        },
        {
          "name": "state/on",
          "read": {"cl": "0x0101", "at": "0x0000", "ep": 1, "fn": "zcl"},
          "parse": {"cl": "0x0101", "at": "0x0000", "ep": 1, "eval": "Item.val = (Attr.val === 1)", "fn": "zcl"},
          "refresh.interval": 600,
          "awake": true
        },
        {
          "name": "state/battery",
          "refresh.interval": 3700,
          "public": false,
          "awake": true
        }
      ]
    }
  ],
  "bindings": [
      {
          "bind": "unicast",
          "src.ep": 1,
          "cl": "0x0101",
          "report": [ {"at": "0x0000", "dt": "0x30", "min": 1, "max": 300 } ]
      },
      {
          "bind": "unicast",
          "src.ep": 1,
          "cl": "0x0020"
      },
      {
          "bind": "unicast",
          "src.ep": 1,
          "cl": "0x0001",
          "report": [ {"at": "0x0021", "dt": "0x20", "min": 600, "max": 3600, "change": "0x00" } ]
      }
  ]
}
1 Like