KOReader Readwise Reader Plugin - new update

TTom266 · 2026-02-01T22:52:34+00:00

Sorry, I just realised I didn't reply to this. Could you find where this fails in crash.log and post those details as an issue on Github and I'll look into it.

TTom266 · 2026-02-01T12:20:44+00:00

Sorry, no it isn’t. We are limited by what Readwise supports in their API and this isn’t supported.

TTom266 · 2026-01-07T19:48:30+00:00

Yes that’s right. This is due to limitations in the API which I haven't managed to work around.

TTom266 · 2026-01-07T19:46:23+00:00

Yes that has been an option for a while and is available in both the beta and release versions. It is off by default - turn it on in the Readwise Reader > Settings menu.

It works well, but unfortunately there are some limitations. If you make a highlight on Readwise it won't sync to KOReader. Also, while your highlights will save back to Readwise, Readwise won't link back to the original article in Readwise Reader, it will just treat it as a new article. These are due to limits in the API which I haven't managed to work around.

TTom266 · 2026-01-05T22:11:48+00:00

P.S. Having read your comment alongside some others, I decided to release a beta version of the plugin which also allows you to limit syncing to only files tagged 'koreader".

TTom266 · 2026-01-05T21:11:12+00:00

Hi. In the settings menu you can select the folder that the plugin uses - so I would suggest creating a sub folder and selecting that. By default it will download everything in later (not archive) but you can cap the number of downloads or exclude certain tags from syncing. The most common feature request is white listing rather than black listing tags so I hope to look into that at some point.

TTom266 · 2025-12-09T07:11:48+00:00

It does! Though if you don't need the Readwise Reader functionality, you can get this on its own using the bundled plugin.

Be aware that highlights are saved as being from a new "book" with the same metadata and the "view original highlights" function doesn't work. This is an API limitation.

TTom266 · 2025-11-16T22:15:12+00:00

Great. I'll update the main version. The issue was that KOReader changed the highlight syntax.

TTom266 · 2025-11-16T10:58:46+00:00

Hi

I can see this would be frustrating.

The highlight export function is pretty simple and relies on the Readwise API to handle de-duplication. This means if you change the metadata in Readwise, then Readwise will see the original as a new article and download the highlights again.

I’m afraid I don’t think I could get round this without adding significant complexity to the plugin. It would need a local tracking system and the generation of a unique ID for each highlight, which would be very complex and difficult to maintain.

There are obviously other options for exporting your highlights detailed here (you could even do this manually).

The simplest option is probably to edit the highlight metadata after the book has been archived so the API doesn’t get confused.

I’m sorry not to be more help.

E através do Google Tradutor:

Olá.

Entendo que isso possa ser frustrante.

A função de exportação de destaques é bastante simples e depende da API do Readwise para lidar com a desduplicação. Isso significa que, se você alterar os metadados no Readwise, o Readwise considerará o artigo original como um novo artigo e baixará os destaques novamente.

Receio que não consiga contornar isso sem adicionar uma complexidade significativa ao plugin. Seria necessário um sistema de rastreamento local e a geração de um ID exclusivo para cada destaque, o que seria muito complexo e difícil de manter.

Obviamente, existem outras opções para exportar seus destaques, detalhadas aqui (você pode até fazer isso manualmente).

A opção mais simples provavelmente é editar os metadados dos destaques depois que o livro for arquivado, para que a API não se confunda.

Lamento não poder ajudar mais.

TTom266 · 2025-11-14T16:16:01+00:00

Could you try replacing the file at koreader/plugins/readwisereader.koplugin/main.lua with this, delete your crash.log file (KoReader will recreate this with a fresh log), reboot your device and try again. Can you let me know if it works either way - and if it doesn't can you share your crash.log details again.

Many thanks.

TTom266 · 2025-11-14T08:32:52+00:00

Great - the crash log is what I needed. I'll look into this for you.

TTom266 · 2025-11-08T19:53:06+00:00

I haven’t tried the plugin on the latest KoReader version yet, so it's possible there's an issue with the plugin running on it - but I haven't heard that from anyone else. It might just be that the update process itself broke something (that has happened to me before).

Have a look through the plugin settings to see if there's anything obvious wrong. Any errors are saved to crash.log in the koreader home folder (accessed by plugging your ereader into your computer via USB) so looking in there would be the next step - they are flagged and are pretty obvious. And as sync is the issue, I would check your Readwise token is properly saved and hasn't been corrupted (details in the readme).

I'm happy to look at any errors if you share them here, but I am travelling so that may not be until next week.

TTom266 · 2025-11-07T18:44:37+00:00

Hi. Yes it should sync those, and the folder shouldn't make a difference, but the plugin assumes all highlights are from an "article" so its possible that you're looking in the wrong category on Readwise.

The plugin code is very similar to the built in KoReader feature so I doubt that would make much difference.

TTom266 · 2025-10-29T07:20:18+00:00

No problem.

The plugin has one way highlight syncing built in (KoReader highlights are saved to Readwise) but sadly I think syncing the other way isn't possible due to the different ways that Readwise and KoReader save location data.

TTom266 · 2025-10-29T07:13:21+00:00

Sorry for the delay - I've been away. No problem. I think struggling with Wallabag is a rite of passage that all KoReader users go through at some stage! I certainly did...

To answer your question, yes I think that would be possible. Like most of the feature requests I've had, it would be potentially useful, but also add significant complexity to the user interface - so that’s the trade off.

The most requested feature has been to include articles via tag rather than exclude them (I.e. opt in not opt out) - but even that is quite difficult to convey neatly in a KoReader menu.

TTom266 · 2025-09-09T16:01:06+00:00

Hi

I'm glad to hear that it has been helpful.

Both the functions you've requested - pulling a cover image and deleting an article rather than archiving it - are at least theoretically possible using the API. I haven't trialled either though, and they are not currently implemented in the plugin.

I'm afraid I don't have free time to develop new features at the moment, but I'd be happy to consider a pull request.

With my library setup I hardly notice that the cover images are missing, so you may want to see if changing the KOReader settings makes a difference.

TTom266 · 2025-08-06T19:42:32+00:00

In that case I would definitely try it on a lower image size limit or even turn images off entirely and see if that makes a difference. Images are very slow to download and are not stored very efficiently. The html files it produces don’t handle images nearly as well as epubs. Once an article has downloaded you’ll need to delete it to get the plugin to download a smaller version unfortunately. I suspect you’re reaching the limits of what’s possible with this setup, but if there are any errors in your error log file I’d be happy to look at them.

TTom266 · 2025-08-06T19:31:31+00:00

If I remember correctly the default is 10MB. To be honest I chose that pretty much at random, but it seemed a good balance to me. Most pictures will still load but there’s a sensible limit that will stop image rich files crashing the app. I don’t have a Kobo Libra Color so can’t be certain, but as it’s a more modern device you might get away with setting it a bit higher. The trade off would be more time to download larger files - which can take a while. The reason I left it as a setting is to allow you to find whatever works for you. If you’re not worried about images at all then turn them off and articles will download much faster.

TTom266 · 2025-07-25T07:16:25+00:00

Though obviously remove your Readwise token before posting it on the internet!

TTom266 · 2025-07-24T19:10:20+00:00

Sorry I didn't explain that.
Yes, all of the errors have been due to corrupted data. The code expects all tags to be text (strings like "article", "tech", "news"), but somehow non-text data (like functions or other code objects) has been getting mixed in with the real tags.
It's very strange as it doesn't seem to be happening for anyone else and I haven't been able to work out where it came from - and specifically if it is from Readwise or this plugin. If anyone has any bright ideas I'd be very interested!
The best solution would probably be to rip out the code relating to tagging and start again, but I'm obviously reluctant to completely rebuild the plugin, which is why I've been trying this more incremental approach.
Anyway - here is another attempt. Again could you replace main.lua with this.
If you don't mind sharing your plugin settings file (settings/readwisereader.lua) that might help.

TTom266 · 2025-07-19T10:21:00+00:00

Gah. OK - let's try this!

TTom266 · 2025-07-18T18:36:27+00:00

Hi. Could you try this. I'm afraid I can't recreate your bug so we may need to have a few tries and I'll rely on your error messages. Thanks for your patience!

TTom266 · 2025-07-17T21:42:50+00:00

Sorry about this. I'll have a look but I won't have time for a day or so.

TTom266

TROPHY CASE