MobileRead Forums - View Single Post - [Kobo] "update reading progress" suddenly not working?

davidfor · 01-20-2019, 06:00 AM

Fetching the reading status from Kobo devices is handled by the Kobo Utilities plugin. From the log, there is no configuration for fetching the reading status from the connected device. This is shown in the line:

Code:

DEBUG:   28.8 KoboUtilites:_on_device_metadata_available - self.current_device_profile: None

The other lines important to what is happening are earlier:

Code:

DEBUG:   28.8 KoboUtilities:get_device - drive_info: {'main': {u'date_last_connected': u'2019-01-19T22:40:28.424000+00:00', u'device_store_uuid': u'4c0225af-271c-4134-84b7-8068a3fdb716', u'prefix': 'H:/', u'device_name': u'Kobo Aura H2O Edition 2', u'calibre_version': u'3.38.1', u'last_library_uuid': u'b6b17ac3-bab9-4664-9da2-3adf8f707180', u'location_code': 'main'}}
DEBUG:   28.8 migrate_library_config_if_required - start
DEBUG:   28.8 get_library_config - library_config: {u'readingPositionChangesStore': {u'selectBooksInLibrary': False, u'updeateGoodreadsProgress': True}, u'profiles': {u'Default': {u'forDevice': u'c6c577eb-fc5d-4834-9052-55b89aa9fbd8', u'storeOptionsStore': {u'storeOnConnect': True, u'promptToStore': True, u'doNotStoreIfReopened': False, u'storeIfMoreRecent': False}, u'customColumnOptions': {u'currentReadingLocationColumn': u'#readlocnow', u'percentReadColumn': u'#readperc', u'lastReadColumn': u'#lastreadtime', u'ratingColumn': u''}, u'profileName': u'Default', u'updateOptionsStore': {u'firmwareUpdateCheckLastTime': 0, u'doEarlyFirmwareUpdate': False, u'doFirmwareUpdateCheck': False}}}, u'SchemaVersion': 0.1}

The first line is the contents of the file calibre.metadata on the device. The highlighted bit is the device id that calibre uses. The third line is the configuration for the plugin. The highlight is the id of the device that you have configured the settings for. As the ids are different, the plugin considers this to be a different device.

The id in calibre.metadata generated when the device is first seen by calibre. It shouldn't change. Unless you delete the file, or do a factory reset. After one of those the id will be different and the plugin will see the device a different device. You can see this in the "Devices" tab of the plugins configuration dialog. This lists the devices known to the plugin. If a known device is connected, there will be an icon in the "Status" column. If the currently connected device is not known, the "Add connected device" button will be enabled.

If you only have one Kobo device, then select "*Any device" for the profile. Only choose individual devices names for the profile if you have multiple devices and want to treat them differently.

01-20-2019, 06:00 AM	#3
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Fetching the reading status from Kobo devices is handled by the Kobo Utilities plugin. From the log, there is no configuration for fetching the reading status from the connected device. This is shown in the line: Code: DEBUG: 28.8 KoboUtilites:_on_device_metadata_available - self.current_device_profile: None The other lines important to what is happening are earlier: Code: DEBUG: 28.8 KoboUtilities:get_device - drive_info: {'main': {u'date_last_connected': u'2019-01-19T22:40:28.424000+00:00', u'device_store_uuid': u'4c0225af-271c-4134-84b7-8068a3fdb716', u'prefix': 'H:/', u'device_name': u'Kobo Aura H2O Edition 2', u'calibre_version': u'3.38.1', u'last_library_uuid': u'b6b17ac3-bab9-4664-9da2-3adf8f707180', u'location_code': 'main'}} DEBUG: 28.8 migrate_library_config_if_required - start DEBUG: 28.8 get_library_config - library_config: {u'readingPositionChangesStore': {u'selectBooksInLibrary': False, u'updeateGoodreadsProgress': True}, u'profiles': {u'Default': {u'forDevice': u'c6c577eb-fc5d-4834-9052-55b89aa9fbd8', u'storeOptionsStore': {u'storeOnConnect': True, u'promptToStore': True, u'doNotStoreIfReopened': False, u'storeIfMoreRecent': False}, u'customColumnOptions': {u'currentReadingLocationColumn': u'#readlocnow', u'percentReadColumn': u'#readperc', u'lastReadColumn': u'#lastreadtime', u'ratingColumn': u''}, u'profileName': u'Default', u'updateOptionsStore': {u'firmwareUpdateCheckLastTime': 0, u'doEarlyFirmwareUpdate': False, u'doFirmwareUpdateCheck': False}}}, u'SchemaVersion': 0.1} The first line is the contents of the file calibre.metadata on the device. The highlighted bit is the device id that calibre uses. The third line is the configuration for the plugin. The highlight is the id of the device that you have configured the settings for. As the ids are different, the plugin considers this to be a different device. The id in calibre.metadata generated when the device is first seen by calibre. It shouldn't change. Unless you delete the file, or do a factory reset. After one of those the id will be different and the plugin will see the device a different device. You can see this in the "Devices" tab of the plugins configuration dialog. This lists the devices known to the plugin. If a known device is connected, there will be an icon in the "Status" column. If the currently connected device is not known, the "Add connected device" button will be enabled. If you only have one Kobo device, then select "*Any device" for the profile. Only choose individual devices names for the profile if you have multiple devices and want to treat them differently.