@b16b I made some changes that I hope should improve the situation, but without the physical device I have no way to tell for sure.
You are welcome to try them (both child and parent DHTs should be updated)
https://bitbucket.org/yashik_gt/smartthings/src/ts0601-child-dni-update/SmartHome4U/
Regards,
Yakov
i just add the new code i re-connect the device after a delete … because if with the new code does not work properly i will waiting until tomorrow to see what will happen
i describe again the situation
after a day or so the app stop update the childs state and stuck to on or off pareent update normally
so for examply if child 1 have stuck off on the app if tap it loading and sta off but the parent become on and the light turn on if tap it again to turn it off because on the app is already off nothing happen
if turn off the parent that work perfect the light turn off
i will waiting and i post the results tomorrow thanks again
Bro this still working fine great job 
1 Like
Hi @ygerlovin
I just received a 2 gang switch and am using this latest version of your device handler.
- The Parent does not seem to function. (Won’t turn on/off )
- The 2 Children work ok and so I did not mind the problem in item 1 yesterday.
- But today, the 2 Children does not function anymore (they are left in the On state and is also reflected in ST (they were turned on at sunset thru an automation). But you can’t turn them off or toggle in ST anymore, but you can do so in the physical switch - but the status is not updated in ST.
I have not done anything yet such as delete and re-pair. Should I do that first?
Hi @ygerlovin, it’s a wall switch.
Model: link to MoesHouse
I don’t know why I cannot switch off the backlight of my switch.
Yesterday I tried that, set it to “Off” but nothing happened. After a couple of minutes, my switch stopped working. I needed to unwire and after that remove and add again (in ST) in order to make it work again.
Hi @Ed_Cayetano,
I would guess your switch has slightly different model number and therefore is not detected by the DHT as one that needs a special handling for the parent. If I’m right, then it also wasn’t detected by the handler and you needed to configure it manually.
To fix that, I will need a zigbee join message (as text) and preferably the link to the product.
Regarding the issue that the switch stops functioning after a while.
Are you using the version that was provided to Kostas
https://bitbucket.org/yashik_gt/smartthings/src/ts0601-child-dni-update/SmartHome4U/
or the latest version from master branch?
1 Like
Hi @iwry ,
Could you please provide zigbee join message and live logging for this issue?
Was the switch automatically detected by the handler or you needed to configure it manually?
Which version are you using?
Is it from the main branch or the version that tries to fix loss of control after disconnection?
Thanks
Hi Yakov,
If you need a live logging I can remove and add the device again.
It was recognized as “Moes Multi Switch 1”, then I changed to TS0601 Relay
I’m using the version from the main branch of Jul-2021.
What I noticed now checking the live logging is that I’m getting some errors since I added the switch again:
6f5ddaf2-6176-4c1e-9048-51a63c43184b 17:35:51: debug Unhandled Event - description:catchall: 0104 0000 01 01 0000 00 0BE7 00 01 115F 0A 01 01FF422B6410010328249839D7A38040953902FFF84205213B009A2000082122130727000000000000000009210205, parseMap:[raw:0104 0000 01 01 0000 00 0BE7 00 01 115F 0A 01 01FF422B6410010328249839D7A38040953902FFF84205213B009A2000082122130727000000000000000009210205, profileId:0104, clusterId:0000, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:0BE7, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:0A, direction:01, attrId:FF01, encoding:42, value:05022109000000000000000027071322210800209a003b210542f8ff0239954080a3d73998242803011064, isValidForDataType:true, data:[01, FF, 42, 2B, 64, 10, 01, 03, 28, 24, 98, 39, D7, A3, 80, 40, 95, 39, 02, FF, F8, 42, 05, 21, 3B, 00, 9A, 20, 00, 08, 21, 22, 13, 07, 27, 00, 00, 00, 00, 00, 00, 00, 00, 09, 21, 02, 05], clusterInt:0, attrInt:65281, commandInt:10], event:[:]
6f5ddaf2-6176-4c1e-9048-51a63c43184b 17:35:51: warn java.lang.StringIndexOutOfBoundsException: String index out of range: 87
Hi @iwry ,
The log you provided doesn’t look like it was sent by Tuya compatible device.
It looks very like as Aqara/Xiaomi.
Are you sure you are providing the logs for the correct device?
Could it be the switch is rebranded Aqara?
Anyway, the device that reports
description:catchall: 0104 0000 01 01 0000 00 0BE7 00 01 115F 0A 01
and sends
attrId:FF01 under cluster 0000 will not work with TS0601 DHT.
You are welcome to try Aqara’s DHT from my repo, it might work
Here is the product link:
And the zigbee join message:
zbjoin: {"dni":"786B","d":"5C0272FFFE249CAC","capabilities":"80","endpoints":[{"simple":"01 0104 0051 01 04 0000 0004 0005 EF0...
</a>
You are correct, it wasn’t detected by the handler and needed to configure it to your device handler.
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:54 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 24 01 0004’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 24 01 0004, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[00, 04], clusterInt:61184, commandInt:36]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:54 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 24 01 0004’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 24 01 0004, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[00, 04], clusterInt:61184, commandInt:36]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:42 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 000A0F04000102’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 000A0F04000102, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 0A, 0F, 04, 00, 01, 02], clusterInt:61184, commandInt:1]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:42 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00090E04000100’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00090E04000100, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 09, 0E, 04, 00, 01, 00], clusterInt:61184, commandInt:1]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:42 AM: debug handleSwitchEvent(): EP=2 value=0 children=[0, 0, 0, 0, 0, 0] main=0
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:42 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00080201000100’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00080201000100, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 08, 02, 01, 00, 01, 00], clusterInt:61184, commandInt:1]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:34 AM: debug handleSwitchEvent(): EP=2 value=1 children=[1, 1, 0, 0, 0, 0] main=2
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:34 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00030201000101’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00030201000101, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 03, 02, 01, 00, 01, 01], clusterInt:61184, commandInt:1]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:34 AM: debug handleSwitchEvent(): EP=1 value=1 children=[1, 0, 0, 0, 0, 0] main=1
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:49:34 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00020101000101’ descMap is [raw:0104 EF00 01 01 0000 00 786B 01 00 0000 01 01 00020101000101, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 02, 01, 01, 00, 01, 01], clusterInt:61184, commandInt:1]
I believe I am using the version that was provided to Kostas as I clicked on the link that you gave in your reply to his message.
Here is the live logging (Switch now using your device handler) when I try to turn off the Parent but no reaction in ST (remains on):
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:56:46 AM: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 786B 00 00 0000 0B 01 0000’ descMap is [raw:0104 EF00 01 01 0000 00 786B 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:786B, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00], clusterInt:61184, commandInt:11]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:56:46 AM: debug sendCommandsToDevice(): delay=500 cmds=[st cmd 0x786B 0x01 0xEF00 0x00 {00090d01000100}, delay 2000] actions=[st cmd 0x786B 0x01 0xEF00 0x00 {00090d01000100}, delay 2000]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:56:46 AM: debug createTuyaCommand(): dp=0d type=01 len=0001 value=00 → cmd=[st cmd 0x786B 0x01 0xEF00 0x00 {00090d01000100}, delay 2000]
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:56:46 AM: debug parentOnOff()… false 786B
f6ad4cdb-e2a3-4541-9c54-5397a468a627 4:56:46 AM: debug off()…
Hi @Ed_Cayetano
The zigbee join message is truncated, I need to see the complete message, including the model.
As alternative, I can try to fix the issue, based on complete Raw device info, which can be found in IDE screen of your device.
The log
createTuyaCommand(): dp=0d type=01 len=0001 value=00 → cmd=[st cmd 0x786B 0x01 0xEF00 0x00 {00090d01000100}, delay 2000]
Clearly shows the handler tries to send a single message to all gangs when using parent, this is not supported by Moes devices, but is used by some Tuya compatible devices.
Do you have logs when child devices stoped working? I don’t see any messages sent from child devices.
Thanks
Sorry, when I do a paste I think the text has HTML code that truncates it, which I really don’t know much about 
. I remove the “<” , I think this is better:
a class=“tooltip-init” title=“” data-toggle=“tooltip” data-original-title=“zbjoin: {"dni":"786B","d":"5C0272FFFE249CAC","capabilities":"80","endpoints":[{"simple":"01 0104 0051 01 04 0000 0004 0005 EF00 02 0019 000A","application":"42","manufacturer":"_TZE200_g1ib5ldv","model":"TS0601"}],"parent":0,"joinType":0,"joinDurationMs":1330,"joinAttempts":1}”>
zbjoin: {"dni":"786B","d":"5C0272FFFE249CAC","capabilities":"80","endpoints":[{"simple":"01 0104 0051 01 04 0000 0004 0005 EF0...
</a>
Unfortunately no. I did not notice it earlier that it wasn’t working anymore.
Thanks Yakov.
Hi @ygerlovin,
Please disregard the log, the deviceId 7b8596ad-0e5c-4067-8773-b14ba268d7db is a Xiaomi Zigbee plug that I have. My mistake.
My switch is exactly the same as the one Ed_Cayetano has. MoesHouse Zigbee switch Version ZTS-US2-W
Please try the following version for the main (parent) device
https://bitbucket.org/yashik_gt/smartthings/src/moes-2-gang/SmartHome4U/TS0601.groovy
This version adds support for Moes 2 gang switch with ‘_TZE200_g1ib5ldv’ signature.
If it works fine, I will merge it into the master branch.
Please note,
This version does not contain changes for child DNI updates as it seems they are not always working. I will need to think about other solution, once I get more logs from people.
Cheers,
Yakov
Thanks @ygerlovin.
For the child device handler - I’ll just leave it as it is for now?
Right, there were no changes in the child DHT
I tried to remove and add the switch again but I couldnt see any zbjoin event 
Switch on and then switch off the child:
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:50: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 9575 00 00 0000 0B 01 0000’ descMap is [raw:0104 EF00 01 01 0000 00 9575 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:9575, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00], clusterInt:61184, commandInt:11]
85115249-393d-4c64-bb37-c2c3575f16b5 19:03:50: debug Event data successfully posted to SharpTools.io
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:50: debug handleSwitchEvent(): EP=2 value=0 children=[0, 0, 0, 0, 0, 0] main=0
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:50: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00080201000100’ descMap is [raw:0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00080201000100, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:9575, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 08, 02, 01, 00, 01, 00], clusterInt:61184, commandInt:1]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:49: debug sendCommandsToDevice(): delay=300 cmds=[st cmd 0x9575 0x01 0xEF00 0x00 {00080201000100}, delay 2000] actions=[st cmd 0x9575 0x01 0xEF00 0x00 {00080201000100}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:49: debug childOnOff(): endPoint=2 turnOn=false cmds=[st cmd 0x9575 0x01 0xEF00 0x00 {00080201000100}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:49: debug createTuyaCommand(): dp=02 type=01 len=0001 value=00 → cmd=[st cmd 0x9575 0x01 0xEF00 0x00 {00080201000100}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:49: debug child off: [label:Luz habitación 1, deviceNetworkId:9575-SW2] parent=[name:Thing habitación]
85115249-393d-4c64-bb37-c2c3575f16b5 19:03:42: debug Event data successfully posted to SharpTools.io
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:41: debug handleSwitchEvent(): EP=2 value=1 children=[0, 1, 0, 0, 0, 0] main=1
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:41: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00070201000101’ descMap is [raw:0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00070201000101, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:9575, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 07, 02, 01, 00, 01, 01], clusterInt:61184, commandInt:1]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:41: debug handleSwitchEvent(): EP=2 value=1 children=[0, 1, 0, 0, 0, 0] main=1
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:41: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00070201000101’ descMap is [raw:0104 EF00 01 01 0000 00 9575 01 00 0000 01 01 00070201000101, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:9575, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 07, 02, 01, 00, 01, 01], clusterInt:61184, commandInt:1]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:41: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 9575 00 00 0000 0B 01 0000’ descMap is [raw:0104 EF00 01 01 0000 00 9575 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:9575, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00], clusterInt:61184, commandInt:11]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:40: debug sendCommandsToDevice(): delay=300 cmds=[st cmd 0x9575 0x01 0xEF00 0x00 {00070201000101}, delay 2000] actions=[st cmd 0x9575 0x01 0xEF00 0x00 {00070201000101}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:40: debug childOnOff(): endPoint=2 turnOn=true cmds=[st cmd 0x9575 0x01 0xEF00 0x00 {00070201000101}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:40: debug createTuyaCommand(): dp=02 type=01 len=0001 value=01 → cmd=[st cmd 0x9575 0x01 0xEF00 0x00 {00070201000101}, delay 2000]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:40: debug child on: [label:Luz habitación 1, deviceNetworkId:9575-SW2] parent=[name:Thing habitación]
7b8596ad-0e5c-4067-8773-b14ba268d7db 19:03:40: debug child on: [label:Luz habitación 1, deviceNetworkId:9575-SW2] parent=[name:Thing habitación]
19:03:21: info Waiting on events…
19:03:21: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.
19:03:21: info This console provides live logging of your SmartThings.
Then I removed the switch from ST and added again:
85115249-393d-4c64-bb37-c2c3575f16b5 19:07:18: debug getDevices, params: [appId:85115249-393d-4c64-bb37-c2c3575f16b5, param1:devices, action:[GET:executeSmartAppGet, POST:executeSmartAppPost, PUT:executeSmartAppPut, DELETE:executeSmartAppDelete, OPTIONS:executeSmartAppOptions], controller:smartAppApi]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:38: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:38: debug updated called
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:35: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:35: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:35: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:35: debug scheduled run, numberOfRuns: 6
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:35: trace in discovery
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:28: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:28: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:28: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:28: debug scheduled run, numberOfRuns: 5
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:28: trace in discovery
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:21: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:21: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:21: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:21: debug scheduled run, numberOfRuns: 4
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:21: trace in discovery
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:14: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:14: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:14: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:14: debug scheduled run, numberOfRuns: 3
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:14: trace in discovery
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:07: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:07: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:07: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:07: debug scheduled run, numberOfRuns: 2
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:08:07: trace in discovery
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:07:59: debug No devices to add, verified devices: [:]
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:07:59: debug detecting status for 2f978ac1-b618-4797-bbc3-c651b82c9436 : true
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:07:59: trace in ssdpDiscover
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:07:59: debug scheduled run, numberOfRuns: 1
2acdb00b-5cfa-4973-88bc-ba825f9af12f 19:07:59: trace in discovery
Thing was created, then I change the type to TS0601 Relay:
32e295c2-387e-4940-98ea-23a438c4457a 19:09:37: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 36E8 00 00 0000 0B 01 0000’ descMap is [raw:0104 EF00 01 01 0000 00 36E8 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:36E8, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00], clusterInt:61184, commandInt:11]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:35: info parse(): description is ‘catchall: 0104 EF00 01 01 0000 00 36E8 00 00 0000 0B 01 0000’ descMap is [raw:0104 EF00 01 01 0000 00 36E8 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:36E8, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00], clusterInt:61184, commandInt:11]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug sendCommandsToDevice(): delay=300 cmds=[st cmd 0x36E8 0x01 0xEF00 0x00 {00016501000100}, delay 2000, st cmd 0x36E8 0x01 0xEF00 0x00 {00021001000100}, delay 2000] actions=[st cmd 0x36E8 0x01 0xEF00 0x00 {00016501000100}, delay 2000, st cmd 0x36E8 0x01 0xEF00 0x00 {00021001000100}, delay 2000]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug createTuyaCommand(): dp=10 type=01 len=0001 value=00 → cmd=[st cmd 0x36E8 0x01 0xEF00 0x00 {00021001000100}, delay 2000]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug createTuyaCommand(): dp=65 type=01 len=0001 value=00 → cmd=[st cmd 0x36E8 0x01 0xEF00 0x00 {00016501000100}, delay 2000]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug updateChildrenDNI: child = 36E8-SW2[name:TS0601 Relay Child]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug updateChildrenDNI: child = 36E8-SW1[name:TS0601 Relay Child]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug updateChildrenDNI()… children=2
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug createRemoveChildDevices()… gangs=2 children=2 device=[label:Thing habitación, deviceNetworkId:36E8]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug updated()… device=Thing habitación settings=[:] DNI=36E8
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug childUpdated: Thing habitación-SW2 vs null
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug childUpdated(36E8-SW2) for device=[label:Thing habitación, deviceNetworkId:36E8]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug Creating SW2 Child Device device=Thing habitación
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug childUpdated: Thing habitación-SW1 vs null
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug childUpdated(36E8-SW1) for device=[label:Thing habitación, deviceNetworkId:36E8]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:32: debug Creating SW1 Child Device device=Thing habitación
32e295c2-387e-4940-98ea-23a438c4457a 19:09:32: debug updateChildrenDNI()… children=0
32e295c2-387e-4940-98ea-23a438c4457a 19:09:32: debug createRemoveChildDevices()… gangs=2 children=0 device=[label:Thing habitación, deviceNetworkId:36E8]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:32: debug installed()… DeviceId : 32e295c2-387e-4940-98ea-23a438c4457a, 36E8 manufacturer: _TZE200_g1ib5ldv, model: TS0601 settings=[:]
32e295c2-387e-4940-98ea-23a438c4457a 19:09:33: debug child installed: Thing habitación-SW2
32e295c2-387e-4940-98ea-23a438c4457a 19:09:32: debug child installed: Thing habitación-SW1
Just to clarify - I’m supposed to use both the Relay and Child device handlers in the link you sent me? I saw there are 2 files in the moes-2-gang branch. (I was using the files for Kostas)
Sorry I’m just learning about github / bitbucket now and their folder / branch structures.
@iwry
Could you please provide zigbee join message for your device?
Device even from the same seller might come from different batches with sl8ghtly different firmware.
For your issue, I will need the logs that show the request (backlight of) and the response to this command and also several button pressing afterwards, if the device stops working.
Thanks