Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 12-24-2020, 07:03 AM   #2053
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Barruel View Post
Thank you very much, David.

I updated the firmware after flashing the sd image and the version file had the correct serial number, so it had to be file deviceinfo.metadata (which I found in the root of the device as driveinfo.metadata). I just deleted that file and now all 3 Claras are detected as different devices.

It seems that the plugin is looking at that file and saving the settings as belonging to the uuid in it. After it has it saved to Kobo utilities.json, it just reads driveinfo.metadata and looks at the version file only when saving the backup, but not at plugin startup. That explains why the backups had the correct s/n but 2 of my devices were being detected as the same device having the same s/n. Is it possible?
Yes, the configuration is stored for the UUID. That is largely because the code to do this is based on code from another plugin (Reading list). I have considered changing it, but, the only time it matters is in cases like yours (very rare) and if something happens to the deviceinfo.calibre file. In that case, the configuration will need to be done again. It just hasn't bugged me enough to want to do it, and I'm not sure the alternatives are actually better.

And, except for the display in the configuration dialog, the serial number is read from the file each time it is needed. For the configuration dialog, it is stored in the configuration, but, you can open the configuration when no device is connected and see what the known devices are.
davidfor is offline