You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Constant Disconnected, reason: 256(Disconnected) in OpenBeken Web Application logs.
Constant Disconnect Messages from MQTT
Constant Unavailable Logs from Home Assistant
2 devices will disconnect with the 256 reason within milliseconds of each other, usually every 5 minutes, sometimes less. This has been occurring since first installed. adding the 2nd device 6mo later and it syncing up to disconnect almost simultaneously warranted investigation.
Firmware:
Version 1.17.579 thru current (1.17.670)
MagicHome RGB Led Controller + TreatLife SS01S Single Pole Smart Switch
Chip/model: BL602 + BK7231N (respectively)
Device config? N/A
To Reproduce
Steps to reproduce the behavior:
Flash OpenBeken to a device and connect to wifi/mqtt
Logs ( !values have been changed to protect the innocent )
OpenBeken Web Application Logs:
Additional context
I have one BL602 device that I've been using for over 6 months.
I recently purchased another BK7231N device 2 weeks ago.
I have just updated both devices to latest firmware as of today (9/1/24)
PowerSave has been turned off. WatchDog IP has been configured.
Both of these devices will disconnect with the 256 reason within milliseconds of each other, usually every 5 minutes, sometimes less. This has been occurring since first installed. adding the 2nd device 6mo later and it syncing up to disconnect almost simultaneously warranted investigation.
The BK7231N device is literally 6feet in direct line of sight from the UniFi AP. It is not a signal quality issue.
I have multiple Tasmota devices all connected to the same wifi AP that have never had this issue in thier 3 years of use.
This seems to be the issue/cause of these devices triggering on a schedule in HomeAssistant but not actually turning on/off. This is a problem with trying to automate lighting in my 6mo old's bedroom. Please help.
The text was updated successfully, but these errors were encountered:
Describe the bug
Constant Disconnected, reason: 256(Disconnected) in OpenBeken Web Application logs.
Constant Disconnect Messages from MQTT
Constant Unavailable Logs from Home Assistant
2 devices will disconnect with the 256 reason within milliseconds of each other, usually every 5 minutes, sometimes less. This has been occurring since first installed. adding the 2nd device 6mo later and it syncing up to disconnect almost simultaneously warranted investigation.
Firmware:
To Reproduce
Steps to reproduce the behavior:
Logs ( !values have been changed to protect the innocent )
OpenBeken Web Application Logs:
This occurs randomly up to every 5 minutes.
MQTT Events exerpt for BL602 device:
Screenshots
Additional context
I have one BL602 device that I've been using for over 6 months.
I recently purchased another BK7231N device 2 weeks ago.
I have just updated both devices to latest firmware as of today (9/1/24)
PowerSave has been turned off. WatchDog IP has been configured.
Both of these devices will disconnect with the 256 reason within milliseconds of each other, usually every 5 minutes, sometimes less. This has been occurring since first installed. adding the 2nd device 6mo later and it syncing up to disconnect almost simultaneously warranted investigation.
The BK7231N device is literally 6feet in direct line of sight from the UniFi AP. It is not a signal quality issue.
I have multiple Tasmota devices all connected to the same wifi AP that have never had this issue in thier 3 years of use.
This seems to be the issue/cause of these devices triggering on a schedule in HomeAssistant but not actually turning on/off. This is a problem with trying to automate lighting in my 6mo old's bedroom. Please help.
The text was updated successfully, but these errors were encountered: