Shelly2 ghost switching with shutter switch

[chrizza87]

Describe the bug
There is a ghost switching for shelly2 device. I installed the shelly2 behind a jarolift THOR shutter switch (link: https://www.jalousiescout.de/Rolladen-Zeitschaltuhr/Jarolift-Thor-Rollladen-Zeitschaltuhr.html). If i use the shelly2 profile the shelly2 relay switches at a certain time continuously (like 5 times per second). I also tried the generic device with Switch1 and Switch2, also with Switch1n and Switch2n. With the n it was even worse because, there the shelly switched once without a switch attached.
I tried the original shelly2 firmware at first. There was no ghost switching, but the attached jarolift switch didn't work properly. The switch state was not recognized corretly. Thats why a flashed the tasmota firmware. There the switch works perfectly, but i have this annoying ghost switching, which only stops when i disconnect the switch. Sometimes it works perfectly for a day and the out of the blue the relay switches continuously
I activated the debug mode for logging and there i saw that the switch is the src of the switching on/off.

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

• Searched the problem in issues and in the wiki
• Hardware used : Shelly2
• Development/Compiler/Upload tools used : Arduino Board and Platform IO for Windows
• You have tried latest release or development binaries? : yes
• Provide the output of commandstatus 0 :

14:17:23 MQT: livingroom/windowShutters/stat/STATUS = {"Status":{"Module":18,"FriendlyName":["livingRoomWindowShutters","livingRoomWindowShutters2"],"Topic":"windowShutters","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}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"xxxxxxxx","RestartReason":"Software/System restart","Uptime":"1T15:08:58","StartupUTC":"2018-12-22T22:08:25","Sleep":50,"BootCount":18,"SaveCount":328,"SaveAddress":"F4000"}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS2 = {"StatusFWR":{"Version":"6.4.0.1(sonoff)","BuildDateTime":"2018.12.17 21:45:20","Boot":31,"Core":"2_4_2","SDK":"2.2.1(cfd48f3)"}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["XXXXXXX",""],"TelePeriod":300,"SetOption":["0000C009","558180C0","00000000"]}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS4 = {"StatusMEM":{"ProgramSize":522,"Free":480,"Heap":21,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000407","0FDAE794","240383A0","23B617CE","00003BC0"]}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS5 = {"StatusNET":{"Hostname":"windowShutters-3511","IPAddress":"192.168.178.67","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.178.1","Mac":"CC:50:E3:13:4D:B7","Webserver":2,"WifiConfig":4}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS6 = {"StatusMQT":{"MqttHost":"xxx.xxx.xxx.xxx","MqttPort":1883,"MqttClientMask":"livingRoomWindowShutters_%06X","MqttClient":"livingRoomWindowShutters_134DB7","MqttUser":"DVES_USER","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS7 = {"StatusTIM":{"UTC":"Mon Dec 24 13:17:23 2018","Local":"Mon Dec 24 14:17:23 2018","StartDST":"Sun Mar 25 02:00:00 2018","EndDST":"Sun Oct 28 03:00:00 2018","Timezone":"+01:00","Sunrise":"08:42","Sunset":"16:57"}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS10 = {"StatusSNS":{"Time":"2018-12-24T14:17:23","Switch1":"ON","Switch2":"ON"}}
14:17:23 MQT: livingroom/windowShutters/stat/STATUS11 = {"StatusSTS":{"Time":"2018-12-24T14:17:23","Uptime":"1T15:08:58","Vcc":3.586,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"FRITZ!Box 7390 CS","BSSId":"24:65:11:50:BE:20","Channel":4,"RSSI":76}}}

To Reproduce
Steps to reproduce the behavior: Flash shelly2 with tasmota, attach the mentioned switch (can happen with another one too. This id don't know) and wait....

Expected behavior
Shelly2 works like the sonoff devices without ghost switching the relay continuously after a certain time

Additional context
Switch is attached like described in the shelly docu.
N -> N
L -> L
O1 -> Shutter_Down
O2 -> Shutter_Up
S1 -> Switch_down
S2 -> Switch_up
.

(Please, remember to close the issue when the problem has been addressed)

[arendst]

Thx for the info. Needs investigation but I'm afraid I need info from Allterco as I think additional GPIO's may be involved but I do not own the schematics.

[chrizza87]

Okay thanks for the quick reply. I hope you can gain some knowledge 👍 I will wait an update ;-)

PS: Happy Christmas!

[arendst]

BTW you might want to experiment with the switch debounce delay. it is currently set to 50 milliseconds.

Use command switchdebounce 100 to change it to a less sensitive value which might work better in your case. The value can change up to 1000 milliseconds.

As you also noticed the n option makes it worse, due to not using input pullup, I suggest to go back to module Shelly 2 (which uses pullup) and try the above setting.

Pls let us know if it makes any difference.

[chrizza87]

okay thank you. I will try it and report back

[chrizza87]

Hey @arendst,
after one day so far it works. There was no more ghost switching until now. I will investigate it.

I added a section for this topic in the shelly wiki: https://github.com/arendst/Sonoff-Tasmota/wiki/Shelly-1-and-2

Hope this is okay ;-) I will close this issue, but it would be great if you can keep me posted if you have new scematics from Allterco.

Thanks in advance and happy holidays!

[chrizza87]

Now after 26 hours the issue has come back -.-

[arendst]

But does it come back once or more often?

If so, increase the debounce and test again.

[arendst]

Just updated the switch debounce code to take jitter in account between input state probe times.

Pls try again using the default switch debounce time of 50 milliseconds and report back.

[chrizza87]

sorry was on tour on the holidays. It switched several times Up and Down. It stopped when a detached the switch again. I will try your proposal.

[ascillato2]

@chrizza87 please, try with latest Tasmota from today from http://thehackbox.org/tasmota/

[chrizza87]

thx @ascillato2, i will try it

[ascillato]

@chrizza87 please, try with latest Tasmota from today (6.4.1.2) (new updates from Theo) from http://thehackbox.org/tasmota/

[chrizza87]

thx @ascillato2 i updated the firmware and will report back!

[chrizza87]

ghost switching is still happening. not mutiple switches after another. Now just switching once.

I have upgraded to the latest firmware and set the debounce rate back to 50

[arendst]

If still ghost switching try the following:

1. Use the latest dev release (v6.4.1.3) as of 20181230
2. Select Shelly 2 as module
3. Set SwitchDebounce to 51. This will enable a feature that will keep current state 1 as long as there are no state change 0 probes within 50 mSec.
4. If no solution try Set SwitchDebounce to 52. This will enable a feature that will keep current state 0 as long as there are no state change 1 probes within 50 mSec.
5. If still fails set SwitchDebounce to 100. This will disable the previous options from bullet 3 and 4 but increase probe samples to 10.

This may take some time for testing but try to report back what worked best.

BTW I cannot test this as my Shelly 2 works as expected without any ghost switching while using very short leads to the switches and no "strange" loads.

[chrizza87]

Thank you very much i will try it. Could be an issue with the electric circuit, too. I have orderd some capacitors to test this. Because with LEDs for example you have sometimes a strange behaviour when you have inteferences in your elctric circuit. The LED will blink or glow. With the capacitor you can fix this problem. I will report back!

[chrizza87]

Hey @arendst, i tried the third approach. so far there was ghost switching just once and i discovered, that this was after a restart of the module. It had set the PowerOnState to 0 ({"PowerOnState":0}), but the relay 2 was set to ON after the restart.

[arendst]

Great.

Could you find in the log if relay 2 was set to ON externally (by retained message)?

[chrizza87]

i must add an logserver an my raspberry. i just have the console in the webinterface right now.

In the last 30 minutes the module has restarted 2 times, first due to "Hardware Watchdog" and second due to "Software Watchdog".

The second relay was switched on in both restarts. I tried cut the power off and force a restart, there the relay hasn't switched.

Very strange.

[ascillato]

Hi, the log can be seen in the console of Tasmota in the webui. No need to set up a syslog for that test.

You can use the command weblog 4 to have more debug information. If you hace a retained message you will see SRC:MQTT so the source of your command is mqtt. Or you will see SRC:SWITCH if the command came from the switch.

The 2 restarts you suffer is bad flashing. You shouldn't have any type of watchdog restarts. Sorry but you need to erase all flash with esptool.py (as explained in the wiki) and flash again with esptool.py the precompiled bins from development branch at http://thehackbox.org/tasmota/

[chrizza87]

but you can just see the current logs, when you open the page. It took me one minute after the ghost switching to look at http page of the module. Or is there a way too see older logs?

Okay i updated the firmware 2 days ago via "firmware update". I will erase the flash and flash it again.

[ascillato]

The retained messages happens only when the device boots up, so after the device is on, you can go to the console and you can see if there is any SRC: as previous post (only is you have set weblog 4 before restarting)

[chrizza87]

okay thank you. i will try this too. :-)

[chrizza87]

this is what a get after restart

CFG: Loaded from flash at F5, Count 370
00:00:00 SRC: Restart
00:00:00 Project sonoff livingRoomDoorShutters Version 6.4.1.4(1fb7993-sonoff)-2_4_2
00:00:00 SRC: Switch
00:00:00 RSL: livingroom/doorShutters/stat/RESULT = {"POWER1":"ON"}
00:00:00 RSL: livingroom/doorShutters/stat/POWER1 = ON
00:00:00 RSL: livingroom/doorShutters/stat/RESULT = {"POWER1":"OFF"}
00:00:00 RSL: livingroom/doorShutters/stat/POWER1 = OFF
00:00:00 SRC: Switch
00:00:00 RSL: livingroom/doorShutters/stat/RESULT = {"POWER2":"ON"}
00:00:00 RSL: livingroom/doorShutters/stat/POWER2 = ON
00:00:00 CFG: Saved to flash at F4, Count 371, Bytes 3584

Could there be a problem with my switch? As i mentioned it is this one: https://www.jalousiescout.de/Rolladen-Zeitschaltuhr/Jarolift-Thor-Rollladen-Zeitschaltuhr.html

[ascillato]

Mmmm, may be the issue is just noise coming from your switch. Please, can you try a normal wall switch?

[arendst]

The switch seems to have all kind of feedback possibilities like "motoranfrier". This may be the cause of the switch commands you see as tries to actuate the motor.

You might want to try to change the switch for a "normal" pushbutton Up/Down and see if these "ghosts" switches still happen.

[chrizza87]

Thx for the reply. I will test it after my holiday on thursday. Would be a pity, if i can't use the switch because it has a light sensor to close the shutters when the sun is shining into the room.

I will test it and report back

[ascillato2]

Ok. I will put the issue ON HOLD up to you have time to test another pushbutton. Thanks

[ahmeaqas]

Have a look on to Ghost / Random Switching on Sonoff Devices (MQTT Retained)