[Device Plugin] PocketBook Improved Driver

[zisoft]

Originally Posted by Moroz1984

But how do I sync back from Pocketbook to Calibre?

It should work automatically without further user action required, the sync works in both directions.

Please note that you cannot mark a book as "unread" (you cannot delete a read book from your brain).

[Stefan P]

Hello,

I just got my new Inkpad 4 and am trying to configure the reading status with Calibre, but unfortunately with no success.
Till Yesterday I used a Kobo with whom that workes well.

The last line in your extention in Calibre shows: "#read_stefan"
I have typed this same "#read_stefan" into the Lookup name in my new column.
When I edit this lookup name it shows only "read_stefan", but in the columns overview I still can see "#read_stefan".

However, I took a book which is marked as read in Calibre and one on the Inkpad which I marked as read. But there is noting sychronising on either sides.

The left down corner of Calibre shows that your Plugin is in use.

What is it I am doing wrong?

Stefan

[Stefan P]

Hi again,

seems I got it working meanwhile.

What I did: I was sending all the books to my new reader. After that updated the Metadata on the reader and disconnected the device.
Nothing synchroniced till there.
So I just connected the reader again, only updated the readers metadata once again and unplugged the reader.
Now my read book are marked as such on the reader

Strange, but it seems I must do that twice.

However, is there a chance to do this with my wives reader to? Of course she has read different book than I have, so she does not want my reading status on her reader.

What happens if I make to collumns in calibre, one for me and one for my wife, and always deaktivate the column which does not belong to the connected reader? Is the column still working when it is not activated / visible?

Stefan

[Titorico]

Originally Posted by zisoft

I'm currently not working on this driver (and "quiet" can mean "it simply works").

Are you missing something?

Yes !
You've been talking about collection support, should be very useful cause it's quite boring inside the reader ...
Thanks a lot for the read status sync, very useful too !

[gredie]

Hi,

i am trying to install/use this plugin, but Calibre can't connect to my PB while using this plugin.

Debug mod is telling me:

DEBUG: 11.3 PB_IMPROVED: open()
DEBUG: 11.3 PB_IMPROVED: read lookup name: #read
DEBUG: 11.3 PB_IMPROVED: Found database at path G:\system\explorer-3\explorer-3.db
DEBUG: 11.3 PB_IMPROVED: database cleanup
DEBUG: 11.4 PB_IMPROVED: 59 rows from books_settings deleted
DEBUG: 11.4 PB_IMPROVED: 42719 rows from booktogenre deleted
DEBUG: 11.4 PB_IMPROVED: 0 rows from social deleted
DEBUG: 12.0 PB_IMPROVED: 17996 rows from books_impl deleted
Unable to open device <calibre_plugins.pocketbook632.device.POCKETBOOK_I MPROVED object at 0x0000024660274070>
Traceback (most recent call last):
File "calibre\gui2\device.py", line 241, in do_connect
File "calibre_plugins.pocketbook632.device", line 82, in open
File "calibre_plugins.pocketbook632.device", line 167, in _cleanup_database
sqlite3.OperationalError: no such table: BOOKS_FAST_HASHES

device.py should be adjusted correctly:
VENDOR_ID = [0x1f85]
PRODUCT_ID = [0x6a42]
BCD = [0x9999]

Has anyone ideas how to fix this?

Thanks in advance

[vicviq]

Looks like someone figured out how to edit collections on a Pocketbook:
- thread on Mobileread talking about it
- source code of the main file of the application "doing the things"

Is there a chance of this functionality getting included in the plugin?

[vicviq]

It looks like someone figured out how to work with collections on a PocketBook:

• Mobileread thread talking about it
• source code of the main part of the application "doing the things"

Any chance of this functionality getting included in the plugin? Thank you!

[vicviq]

Ugh, apologies for double post, it didn't show up when I first posted

[Titorico]

Oh please ! Would be so useful to manage collections with Calibre ...
Thanks !

[zisoft]

Just released Version 1.0.4
Support for Inkpad Color 3 devices

[libeluratio]

Originally Posted by zisoft

Just released Version 1.0.4
Support for Inkpad Color 3 devices

Hi,

thank you very much for the update.

This sometimes works, but very often the Inkpad Color 3 is still detected as a "Diva HD" device as you can see in the picture attached:



Is there any way you could maybe correct this with a new update ?

Thank you !

[Grins]

Thank you very much for this plugin. Works wonderful! (MacBook M1 Pro, calibre 7.20, plugin 1.0.4, Pocketbook Inkpad Color 3).

The small cosmetic defect - device shown as "Diva" - mentioned in the last post above does not affect the functionality for me. In fact, sometimes "Diva" and sometimes "PocketBook Improved" seems to be used. Maybe it depends on whether the erader was turned on or just woken up from sleep.

[CoreTheMan]

Originally Posted by libeluratio

Hi,

thank you very much for the update.

This sometimes works, but very often the Inkpad Color 3 is still detected as a "Diva HD" device as you can see in the picture attached:



Is there any way you could maybe correct this with a new update ?

Thank you !

I simply deactivated the DivaHD plugin in settings-plugins, so the PB improved is always used.

[CoreTheMan]

I have a Verse Pro Color, and the "Read" Column update doesn't work.
To get an idea what might go wrong I started calibre from the console with calibre_debug -g, and the output shows that the open() method is called -> plugin is used (as I can also see from the left lower corner display).
However, if I mark a book or two and send them to my device, there is no debug info from the plugin in the console...it says
Device using plugboard epub POCKETBOOK_IMPROVED None (sounds good)
but then no other message. I think this means that the synchronize_with_db() method doesn't seem to be called. There is a line "debug_print('PB_IMPROVED: start sychronize_with_db')" in device.py, which should lead to some output, right?
So can you guide me to what I might be missing?

[CoreTheMan]

My bad...I have to press the respective function in the Ui first. I somehow thought this function is executed always...