If the temperature outside passed the temperature inside
while outside is bigger than inside
then action
If the temperature outside passed the temperature inside
while outside is smaller than inside
then action
Right now I can make a flow using KNMI app
But then I have to use when temperature changes
This means that the action will start again and again at every change of .1 or 1. degrees
But I only want an action at the moment at the moment outside becomes bigger or outside becomes smaller. While temp is passed the setpoint, the action should simply stop.
Do anybody have an idea how to put this proper in a flow?
But does this mean, the heater is started 1 time? Or will the heater receive a start command every time the outside temperature change and is < inside?
I think it is the last, and that is exactly not what I want.
The heater is started once.
As the first time te outside temp gets below the heater is switched on. The next time the outside temp changes, the heater is already on and won’t be switched on again.
Right, I did missed it indeed. But now that is clear to me!
Your flow look like my idea. But I want to use the outside temperature from for example KNMI, because there is no outside sensor yet. While using KNMI there is no basic option becomes less than.
I think the most easy solution is place soon an outside temp sensor…
But I am still open for any logic solution with using KNMI or an other accurate outside value.
True, i don’t know why, but not all apps provide for triggers with “becomes less/more than”.
In that case you’d use the first @Rmb example.
The KNMI temperature tag is always available, for use in a logic condition.
Right, but temperature valuve change at every input change. So it is not possible to compare old temperature (before the change) with the new temperature.
IMO this result in a number of action with every change of temperature.
What I mean and like to create is
Outside temp = 23
Inside temp = 24
Outside temp increase to 24 → close all doors and windows
Outside temp increase to 25 no action
Outside temp increase to 26 no action
and so on…
outside temp decrease to 23 → open all doors and windows
outside temp decrease to 22 no action
outside temp decrease to 21 no action
and so on
I do asked KNMI to add 2 charts, this will make life much easier
YW!
I agree some cards which make more sense are missing, but Homey seems not to be bothered driving flows with “when temperature changed” trigger cards.
Some think it can have a negative impact on overall performance.
I believe it doesn’t, (why would those cards be available?) but I did no lab tests.
So, you might not want a flow to be triggered at every temperature change by 0.1, but I don’t bother about that all. It’s just how Homey works.
Because temperature changes are being received lets say every 10 seconds, should be handled anyway for displaying and storing in Insights. So adding a few instructions to compare it with a value and doing nothing most of the time might not be a big problem.
If an app is using a numeric capability (Standard or custom), Homey autogenerates the get higher/lower trigger. For subcapabilities this is not done. So it’s possible, that apps are using subcapabilities in this case.
I think you worry too much about unnecessary things. Have you ever checked in Insights how often a temperature change is reported by the KNMI app, which is a cloud service?
This is a screenshot of the current temperature, which I get via @RonnyW’s OpenWeather app:
This means that the temperature has only been reported 9 times in the last 60 minutes. And if the temperature doesn’t change (see marked area), no data will be transmitted at all. That’s right @RonnyW, isn’t it?
Of course, such trigger cards “X becomes more than Y” and “X becomes less than Y” makes definitely sense and, in my opinion, should be used whenever possible. But it’s not always possible, for whatever reason.
Just a little extra info. These trigger flow cards “X becomes more than Y” and “X becomes less than Y” exist not so that long ago, maybe for about 2-3 years.
Before that, you always had to use these “X has changed” trigger flow cards followed by a logic flow card, and that didn’t cause any problems that I know of, even with the old Homey models from 2016.
I thnk I do find a solution with the app Weather Forecoast. No unneeded messages, just usefull in summertime to open or close the house to keep it inside as cool and comfortable as possible
Right, the “capability changed” flow trigger are only started if the capability value changes.
If an app request data every 5min, the trigger will start every 5min (if the value changes) or with one of the next intervals.
If the temperature is stable, no trigger is started.
