This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
I tried to copy the motion/speech/manual scenario. In my case I haven't implemented voice switching yet, to keep things simple.
The App is working, I can switch manually and that state remains functioning, but motion controlled switching doesn't work. This does work in other flows, but I want to use State Control because it allows me to override via mnaul switching.
Does anyone know what I might have misses? I followed the wiki guide and this is the result:
In the flows that switch the light (with the switch, or as motion) I added a voice card that commented on the action (so; lights on after movement, lights on after manual switch, and the overall action lights on).
The actual switch is a Fibaro FGS-222
- Movement is not reported!
- Manual switching is reported
Light on is reported, and repeated continuously and only stops after a PTP / reboot. Even disabling all flows doesn't halt the voiced output!In the case of the dimmer, I know that scene activation is not working (yet). If you have a flow which triggers on the device going on/off, it will trigger in situations when a) the device is manually used and b) the device has changed its state.
So when you switch the light on manually using a wall switch, the flow is triggered.
When the light has been switched on using another flow, the flow is triggered.
This causes the unwanted behaviour. For the dimmer, we're going to have to wait until scene activation is supported.
From what I can see, the FGS-222 does not support scene activation altogether (although I hope I'm wrong).
I'm going to think of a work-around, and will report back here.
The only thing I want is to get homey in different states, but don't know how
Example:
Homey state -> Here is homey in when someone is home (use smart precense)
Homey away -> Nobody is home
Homey sleep -> When we are sleeping
Homey holiday -> When we are on holiday
Is it possible to set these things. I want to use the normal flows, but checking in the "and" colum in witch state is homey before fireing the flow?
I made the following group "Kerst" with the sections "KerstBoomVerlichting" en "BuitenVerlichting". All X-Mas related.
I defined the following events & triggers:
In the flow I have created a number of actions based on movement, etc:
The action is on the Kerstboom and says Lichts on.
In the panel "Here is where magic is" I cannot select an section anymore. This means that all actions are based on the same events?
which is in my case not true. The XMas tree is based on movement in the house and will switch off after a certain time when there is no movement. The Xmas lights outside will be triggered after sunset and stay on until all lights are switched off. Does this mean that I need to create events specific for each section if they behave differently?
I am not sure if all the overhead reduce a lot of work as you still need to make a huge number of flows. In cases where you have for example a lot of rooms that needs to behave similar this can work I think.
Is my thinking wrong here?
What I like is the structured way that you have more overview where something goes wrong. Currently I have so much flows that I lost track....
Is it possible to conditionally go from WASHING to DONE based on the expiration of a delay? And can I cancel the delay when the energy consumption goes up again?
I really like the idea behind this app.
However, I'm a bit puzzled about how to actually use it rationally - perhaps someone can enlighten me?
As I understand it, I need to make a lot of variables in the app itself.
Then, I have to make an enormous number of flows that connect the different variables to the actions to be carried out in he end.
How is it, that this is easier than creating these variables in "Better Logic" and approximately the same number of flows (or a little more, to change the variables, but still - that would be without the work of making all the variables in "State Control" anyway).
As example, I've made some variables regarding the status of the light in different rooms.
One of the features I then try to implement is a connection to my smoke alarm - if the smoke alarm goes of, all lights turn on. When trying to do this, it seems like I have to make a flow for each room, that reacts on the "Light-alarm" variable and turn on the light?
In that case, it seems a lot easier to make a single flow "alarm goes off" and put each lamp in this.
Am I totally off or?
(Perhaps being non-dutch-speaking makes it somewhat more difficult to figure out the flows - but I think I got it mostly right).
Regards,
Chr.
Examples of "codebooks" are more than wellcome (even in Dutch ;-)) - just to get it going...