search

hombach / ioBroker.tibberlink

links tibber API data to be used in ioBroker
https://github.com/hombach/ioBroker.tibberlink
GNU General Public License v3.0
25 stars 5 forks source link

Calculator channels do no longer work in Version 1.5.0 #212

Closed mtbsteve closed 1 year ago

mtbsteve commented 1 year ago

I have defined the following channels: snip1 The triggers for the channels are set as follws:

snip3

Result is, that the Best Hours Block channel apparently never gets activated, but the Worst Hours Block went true for 4 hours between 20:00 and 24:00 yesterday, despite of the Amount Hours setting of "22", and the tibber price being actually low. snip2

For reference, this was the corresponding tibber price at that time. snip4

My expected behavior would have been: Best Hours Block true between 0:00 and 4am yesterday, and 1:00-4:00am today, Worst hours block being true 8:00-10:00am yesterday and 17:00-19:00pm today.

The calculation channels were working ok for the previous 1.4x version.

hombach commented 1 year ago

Could you please try the same with 1.6.0 directly installed from GIT? I think I found the error "by accident", 3h ago... ;) 1.6.0 is finished - if my test will be ok. -> you could try "Best Cost LTF" - this has been validated

hombach commented 1 year ago

You are rigth - I didn't notice this error in 1.5.0 .... and none of the 120 users who tested 1.5.0, too... ;) image

hombach commented 1 year ago

Fixed in 1.6.0

hombach commented 1 year ago

1.6.0 released to "latest" repository

mtbsteve commented 1 year ago

@hombach thanks! So the Best hours Block settings work now. However I am still struggling with the "Worst hours block" set like this whixch is still not working as expected. snip3

The Tibber price level today is: snip5

My expectation would have been that the Worst Hours Block woukd have been triggered from 18:00-20:00 today. I have the 1.6.0 version installed from Github, and all settings were re-initialized after the installation. Any ideas?

hombach commented 1 year ago

you have to use best single hours to get the result you wanna have. Best hours block always generates one block with the "YES" value - e.g. "False" in this inverse case. best single hours will find all hours before and after the peak in your graph. If a real worst block is needed, e.g. one "solid" 10 hours block in your example data, we would need a new channel type.

mtbsteve commented 1 year ago

Thanks works now :-)