-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
pvpc_hourly_pricing integration is broken since 2021-11-02 #58986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
pvpc_hourly_pricing documentation |
Not involved at all, but I just saw this |
So now there is nothing we can do locally to patch the issue... Or can we add by hand the User-Agent header until a new version is released? Thanks a lot for this integration. Rom |
@deltazerorsan, the quickest way of solving it: azogue/aiopvpc#27 (comment) (install as custom_component with attached zip) |
Perfect man! Working again... Thanks a lot! |
Thank you @azogue , you are always really quick fixing this integration. |
The problem
Some configuration has changed in the public server https://api.esios.ree.es and now it's returning a 403 Forbidden for the API call used to retrieve electricity prices.
The solution is easy, but tricky and somehow unexpected. It works just by:
aiohttp
to 3.8.0 from the current 3.7.4.post0 🤷A version patch for the
aiopvpc
library has been published (with just option 1, adding the header), and I'll push the PR with the version bump before EOD, but as right now I'm very disconnected from theaiohttp
lib (using httpx for everything), I thought this detail appreciation could be useful for someone ¿?What version of Home Assistant Core has the issue?
2021.11.b4
What was the last working version of Home Assistant Core?
2021.10.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
pvpc_hourly_pricing
Link to integration documentation on our website
https://www.home-assistant.io/integrations/pvpc_hourly_pricing/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: