Lidl (Silvercrest) Smart Home (Zigbee version) integration

anon71759204 · December 10, 2021, 8:47pm

The ZigBee Binding thinks that the device is initialised (zigbee_device_initialised):

Does it mean that phase 1 or phase 2 is finished (from the view of the binding …)? It doesn’t work.

zigbee_powersource is wrong. Just for comparison the parameters of my eWeLink MS01:

Does it make a difference to the binding?

How can I check that the device is properly configured?

BC33ACFFFE615CDF.xml (46.3 KB)

anon71759204 · December 10, 2021, 9:13pm

Someone sniffed the remote:

github.com/dresden-elektronik/deconz-rest-plugin

(Lidl) Livarno Lux Remote Control

opened 09:07PM - 07 Dec 20 UTC

closed 02:56PM - 23 Dec 20 UTC

derrohrbach

Device Request Awaiting Merge

Note: This is a device request for the remote control included with the new lidl lamps ## Device - Product name: Livarno Lux Remote Control - Manufacturer: _TYZB01_bngwdjsr - Model identifier: TS1001 - Device type : Please remove all unrelated device types. - Remote  ## Screenshots  ![grafik](https://user-images.githubusercontent.com/13820214/101405115-e7063580-38d7-11eb-898c-8f392444e216.png) ![grafik](https://user-images.githubusercontent.com/13820214/101405182-043b0400-38d8-11eb-9892-17042d9be5b9.png) ![grafik](https://user-images.githubusercontent.com/13820214/101407259-e8852d00-38da-11eb-8b33-233b101e4ed1.png) ![grafik](https://user-images.githubusercontent.com/13820214/101405298-2896e080-38d8-11eb-9b24-84c406d8645e.png)

It doesn’t look standard to me …

chris · December 10, 2021, 10:02pm

I think it will still set this to true even if it fails - otherwise it can keep trying forever for devices that don’t work and that will choke the system.

Check if there are any errors in the log - or provide a debug log and i’ll have a look.

Ok, I’m only going on the clusters / channels I saw above, and it apparently supports the ONOFF and LEVELCONTROL and it reports as a DIMMERSWITCH device, so you should get a channel providing these functions, and I would have expected the device to send the respective commands for these clusters. Without more detailed info I’m just guessing.

I will need to find some time to look at the link and try and work out what it’s doing - I’ll try and do that tonight if I can.

anon71759204 · December 11, 2021, 2:22pm

openhab> log:display | grep -i cdf
14:42:48.112 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:42:57.845 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:43:07.579 [INFO ] [ing.zigbee.handler.ZigBeeThingHandler] - BC33ACFFFE615CDF: Channel zigbee:device:dbb76ab009:bc33acfffe615cdf:BC33ACFFFE615CDF_1_batteryalarm failed to initialise device
14:43:56.248 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from UNKNOWN to ONLINE
14:43:56.287 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from ONLINE to UNKNOWN
14:48:46.502 [ERROR] [nverter.ZigBeeConverterBatteryPercent] - BC33ACFFFE615CDF: Error 0xffff setting server binding
14:48:56.295 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:49:06.028 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:49:15.760 [INFO ] [ing.zigbee.handler.ZigBeeThingHandler] - BC33ACFFFE615CDF: Channel zigbee:device:dbb76ab009:bc33acfffe615cdf:BC33ACFFFE615CDF_1_batteryalarm failed to initialise device
14:50:04.583 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from UNKNOWN to ONLINE
14:50:04.621 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from ONLINE to UNKNOWN
14:51:12.849 [ERROR] [nverter.ZigBeeConverterBatteryPercent] - BC33ACFFFE615CDF: Error 0xffff setting server binding
14:51:22.574 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:51:32.395 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:51:42.151 [INFO ] [ing.zigbee.handler.ZigBeeThingHandler] - BC33ACFFFE615CDF: Channel zigbee:device:dbb76ab009:bc33acfffe615cdf:BC33ACFFFE615CDF_1_batteryalarm failed to initialise device
14:52:30.834 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from UNKNOWN to ONLINE
14:52:35.534 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from ONLINE to UNKNOWN
14:53:04.729 [ERROR] [nverter.ZigBeeConverterBatteryPercent] - BC33ACFFFE615CDF: Error 0xffff setting server binding
14:53:14.513 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:53:24.245 [ERROR] [.converter.ZigBeeConverterSwitchLevel] - BC33ACFFFE615CDF: Error 0xffff setting client binding
14:53:33.976 [INFO ] [ing.zigbee.handler.ZigBeeThingHandler] - BC33ACFFFE615CDF: Channel zigbee:device:dbb76ab009:bc33acfffe615cdf:BC33ACFFFE615CDF_1_batteryalarm failed to initialise device
14:54:22.746 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:dbb76ab009:bc33acfffe615cdf' changed from UNKNOWN to ONLINE

