RocketController - Relays keep going on and off

[dac2020]

I have a RocketController 4 relay device that is running the latest Tasmota.
https://rocketcontroller.com/product/controller-esp32r4/

I have it connected nearby so can hear it and noticed that relays keep going on and off without my sending any commands.
I have two questions which I cannot seem to find answers for.

1: What could be causing the interference since this is what seems to be happening and how could I monitor that?

2: Is there a way to subscribe to this device, to get only a message if a relay status has changed, on or off.
By having the ability to monitor only those changes, maybe I could correlate those with something else going on nearby.

[sfromis]

Read the console, after setting Weblog 3 for details, to see what Tasmota is doing.

[barbudor]

Rules may have been installed by the manufacturer as part of their factory testing.
Do you know if you have a RF module installed ? I thought they were not available yet.
Whatever, if you do not intend to use RF, you can remove the RFrecv from GPIO27 (replacing by None)

[dac2020]

Not sure if there is an RF module installed on these. I do control it using an app but not RF buttons.
A second one I bought from Aliexpress was junked so cannot compare against the other.
I used your suggestion Rule0 " so I'll keep an eye on it.

[sfromis]

What you posted clearly shows that the device was picking up something as RF input, which makes it implausible that no RF module was installed.

[barbudor]

It's called noise
Not a proof that there is a module
If you look at the other discussion I reported that mine also went crazy with rf received messages while no rf is installed

[dac2020]

So mainly spurious then if I'm using the term correctly. Something that the board is picking up causing it to consider interference as commands.

I've changed it as above and so far, no status change today so seems to be solved.

[dac2020]

So I'm back on this topic because something comes to mind and I wonder if someone could provide a little more info.

I understand that some functions are outdated, no longer used and can cause the problems I saw above.

However, it brings up the question of why each outlet might have its own RF function if that's the case.
And, if this is outdated, how was it used in the past?

I ask because I cleared all of the rules on all of my Tasmota devices without even thinking about it and wondered if I might have cleared other rules that might have been important to functionality.

[dac2020]

Ok, so there is nothing to lose by removing all rules on all Tasmota devices then?
And 'just do not have GPIO pins' means configuring the rule right?

[sfromis]

There can be much to lose by removing all rules, you first have to review what they're doing. And "do not have gpio pins configured" has absolutely nothing to do with rules, it has to do with configure template/module. If you have irrelevant RF pins configured, unconfigure.

[dac2020]

I'm using the template so don't have any custom settings.
It was suggested in this thread that I use 'rule0 "' on the relay device and since the others seemed to be getting noise also, I did the same to all of them. So, all of them have the same default rules.

19:49:13.349 MQT: stat/84F3EB647217/RESULT = {"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
19:49:13.398 MQT: stat/84F3EB647217/RESULT = {"Rule2":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
19:49:13.441 MQT: stat/84F3EB647217/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}

Rule 1 was the culprit but after using the clearing command, these continue to exist. Does it mean that Tasmota has these by default then?

[sfromis]

The whole template is custom settings, where you can modify what you want, like unconfiguring noisy pins.

And yes, it is perfectly possible that commands to set initial rules are part of the custom binary from them, reappearing after a full reset. My preference would be to upgrade to standard Tasmota builds, but I don't know if they did other things with their custom binary, which then might be missing.

[barbudor]

RocketController doesn't need any specific rule to work
You may need rules for your own usage for local automation but nothing mandatory for RC to work as intended

Rule 1 was the culprit but after using the clearing command, these continue to exist. Does it mean that Tasmota has these by default then?

Tasmota as 3 Rules set. This is what the command Rules0 shows you. IT will always show you those 3 lines.
What is key is what is shown for each ruleset:

• The "State" telling if the ruleset is active
• The "Rules" which list the rules inside the ruleset
• The "Once" parameter as well as some other details about memory used
  In your case, all 3 ruleset are empty and OFF

Here is a exemple of what Rule0 display on one of my plug with energy metring. Rules are intended to power off the plug once the power consumption fall below a given threshold:

22:42:48.974 CMD: rule0
22:42:48.982 MQT: stat/skt-barbuxps/RULE = {"Rule1":{"State":"ON","Once":"ON","StopOnError":"OFF","Length":94,"Free":417,"Rules":"on Energy#Power<%Mem1% do ruletimer1 %Mem3% endon on Energy#Power>%Mem2% do ruletimer1 0 endon"}}
22:42:49.000 MQT: stat/skt-barbuxps/RULE = {"Rule2":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":35,"Free":476,"Rules":"on rules#timer=1 do power off endon"}}
22:42:49.016 MQT: stat/skt-barbuxps/RULE = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}

You can read the rules that are in ruleset 1 and ruleset 2 which both are ON. Ruleset3 is empty and OFF