Open roxart opened 1 month ago
manufName:_TZ3000_iszegwpd powerSource: Battery modelId: TS0046 epList:[1,2,3,4,5,6], ep1: inClusterList: [1,6,57344,0], outClusterList: [25,10] ep2: inClusterList: [6,1,6], outClusterList: [] ep3: inClusterList: [6,1,6], outClusterList: [] ep4: inClusterList: [6,1,6], outClusterList: [] ep5: inClusterList: [6,1,6], outClusterList: [] ep6: inClusterList: [6,1,6], outClusterList: []
I'll add this to the next update, please report back how it works. I know it supports 1 and 2 click aswell as long press. Initially it will only support 1 and 2 clicks.
do I get a notification here when it's added?
@roxart in the test version now
not sure if you want feedback here or in the homey forum - however on a quick check with the flow below everything seems to trigger.
when I long press the 1 click triggers (I know you said it wont work at first just for you to know what happens)
also I want to add: the longpress is actually important for me, as I want to use some of these buttons to control blinds and longpress is to go up and stop on release - i guess on release does not have a trigger so that is obsolete what is the problem, that those do not work?
Hi @roxart, no problem just work.. :)
This is what I see in the log when you press the buttons: 2024-10-07T21:27:23.247Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] endpointId: 4 , clusterId: 6 , frame: <Buffer 01 13 fd 00> , meta: { dstEndpoint: 1 } 2024-10-07T21:27:23.250Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Frame JSON data: { type: 'Buffer', data: [ 1, 19, 253, 0 ] } 2024-10-07T21:27:23.258Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Triggered 4 Gang Wall Remote, action=rightDown-oneClick 2024-10-07T21:27:24.257Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] endpointId: 4 , clusterId: 6 , frame: <Buffer 01 13 fd 00> , meta: { dstEndpoint: 1 } 2024-10-07T21:27:24.259Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Frame JSON data: { type: 'Buffer', data: [ 1, 19, 253, 0 ] } 2024-10-07T21:27:24.266Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Triggered 4 Gang Wall Remote, action=rightDown-oneClick 2024-10-07T21:27:35.131Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] endpointId: 1 , clusterId: 6 , frame: <Buffer 01 14 fd 00> , meta: { dstEndpoint: 1 } 2024-10-07T21:27:35.132Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Frame JSON data: { type: 'Buffer', data: [ 1, 20, 253, 0 ] } 2024-10-07T21:27:35.335Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Triggered 4 Gang Wall Remote, action=leftUp-oneClick 2024-10-07T21:27:36.121Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] endpointId: 1 , clusterId: 6 , frame: <Buffer 01 14 fd 00> , meta: { dstEndpoint: 1 } 2024-10-07T21:27:36.121Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Frame JSON data: { type: 'Buffer', data: [ 1, 20, 253, 0 ] } 2024-10-07T21:27:36.298Z [log] [ManagerDrivers] [Driver:wall_remote_4_gang_3] [Device:72f144fa-4201-4cdc-ae33-0f42348505eb] Triggered 4 Gang Wall Remote, action=leftUp-oneClick
For me to know what button does what on your side it's important you use the buttons in the order of button 1 - 1 click, button 1 - 2 clicks, button 1 - long press and so forth. so that I can map the buttons to behaviour.
I'll add some extra logging too and give a notice when you can try and send a new diagnostic report.
ok I did what you asked for from button 1 to 6 always 1 click 2 click longpress d3367203-408a-4681-aaa5-8dfc5dda050c
ok I did what you asked for from button 1 to 6 always 1 click 2 click longpress d3367203-408a-4681-aaa5-8dfc5dda050c
did this help @JohanBendz or you need anything else?
Prerequisites:
Device Information
Device Interview
Data
Settings
Additional Comments:
How to interview a device