Closed Bloodyagent closed 5 years ago
Yes, datasheet suggest X5R if I remember correctly.
Have a look on to Ghost / Random Switching on Sonoff Devices (MQTT Retained)
Just curious where this has left off. It appears by comments here that CAPs did not necessarily fix the problem, so I have not tried it. I did followed the MQTT Retained instructions in link above, but I still get ghost switching on both of my T1 3CH. The T1 starts with beep.... beep.beep. Then the light changes state. It is most often the center switch, but the top and bot switch also trigger on occasion.
With log turned ON, the ghost switch happens here:
`02:27:03 WIF: Checking connection... 02:27:03 WIF: Connected 02:27:05 APP: Button1 multi-press 1 02:27:16 SRC: Button 02:27:16 MQT: sonoff-5682/tele/STATE = {"Time":"2019-05-25T02:27:16","Uptime":"10T01:17:00","Vcc":3.202,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"ON","POWER3":"ON","Wifi":{"AP":1,"SSId":"XXXX","BSSId":"A0:63:91:D7:XX:XX","Channel":9,"RSSI":78,"LinkCount":2,"Downtime":"0T00:02:05"}} 02:27:16 MQT: sonoff-5682/stat/RESULT = {"POWER1":"OFF"} 02:27:16 MQT: sonoff-5682/stat/POWER1 = OFF (retained) 02:27:17 SRC: MQTT 02:27:17 RSL: Received Topic sonoff-5682/cmnd/POWER1, Data Size 3, Data OFF 02:27:17 RSL: Group 0, Index 1, Command POWER, Data OFF 02:27:17 MQT: sonoff-5682/tele/STATE = {"Time":"2019-05-25T02:27:17","Uptime":"10T01:17:01","Vcc":3.186,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"ON","POWER3":"ON","Wifi":{"AP":1,"SSId":"XXXX","BSSId":"A0:63:91:D7:XX:XX","Channel":9,"RSSI":72,"LinkCount":2,"Downtime":"0T00:02:05"}} 02:27:17 MQT: sonoff-5682/stat/RESULT = {"POWER1":"OFF"} 02:27:17 MQT: sonoff-5682/stat/POWER1 = OFF (retained) 02:27:17 CFG: Saved to flash at F4, Count 304, Bytes 3584 02:27:23 WIF: Checking connection... 02:27:23 WIF: Connected'
Did you try to keep sonoff without glass cover? In my opinion is a sensitivity problem about touch
I was trying to avoid modifying hardware, thinking it could be done in firmware. After looking at the chip document, it appears WTC6104 chip sensitivity is set by a capacitor (unlike the MPR121 set by firmware). Since we are all putting tasmota firmware on these devices, the next question for me is... does this happen with Sonoff T1's with stock factory binary. I don't have one to test. But if stock binary does not have the issue, then there may still be something about tasmota firmware causing this. I am studying the tasmota firmware at the moment.
By the way, with Home Assistant PI turned off (not controlling Sonoffs), I still had a T1 US button change state over night.
Me too when the problem appeared I suspected that was a firmware bug but I didn’t have anymore sonoff to try. After that I saw no ghost switching without glass cover and I looked for hardware bugs..
Im using T1 3 gang usa for 2 weeks. 11 days with stock FW and last 2 days with Tasmota. I havent noticed this problem on stock and noticed it 3 times in last 2 days with tasmota.
I have configured OpenHab to turn on some other lights on long press so even if i dont hear beep, pause, beep beep, I can see in the morning which channel ghosted a long press.
There's always a chance this is only accident, that somehow i missed ghost clicks on the stock fw, but I'd say 11 days (0) to 2 days (3)... Slim chance. I bet on some tasmota error or at least hardware error byoassed in original fw and not in tasmota.
This is my scenario.
T1 1 gang: 3 un T1 3 gang: 1 un
One T1 1 gang I’m running esp easy firmware. Others T1’s I’m running Tasmota firmware.
First T1 1 gang I improved were flashed with esp easy firmware and I got ghost switch at few hours later.
When received other T1’s I was deicied flash with Tasmota.
T1’s 1 gang running last Tasmota firmware start ghost switch after few hours later also.
As I had two T1 1 gang with different firmwares version with ghost switching, I was deciding test T1 3 gang with stock firmware and leave it for two weeks, results no ghost switching. After two weeks, flashed same T1 3 gang with Tasmota, result ghost switch appear again.
After that, I was deicied running all T1’s 1 and 3 gang without glass cover, no ghost switching for three days tested. After three days, remount glass cover but now with an different assembly approach leaving glass cover for last one mounting it very carefully , results no ghost switching for few tested days, including T1 running esp easy firmware.
All T1’s running Tasmota firmware I had pasted below commands at console
SwitchRetain Off ButtonRetain On ButtonRetain Off Powerretain On
Part a time I thinked could be touch sensibility but when running with stock firmware no ghost switch appear.
All times I had ghost switching I heard beep, pause beep beep.
Hi
What version of Tasmota are you running?
I had the ghost switching problem with version 6.5
Once I downgraded the version to 6.3 all ghost problems stop with no modification to the devices required.
Best regards
Andy Goldie On 31 May 2019, at 22:37, sorokaalex notifications@github.com<mailto:notifications@github.com> wrote:
This is my scenario.
T1 1 gang: 3 un T1 3 gang: 1 un
One T1 1 gang I’m running esp easy firmware. Others T1’s I’m running Tasmota firmware.
First T1 1 gang I improved were flashed with esp easy firmware and I got ghost switch at few hours later.
When received other T1’s I was deicied flash with Tasmota.
T1’s 1 gang running last Tasmota firmware start ghost switch after few hours later also.
As I had two T1 1 gang with different firmwares version with ghost switching, I was deciding test T1 3 gang with stock firmware and leave it for two weeks, results no ghost switching. After two weeks, flashed same T1 3 gang with Tasmota, result ghost switch appear again.
After that, I was deicied running all T1’s 1 and 3 gang without glass cover, no ghost switching for three days tested. After three days, remount glass cover but now with an different assembly approach leaving glass cover for last one mounting it very carefully , results no ghost switching for few tested days, including T1 running esp easy firmware.
All T1’s running Tasmota firmware I had pasted below commands at console
SwitchRetain Off ButtonRetain On ButtonRetain Off Powerretain On
Part a time I thinked could be touch sensibility but when running with stock firmware no ghost switch appear.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/arendst/Sonoff-Tasmota/issues/5449?email_source=notifications&email_token=AIO5ZCRWMFKEPEURT5FVST3PYGLCJA5CNFSM4G5OGQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWN2GQ#issuecomment-497868058, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIO5ZCWJVZSPLFWMSW2XDLDPYGLCJANCNFSM4G5OGQNQ.
Hi What version of Tasmota are you running? I had the ghost switching problem with version 6.5 Once I downgraded the version to 6.3 all ghost problems stop with no modification to the devices required. Best regards Andy Goldie
I’m running 6.5 firmware on all Tasmota devices. If one more ghost switch appear I’ll try downgrade firmware version.
@AndyGoldie
May I request that you try your tests with 6.5.0.13 available at http://thehackbox.org/tasmota/020300/sonoff.bin??
If your results are similar, please open a new issue providing the details of your stock firmware tests, Tasmota 6.3, and Tasmota 6.5.0.13.. Perhaps these clues will result in Theo being able to uncover what causes the instability.
Thanks
Mike
I have this issue and it is not restricted to 3 channel versions. I am currently seeing it on 1s, 2s and 3s. 3s are most prone to it, however I think this is straight up a function of having 3 pads.
Currently I have 2 x 3 channel, 2 x 1 channel and 3 x 2 channels installed and all have ghosted. Mtqq server is offline, the only solution is to have the faceplate off. I tried the paper behind the glass option without success.
I will try the firmware above. Testing wise a 3ch will ghost approximately once every 6 to 8 hours.
I have 1 3ch which still has stock firmware. It has had zero ghost switches.
With the 6.5.0 firmware, I set "SetOption13=1" to disable multi-button action (enables single action only). The Beep -- Beep - Beep still occurs once or twice a day BUT the lights do not switch as a result.
I've got setoption13 1 on all my switches and they still switch the lights. This was one of the things I tried.
I've updated with the firmware listed above and set weblog 4, as well as SwitchRetain Off; ButtonRetain On; ButtonRetain Off; PowerOnState 3; PowerRetain On; SetOption13 1
For the purposes of this test the MQTT server field is left intentionally blank.
Information page output
Sonoff T1 3CH Module Sonoff Master Bedroom 1 Program Version 6.5.0.14(d0502c1-sonoff) Build Date & Time 2019-06-02T19:01:37 Core/SDK Version 2_3_0/1.5.3(aec24ac9) Uptime 0T00:03:23 Flash write Count 231 at 0xF8000 Boot Count 20 Restart Reason Software/System restart Friendly Name 1 Sonoff Master Bedroom 1 Friendly Name 2 Sonoff Master Bedroom 2 Friendly Name 3 Sonoff Stairwell Light Upper
AP1 SSId (RSSI) Skyenet (100%) Hostname sonoffmasterbedroom-6947 IP Address 10.1.1.52 Gateway 10.1.1.254 Subnet Mask 255.255.255.0 DNS Server 10.1.1.254 MAC Address C4:4F:33:9E:DB:23
MQTT Host
MQTT Port 1883
MQTT User mqtt
MQTT Client DVES_9EDB23
MQTT Topic sonoffmasterbedroom
MQTT Group Topic sonoffs
MQTT Full Topic sonoffmasterbedroom/cmnd/
MQTT Fallback Topic cmnd/DVES_9EDB23_fb/
Emulation None mDNS Discovery Disabled
ESP Chip Id 10410787 Flash Chip Id 0x144051 Flash Size 1024kB Program Flash Size 1024kB Program Size 524kB Free Program Space 476kB Free Memory 14kB
Initial boot output: 00:00:00 CFG: Loaded from flash at F9, Count 230 00:00:00 SRC: Restart 00:00:00 Project sonoff Sonoff Master Bedroom 1 Version 6.5.0.14(d0502c1-sonoff)-2_3_0 00:00:00 WIF: Checking connection... 00:00:00 WIF: Attempting connection... 00:00:00 WIF: Patch issue 2186 00:00:00 WIF: Connecting to AP1 Skyenet in mode 11N as sonoffmasterbedroom-6947... 00:00:01 WIF: Checking connection... 00:00:01 WIF: Attempting connection... 00:00:02 WIF: Checking connection... 00:00:02 WIF: Attempting connection... 00:00:03 WIF: Checking connection... 00:00:03 WIF: Attempting connection... 00:00:04 WIF: Checking connection... 00:00:04 WIF: Connected 00:00:04 HTP: Web server active on sonoffmasterbedroom-6947 with IP address 10.1.1.52 00:00:06 HTP: Main Menu 00:00:08 HTP: Console 00:00:10 APP: Boot Count 20 00:00:10 CFG: Saved to flash at F8, Count 231, Bytes 3584 00:00:12 APP: (UTC) Mon Jun 03 01:24:24 2019, (DST) Sun Mar 31 02:00:00 2019, (STD) Sun Oct 27 03:00:00 2019 02:24:32 CMD: backlog SwitchRetain Off; ButtonRetain On; ButtonRetain Off; PowerOnState 3; PowerRetain On 02:24:32 SRC: WebConsole from 10.1.1.45 02:24:32 RSL: Received Topic /backlog, Data Size 83, Data SwitchRetain Off; ButtonRetain On; ButtonRetain Off; PowerOnState 3; PowerRetain On 02:24:32 RSL: Group 0, Index 1, Command BACKLOG, Data SwitchRetain Off; ButtonRetain On; ButtonRetain Off; PowerOnState 3; PowerRetain On 02:24:32 SRC: Backlog 02:24:32 RSL: Received Topic /SwitchRetain, Data Size 3, Data Off 02:24:32 RSL: Group 0, Index 1, Command SWITCHRETAIN, Data Off 02:24:32 RSL: sonoffmasterbedroom/stat/RESULT = {"SwitchRetain":"OFF"} 02:24:32 SRC: Backlog 02:24:32 RSL: Received Topic /ButtonRetain, Data Size 2, Data On 02:24:32 RSL: Group 0, Index 1, Command BUTTONRETAIN, Data On 02:24:32 RSL: sonoffmasterbedroom/stat/RESULT = {"ButtonRetain":"ON"} 02:24:33 SRC: Backlog 02:24:33 RSL: Received Topic /ButtonRetain, Data Size 3, Data Off 02:24:33 RSL: Group 0, Index 1, Command BUTTONRETAIN, Data Off 02:24:33 RSL: sonoffmasterbedroom/stat/RESULT = {"ButtonRetain":"OFF"} 02:24:33 SRC: Backlog 02:24:33 RSL: Received Topic /PowerOnState, Data Size 1, Data 3 02:24:33 RSL: Group 0, Index 1, Command POWERONSTATE, Data 3 02:24:33 RSL: sonoffmasterbedroom/stat/RESULT = {"PowerOnState":3} 02:24:33 SRC: Backlog 02:24:33 RSL: Received Topic /PowerRetain, Data Size 2, Data On 02:24:33 RSL: Group 0, Index 1, Command POWERRETAIN, Data On 02:24:33 RSL: sonoffmasterbedroom/stat/RESULT = {"PowerRetain":"ON"} 02:24:36 WIF: Checking connection... 02:24:36 WIF: Connected 02:24:45 CMD: SetOption13 1 02:24:45 SRC: WebConsole from 10.1.1.45 02:24:45 RSL: Received Topic /SetOption13, Data Size 1, Data 1 02:24:45 RSL: Group 0, Index 13, Command SETOPTION, Data 1 02:24:45 RSL: sonoffmasterbedroom/stat/RESULT = {"SetOption13":"ON"} 02:24:56 WIF: Checking connection... 02:24:56 WIF: Connected 02:25:11 CMD: weblog 4 02:25:11 SRC: WebConsole from 10.1.1.45 02:25:11 RSL: Received Topic /weblog, Data Size 1, Data 4 02:25:11 RSL: Group 0, Index 1, Command WEBLOG, Data 4 02:25:11 RSL: sonoffmasterbedroom/stat/RESULT = {"WebLog":4} 02:25:16 WIF: Checking connection... 02:25:16 WIF: Connected 02:25:36 WIF: Checking connection... 02:25:36 WIF: Connected
I am reopening this issue as I am still experiencing ghosting after lowering C6 capacitor to 16nf.
Morning all,
So I had ghost switching on a 3 gang last night with the firmware above. I didn't catch it in the weblog so I have configured a logging server to catch the next one.
Unlike bloodyagent I am definitely getting them on 2ch switches as well as 3ch.
Managed to catch the change on a 2 channel. This one is connected to MQTT server.
23:18:08 WIF: Checking connection... 23:18:08 WIF: Connected 23:18:28 WIF: Checking connection... 23:18:28 WIF: Connected 23:18:48 WIF: Checking connection... 23:18:48 WIF: Connected 23:19:08 WIF: Checking connection... 23:19:08 WIF: Connected 23:19:28 WIF: Checking connection... 23:19:28 WIF: Connected 23:19:48 WIF: Checking connection... 23:19:48 WIF: Connected 23:20:08 WIF: Checking connection... 23:20:08 WIF: Connected 23:20:26 MQT: sonoffliving/tele/HASS_STATE = {"Version":"6.5.0.14(d0502c1-sonoff)","BuildDateTime":"2019-06-02T19:01:37","Core":"2_3_0","SDK":"1.5.3(aec24ac9)","Module":"Sonoff T1 2CH","RestartReason":"Software/System restart","Uptime":"0T11:45:01","WiFi LinkCount":1,"WiFi Downtime":"0T00:00:04","MqttCount":1,"BootCount":21,"SaveCount":286,"IPAddress":"10.1.1.53","RSSI":"100","LoadAvg":19} 23:20:28 WIF: Checking connection... 23:20:28 WIF: Connected 23:20:38 MQT: sonoffliving/tele/STATE = {"Time":"2019-06-03T23:20:38","Uptime":"0T11:45:13","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Skyenet","BSSId":"1C:F2:9A:CA:FE:A3","Channel":1,"RSSI":100,"LinkCount":1,"Downtime":"0T00:00:04"}} 23:20:48 WIF: Checking connection... 23:20:48 WIF: Connected 23:20:49 APP: Button1 immediate 23:20:49 SRC: Button 23:20:49 MQT: sonoffliving/tele/STATE = {"Time":"2019-06-03T23:20:49","Uptime":"0T11:45:24","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"ON","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Skyenet","BSSId":"1C:F2:9A:CA:FE:A3","Channel":1,"RSSI":100,"LinkCount":1,"Downtime":"0T00:00:04"}} 23:20:49 MQT: sonoffliving/stat/RESULT = {"POWER1":"ON"} 23:20:49 MQT: sonoffliving/stat/POWER1 = ON (retained) 23:20:50 CFG: Saved to flash at FA, Count 287, Bytes 3584 23:21:08 WIF: Checking connection... 23:21:08 WIF: Connected 23:21:15 HTP: Console 23:21:28 WIF: Checking connection... 23:21:28 WIF: Connected 23:21:48 WIF: Checking connection... 23:21:48 WIF: Connected 23:22:08 WIF: Checking connection... 23:22:08 WIF: Connected
Additional on the switch that triggered.
Sonoff T1 2CH Module Sonoff Living 1 Program Version 6.5.0.14(d0502c1-sonoff) Build Date & Time 2019-06-02T19:01:37 Core/SDK Version 2_3_0/1.5.3(aec24ac9) Uptime 0T11:50:15 Flash write Count 287 at 0xFA000 Boot Count 21 Restart Reason Software/System restart Friendly Name 1 Sonoff Living 1 Friendly Name 2 Sonoff Living 2
AP1 SSId (RSSI) Skyenet (100%) Hostname sonoffliving-2245 IP Address 10.1.1.53 Gateway 10.1.1.254 Subnet Mask 255.255.255.0 DNS Server 10.1.1.254 MAC Address 84:0D:8E:67:C8:C5
MQTT Host 10.1.1.99 MQTT Port 1883 MQTT User mqtt MQTT Client DVES_67C8C5 MQTT Topic sonoffliving MQTT Group Topic sonoffs MQTT Full Topic sonoffliving/cmnd/ MQTT Fallback Topic cmnd/DVES_67C8C5_fb/
Emulation None mDNS Discovery Disabled
ESP Chip Id 6801605 Flash Chip Id 0x144051 Flash Size 1024kB Program Flash Size 1024kB Program Size 524kB Free Program Space 476kB Free Memory 13kB
@Bloodyagent
Have you tried increasing debounce with buttondebounce command? (https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#control)
Denounce set to 1000 to test
@kyemacdonald have you reduced size of C6 capacitor? This definitely helps but does not eliminate completely. @ascillato no have not tried, will give it a go, thanks.
Debounce to 1000 is too much. Try first 100 please
I apologize. In my earlier post when I said I "SetOption13 1"
I failed to indicated that at the same time I set "ButtonDebounce 500".
Since setting these two option settings last week, the 3x beeps still occur once or twice a day, but the states of the buttons/lights do not change.
I have 2x "T1 US 3CH" sonoff switches.
I don’t remember if my final cap value was 16nF. Maybe a little bit lower. However in my home I’m using 7 sonoff T1 3 gang for 4 months with this setting and I NEVER had ghost switching. So in my opinion in original firmware there is some algorithm to bypass hardware issue but adjusting capacitance we fix it
@Bloodyagent
Have you tried increasing debounce with buttondebounce command?
@Bloodyagent No I haven't swapped the capacitor as yet as the stock firmware doesn't have this issue. So from my perspective, at this stage anyway, a software solution should be possible.
@ascillato I've gone to the extreme of 1000 to see if that removes the problem completely. If it does then I will lower the number until it starts happening again. It does make the switches pretty horrible to use set that high as you have to wait a noticeable length of time before you can activate the next button in the gang.
@kyemacdonald
Please, use a small value like 100 for debounce. Thanks
@ascillato - done. Let me know if there is any other testing setting that would be useful.
That debounce time should be enough and the response time is not noticeable (on button release). If you want faster response time (on button push), disable multipress with setoption commands.
Switch triggered with debounce set to 100. Upping to 200
03:54:28 WIF: Checking connection... 03:54:28 WIF: Connected 03:54:31 APP: Button2 immediate 03:54:31 SRC: Button 03:54:31 MQT: sonoffliving/tele/STATE = {"Time":"2019-06-05T03:54:31","Uptime":"0T00:51:47","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"ON","Wifi":{"AP":1,"SSId":"Skyenet","BSSId":"1C:F2:9A:CA:FE:A3","Channel":1,"RSSI":100,"LinkCount":1,"Downtime":"0T00:00:04"}} 03:54:31 MQT: sonoffliving/stat/RESULT = {"POWER2":"ON"} 03:54:31 MQT: sonoffliving/stat/POWER2 = ON (retained) 03:54:32 CFG: Saved to flash at F9, Count 376, Bytes 3584 03:54:48 WIF: Checking connection... 03:54:48 WIF: Connected 03:55:08 WIF: Checking connection... 03:55:08 WIF: Connected 03:55:17 HTP: Main Menu 03:55:17 HTP: Console
Switch triggered with debounce set to 200. Upping to 500.
07:16:09 WIF: Checking connection... 07:16:09 WIF: Connected 07:16:29 WIF: Checking connection... 07:16:29 WIF: Connected 07:16:38 APP: Button1 immediate 07:16:38 SRC: Button 07:16:38 MQT: sonoffliving/tele/STATE = {"Time":"2019-06-05T07:16:38","Uptime":"0T04:13:54","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"ON","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Skyenet","BSSId":"1C:F2:9A:CA:FE:A3","Channel":1,"RSSI":100,"LinkCount":1,"Downtime":"0T00:00:04"}} 07:16:38 MQT: sonoffliving/stat/RESULT = {"POWER1":"ON"} 07:16:38 MQT: sonoffliving/stat/POWER1 = ON (retained) 07:16:38 CFG: Saved to flash at F6, Count 379, Bytes 3584 07:16:49 WIF: Checking connection... 07:16:49 WIF: Connected 07:17:09 WIF: Checking connection... 07:17:09 WIF: Connected
@Bloodyagent
Have you tried increasing debounce with buttondebounce command?
Closing this issue as there is no feedback. When you have time, please share your results. Thanks.
Buttondebounce set has 500 has removed ghost press on all my switches.
I believe there is a difference in the sensitivity between individual switches. 500 is likely too high for most of my switches and I will test lowering it, however 1 of my switches (the logs above) was particularly sensitive.
Great findings. Thanks a lot for sharing. :+1:
Sorry for delayed feedback. Have work kids and wife to deal with! Have changed debounce to 200, so far so good.
Why does this issue get closed when there is a known problem with no conclusive resolve? The fact that "SetOption13 1" and ButtonDebounce 500" has prevented false state changes on my two T1 SS 3CH only suggests that firmware needs investigation. I still get an occasional 3 beeps with "SetOption13 1", but why? And a "ButtonDebounce 500" setting is unrealistic. I will set 100ms debounce tonight.
Changing capacitors internally is only an investigative approach, but not an answer for the masses. I would dig into the firmware myself, if it were not for other pressing activities. This issue should stay open until a viable fix is identified, and firmware updated if necessary.
An update.
Buttondebounce 500 has not removed ghost switching entirely. It has reduced the frequency though.
Severely is definitely different between each piece of hardware.
I have same problem. I hear 1 beep the fast 2 beeps and light is turning on Increasing buttondebounce helps but I need to put over 500 and its unrealistic to use it with so slow response time
Same issue here in my Sonoff T1 3CH US. Changed the settings to SwitchRetain Off; ButtonRetain On; ButtonRetain Off; PowerOnState 3; PowerRetain On removed /var/lib/mosquitto/mosquitto.db, restarted the service, but the ghost switching still happens.
@ascillato - would you like to re-open this or would you rather I created a new issue?
Debounce doesn't solve the issue at best it lowers the frequency.
I've just done a full reset on the switch that is doing it the most and set it up with full logging. I will upload the logs when it switches.
I was wondering if it would be possible to have a firmware that ignored the first press, waited 40 and then resampled the sensor. Would this be possible?
No ghosting on all 3 of my T1 3CH US units for 2 days now. So looking promising. I did the following:
Ok took 20 minutes for the first ghost press to occur
06:50:54 WIF: Connected 06:51:14 WIF: Checking connection... 06:51:14 WIF: Connected 06:51:14 APP: Button1 multi-press 1 06:51:23 SRC: Button 06:51:23 RSL: stat/sonoff/RESULT = {"POWER1":"ON"} 06:51:23 RSL: stat/sonoff/POWER1 = ON 06:51:23 CFG: Saved to flash at F4, Count 16, Bytes 3584 06:51:34 WIF: Checking connection... 06:51:34 WIF: Connected
Also it has caused a reset of the device. So it has gone back to a sonoff basic.
Redoing with setoption1 on, SetOption13 on & SetOption32 100
@Bloodyagent - surely modding the hardware shouldn't be necessary though. The stock firmware isn't doing this so there must be a software solution.
@kyemacdonald
I agree but it's a very simple procedure and seems a good temporary solution. However the firmware still needs to be looked at and the issue should be reopened.
Lowering the cap to 16nf does reduce the switch sensitivity considerably, so it's not ideal.
Sigh. This switch is doing it all the time. Basically an hour since the last trigger. Upped debounce from 200 to 500.
I'm going to swap the control board with a spare next to see if it's the control board or maybe the power supply from the relay block.
07:55:05 RSL: tele/sonoff/STATE = {"Time":"2019-06-08T07:55:05","Uptime":"0T00:44:59","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"ON","POWER2":"ON","Wifi":{"AP":1,"SSId":"Skyenet","BSSId":"1C:F2:9A:CA:FE:A3","Channel":1,"RSSI":96,"LinkCount":1,"Downtime":"0T00:00:04"}} 07:55:10 WIF: Checking connection... 07:55:10 WIF: Connected 07:55:15 APP: Button2 immediate 07:55:15 SRC: Button 07:55:15 RSL: stat/sonoff/RESULT = {"POWER2":"OFF"} 07:55:15 RSL: stat/sonoff/POWER2 = OFF 07:55:16 CFG: Saved to flash at F5, Count 31, Bytes 3584 07:55:30 WIF: Checking connection... 07:55:30 WIF: Connected 07:55:50 WIF: Checking connection...
Just tried the latest firmware based on the 2.5.2 core. Still ghost switches.
12:57:41 WIF: Attempting connection... 12:57:42 WIF: Checking connection... 12:57:42 WIF: Connected 12:58:02 WIF: Checking connection... 12:58:02 WIF: Connected 12:58:13 APP: Button1 immediate 12:58:13 SRC: Button 12:58:13 RSL: stat/sonoff/RESULT = {"POWER1":"ON"} 12:58:13 RSL: stat/sonoff/POWER1 = ON 12:58:13 CFG: Saved to flash at F9, Count 38, Bytes 3584 12:58:22 WIF: Checking connection... 12:58:22 WIF: Attempting connection... 12:58:22 WIF: Connecting to AP1 Skyenet in mode 11N as sonoff-2245... 12:58:23 WIF: Checking connection... 12:58:23 WIF: Attempting connection... 12:58:24 WIF: Checking connection... 12:58:24 WIF: Attempting connection... 12:58:25 WIF: Checking connection...
status 0
: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.