Home Assistant release with the issue:
0.76.1
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
PocketCast
Description of problem:
Component is broken, errors:
Connection to server failed: 403 Client Error: Forbidden for url: https://play.pocketcasts.com/users/sign_in
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
- platform: pocketcasts
username: !secret my_email
password: !secret my_pass
Traceback (if applicable):
Additional information:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Still getting the same error on 0.80.3. It looks like the dev for the library that this component depends on has abandoned his project. It might be time to remove this Component from the website...
I have it working, but I need to clean up the code.

If you want to test it out, you can update the api.py for pocketcasts with my patched version. Keep in mind that it's still under construction.
Use linux find to located the correct file.
find / -name 'pocketcasts'
My location (docker) was: /usr/local/lib/python3.6/site-packages/pocketcasts/api.py
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still not working in 0.95.4
Not working in 0.95.4; any thoughts of branches that fix the issue?
Not working for me either with the same error in 0.106.6