This repository was archived by the owner on Jan 11, 2026. It is now read-only.
feat: Add support for reMarkable firmware 3.0+ highlights#23
Open
CodeBySladman wants to merge 1 commit intoAndrewBestbier:mainfrom
Open
feat: Add support for reMarkable firmware 3.0+ highlights#23CodeBySladman wants to merge 1 commit intoAndrewBestbier:mainfrom
CodeBySladman wants to merge 1 commit intoAndrewBestbier:mainfrom
Conversation
BREAKING CHANGE: Requires Python server for highlight extraction ## Problem reMarkable firmware 3.0+ changed from .highlights/*.json files to storing text highlights as GlyphRange objects inside binary .rm files. The existing code couldn't extract highlights from modern reMarkable tablets. ## Solution - Add Python API using rmscene library to parse v6 .rm binary files - Update highlights API to download .rm files and send to Python for parsing - Fix reMarkable cloud API endpoints that had changed - Update to use rmapi-js library for cloud API interactions ## Changes - pages/api/highlights.ts: Rewritten to download .rm files and call Python API - pages/api/files.ts: Updated to use rmapi-js library - pages/api/register.ts: Fixed API endpoint URL - pages/api/refresh-token.ts: Fixed API endpoint URL - pages/index.tsx: Simplified to work with new rmapi-js - api/parse-highlights.py: NEW - Vercel serverless Python function - python-server.py: NEW - Local development Flask server - requirements.txt: Added rmscene>=0.5.0 and flask>=2.0.0 - README.md: Updated with Python setup instructions ## Local Development For local development, run the Python server alongside Next.js: python3 -m venv venv && source venv/bin/activate pip install rmscene flask python python-server.py # Terminal 1 npm run dev # Terminal 2
Author
|
Managed to get it working again for myself - so wanted to share the solution I found with the community |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: Requires Python server for highlight extraction
Problem
reMarkable firmware 3.0+ changed from .highlights/*.json files to storing text highlights as GlyphRange objects inside binary .rm files. The existing code couldn't extract highlights from modern reMarkable tablets.
Solution
Changes
Local Development
For local development, run the Python server alongside Next.js:
python3 -m venv venv && source venv/bin/activate
pip install rmscene flask
python python-server.py # Terminal 1
npm run dev # Terminal 2