Calibredb --search ondevice:true not returning any results

Meelibomin · 10-10-2022, 03:08 PM

Hello everyone,

I'm trying to use the search option with calibredb list. The list comes up empty everytime I add this filter to the cmd. I'm using Windows 10, Calibre V6.

I've tried:
--search ondevice:true
--search "ondevice:true"
--search=ondevice:true
--search="ondevice:true"
--search="ondevice:"""=true"
--search='ondevice:"true"'
Along with the same variations using --s

I've also tried creating a custom column using program: ondevice() and using --search on that column instead, but to no avail. Using calibredb catalog with this search also doesn't work for me. All other fields available for --search seem to otherwise work fine for both list and catalog.

Searching ondevice:true works fine on the GUI. But I know I can't have both the GUI and calibredb cmd running at the same time.
Using ebook-device books (from the command line) works, and calibre-debug debug-device-driver correctly outputs my device. So it's left me quite confused.

Is there something I can do to make the calibredb --search option work with ondevice either using list or catalog?

kovidgoyal · 10-10-2022, 03:09 PM

ondevice only works in the GUI. calibredb knows nothing about connected devices.

Meelibomin · 10-10-2022, 07:08 PM

Thanks for clarifying, Kovid. I did read that in the manual, but got hopeful reading old blogs with outdated info on using calibredb that I came across in some google searches haha. Then of course, deluded myself into thinking ondevice is mentioned in the actual calibredb manual, when it's not at all. My bad!

10-10-2022, 03:08 PM	#1
Meelibomin Junior Member Posts: 2 Karma: 10 Join Date: Oct 2022 Device: Onyx Boox Poke3	Calibredb --search ondevice:true not returning any results Hello everyone, I'm trying to use the search option with calibredb list. The list comes up empty everytime I add this filter to the cmd. I'm using Windows 10, Calibre V6. I've tried: --search ondevice:true --search "ondevice:true" --search=ondevice:true --search="ondevice:true" --search="ondevice:"""=true" --search='ondevice:"true"' Along with the same variations using --s I've also tried creating a custom column using program: ondevice() and using --search on that column instead, but to no avail. Using calibredb catalog with this search also doesn't work for me. All other fields available for --search seem to otherwise work fine for both list and catalog. Searching ondevice:true works fine on the GUI. But I know I can't have both the GUI and calibredb cmd running at the same time. Using ebook-device books (from the command line) works, and calibre-debug debug-device-driver correctly outputs my device. So it's left me quite confused. Is there something I can do to make the calibredb --search option work with ondevice either using list or catalog? Last edited by Meelibomin; 10-10-2022 at 03:10 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
New Feature? Embed search term as a tag into Search Results with one click?	mikhail_fil	Library Management	1	04-02-2022 11:18 PM
Search results only show first result. How can I view successive results?	lovedj1	Calibre	2	05-07-2021 08:53 AM
Forma Search-in-book results sometimes ends on page17, even if there's more (hidden)results	droopy	Kobo Reader	9	06-30-2020 12:05 PM
calibredb inconsistent title: search results	Terry Brown	Library Management	2	05-05-2020 12:29 PM
Search library and ondevice	AlanB	Library Management	4	07-22-2018 02:53 PM

10-10-2022, 03:09 PM	#2
kovidgoyal creator of calibre Posts: 44,764 Karma: 24967300 Join Date: Oct 2006 Location: Mumbai, India Device: Various	ondevice only works in the GUI. calibredb knows nothing about connected devices.

10-10-2022, 07:08 PM	#3
Meelibomin Junior Member Posts: 2 Karma: 10 Join Date: Oct 2022 Device: Onyx Boox Poke3	Thanks for clarifying, Kovid. I did read that in the manual, but got hopeful reading old blogs with outdated info on using calibredb that I came across in some google searches haha. Then of course, deluded myself into thinking ondevice is mentioned in the actual calibredb manual, when it's not at all. My bad!