Copied from https://www.googlenestcommunity.com/t5/Streaming/ADB-over-Network-is-blocked-on-a-wired-connection/m... because it was closed and locked with zero responses.
Aside from the issues that seem common so far, I was also able to spot another problem in regards to the updated Wireless Debugging options.
If the device is connected to the network over an Ethernet connection, trying to select "Enabled" in the settings toggles immediately back to disabled.
However, if I unplug the Ethernet cable from the adapter, wait for the Chromecast to go online over WiFi, and then enable the option again, I'm able to get to the pairing mode activity.
Then, if I don't exit the screen with the pairing port and code before plugging the Ethernet cable again, the device recognizes the change in connectivity and replaces the name on the screen to reflect that, but as soon as I exit this screen again, it forcefully disables Wireless Debugging and closes any connection I was still active on while on the pairing menu.
This behavior remains constant even after a factory reset, and while I'd love to provide logs, the nature of this issue makes it a bit difficult to gather them beforehand, so any help would be appreciated.
----
This is a significant regression and is unacceptable. Every single google product I own seems to degrade and decay with time.
