Sonoff Basic R2 with GPIO3 breakout for light switch

[steeegraham]

HISTORY: For years I've been using Sonoff Basic R2 v1.0 's as Smart switches in my house and usually they work without issue. Occasionally (2-3 months) one or two become invisible to Alexa and HomeAssistant but still operate via the switch attached to GPIO3. To fix, I have had to turn the power for the lighting ring on and off at the fusebox then they work as normal again. <This level of repair is acceptable to me. I realise I could probably address why it's losing connectivity via MQTT by looking at interference etc but restarting the device this infrequently is fine. Out of 5 Sonoff's, only 2 tend to need attention 'infrequently' so not trying to fix the cause.>

AIM: Instead I've been trying to find a way to Restart a singular Sonoff so I don't have to turn all the lights on the ring on and off. Since the current switches are standard on/off toggle switches, I thought I'd be able to set rules so that when the switches were toggled a number of times within a given timeframe it could trigger a rule to "Restart" the Sonoff... so far, I have failed dismally!

SETUP: Each existing Sonoff Basic R2 v1.0 Hardware is configured as follows:-
Flash: Sooff Tasmota 6.6.0 by Theo Arends (sonoff.bin from 5+yrs ago)
Module type: Sonoff Basic (1)
GPIO03 Serial In - Switch7 (15)

SwitchMode1 0
SetOption1 OFF
SwitchTopic ""
No Rules set

TESTING: I want to add 2 additional rooms so have flashed 1xSonoff Basic R2 with my existing 6.6.0 sonoff.bin & 1xSonoff Basic R2 with current Tasmotizer offering of tasmota.bin Tasmota 15.1.0 (release-tasmota) by Theo Arends
Both appear to operate the same, whether I choose module "Sonoff Basic Module" or "Sonoff BASICR2" as the same GPIO pins are broken out... mainly GPIO3 but I've also experimented with GPIO2(can't be low when restarted but pulled high by default as long as a push button is connected rather than a switch which is Closed!)

PROBLEM: Set rules don't display so I don't see RUL: I don't see switchstate results, just MQT ones. Rules aren't applying and I can't work out why. Any help would be greatly appreciated!

Logs and further detail of what I've tried I'll be glad to add

[sfromis]

Hard to guess what happens with your rules when you do not post them. Maybe they were just not enabled, or have syntax errors. The command Rule0 can be useful to display all 3 rule sets, including whether they are enabled.

BTW. One plausible issue with old Sonoff Basic (especially the R2) is that it is just not good hardware, "more than a few" users are experiencing trouble.

[steeegraham]

Hi Sfromis, thank you so much for replying. I've tried a lot of rules. The basis of them is this:-

Rule1 ON Switch7#state=1 DO backlog Add1 1; ruletimer1 10 ENDON
Rule2 ON Rules#Timer=1 DO Add1 0 ENDON
Rule3 ON Add1#Data>=3 DO backlog Add1 0; restart 1 ENDON

So it's supposed to set a variable called Add1 + 1 on every press until it equals 3 then restart. If the timer gets to 3 ie. it's not pressed 3 times within the time then the variable Add resets to 0.

That's just one of the many rules I've tried. I guess, I'm asking if anyone has a similar experience and has a solution. If not, can anyone help me find one.

[sfromis]

To apply to further rules, your rule set 2 should use Backlog too (even if only one command). This requirement is mentioned in this section:
https://tasmota.github.io/docs/Rules/#examples-of-available-triggers

While your trigger Add1#Data should be ok in your context, the general trigger for updates to vars is like Var1#State

Not clear why you have those Add1 0, but if you want to reset the variable to 0, you should use Var1 0 instead.

In general, watch the console closely to see what happens (or not). For some types of things, getting extra detail with Weblog 3 first can be useful.

Also, you should not skip numbers when assigning gpios, like your Switch7 - if that's not just typo here. In case it really was Switch1, your SwitchMode1 0 means toggle mode, where you do not get the value 1 when pushed, but 2 for toggle.

[steeegraham]

will test switch# but found switch7, historically to work. Probably before I understood the defaults. Thanks for your reply.

[steeegraham]

btw, u are a legend for replying. Thank you so much