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.
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).
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?