Hi - yes that is the same as the _TZ3000_xabckq1v I am testing with, and which I am having difficulties getting to work properly.
(Pic of other device to follow later)
Hi - yes that is the same as the _TZ3000_xabckq1v I am testing with, and which I am having difficulties getting to work properly.
(Pic of other device to follow later)
@trakker2 Thanks for all your hard work on this DTH.
I have a MOES 4-panel wireless switch, seems to be the Tuya that’s in this thread, picking up the _TZ3000_xabckq1v / TS004F identity.
I paired it, changed the device to use the DTH, and used the 2/4 button reset to get it to scene mode. Using the 2.6 version of the handler, only button 1 shows up in Live Logging. The other buttons do not respond.
Thoughts?
Hi @ssbn ,
Just changing the DHT is not enough to successfully initialize TS004F wireless switch into a scene control mode. After switching to this DHT, you need to re-pair the device.again , because it can be initialized into scene control mode only during the short time period (7-8 seconds) while it joins the zigbee network. The most effective way is to first delete it (from ST mobile app : device details page → Edit → Remove device ). At the time when you delete it, press button 1 to make sure the device wakes up and leaves the zigbee network. I recommend also removing the battery for about 1-2 minutes to make sure it loads factory defaults settings.
Then from the mobile app add new device ( “+”, “scan nearby” ). Put TS004F into pairing mode by holding the left bottom button for 6-7 seconds. Perform the pairing close to the ST hub, this reduces the possibilities for communication errors and packets retransmissions, respectively increasing the chances to successfully complete the initialization process. An indication of successful pairing is when all 4 LEDs stop flickering in about 4-5 seconds after the pairing process was started.
I have just updated the driver to version 3.0. It adds support for the new YSR-MINI-Z remote controls and also supports the default ‘Dimmer mode’ From the Groovy IDE device details page you can check what is the currently operational mode (“Scene” or “Dimmer” ).
I hope that I have also optimized the pairing timings a bit more in the new version 3.0. Please update the DHT and let me know if it works for you.
All buttons now register all actions however i cannot assign actions to buttons 3,4 and 5.
Have you tried the ABC - Advanced Button Controller - Newest Edition ?
I’m new to that - how can that help?
The Advanced Button Controller was one of the few custom applications that in the last weeks were able to make use of the multiple buttons controllers… until yesterday!
Samsung have finally managed to fix the long-lasting bug in SmartThings mobile app, and now it is possible to assign different simple actions (routines) from the mobile app device page:
Check Google or Apple stores on your mobile device to make sure you have the mobile app updated to the latest version.
Ive finally managed to setup in smartthings with a device handler 1.6 but press any button & nothing happends , if i add a routing to Button 1 nothing happens, if i setup a routine in any other button they dont even show up? Hope someone can help
Can you post the device details as shown in the Groovy IDE, ‘My devices’ tab?
Should be something like this:
Although SangBoyST original driver should also work with TS004F model devices, providing single button push events for the left buttons and single+held events for the right buttons, I would recommend to try the modified version here:
Steps:
Let me know if this procedure works for you. You can also observe the Groovy IDE ‘Live logging’ page for any debug / log messages that are shown when you press any of the buttons. If the device still does not work for you, copy and paste the logs and send them to me. Good luck!
Many thanks, ive tried again & yes that worked but when i add to button 2,3 or 4 even though thwy work nothing shows up in under Press, Double press or Held?.
That’s the SmartThings mobile app bug in action…
Make sure you are using the latest app version:
(Menu → Gear icon → ‘About Smartthings’ :
This is the Android version as on 19th of December 2021 :
This is exactly the ST bug that was fixed recently. Make sure you have the latest mobile app version installed on your mobile device. In the device page should see only 4 sections for the 4 buttons and the battery status on the bottom. If you still see 5 sections ( a common Pressed/Double/Held section on the top, followed by 4 individual buttons similar sections) - then you are using an old mobile app version.
Thanks. Works well now! Let’s see how the battery holds up.
I’m also trying to put this scene switch to work, but no success. Only the button 4 (TL) works properly and also, in the app, is shown 5 buttons, main and 1 to 4. Only the main button accepts automations and it’s triggered by the button 4.
@anthonyceegp did you follow all the steps in this post: Four button Tuya Zigbee device DTH (DTH link in post #7) (Same device from multiple brands: Zemismart, Yagusmart, Losonho , DYHF, etc) - #113 by Trakker2 ? Please make sure you are not skipping a step.
Also, seems like you are not using the latest SmartThings mobile app, please update it from Google or Apple stores.
@Trakker2 Thank you very much for sharing DTH.
I’m looking at your DTH to try to port it to edge.
Could you please clarify what the following line means?
"raw 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}", "send 0x${device.deviceNetworkId} 1 1", "delay 200",
"raw 0x0000 {10 00 00 04 00 20 00 21}", "send 0x${device.deviceNetworkId} 1 1", "delay 50",
Also, what is the attribute 0xD011 under 0xE001 cluster?
Thank you
Hi @ygerlovin , thank you for your efforts in making an Edge driver!
These two commands are reading a set of attributes in single commands, matching exactly the way that Tuya Zigbee gateway does it. Mimicking the Tuya initialization sequence is the key point to successfully initialize the TS004F device in Scene control mode.
The same lines of code for Hubitat look this way :
cmd += zigbee.readAttribute(0x0000, [0x0004, 0x000, 0x0001, 0x0005, 0x0007, 0xfffe], [:], delay=200) // Cluster: Basic, attributes: Man.name, ZLC ver, App ver, Model Id, Power Source, Unknown 0xfffe cmd += zigbee.readAttribute(0x0006, 0x8004, [:], delay=50) // success / 0x00 cmd += zigbee.readAttribute(0xE001, 0xD011, [:], delay=50) // Unsupported attribute (0x86) cmd += zigbee.readAttribute(0x0001, [0x0020, 0x0021], [:], delay=50) // Battery voltage + Battery Percentage Remaining cmd += zigbee.writeAttribute(0x0006, 0x8004, 0x30, 0x01, [:], delay=50) // switch into Scene Mode ! cmd += zigbee.readAttribute(0x0006, 0x8004, [:], delay=50)
It is important to send the readAttribute commands for the Basic and Power clusters at once. Sending individual readAttribute commands for each attribute didn’t work.
This attribute is actually not used in the driver logic any further, but reading it is required for the successful initialization of the device.
It is also important to send the initialization sequence quickly, hence the very aggressive low-value delays between the readAttributes commands.
Good luck, I am eager to test the Edge driver!
@ygerlovin
Thanks for developing that driver ,in case you need it , i have that device i can test it , i can give you logs from cli