[Solved] Module with OpenBeken - relay clicks intermittently after firmware upload

Hello.
And again I come to you for help.
I have acquired the following module:
.
.
.
.
.

After uploading OpenBeken (all automatic, so to speak) everything is ok except for the relay, which clicks intermittently all the time - connects and disconnects itself. The relay can be switched on/off between its clicks either by pressing a button or via the web, but it still clicks.
After reverting to the original firmware it works fine.
This is how the flaher configured it:
.
What could be the reason for this behaviour?

Adam

I am sending his original batch as an attachment.

To start with, I suggest doing some separate tests to narrow down the source of the problem.
1. set the pin from the relay to AlwaysHigh instead of Rel. Does the relay continue to "jump" or is it in the same state 100% of the time (probably closed)?
2. set the relay pin to AlwaysLow instead of Rel. Does the relay continue to "jump" or have the same state 100% of the time (probably open)?
3. remove the TglCHanOnToggle role (or change its channel to e.g. channel 5, as you don't use it, this will detach it from the relay). Does the relay continue to switch randomly? (Obviously, restore the Rel role to the relay for the duration of this test).
4. are you using PowerSave? Enable PowerSave (e.g. enter PowerSave 1 in the startup command and perform a reboot) and write if the problem continues. PowerSave is needed with such devices because they have quite weak power supplies, otherwise you are waiting:
How to fix a smart device that crunches, squeaks and makes strange noises? .

I will start from the end:
Ad4 so I create an autoexec and in it PowerSave 1 and startDriver BL0942. (clicked)
Ad1 yes 100% of the time closed.
Ad2 yes 100% of the time open.
Ad3 I didn't manage to test because after the first 2 tests the relay calmed down.
Now reboots or powering down and powering up the module again do not result in the relay clicking.
Everything works as it should. I wonder what was the reason for this clicking?

Thank you for your help.

Adam

Well, the tests are inconclusive. There are two options.
a) either a weak power supply is to blame - PowerSave 1 helped, Remember that PowerSave 1 will only work after a reboot.
b) either TglChanOnToggle has interference, which has already been reported, and people have either fixed this in code or added a resistor to this pin. This is a bit problematic, because the OBK is one, and there are many devices and they have different designs, so TglChanOnToggle on one series of devices works better and on another it works worse

As far as PowerSave is concerned - always after uploading openbeken when the module is still plugged into usb I run it and set everything up including creating an autoexec and in it the aforementioned PowerSave and startDriver. Then there are a few reboots of the module. After all this, I desolder the cables and connect after 230V to calibrate the measurements. And then the relay started clicking in this exemplar. I did this several times because I had uploaded different versions of openbeken and it always clicked tem relay and 100% PowerSave was on.
As for TglChanOnToggle, as I'm still inexperienced I don't know what it's responsible for 😉 .

By the way, let me ask another question about calibration. I have always measured the voltage with a meter at the beginning and set it with VoltageSet, then connected a 300 watt ordinary light bulb measuring the current and of course CurrentSet and PowerSet and the measurements were good including reactive power measurements, apparent power and the PF was equal to 1. In this module my PF has split and it is 0.99 and the reactive power is 16-17vars. In addition when the relay is switched off there are these readings:
.
How do you set this up?

And another question this time about the Home Assistant - after restarting the HA I have all openbeken in this (unknown) state:
.


The measurements are displayed correctly and the status of the switch is unknown. Just switch it off/on in HA and it is already correct. Can something be done about this?

Adam

BL0942 sends us measurements and we can only receive them. Your problem has already been reported and the only solution we have come up with is a flag:
.
Do you have it enabled? Rather not?


As for relay states, do you have it enabled to publish its state every minute or so?

p.kaczmarek2 wrote:

Rather not?

.
Already included, thank you.

p.kaczmarek2 wrote:

have you enabled it to publish its status every minute or so?

.
Unfortunately I don't know how to do/enable this .

To check:
1. type the command in the device:
.
this you have to execute in real time, NOT in autoexec.bat, but in the "execute command" or in the web app in the console.
Wait, does it appear in HA status correctly?
2. enable flag:
.
Is the problem solved after this?

p.kaczmarek2 wrote:

does the status appear correctly in HA?

.
Yes, the status appears correct.

p.kaczmarek2 wrote:

Is the problem solved afterwards?

.
Yes, you are great. Thank you very much.

Greetings
Adam

Explanation in posts above 😉.