Lost Mouse

Thank you for confirming that your TinyPilot devices are directly connected. We really appreciate you taking the time to work through these diagnostics with us!

We've been going through the possibilities within the team and we think this is unlikely to be a hardware issue. Keyboard and mouse input travel mostly on the same channel and this would be the first ever report of a hardware issue causing the mouse to fail while the keyboard still functions. It’s also very unlikely that an identical hardware failure would affect two devices in quick succession.

I appreciate it's a hassle, but we've put together a few more tests that will hopefully help us to narrow down where the issue is occurring:

• Can you please check your browser console logs for any errors or warnings?

• Can you try accessing either of your TinyPilot devices with a different computer and browser? If that's not an option, could you please try using incognito or private browsing mode? This test is so we can check what happens in a clean session with no extensions.

• Can you try enabling SSH and copying the following snippet into the terminal? It will send mouse input directly to the mouse interface, eliminating any kind of network or client machine issues from the equation.

  for i in {1..5}
  do
     echo "$(date --iso-8601=seconds):" "Moving mouse cursor"
     echo -ne "\0\x03\x16\x58\x4c\0\0" > /dev/hidg1
     sleep 1
     echo -ne "\0\xbc\x1b\xdd\x2a\0\0" > /dev/hidg1
     sleep 1
  done