Hello? kkossev
"Switch-type button" among Sihas products in Korea
I want to use (SBM-300-ZB)
I can't find the right driver.
Can you check the driver?
Hi @user6226 , I will look at this device as soon as my time permits in the next few days.
@ moderators, can you move this and the post above to this thread, please?
3 Likes
Hi @user6226 ,
You can manually update the driver to version 2.8.1, '2025/01/12 9:09 AM'. I have added - added SiHAS models SBM300Z2, SBM300Z3, SBM300Z4, SBM300Z5, SBM300Z6, ISM300Z3.
https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20TS004F/TS004F.groovy
Click on the Configure () command.
Can you post a screenshot of the debug logs that follow pressing a button?
Been trying to get my new Tuya Scene Switch working. I think I have it paired correctly, but it doesn't generate any events.
Here's a minute or two of logs if that helps. I've tried a number of things, but I'm stumped. Thanks!
Did you click the configure button after pairing the switch while clicking one of the buttons to "wake it up"
On the commands tab of the device page you should see something like this:
On the device info page make sure the "Type" is what is shown below:
Pretty much looks the same. I put it in pairing mode and the hub saw it. All I see in the logs relates to button 0.
I appreciate the input though.
I did not see a match for the Manufacturer code "_TZ3000_5tqxpine" in the driver so the driver does not know the specifics of your switch.
You can try adding a new fingerprint to the driver with the manufacturer code in it.
1 Like
I have added this new device fingerprint in the driver update version. 2.8.2 2025-05-04 (also pushed via HPM). However, I am not quite sure this will solve the problem, this device is a new one (not supported in HA ZHA/Z2M yet) and it has some 'specifics' different than the other similar Tuya 4-button scene switches.
Please update the driver first, then delete the device (use the red REMOVE button in the Device Info tab). Then pair the device again with your HE hub.
Will this driver be selected automatically?
Will the device stay connected for more than 1-2 minutes? Enable the Debug logging and observe the live logs. Will a key press produce anything in the logs a few minutes after the initial pairing?
1 Like
Selected automatically!
Still online 10 minutes later.
Sadly, no. Nothing in the logs now.
Puked out nearly 200 lines in the logs before going quiet. I'll paste the first few lines and the last few lines here.
I wish there was a better way to export logs. But I hope that helps. Thanks. I bought this switch super cheap on a lark hoping it would work. But also knowing that AliExpress is a crapshoot.
Here's a pic of the switch and box in case that's of any help.
Thanks for your efforts and let me know if you need anything from me.
Best,
Jay
2 Likes
Thank you for the logs and for the tests Jay, now I see where the problem is :
This is very unusual and non-standard behaviour (a Zigbee end-device to send 'Active Endpoint Request' (0x0002) to the hub, and because we see these requests in the debug logs, obviously the HE hub is not handling them on a system/platform level...
Don't throw away this device yet, I will try to make a patch, although I can't promise a quick timing.
1 Like
Just as a comment, I was going to buy that style (4 button) but opted to stay with this style and haven't had any issues, YMMV. They have the case ridge around the perimeter of the switch. I have bought all my mine (~10) from Aliexpress, the seller was IHSENO (no endorsement though).
2 Likes
Thatโs also the one I use and it works great.
1 Like
Just to note that this driver also works with this 4 button Zigbee switch, Zenismart ZRM4.
https://www.amazon.com/dp/B0F1CJ6DHT
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0006", outClusters:"0019,000A", model:"TS0044", manufacturer:"_TZ3000_xwuveizv", controllerType: "ZGB"
ZCL version:03
Model:TS0044
Manufacturer:_TZ3000_xwuveizv
The device did pair initially with the built-in 'Tuya ZigBee Scene Switch' driver, but that didn't report battery.
3 Likes
Okay. So it took like 6 weeks to get here, but still no joy. Is this the wrong one? Should it work. It pairs but then I don't get events.
Errors:
Actually, I think I was looking at "past logs." Tap and Double-Tap work. I guess there's no "hold" for this device?
I have a personal general rule to pair every Tuya based device twice. They seem to pair the first time, but not all features are available. So I pair the first time, select my preferred driver, hit โconfigureโ, then pair a second time without deleting the device.
This has worked well with me with Tuya buttons, temperature and humidity sensors, contact sensors, gas sensors, leak sensors, motion sensors, etc.
3 Likes
When you click the configure button in the HE driver, you also need to press one of the buttons (within 1-2 seconds) on the scene switch to "wake it up" so it will receive the proper config from the HE driver.
I usually press the pairing button.
Most if not all battery powered IOT devices go into a sleep mode (to conserve power) within a very short time after they generate any activity. Button presses, sensor readings, etc. They wake up, send the report to HE, then got to sleep. Any messages from HE will not be heard by the device (and acted on by the device) unless it is awake.
