IDlock 150 - No binding for door state

[brujoand]

Describe the bug

According to this specification

deconz-rest-plugin/general.xml

Line 1541 in 2b71bd9

<attribute id="0x0003" name="Door state" type="enum8" access="r" required="m">

we should be reading the attribute 0x0003 from cluster 0x1010 which shows the door state. However when adding the IDlock there are only bindings for battery status and lockstate (locked unlocked).

Steps to reproduce the behavior

Add the lock using the deconz webapp
curl the api to see that only data for battery and lock state are presented
-->

Expected behavior

There should afaik be a binding of the door state aswell to say wether it is closed, open, jammed etc..

Screenshots

N/A

Environment

Phoscon: 2.14.00 / 18/12/2021
Deconz: v2.14.0-beta

• Host system: PC
• Running method: Kubernetes / Docker
• Firmware version: 26660700
• deCONZ version: v2.14.0-beta
• Device: ConBee II
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? If so: Which? No

deCONZ Logs

Nothing that looks interesting

Additional context

N/A

[Mimiix]

Whats the model ID / Manufacturer name of this device?

[brujoand]

It's this one: #3827
https://idlock.no/wp-content/uploads/2020/11/User-Manual-Zigbee-module_EN_v0.4.pdf

Product name: ID-Lock
Manufacturer: Id-lock
Model identifier: 150

[brujoand]

I guess Datek is technically the manufacturer id, as they produce the zigbee module for the lock.

[Mimiix]

Please read the Basic cluster for it on your device if you can.

[Mimiix]

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/How-to-read-Clusters

[brujoand]

Sure, that should be this one right?

[Mimiix]

No, i want the basic cluster :)

[brujoand]

Ah right, that was the door lock cluster. Gotcha.

[Mimiix]

Almost there :) Can you please click " read" ?

We need those Manu name and model ID to show up.

[brujoand]

haha... I was a facepalming as I posted it.. I need more coffee.

.

[Mimiix]

@Smanar Is the above device implemented by you already? If so, i have to forward @brujoand to the forums. Not sure if this is a newer version or not.

[Smanar]

The PR is here since May 2021 #4876
So If I m right ATM the API don't support the doorlock state.

You have it on your device JSON ?

[brujoand]

Nope, I can only find the value in the phoscon app,

{
  "config": {
    "battery": 90,
    "lock": false,
    "on": true,
    "reachable": true
  },
  "ep": 1,
  "etag": "e6de70ee105a141b51a1ad82dbc90d81",
  "lastannounced": "2022-02-01T13:03:33Z",
  "lastseen": "2022-02-01T14:07Z",
  "manufacturername": "Datek",
  "modelid": "ID Lock 150",
  "name": "Hoveddøra",
  "state": {
    "lastupdated": "2022-02-01T13:07:09.197",
    "lockstate": "unlocked"
  },
  "swversion": "0.7",
  "type": "ZHADoorLock",
  "uniqueid": "68:0a:e2:ff:fe:6b:b8:26-01-0101"
}

[brujoand]

@Smanar seems like your PR would solve my problem perfectly. Is there any reason why it hasn't been merged?

[Mimiix]

@brujoand #5733

[brujoand]

Oh, just read the ddf proposal. Looks like a good approach 👍