Skip to content
Tilecast Docs
Tilecast Edge is in preview. Its software is complete, but it is not qualified on physical hardware yet. Use the stable Linux Player on production screens until a Tilecast release supports your hardware.

Troubleshoot Tilecast Edge

Start in Studio. Edge reports through the normal Screens, Activity, and Player updates pages, so check those before you open a shell on the computer.

Local status and logs

Section titled “Local status and logs”
On the Edge computer
/opt/tilecast-edge/current/bin/tilecastctl status
journalctl -u tilecast-edge.service
journalctl -u tilecast-renderer.service

tilecastctl status shows pairing, the server connection, the renderer, safe mode, and recovery mode. The Player service and the renderer have separate logs, so you can tell a renderer crash from a Player problem. tilecastctl capabilities shows why a hardware feature is unavailable.

Common problems

Section titled “Common problems”
  • No server found: enter the server address manually. LAN discovery is optional.
  • Presentation unavailable: the content needs something Edge can’t show yet, such as a Website. Check content compatibility and the capability matrix.
  • Renderer keeps restarting: check Activity and safe mode before you delete any Player data.
  • Display Control unavailable: check the reason in tilecastctl capabilities, such as missing hardware, a missing permission, a disconnected display, no DDC/CI response, or an unsupported control. See Display Control troubleshooting.
  • Migration refused or rolled back: run sudo /opt/tilecast-edge/current/bin/tilecast-edge-migrate status for the reason, fix it, and migrate again. See Migrate.

Updates

Section titled “Updates”
On the Edge computer
sudo /opt/tilecast-edge/current/bin/tilecast-edge-update status
journalctl -u tilecast-edge-update.service -u tilecast-edge-update-guard.service

status shows the installed releases, the current one, and the last update with its result and reason. Update Tilecast Edge explains each rollback reason. For deployment problems in Studio, see Player update troubleshooting.

If the screen shows its recovery screen after an update and tilecastctl status reports state_db_newer_schema, follow Recover after a rollback.

What not to do

Section titled “What not to do”
  • Don’t run tilecastd as root to work around a device permission.
  • Don’t delete /var/lib/tilecast-edge/ as a routine troubleshooting step. It holds the screen’s pairing and cached content.
  • Don’t post Player credentials, pairing secrets, or private state files in a public issue.