[FR] Add support for Lidl Smart Wireless Door Bell

Question

[FR] Add support for Lidl Smart Wireless Door Bell

Closed this issue 3 years ago · 34 comments

Should be nice if the Lidl Smart Wireless Door Bell supported with triggers within Home Assistent.
See also my issue at deconz-rest-plugin git repo; dresden-elektronik/deconz-rest-plugin#4450

The Lidl Smart Wireless Door Bell only contains one button.

Device registry;

2021-06-16 11:07:50 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"id":"14","lastannounced":"2021-05-18T10:56:46Z","lastseen":"2021-06-16T09:07Z","manufacturername":"EcoDim BV","modelid":"Dimmer-Switch-ZB3.0","name":"Slaapkamer T&I spotjes","swversion":"3.09","type":"Dimmable light","uniqueid":"08:6b:d7:ff:fe:5d:75:98-01"},"e":"changed","id":"14","r":"lights","t":"event","uniqueid":"08:6b:d7:ff:fe:5d:75:98-01"}

2021-06-16 11:07:52 DEBUG (MainThread) [pydeconz.websocket] {"e":"added","id":"53","r":"sensors","sensor":{"config":
{"battery":null,"enrolled":0,"on":true,"pending":[],"reachable":true},"ep":1,"etag":"c0d25a498684b0634797d3d79aa45ef1","id":"53","lastseen":"2021-06-16T09:07Z","manufacturername":"LIDL Silvercrest","mode":1,"modelid":"HG06668","name":"Switch 53","state":

{"buttonevent":null,"lastupdated":"none","lowbattery":false,"tampered":false},"type":"ZHASwitch","uniqueid":"84:2e:14:ff:fe:f9:4a:ca-01-0500"},"t":"event","uniqueid":"84:2e:14:ff:fe:f9:4a:ca-01-0500"}
2021-06-16 11:07:52 DEBUG (MainThread) [pydeconz.deconzdevice] Switch 53 created as
{'config': {'battery': None,
            'enrolled': 0,
            'on': True,
            'pending': [],
            'reachable': True},
 'ep': 1,
 'etag': 'c0d25a498684b0634797d3d79aa45ef1',
 'id': '53',
 'lastseen': '2021-06-16T09:07Z',
 'manufacturername': 'LIDL Silvercrest',
 'mode': 1,
 'modelid': 'HG06668',
 'name': 'Switch 53',
 'state': {'buttonevent': None,
           'lastupdated': 'none',
           'lowbattery': False,
           'tampered': False},
 'type': 'ZHASwitch',
 'uniqueid': '84:2e:14:ff:fe:f9:4a:ca-01-0500'}

On button press

2021-06-16 11:08:01 DEBUG (MainThread) [pydeconz.websocket] {"e":"changed","id":"53","r":"sensors","state":
{"buttonevent":1002,"lastupdated":"2021-06-16T09:08:01.838","lowbattery":false,"tampered":false},"t":"event","uniqueid":"84:2e:14:ff:fe:f9:4a:ca-01-0500"}

Kane610 commented 2 years ago

Exactly

Answer 1 · 2021-06-16T10:10:19.000Z

Don't want to get in your way of development. Not entirely clear to me where I can easily create the merge for this. Directly in the Home Assistant git project?

But here is the code;

LIDL_SILVERCREST_DOORBELL_MODEL = "HG06668"
LIDL_SILVERCREST_DOORBELL = {
    (CONF_SHORT_PRESS, ""): {CONF_EVENT: 1002},
}

..
..
REMOTES = {
..
LIDL_SILVERCREST_DOORBELL_MODEL: LIDL_SILVERCREST_DOORBELL,
...

}

Have already tested it;

Answer 2 · 2021-06-16T18:00:08.000Z

Hey! Awesome!! Try it out! Put up a PR and I'll help you get it through!

Answer 3 · 2021-06-17T16:02:16.000Z

Congratulations!

Answer 4 · 2022-03-08T11:24:01.000Z

There is still no button available. Just a tampered sensor which does not respond to button press. Is that intended?

Answer 5 · 2022-03-08T12:07:23.000Z

There is still no button available. Just a tampered sensor which does not respond to button press. Is that intended?

The button is only an event just like all other remotes. The above mentioned PR adds device triggers to automations, you will get it listed in automations but there won't be an entity for the button itself

Answer 6 · 2022-03-08T12:12:06.000Z

There is still no button available. Just a tampered sensor which does not respond to button press. Is that intended?

The button is only an event just like all other remotes. The above mentioned PR adds device triggers to automations, you will get it listed in automations but there won't be an entity for the button itself

thanks for the fast answer. Yes but I have no button trigger to select for automations and I get the same event (0) on press as mentioned above

Answer 7 · 2022-03-08T12:24:51.000Z

@boehser-enkel What automation tool are you using? Or only Deconz?

Answer 8 · 2022-03-08T12:26:29.000Z

Ow wait, home assistent ofcourse. Then you should be able to create an trigger like this;

Answer 9 · 2022-03-08T12:26:54.000Z

@boehser-enkel What automation tool are you using? Or only Deconz?

Home Assistant. But also in Phoscon I am not able to choose it as a button

Answer 10 · 2022-03-08T12:28:51.000Z

there is only tampered and battery

Answer 11 · 2022-03-08T12:30:48.000Z

Hm. Which version of HA & Deconz are you using?

Answer 12 · 2022-03-08T12:32:05.000Z

Hm. Which version of HA & Deconz are you using?

2022.3.2 & 2.14.01

Answer 13 · 2022-03-08T12:44:19.000Z

Strange, it's still in the code. Do you see the events in the logs of deconz and home assistent?

Answer 14 · 2022-03-08T13:45:35.000Z

Strange, it's still in the code. Do you see the events in the logs of deconz and home assistent?

I see the events in HA. Can look at deconz in the evening if you need them.

Answer 15 · 2022-03-13T10:00:56.000Z

Has the model id changed? Right now it's expected to be "HG06668"

Answer 16 · 2022-03-13T10:04:03.000Z

Has the model id changed? Right now it's expected to be "HG06668"

It’s the same

Answer 17 · 2022-04-30T07:03:31.000Z

Has the model id changed? Right now it's expected to be "HG06668"

It’s the same

Can you share a diagnostics file from the integration?

Answer 18 · 2022-05-02T10:30:43.000Z

Has the model id changed? Right now it's expected to be "HG06668"

It’s the same

Can you share a diagnostics file from the integration?

U mean the Home Assistant Deconz Integration diagnostic file?

Answer 19 · 2022-05-02T11:06:38.000Z

config_entry-deconz-26968d9235b79c6841870ed86d4a94fe.json.txt
Here you go

Answer 20 · 2022-05-02T11:20:53.000Z

Strange, in your diagnostics the device is recognized as TS0211, instead of HG06668
For example my output;

      "54": {
        "config": {
          "battery": null,
          "enrolled": 1,
          "on": true,
          "pending": [],
          "reachable": true
        },
        "ep": 1,
        "etag": "80c742102fab2bb3da6a6b08cf363e32",
        "lastannounced": "2022-03-24T12:44:47Z",
        "lastseen": "2022-04-04T13:21Z",
        "manufacturername": "LIDL Silvercrest",
        "mode": 1,
        "modelid": "HG06668",
        "name": "Switch 54",
        "state": {
          "buttonevent": 1002,
          "lastupdated": "2022-04-28T13:10:13.704",
          "lowbattery": false,
          "tampered": false
        },
        "type": "ZHASwitch",
        "uniqueid": "84:2e:14:ff:fe:f6:d5:ea-01-0500",
        "attr": {
          "id": "54",
          "lastannounced": "2022-03-24T12:44:47Z",
          "lastseen": "2022-05-02T10:50Z",
          "manufacturername": "LIDL Silvercrest",
          "modelid": "HG06668",
          "name": "Switch 54",
          "swversion": null,
          "type": "ZHASwitch",
          "uniqueid": "84:2e:14:ff:fe:f6:d5:ea-01-0500"
        },
        "e": "changed",
        "id": "54",
        "r": "sensors",
        "t": "event"
      },

Answer 21 · 2022-05-02T11:22:06.000Z

This is strange. Even on the device itself its printed HG06668.
Any way to work around this?

Answer 22 · 2022-05-02T11:24:48.000Z

Can you try to add here https://github.com/home-assistant/core/blob/dev/homeassistant/components/deconz/device_trigger.py#L480

LIDL_SILVERCREST_DOORBELL_MODEL2 = "TS0211"

And then here; https://github.com/home-assistant/core/blob/dev/homeassistant/components/deconz/device_trigger.py#L609

    LIDL_SILVERCREST_DOORBELL_MODEL2: LIDL_SILVERCREST_DOORBELL,

or just change HG06668 for TS0211.

Answer 23 · 2022-05-02T11:35:36.000Z

I can't find these files in my (supervised container) installation.
Won't they be overwritten on the next update anyways?

Answer 24 · 2022-05-02T11:56:15.000Z

I haven't experience with the supervisor setup, but can you access the Home Assistent container?
docker exec -it $(docker ps -f name=homeassistant -q) bash

Then I guess Home Assistent is in /usr/src/homeassistant/homeassistant or /usr/share/hassio/homeassistant.
But try otherwise a find; find / -name deconz

Answer 25 · 2022-05-02T12:33:55.000Z

Changed it and did a restart of HA. Now i can select "button pressed" but it won't get recognized when i press the doorbell

Answer 26 · 2022-05-02T12:45:40.000Z