It is impossible to get reproducible results from the UI. Unknown device/known device after Scan, status ONLINE/UNKNOWN, zigbee_device_initialised false/true, Initialize device works/doesn’t work (from the view of the UI) - almost any combination of these states seems to be possible … Initialize device doubled etc.

One cannot tell apart whether one is dealing with problems/bugs within the openHAB core, the presentation layer, the binding or the physical device.

chris · December 11, 2021, 6:40pm

This is the error that means reporting is not configured.

I don’t see that here. You don’t have two bindings loaded or something like that? This is provided by the binding itself and I just checked and it’s definitely just there once.

Given the above error, there is something wrong when configuring the device. A debug log might provide a little more information - if there is a timeout or if the device is reporting an error during configuration.

anon71759204 · December 11, 2021, 10:22pm

DUT is 7776 / BC33ACFFFE615CDF :

lrup.zip.txt (79.6 KB)

Actions:
2x ZigBee Scan, then Add Thing from Inbox

Intermediate Result:
State: UNKNOWN
Thing properties: 14 (or 15?)

Show advanced → Initialize device → Toggle ON

Final Result:
State ONLINE
Thing properties: 20, zigbee_device_initialised: true

Now there are three Toggle Switches that seem to be synchronized :

Data received when button pressed (buttons #1-#4 (from top to bottom) - excerpt from debug log, see below for a complete log):

Button #1 ("O" - off):

22:38:36.641 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=5, ackNum=2, reTx=false, data=6A 90 01 3F 00 03 FD FF 04 01 06 00 01 FF 00 01 00 00 EB 00 00 00]
22:39:26.448 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=0, ackNum=4, reTx=false, data=9C 90 01 3F 00 03 FD FF 04 01 06 00 01 FF 00 01 00 00 EC 00 00 00]
22:40:11.264 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=5, ackNum=0, reTx=false, data=C8 90 01 3F 00 03 FD FF 04 01 06 00 01 FF 00 01 00 00 ED 00 00 00]
22:40:51.086 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=6, ackNum=0, reTx=false, data=F0 90 01 3F 00 03 FD FF 04 01 06 00 01 FF 00 01 00 00 EE 00 00 00]
22:42:56.104 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=4, ackNum=5, reTx=false, data=6D 90 01 3F 00 03 FD FF 04 01 06 00 01 FF 00 01 00 00 EF 00 00 00]

Button #2 ("I" - ON):

22:49:23.364 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=5, ackNum=0, reTx=false, data=F0 90 01 3F 00 00 76 77 04 01 06 00 01 01 40 11 00 00 39 2F 00 00]
22:50:05.504 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=3, ackNum=2, reTx=false, data=1A 90 01 3F 00 00 76 77 04 01 06 00 01 01 40 11 00 00 3A 30 00 00]

Button #3 (dim+):

22:51:24.497 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=4, ackNum=0, reTx=false, data=68 90 01 3F 00 03 FD FF 04 01 08 00 01 FF 00 01 00 00 F6 00 00 00]
22:52:30.437 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=7, ackNum=2, reTx=false, data=AA 90 01 3F 00 03 FD FF 04 01 08 00 01 FF 00 01 00 00 F7 00 00 00]

Button #4 (dim-):

22:53:08.514 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=6, ackNum=0, reTx=false, data=D0 90 01 3F 00 03 FD FF 04 01 08 00 01 FF 00 01 00 00 F8 00 00 00]
22:53:55.684 [DEBUG] [le.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=6, ackNum=7, reTx=false, data=FF 90 01 3F 00 03 FD FF 04 01 08 00 01 FF 00 01 00 00 F9 00 00 00]

Button #2 seems to be special insofar as the message contains the address of the DUT, whereas all messages “from” all other buttons contain FFFD (broadcast?).

Debug log (2x button #1, 2x button #2, 2x button#3, 2x button#4):
buttons1.txt (28.3 KB)

2nd try, same actions:
buttons2.txt (43.5 KB)

anon71759204 · July 6, 2022, 10:46am

Success story:

DUT:

Lidl Smart Home LED-Band (RGB, 2 m, IAN 360061_2010, EAN 4055334240956)
hacked Lidl/Silvercrest gateway
latest openHABian (#2987)

You have to set the Color Channel to ‘XY’, ‘Auto’ doesn’t work:

Works like a charm.