- #Gpodder device sync metadata how to#
- #Gpodder device sync metadata android#
- #Gpodder device sync metadata download#
Last edited by bailewen January 22nd, 2012 at 04:05 AM. In the view settings of all of your metadata-driven views, set the Folders option to Show all items without folders (see screenshot). I just figured out that it's only happening on some podasts and not on others.
#Gpodder device sync metadata download#
That means that when transfered to a player all of the Gpodder files, when sorted by podcast title, show up as "Unknown" and if you just go by individual file titles you get a bunch of 10 digit number followed by some obscure abbreviation.Īny suggestions other than going back to Miro/Rythmnbox/Amarok? None of them download and sort podcasts to my laptop very smoothly compared to Gpodder.
With Gpodder, I end up with a file called "20120120_totn_01" and no metadata beyond the fact that it's a3.9 mg mp3. With itunes, the file name in my MP3 player would be ""Defending Climate Science's Place In The Classroom" and the metadata would show that it was downloaded on such and such date from "NPR: Talk of the Nation". So maybe the filename is write and it's missing some metadata.īy way of example, I just downloaded "Defending Climate Science's Place In The Classroom" from NPR. I generally end up with file name that is just the date + some sort of abbreviation of the title. mp3 or Mp4u or whatever ends up with a garbage file name which prevents my phone or other device from sorting the podcasts by title. I like to load up a lot of podcasts on my cellphone and in general gpodders seesm to be the top podcast aggregator but it has one major problem.while the podcasts show up with proper titles in Gpodder, when you synchronize, or even just export the file to your desktop, the.
#Gpodder device sync metadata how to#
“episodes”: ],įile “/home/homeassistant/.homeassistant/custom_components/gpodder/ init.py”, line 161, inįile “/home/homeassistant/.homeassistant/custom_components/gpodder/ init.Looking for any suggestions on how to work out this bug/issue with Gpodder. Hass.data = update_using_feedservice(urls)įile “/home/homeassistant/.homeassistant/custom_components/gpodder/ init.py”, line 161, in update_using_feedservice 09:51:16 ERROR (MainThread) gpodder: Error on device update!įile “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py”, line 312, in _async_add_entityĪwait entity.async_device_update(warning=False)įile “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py”, line 474, in async_device_updateįile “/home/homeassistant/.homeassistant/custom_components/gpodder/sensor.py”, line 27, in async_updateĪwait update_data(self.hass, self._device)įile “/home/homeassistant/.homeassistant/custom_components/gpodder/ init.py”, line 110, in update_data Hi, is there an actual limit to the amount of subscriptions you can add? Every time I try to add a third I get an error: What else can I do and/or change to get all my subscriptions in Home Assistant? My next attempt would be to use the version linked in 's gist however, that is just the card, and the problem seems to be with the sensor itself.
#Gpodder device sync metadata android#
However, I was hoping to use all my podcasts as this would allow me to sync with my Android app. So then I tried to (manually) deleting all podcasts listed like Unknown Podcast from (the ones that neither display the correct logo nor podcast title). Just now I deleted the device on, re-created it (after permanently removing it from trash as well), and uploaded a test. With Podcasts - the device automatically keeps track of how far the.
I also deleted all (well, the one) podcasts with special characters to make sure that this was not causing this problem. Im using a NWZ-E464 walkman to sync podcasts using direct filesystem access on a. opml export from my android podcast player. On I set up a new device called homeassistant and imported my. My sensor.gpodder won’t show podcasts podcasts: ĭefault_target: media_player.schlafzimmer_2
0 kommentar(er)