But do you see this event on Deconz self? Wondering of there is not more different then only the device identifier.

docker logs -f --tail 100  $(docker ps -f name=deconz -q)

Answer 27 · 2022-05-02T13:20:09.000Z

What do i have to look for?
I found this:
15:16:11:297 DEV no DDF for 0x842E14FFFEF6E87B, modelId: TS0211 15:16:11:297 DEV create on-the-fly DDF for 0x842E14FFFEF6E87B

15:16:42:740 [INFO] - No button map for: TS0211, unicast to: 0x0000, endpoint: 0x01, cluster: IAS_ZONE

Answer 28 · 2022-05-02T14:07:32.000Z

Hmm; No button map for: TS0211. So I guess you don't see a log message in deconz when you pushed the button, right?
Do you see something like this; dresden-elektronik/deconz-rest-plugin#4450 (comment)

Answer 29 · 2022-05-03T07:35:15.000Z

No button map for: TS0211

That would mean you can either create a DDF for the file or request device support on the forums

Answer 30 · 2022-12-14T11:17:25.000Z

Updated my deconz container, where after button mapping was broken. Here is the request in deconz;

12:09:21:872 [INFO] - No button handler for: HG06668, unicast to: 0x0000, endpoint: 0x01, cluster: IAS_ZONE (0x0500), command: STATUS_CHANGE (0x00), payload: 0D0000640000, zclSeq: 74
12:09:21:873 Websocket 172.21.0.5:47964 send message: {"e":"changed","id":"54","r":"sensors","state":{"buttonevent":1002,"lastupdated":"2022-12-14T11:09:21.871"},"t":"event","uniqueid":"84:2e:14:ff:fe:f6:d5:ea-01-0500"} (ret = 165)
12:09:21:874 Websocket 172.21.0.5:44130 send message: {"e":"changed","id":"54","r":"sensors","state":{"buttonevent":1002,"lastupdated":"2022-12-14T11:09:21.871"},"t":"event","uniqueid":"84:2e:14:ff:fe:f6:d5:ea-01-0500"} (ret = 165)
12:09:21:875 Websocket 172.23.0.18:58272 send message: {"e":"changed","id":"54","r":"sensors","state":{"buttonevent":1002,"lastupdated":"2022-12-14T11:09:21.871"},"t":"event","uniqueid":"84:2e:14:ff:fe:f6:d5:ea-01-0500"} (ret = 165)
12:09:21:877 Websocket 172.23.0.18:58282 send message: {"e":"changed","id":"54","r":"sensors","state":{"buttonevent":1002,"lastupdated":"2022-12-14T11:09:21.871"},"t":"event","uniqueid":"84:2e:14:ff:fe:f6:d5:ea-01-0500"} (ret = 165)
12:09:21:878 Websocket 172.21.0.5:52864 send message: {"e":"changed","id":"54","r":"sensors","state":{"buttonevent":1002,"lastupdated":"2022-12-14T11:09:21.871"},"t":"event","uniqueid":"84:2e:14:ff:fe:f6:d5:ea-01-0500"} (ret = 165)
12:09:21:879 APS-DATA.request id: 161, addrmode: 0x02, addr: 0xa888, profile: 0x0104, cluster: 0x0500, ep: 0x01 -> 0x01 queue: 2 len: 5 tx.options 0x04

Device visible within HA;

Previous trigger setup;

New trigger;

Can you check of this works too for you, @boehser-enkel ?

Answer 31 · 2024-01-09T13:09:35.000Z

Sorry for posting in this old old thread, but have you been able to get it working?

Back in the days I was able to trigger Alexa with this, but the automation is gone and I don't know how to get it fixed.

I get this in the logs

"71": {
        "config": {
          "battery": 0,
          "on": true,
          "pending": [],
          "reachable": true
        },
        "ep": 1,
        "etag": "374b0fc960eef220d96229f3f9611008",
        "lastannounced": null,
        "lastseen": "2024-01-07T10:48Z",
        "manufacturername": "LIDL Silvercrest",
        "mode": 1,
        "modelid": "TS0211",
        "name": "Button A01",
        "state": {
          "buttonevent": 1002,
          "lastupdated": "2024-01-09T13:01:10.136"
        },
        "type": "ZHASwitch",
        "uniqueid": "84:2e:14:ff:fe:f9:46:f2-01-0500"
      },

And I also get events being fired, but still, I can neither select something relevant in automations nor do I see the battery state (which I replaced an hour ago).

I'm using HA 2024.1.2 and deconz 2.24.2.

Would appreciate any feedback as these device lay around for almost two years now and I want to start using them ;-)

Answer 32 · 2024-01-13T08:56:51.000Z

It looks like the TS0211 model id has been added to deconz so we should be able to support this now that it has button mappings

Answer 33 · 2024-01-13T10:01:44.000Z

PR is up, should be supported with next major HA release.