Used together
Press the button. Pick the device. The console opens.
BaudHoundTerm's BaudHound button lists the devices on the networks your PC is on, then opens the one you pick in a tab set up for it: local echo and line editing, the device's commands on the right-click menu, logging and reconnect.
How it goes
1. Find
The button asks the network for about two seconds. Each device answers with its address, firmware, baud rate, the network it joined and its certificate fingerprint.
2. Trust
The first TLS connection shows the fingerprint. Compare it with the TLS line on the device's Settings page, then trust it. Later connections check it silently.
3. Keep
Save it as a shortcut in the BaudHound folder. If DHCP moves the device, saving again moves the shortcut to the new address.
One session at a time
While you hold it, nobody else is watching.
Over TLS the device takes one client at a time. While your session is open, plain telnet is disconnected and refused, and the web console stops showing output and refuses input. The picker marks the device in use. Closing the tab frees it; a PC that drops off the network frees it after about 25 seconds.
Good to know
Discovery and TLS need firmware 1.4 or later. Older firmware is found when the PC is on the device's own WiFi.
Windows can block the replies on a network marked Public. You can type the address instead.
If the fingerprint ever changes, the connection stops with a warning. Refuse it unless you erased the device's flash.
Line mode sends each line with CR LF and edits it locally, for consoles that echo nothing.