entity is no longer provided by the integration - unavailable since 4 pm october 14th #417
Comments
|
Same for Finland after last restart, version 0.0.14, and HA version 2024.10.2 This link doesn't lead anywhere: File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1243, in json Page Not Found We hope you'll find what you need on our website: nordpoolgroup.com If you're searching for Market Data, you can find it on our Data Portal. Logger: homeassistant.config_entries Error setting up entry Nordpool for sensor Logger: homeassistant.config_entries Error setting up entry Nordpool for sensor During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
Same for me (also DE-LU), also 14th. I was suspecting the problem being the API change referenced to in the 0.0.15 release notes. Maybe that is the problem as I also have 0.0.14 installed. At least it is what is shown on the 'local' integrations page. I have no option to update to 0.0.15 in 'updates' of home assistant. Just a thought what COULD be the problem. Did not do detailed logging but what I personally get is: 2024-10-15 09:05:18.981 DEBUG (MainThread) [custom_components.nordpool] Added nordpool to hass.data MAYBE re-installing COULD work if that is the problem but did not have time to check that as of now. But maybe I am completely wrong too :D |
|
I updated to 0.0.15 and rebooted, now the values are
nordpool |
|
maybe that is the reason that no update is shown by HA 'update function' and so if you do not update manually you still have the version in place that does not work with the changed api. but just a wild speculation (sorry if that does not technically help) |
|
OK, And then out of nowhere yesterday todays chart was empty while the reminder for tomorrow release date was shown properly.
I hope that there will be a fix soon cause during autumn the car will be charged based on these prices during the night if the day ahead expectation for surplus solar power are low. And that is based on these dynamic tibber prices. Still a shame that tibber is not able to get their solution working again when the depreciation of the mathplot libary killed it 6 months ago or even longer when I became a customer and the prices disappeared. Thanks for sharing the progress. |
|
I have checked the link provided and I fear that they are not really happy about our HA traffic and that they might have removed this access cause it seems to be customer only solution for traders which we are not (in most cases I bet).
For all those who are using EVCC for surplus charging the EV there "integration" of the tibber prices seems to work cause they are showing the tibber prices based on the tibber token I had provided.
|
|
just a thought. Does one of you DE-LU users have the configuration 'adjustable' (in configuration.yam) and some minutes ? If I would do I would try changing DE-LU with GER, reload an test again. The reason I would try this is that first of all many germans commenting here (not only but....), secondly in my logs I see a key error (DE-LU) -> can be all and nothing and I did see on https://data.nordpoolgroup.com/auction/day-ahead/prices that germany is labeled 'GER' and the others seem to match the configuration parameter. Maybe that could be an easy try on error. Just a thought |
|
but the entry point , that url has gone - at least that api/10 is no longer available an shows an 404 error. But I will give it a try in my sensors yaml file. There is a nordpool sensor but the prices are way off I guess. today: 33.623, 32.93, 33.202, 32.571, 32.097, 33.372, 37.034, 47.406, 46.12, 36.45, 33.846, 32.426, 31.756, 30.772, 31.379, 32.471, 33.301, 37.935, 40.292, 34.513, 31.432, 30.026, 29.001, 26.239
|
|
and now back in DE-LU same old picture as before with missing sensors aka unavailable. Conclusion: Api is working somehow and delivering something for GER, but that does not match my tibber app prices.
|
|
Is there an alternative source for tibber prices ? And I guess we all shoud do that to put pressure on tibber to deliver now and not some times in the unknown future. |
|
I updated the integration in HACS. After reloading it works perfectly. |
What do you mean with reloading ? But I got an error during reboot in my notifications 2024-10-15 17:04:30.930 DEBUG (MainThread) [custom_components.nordpool.sensor] Dumping config mappingproxy({'region': 'DE-LU', 'currency': 'EUR', 'VAT': True, 'precision': 3, 'low_price_cutoff': 1.0, 'price_in_cents': True, 'price_type': 'kWh', 'additional_costs': '{{ (0.202 + (current_price * 0.19)) | float }}'}) |
|
The region settings have been changed, I had to change my 3 sensors region settings in core.config.entries from Tr.Heim to NO3 in norway to get it working again. After restart 3 new sensors came up and online again. It also seems to be working if you delete old nordpool sensors and add new one. |
Not sure if I wanna delete the sensors, but I have just upgraded to HA 2024.10.2 or so which means I have a new backup and will try to change that entities line to GER - as a german customer. So I did it and it seemed to work , graph is back, but with a complete different and unusual patter: highest price in the morning That can not be true and is wrong! Here is the real price from tibber which I got from evcc which matches the TIBBER App prices Here the price comparison for the cheapest time and here for tomorrow evening the most expensive price at 7 pm There must be something wrong at least when using this GER parameter. |
|
Chiming in - had the same issue with 0.0.14, update to 0.0.15 has fixed it. Latvia region, did not have to update configuration. |
I had updated too today but after 2 reboots nothing had changed, the sensor was still unavailable. |
|
@typxxi thanks for checking. I think it's two problems. The first being that obviously an update to newest version is necessary but also for some regions including germany there is some additional change. I am back home now and will play around with it to see if I get it working and valid prices. But just one little info. today the price was higher in the morning. The graph pattern is ok. The offset seems a bit high (highest tibber price for me this morning was 39.6 ct |
no, the offset is changing from 1 to 2.5 cents from 20 to 30 cents. Not sure what is going on. I also got 2 sensors this time - before I had just one. sensor.nordpool_kwh_ger_eur_3_10_023 is available with the DE-LU in the yaml file and also when I am using the GER sensor.nordpool_kwh_ger_eur_3_095_023 is only available for the GER location, otherwise it becomes unavailable. |
|
I now changed my config (in fact re-installed the integration and configured GER instead of DE-LU) and sesor same as for you @typxxi works n´again. I would assume that I was right with my guess that they changed the region 'code' for germany. I also compared my charts with the actual tibber prices and the graph pattern is 100% right for me (comparing to tibber, again). Only 'problem' that the prices do not match (as you said). I already had differences before, never got it to match 100% but now it seems that the difference between the nordpool prices and tibber is bigger, between 2,3 and 1,8 ct for tomorrow depending on the price being high or low (with same setting for 'additional cost). I will again play around a bit with additional cost and see if it still is applied (or if maybe there is a problem, because I lookedup DE-LU and that value is also in some js code). If I get the values to halfway match I am ok. I think those code changes (and docs) will have to be implemented and updated one day |
|
Meanwhile I reinstalled the tibber custom integration and also copied the token again. It works and the prices are spot on, but now I have to get those prices here into the chart again, which I had been using for quite a while and all are familiar too. On the top of the screenshot in the middle you can see the current price of 27.08 cent price is the same in the tibber app for the third last hour of the day (makes it easier to find that in the long list of figures).
Any ideas or suggestions to get that tibber sensor data to power the chart ? |
|
[edit]looks like the keys have changed. Using NO1 instead of OSLO works[/edit] |
|
So I have moved back to the tibber implementation using this integration and then this rest sensor and apex chart and improved it a bit ATTENTION: the following code has not been cleaned, therefore these explanations It is designed to be used for the prices of tomorrow and the chart is hidden, if it is before 1 pm release time of the prices for tomorrow. The hiding is realised by an input helper. An automation will set the input helper = 1 at 1 pm, at midnight another automation will reset it to 0 again. If it is before 1 pm then there is a message to be patient till 1 pm till the new prices will be released. Those protected spaces around "now" are used to make the marker bigger and more visible but DO NOT work for this code as that is for tomorrow only and NOW will never match with tomorrow, but I keep the code the same in both graphs. |
|
Guys, it's literally in the changelog, under breaking changes. There's a new API integration (#413), and you need to use NO1 instead of Oslo. Just make a new integration entry and update the sensor name wherever you need to. |
|
Or update in configuration.yaml if using that option. |
OK, as mentioned above by @henrikhermansen there was that mayor api change and looks like GER should be the new normal, untfortunatelly the prices are not matching at all. Have you found a solution cause my "tibber adaption calculation" to get my zip code based price has not changed. Here is a comparison from August from my sensor yaml cause I check it regualary every 6 months. So I went back to the tibber integration to get the chart back alive with proper figures and that worked out for me. But only partially cause I had forgotten about my plan for end of october to start using the AIO energy management for AC Charging during night or to LOWER the consumption during the cheapest AC prices in the night or to turn of the hybrid inverter production during the cheapest hour to make the battery last longer in the morning to cut out those expensive early morning hours for 40 cents. If I can use grid power for 20 Cent at 1 am for 2 hours I can save 40 cents during peak hours without the round trip losses of 15 - 20% I have from charging. Charging would mean to pay 20Cent plus 4 cent losses = 24 Cent to save 16 Cent instead of using cheap grid power for 20 Cent and use that kWh saved (for 20 Cent) in the morning when price is 40 Cent. I need to get the nordpool solution running again as accurate as before or at least have to find the cheapest hours during the night to save energy in my battery for the morning hours. I wanna use this solution based on nordpool and quite well described there which also has gotten a brother based on the entso integration modell as well. 0.2.2 is the most recent AIO verision on github so keep that in mind when readin the following. Nordpool AIO - best to start with cause here you can find the whole story Entso E - which is the description how to get the extra steps done to get from Nordpool to Entso only, so start above. So I hope that you find a fix to get proper prices again. Thanks a lot. |
There is nothing to fix. The prices are as is from the API. |
But those are unuseable for my area in germany cause 47 cents versus 39 cents in the tibber app is a bit too much. And I wanna continue to use the AIO energy management based on nordpool integration so I need proper prices and not a guess work. Finally the gap was changing during the day a lot from 1 to 7 cent between nordpool api results and tibber app prices incl. all the fees - of cause in both systems the same. Therefore I hope that someone will find the cause for the current deviation which is right now tibber value for now nordpool value So the source must have changed its pricing level cause it had been 7 cent yesterday morning (40 cent versus 47 cent) |
|
@typxxi could you please verify that the prices you are seeing via the custom component match with https://data.nordpoolgroup.com/ ? Maybe some other region more closely aligns with what you are seeing in your app? |
|
Yeah, and please remove any additional costs so you compare apples to apples. Remember that the prices you see on their webpage is in Mwh |
Here is the solution for german tibber users. The VAT for germany in the backend is wrong if you use the dialog and click on VAT. Here is the full story and how I solved it. |
|
Solved for german customers too where the wrong VAT of 23% would hit you if you configure it via the UI and enable VAT. You will need to read that carefully to get rid of the wrong VAT and to find out the proper tibber fees. |
Version of the custom_component
latest: 0.0.14
Homeassistant version
Configuration
platform: nordpool
region: "DE-LU" # Country/region to get the energy prices for.
currency: "EUR"
VAT: True # Add Value Added Taxes (VAT)?
precision: 3 # Energy price rounding precision.
price_in_cents: true # Display price in cents in stead of (for example) Euros.
price_type: kWh # Price displayed for MWh, kWh or Wh
#Percentage of average price to set the low price attribute
#low_price = hour_price < average * low_price_cutoff
low_price_cutoff: 0.95
#Template to specify additional cost to be added to the tariff.
#The template price is in EUR, DKK, NOK or SEK (not in cents).
#For example: "{{ current_price * 0.19 + 0.023 | float}}"
additional_costs: "{{ (0.2027 + (current_price * 0.19)) | float }}"
Describe the bug
entity is no longer provided by the integration
Debug log
The text was updated successfully, but these errors were encountered: