With this flow it doesn’t work over the 00.00 clock. Is there any workaround for that?
First it trigger 3 times before 12 and then 3 times after 12… The variable laddtime is set to 3.
First it trigger 3 times before 12 and then 3 times after 12… The variable laddtime is set to 3.
1 Like
Is there a bug with “High prices X hours of the day”? It was appearing buggy to me, so I made two triggers:
If it makes sense that these two triggers should do the same, then there’s something weird going on. I am using prices from the Strøm app. Today, the “22 low hours” have turned off heating during these two hours: 8-9 and 17-18 (Oslo area). I’ve verified the pricing, and these were the two highest hours of the day. However, the “high prices 2 hours” card has instead wanted to turn them off like this:
9-10, 11-12. Looking back over the history, it’s actually been locked at 9-10, 11-12 as the high prices of the day. At least as far back as November 10th has been the same times of day from that flow card.
Thanks for the app! It’s been really helpful for quite some time!
However, I’ve noticed recently that the heating Controller sometimes does not trigger ECO mode when it should - and remains in Day mode even after the period is set to end. Example in the pics below: This was a Sunday and the advanced settings for the bedroom is set to use comfort mode only between 9 and 10 in the morning - but it’s still on after 11…
I’m running 6 different Heating controllers for different rooms in case that’s an issue. After noticing the issue, I restarted the app from the Apps page - but that didn’t make a difference.
Yes, I will have a look at it
No, it’s supposed to be like that. Read about the “High prices X hours of the day” trigger on the top of this page.
Are you using the lastest version, v. 1.11.0. ?
Yes. v. 1.11.0.
Thanks! Constructively; might I suggest adding something to the title card, or at least the descriptive text to differentiate the two? 
I was sure from checking them both that they did the exact same thing, inverted.
Today, the price logged by heating controller in NO2 at 06 was 3.63 NOK and at 07 it was 5.32 NOK. Still the following card did not trigger; “Current price is 25% below the average of the next 1 hour”
Is there something I am missing here or is this a bug?
I have another flow with the same card using 30% and 3 hours that also should have triggered today, but did not. So something seems to be wrong with this card now - it has been working previously. I have sent you a diagnostic report; 62de445c-af90-41ad-9560-9eff07f980a7
I think I figured this out… When “End hour working day” and “hour finished at work” is the same - then the controller sometimes shows “night” even if it should show “day”. That messes it all up. Changing “End hour working day” from 17 to 17,1 resolves the issue - but it will off course lead to the unnecessary turning on of heat for some 6 minutes in the evening. Not a lot of power - but “messy”. It would be great if the controller app could handle the scenario when these settings are the same…
Edit:
The controller jumped down to eco again at 12:00 and shows “night” even if it’s a Friday. Could the working/non working day be off??
This is the only one of my 6 controllers to show this behavior. I event tried to remove it and set up a new controller with a slightly different name to “reset” it.
Yep!
If I change end of non-working day to 17, then it pops back to “Day”. The only problem is that today is Friday which is a working day - there’s no holiday in Norway today - and the other controllers consider today a working day……!
(I also tried to remove one other controller, bringing the total down to 5 - but the bedroom controller is still off!)
EDIT: Submitted a diagnostic report:
6a13e0b8-4cdd-458c-8d44-d616e8a40c6e
Hi!
I havent found a way to solve the below request with existing functionality, so see this as a feature request.
The need that I have is a trigger/condition that feeds a local variable that calculates how many hours are above average price per day?
That way I can use that value to calculate & set how much remaining W effect the battery storage system should use if I want to run it in price shaving mode.
Basically I could then run the following rules
- Each hour calculate max discharge for price shaving, by setting variable X to (remaining SoC*total Effect)/HoursAboveAverage
- if the price changes, and its above average set a discharge according to variable X otherwise set it to something lower.
With such rules I can ensure that I get max remaining effect out of the battery for the day during each of the hours when the price is above average and hence max price shaving. Ofcourse I adjust the total effect so that the batteries isn’t run down to 0%.
Best regards,
Kaj Lehtinen
Does the “at work” setting also work on weekends?
Obviously not, now, is there a way to programmatically override weekends and holidays and have an „at work“ setting for 7 days a week?
I have some problems to set holiday and work days.
I get an error message that “args is not defined”.
The two flows abow (Set away and Activate) is just for troubleshooting, In my first test i route it directly to Not a holiday and holiday.
What I want is to set Saturdays as workingdays.
/F
I second that, and actually one should be able to set any day as a working or non-working day. I just fear it makes things more complex …
Yes, you can by using the ‘Holiday today’ / ‘Not a holiday today’ action.
Here is version 1.11.1 with a fix for the “args is not defined” bug:
