Manual Device Discovery
When automatic mDNS discovery fails or is unavailable, you can configure your devices with instance details during flashing to enable direct connection. This method is useful for enterprise networks, VLANs, or troubleshooting connectivity issues.
Use mDNS First
Automatic mDNS discovery is recommended for most setups. Only use manual discovery as a fallback when automatic discovery fails. See the Automatic Discovery (mDNS) guide first.
Configuring Devices for Manual Discovery
When mDNS discovery doesn't work in your network environment, you can configure the TOMMY instance details directly during the device flashing process. This allows devices to connect to your TOMMY instance even when automatic discovery fails.
During Flashing
When flashing your device using either the TOMMY Flasher or ESPHome, you can provide optional instance details:
- Instance IP: The IP address where your TOMMY instance is running (e.g.,
192.168.1.100) - UDP Relay Port: The default is
8547unless overridden
TOMMY Flasher
When using the TOMMY Flasher, you will be able to configure these optional fields during Wi-Fi provisioning:
- Instance IP:
192.168.1.100 - UDP Relay Port:
8547
See the TOMMY Flasher guide for complete instructions.
ESPHome
When using ESPHome, add the optional configuration to your device YAML:
sensor_tommy:
instance_ip: "192.168.1.100"
udp_relay_port: 8547See the ESPHome flashing guide for complete instructions.
When to Use
Configure these optional details if:
- Your network blocks mDNS/multicast traffic
- Devices are on different VLANs from the TOMMY instance
- You're using enterprise network equipment that restricts discovery protocols
- Automatic discovery isn't working in your environment