SquirrelCast currently receives CRSF telemetry over Wi-Fi UDP broadcast from the TX backpack. The phone or tablet and the backpack need to be on the same Wi-Fi network.
For the initial backpack setup, follow the official ExpressLRS guide:
Flashing via WiFi
It is recommended to set the Backpack Home Wi-Fi SSID and password to match your phone hotspot when flashing. That gives you both options later:
1.5.7 or newerThe feature has been merged and is present in ExpressLRS Backpack 1.5.7 or newer.
1.5.7 or newer.As an alternative, you can also use the official ExpressLRS Web Flasher:
https://expresslrs.github.io/web-flasher/
In the Web Flasher:
1.5.7 or newer.A patch for some ESP32-C3 based TX backpack targets has been merged into Backpack master, but it is not included in Backpack 1.5.7. On affected targets, setting Telemetry to WiFi may not make the backpack start or connect to Wi-Fi.
If this happens, either flash the current master branch or use the short-term workaround: set Link Mode to MAVLink, set Telemetry to WiFi, wait for Wi-Fi to start, then set Link Mode back to Normal. The workaround needs to be repeated after power cycling.
For the full master flashing flow and a more detailed explanation, see ELRS Backpack C3 Wi-Fi telemetry troubleshooting.
To enable Wi-Fi telemetry forwarding:
WiFi.
Note: Do not use WiFi Connectivity -> Enable Backpack WiFi for telemetry forwarding. That menu is for firmware update mode. For telemetry forwarding, setting Telemetry to
WiFistarts the backpack Wi-Fi automatically.
It is often worth increasing the telemetry frequency from 1:64 if you want smoother updates in the app. At 250Hz, a telemetry ratio of 1:64 means one telemetry slot about every 256ms, or roughly 3.9 telemetry packets per second.
That does not mean every telemetry value updates 3.9 times per second. Telemetry is split across different packet types, so any particular value can update much more slowly. At 1:64 and 250Hz, GPS updates can be roughly every 5-10s.
A faster ratio such as 1:2 makes telemetry look much smoother in the app, but it also reduces control link update frequency. At 1:2, roughly one out of every three RF packets is telemetry, so a 250Hz link behaves more like about 166Hz for control updates.
This is optional. If you prefer maximum control link update frequency, leave the telemetry ratio lower. For more detail, see the official ExpressLRS page on Telemetry Bandwidth.

When Telemetry is set to WiFi, the backpack starts Wi-Fi automatically.
This is the most convenient option if you want the backpack to join your hotspot as soon as it powers on.
ExpressLRS TX Backpack XXXXXX.expresslrs.The XXXXXX part is a 6-character identifier unique to your TX backpack. On Android, this network will usually show up as having no internet access. In that case, choose Use network as is, Stay connected, or the closest equivalent on your device.
If you only want telemetry in the app and do not need video streaming, a hotspot is not required. You can simply connect directly to the backpack access point.

The map will show a position only after the flight controller has a GPS fix.
By default, the backpack and the app both use UDP port 14550, so they should work immediately without any port changes.
If you want to use a custom port:
http://elrs_txbp.local/ when connected through Home Wi-Fi or hotspot, or http://10.0.0.1/ when connected directly to the backpack AP.
MAVLink support has not been added to SquirrelCast yet, but it is planned. For now, telemetry over Wi-Fi works only when your radio link is using the CRSF protocol.