Tasmota: second button on Sonoff T1 2ch not working (sonoff.bin)

[joggs]

Second button on Sonoff T1 2ch touch panel is not working using the dev builds of sonoff.bin (as of 190211) for 2.4.2 and 2.5.0 , 6.4.1.
The release version of 6.4.1 works well.
the second button works well from the web ui, but not if you push the button on the panel.

_Also, make sure these boxes are checked [x] before submitting your issue - Thank you!_

• [x ] _Searched the problem in issues and in the wiki_
• [ ] _Hardware used_ : Sonoff T1 2ch
• [ ] _Development/Compiler/Upload tools used_ : webui
• [ ] _If a pre-compiled release or development binary was used, which one?_ :
• [x ] _You have tried latest release or development binaries?_ : release works, deve does not
• [ ] _Provide the output of command_status 0 :

To Reproduce
_Steps to reproduce the behavior:_
install devbuilds of sonoff.bin for 2.4.2 or 2.5.0 and the second button does not work if you push the touchplate. It works well in the web ui.

[ascillato]

Hi,

Can you confirm if that button was working with the original firmware?

Can you confirm if there is no wire loose inside the module?

You can also try to check if the gpios are the same as the template for that module. Sometimes happens that a device is not original and it does not have the same pinout.

Also remember that for support it is available the Tasmota Support Chat for live Support.

[wongnam]

My Sonoff T1-US 2CH is working normally on 6.4.1.15 core 2.4.2
Make sure that you are selecting Sonoff T1 2CH (29) in Module parameters.

[tompipe]

Ensure SetOption51 is enabled

[joggs]

@ascillato yes, the button worked with the original fw and also with the current release version. No wire is loose. Also, the button still works with the problematic fw if i click it from the web gui. It is just the physical button on the touch panel that stopped working after the update to the problematic fw.

I actually have 2 T1 2ch and they both stopped working after the fw update. I also updated a T1 1ch and that works.

@wongnam Yes Sonoff T1 2CH (29) is selected

@tompipe I will try option 51 after work today. How will that change affect the T1 ? The explanation says "Enable to view extra pins for ESP8285 in Module", but I do not understand it in this case :-)

Also, these T1's are the 'new' revision where you had to ground r19 in addition to the original procedure, to be able to get into flash mode. Not sure if that could be a cause of the problem, new archticture etc?

I rolled back the fw last night as I needed the switches to work and then everything works well again.

[ascillato2]

Please, try the new version from today from the development branch. Thanks

[joggs]

The same problem with 20190212 - http://thehackbox.org/tasmota/020500/sonoff.bin

[ascillato2]

Have you erased all flash with esptool.py as explained in the wiki and then flashed the firmware?

Because the firmware is working fine for that device, so we have to find where is the misconfiguration in yours.

[joggs]

yes. i have tried the first time on web interface and after that with esptool.py including erase

[joggs]

Strange indeed. The 2.3.0 version is the most stable for me, also no connection drops. I can always roll back to that one, but I am curious to see if the 2.5 version has a more stable wifi connection than 2.4 that has given me lots of connection drops, but that is a separate issue.
Strange if this version is working for other peoples T1 2ch? Could there be a different hardware revision so that a matching template is not found? I guess that would give problems with the older versions if that was the case, but they are working.

Here is my status 0

20:02:44 RSL: stat/sonoff/STATUS = {"Status":{"Module":29,"FriendlyName":["Sonoff","Sonoff2"],"Topic":"sonoff","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
20:02:44 RSL: stat/sonoff/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/release/sonoff.bin","RestartReason":"Power on","Uptime":"0T00:08:04","StartupUTC":"2019-02-12T18:54:40","Sleep":50,"BootCount":12,"SaveCount":66,"SaveAddress":"FA000"}}
20:02:44 RSL: stat/sonoff/STATUS2 = {"StatusFWR":{"Version":"6.4.1.16(e779c7b-sonoff)","BuildDateTime":"2019-02-12T17:12:11","Boot":31,"Core":"2_5_0","SDK":"3.0.0-dev(c0f7b44)"}}
20:02:44 RSL: stat/sonoff/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["dd-wrt12",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","280500000100000000000000000000000000","00000000"]}}
20:02:44 RSL: stat/sonoff/STATUS4 = {"StatusMEM":{"ProgramSize":556,"Free":444,"Heap":22,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashMode":3,"Features":["00000809","0FDAE794","000783A0","23B617CE","00003BC0"]}}
20:02:44 RSL: stat/sonoff/STATUS5 = {"StatusNET":{"Hostname":"sonoff-3650","IPAddress":"192.168.0.143","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.0.1","Mac":"","Webserver":2,"WifiConfig":1}}
20:02:44 RSL: stat/sonoff/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_DEAE4242","MqttUser":"DVES_USER","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
20:02:44 RSL: stat/sonoff/STATUS7 = {"StatusTIM":{"UTC":"Tue Feb 12 19:02:44 2019","Local":"Tue Feb 12 20:02:44 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+01:00","Sunrise":"08:03","Sunset":"18:05"}}
20:02:44 RSL: stat/sonoff/STATUS10 = {"StatusSNS":{"Time":"2019-02-12T20:02:44"}}
20:02:44 RSL: stat/sonoff/STATUS11 = {"StatusSTS":{"Time":"2019-02-12T20:02:44","Uptime":"0T00:08:04","Vcc":4.466,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"dd-wrt12","BSSId":"","Channel":8,"RSSI":100}}}

[ascillato2]

Could there be a different hardware revision so that a matching template is not found?

The internal Tasmota template of gpios config for that device was not changed.

[wongnam]

@joggs Use serial to erase the flash with esptool.py and then flash it direct from the latest fw with core 2.4.2. You will see the different.
Note: as i have experienced that don't flash 2.3.0 and upgrade to 2.4.2, to do so i am not sure it will stable with some hw.
Update: i use VSC+PlatformIO to compile and flash

[joggs]

I have tried all different versions now and performed eraseflash + serial flash with all mentioned tools and I still have the same problem with the second button that seems to have appeared somewhere after the the release of the current release version and I get this on 2 different T1 2ch units.
I have rolled back to 2.30 and that version works perfectly, so I will continue to use that version.
Strange indeed. I am not new to flashing and firmware tweaking so I am pretty certain that I have done everything correctly.
There must be a change in the code between the release version and current version that broke the functionality for my units/revisions.

[Jason2866]

It has to be Arduino Core related if it works with Core 2.3.0.

I have rolled back to 2.30 and that version works perfectly, so I will continue to use that version.

Tasmota "hooks up" on the Core. There is no general change in code of Tasmota if you use Core 2.3.0, 2.4.2 or 2.5.0 (only a few conditional bug fixes for the core...)
You can compile latest dev Tasmota with Core 2.3.0. You will get latest Tasmota version.

[wongnam]

@joggs I can replicate your T1-US 2C issue with latest develop version 6.4.1.17 core 2.4.2. The 2nd touch button no working. the soft buttons in Web-UI are still working well.

• I can confirm that the 6.4.1.15 is working well for all touch button on T1-US 2C

@ascillato please consider this case is an issue and have an investigate. Thanks.

Update: version 6.4.1.17 core 2.4.2 even the T1-US 3C is still no working for the 2nd and 3rd touch button.

My status 0:

21:34:35 CMD: status 0
21:34:35 MQT: stat/groundfloorlight1/STATUS = {"Status":{"Module":30,"FriendlyName":["Ground Floor Light 1","Front Yard Light","Ground Floor Balcony Light"],"Topic":"groundfloorlight1","ButtonTopic":"","Power":4,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"SwitchTopic":"","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
21:34:35 MQT: stat/groundfloorlight1/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/release/sonoff.bin","RestartReason":"Software/System restart","Uptime":"0T00:11:06","StartupUTC":"2019-02-15T14:23:29","Sleep":50,"CfgHolder":4617,"BootCount":2,"SaveCount":7,"SaveAddress":"F5000"}}
21:34:35 MQT: stat/groundfloorlight1/STATUS2 = {"StatusFWR":{"Version":"6.4.1.17(sonoff)","BuildDateTime":"2019-02-15T21:13:33","Boot":31,"Core":"2_4_2","SDK":"2.2.1(cfd48f3)"}}
21:34:35 MQT: stat/groundfloorlight1/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"SysLog":1,"LogHost":"192.168.12.155","LogPort":514,"SSId":["iot-2","Wong"],"TelePeriod":60,"Resolution":"558180C0","SetOption":["0000880B","140500000100000000000000000000000000","00000000"]}}
21:34:35 MQT: stat/groundfloorlight1/STATUS4 = {"StatusMEM":{"ProgramSize":493,"Free":508,"Heap":23,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashMode":3,"Features":["00000809","0F8AA790","24038000","00B400CE","000013C0"]}}
21:34:35 MQT: stat/groundfloorlight1/STATUS5 = {"StatusNET":{"Hostname":"groundfloorlight1-5108","IPAddress":"192.168.12.117","Gateway":"192.168.12.1","Subnetmask":"255.255.255.0","DNSServer":"210.245.31.220","Mac":"DC:4F:22:DB:F3:F4","Webserver":2,"WifiConfig":4}}
21:34:35 MQT: stat/groundfloorlight1/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.12.155","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_DBF3F4","MqttUser":"admin","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
21:34:35 MQT: stat/groundfloorlight1/STATUS7 = {"StatusTIM":{"UTC":"Fri Feb 15 14:34:35 2019","Local":"Fri Feb 15 21:34:35 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+07:00","Sunrise":"06:13","Sunset":"18:00"}}
21:34:35 MQT: stat/groundfloorlight1/STATUS10 = {"StatusSNS":{"Time":"2019-02-15T21:34:35"}}
21:34:35 MQT: stat/groundfloorlight1/STATUS11 = {"StatusSTS":{"Time":"2019-02-15T21:34:35","Uptime":"0T00:11:06","Vcc":3.434,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"OFF","POWER3":"ON","Wifi":{"AP":1,"SSId":"iot-2","BSSId":"38:17:C3:F1:90:01","Channel":1,"RSSI":52}}}

[Jason2866]

Is it verified that all buttons work with Arduino core 2.3.0 with latest dev version?
Or is the issue with all core versions?

[yellowonblack]

Yesterday, I updated a Sonoff T1 2CH Module and I can confirm the same problem: the second touch-plate button does not work anymore:

• Program Version 6.4.1.17
  
  
  
  • Build Date & Time 2019-02-14T18:00:57
  
  
• Core/SDK Version 2_4_2/2.2.1(cfd48f3)

The "Toogle 2" button and MQTT commands works normal.

[tompipe]

I had the same problem a few days back. After some playing about with a few things, I did manage to get it working. I briefly stated above, but didn't give reason...

I can't be sure exactly what did it, but I'm fairly sure it was enabling option51. Setting the module type to generic, and then ensuring the gpio connections match those I found here - https://github.com/arendst/Sonoff-Tasmota/wiki/Sonoff-T1-UK,-EU,-and-US

I think even after switching it back to the right module type it still worked.

It could've been something else, as I don't remember everything I did, but I do recall those above.

Unfortunately I can't confirm now, as I've re-flashed it with a different fork with the shutter configuration options.

[wongnam]

Is it verified that all buttons work with Arduino core 2.3.0 with latest dev version?
Or is the issue with all core versions?

@Jason2866 I will not go back to 2.3.0 since it make many issue for me in the past.

• version 6.4.1.17 core 2.4.2 -> has issue with 2nd and 3rd touch button fucntion.
• version 6.4.1.15 core 2.4.2 -> has no issue with any touch button function.
  I think you can imagine the issue that it's not related to the core.

and also @joggs wrote that :

• Second button on Sonoff T1 2ch touch panel is not working using the dev builds of sonoff.bin (as of 190211) for 2.4.2 and 2.5.0 , 6.4.1.
• The release version of 6.4.1 works well.

[arendst]

As a workaround use setoption51 1

This re-enables gpio9 and 10 which seem to be disabled by the latest template update. Will fix today.

[arendst]

SetOption51 1 is not a workaround.

Working on fix...

[arendst]

Due to the bug the settings for GPIO9 and GPIO10 ar lost. They are being used for button2 (Touch 2CH and Pros) and button3 (Touch 3CH and Pros).

What is a workaround:

• Execute SetOption51 1 (enabling GPIO9 and GPIO10)
• Remember current module and change current module to whatever (Rewriting GPIO9 and GPIO10 values)
• Change to remembered module (Rewriting GPIO9 and GPIO10 values)

Once the fix is released execute SetOption51 0

[wongnam]

I already revert it back to 6.4.1.15 lastnight, so i will wait for a fix release.

[arendst]

Thx you for finding the most possible small deviation between (non)-working versions making solving this a lot easier.

[andrethomas2]

Closing as it was fixed with commit https://github.com/arendst/Sonoff-Tasmota/commit/1fde362998c86c6f9d9bb259afd2252de0cd67e7

Support Information

See Wiki for more information.
See Chat for more user experience.