opal06
Push fails with status 410
Pushing any file to remarkable now fails with a status 410:
$ python zotero2remarkable_bridge.py -m push
Pushing...
Found 1 elements to sync...
0%| | 0/1 [00:00<?, ?it/s]Processing Pan et al. - 2024 - Task and Motion Planning for Execution in the Real.pdf...
ERROR: 2024/09/23 08:38:48 main.go:77: failed to build documents tree, last error: request failed with status 410
Failed to upload Pan et al. - 2024 - Task and Motion Planning for Execution in the Real.pdf to reMarkable.
It seems like the endpoint no longer exists?
Unfortunately, you are probably right. Since this program uses rmapi under the hood for the interaction with remarkable's API, it would need to be fixed by rmapi's maintainer. Unfortunately, that project has been archived in July of 2024. I don't know the reasons, but I would bet that remarkable's constant changes in their storage architecture and API stemming from the need for supporting the new features introduced around notes etc played its part. In my very limited experience, it has been quite annoying developing against this constantly moving and very intransparent target. It seems as if they have changed something once again and it might be even trivial to fix, but I fear there are few people left trying to do so. And honestly it might just be the straw that breaks the camel's back for many of these community projects that interface with remarkable's cloud API. If this isn't resolved quickly, I'll probably archive this project as well.
I have also moved on from this solution as I actually needed a dependable device for my PhD and don't have much time to fix bugs and work around issues anymore. I now have installed KOReader and rclone from the toltec package manager. I have found that KOReader is a much better and more configurable reader software, that can replace the entire UI of the tablet, opens and saves to standard PDF files directly, also creating proper PDF highlights and comments. Together with rclone's bisync feature, I can now simply sync PDFs from my Nextcloud (or any supported cloud really) to the remarkable, read them in KOReader, save my changes directly to the files, and sync them back to Nextcloud. I have automated the syncing with a small script and system-d's scheduling features. Now, this looses remarkable's handwriting support and notes aspect (although there are launchers you can install to switch between KOReader and the default UI), but neither have worked very well for me anyway, so for me that was an easy trade-off. If you want, I can elaborate more on this, but I fear I won't be able to address the bug you encounter unless rmapi fixes it upstream, I'm sorry.
Thanks for the fast reply! I'll have another look at the alternatives, I briefly checked them out a while ago but they seemed to be more involved. But I agree, maybe it's time to make the switch.
Thank you for maintaining this project so far and good luck with your PhD!
if you take the new rmapi fork, it works again: https://github.com/ddvk/rmapi
