Skip to content
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

Wrong prices in the end of JSON #901

Open
mortenm22 opened this issue Jan 16, 2025 · 5 comments
Open

Wrong prices in the end of JSON #901

mortenm22 opened this issue Jan 16, 2025 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@mortenm22
Copy link

Describe the bug
I am getting some strange values ​​on price when I get prices for more than one day. The last two prices are wrong. The last one is way too high and the second to last one is a copy of the price before. Max is also wrong since the last price is too high.
The error only comes when I get prices for two different days.

{"id":"XX:XX:XX:XX:XX:XX","prices":{"0":0.4893,"1":0.4766,"2":0.5327,"3":0.5235,"4":0.6431,"5":0.5231,"6":0.4816,"7":0.4516,"8":0.4362,"9":0.4273,"10":0.4230,"11":0.4233,"12":0.4158,"13":0.4193,"14":0.4179,"15":0.4225,"16":0.4232,"17":0.4323,"18":0.5182,"19":0.6426,"20":0.5334,"21":0.4927,"22":0.4430,"23":0.4381,"24":0.4324,"25":0.4327,"26":0.4337,"27":0.4384,"28":0.4386,"29":0.4322,"30":0.4329,"31":0.4349,"32":0.4342,"33":0.4324,"34":0.4308,"35":0.4308,"36":5.3161,"37":null,"min":0.4158,"max":5.3161,"cheapest1hr":"2025-01-17T00:00:00Z","cheapest3hr":"2025-01-17T00:00:00Z","cheapest6hr":"2025-01-16T22:00:00Z"}}

Hardware information:

  • Country: [Norway]
  • Meter: [Kamstrup]
  • Encryption enabled [no]
  • AMS reader: [Pow-K+, esp32s2]

Relevant firmware information:

  • Version: [2.4.0]
  • MQTT: [yes]
  • MQTT payload type: [JSON (classic)]
  • ENTSO-E API enabled: [yes]
@gskjold gskjold self-assigned this Jan 22, 2025
@gskjold gskjold added the bug Something isn't working label Jan 22, 2025
@gskjold gskjold added this to the v2.4.1 milestone Jan 22, 2025
@gskjold
Copy link
Member

gskjold commented Jan 23, 2025

I have found the issue and fixed it:
esp32s3.zip
esp32solo.zip
esp32.zip
esp32c3.zip
esp32s2.zip

@mortenm22
Copy link
Author

Thanks for the quick response. It is still an hourly rate too much. It looks like it's a copy of the 11pm rate.

MQTT at 4pm:
{"id":"xx:xx:xx:xx:xx:xx","prices":{"0":0.9281,"1":0.9705,"2":0.8357,"3":0.6871,"4":0.5332,"5":0.4819,"6":0.4431,"7":0.4352,"8":0.4313,"9":0.4286,"10":0.4253,"11":0.4237,"12":0.4174,"13":0.4256,"14":0.4451,"15":0.8067,"16":0.9173,"17":0.6805,"18":0.5365,"19":0.4639,"20":0.4371,"21":0.4324,"22":0.4337,"23":0.4261,"24":0.4151,"25":0.4202,"26":0.4092,"27":0.3783,"28":0.3669,"29":0.3619,"30":0.3619,"31":0.3606,"32":0.3606,"33":null,"34":null,"35":null,"36":null,"37":null,"min":0.3606,"max":0.9705,"cheapest1hr":"2025-01-24T22:00:00Z","cheapest3hr":"2025-01-24T21:00:00Z","cheapest6hr":"2025-01-24T18:00:00Z"}}

@mortenm22
Copy link
Author

MQTT is correct after midnight.

{"id":"xx:xx:xx:xx:xx:xx","prices":{"0":0.4286,"1":0.4253,"2":0.4237,"3":0.4174,"4":0.4256,"5":0.4451,"6":0.8067,"7":0.9173,"8":0.6805,"9":0.5365,"10":0.4639,"11":0.4371,"12":0.4324,"13":0.4337,"14":0.4261,"15":0.4151,"16":0.4202,"17":0.4092,"18":0.3783,"19":0.3669,"20":0.3619,"21":0.3619,"22":0.3606,"23":null,"24":null,"25":null,"26":null,"27":null,"28":null,"29":null,"30":null,"31":null,"32":null,"33":null,"34":null,"35":null,"36":null,"37":null,"min":0.3606,"max":0.9173,"cheapest1hr":"2025-01-24T22:00:00Z","cheapest3hr":"2025-01-24T20:00:00Z","cheapest6hr":"2025-01-24T17:00:00Z"}}

@ArnieO
Copy link
Contributor

ArnieO commented Jan 25, 2025

So the thread can be closed?

@mortenm22
Copy link
Author

It's still one price too many when I receive more than 24 prices

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants