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
#3
(02.05.2023, 09:56)admin Wrote: Commands sent via object mapping are not visible in the monitor.
Install the latest ZigBee app from the store, go to Configuration and enable Debug logging. Then please provide logs for door commands sent via UI and object mapping.

Hi Admin,

See copy of logs under:

Command sendt from UI

Date Entry

2023-05-18 17:47:16 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:47:16 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:47:16 ZNP: sending request:
[7] FE 02 27 0A 00 00 2F
2023-05-18 17:47:16 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 0 }
2023-05-18 17:47:14 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:47:14 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:47:14 ZNP: sending request:
[7] FE 02 27 0A 00 01 2E
2023-05-18 17:47:14 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 1 }
2023-05-18 17:47:12 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:47:12 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:47:12 ZNP: sending request:
[7] FE 02 27 0A 00 00 2F
2023-05-18 17:47:12 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 0 }
2023-05-18 17:47:10 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:47:10 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:47:10 ZNP: sending request:
[7] FE 02 27 0A 00 01 2E
2023-05-18 17:47:10 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 1 }


Command Sendt from Object mapping

Date Entry

2023-05-18 17:50:11 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:50:11 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:50:11 ZNP: sending request:
[7] FE 02 27 0A 00 01 2E
2023-05-18 17:50:11 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 1 }
2023-05-18 17:50:09 ZB: packet from 680ae2fffe6bb81a:
{ FrameControl = [ "FrameTypeLocal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 2, ClosuresDoorLockClusterFrame = { CommandIdentifier = "LockDoorResponse", LockDoorResponse = { Status = 0 } }, ClusterName = "ClosuresDoorLock" }
2023-05-18 17:50:09 CC: incoming message from D0D6, cluster 0101, dst EP 1
2023-05-18 17:50:09 CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 39, Data = [ 25, 2, 0, 0 ], SrcAddr = 53462, SecurityUse = 0, Radius = 27, ClusterId = 257, SrcEndpoint = 1, MacSrcAddr = 36372, GroupId = 0, TransSeqNumber = 0, Timestamp = 2073050, DstEndpoint = 1, WasBroadcast = 0 }
2023-05-18 17:50:09 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 A1 1F 00 00 04 19 02 00 00 14 8E 1B
2023-05-18 17:50:09 CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [ 32854, 36372 ], DstAddr = 53462 }
2023-05-18 17:50:09 CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[9] 45 C4 D6 D0 02 56 80 14 8E
2023-05-18 17:50:09 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:50:09 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:50:09 ZNP: sending request:
[7] FE 02 27 0A 00 00 2F
2023-05-18 17:50:09 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 0 }
2023-05-18 17:50:08 CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 0, TransId = 2, Endpoint = 1 }
2023-05-18 17:50:08 CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 00 01 02
2023-05-18 17:50:08 CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2023-05-18 17:50:08 CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2023-05-18 17:50:08 ZNP: sending request:
[19] FE 0E 24 01 D6 D0 01 01 01 01 02 00 1E 04 11 02 00 00 26
2023-05-18 17:50:08 CC: sending SREQ_AF_DATA_REQUEST, data:
{ ClusterId = 257, DstEndpoint = 1, Data = [ 17, 2, 0, 0 ], DstAddr = 53462, Radius = 30, Options = [  ], TransId = 2, SrcEndpoint = 1 }
2023-05-18 17:50:08 ZB: sending ZCL message to 680ae2fffe6bb81a, cluster 0101:
{ ClosuresDoorLockClusterFrame = { CommandIdentifier = "LockDoor", LockDoor = { PinCode = "" } }, TransactionSequenceNumber = 2, FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ] }
2023-05-18 17:50:08 ZB: packet from 680ae2fffe6bb81a:
{ FrameControl = [ "FrameTypeLocal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 1, ClosuresDoorLockClusterFrame = { CommandIdentifier = "LockDoorResponse", LockDoorResponse = { Status = 0 } }, ClusterName = "ClosuresDoorLock" }
2023-05-18 17:50:08 CC: incoming message from D0D6, cluster 0101, dst EP 1
2023-05-18 17:50:08 CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 39, Data = [ 25, 1, 0, 0 ], SrcAddr = 53462, SecurityUse = 0, Radius = 27, ClusterId = 257, SrcEndpoint = 1, MacSrcAddr = 36372, GroupId = 0, TransSeqNumber = 0, Timestamp = 2069774, DstEndpoint = 1, WasBroadcast = 0 }
2023-05-18 17:50:08 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 0E 95 1F 00 00 04 19 01 00 00 14 8E 1B
2023-05-18 17:50:08 CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [ 32854, 36372 ], DstAddr = 53462 }
2023-05-18 17:50:08 CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[9] 45 C4 D6 D0 02 56 80 14 8E
2023-05-18 17:50:08 CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 0, TransId = 1, Endpoint = 1 }
2023-05-18 17:50:08 CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 00 01 01
2023-05-18 17:50:07 CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2023-05-18 17:50:07 CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2023-05-18 17:50:07 ZNP: sending request:
[19] FE 0E 24 01 D6 D0 01 01 01 01 01 00 1E 04 11 01 00 00 26
2023-05-18 17:50:07 CC: sending SREQ_AF_DATA_REQUEST, data:
{ ClusterId = 257, DstEndpoint = 1, Data = [ 17, 1, 0, 0 ], DstAddr = 53462, Radius = 30, Options = [  ], TransId = 1, SrcEndpoint = 1 }
2023-05-18 17:50:07 ZB: sending ZCL message to 680ae2fffe6bb81a, cluster 0101:
{ ClosuresDoorLockClusterFrame = { CommandIdentifier = "LockDoor", LockDoor = { PinCode = "" } }, TransactionSequenceNumber = 1, FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ] }
2023-05-18 17:50:07 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:50:07 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:50:07 ZNP: sending request:
[7] FE 02 27 0A 00 01 2E
2023-05-18 17:50:07 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 1 }
2023-05-18 17:50:05 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:50:05 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:50:05 ZNP: sending request:
[7] FE 02 27 0A 00 00 2F
2023-05-18 17:50:05 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 0 }
2023-05-18 17:50:03 CC: MT command SRSP_UTIL_LED_CONTROL, payload:
{ Status = 1 }
2023-05-18 17:50:03 CC: MT type SRSP (3), subsystem UTIL (0x07), command id 0x0A, data:
[3] 67 0A 01
2023-05-18 17:50:03 ZNP: sending request:
[7] FE 02 27 0A 00 01 2E
2023-05-18 17:50:03 CC: sending SREQ_UTIL_LED_CONTROL, data:
{ Mode = 1 }
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: