-
Notifications
You must be signed in to change notification settings - Fork 6
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
Prognosed gas not corresponding to mindergas.nl #18
Comments
@bakboord4 If I remember correct, it is based on a year starting from the date you have entered in the integration (the billing year. I'm surprised that you get 60% of what mindergas.nl finds, it should be more or less the same (if you use the same settings in both mindergas.nl and this integration. So, I also checked it, I have 902 m3 on mindergas.nl and about 800 m3 prognosed in the integration. Strange. I'm going to look into this. |
@Ernst79 your remark: 'I'm surprised that you get 60% of what mindergas.nl finds, it should be more or less the same (if you use the same settings in both mindergas.nl and this integration." |
My configuration. |
First checks.
hmm, first have to investigate why they differ..... The "meterstanden" are equal <style> </style>
|
Do you have the same settings on mindergas.nl? |
Het verschil in gasverbruik lijkt een bug in DSMRreader te zijn dsmrreader/dsmr-reader#1828 |
@Ernst79 Thanks for settings remark. They have the same settings now. |
it is based on the billing year. the prognose is calculated here, where the past weighted degree days are calculated on the actual KNMI data, and the future days (till the end of the billing year) are calculated on the average of the past 20 years (or at least, it should do that).
|
@Ernst79 My lesson learned is to be sure that the Billing-YTD-gas-consumption in my test HA is recorded (entry in recorder.yaml). I am using a test HA remote connected to production HA giving the needed sensors. Values. This integration is running now for one hour or so. Due to the fact that the first two values are practically the same, I will wait until tomorrow to see what the results are of a possible night cycle and a bit more gas-consumption than zero in first hour of its operation. Expect (hope) to see that gas-prognose has narrowed the gap of 22 m3. W'll see. |
Unfortunately I am not systems developer wring code. Some of the code give me an idea, most of it not. But the code is easy to read and is documented. |
has it been solved now? |
@Ernst79 No. |
Both instances of HA are up and running again.
Finding explanation for the difference was not possible. I read code but really understand the calculation was not possible for me.
|
I think the difference between the gas prognose values between DD (1056) and MG (1072) is very small. There are multiple ways to calculate the prognose so differences are inevitable. The most important factor for the calculation is the amount of historical data where the estimation is based on. DD uses for instance the data per day for the past 20 years. Changing the number of years can have a large effect on the prognose. Note that the prognose becomes more accurate the closer you get to the end date. |
Copied from #17 by @bakboord4
Noticed that the prognosed gas consumption shows about 60% what the dutch mindergas.nl website is prognosing.
I have to find out how your integration is working.
It would be helpful to me what is meant with 'year'. May I suggest to make in the documentation and in the sensor names everywhere explicit: calendar year (starting 1 jan) or billing year (date of year-gas-consumption is measured).
Especialy for prognosed gas consumption. Is this for the whole billing year or to 'year to date' (today)?
Thanks in advance for your reaction.
The text was updated successfully, but these errors were encountered: