BK7231N Switches with OpenBK in HA Turning On at 3 AM - Firmware Issue?

Question

Hello!
For months, I have had several switches with BK7231N and OpenBK in their latest versions integrated into HA. Always updated via OTA once a month or so.
The problem is that for some time, some lights have been turning on when waking up.
They are set to remember their last state upon reboot. And I have noticed that they always turn on at approximately the same time, 03:00 am.
Could someone tell me what could be happening?

p.kaczmarek2 · Answer

That's a very strange issue. Do they also reboot at that 03:00 AM? Do they also turn on when you disconnect them from MQTT (clear IP, username, password and client name of your HA)?

4139ggn · Answer

I haven't tried leaving it disconnected from MQTT.But tonight, again. This is the record he leaves in HA.

p.kaczmarek2 · Answer

What about OBK up time?

4139ggn · Answer

is at -1. May it maintain its status

p.kaczmarek2 · Answer

What is -1? It seems that you have misunderstood me. I have asked about OBK uptime, the one that can be read here:

4139ggn · Answer

Okay! Today that I added another device, I realized that this particular one (the one that turns on by itself), when it restarts, turns on. I do not understand why...

p.kaczmarek2 · Answer

You can configure your device to either keep state after restart, or to always set high value after restart, or to set low value after restart. You can also do the same manually in autoexec.bat by executing channel-related commands there.

So, tell me, does the device reboot at that 3AM? You can tell that by looking at the device uptime.

4139ggn · Answer

Today, again.Now I have looked at the connection time:Online for 16 hours, 38 minutes, and 8 secondsFrom what I understand, there has been no reboot....

4139ggn · Answer

Hello! I've been reviewing the history of Home Assistant. And from what I see, every day around 03:01:00 it does this cycle:It became UnavailableIt is turned offIt's onSo it stays on all night...

p.kaczmarek2 · Answer

Maybe you have your router scheduled to reboot at 3AM?

4139ggn · Answer

I have been able to verify that there are MQTT devices that reboot every night and others do not.I have to find out why.Anyway, why doesn't it save its status like the others?

p.kaczmarek2 · Answer

You can set OBK device to remember it's last state. It's possible to configure it in the Configure Startup menu.

4139ggn · Answer

This is how I have it configured...
The same thing has happened to me with some other lamp with OpenBK. But every time I update it, it has disappeared...
But this time no matter how much I update, nothing

4139ggn · Answer

This night there were two lights that turned on. And they have waited a little longer, until 04:00:00.
Both devices run OpenBk. And I have found that they have been connected for more than two days.
That is, they have not been restarted...
Any ideas?

p.kaczmarek2 · Answer

As I said, disable MQTT and check if they still turn on.

If only MQTT devices reboot, then check your Home Assistant uptime and Home Assistant logs, I don't think that OBK device can turn itself on its own, I think HA must be sending something.

You can also post device config here. Which drivers you have enabled? Anything like DGR, Wemo? Still, you said it does not happen without MQTT, right?

4139ggn · Answer

No, that is connected to MQTT.Tonight I'll disable mosquitto to see what happens.But I checked again and it seems that something happens between 3 and 4 at night.Many devices become unknown and reconnect a few seconds later. I don't know if it's some kind of glitch that does something and throws everything away for a few seconds.Mosquitto perhaps?

4139ggn · Answer

Hello, good!Well, I updated to version 1.17.405 and that power-up disappeared at 03:00.But... This morning when I woke up, I had another switch on!I have reviewed it, and I want to remember that it was at version 1.0.0, so I have updated it to the latest (1.17.442).What happened? It is true that this one had already done it once. But since the last time I updated it, it stopped doing that.Why did it do it again today? Why at 03:00?In the image, it looks like three different lights (03:00, 04:00, and 05:00). We were all asleep at home.

4139ggn · Answer

Today when I woke up, I had two switches on!
I have updated again to the latest version (1.17.424).
I have discovered that when the switch is reset, it starts with the switch on!

I don't understand what's wrong...

p.kaczmarek2 · Answer

Can you setup a clear instance of Home Assistant and check if it also restarts then? Added after 47 : You have set it to remember last state..

4139ggn · Answer

I do not know what you mean Yes, if it is off, let it be off and the other way around. But if I restart it, it turns on!

4139ggn · Answer

Today without any update two switches have turned on. I have updated them again to the latest version. And when it reboots with the update, they turn on again. I have looked at the OpenBK registry and what catches my attention is what is marked in bold. I don't know why the state changes when it restarts.

p.kaczmarek2 · Answer

This is a very big progress, @4139ggn ! But you haven't marked enough on your log dump.

Here, look:

The fragment in red frame indicates that your HA sends value 1 to OBK just when OBK connects to it.

Now, the question is, why HA sends it?

I am not sure if I have asked about it already, but have you tried to enable "retain" on a device, in flags settings? Maybe it can help as a work around.

4139ggn · Answer

Where should I look at this, what do you say about retaining?In the configuration.yaml the configuration is this:

p.kaczmarek2 · Answer

Wait, so you're not using automatic hass discovery? You can try to set retain to true, instead of false.

4139ggn · Answer

I have switched to automatic detection of Home Assistant.
I have also made sure to have Flags enabled:
"Flag 21 - [MQTT] Retain power channels (Relay channels, etc)"
I restart the device and it turns on.
I have tried restarting Mosquitto. And it also lights up!

Nakano · Answer

Hello, have you managed to solve the problem?
I have a similar situation, only it is not about the lights, but about the gate. Every call after losing the connection to the MQTT triggers the switches (2ch) and opens or closes the gate.

jtauscher87 · Answer

I have the same problem, I have two Bekens with identical config/flags etc and still, one is turning on after reboot or wifi loss, whereas the other device works like a charm. Retain true/false doesn't make any difference. As soon as it connects to HASS MQTT broker the device turns on.

Info:MQTT:MQTT client in mqtt_incoming_data_cb data is 1 for ch 0
Info:GEN:CHANNEL_Set channel 0 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 0 
Info:MQTT:Publishing val (303 bytes) to tele/GarageLicht/STATE retain=0
Info:MQTT:Publishing val 1 to GarageLicht/0/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic tele/GarageLicht/STATE
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic GarageLicht/0/get
Info:MQTT:Publishing val (303 bytes) to stat/GarageLicht/RESULT retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic GarageLicht/0/set
Info:MQTT:MQTT client in mqtt_incoming_data_cb data is 1 for ch 0
Info:GEN:No change in channel 0 (still set to 1) - ignoring

p.kaczmarek2 · Answer

Well this clearly means that your Home Assistant send value 1, doesn't it?


Info:MQTT:MQTT client in mqtt_incoming_data_cb data is 1 for ch 0
Info:GEN:CHANNEL_Set channel 0 has changed to 1 (flags 0)

How is it configured in HA?

jtauscher87 · Answer

Its configured as suggested. Retain true/false doesn't make any difference. Its clearly a mosquitto fault but i have no clue why one bekens works fine and one doesn't.

# GarageLicht:
- unique_id: "GarageLicht_relay_0"
name: "GarageLicht 0"
state_topic: "GarageLicht/0/get"
command_topic: "GarageLicht/0/set"
qos: 1
payload_on: 1
payload_off: 0
retain: true
availability:
- topic: "GarageLicht/connected"

BK7231N Switches with OpenBK in HA Turning On at 3 AM - Firmware Issue?

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary