[GUI Plugin] OverDrive Libby

[Ellsinore]

Originally Posted by sgmoore

Depends on where you installed it from.

Since ping (who wrote this plugin) is not around, the official plugin no longer works and you need to use my patched version from https://github.com/sgmoore/libby-calibre-plugin

This fixes the certificate error, but does not fix other issues. In particular, it does not allow you to download books or magazines and you still need to get the token manually.

Features that still work are - viewing your current loans and holds, searching for books, borrowing, placing holds and returning books.

Unfortunately I installed from Calibre. I don't understand the Plugin Universe, especially in this case. One that doesn't work.

I'm sorry I'm so frustrated. I got a new Kobo and spent almost two weeks trying to get it to work with Calibre. Returned it the other day. So, just use my tablet, which has been working just fine, but let's step that up. No.

I'm way beyond my geek years where I gleefully spend hours, days, weeks trying to get things tweaked. Now? Looking for stuff that works out of the box. Turns out, that's harder to find than you'd think!

Thanks for the explanation(s)!

[lumping-sugar66]

Originally Posted by Ellsinore

I'm sorry I'm so frustrated. I got a new Kobo and spent almost two weeks trying to get it to work with Calibre.

FWIW, you don't need this plugin to borrow books from libraries. So long as you have deACSM installed, you can go to libby website, borrow the DRM-protected ascm file (don't click open the book with libby) and drag&drop it into calibre.

This deACSM setup you need to do anyway. So it's a hassle to download the book files from the website but it doesn't mean using calibre to manage borrowed books is unusable.

[Terisa de morgan]

Thank you for all the information. The new plugin has solved the certificate issue and the token I've been able to get it, so I have it working again for the interesting part for me (holds).

[JSWolf]

Originally Posted by Terisa de morgan

Thank you for all the information. The new plugin has solved the certificate issue and the token I've been able to get it, so I have it working again for the interesting part for me (holds).

Since the new plugin is working, can it please be put in the first post?

[PeterT]

Originally Posted by JSWolf

Since the new plugin is working, can it please be put in the first post?

I'd suggest that before that happens, someone needs to update the internal version number to reflect the changes... Currently it still reads 1.9

[DNSB]

I modified the .zip file for the plugin downloaded from sgmoore's link to report the version number as 0.1.9.1 to distinguish it from 0.1.9

[danamr]

Originally Posted by Ellsinore

Unfortunately I installed from Calibre. I don't understand the Plugin Universe, especially in this case. One that doesn't work.

I'm sorry I'm so frustrated. I got a new Kobo and spent almost two weeks trying to get it to work with Calibre. Returned it the other day. So, just use my tablet, which has been working just fine, but let's step that up. No.

I'm way beyond my geek years where I gleefully spend hours, days, weeks trying to get things tweaked. Now? Looking for stuff that works out of the box. Turns out, that's harder to find than you'd think!

Thanks for the explanation(s)!

@74 I'm don't have the patience to screw around trying to get stuff working.
A thought. Have you tried the Libby app for library books on your tablet? It works fine on iPadOS, MacOS and AndroidOS.

[foosion]

Originally Posted by Terisa de morgan

Thank you for all the information. The new plugin has solved the certificate issue and the token I've been able to get it, so I have it working again for the interesting part for me (holds).

I'm glad to see someone agrees with me that the plugin continues to be useful. Search/hold/borrow works nicely for the moment and is easier for me than using libby. When the book is available I download the acsm file with libby, double click and the book shows up in Calibre. Not as convenient as before, but still better for me than the alternatives.

[Ellsinore]

Originally Posted by danamr

@74 I'm don't have the patience to screw around trying to get stuff working.
A thought. Have you tried the Libby app for library books on your tablet? It works fine on iPadOS, MacOS and AndroidOS.

Hi!

You've got me beat, but I'm right behind you. :-D

I already use Libby on my phone, tablet and PC. I also have a huge eBook library, as well a "real" books.

I really, really wanted to get a handle on organizing and Calibre is the #1 recommendation from Google results. My struggle with this plugin is only the latest frustration. I'm not sure when I first installed Calibre, but it was a long, LONG time ago. And it keeps getting put back on the shelf. Or uninstalled.

It just seems anything that sounds neet and I want to customize, it's a rabbit trail. I'm getting notifications from this thread and was so excited to see the plugin was updated! But NO. Still won't work. Can only get a pass key, not a set up code. Someone else mentioned this, but I didn't see any responses to it. I DO see lots of people who are happy with the update, though! :-D

And I'm happy FOR them!

[foosion]

Now nothing is working. The error message includes "error_response='{"result":"missing_chip"}" which was not there previously.

Spoiler:

calibre, version 7.19.0
ERROR: Unhandled exception: <b>ClientForbiddenError</b>: Error synchronizing data<p>HTTP Error 403: Forbidden</p>

calibre 7.19  embedded-python: True
Windows-10-10.0.19045-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19045')
Python 3.11.5
Windows: ('10', '10.0.19045', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: C:\Program Files\Calibre2\calibre.exe
Successfully initialized third party plugins: DeACSM (0, 0, 16) && DeDRM (10, 0, 3) && Action Chains (1, 20, 7) && EpubSplit (3, 6, 0) && Find Duplicates (1, 6, 3) && KePub Output (3, 6, 11) && Kindle hi-res covers (0, 5, 1) && Kobo Utilities (2, 17, 1) && KoboTouchExtended (3, 6, 11) && Modify ePub (1, 8, 4) && OverDrive Libby (0, 1, 9) && Reading List (1, 15, 4) && SmartEject (2, 5, 1)
Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.libby.client", line 520, in send_request
  File "urllib\request.py", line 525, in open
  File "urllib\request.py", line 634, in http_response
  File "urllib\request.py", line 563, in error
  File "urllib\request.py", line 496, in _call_chain
  File "urllib\request.py", line 643, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.workers", line 381, in run
  File "calibre_plugins.overdrive_libby.libby.client", line 633, in sync
  File "calibre_plugins.overdrive_libby.libby.client", line 540, in send_request
  File "calibre_plugins.overdrive_libby.libby.errors", line 143, in process
calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError: <calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError; http_status=403, msg='HTTP Error 403: Forbidden', error_response='{"result":"missing_chip"}''>

[miss_p1nky]

Originally Posted by foosion

Now nothing is working. The error message includes "error_response='{"result":"missing_chip"}" which was not there previously.

Spoiler:

calibre, version 7.19.0
ERROR: Unhandled exception: <b>ClientForbiddenError</b>: Error synchronizing data<p>HTTP Error 403: Forbidden</p>

calibre 7.19  embedded-python: True
Windows-10-10.0.19045-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19045')
Python 3.11.5
Windows: ('10', '10.0.19045', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: C:\Program Files\Calibre2\calibre.exe
Successfully initialized third party plugins: DeACSM (0, 0, 16) && DeDRM (10, 0, 3) && Action Chains (1, 20, 7) && EpubSplit (3, 6, 0) && Find Duplicates (1, 6, 3) && KePub Output (3, 6, 11) && Kindle hi-res covers (0, 5, 1) && Kobo Utilities (2, 17, 1) && KoboTouchExtended (3, 6, 11) && Modify ePub (1, 8, 4) && OverDrive Libby (0, 1, 9) && Reading List (1, 15, 4) && SmartEject (2, 5, 1)
Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.libby.client", line 520, in send_request
  File "urllib\request.py", line 525, in open
  File "urllib\request.py", line 634, in http_response
  File "urllib\request.py", line 563, in error
  File "urllib\request.py", line 496, in _call_chain
  File "urllib\request.py", line 643, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.workers", line 381, in run
  File "calibre_plugins.overdrive_libby.libby.client", line 633, in sync
  File "calibre_plugins.overdrive_libby.libby.client", line 540, in send_request
  File "calibre_plugins.overdrive_libby.libby.errors", line 143, in process
calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError: <calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError; http_status=403, msg='HTTP Error 403: Forbidden', error_response='{"result":"missing_chip"}''>

+1, mine won't sync.

Spoiler:

calibre, version 7.19.0
ERROR: Unhandled exception: <b>ClientForbiddenError</b>: Error synchronizing data<p>HTTP Error 403: Forbidden</p>

calibre 7.19  embedded-python: True
Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.libby.client", line 520, in send_request
  File "urllib\request.py", line 525, in open
  File "urllib\request.py", line 634, in http_response
  File "urllib\request.py", line 563, in error
  File "urllib\request.py", line 496, in _call_chain
  File "urllib\request.py", line 643, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "calibre_plugins.overdrive_libby.workers", line 381, in run
  File "calibre_plugins.overdrive_libby.libby.client", line 633, in sync
  File "calibre_plugins.overdrive_libby.libby.client", line 540, in send_request
  File "calibre_plugins.overdrive_libby.libby.errors", line 143, in process
calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError: <calibre_plugins.overdrive_libby.libby.errors.ClientForbiddenError; http_status=403, msg='HTTP Error 403: Forbidden', error_response='{"result":"missing_chip"}''>

[foosion]

I do wonder about "error_response='{"result":"missing_chip"}". I see it was mentioned in https://github.com/ping/odmpy/issues/69 and #115 in this thread, but those are from April and the plugin was working after that. That's a different error from the one I was getting when download failed but other functions were working.

[sgmoore]

Originally Posted by foosion

Now nothing is working. The error message includes "error_response='{"result":"missing_chip"}" which was not there previously.

Sorry for the delay in responding, but I missed this message.

The forbidden/missing_chip message simply means you need to manually refresh your token.

I'm still using simon-techkid's extension to get the token : see https://github.com/ping/libby-calibr...ent-2305881945

The bad news is that unfortunately we are going to have to do this a lot more regularly (probably every week)

The token contains an expiry date and stops working after a week. What used to happen was when you synced successfully, the response you got back contained a new token with an updated expiry date and ping's code saved this token back for use the next time. So simply opening this plugin regularly would keep refreshing the token and it did not expire.

Now the response from libby website no longer returns a new token and so the token we have will expire after a week.

[foosion]

Originally Posted by sgmoore

Sorry for the delay in responding, but I missed this message.

The forbidden/missing_chip message simply means you need to manually refresh your token.

I'm still using simon-techkid's extension to get the token : see https://github.com/ping/libby-calibr...ent-2305881945

The bad news is that unfortunately we are going to have to do this a lot more regularly (probably every week)

The token contains an expiry date and stops working after a week. What used to happen was when you synced successfully, the response you got back contained a new token with an updated expiry date and ping's code saved this token back for use the next time. So simply opening this plugin regularly would keep refreshing the token and it did not expire.

Now the response from libby website no longer returns a new token and so the token we have will expire after a week.

That works for everything other than actually download a book, for which I'm still getting a 403 forbidden error. simon-techkid's extension makes it much easier to update the token.

Is there something else I should be doing so that I can download books using this plugin or is that gone?

Thank you!

[PeterT]

Originally Posted by sgmoore

Sorry for the delay in responding, but I missed this message.

The forbidden/missing_chip message simply means you need to manually refresh your token.

I'm still using simon-techkid's extension to get the token : see https://github.com/ping/libby-calibr...ent-2305881945

The bad news is that unfortunately we are going to have to do this a lot more regularly (probably every week)

The token contains an expiry date and stops working after a week. What used to happen was when you synced successfully, the response you got back contained a new token with an updated expiry date and ping's code saved this token back for use the next time. So simply opening this plugin regularly would keep refreshing the token and it did not expire.

Now the response from libby website no longer returns a new token and so the token we have will expire after a week.

I also found installing mitmproxy was an invaluable tool in capturing the token. This also lets you see all the requests and responses inb what I found to be an easier format to read than the chrome internal network logging.