Somebody home?

[remcoploeg 10]

Hi,

I want to create a LUA script where I can check if somebody is home. I have a lua script when one of the sensor is breached it will set a variable to Yes. But no I want to check the last breachtime of a sensor (if breach > 1 hour ago and we are not sleeping, we are not at home). But how can I check this?

[Dalle1985 16]

Please login or register to see this code.

Replace 86 with your motion detector id. It apparently doesn't work with some versions of the hc firmware, but it works for me. It returns unix system time of last breached which can then be compared to present time

[remcoploeg 10]

Dalle1985,

Thanks!

[ Added: 2014-10-05, 15:49 ]

Is there also a lua function where I can check when a global variable is last changed?

I have several motion sensor and this is maybe not the past way to check if somebody is home(I have to check 10 sensors every time). If I set a global variable when a motion is detected is maybe better? But then I need to check the last time the global variable is changed.

[MalvinYNJ 4]

Create a scene and set the global variable as the trigger condition? Anyone can enlighten me if changes in global variable can be set as a trigger condition?

PS I have just checked, it can be used as a trigger condition. I tested for the case IN and out. If globalvar == IN, do something.

[Dalle1985 16]

There is no way to check when the global was last changed. But you could set the global to the current unix time when motion is detected, so basically, have a scene which triggers on any motion detector breach and then save the current unix timestamp to the global. That way you can always find the last time a motion detector was breached:

Please login or register to see this code.

This should do it for you. Then your scene can just take the timestamp from the global and check it against the current os.time. If it the difference is greater than i.e. 3600 it means no motion for more than one hour.

[remcoploeg 10]

Dalle1985,

Thanks, good solution!

[ Added: 2014-10-09, 22:51 ]

I am not the best(...) programmer. But I have this now:

Please login or register to see this code.

The problem what I seems to have is only one of the if statements runs (the first). Do I need two scenes to achieve my goal?

[MalvinYNJ 4]

Maybe you should use 2 different sets of if else. Change elseif to else if or end if

[Dalle1985 16]

First off, the same global can't be two values so this will never return true:

Please login or register to see this code.

If it is because it should be either, you should use an or statement instead. And then you should put the two in a parenthesis, this way, the lua engine will evaluate it together and return the parenthesis true or false instead.

Try and see if this works:

Please login or register to see this code.

I've also removed the elseif. As you mention, this is never run. This is because your scene is only run when a motion detector is breached. So it will not trigger 3600 seconds after last motion, but only on the next motion event, and then the timer will ofcause reset. Therefore, you need either a separate scene or recode you scene to run in an infinite autostart loop with no triggers. So basically run above code, sleep for 5 seconds and then repeat. This isn't very tidy - some would call it junk code, but it is the only way to work with the lua available.

The second solution would be to run two scenes:

Please login or register to see this code.

Above scene is triggered on motion detection, kills the scene below and then restarts it. This might seem a bit strange, but there is reason behind it. Lets take the second scene first, then I'll explain:

Please login or register to see this code.

So what this does, is that the first scene will set the somebodyhome variable to yes whenever motion is detected, it also kills the second scene and spawns a new instance. The second scene meanwhile, is set to start, wait 3600 seconds and then change the somebodyhome variable to no. Now as the first scene will autokill the second scene whenever motion is detected, the second scene will only ever complete if there has been no motion for 3600 seconds.

Some might call this junk programming... And it probably is, but it works, so I don't think it really matters if purist (those who cann themselves "real") programmers don't like this... Anyway, hope this helps?

[alex88 71]

There is no way to check when the global was last changed. But you could set the global to the current unix time when motion is detected, so basically, have a scene which triggers on any motion detector breach and then save the current unix timestamp to the global. That way you can always find the last time a motion detector was breached:

Please login or register to see this code.

This should do it for you. Then your scene can just take the timestamp from the global and check it against the current os.time. If it the difference is greater than i.e. 3600 it means no motion for more than one hour.

FYI, You can use a global as a trigger to a scene.

Please login or register to see this link.

Look at the example using "A change to the global variable ‘isItDarkOutside’"

If you use Dalle's example above you can trigger your scene each time the global is updated.

[remcoploeg 10]

Thanks guys for the suggestions!

[Dalle1985 16]

Your very welcome... Did you find a solution?

[Brick 13]

Is there also a lua function where I can check when a global variable is last changed?

There is no way to check when the global was last changed.

Well, in fact there is one way...

The function fibaro:getGlobal("GlobalVariableName") actually returns two values. The first one is the value of the global, the second one the time it changed. Watch out: CHANGED. This means that it will not be updated if the global value is overwritten with the same value. It only updates the time if the value is different.

So:

Please login or register to see this code.

will set "v" with the value and "t" with the last change time of global "GlobalVariableName".

You might probably found a different solution through Dalle1985's approach though, but this info should be useful for further scenarios.[/b]