bkbartk
(Bkbartk)
August 24, 2024, 7:42pm
1
I have some devices with restore mode always_on
light:
- platform: rgbww
id: light_rgbww
name: Light
color_interlock: true
cold_white_color_temperature: 6500 K
warm_white_color_temperature: 2700 K
red: output_red
green: output_green
blue: output_blue
cold_white: output_cold
warm_white: output_warm
restore_mode: ALWAYS_ON
but when there is a wifi hick up like my router restarts, sometimes afterwards the light suddenly turns on. I think this shouldn’t be the case.
can I changes this behaviar?
I added reset_reason
for debugging, but of course while trying to get any info if the device might accidentally restarts, the issue doesn’t occur.
It’s possible the esp can’t reconnect to WiFi/api and is rebooting itself after the wifi issue (15min by default).
If you add an uptime:
sensor that will help confirm.
bkbartk
(Bkbartk)
August 25, 2024, 1:36pm
3
That would make sense. However, I changed this period to 12hours. And also. The devices are marked unavailable for 1:30 minutes.
I will add uptime later. I think it’s helpful as well.
bkbartk
(Bkbartk)
August 25, 2024, 2:55pm
4
I could test now, and is seems like the device reboots, with reset reason
2024.8.0|Version: v1.6.0 on generic-bk7231n-qfn32-tuya, compiled at Aug 25 2024 16:38:44, GCC 10.3.1 (-O1)|Reset Reason: WDT Reset|Chip Name: BK7231N|Chip ID: 0x00e4ce3a|Flash: 2048 KiB|RAM: 256 KiB
And now I found that WDT seset means that something didn’t respond in a specific amount of time, but it’s different from the reboot_timeout.
Do you know if and how to change this behaviar?