wrong EPEX prices for AT

[cmock]

Describe the bug
Today, the EPEX prices shown by AMS reader are wrong for Austria. Notice how the prices from EPEX are negative, but AMS reader shows positive prices.

To Reproduce

Expected behavior

Hardware information:

• Country: Austria
• Meter: Sagemcom T210-D
• Encryption enabled: yes
• AMS reader: ESP32
• M-bus adapter (if applicable): resistive divider

Relevant firmware information:

• Version: 2.4.7
• MQTT: yes
• MQTT payload type: Home Assistant
• HAN GPIO: GPIO16
• HAN baud and parity: 2400 8E1
• Temperature sensors: n/a
• ENTSO-E API enabled: yes

Additional context
I'm not sure how often the prices are wrong, I just noticed it because the negative prices were not shown today.

[ArnieO]

Interesting!
We fetch the prices from Entso-E, and their website confirms your curve for today:

This looks like a bug, potentially coming from the fact that Austria publishes both 15-minute and hourly prices.
Thank you for noticing, we'll certainly look into it ASAP!

[ArnieO]

@cmock : Please confirm whether you read prices directly from Entso-E or from our intermediate server.
Your config should look like this (no Entso-E API key):

We strongly recommend using our intermediate server, and will probably soon remove the option to read directly from Entso-E (using API key). The reason is that the transition to 15 minute pricing during 2025 is causing issues, as the transition is not synchronized in Europe, and we are not able to keep the device firmware up-to-date. Instead, we deal with it on our intermediate server.

[cmock]

Yes, I fetch from your server, the API key field is empty.
The 15min/1hr issue was already discussed in #963.
Thanks for looking into it!

[gskjold]

It looks like the server chose the 15min interval after all in this case... I will look into this

[gskjold]

After a quick debug on a local test instance, it does choose the 60min interval for AT from that date.. I'm left to wonder if the entso-e server only served a 15min interval at the time and that the 60min arrived later. I will start saving the raw response from entsoe in case this happens again