Open rinowit opened 1 year ago
Hi! I can't see any differences between the currenthour-attribute and the list item for the same hour (2023-05-22T11:00:00+02:00) for the raw_today-attribute in your pasted text?
Is that what you meant?
start: '2023-05-22T11:00:00+02:00'
end: '2023-05-22T12:00:00+02:00'
value: 1.063
price_next_hour: 0.967
price_in_2_hours: 0.936
is_gaining: false
is_falling: true
is_max: false
is_min: false
is_low_price: false
is_over_peak: true
is_over_average: true
price_percent_to_average: null
is_ten_cheapest: false
is_five_cheapest: false
is_five_most_expensive: false
is_falling_a_lot_next_hour: false
temperature_correction: -1
reason: Is falling and not low price
In the Five cheapest today on the other hand, we find this:
start: '2023-05-22T11:00:00+00:00'
end: '2023-05-22T12:00:00+00:00'
value: 0.936
Note that this is two hours later (as this timestring does not have a timezone-value), and another value. I think the bug here is that the 'top 5' and 'top 10' values does not add timezone's to the date-string? 2023-05-22T11:00:00+02:00 is rightly not in top 5 or top 10.
Tip: Add code-snippets like this (without the -) to format it nicely in markdown:
-```yaml
code: code
-```
How can I correct the time issue? You are probably right.
Thanks for helping
Well, you can submit a PR, or wait for me to fix it, hehe. It's not technically wrong per se, since 2023-05-22T11:00:00+00:00 is the same date and time as 2023-05-22T11:00:00+02:00. So the current_hour attribute will be correct. The time is just displayed differently, but is the same time, regardless.
This can be visually validated with the apex chart for the component:
I'll keep the issue open, and fix it once i have some time to fix it :-)
Aha:) I understand now:) Thank you so much:)
Hello, I have a updated HA with a updated priceanalyzer 1.4. I have a Issue that priceanalyzer is showing false on today top 5 and top 10 when it should be true. It's showing the right value on the attribute list. But wrong value in "current hour"
I was running priceanalyzer 1.0 for a while and had to downgrade from 1.4 a while ago as the value was broken in the newer HA releases. Now the HA was update in may and the value for 1.0 is also broken.