Add DDF + Button Map for _TZ3000_ja5osu5g Tuya Smart Button #6977
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My Try at a DDF for a smart button I recently bought:
https://de.aliexpress.com/item/1005005238316199.html?spm=a2g0o.order_list.order_list_main.11.49a15c5fjVVmas&gatewayAdapt=glo2deu
This is a single button, battery powered (button cell).
The button has two modes, you can switch between them by 3xPressing the button very fast.
Scenario Mode
Single Press
Double Press
Long Press
I added the button events for this mode. They are working very reliable.
Remote Mode
Not very much info yet.
Single Press to turn on, double to turn off.
When on: press and hold to dim.
It seems to increase, then decrease and cycle again.
I was not able to identify a "start" event for dimming, although a "LEVEL_CONTROL STOP" event was sent.
Single press when on: Seems to cycle between 4 Presets of Level & Color Control based on the received button events (When on) I have no dimmable light to test this using a direct binding.
Could also just be some kind of Tuya-Magic.
The button can be bound directly to a plug to control on/off (tested)
Notes
Testing is quite challenging. When playing aroung with bindings, I managed to put the button in some kind of state, that prevented the mode switch by 3x pressing the button.
Even after re-pairing this state remained.
Only after I brute-force played around with the unbinding in the GUI I managed to revert it backt to its initial behaviour.