The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Flags Flags Flags!
Spawnreaper
Member
(please implement!!)
Flag systems are lists of info that homey collects. Other flows can call on this info. The list values change during the day (and during prolonged use.)
Value's Homey can collect:
- if you speak he knows you are near, and therefor home. "Home flag on"
- motion sensors also indicate that you are home."Home flag on"
- schemer sensor tels homey the lights level. Lights can respond accordingly. But it also prevents multiple triggers during sundown. (very annoying)
- contact sensors can inform homey a door is open. In sequence I could calculate if you are leaving the house or getting home.
- agenda appointments can inform homey that you are not home. "Home flag off unless...."
- Weather information.
- temperature
Flags prevent multiple triggerings of the same sensor. I've noticed this on motion sensors and schemer sensors. If a flow is triggered by a flag in stead of a sensor (sensor triggers the flag) it can only turn the flag on a second trigger does not change the flag status. After this the flag can be turned of ether after a certain amount of no activity or some other trigger. Very handy for motion sensors.
informing homey that "there are pets in the house" (pet flag) could automatically turn of the motion sensors.
Flags could also be used to activate or deactivate multiple flows preventing false triggers. For instance: Already turned on the lights manually? flag lights on in the living room, suppress schemer-sensor that notices its getting dark and wants to turn of the lights.
Color and Dim value flags can be used as a reference for the lights. That way homey can set multiple lights to the same preset value for that time of the day with a specific dim level. If this flag change would have a force effect it could change the lights gradually throughout the evening. Maybe even linked to the current weather.
Not having anything like this in homey at the moment is driving me nuts on numerous flows.
Comments
Variables
Edit: Except for the light part, there is no way to change the color of the lights according variables, but this is not a variable thing, It (still) needs to be implemented in the (for example) the hue app
Variables don't work with a list. So its harder to manage in my opinion.
It is given in a nice "list" way like you want it.
The default logic (variables) will get an update pretty soon to be more viable/edible as well.
I just would like an information list that can be looked on to by every flow. A self determined list of variables that is being altered by several logical flows during the day based on time, temperature, mood, weather, proximity, and custom situations.
The "better logic app" to me looks like a normal box like all the others and is just a bit more complex then the basic one.
There is no/ or I don't see any overview of variables that are active or inactive at the time.
It misses clarity that the vlag sheet would provide. I even think that a flag sheet needs to be an entire different element just like flows and devices but influences both.
@emile What's this 'Soon' I keep hearing about?
Are there any video's on how to do it, if its possible?
[IF] variable is changed (better logic one)
[THEN] set variable: tag(value).
The default app is already global thanks to:
{{$variablename}}
For the ThermoSmart the Slider is already discussed
I guess it is already on their list to change it to Cards with values, an other solution is also requested here:
slider is really annoying #5
I guess it is also possible to fork the code on Github for the thermosmart App to create a card with value filed in an updated app.
@Emile ;
I think you'll have to be more specific. You want a global variable called "temperature" then you can create one or two: "temperature inside", "temperature outside" etc etc... "pets in the house" would require a different sensor (perhaps bluetooth?) of RFID and a corresponding flow? You want to set a light level with a variable? That's a specific question (which has been asked before), don't know if there's a github issue for this already?
Smile said there where plans to make something for that.
Because of alle the question marks I will explain the idea again.
Create a separate section.
in the section give an option to set value's. Example: level % name "light level" or code. name "colour" or yes or no. named "home"
Al these levels can be changed by flows. example: At 20:00 set "global variable" "light level" to 40%.
If you can set the lights on "global level" then all light can just look what level (and colour) they need to be set on.
You would probably say: "Well why not just make a flow for every time you want to change the light level and color and manually set all of them to the level you want?" Well, my way is cleaner. and you only need one flow that change the values of lights to the global level. If you want to change something in my setup you only need to change one global level instead of 8 different ones in one or more flows.
Setting a global variable home "yes or no" can be influenced by, motion sensors, voice commands, running media stuff like that.
This yes not value an be used as a variable in flows "only run if global home setting is set to yes.
I am sure there are ways to make something that will function the same way, but personally I think people would find it easier to use like I explained. More user friendly.
The reason I posted today was just to ask Emile if there is progress on the "global variables" since he said they where working on it.