[bug] Random wifi disconnection (and no reconnection behind)

albaintor commented 3 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Description

Hi,

I have random wifi disconnections, which can be normal in a wifi environment, however the reconnection fails. A wifi icon with a stroke appears on the screen then. I don't know how exactly it was fixed but when I went to wifi settings to list all available networks, the connection went back, this would mean that my action unlocked the reconnection process. Please note that I configured a fixed IP from my router to the remote so that I can connect easily. Here are the logs and some hints :

The problem starts at line 5854 at 13:44:05 with : "wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:e9:31:23:ba:e8 reason=2"
Then 13:44:06 "WifiEvent: SCAN_STARTED" right after but no reconnection occurs
During 30 minutes, all sort of error messages due to lack of connectivity such as Failed to connect to host: Network is unreachable
Then line 338 at 14:23:04 WifiEvent: SCAN_STARTED => this event is probably due to my action in the remote while going into wifi settings
This time it seems to work : "Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant"*
Integrations reconnect, and right after the commands are processed correclty

2024-03-15 13:44:05.825727 +00:00   intg-androidtv  INFO    DEBUG:ucapi.entities:[configured]: entity '00044BE87F74' attributes updated
2024-03-15 13:44:05.825727 +00:00   intg-androidtv  INFO    DEBUG:driver:Android TV disconnected: 00044BE87F74
2024-03-15 13:44:05.821127 +00:00   intg-androidtv  INFO    INFO:tv:00044BE87F74 notified that is_available: False
2024-03-15 13:44:05.749865 +00:00   core    NOTICE  WifiEvent: SCAN_STARTED
2024-03-15 13:44:05.717771 +00:00   avahi-daemon    INFO    Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::d217:69ff:fe85:26d7.
2024-03-15 13:44:05.716733 +00:00   avahi-daemon    INFO    Leaving mDNS multicast group on interface wlan0.IPv6 with address fd31:fa02:cfb7:f54c:d217:69ff:fe85:26d7.
2024-03-15 13:44:05.715541 +00:00   avahi-daemon    INFO    Withdrawing address record for fd31:fa02:cfb7:f54c:d217:69ff:fe85:26d7 on wlan0.
2024-03-15 13:44:05.713226 +00:00   avahi-daemon    INFO    Registering new address record for fe80::d217:69ff:fe85:26d7 on wlan0.*.
2024-03-15 13:44:05.712025 +00:00   avahi-daemon    INFO    Registering new address record for fd31:fa02:cfb7:f54c:d217:69ff:fe85:26d7 on wlan0.*.
2024-03-15 13:44:05.710714 +00:00   avahi-daemon    INFO    Joining mDNS multicast group on interface wlan0.IPv6 with address fd31:fa02:cfb7:f54c:d217:69ff:fe85:26d7.
2024-03-15 13:44:05.706787 +00:00   avahi-daemon    INFO    Leaving mDNS multicast group on interface wlan0.IPv6 with address 2a01:cb04:b18:3700:d217:69ff:fe85:26d7.
2024-03-15 13:44:05.705574 +00:00   avahi-daemon    INFO    Withdrawing address record for 2a01:cb04:b18:3700:d217:69ff:fe85:26d7 on wlan0.
2024-03-15 13:44:05.701342 +00:00   systemd-timesyncd   INFO    No network connectivity, watching for changes.
2024-03-15 13:44:05.696218 +00:00   wifi    INFO    wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
2024-03-15 13:44:05.692602 +00:00   systemd-networkd    INFO    wlan0: DHCPv6 lease lost
2024-03-15 13:44:05.680545 +00:00   wifi    INFO    wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2024-03-15 13:44:05.675894 +00:00   core    NOTICE  Network changed: link_name: wlan0, operational_state: unknown, carrier_state: unknown, online_state: offline
2024-03-15 13:44:05.673900 +00:00   systemd-networkd    INFO    wlan0: DHCP lease lost
2024-03-15 13:44:05.670956 +00:00   systemd-networkd    INFO    wlan0: Lost carrier
2024-03-15 13:44:05.669776 +00:00   avahi-daemon    INFO    Interface wlan0.IPv4 no longer relevant for mDNS.
2024-03-15 13:44:05.666879 +00:00   avahi-daemon    INFO    Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.136.
2024-03-15 13:44:05.656363 +00:00   avahi-daemon    INFO    Withdrawing address record for 192.168.1.136 on wlan0.
2024-03-15 13:44:02.746638 +00:00   core    NOTICE  WifiEvent: DISCONNECTED
2024-03-15 13:44:02.616254 +00:00   wifi    INFO    wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:e9:31:23:ba:e8 reason=2

UCR2_logs_2024-03-15.zip

How to Reproduce

Not systematic. It seems to start with this error "wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:e9:31:23:ba:e8 reason=2" from wifi module.
My remote was not in the dock
I had an activity launched and running (bluray player) and the activity was configured to prevent sleep mode

Expected behavior

Reconnection after disconnection :

the network may be unreachable : this was not my case as I was working through VPN session with my PC near the remote, but sometime the router may be faulty or reboot
In that case the remote should try to reconnect to the configured network until it succeeds even if is off the dock

System version

1.7.5

What part of the system affected by the problem?

Core

Additional context

No response

albaintor commented 3 months ago

Hi again, I had the disconnection again today. Same behaviour : for an unknown reason the remote looses wifi connection, and it does not look after recovering the connection. The buttons press won't raise any error (no red error tooltip on upper border). I didn't have these disconnections before, or not so frequently UCR2_logs_2024-03-21 (1).txt

albaintor commented 2 months ago

Update : this problem is related to the way that the remote handles wifi mesh networks. In my case this causes frequent dropouts or connections loss (probably while switching to one AP to another, and failing). Only androidtv integration won't reconnect correctly but I already raised an issue for that https://github.com/unfoldedcircle/integration-androidtv/issues/40

unfoldedcircle / feature-and-bug-tracker