mirror of
https://github.com/Gathin23/cleanyourtv.git
synced 2026-10-27 19:54:45 +00:00
Mazin KanugaandClaude Opus 5.5
9d77a82c62
relay.py now takes the TV's port as tv.py and adb-closed.py do (--tv-port, else a port in the address or TV_HOST, else TV_PORT, else 5555), where it relayed to 5555 whatever TV_PORT said and TV_HOST=ip:port to "ip:port:5555"; a TV_PORT that is a relay's port (TV_HOST=127.0.0.1 TV_PORT=15555 left exported for the tools) is refused, not used as the TV's. Tried on a Chromecast with Google TV 4K (Google TV 14, UTTC.250917.004): with TV_HOST=<tv ip>:5555 the stock adb read getprop through the relay, and with the tools' settings exported `relay.py <tv ip>` was refused. Refs #997 Co-Authored-By: Claude Opus 5.5 <[email protected]>
2.5 KiB
2.5 KiB
tools/relay.py
Forwards a port on this computer to the TV's ADB port. Use it when your coding assistant runs its commands in
a sandbox that can reach this computer but not other devices on your network. Claude Code on macOS is the
usual case: Local Network privacy blocks its sandbox, so tools/tv.py times out or says "No route to host"
even though the TV answers from an ordinary terminal.
# In an ordinary terminal (Terminal, iTerm, VS Code), and leave it running:
tools/venv/bin/python -I tools/relay.py 192.168.1.50
# Then, wherever the assistant runs the tools:
export TV_HOST=127.0.0.1 TV_PORT=15555
tools/venv/bin/python -I tools/tv.py --probe
- Options:
--tv-portif the TV's ADB port isn't 5555, or give it with the address (192.168.1.50:5877);--portfor another local port (run one relay per TV, each on its own port). The TV's address defaults to$TV_HOSTand its port to$TV_PORT, as fortools/tv.py. - It prints the
TV_HOST/TV_PORTto use, and one line each time it can't reach the TV. - Stop it with Ctrl-C when you're done.
Safety
- It listens on
127.0.0.1only, never on your network, and has no option to change that. Other devices can't use it to reach your TV. - Programs on this computer can reach the TV's ADB port through it while it runs. ADB still needs a key the TV has accepted ("Allow USB debugging?"), but stop the relay when you're done, as you'd close network ADB itself.
When it fails
- "cannot reach 192.168.1.50:5555", printed by the relay: the TV is off or in standby (some TVs drop off
the network), on another network, or network debugging was switched off. The tools then see the connection
reset by peer. If the port it names isn't the TV's, it came from a
TV_PORTexported in this terminal: rununset TV_PORT, or give the TV's port with the address (192.168.1.50:5555). - "cannot listen on 127.0.0.1:15555": a relay is already running on that port. Use it, or pick another
--port. - "TV_PORT=15555 is a relay's port": the tools'
TV_HOST/TV_PORTare exported in this terminal, so the relay would forward to the TV's IP on a relay's port. Rununset TV_HOST TV_PORT, then give the TV's IP address, or give the TV's port with the address (192.168.1.50:5555). - "that is the relay itself": the TV's address was given as
127.0.0.1with the relay's own port, perhaps from aTV_HOST=127.0.0.1:15555exported for the tools in this terminal. Give the TV's IP address.