+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: Zigbee - ID Lock 150 Issues (/showthread.php?tid=4746)
Zigbee - ID Lock 150 Issues - Evens - 30.04.2023
Hi,
I have some issues with integrating ID Lock 150 door control with LM5 through Zigbee.
In this system I already have a Zigbee network with two devices, I’m using the USB dongle in this case.
LM Firmware: 20211215
LM Hardware: LM5 Lite + Ext (i.MX6)
Zigbee app: Latest.
I have through the Zigbee App added the ID Lock 150, and I can from the Control and status tab lock and unlock the door.
After linking to group address, I try to lock and unlock the door from the LM but nothing happens. When running monitor in Zigbee app and sending commando from LM there are no data. When doing the same but sending the command from the Control and status tab in Zigbee app there are data in the monitor.
For me there seems to be a bug in sending data from LM to Zigbee, but my other two devices work flawlessly. Any idea on what can be the problem?
I have also read the thread on the forum where the same issues are highlighted, but no solution is presented there.
Best Regard
Even Sundgot.
RE: Zigbee - ID Lock 150 Issues - admin - 02.05.2023
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.
RE: Zigbee - ID Lock 150 Issues - Evens - 18.05.2023
(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 }
RE: Zigbee - ID Lock 150 Issues - admin - 19.05.2023
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.
RE: Zigbee - ID Lock 150 Issues - Evens - 20.05.2023
(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" ] }
RE: Zigbee - ID Lock 150 Issues - admin - 22.05.2023
Still no entries when sent from the UI. Look for entries starting with { ClosuresDoorLockClusterFrame = ...
Mapping control also looks fine - coordinator sends UnlockDoor command, lock responds with UnlockDoorResponse with Status = 0 (Success).
RE: Zigbee - ID Lock 150 Issues - stemic01 - 24.05.2023
Following....
RE: Zigbee - ID Lock 150 Issues - Evens - 25.06.2023
(22.05.2023, 06:46)admin Wrote: Still no entries when sent from the UI. Look for entries starting with { ClosuresDoorLockClusterFrame = ...
Mapping control also looks fine - coordinator sends UnlockDoor command, lock responds with UnlockDoorResponse with Status = 0 (Success).
found no entries starting with { ClosuresDoorLockClusterFrame = ...
its strange becouse it works good from the mapping control.
RE: Zigbee - ID Lock 150 Issues - stemic01 - 20.07.2023
@Evens - Did you find a way of mapping and controlling your ID lock from LM? It would be so cool to manage this.
My goal is to:
1) Being able to remotely open/lock the ID lock 150 (I can today but need to enter the zigbee app and its not very user friendly and takes time).
2) Being able to change how the auto lock works with logics. In example following the "mode" of the house (Home/away/night etc) and also times for autolock etc.
3) Easily disable and enable the autolock function (I love autolock most days, but not when expecting visitors or when working around the house and garden it is nice to disable it).
4) Bonus; being able to add codes to visitors if needed. (Guess this is not easy).
5) Read status of locked / open.
I was considering to go for the Unifi Door Access system which looks very intuitive and interesting, but I guess that will be even harder to integrate to the LM.
RE: Zigbee - ID Lock 150 Issues - Evens - 25.08.2023
(25.06.2023, 17:55)Evens Wrote:(22.05.2023, 06:46)admin Wrote: Still no entries when sent from the UI. Look for entries starting with { ClosuresDoorLockClusterFrame = ...
Mapping control also looks fine - coordinator sends UnlockDoor command, lock responds with UnlockDoorResponse with Status = 0 (Success).
found no entries starting with { ClosuresDoorLockClusterFrame = ...
its strange becouse it works good from the mapping control.
Hi Admin,
Are there anything i should do to assist more?
(20.07.2023, 08:39)stemic01 Wrote: @Evens - Did you find a way of mapping and controlling your ID lock from LM? It would be so cool to manage this.
My goal is to:
1) Being able to remotely open/lock the ID lock 150 (I can today but need to enter the zigbee app and its not very user friendly and takes time).
2) Being able to change how the auto lock works with logics. In example following the "mode" of the house (Home/away/night etc) and also times for autolock etc.
3) Easily disable and enable the autolock function (I love autolock most days, but not when expecting visitors or when working around the house and garden it is nice to disable it).
4) Bonus; being able to add codes to visitors if needed. (Guess this is not easy).
5) Read status of locked / open.
I was considering to go for the Unifi Door Access system which looks very intuitive and interesting, but I guess that will be even harder to integrate to the LM.
Hi Stemic01,
No not yet, but it should be possible to fix.
1) Should work when bug is fixed.
2) Should be easy to do.
3) Should be possible to do if Schedule are in LM.
4) as of now not possible trough zigbee profile that are in LM, but maby its possible to add?
5) works when bug is fixed.
BR Even.
RE: Zigbee - ID Lock 150 Issues - admin - 25.08.2023
The manufacturer was supposed to send us the lock for integration but unfortunately it never happened. It's quite hard to debug without having the actual device.
RE: Zigbee - ID Lock 150 Issues - Evens - 25.08.2023
(25.08.2023, 14:05)admin Wrote: The manufacturer was supposed to send us the lock for integration but unfortunately it never happened. It's quite hard to debug without having the actual device.
I understand. I can provide vpn to the site if that helps with the debug?
RE: Zigbee - ID Lock 150 Issues - admin - 28.08.2023
Send me access details via PM.