Skip to content
DeckConnectorSet it up
Skip to Content

Troubleshooting

What the deck screens mean, and what to do when something does not connect.

Flashing fails? See Flashing problems.

The deck screens

On the deckWhat to do
No networkNeither LAN nor Wi-Fi has an address. Plug in a cable, or tap Wi-Fi on the deck to start the setup Wi-Fi
Waiting for CompanionCompanion is the active source but not connected. See below
Companion not reachableThe Companion address does not answer. Check it under Sources
Waiting for the Elgato AppSee below
Looking for a serverNo server address set, and none announces itself. Add one under Sources
Server offlineCheck that the server runs, and its address and port
Connection requestAn unknown computer wants the deck. Accept lets it in, Deny keeps it out
Companion foundConnect connects it over Satellite. No stops asking
Setup 2/5 on a keySomeone runs the setup in a browser. Finish or skip it there

The deck stays dark or is slow

  • The connector needs power. With PoE, the switch port must deliver it.
  • The deck goes into the USB-A port.
  • Reconnect in the web UI turns its USB power off and on.
  • A dark deck wakes with one press. If the screen saver, the screen switch or brightness 0 made it dark, that press only wakes it. If Companion or the Elgato app set brightness 0, the press also goes to them.
  • Behind a USB hub the deck may run at full speed, and pictures come slower. Plug it in directly.

The web UI does not open

  • Use the IP from the deck menu instead of the .local name.
  • With HTTPS only on, use https://.
  • After a network change the address changes. The deck menu shows the new one.
  • After too many wrong passwords, the login waits up to a minute.
  • Lost the password?

Companion does not connect

  • Settings › Satellite must be on in Companion.
  • The connector must reach Companion on TCP 16622, or 16623 for ws://. For Docker see Connect Companion.
  • Under Sources, Save tests the Companion address first and says whether Companion answers.
  • The deck shows up twice? A proxy hides Companion's address. Remove the remote surface in Companion.

The Elgato app does not find the deck

  • The computer must be in the same network, not a guest Wi-Fi.
  • A firewall on the computer may block the app.
  • The deck must be plugged in when the app starts. Otherwise restart the app.
  • A denied app asks again only after it restarts.

An update does not stay

The new firmware did not reach the network within two minutes, or did not stay up for 20 seconds. Log shows why. Turn on Technical. The lines below the restart are from the start before (demo).

Logs and crash reports

Log has the events, inputs and the raw log in one list. Events stay over restarts and power cuts. The raw log of the start before stays until a power cut. Diagnostics has the last crash report. A crash report can hold the password, so only the password opens it.

curl -u admin:PASSWORD http://192.168.1.50/api/log > log.txt
curl -u admin:PASSWORD 'http://192.168.1.50/api/log?boot=prev' > log-prev.txt

On this page