You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! This night we changed DST and I examined the output of the schedule from a Schedule Merger Node I have set up. I compared it with what was sent to the node and what was coming from Tibber. I found that there is a price element missing after the Schedule Merger Node, due to DST change.
Output from Tibber Query node (price array snippet):
Input to Merge node from Fixed Schedule Node:
Input to Merge node from own Hours array:
And output from Schedule Merger Node after merge. If you compare the input/output above you can see that after the Schedule Merger Node the MTU with UTC time 24:00 (midnight) and price 0.4958 is missing:
Here is what I was expecting:
UTC 23:00 -> 2023-10-29T01:00:00.000+02:00 with price 0.523
UTC 24:00 -> 2023-10-29T02:00:00.000+02:00 with price 0.4958
UTC 01:00 -> 2023-10-29T02:00:00.000+01:00 with price 0.4518
Could it be a bug in the Power Saver DST handling?
The text was updated successfully, but these errors were encountered:
Hi! This night we changed DST and I examined the output of the schedule from a Schedule Merger Node I have set up. I compared it with what was sent to the node and what was coming from Tibber. I found that there is a price element missing after the Schedule Merger Node, due to DST change.
Output from Tibber Query node (price array snippet):
Input to Merge node from Fixed Schedule Node:
Input to Merge node from own Hours array:
And output from Schedule Merger Node after merge. If you compare the input/output above you can see that after the Schedule Merger Node the MTU with UTC time 24:00 (midnight) and price 0.4958 is missing:
Here is what I was expecting:
Could it be a bug in the Power Saver DST handling?
The text was updated successfully, but these errors were encountered: