-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
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
Tibber getPrices failing when subscription is about to end #131881
Comments
Hey there @Danielhiversen, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tibber documentation |
Same here, i ended my subscription and now the price is not available the rest of the time until it ends |
FYI: Tibber Support answered with: "Uns ist das von dir beschriebene Anliegen bereits bekannt und wir arbeiten bereits an einer schnellen Lösung. Vielen Dank für deine Geduld." → Translation: It's a known issue and we're already working on it. That's for your patience." |
Temporary workaround for the issue:Access your Home Assistant via SSH:(For SSH access, I am using the Run the following commands:
Modify the code:Once you open the file in vi, navigate to line 324, where you'll find the function
Add
|
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. |
The problem
I debugged an issue with no longer getting hourly prices.
Reason seems that I recently cancelled my tibber tariff (which is still active some weeks) and now the tibber API lists my subscription as „ended“:
But the tibber integration only seems to read prices for an „active“ subscription:
core/homeassistant/components/tibber/services.py
Line 47 in d596b41
Looking into pyTibber I think my guess seems right:
https://github.com/search?q=repo%3ADanielhiversen%2FpyTibber+only_active&type=code
I already informed the Tibber support about this issue, hoping they can fix this on their end.
But I think it should somehow be possible to work around such an issue by maybe having a setting for this?!
Thanks a lot for your great work with all this. Hope someone can look into this soon.
Kind regards
Björn
What version of Home Assistant Core has the issue?
core-2024.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tibber
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tibber
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: