SilverCrest PowerStrip 3 AC (16A) with 4 USB Model HG06338 #9564
Comments
|
I have the same problem if anyone knows how to solve this problem tell us pls |
|
This is happening to me as well. When I toggle the 1st switch, they all toggle. When I try to toggle switches 2 or 3, I get errors. From what I can tell, the endpoints aren't being exposed properly. And the database entry is: I'm using: |
|
I having one that is around one year old and its have 4 end points and working OK switching etch plug. Its have App version 69 then reading it from basic cluster and some user is having version 70 that looks having problem in the firmware. Do some user have one LIDL or tuya ZBGW for testing if its working there with some magic ? |
|
I have the exact same problem `Zigbee2MQTT:error 2021-12-12 18:22:20: Device 'MQTT Extensao Escritorio' has no endpoint 'l2' |
|
I also have the same problem, only the first endpoint works and it toggles all 3 switches. I noticed we seem to be all Portuguese, could it be a problem specific to the version sold in LIDL Portugal? 🤔 Using Zigbee2MQTT version 1.22.1 and the Slaesh's CC2652RB stick as coordinator. |
|
I have the same issue with a 07/2021 strip, only 1 switch that works, but controls all three. Other switched give the error message no endpoint available |
|
I'm trying to read the Lidl Home application code, but so far I haven't found anything useful for this problem. I don't know if it's possible or not, to sniff the zigbee network to try to capture the communication between the APP (mobile phone) and the Zigbee network. |
|
If you is having one EM35X or EFR32MGX coordinator or one TI CC-2531 with sniffing firmware you can sniffing all Zigbee traffic you like If you is paring the power strip and sniffing how the tuya ZBGW is "talking" with it i can looking in it and see if its doing some magic. One thing is then you is posing one Zigbee sniffing then pairing one device its also possible see you current network key !! |
I agree this seems to be a Portuguese LIDL problem. The reports I've seen of this problem here and some other places are all from Portugal. Can anyone connect their power strip to the official LIDL gateway and check if there are any firmware updates pending (if it even has that function). I can try this later this week. |
|
I’m actually Dutch and have the same problem, with the cc2531 and the
Sonoff Zigbee 3 stick. Sold by lidl Netherlands during the Black Friday
sale
IAN 369230_2010 spsz3a1 version 07/2021 (25?)
…On Wed, 29 Dec 2021 at 17:08, BFFonseca ***@***.***> wrote:
I also have the same problem, only the first endpoint works and it toggles
all 3 switches.
I noticed we seem to be all Portuguese, could it be a problem specific to
the version sold in LIDL Portugal? 🤔
Using Zigbee2MQTT version 1.22.1 and the Slaesh's CC2652RB stick as
coordinator.
I agree this seems to be a Portuguese LIDL problem. The reports I've seen
of this problem here and some other places are all from Portugal.
Could this be a firmware issue? I sure hope it's not a hardware revision
to use less parts...
Can anyone connect their power strip to the official LIDL gateway and
check if there are any firmware updates pending (if it even has that
function). I can try this later this week.
—
Reply to this email directly, view it on GitHub
<#9564 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW7JROC7AHWCHYH4V3XRR4DUTMXAPANCNFSM5HTTTQNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
I can confirm that: with the Lidl GW works normally.
I don't have that hardware :-( I'm only using the CONBEE II and also have a SONOFF Zigbee with tasmota. |
|
Sonff ZBB and stick both can being used for sniffing Zigbee traffic so if having one tuya TBGW pleas sniff then paring the device with tuya ZBGW and posing the sniff so we can taking on look how they is doing there magic. Zigpy Wiki how to sniffing with links to other guides and hardware https://github.com/zigpy/zigpy/wiki/Sniffing-Zigbee-traffic. PS I have 2 early ones that is on the od firmware but LIDL is having them in this week for 25€ but i dont baying more them i dont need only the things that i dont have but i think the is one new batch with the new firmware and not only the PT version but we is going to knowing more in some days then more user is buying them. Edit ConBee II is having sniffing firmware 2 !! |
|
Any update on this? I have multiple powerstrips but only the latest with app 70 has this problem. |
Same issue over here (also in the Netherlands), bought the €25,- version in december and I can only control all the plugs at once. The older version (bought for €30,-) can control alle the plugs seperatly. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
Still an issue. |
|
Hi, Able to modify some files if you need someone to test. Kind regards, |
|
Hello, I got a couple of this from LIDL (France) and I'm experiecing the same issue (3 switches reported, only first is functionnal but manages all channels simultaneously). I am using a usb coordinator, a Texas Instrument CC2531 CDC device (20180507). I also gave it a shot within Home Assistant and its ZHA integration, using a Sonoff ZBBridge with less success (only reported one switch, turning on/off all channels at once). I'm willing to help debug this with some guidance (only got so far as pairing devices and small debugging so far) if needed. Cheers : ) |
|
Sniffing then pairing it with one tuya ZBGW is the only thing that can reviling the "tuya magic" but very likely its the same as being found on the TS004F dimmer switch. |
|
Someone has sniffed pairing with lidl gateway: 32 77.217605 0x0000 0x33e8 ZigBee 73 Transport Key If it can help.. |
|
Yes i have seen that but its not showing the attributes and commands with all flags that is needed for see what being dome under the hood. |
|
Hey @Element2 thanks for posting the briefly sniffing (in deCONZ git) of the LIDL power strip but can you pleas posting the capture file from wireshark so its possible to see all the flags and parameters the tuya ZBGW is using then only "read attribute" is not helping. Thanks in advance !! |
|
I'm willing to post any interesting frames here, but not the whole capture since the network key is in all the frames. |
|
Thanks Element2 !! Can you folding out all feeds of frame 37, 54, 87, 89, 92, 94, 98, 102, 108, 112, 114, 151, 153, 224, 230, 234, 236, 241 and 245 (all attribute reading and replay from the device) and posting them or making on text file of them and attaching it in one post ? I think the rest is not important then normally tuya is reading and writing attributes for making there magic and the rest is normal pairing what i can see. |
|
Sorry dont folding out Zigbee network security, And copy all shown elements then the network key is not being exposed. |
|
Here are the requested frames. |
|
@MattWestb the standard tuya "magic spell" may be enough to make these LIDL powerstrip sockets be controlled individually! Last days I had a very similar case with this device ( combined wall switch with a socket for Brazil ) : The two switches and the one socket can be controlled individually using the standard OnOff cluster 0x006, but different endpoints 1, 2, and 3. Sending the during the Zigbee pairing process solved the issue. |
|
@kkossev Its more or less the standard for tuya device both "normal Zigbee" ones and its looks like some MCU / DP devices is needing the same spells for working "normal". Have you starting putting it as standard for all tuya devices in Hubitat or is you waiting for problems before adding it ? PS. Nice matrix https://github.com/kkossev/Hubitat/blob/main/Tuya.md !! |
|
Don't know if this is relevant, but this new powerstrip has also problems with pairing and discovering all three endpoints in Phoscon. |
|
I also have the same problem, only the first endpoint works and it toggles all 3 switches. |
|
Same problem as reported here with a new fresh device buy in france. |
|
For people want to test now: for the device "HG06338" change the configure section: ` ` As @MattWestb mentionned you need read some attributes on endpoint1 |
|
Tested here, the device now works as expected, good job ! 👍 |
|
@luminouw you just edited the devices.js right? I did it and didnt worked for me. |
You must edit the lidl.js and restart zigbee2mqtt |
|
Thanks a lot, it works perfectly |
|
@simaoafonso As @realPy said, I just edited the |
Yes you are right i'm forgot to mention to remove device and reassociated |
|
@realPy I did all that but not on the lidl.js, where can I find it? |
I dont known how you have launch zigbee2mqtt.It must be in the node-modules/zigbee-herdsman-converters/devices/lidl.js |
I dont have that devices folder I just have the devices.js. I´ll wait for the next realese, tanks! |
|
@realPy could you make a PR? Just click the pencil/edit icon here: https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices%2Flidl.js Nevermind, just saw Koenkk/zigbee-herdsman-converters#3967 Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
|
Largest thanks is going to @Element2 that was doing great sniffing and now hi must waiting getting working in de(F)CONZ . . . ;-(( Now only waiting for next tuya device that need some tuya magic cast for working OK :-)) God work done !! |
|
Hello. Thank you in advance...
|
|
The power splay have one capacitor that is being bad (its start expanding and can blowing) and need being replaced but its not recommended to do if you is having the skill doing it right. |
What happened
After pair , can't control each socket of device.
When I toggle the first socket, it's change all 3.
the other two, return error.
Zigbee2MQTT:error 2021-11-08 20:39:07: Device '0x50325ffffe5308b5' has no endpoint 'l2'
Zigbee2MQTT:error 2021-11-08 20:39:07: Device '0x50325ffffe5308b5' has no endpoint 'l3'
What did you expect to happen
control the 3 switch individual
How to reproduce it (minimal and precise)
Debug info
Zigbee2MQTT version: 1.22.0
Adapter hardware: Conbee II
Adapter firmware version: 0x26720700
Frontend version 0.6.30
(HA Addon)
https://zigbee.blakadder.com/Lidl_HG06338.html
2021-11-08T20:25:08.295Z zigbee-herdsman:controller:device:log Interview - got 'hardwareVersion' for device '0x50325ffffe5308b5'
2021-11-08T20:25:08.295Z zigbee-herdsman:controller:endpoint Read 0x50325ffffe5308b5/1 genBasic(["dateCode"], {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2021-11-08T20:25:08.296Z zigbee-herdsman:deconz:adapter zclFrame.payload:
2021-11-08T20:25:08.296Z zigbee-herdsman:deconz:adapter [ { attrId: 6 } ]
2021-11-08T20:25:08.296Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x2017 EP:1 SeqNr. 100 request id: 20
2021-11-08T20:25:08.307Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 20 status: 0
2021-11-08T20:25:08.308Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.308Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2021-11-08T20:25:08.308Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.312Z zigbee-herdsman:deconz:driver query aps data confirm
2021-11-08T20:25:08.317Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 101
2021-11-08T20:25:08.320Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x2017 request id: 20 confirm status: 0
2021-11-08T20:25:08.320Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.320Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 12
2021-11-08T20:25:08.358Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2021-11-08T20:25:08.358Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.360Z zigbee-herdsman:deconz:driver query aps data indication
2021-11-08T20:25:08.366Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 102
2021-11-08T20:25:08.370Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 102 srcAddr: 0x2017 destAddr: 0x0 profile id: 0x104 cluster id: 0x0 lqi: 255
2021-11-08T20:25:08.370Z zigbee-herdsman:deconz:frameParser response payload: 24,12,1,6,0,0,66,0
2021-11-08T20:25:08.371Z zigbee-herdsman:deconz:adapter resolve data request with transSeq Nr.: 12
2021-11-08T20:25:08.372Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":12,"manufacturerCode":null,"commandIdentifier":1},"Payload":[{"attrId":6,"status":0,"dataType":66,"attrData":""}],"Command":{"ID":1,"name":"readRsp","parameters":[{"name":"attrId","type":33},{"name":"status","type":32},{"name":"dataType","type":32,"conditions":[{"type":"statusEquals","value":0}]},{"name":"attrData","type":1000,"conditions":[{"type":"statusEquals","value":0}]}]}},"address":8215,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
2021-11-08T20:25:08.373Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.373Z zigbee-herdsman:deconz:adapter response received
2021-11-08T20:25:08.374Z zigbee-herdsman:controller:device:log Interview - got 'dateCode' for device '0x50325ffffe5308b5'
2021-11-08T20:25:08.374Z zigbee-herdsman:controller:endpoint Read 0x50325ffffe5308b5/1 genBasic(["swBuildId"], {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2021-11-08T20:25:08.375Z zigbee-herdsman:deconz:adapter zclFrame.payload:
2021-11-08T20:25:08.375Z zigbee-herdsman:deconz:adapter [ { attrId: 16384 } ]
2021-11-08T20:25:08.383Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x2017 EP:1 SeqNr. 103 request id: 21
2021-11-08T20:25:08.399Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 21 status: 0
2021-11-08T20:25:08.399Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.399Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2021-11-08T20:25:08.399Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.405Z zigbee-herdsman:deconz:driver query aps data confirm
2021-11-08T20:25:08.410Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 104
2021-11-08T20:25:08.413Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x2017 request id: 21 confirm status: 0
2021-11-08T20:25:08.413Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.413Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 13
2021-11-08T20:25:08.450Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2021-11-08T20:25:08.450Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.452Z zigbee-herdsman:deconz:driver query aps data indication
2021-11-08T20:25:08.458Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 105
2021-11-08T20:25:08.462Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 105 srcAddr: 0x2017 destAddr: 0x0 profile id: 0x104 cluster id: 0x0 lqi: 255
2021-11-08T20:25:08.462Z zigbee-herdsman:deconz:frameParser response payload: 24,13,1,0,64,134
2021-11-08T20:25:08.462Z zigbee-herdsman:deconz:adapter resolve data request with transSeq Nr.: 13
2021-11-08T20:25:08.463Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":13,"manufacturerCode":null,"commandIdentifier":1},"Payload":[{"attrId":16384,"status":134}],"Command":{"ID":1,"name":"readRsp","parameters":[{"name":"attrId","type":33},{"name":"status","type":32},{"name":"dataType","type":32,"conditions":[{"type":"statusEquals","value":0}]},{"name":"attrData","type":1000,"conditions":[{"type":"statusEquals","value":0}]}]}},"address":8215,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
2021-11-08T20:25:08.464Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.464Z zigbee-herdsman:deconz:adapter response received
2021-11-08T20:25:08.465Z zigbee-herdsman:controller:endpoint Read 0x50325ffffe5308b5/1 genBasic(["swBuildId"], {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')
2021-11-08T20:25:08.465Z zigbee-herdsman:controller:device:log Interview - failed to read attribute 'softwareBuildID' from endpoint '1' (TypeError: Cannot read property 'swBuildId' of undefined)
2021-11-08T20:25:08.466Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x2017 EP:0 SeqNr. 106 request id: 22
2021-11-08T20:25:08.478Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 22 status: 0
2021-11-08T20:25:08.478Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.479Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2021-11-08T20:25:08.479Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.482Z zigbee-herdsman:deconz:driver query aps data confirm
2021-11-08T20:25:08.488Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 107
2021-11-08T20:25:08.492Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x2017 request id: 22 confirm status: 0
2021-11-08T20:25:08.492Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.532Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2021-11-08T20:25:08.532Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.537Z zigbee-herdsman:deconz:driver query aps data indication
2021-11-08T20:25:08.542Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 108
2021-11-08T20:25:08.547Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 108 srcAddr: 0x2017 destAddr: 0x0 profile id: 0x0 cluster id: 0x8004 lqi: 252
2021-11-08T20:25:08.547Z zigbee-herdsman:deconz:frameParser response payload: 22,0,23,32,10,242,224,161,97,0,0,0,1,33,0
2021-11-08T20:25:08.547Z zigbee-herdsman:deconz:adapter resolve data request without a transSeq Nr.
2021-11-08T20:25:08.548Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.548Z zigbee-herdsman:deconz:adapter RECEIVING SIMPLE_DESCRIPTOR - addr: 0x2017 EP:242 inClusters: outClusters: 33
2021-11-08T20:25:08.548Z zigbee-herdsman:controller:device:log Interview - got simple descriptor for endpoint '242' device '0x50325ffffe5308b5'
2021-11-08T20:25:08.550Z zigbee-herdsman:controller:device:log Interview - completed for device '0x50325ffffe5308b5'
2021-11-08T20:25:08.550Z zigbee-herdsman:controller:log Succesfully interviewed '0x50325ffffe5308b5'
2021-11-08T20:25:08.573Z zigbee-herdsman:controller:endpoint Bind 0x50325ffffe5308b5/1 genOnOff from '0x00212effff0711ab/1'
2021-11-08T20:25:08.585Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x2017 EP:0 SeqNr. 109 request id: 23
2021-11-08T20:25:08.601Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 23 status: 0
2021-11-08T20:25:08.601Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.662Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101110
2021-11-08T20:25:08.662Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.663Z zigbee-herdsman:deconz:driver query aps data confirm
2021-11-08T20:25:08.669Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 110
2021-11-08T20:25:08.670Z zigbee-herdsman:deconz:driver query aps data indication
2021-11-08T20:25:08.672Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x2017 request id: 23 confirm status: 0
2021-11-08T20:25:08.672Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.672Z zigbee-herdsman:deconz:driver query aps data indication
2021-11-08T20:25:08.675Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 111
2021-11-08T20:25:08.680Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 112
2021-11-08T20:25:08.680Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 111 srcAddr: 0x2017 destAddr: 0x0 profile id: 0x0 cluster id: 0x8021 lqi: 255
2021-11-08T20:25:08.681Z zigbee-herdsman:deconz:frameParser response payload: 23,0
2021-11-08T20:25:08.681Z zigbee-herdsman:deconz:adapter resolve data request without a transSeq Nr.
2021-11-08T20:25:08.681Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:08.681Z zigbee-herdsman:deconz:adapter BIND RESPONSE - addr: 0x2017 status: 0
Zigbee2MQTT:error 2021-11-08 20:25:08: Failed to configure '0x50325ffffe5308b5', attempt 1 (TypeError: Cannot read property 'bind' of undefined
at Object.bind (/app/node_modules/zigbee-herdsman-converters/lib/reporting.js:33:24)
at Object.configure (/app/node_modules/zigbee-herdsman-converters/devices/lidl.js:98:33)
at Configure.configure (/app/lib/extension/configure.ts:115:13))
2021-11-08T20:25:16.743Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 113
2021-11-08T20:25:16.754Z zigbee-herdsman:deconz:frameParser device state: 10100010
2021-11-08T20:25:16.755Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2021-11-08T20:25:26.742Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 114
2021-11-08T20:25:26.748Z zigbee-herdsman:deconz:frameParser device state: 10100010
2021-11-08T20:25:26.749Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
The text was updated successfully, but these errors were encountered: