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
Gas meter reading failed to upload to mindergas on 08JAN #228
Comments
I think that it's a timing bug. The gas positions are uploaded right at midnight, but the gasmeter sometimes takes a few minutes to report it's new hourly value to the smart meter. This might be fixed by accident with #204, which is part of a patch release that just happens to be released in the next hour. You could check your own logs to see when the gas meter positions should be uploaded: |
The patch is released. You should:
In the
Please let me know whether this resolves your problem. |
Thanks. I have updated. After setting the next export (to Jan 9 at noon(!)) it did not "update within a few seconds" however. It is still at: Next export: |
I think my DSMR-reader instance is now hammering mindergas.nl every minute...
|
Can you try setting the next_export field a bit forward into the future then? You can stop It seem that MinderGas rejects the reading, but due to a small typo of me the actual error isn't displayed. And the hammering is something that I will fix as well. Can you check your API key you've entered? Also, the info message states: |
Thanks for your quick response. But it seems to still be hammering. I have verified and re-entered the API key and that is correct. Which makes sense as the 09JAN meter reading (99,854) did upload correctly last night. |
Hmmm, can you try to disable the I will make sure that the hammering stops and that a decent error message is displayed later. |
I seem to be unable to stop the upload, because if I remove the checkmark from "upload to mindergas" and SAVE settings the application seems to crash.. Is there a command line option to temporarily disable mindergas uploads? |
Sure, this should do it: |
That worked, thanks. |
It weird that the application crashes on the settings pages though. I will continue to investigate this tomorrow and also create a patch to stop the hammering, as well as displaying the error from MinderGas. Thanks for reporting this though, as it's very nasty bug. |
Aangezien ik er (pas) gisteren achter kwam dat ik tegen dezelfde persoon zowel in NL als EN praatte in verschillende ticket, zal ik hier NL doen voor het gemak. Ik heb een nieuwe patch uitgebracht nu, Wil je kijken of je dit meer inzicht geeft in waarom de upload faalt? |
1.5.3 geeft inderdaad meer inzicht, in eerste instantie faalt de upload door een foute API key (401), ik had namelijk nog een foute API-key staan omdat ik die express naar een random value had verandert om de upload te 'stoppen'. Maar de hammering lijkt er ook nog te zijn.
Na het invullen van de goede API key werkt de upload weer:
|
Ik zie het al, zoals eerder gezegd was ik niet fit, maar ook vooral niet wakker zie ik. Het was de bedoeling dat hij bij falen het een uur vooruit schuift. Dat doet die ook, maar vanaf de meest recent middernacht ipv 'nu': * facepalm * Je kunt het instellen in het DB-veld
|
Ik heb het laatste bugje zojuist opgelost in patch Mocht je nog benoemd willen worden in de 'hall of fame', laat dan even wat achter in #231. En laat het ook vooral weten wanneer de MinderGas upload toch niet meer blijkt te werken. |
Top, het werkt nu en ik zal me weer melden als er toch nog iets fout mocht gaan. |
While the mindergas.nl output has been working for two days, and DSMR reader is still displaying gas usage, the gas meter reading of JAN08 was never uploaded to mindergas.nl.
Is there any logging available to check what might have gone wrong here?
Next export:
Jan. 10, 2017
Timestamp of the next export. Automatically updated by application.
SAVESave and continue editing
Maybe this?
Data processing is on schedule: Jan. 8, 2017
(While GAS STATISTICS
FOR DASHBOARD DISPLAY.
Data processing is on schedule: an hour ago)
The text was updated successfully, but these errors were encountered: