Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonoff T1 3CH US Ghost Switching #5449

Closed
10 tasks done
Bloodyagent opened this issue Mar 12, 2019 · 338 comments
Closed
10 tasks done

Sonoff T1 3CH US Ghost Switching #5449

Bloodyagent opened this issue Mar 12, 2019 · 338 comments
Assignees
Labels
awaiting feedback duplicated troubleshooting

Comments

@Bloodyagent
Copy link

@Bloodyagent Bloodyagent commented Mar 12, 2019

STATUS 0 OUTPUT HERE:
18:56:44 MQT: stat/TestBench/STATUS = {"Status":{"Module":30,"FriendlyName":["Sonoff","Sonoff2","Sonoff3"],"Topic":"TestBench","ButtonTopic":"0","Power":2,"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}}
18:56:44 MQT: stat/TestBench/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/release/sonoff.bin","RestartReason":"Software/System restart","Uptime":"0T02:00:38","StartupUTC":"2019-03-12T15:56:06","Sleep":50,"BootCount":4,"SaveCount":92,"SaveAddress":"F8000"}}
18:56:44 MQT: stat/TestBench/STATUS2 = {"StatusFWR":{"Version":"6.4.1(release-sonoff)","BuildDateTime":"2018-12-24T15:51:34","Boot":31,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}
18:56:44 MQT: stat/TestBench/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Byterite",""],"TelePeriod":300,"SetOption":["0000A009","558180C0","00000000"]}}
18:56:44 MQT: stat/TestBench/STATUS4 = {"StatusMEM":{"ProgramSize":503,"Free":500,"Heap":14,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashMode":3,"Features":["00000809","0FDAE794","000383A0","23B617CE","00003BC0"]}}
18:56:44 MQT: stat/TestBench/STATUS5 = {"StatusNET":{"Hostname":"TestBench-8169","IPAddress":"192.168.0.80","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.0.250","Mac":"DC:4F:22:91:FF:E9","Webserver":2,"WifiConfig":4}}
18:56:44 MQT: stat/TestBench/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.0.60","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_91FFE9","MqttUser":"admin","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
18:56:44 MQT: stat/TestBench/STATUS7 = {"StatusTIM":{"UTC":"Tue Mar 12 17:56:44 2019","Local":"Tue Mar 12 18:56:44 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+01:00","Sunrise":"07:10","Sunset":"18:49"}}
18:56:44 MQT: stat/TestBench/STATUS10 = {"StatusSNS":{"Time":"2019-03-12T18:56:44"}}
18:56:44 MQT: stat/TestBench/STATUS11 = {"StatusSTS":{"Time":"2019-03-12T18:56:44","Uptime":"0T02:00:38","Vcc":3.209,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"ON","POWER3":"OFF","Wifi":{"AP":1,"SSId":"Byterite","BSSId":"18:E8:29:17:48:84","Channel":11,"RSSI":74}}}

  • Provide the output of console when you experience your issue if apply :
    (Please use weblog 4 for more debug information)
CONSOLE OUTPUT HERE:
18:47:27 MQT: stat/TestBench/RESULT = {"POWER3":"ON"}
18:47:27 MQT: stat/TestBench/POWER3 = ON

Hey Guys

OK, so I bought 3 each of sonoff T1 1CH, 2CH, 3CH touch switches.

I successfully flashed all 9 units and installed. All of the CH3 units are experiencing ghost switching. The 1CH and 2CH units are fine. 

I have replaced the 3CH units with 2CH units, I.E using the same wall box and switching the same lights (I was only using 2 lights on the 3CH anyway). The problem is not with the location of the units and not with the load they are switching as the 2CH unit is fine in the same wallbox. 

I erased and re-flashed all three 3CH units and put them on my test bench. Joined to wireless, but did not configure any MQTT broker, and they are all still randomly switching (every few hours any channel will switch on, never off) 

Just after they Channel switches on, there is a beep, then a pause, then 2 quick beeps.

So my thought is that there is an issue with the 3CH units and tasmota? (they were not randomly switching using original firmware)

Has anyone else experienced this issue with the 3 CH T1 US units?

Thanks in Advance.
@ascillato
Copy link
Contributor

@ascillato ascillato commented Mar 12, 2019

Please use weblog 4 for more debug information. When you use that, it will tell you in the console the source of the command that triggers your relay. It will be shown as SRC:

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 12, 2019

ok, will enable weblog 4 and send result when random switching happens again, thanks

@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 12, 2019

Hi, I have same issue. At the first time I thought was some interference on 315MHz receiver. So, seeing data sheet of SYN470R, I lift pin 11, in this way receiver is in shutdown. After that I put pin 10(DO line) at GND to avoid floating pin. After that I tried all my 7 sonoff without glass cover for 2 days and worked fine! no ghost switch.
So, I remount glass cover and ghost switching returns!
So, if you try to long press one of touch button you hear the first beep and after that quickly 2 beep. In original firmware with this operation you can pair with phone, with tasmota seems do nothing fortunately.
So, the problem is touch sensitivity. I try to find a solution but the are no name on IC between touch button and IC. I hope that someone know its name. I do reverse engineering on that and I draw schematic connection and I'm searching on web a datasheet with pin compatibility.
If is useful I can share my schematic on this part of circuit. If I have time tomorrow I'll see some signal coming from button with oscilloscope because maybe it's possibile to adjust sensitivity adjusting input RC network.

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 12, 2019

Ok, just had random switching again, here is output

20:53:35 APP: Button2 immediate
20:53:35 SRC: Button
20:53:35 MQT: stat/TestBench/RESULT = {"POWER2":"ON"}
20:53:35 MQT: stat/TestBench/POWER2 = ON
20:53:35 CFG: Saved to flash at F4, Count 136, Bytes 3584

Thanks

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 12, 2019

Hi, I have same issue. At the first time I thought was some interference on 315MHz receiver. So, seeing data sheet of SYN470R, I lift pin 11, in this way receiver is in shutdown. After that I put pin 10(DO line) at GND to avoid floating pin. After that I tried all my 7 sonoff without glass cover for 2 days and worked fine! no ghost switch.
So, I remount glass cover and ghost switching returns!
So, if you try to long press one of touch button you hear the first beep and after that quickly 2 beep. In original firmware with this operation you can pair with phone, with tasmota seems do nothing fortunately.
So, the problem is touch sensitivity. I try to find a solution but the are no name on IC between touch button and IC. I hope that someone know its name. I do reverse engineering on that and I draw schematic connection and I'm searching on web a datasheet with pin compatibility.
If is useful I can share my schematic on this part of circuit. If I have time tomorrow I'll see some signal coming from button with oscilloscope because maybe it's possible to adjust sensitivity adjusting input RC network.

Thanks for this, I suspected this and did remove the cover at some point, but didn't really take note, think you may be right in that it didn't switch while cover was off. I didn't pursue this because its only happening with the 3CH versions and wasn't an issue with original firmware. I may just disable the middle button and turn the 3CH into a 2CH to see if this fixes it.

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 12, 2019

Just not sure why, if its a sensitivity problem, is it a non issue with original firmware and with the 2ch and 1ch versions?

@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 12, 2019

I have also another sonoff t1 and I use it for 1 month without any ghost switch using last Tasmota firmware with the last core version. When I received others sonoff I saw some disconnection and looking on the web I installed last Tasmota with 2.30 core and disconnections disappears. Some minutes ago sonoff that worked for a month had a ghost switch. So, now I flash last core version again and I want to see if ghost switch disapper. I’ll inform you

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 12, 2019

Yes I moved to core 2.3.0 because of disconnects and haven't tested on 2.4.0

I've removed the white rectangular pads on switches....still getting ghost switching!

Let me know. Thanks

@ascillato2 ascillato2 added duplicated awaiting feedback troubleshooting labels Mar 12, 2019
@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 13, 2019

Did you remove all rectangular pads and did you have ghost switch without glass?

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 13, 2019

Removed pads. Still ghost switching with cover on. Cover off no switching pads or no pads

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 13, 2019

Ok, just had random switching again, here is output

20:53:35 APP: Button2 immediate
20:53:35 SRC: Button
20:53:35 MQT: stat/TestBench/RESULT = {"POWER2":"ON"}
20:53:35 MQT: stat/TestBench/POWER2 = ON
20:53:35 CFG: Saved to flash at F4, Count 136, Bytes 3584

Thanks

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 13, 2019

Ok so have compared the boards off the 1 ch and 3 ch switches. They are identical in every way. There are no missing components on the 1ch as opposed to the 3 channel. Only difference I can see is relay count. So why is it the that when I configure the 3ch as a 2ch the bottom touch button is disabled and not the middle similar to the 2ch. Was hoping to make the 3ch exactly as the 2ch to see if removing the middle touch switch would stop the ghost switching.

@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 13, 2019

Can you see if in 1ch and 2ch versione there are some mark on ic touch component? In 3ch there is not mark on this.
Thank you!
Inked40544554-ff83d8d6-6028-11e8-8cf4-c951b75897d9_LI

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 13, 2019

Chips blank ok all boards. I Googled and there are a few 16pin touch chips out there. Looks to be a 4 ch touch chip

@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 13, 2019

Today I had one ghost switch on button 2 with core 2.42. Do you have ghost switch only on middle button or also others? Now I try to put a paper sheet between cover and plastic pad. I'll see...
I found some chip but no one that I found is compatible with schematic I drawn by inspection(I think is correct).
If you found component with 16 pin that can fit please tell me. Or if you write down a list I can check if they can be fit.
1WqXCpu2TceY3FYOoPuz0A_thumb_95b

@ToRvaLDz
Copy link

@ToRvaLDz ToRvaLDz commented Mar 14, 2019

I'm using about 20 Sonoff T1-2-3 in my home since one year with Tasmota and I found that ghost switching only happen with Mqtt retain and/or RF interference.
In my case I solved disabling Mqtt retain, also try wifi config 4 or 5.

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

Hi @ToRvaLDz

This is on the test bench without mqtt configured. Only happens on my 3CH units, all of them.

I erased the flash, reflashed with 6.4.1 - 2.3.0, joined to wireless, chose sonoff T1 3CH from the config menu, restarted and left them on the testbench with no load and no mqtt, they all ghost switching.

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

haven't tried wifi config 4 or 5. Will try...thanks

@ToRvaLDz

This comment has been minimized.

@beppeserafini
Copy link

@beppeserafini beppeserafini commented Mar 14, 2019

@ToRvaLDz ghost switching you had like us? So, beep and then other two beep quickly?

@ToRvaLDz
Copy link

@ToRvaLDz ToRvaLDz commented Mar 14, 2019

@beppeserafini The beep indicate the long press, the only thing I understood is that the touch is not responding while tasmota is looking for an mqtt connection if not available and that if wifi is not connected tasmota do a reboot causing a relay toggle. For ghost switching, that is a button/relay that activate/deactivate itself, the only cause I found are: mqtt retain or wificonfig != 3 or 4.

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

OK, so this is strange. I remove the 1k resistor from the middle touchpad thereby totally disabling the middle sensor touchpad. The ghost switching is now only happening on the middle sensor!!

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

So its definitely interference of some type. Maybe a lowpass filter on the input pins of the IC? Not sure how the capacitive touch IC works? I see there is a space right next to the 1k resistor for a capacitor, not sure if this is meant to be an RC filter of some type?
tempFileForShare_20190314-190132

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

image
This looks close?
Edit. This is the chip for sure.

http://en.wincomtech.com/prod_view.aspx?TypeId=65&Id=162&FId=t3:65:3

@ToRvaLDz
Copy link

@ToRvaLDz ToRvaLDz commented Mar 14, 2019

Just a stupid question: are you trying it with a serial console connected?

@Bloodyagent
Copy link
Author

@Bloodyagent Bloodyagent commented Mar 14, 2019

Nope. Can we get more debug data that way?

@ToRvaLDz
Copy link

@ToRvaLDz ToRvaLDz commented Mar 14, 2019

No, just because I noticed a ghost switching issue while it is not mounted in the wall socket

@mpkoslovsky
Copy link

@mpkoslovsky mpkoslovsky commented Mar 3, 2020

After updating all devices to firmware 8.1 I forgot what is ghost switching.

@lucianocf
Copy link

@lucianocf lucianocf commented Mar 3, 2020

After updating all devices to firmware 8.1 I forgot what is ghost switching.

Really? Need any aditional configuration? I'll try to upgrade one of my devices to check.

@rnogueiragh
Copy link

@rnogueiragh rnogueiragh commented Mar 3, 2020

For now (2 days straight), i have the same results with the newest firmware (8.1). No ghost switching.
But I'll wait a little more to be sure… :)

@mpkoslovsky
Copy link

@mpkoslovsky mpkoslovsky commented Mar 3, 2020

No, no need any changes. I'm with more than 10 days without ghost switching.

@felipenanoclick
Copy link

@felipenanoclick felipenanoclick commented Mar 17, 2020

tasmota 8.11, bye bye ghost!

@Collin7
Copy link

@Collin7 Collin7 commented Mar 17, 2020

I can also confirm, 8.1 seems to do the trick. After setOption40 came out, I had the rare ghost that the light would actually come one, but mostly my switches would do the 3 beeps, multiple times a day. Its been about 2 weeks now with tasmota 8.1, and not a single ghosting incident or beeping incident. Thank you @arendst

@REALogics
Copy link

@REALogics REALogics commented Mar 17, 2020

My Sonoff T2 3x Gang switches which were ghost switching several times a day. V8.1 has solved it, not a single ghost in weeks!

@wookie666
Copy link

@wookie666 wookie666 commented Mar 17, 2020

Ok. Upgraded one of my switches to 8.1 that usually ghosts switches. Will now see what happens over the next few weeks. Can i ask though, does anybody know what change in 8.1 has fixed the issue specifically.

@kyemacdonald
Copy link

@kyemacdonald kyemacdonald commented Mar 17, 2020

Pushing update to all my switches right now! Oh please! I have a pile of switches not installed because of this issue.

@kyemacdonald
Copy link

@kyemacdonald kyemacdonald commented Mar 22, 2020

@arendst

5 days and 14 switches - no ghost switches on 8.1

@lucianocf
Copy link

@lucianocf lucianocf commented Mar 23, 2020

Confirmed. 20 days without ghost switching. Version 8.1 solved completely. Thanks everyone.

@Fusseldieb
Copy link

@Fusseldieb Fusseldieb commented Jun 15, 2020

Ok. Upgraded one of my switches to 8.1 that usually ghosts switches. Will now see what happens over the next few weeks. Can i ask though, does anybody know what change in 8.1 has fixed the issue specifically.

I also like to know that

@garageeks
Copy link

@garageeks garageeks commented Apr 8, 2021

Hi guys, I have a Sonoff T3 EU, latest PCB version. Had ghost switching with stock firmware from day one.
Tried disabling RF chip by disconnecting pin 11 as someone suggested here, to no avail. Tried 18pF caps to make an RC filter on the capacitive touch areas, but they wouldn't register any input. For some reason, the ghost switches appeared at regular intervals of 30 minutes.

Flashed yesterday Tasmota 9.3.1, ghost switching still occurs, albeit less frequent. Haven't observed a pattern so far.
Tried the combo Backlog SetOption1 1; SetOption13 0;SetOption 40 10; seems to work better but the problem is not completely erased.
I'm not using any home automation service, just connected the Sonoff to the WiFi to access Tasmota web page.
It seems a hardware issue, the Sonoff PSU is noisy or not good at filtering... Do you have any other recommendations? Or different values for SetOption 40?

Thanks
Nick

@Fusseldieb
Copy link

@Fusseldieb Fusseldieb commented Apr 8, 2021

@garageeks

From what I've observed, it's related to WiFi traffic.

Yes, seems absurd, but I've observed that when a device connects or disconnects from the wifi, some of my switches ghost switch, but not always.

@kyemacdonald
Copy link

@kyemacdonald kyemacdonald commented Apr 8, 2021

@garageeks I think you might have bad hardware. I've got ~25 sonoff switches installed now including several T3s and have zero ghost switching since moving to 8.1 or newer. Ghost switching on stock firmware was there, but it was rare, as in it took several days.

Also even when I had loads of switches doing it there was no consistent timing. Some switches would do it in under 20 mins, other would take days, but there was no consistency or regularity to the timing.

@garageeks
Copy link

@garageeks garageeks commented Apr 9, 2021

@LaurentG91
Copy link

@LaurentG91 LaurentG91 commented Apr 9, 2021

Hello, have you done a reset 5 after flashing tasmota, to clean the memory....

@kyemacdonald
Copy link

@kyemacdonald kyemacdonald commented May 17, 2021

@Fusseldieb or update to any version of tasmota version 8 or later.....

Like seriously, your commenting on a tasmota thread, when you don't use tasmota, with a solution for a problem tasmota hasn't had on these switches for ages....

I have no idea if your "solution" works, but seriously if you have a sonoff switch just update to tasmota 8 or newer and don't butcher your devices.

@Fusseldieb
Copy link

@Fusseldieb Fusseldieb commented May 17, 2021

@Fusseldieb or update to any version of tasmota version 8 or later.....

Like seriously, your commenting on a tasmota thread, when you don't use tasmota, with a solution for a problem tasmota hasn't had on these switches for ages....

I have no idea if your "solution" works, but seriously if you have a sonoff switch just update to tasmota 8 or newer and don't butcher your devices.

The thing is, its another chip that toggles the touch buttons ocasionally. Even with Tasmota 8, afaik, it's a hit or miss. Tasmota manages the ESP, but not the EFM, so it physically can't solve this issue for everyone.

This is even commented on the official Tasmota documentation:

Some of these devices are prone to hardware ghost switching. You may need to experiment with ButtonDebounce and SetOption40 to reduce or eliminate these issues.

This hardware mod solves that, for every firmware, on every version, guaranteed.

But I hear you, I put a disclaimer on top.

@artemdavydenko
Copy link

@artemdavydenko artemdavydenko commented Jun 28, 2021

Found "crutch" solution with no soldering, but it works fine for me with no ghost switching for a week (had ghost switching several times per hour). Faced with ghost switching on Avavtto WiFi switches with no connection to MQTT - they were installed on their places on a wall, connected to WiFi but not connected to HA, it means root cause is not retained MQTT messages. Tried to increase ButtonDebounce even to 1000 and SetOption40 but with no luck - ghost frequency decreased but wasn't gone. After some investigation, I figured out that the root cause of the problem is touch panel - it generates ghost touches. I tried to detach buttons from relay with command SetOption73 1 and I continued watching the log - there were ghost switches only single press command, like {"Button1":{"Action":"SINGLE"}} and were no double or hold commands. Then I decided just to ignore all single press commands and turn on/off relay only by hold action - I decreased time for hold action with command SetOption32 2 (0.2 sec for hold action) and added the rule Rule1 ON button1#state=3 DO Power1 2 ENDON which switch on/off relay by hold action. That's all, no ghost switches at all. I tried to set SetOption32 1 but very rarely ghost switches happened like 1 for several days and there is a risk to reset your Tasmota device because SetOption32 1 also defines time for reset x10 times of time from SetOption32 (maybe someone can open request to set time threshold not less than 10 sec HOLDING action for reset).

Used commands:

Backlog ButtonTopic 0; SetOption1 1; SetOption73 1; SetOption32 2
Rule1 ON button1#state=3 DO Power1 2 ENDON
Rule1 1

I hope it helps.

@b0rder
Copy link

@b0rder b0rder commented Jul 26, 2021

Found "crutch" solution with no soldering, but it works fine for me with no ghost switching for a week (had ghost switching several times per hour). Faced with ghost switching on Avavtto WiFi switches with no connection to MQTT - they were installed on their places on a wall, connected to WiFi but not connected to HA, it means root cause is not retained MQTT messages. Tried to increase ButtonDebounce even to 1000 and SetOption40 but with no luck - ghost frequency decreased but wasn't gone. After some investigation, I figured out that the root cause of the problem is touch panel - it generates ghost touches. I tried to detach buttons from relay with command SetOption73 1 and I continued watching the log - there were ghost switches only single press command, like {"Button1":{"Action":"SINGLE"}} and were no double or hold commands. Then I decided just to ignore all single press commands and turn on/off relay only by hold action - I decreased time for hold action with command SetOption32 2 (0.2 sec for hold action) and added the rule Rule1 ON button1#state=3 DO Power1 2 ENDON which switch on/off relay by hold action. That's all, no ghost switches at all. I tried to set SetOption32 1 but very rarely ghost switches happened like 1 for several days and there is a risk to reset your Tasmota device because SetOption32 1 also defines time for reset x10 times of time from SetOption32 (maybe someone can open request to set time threshold not less than 10 sec HOLDING action for reset).

Used commands:

Backlog ButtonTopic 0; SetOption1 1; SetOption73 1; SetOption32 2
Rule1 ON button1#state=3 DO Power1 2 ENDON
Rule1 1

I hope it helps.

Thanks. Very usefull solution.
One more question, is there possible to avoid of MQTT "SINGLE" press events like follow:
10:49:13.816 MQT: stat/avatto-2/RESULT = {"Button1":{"Action":"SINGLE"}}
10:49:13.830 MQT: stat/avatto-2/RESULT = {"Button2":{"Action":"SINGLE"}}
10:49:13.843 MQT: stat/avatto-2/RESULT = {"Button3":{"Action":"SINGLE"}}
10:49:14.721 MQT: stat/avatto-2/RESULT = {"Button1":{"Action":"DOUBLE"}}
10:49:14.737 MQT: stat/avatto-2/RESULT = {"Button2":{"Action":"DOUBLE"}}
10:49:14.751 MQT: stat/avatto-2/RESULT = {"Button3":{"Action":"DOUBLE"}}

Because of "ghost" switching, there are a lot of MQTT events occured and I have no idea how to mute it.

@siyuan-nz
Copy link

@siyuan-nz siyuan-nz commented Oct 6, 2021

I'm planning to get some T2 1/2/3CH US switches myself, but coming across the discussion here concerns me.

Looking at the datasheet, I see the touch IC works in self-lock mode, also mentioned by @beppeserafini 's comment. Which means the min time filter won't work because the output is going to be held stable by the touch IC. But it looks like the self-locking mode can be disabled by either lifting pin 1 or cut its trace, then solder a wire connecting pin 1 to pin 12 (VCC). That way, the min time filter should work.

The datasheet also adviced that any unused input (just one in the 3CH case, don't know what IC is used on other variants), then it should be left floating rather than being pull-down as seen in @beppeserafini 's drawing. Because of that, one should try also lift/cut pin 6.

I'll probably get a T2 3CH US first to experiment with myself too.

@kyemacdonald
Copy link

@kyemacdonald kyemacdonald commented Oct 6, 2021

@siyuan-nz This issue was solved back in March of last year with the release of version 8 of tasmota.

@siyuan-nz
Copy link

@siyuan-nz siyuan-nz commented Oct 6, 2021

@kyemacdonald, oops, I read 80% of the ticket, but missed the most important part...

@Fusseldieb
Copy link

@Fusseldieb Fusseldieb commented Oct 6, 2021

Rporting back, the hardware mod did NOT solve it. The problem lies on the touch chip itself.

I deleted my eariler answer.

@Fusseldieb
Copy link

@Fusseldieb Fusseldieb commented Oct 7, 2021

@mihalceac
Copy link

@mihalceac mihalceac commented Mar 8, 2022

Found "crutch" solution with no soldering, but it works fine for me with no ghost switching for a week (had ghost switching several times per hour). Faced with ghost switching on Avavtto WiFi switches with no connection to MQTT - they were installed on their places on a wall, connected to WiFi but not connected to HA, it means root cause is not retained MQTT messages. Tried to increase ButtonDebounce even to 1000 and SetOption40 but with no luck - ghost frequency decreased but wasn't gone. After some investigation, I figured out that the root cause of the problem is touch panel - it generates ghost touches. I tried to detach buttons from relay with command SetOption73 1 and I continued watching the log - there were ghost switches only single press command, like {"Button1":{"Action":"SINGLE"}} and were no double or hold commands. Then I decided just to ignore all single press commands and turn on/off relay only by hold action - I decreased time for hold action with command SetOption32 2 (0.2 sec for hold action) and added the rule Rule1 ON button1#state=3 DO Power1 2 ENDON which switch on/off relay by hold action. That's all, no ghost switches at all. I tried to set SetOption32 1 but very rarely ghost switches happened like 1 for several days and there is a risk to reset your Tasmota device because SetOption32 1 also defines time for reset x10 times of time from SetOption32 (maybe someone can open request to set time threshold not less than 10 sec HOLDING action for reset).

Used commands:

Backlog ButtonTopic 0; SetOption1 1; SetOption73 1; SetOption32 2 Rule1 ON button1#state=3 DO Power1 2 ENDON Rule1 1

I hope it helps.

Hello
I’ve tried the solution above and from ghost switching now I have ghost flashing.
The lights randomly flash 4 times, at least they remain off at the end so I consider this an improvement.
Dose anyone have any other option I can try.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback duplicated troubleshooting
Projects
None yet
Development

No branches or pull requests