14 · Troubleshooting
Troubleshooting
A symptom → cause → action index.
Applies to the kit and the Free edition
Communication#
| Symptom | Cause | Action |
|---|---|---|
| No receiver gets tally | Firmware version mismatch | Re-flash both ends to the same version (03) |
| All receivers dropped | A failed channel change | Reboot the master and set the channel again (10) |
| Some receivers dropped | They were off during the change | Re-match channels — move the master back or reconfigure (10) |
| No traffic after a change | Frequency/Sync Word mismatch | Verify both values match (10) |
| Switcher Disconnected | Link down or bad settings | Reconnect, then the per-type checklist (09) |
| Connection never starts after forcing an interface | Forced interface link down | Check the link — revert to Auto or fix the link (09) |
| Intermittent drops | Frequency interference | Scan and move to a Clear channel (10) |
| OSEE stuck on Timed Out | Send direction not set | Point the OSEE unit at this device IP:52381 (09) |
Display#
| Symptom | Cause | Action |
|---|---|---|
| Battery/temperature/Device ID read N/A | Free edition (no such sensors) | Normal — nothing to do |
| Registered count shows 0 | Aggregation lag | Card count is the real number — normal |
| Receiver LEDs never light | Power or enrollment | Check power, then status on Devices (11) |
| Red LED invisible outdoors | Sunlight | Use the OLED Tally page (12) |
| Number changed, lighting position wrong | Mapping mismatch | Check number-to-position in the mapping (09) |
| Number change not reflected | Radio/report latency (normal ~30s) | Wait; if still nothing, check the receiver online state (11) |
| Color preset missed some receivers | They were off | Power on and tap again (11) |
| Web Tally dot stays red | Phone network cut | Check phone WiFi and the device AP (13) |
Web console#
| Symptom | Cause | Action |
|---|---|---|
| Device IP unreachable | Path confusion or changed IP | Read the IP from the OLED network page; retry per-path defaults (04) |
| tally.local does not open | mDNS unsupported on the path | Use the numeric IP (04) |
| Values not updating | Polling interval or dead link | Check Update Speed; if Offline, fix the path and refresh (08) |
| Saved settings slow to appear | Polling cycle (normal) | Wait up to one cycle (08) |
| Ethernet Not Detected | Chip not detected | Inspect module and board (08) |
Boot and power#
| Symptom | Cause | Action |
|---|---|---|
| Boot progress stuck at a stage | Stage hardware/firmware issue | If it persists after a reboot, reinstall firmware (03) |
| Reboot loop after boot | Corrupted firmware | Enter download mode and flash again (03) |
| No power | Battery depleted | Charge and reboot — low battery deep-sleeps after a 10s countdown (12) |
| Browser cannot see the device (flash) | Charge-only cable, port, permission | Data cable, another port, grant serial access (03) |
| Device unfound after a reset | Factory defaults (AP) | Rejoin the AP Tally-XXXXXX (192.168.4.1, password 12345678) (06) |
Software#
| Symptom | Cause | Action |
|---|---|---|
| STOPPED overlay on receivers | Invalid license | Reactivate, then physically reboot receivers (07) |
| Activation keeps failing | Bad or already-assigned key | Check the 16 characters and the reason toast (07) |
| Validation stuck on Checking | No internet | Run Connection Test (07) |
| Test mode cannot start (N/A) | Free edition | Normal — master-only feature (06) |
| Display lingers after Stop Test | Last state kept (normal) | Clears on the next switcher event (06) |
| Notices empty | Offline or server state | Refresh icon; retry later (06) |
Still stuck?
Ask in the forum with the symptom and device state.
Last modified —