Skip to content

WiFi fails to reconnect auto or manually after it was out of range even after going back into range. #83

Closed

Description

@just4747

Not only does Wifi not seem to automatically attempt to reconnect to saved network on its own after getting back in range (Wifi was always turned on) but also will not even reconnect after several attempts to manually reconnect. The only way to get it reconnected is so toggle Wifi off and back on again and then it connects fine. Has happened several times to me now. Just submitted an error report about a minute ago. Install ID is A204F45A.

Also generally have been having issues with Wifi range in general. Maybe this is due to the hardware but I am out of range just slightly in an upstairs room unless I walk to the half of the room closer to the door (router is downstairs). The entire room and further have zero issue with Wifi range for any other device I've ever owned. Seems very limited here.

Activity

  1. SchulzCode commented on Oct 31, 2026

    @SchulzCode
    Owner

    Thanks for the report and the install ID, that made it easy to find. I looked at the logs: when it finally connected, the signal was good (−59 dBm), so the reconnect problem wasn't range. After the player woke up, the Wi-Fi kept searching but never saw your network (it saw four others), and Connect said "not found". Only switching Wi-Fi off and on fixed it, exactly as you described.

    Beta 9.2.5 now does that by itself: if Wi-Fi searches for about a minute without seeing any saved network, the player switches it off and on once (at most every ten minutes until it connects). Your Wi-Fi setting stays as you set it.

    On range in general: the Y2's antenna is small and won't reach as far as a phone or laptop. That's a hardware limit software can't change. Your logs show the signal was fine where it failed, though.

    If it happens again on 9.2.5, please send another error report and reopen this.

  2. just4747 commented on Oct 31, 2026

    @just4747
    Author

    Thanks for the report and the install ID, that made it easy to find. I looked at the logs: when it finally connected, the signal was good (−59 dBm), so the reconnect problem wasn't range. After the player woke up, the Wi-Fi kept searching but never saw your network (it saw four others), and Connect said "not found". Only switching Wi-Fi off and on fixed it, exactly as you described.

    Beta 9.2.5 now does that by itself: if Wi-Fi searches for about a minute without seeing any saved network, the player switches it off and on once (at most every ten minutes until it connects). Your Wi-Fi setting stays as you set it.

    On range in general: the Y2's antenna is small and won't reach as far as a phone or laptop. That's a hardware limit software can't change. Your logs show the signal was fine where it failed, though.

    If it happens again on 9.2.5, please send another error report and reopen this.

    Awesome thanks for the quick fix! Will test out and report back if any issues. Figured the antenna itself wasn't best but glad the bug is fixed as that part didn't seem range related.

  3. just4747 commented on Oct 31, 2026

    @just4747
    Author

    Actually another quick follow up. Upon the update finishing and rebooting, I was connected to Wifi fine and in range and after picking the Y2 up after putting it down for 5 minutes it was again disconnected from Wifi and I don't believe it reconnected on its own. I think it may have said out of range but I forget. I sent another error log for you to check in case it is still FW related. Thanks for checking.

    Edit: Just had major issues getting wifi to allow it to check for updates. Even after clicking the network and turning wifi off and in it just kept not connecting to the saved network and checking for updates kept failing multiple times. Definitely in range. Finally after like 3rd try it connected. Sent another report. Can you check? And then just now after the update reboot, it once again wasn't connected to Wifi automatically.

    And then repeated failures to reconnect to the saved network even after clicking on it manually just now. Over and over. It says Saved - Not in range next to it even when it is in range. Sent one more report.

    Thanks.

  4. SchulzCode commented on Oct 31, 2026

    @SchulzCode
    Owner

    Thanks for the four new reports, they show a lot. Your player is in a very busy Wi-Fi area: it sees around 50 networks, all on 2.4 GHz, and yours is on channel 6 with them. It sees your network fine (about −55 to −61 dBm, a good signal), but when it tries to connect, your router rejects it, over and over: up to 20 times in a few minutes. After each rejection the Wi-Fi waits a little longer before trying again, which is why it can stay disconnected for minutes and shows "Saved – Not in range" in between. The automatic off/on from 9.2.5 did kick in once, but the router kept rejecting it.

    So this isn't range, and it isn't proven to be a fault in the player yet: the router is turning it away. A common reason is "band steering" (also called Smart Connect): routers and mesh systems that use one network name for 2.4 and 5 GHz sometimes refuse devices on 2.4 GHz to push them to 5 GHz. Phones and laptops simply move to 5 GHz, but the Y2 only has 2.4 GHz, so it gets refused until the router gives in.

    The next update will record the router's reason for each rejection, so a report will tell us whether it refuses on purpose or doesn't hear the player at all. Until then, it would help a lot to know:

    • Which router or mesh system do you have?
    • Does it use one network name for both bands (Smart Connect / band steering)? If it lets you set up a separate 2.4 GHz network, does the Y2 connect reliably to that?

    I've reopened this until we know more.

  5. SchulzCode commented on Oct 31, 2026

    @SchulzCode
    Owner

    Beta 9.2.8 is out with that recording. When it fails to join again on 9.2.8, please send an error report right away; it will now show the reason your router gives for each refusal.

  6. just4747 commented on Nov 3, 2026

    @just4747
    Author

    9. Beta 9.2.8 is out with that recording. When it fails to join again on 9.2.8, please send an error report right away; it will now show the reason your router gives for each refusal.

    Will do, thank you.

  7. SchulzCode commented on Nov 3, 2026

    @SchulzCode
    Owner

    Quick status: in Beta 9.3.7 I rewrote the radio part of the player. Wi-Fi on/off, the automatic off/on from 9.2.5 and the order after waking now go through the same program that owns Bluetooth, so the two radios no longer get in each other's way after sleep.

    The part that actually joins your network, where your router kept refusing the player, is the next piece I'm rewriting, so this one isn't fixed yet. If it fails to join again on 9.3.7, a report right after it happens still helps: since 9.2.8 it shows the reason your router gives for each refusal.

  8. just4747 commented on Nov 4, 2026

    @just4747
    Author

    I did seem to be having the stay connected issue later yesterday and sent a log in, but not sure exactly what time it was around and not even 100% sure it was the same issue we've been discussing. But thought I'd mention it just in case. I think at least it had disconnected itself after the device had been laying around and I had a few failed attempts at manually reconnecting it - so might be what we are looking for with the new logging.

  9. just4747 commented on Nov 5, 2026

    @just4747
    Author

    Just now had a definitive occasion where the device just would not connect to Wifi after it had been sitting idle on my desk for a few hours. I clicked on the network twice and was in range. After a bit of trying it failed to connect both times. I toggled Wifi off and on and then it (eventually) connected (I still had to click my saved network manually though - shouldn't it attempt to connect to a saved one on its own, aside from the connection issue?). Just sent a log in right after it happened now.

  10. SchulzCode commented on Nov 5, 2026

    @SchulzCode
    Owner

    Thanks for the report from last night, it showed something new: this time your router did not refuse the player at all. After Wi-Fi was switched on, the player scanned for about 34 seconds without ever seeing your network, so your tap on it answered "not found"; switching Wi-Fi off and on then found it in 3 seconds.

    Beta 9.3.13 does that by itself now: when you pick a network and it isn't found, the player switches Wi-Fi off and on once and tries again (the row keeps saying "Connecting…" meanwhile).

    About connecting on its own: the player does join saved networks by itself while Wi-Fi is on. In last night's log Wi-Fi had been switched off in Settings earlier that evening, a few seconds after it had connected, and stayed off until you turned it on again, so there was nothing to reconnect. If Wi-Fi is on and it still sits there without connecting, a report right after it happens helps.

    The other problem in this issue, where your router turns the player away again and again, is not fixed yet, so I'm leaving this open for it.

  11. just4747 commented on Nov 5, 2026

    @just4747
    Author

    Thanks for the report from last night, it showed something new: this time your router did not refuse the player at all. After Wi-Fi was switched on, the player scanned for about 34 seconds without ever seeing your network, so your tap on it answered "not found"; switching Wi-Fi off and on then found it in 3 seconds.

    Beta 9.3.13 does that by itself now: when you pick a network and it isn't found, the player switches Wi-Fi off and on once and tries again (the row keeps saying "Connecting…" meanwhile).

    About connecting on its own: the player does join saved networks by itself while Wi-Fi is on. In last night's log Wi-Fi had been switched off in Settings earlier that evening, a few seconds after it had connected, and stayed off until you turned it on again, so there was nothing to reconnect. If Wi-Fi is on and it still sits there without connecting, a report right after it happens helps.

    The other problem in this issue, where your router turns the player away again and again, is not fixed yet, so I'm leaving this open for it.

    That's great, sounds like good progress. Getting closer to this one being solved it seems!
    I will def continue to send logs if it happens.

  12. just4747 commented on Nov 5, 2026

    @just4747
    Author

    @SchulzCode Just had another occasion of these issues. Woke device after it had been sitting on my desk (was powered on). Did not auto-reconnect to the saved network even though I went into the WiFi menu and was in range. Tried clicking on it manually and it failed twice saying out of range even though it wasn't. Toggled Wifi manually and then could reconnect after tapping the network manually. Seems like the same issues persisting. Sent in another log, thanks!

  13. SchulzCode commented on Nov 9, 2026

    @SchulzCode
    Owner

    Sorry for the slow answer to your last report (5 Nov). It, together with your earlier ones, finally showed a pattern.

    What I found: every time Wi-Fi said "not found" after a wake, the player was at the same moment calling your earbuds over Bluetooth (they were away, so each call ran ~18 s until it timed out, three times in a row). Wi-Fi and Bluetooth share one radio in the Y2, and while it was calling the earbuds, Wi-Fi scans missed your network. In your report from 5 Nov the network was seen (−57 dBm), and the player was in the middle of connecting when the "restart Wi-Fi and try again" step from 9.3.13 cut that connection off. It only connected once the Bluetooth calls had stopped.

    Changed for the next update (Beta 9.3.20):

    • Joining a network only gives up with "not found" when the last scan really doesn't list it, and Wi-Fi is never restarted while a connection is being made.
    • After a wake, if no headphones were connected before the player slept, it now looks for them once instead of three times. Headphones you switch on later still connect by themselves.

    I'm leaving this open until you've had the update for a few days. If it fails again, a report right after it happens is still the most useful thing.

  14. SchulzCode commented on Nov 10, 2026

    @SchulzCode
    Owner

    The Wi-Fi changes are out in Beta 9.3.20: the player no longer gives up on a network it can see and restarts Wi-Fi, and after a sleep without Bluetooth headphones it no longer holds the radio for almost a minute looking for them. If Wi-Fi still doesn't come back after waking on 9.3.20, an error report right after it happens would help a lot.

  15. just4747 commented on Nov 10, 2026

    @just4747
    Author

    @SchulzCode This is awesome! Thank you sir!

  16. SchulzCode commented on Nov 10, 2026

    @SchulzCode
    Owner

    Glad to hear it! I'm closing this now. If Wi-Fi doesn't come back after waking or after being out of range again, send an error report right after it happens and reopen this, or open a new issue.

  17. just4747 commented on Nov 11, 2026

    @just4747
    Author

    @SchulzCode I noticed a few times today that I would wake the device from just sitting powered on on my desk and shortly after looking at a music list, went to settings to check for a FW update and it always looks like WiFi is staying disconnected (says Not Connected in the settings high level menu) until shortly after actually going into that screen. In other words, the status makes it seem like it doesn't reconnect automatically UNTIL I physically go into settings where I can view that status on the main settings screen. Not sure if that is accurate or if it was actually connected prior. Just in case, I sent in another error report right after (this was maybe 15-20 minutes ago from now), just in case you see what might really be happening.
    Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions