Closed Magnus-rosenborg closed 3 weeks ago
Publishing payloads with POWER
has nothing directly to do with what button is being pushed, but is instead about what relay is changing state. But indirectly, the default action for button/switch inputs is to toggle power.
You are not creating any relationship between buttons and relays by the number, the only thing that matters is the sequence, and indexes you assign per component type has to start at 1, and not skip any numbers.
SetOption114 (which is for Switch inputs) is not doing anything when inputs are configured as a Button, that would be SetOption73.
If you've been messing around with ButtonTopic
, better not do that, without fully understanding this specialized command. In fact, I'd recommend going back to initial configuration, and not heaping different config options on top on each other. Your mixup of topics with KNAPP37 and just 37 also looks like your config is too much combination of attempts of doing something.
PROBLEM DESCRIPTION
A clear and concise description of what the problem is. My device is a sonoff touch wall switch with 3 buttons. ( T1EU3C) I have tried the template for it and also setting it by myself using the generic template. The problem is that it sends POWER1 on every button shoudn't it be POWER2 for button 2 end so on? See the image for more details.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior: I have tried to have button 1,2,3 and like 4,5,6 no difference. Even when detach buttons using SO114 still sends mqtt like power1 1 on button 4. So strange!!! It works fine in gui. But not the touch buttons.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen. if button 4 is pressed should send power4 1 or power4 0
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
![image](https://github.com/arendst/Tasmota/assets/49500329/95e9a13c-4cd5-42ba-bc78-4ef612ab11e3)
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)