Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Looks like awesome project!

EDIT: Ctrl-C and restart with ./goMarkableStream got it working more or less. Saving the below message if it helps anyone else

EDIT2: Awesome when it works - but getting quite a bit of spotty service. Still frequent `waiting for reMarkable screen` . SSH is showing everything normal, except for occasional:

  2023/08/20 14:48:16 read /dev/input/event2: file already closed

  2023/08/20 14:48:16 read /dev/input/event1: file already closed
I upgraded my reMarkable2 to 3.5.2.1807 (from ancient 2 something version)

Unfortunately I am getting waiting for reMarkable screen after installation.

That is nothing is happening when I draw on reMarkable2 - in notebook, in sheets, on book.

On inspection ReMarkable2 is certainly serving html with canvas element

Both https://192.168.8.143:2001/ and https://10.11.99.1:2001/ work (after accepting unsafe SSH cert which is normal) and are serving html.

Tried on Chrome, Firefox, Brave

I installed it per github instructions.

From Windows via PuTTY through 10.11.99.1

EDIT3: Looks like limitation is one browser (and one IP address) per stream - normal considering the usage :). Still sometimes no matter what address and browser I try I get `waiting for reMarkable screen`

EDIT4: tried `nohup ./goMarkableStream &`, closed PuTTY and restarted client computer - all browsers giving `waiting for reMarkable screen`

How would I restart the stream? Inspecting https://10.11.99.1:2001/stream gives `too many requests` response.



Regarding Edit 3: Yes it is a feature not a bug. I don’t want to stream to several browsers at once.


Agreed that is completely reasonable. One stream is sufficient.

Unfortunately per EDIT4, it looks like it is not possible to leave this service running on reMarkable2 until the next time.

Any way to reset without going into SSH again?

EDIT: looks like enabling USB on reMarkable2 got the stream working. Curious though why did the web server work at all then (possibly sharing of common wi-fi?)

FINAL_EDIT: I give up, there is no sense to this madness. Suddenly the stream starts working on same same https://10.11.99.1:2001/ where it was giving `waiting for reMarkable` canvas for last 15 minutes.

Possibly there is some sort of timeout for the old stream?


There is a timeout of one hour (after an hour you need to refresh the tab). Adding a & at the end does not help to make it run until next time? Do not hesitate to open an issue on GitHub.

Thank you


Thank you once again!

It seems the timeout is about 15-20minutes (when a new tab or new browser starts working).

Adding & did work, I was able to go to a different computer attach USB cable and have https://10.11.99.1:2001/ work (without SSHing and restarting goMarkableStream).

I




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: