After a few moves the red bar “Claim victory” started to appear, ticking down from like 1:30 min or something. Clearly my opponent was still playing normal moves, with the red bar disappearing after he had moved. Reappearing a few second after I had made my move.
Later in the game there was no time on the bar, just showing “Claim victory” while the opponent still was playing normally. See video here for an example https://www.youtube.com/watch?v=mT5iFzNu-Rk.
In the end of the game, even late, the opponent’s clock was sticking for like 2-3 min and he did not move…then I started the Lichess app on the phone, to see that the board had not sent my last move to Lichess and I had to redo my move and to continue finishing the game in the app.
That’s exactly what happened to me in this game today:
And I ran out of time without even knowing it since the clock on my Chessup 2 was not reflecting the correct time (I think I had more than 2 minutes remaining when I lost because of running out of time). My last move was not sent to Lichess, hence I lost on time. But, as I checked on the website after the “claim victory” banner had appeared during the game, I thought that the bug (lost move) was due to me checking on the app as we’ve been told not to do that during a game …
However, I’ve just experienced another lost move (my move not sent to Lichess) without checking on the app first ! I checked on the app because my opponent was taking suspicously too long a time to play his move, and indeed: once I checked on the app, I saw that he had moved a long time ago (maybe ten minutes or so !) and that my clock was almost running out of time !!! So I continued on the app, and lost the game but that’s not the point. The point is about lost moves (moves not being sent to Lichess). Here is the link to this other game:
The move that has not been sent is my (Black) 10th move. I’ve continued on the app from this move, but I repeat that I had not been tampering with it during the game until this move, so the bug is not in any way related to me checking on the app.
CoolPony & testarlite - I’ve reviewed the logs for all three of these games, at some point the board lost the ability to send requests to the server, but was still connected to the server, so it still received the game ending. This is strange and not expected. This one might take us a bit to figure out. It did not have anything to do with the Lichess server reboot that day.
I have a suspicion what might be happening, but it’s going to take a while to prove and test. If you’re playing multiple games, I suggest restarting the board between Lichess games while I try to track this down over here.
I gotta say that the board is working flawlessly with chess com ! I say that for two reasons:
I want to thank you, once again, for making this excellent board which works so well now that the original (chess com) lost move bugs have been solved !
The hardware (the board and my network gear) is in perfect woking condition, as demonstrated by the perfect gameplay on chess com.
Thank you for investigating this and all your previous dedicated work !
I typically play om chess.com. but played a game on Lichess yesterday. During the game, I kept getting a red “claim victory” notice, but my opponent was still making moves. The game finished fine despite these messages.
Description of the Issue:
While playing online with my ChessUp 2 connected to lichess.org, a critical desynchronization occurred. My last move (Rc5) was acknowledged locally by the ChessUp board — the LEDs updated, and my opponent’s clock began to run. However, the move was never transmitted to lichess. On lichess, it remained my turn, and after waiting for my opponent’s reply OTB, I eventually lost on time.
This is the second time this exact problem has happened to me (the first was about a year ago on chess.com). It makes online play unreliable, since the app/board can appear to be in sync while the server is not.
Firmware 4.1.0 has a fix for the connection issue, and is available on Beta. Please PM me your serial number if you’d like to join the beta group and test early.
