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
Added my Smart Sensor 6 back in zwave again yesterday.
All looks ok but i have the Always Motion Alarm.
I tried setting is to basic save and then binary cc save and wake up the ms6
No change, is there already a solution for the Always motion ?
In Insights all parameters are shown, except motion. I will give it some days to see if this solves itself :-)
[motion alarm and insights]
See below the output from today and also my sensor settings:
Should I set the "Motion alarm will be cancelled in the main controller and the associated devices after the period of time set in this parameter" from 240 to e.g. 3 or 4 ?
Thanks! Will try...
So far I can't think of a way to implement this in my flow.... The only thing I can use is if the motion sensor is on or off but not during/since a certain time period.
Do you, or anyone else, have an idea?
PS I don't want to use 'presence detection' since this is way too unreliable for me.
@Jon I will have a look if I have a flow , still in use, when I get home tomorrow.
Flow 1
If motion is detected start countdown {name} timer for 5 minutes
Flow 2
If Lux has changed set {LUX 1} variable.
Flow 3
If Variable {LUX1} has changed and {LUX 1} < ..5..? and Countdown {name} timer is still running. Turn on lights
hope this helps.
Me guess u want lights on as long there is motion aye?
Make a BL variable, boolean, "lights-on".
Make a countdowntimer "lights-on".
Flow 1: When motion is detected-----And lux<25-----Set boolean "Lights-on" to true.
Flow 2: When a variable changed-----And boolean "Lights-on" is true-----Stop countdowntimer "lights-on", put lights on.
Flow 3: When motion stops-----Nothing here-----Set Boolean "Lights-on" to false.
Flow 4: When a variable changed-----And boolean "Lights-on" is false-----Turn countdowntimer "Lights-on", 300 sec.
Flow 5: When countdowntimer is empty-----Nothing here-----Turn lights off.
Bit complex with 5 flows but it works like a charm here.
thnx
@thijsdejong called it {LUX1}
Then the first flow will be:
Flow 1: When motion is detected-----And lux1<25-----Set the boolean variable "Lights-on" to true.
I Thought that was the deal, but i had to ask to be sure.
I was thinking about a solution with less flows, but kept hitting issue's Like"what if..."and so on.
Your solution tackled all those what iff's.
THNX for sharing and I think this is a great flow example to post in "Flow that works"
I have succesfuly used these examples for my kitchen lights; works great.
What a bummer I have to manually re-create all these flows for my other 4 room sensors...and can't simply copy them.
Other question; What if I want to switch a light ON if lux is below a certain value, and light 2 if the lux value is between to values...? So, the state can be OFF/Light1/light2.
Thanks