This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Zigbee - ID Lock 150 Issues
#5
(19.05.2023, 07:47)admin Wrote: There's no door lock/unlock request in the log when the command send from the UI. The log from object mapping looks correct.
Please close the network to reduce the number of logs an try again. Send both True and False from object mapping (make sure that object data type is set to 1 bit boolean). Same for UI - send both Lock and Unlock commands.

Object is 1 bit Boolean. see new log with network closed. 

Command sendt from UI

Date Entry

2023-05-20 18:21:08 CC: MT command SRSP_UTIL_GET_DEVICE_INFO, payload:
{ AssocDevicesList = [ 32854 ], DeviceType = [ "Coordinator", "Router", "EndDevice" ], Status = 0, DeviceState = 9, ShortAddr = 0, IEEEAddr = "00124b0018de517d" }
2023-05-20 18:21:08 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x00, data:
[18] 67 00 00 7D 51 DE 18 00 4B 12 00 00 00 07 09 01 56 80
2023-05-20 18:21:08 ZNP: sending request:
[5] FE 00 27 00 27
2023-05-20 18:21:08 CC: sending SREQ_UTIL_GET_DEVICE_INFO, data: nil
2023-05-20 18:20:58 CC: MT command SRSP_UTIL_GET_DEVICE_INFO, payload:
{ AssocDevicesList = [ 32854 ], DeviceType = [ "Coordinator", "Router", "EndDevice" ], Status = 0, DeviceState = 9, ShortAddr = 0, IEEEAddr = "00124b0018de517d" }
2023-05-20 18:20:58 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x00, data:
[18] 67 00 00 7D 51 DE 18 00 4B 12 00 00 00 07 09 01 56 80
2023-05-20 18:20:58 ZNP: sending request:
[5] FE 00 27 00 27
2023-05-20 18:20:58 CC: sending SREQ_UTIL_GET_DEVICE_INFO, data: nil
2023-05-20 18:20:49 CC: MT command AREQ_ZDO_MGMT_PERMIT_JOIN_RSP, payload:
{ SrcAddr = 0, Status = 0 }
2023-05-20 18:20:49 CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xB6, data:
[5] 45 B6 00 00 00
2023-05-20 18:20:49 CC: MT command SRSP_ZDO_MGMT_PERMIT_JOIN_REQ, payload:
{ Status = 0 }
2023-05-20 18:20:49 CC: MT type SRSP (3), subsystem ZDO (0x05), command id 0x36, data:
[3] 65 36 00
2023-05-20 18:20:49 ZNP: sending request:
[9] FE 04 25 36 FF FF 00 00 17
2023-05-20 18:20:49 CC: sending SREQ_ZDO_MGMT_PERMIT_JOIN_REQ, data:
{ AddrMode = 255, TCSignificance = 0, Duration = 0, DstAddr = 65535 }


Command Sendt from Object mapping

Date Entry

2023-05-20 18:23:04 ZB: packet from 680ae2fffe6bb81a:
{ FrameControl = [ "FrameTypeLocal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 28, ClosuresDoorLockClusterFrame = { CommandIdentifier = "UnlockDoorResponse", UnlockDoorResponse = { Status = 0 } }, ClusterName = "ClosuresDoorLock" }
2023-05-20 18:23:04 CC: incoming message from D0D6, cluster 0101, dst EP 1
2023-05-20 18:23:04 CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 39, Data = [ 25, 28, 1, 0 ], SrcAddr = 53462, SecurityUse = 0, Radius = 27, ClusterId = 257, SrcEndpoint = 1, MacSrcAddr = 36372, GroupId = 0, TransSeqNumber = 0, Timestamp = 13475290, DstEndpoint = 1, WasBroadcast = 0 }
2023-05-20 18:23:04 CC: MT type AREQ (2), subsystem AF (0x04), command id 0x81, data:
[26] 44 81 00 00 01 01 D6 D0 01 01 00 27 00 DA 9D CD 00 00 04 19 1C 01 00 14 8E 1B
2023-05-20 18:23:04 CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [ 32854, 36372 ], DstAddr = 53462 }
2023-05-20 18:23:04 CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[9] 45 C4 D6 D0 02 56 80 14 8E
2023-05-20 18:23:02 CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 0, TransId = 119, Endpoint = 1 }
2023-05-20 18:23:02 CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 00 01 77
2023-05-20 18:23:02 CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2023-05-20 18:23:02 CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2023-05-20 18:23:02 ZNP: sending request:
[19] FE 0E 24 01 D6 D0 01 01 01 01 77 00 1E 04 11 1C 01 00 4C
2023-05-20 18:23:02 CC: sending SREQ_AF_DATA_REQUEST, data:
{ ClusterId = 257, DstEndpoint = 1, Data = [ 17, 28, 1, 0 ], DstAddr = 53462, Radius = 30, Options = [  ], TransId = 119, SrcEndpoint = 1 }
2023-05-20 18:23:02 ZB: sending ZCL message to 680ae2fffe6bb81a, cluster 0101:
{ ClosuresDoorLockClusterFrame = { CommandIdentifier = "UnlockDoor", UnlockDoor = { PinCode = "" } }, TransactionSequenceNumber = 28, FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ] }
Reply


Messages In This Thread
Zigbee - ID Lock 150 Issues - by Evens - 30.04.2023, 18:21
RE: Zigbee - ID Lock 150 Issues - by admin - 02.05.2023, 09:56
RE: Zigbee - ID Lock 150 Issues - by Evens - 18.05.2023, 15:52
RE: Zigbee - ID Lock 150 Issues - by admin - 19.05.2023, 07:47
RE: Zigbee - ID Lock 150 Issues - by Evens - 20.05.2023, 16:25
RE: Zigbee - ID Lock 150 Issues - by admin - 22.05.2023, 06:46
RE: Zigbee - ID Lock 150 Issues - by Evens - 25.06.2023, 17:55
RE: Zigbee - ID Lock 150 Issues - by Evens - 25.08.2023, 14:00
RE: Zigbee - ID Lock 150 Issues - by stemic01 - 24.05.2023, 21:59
RE: Zigbee - ID Lock 150 Issues - by stemic01 - 20.07.2023, 08:39
RE: Zigbee - ID Lock 150 Issues - by admin - 25.08.2023, 14:05
RE: Zigbee - ID Lock 150 Issues - by Evens - 25.08.2023, 19:49
RE: Zigbee - ID Lock 150 Issues - by admin - 28.08.2023, 08:21

Forum Jump: