KoboSync & Calibre-Web

[Dirk-71]

Is there anyone syncing books on Kobo devices with Calibre-Web?

It did work earlier but now I think, Kobo has blocked it in the latest firmware updates.

[JSWolf]

Originally Posted by Dirk-71

Is there anyone syncing books on Kobo devices with Calibre-Web?

It did work earlier but now I think, Kobo has blocked it in the latest firmware updates.

Which firmware are you running?

[Dirk-71]

Clara Bw: 4.46.23836
Libra 2: 4.38.23697

The latest firmware.

[PeterT]

What version of calibre web?

[Dirk-71]

Always the latest version of docker....

[PeterT]

I doubt that Kobo would do anything to break the integration. I d suggest validating against the Calibre Web Kobo integration wiki and following the documented problem shooting steps. https://github.com/janeczku/calibre-...bo-Integration


Sent from my SM-X238U using Tapatalk

[Dirk-71]

Ok, I'll look into it. So, it works for you? No issues?

[PeterT]

|I never said I used it!

[Dirk-71]

It works with Calibre-Web Automated, both: internally and with Tailscale externally. It took a while I got through to it.

[mgrimace]

Yes, happily using Calibre-Web Automated Next-Gen, link: https://github.com/new-usemame/Calibre-Web-NextGen on a KLC on current firmware using the Kobo Sync API.

Next-gen is the currently maintained fork of Automated, which in turn was a maintenance and feature fork of Calibre-Web (o.g.). I can't recommend it enough, especially as the 'sysadmin' for my family's devices.

[Dirk-71]

Originally Posted by mgrimace

I can't recommend it enough

I never heard about Nextgen CW before and have tested it shortly. What I've seen is really promising. KoboSync works great.

Only loading the book-covers is a bit slow.

Thank you for sharing.

[rantanplan]

I have a few weeks of experience with NextGen. It’s slightly heavier on the CPU, though it’s only noticeable for me because I use a Raspberry Pi 4 and don’t want to pay the current ram prices.

[Dirk-71]

Concerning KoboSync NextGen is by far the best of all CW-versions I have tested. KoboSync is often a mess, especially if you have to sync more than 1 reader. NextGen doesn't disappoint here. It's reliable and stable as it should be. Really good job!

Currently one has to switch to the CWA-GUI in order to get all available options (e.g. KoboSync-Token). And for the magic bookshelf there is no option to sync with Kobo devices.

I stick with NextGen and looking forward for further improvements.

[mgrimace]

It's entirely off-topic, but the other quality-of-life service I add into the mix is Rakuyomi for Manga because its streaming, no downloads/conversion or messing with metadata(!).

Kobo sync API and Nickel/kobo for standard books, then tap Koreader via nicklemenu to jump right into manga library. Keeps things nice and tidy.

Nicklemenu > Koreader > Rakuyomi, with a startup plugin to jump right into manga library when Koreader is launched.

[DaRon]

Hi there,
i am a bit desperate already and i hope you can give me a hint, where i took the wrong turn.

My Setup:
CWNG v4.1.59 in a docker environment with nginx as reverse proxy
Kobo Libra Colour (v4.46.23852)

NGINX config (for the proxy part)

location /books/ {
proxy_bind $server_addr;
proxy_pass http://127.0.0.1:8083;
proxy_set_header Host $host;
proxy_set_header X-Script-Name /books;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffer_size 1024k;
proxy_buffers 4 512k;
proxy_busy_buffers_size 1024k;
client_max_body_size 50M;
}

docker compose

services:
calibre-web-automated:
# --> CWA image: ghcr.io/crocodilestick/calibre-web-automated:latest
# --> CWNGimage: ghcr.io/new-usemame/calibre-web-nextgen:latest
image: ghcr.io/new-usemame/calibre-web-nextgen:v4.1.59
container_name: calibre-web-automated
environment:
- PUID=33
- PGID=1002
- TZ=Europe/Vienna
# - NETWORK_SHARE_MODE=false
- NETWORK_SHARE_MODE=true
- DESKTOP_COMPAT_MODE=true
- CWA_PORT_OVERRIDE=8083
- PROXY_SCRIPT_NAME=/books
volumes:
- /home/daron/docker/calibre-books/config:/config
- /home/daron/docker/calibre-books/ingest:/cwa-book-ingest
- "/home/daron/library:/calibre-library"
- /home/daron/docker/calibre-books/plugins:/config/.config/calibre/plugins
ports:
- 127.0.0.1:8083:8083
restart: unless-stopped

My Kobo conf

[ApplicationPreferences]
SideloadedMode=true

[OneStoreServices]
api_endpoint=https://domain.tld/books/kobo/7fd9f3092e5a8e1bd4b03413129c6fdb

Here's what i did:
1) Enabled Kobo Sync
2) generated a token
3) edited the kobo config (on the Kobo device)
4) rebooted the Kobo
5) tried to sync
Note: the Kobo was working before just fine, nevertheless, i did a full factory reset (via devmode) in order to start from scratch ;-)

Problem:
When trigger a sync ion the Kobo, nothing will be synced.

Here are some findings:
1) when i use the browser (or curl) and browse to the api endpoint (which is also configured on the Kobo device)

https://domain.tld/books/kobo/7fd9f3092e5a8e1bd4b03413129c6fdb/v1/initialization

I get (among many other lines, of course) the following line back:

"library_sync":"https://domain.tld/books/kobo/7fd9f3092e5a8e1bd4b03413129c6fdb/v1/library/sync"

2) when i browse (or curl) to the just received sync url, i get a list of books back

--> so, it seems, that everything is working as it should.

BUT:
1) when i use the Kobo with the following config (among others):

api_endpoint=https://domain.tld/books/kobo/7fd9f3092e5a8e1bd4b03413129c6fdb

I get (among many other lines, of course) the following line back:

"library_sync":"https://storeapi.kobo.com/v1/library/sync"

(I don't actually get it "back", I can find this part in the docker logs)

--> so, it seems, that the sync "request" is forwarded (if even received by CWNG) to Kobo (i am not logged in and the Kobo is in SideLoadeMode)

So, is there anything i messed up or configured wrong? do you have any idea where the root cause of this problem could be? Any log or anything else i could possibly check?

thank you very much in advance!

Ron

PS: i posted this question also in the discussion area on gh (https://github.com/new-usemame/Calib...scussions/2781), maybe with slightly different keys or ids (tried a few things since yesterday). But either way, the behaviour is the same.
If there will be a solution available on either side (gh or here), I will update the other side respectively.