Tagging @erickv @Mariano_Colmenarejo @zambobmaz Thanks in advance!
Added and applied (2025-05-01T11:36:10.717952179)
1 Like
Thank you Zambobmaz! I was previously running this button on your driver but the battery would only last for a few days max. Could that have been a result of it not being added yet?
The driver doesn’t need futher modification because it’s simply displaying the battery value reported by the device. Especially in the case of low-cost devices like tuya, the battery readings are often inaccurate.
Thank you for your reply, I’m not concerned about the battery indicator but the actual battery is dead within 2-3 days and the button no longer works until you replace the battery again.
If you’re referring to battery drain, this part remains a mystery to me as well. It wasn’t an issue when using DTH in the past, so it seems to be a software or Edge-related problem rather than a hardware one. I’ve tried various tests to resolve the battery drain but haven’t been able to pinpoint a clear cause. I reinstalled the same driver, replaced batteries with different brands, added and removed repeaters, but even with identical devices, sometimes the issue occurred and sometimes it didn’t. Other developers also don’t seem to know the exact cause of this. (If you come across any related posts, please do share them.)
1 Like
Hi! @erickv
I bought ZigBee 1 and 3 buttons from AliExpress, but 3 buttons are supported, but 1 button is not supported, so could you add it? Please understand that the sentence is not natural using a translator. The device I use is the device below.
id: “_TZ3000_vn88ezar/TS0041”
deviceLabel: “Scene Switch”
manufacturer: “_TZ3000_vn88ezar”
model: “TS0041”
deviceProfileName: button-battery
Should work with @zambobmaz driver. Give it a try. His channel is here:
Hi, sorry for the delay
I’ve applied the update you required.
As for the grouping, that’s a configuration that should be set from the device settings page (aka preferences). Select Dimmer mode and re-add the device to set the configuration on the device’s server.
Now!.. if it doesn’t work and the device keeps working as a in Scene mode, then is a firmware thing. I had the same experience with a 4-scene MOES button, the very same referred at the title of this topic.
What happened is that my first device had support for both modes, but years later, the same model had a different firmware removing support for the Groups cluster.
Pros:
- Removed trigger delays between consecutive presses
Cons:
- No more Groups support…
- Increased energy consumption, even on highest state refresh rate
I cannot tell if theres more, but certainly that’s how it feels measuring so far.
The same thing happens with my devices. After a year or so they keep reporting between 100 and 80, and months ago some of them began blinking a lot reporting 80s… so, battery measurement is just odd.
I havent pushed and update regarding the battery measurement given the nature of the devices reporting low battery around 2 months before running out of battery.
Hi everyone,
I’ve added a few new fingerprints under the latest version, so there’s no need to adjust anything on your end.
Thank you all for the support and interest on this driver.
Thanks @erickv .
Eventually i figured out that a repairing was needed after changing to dimmer mode, in order to group control start working. Im using the knob to directly control a gledopto smart bulb, working very well. The knob could be more responsive, with less delay, but this is the device design.
Works perfectly, Thank You!
2 Likes
Do you experience any behavior other than delays? Mine just stops working after a few tries and shot the light off.
This may be due to the fact that the knob sends an event on every click it has, so half of a twist may be sending 50 events in less than a second… probably, this is just an empirical guess.
I assume there’s a server configuration to debounce such interactions, but I haven’t seen any manual out there other than the clusters info… or probably your device shows such debouncing
feature to keep the server alive.
Have a great day!
No other behaviors. Working fine since added.
Reading through home assistant forums, it seems that the device identify the “speed” of the knob twist and react accordingly, for example: if rotated slowly will send 1 message every click with a lower step level, but if rotated rapidly will send a message every 3 ou more clicks with a greater step.
This direct communication is ZLL protocol, so your bulb needs to support that.
1 Like
That’s interesting, I’ll take a look at the specs of the bulbs just in case.
Thanks Marcos
manufacturer: “_TZ3000_zgyzgdua”
model: “TS0044”
It is recognized as a switch and cannot work. Please help.
1 Like
You open issue in @zambobmaz GitHub and he will add to his driver:
1 Like
I added (2025-05-24T13:09:21.810675115)
1 Like
