Good point. I guess it could be a /22 (subnet mask 255.255.252.0) and all be the same network. That would jive with the broadcast being 192.168.7.255, too.
thanks fro looking! I tried to answer everything here, sorry if i miss something- sounds lie a botched eero setting?
I must admit , I am not a network guy. I left all eero on automatic- and its been working fro teh past 2 years. I did some searching - plex rolled out a new app stating 12/20 (12/22 is when it stopped working). eero rolled out update 12/15 (they cannot tell me when it actually updated)
Sonos device?
I (or anyone here) never owned a sonos device. Not sure how to remove that.
Is everything logged into the same account?
Yes, clients logged out and back in, server rebooted, but not logged out. maybe I need to?
Is that all controlled by the eero? plex app? or from the plex server?
seems odd that my roku devices can all connect- but android cannot.
seems its maybe the app? as I can use the browser to access plex on all devices.
here is the setting page from my eero.
Here is network page from server:
cell setting
Is there a way to see the ip somewhere in the plex app?
Can you identify the 192.168.7.x network your Android client is sending from?
I don’t now where to start- I had the issue, then I reformatted my phone and i only installed bare minimum apps. I tried it with fresh reformat, & plex only and it still happened.
I used a network scanning app, and it does not show any other ip range other than 192.168.4.xxx
Perhaps i can manually set this up? not sure what to put where though?
found this in the eero under manual settings:
How do i get rid of this? I never had a sonos device (nor is one listed in my authorized devices in the server settings) or account nor anyone in the home. Seems to take up alot of time/resource calling it constantly.
Is it from a device or the server?
Seems the errant 192.168.7.xx device(s) are gone with the new settings.
I checked the lan scan vs eero and can account for every device.
I deleted any remote devices from authorized devices in server settings.
I pulled the plug on a firestik- I installed it for testing when this issue popped up (192.168.4.95 ) There was much activity from it.
Still only android devices with issue- rokus still pluggin along.
No problem- I understand. But FyI I updated the eero to be manual. I posted the setting here- its more in line now with what I am accustomed to seeing ion a router.
Will do, If i go that way I may just get a pihole w/dns server up and running.
I am doing 3 more things:
asked eero to downgrade my last 12/15/2023 firmware update (wont hold my breath for this)
Am looking ot buy or borrow a cheap router to quickly test- will hook up to a new ssid and quickly test.
I ordered a rasp pi3 to run pihole/dns w/ eero in bridge mode.test
However I am really leaning toward that the issue is with the plex android app update- as my roku devices all work including one that I borrowed to test after the issue started & it all started after the app update on 12/21.
Issue went away before I had installed new router etc…
Play store had 5 new updates- I do check daily for updates. (plex did not work correctly before these updated)
2 updates (firefox/chrome) I felt had nothing to do with the change.
3 I feel could have contributed:
google cross device services, android device policy, google device health services. After I performed the play store updates,I checked plex and it worked!
Either way- Its working super fast again.
I checked the logs and the only error is the sonos connect error.