The clock never asks for your chess.com or Lichess password. All three connect from the webadmin, more than one can be set up at once, and switching the "Data source" selector between them never erases the others' saved connections — flip back any time.
A standard OAuth login — the clock never sees your password, and there's nothing to copy or paste.
Open the clock's webadmin (http://ivochess.local/) → Lichess account section → Connect to Lichess.
You'll land on Lichess's own site. Log in if needed, review what the clock is asking for (permission to see your live games), and approve it.
Lichess sends you back to the webadmin, already connected and showing your username. Select Lichess as the data source and save.
Chess.com doesn't offer a public OAuth login for third-party devices, so this one works a bit differently: the clock borrows a browser session the same way a phone app would — one cookie, captured once, that lets it watch your live games and keep itself signed in indefinitely.
Ctrl/Cmd+Shift+N (Chrome/Edge) or Ctrl/Cmd+Shift+P (Firefox) opens a private window. Go to chess.com and log in normally, with your real password — this part never touches the clock, it's just a regular login in your browser.
Press F12 (or right-click → Inspect), then go to the Application tab (Chrome/Edge) or Storage tab (Firefox). In the sidebar, expand Cookies and select https://www.chess.com.
Find the row named CHESSCOM_REMEMBERME and copy its Value column (double-click the value to select it). That's the only one you need.
| Cookie name | What it's for |
|---|---|
| CHESSCOM_REMEMBERME | The long-lived token that keeps the clock signed in. Everything else — including the actual session — is derived from this one automatically. |
Open the clock's webadmin (http://ivochess.local/) → Chess.com account section. Paste the value into the CHESSCOM_REMEMBERME field, fill in your chess.com username too, and save.
Don't use it to play — just close it. The clock now has everything it needs and will keep its own session alive on its own from here on.
Chess.com identifies a logged-in session with a PHPSESSID cookie, which expires on its own after a while. Earlier versions of this project asked you to paste that one too — and it meant coming back here to re-paste it every time it lapsed.
A normal browser tab never shows you that, because it renews silently in the background, and the clock now does exactly the same thing. Chess.com also issues the much longer-lived CHESSCOM_REMEMBERME token, and presenting it is enough to be handed a brand-new PHPSESSID with no login form involved. So the clock mints its own session on demand and refreshes it forever — there is nothing for you to paste a second time.
The one thing worth knowing: each time that token is used, chess.com issues a replacement and immediately invalidates the previous value — a standard defence so a stolen token can't be reused. The clock stores every replacement as it arrives. It also means a token can only ever belong to one client, which is the real reason for the incognito-window rule above: if a browser session you're still using refreshes the same token, the clock's copy is dead from that moment on, and vice versa.
As long as you don't log out of chess.com everywhere or change your password, the clock should stay connected indefinitely without you ever needing to come back to this page.
No login on the clock at all — Chessconnect drives it directly over Bluetooth.
Open the clock's webadmin (http://ivochess.local/) → Data source → select ChessConnect and save.
In Chessconnect's own settings, pick "DGT3000 BLE Gateway" as your clock type, then connect to DGT3000-Gateway from its device list.
The clock shows up over Bluetooth from then on — no account, no password. It shows White/Black and the running clocks; for names and ratings, connect chess.com or Lichess directly instead.