Filter the KNX Motion detection?

[brononius]

Hey,

I've got several motion detector around my house to activate some outside lights. But for the moment, they're triggered a lot by moving trees/plants... Fe i've got 35 times last night that a light went on (and off). Luckily i'm using all 'leds', but nevertheless. I would like to limit this a bit on an intelligent way (=by linuxmce i would like to say?).

I was thinking for example to use an kind of event that needs 2x times a input trigger before it activate the light. But can't find the proper formula for this.

Any tips or examples for it?

[Marie.O]

Parameterize your KNX motion detectors to be less sensitive.

[brononius]

I've tried that, but or i'm doing something wrong, or it doesn't do a lot. Tried min and max level, but it keeps on triggering to much.... In fact, I didn't see any difference. Btw I hate that ETS stuff to get something done with KNX.

So I was thinking of finding a solution with LinuxMCE. Much easier with the events and so.

[Marie.O]

One thing that might work is the eggtimer device. It is currently not distributed, but has been working fine for quite a bit.

Let me know what version of LinuxMCE you are running, and I can give you a binary for it. Put that into /usr/pluto/bin - create an eggtimer device under the CORE.

Check http://forum.linuxmce.org/index.php?topic=12493.0 for details.

[brononius]

I'm using 14.04.

Not sure if the egg-timer can help me in this case, but i'm willing to give it a try.

But the eggtimer is certainly interesting since I've got the same issue that when movement is detect, the light goes out after a certain time, even when another motion has been detected. So it would be nice to extend each time the 'ON-time' when movement is detected.

[Marie.O]

I've created a small wiki page for it.

I've created a 1404 binary for you at http://deb.linuxmce.org/possy/eggtimer.1404 - download and save as eggtimer in /usr/pluto/bin

The eggtimer might be usable with a bit of trickery and a setup KNX device that does not point to a real KNX device. My idea would be:

* setup a KNX light device (virtLight)
* upon motion detect check if the virtLight is on - if not, create an eggtimer to turn it on for 10seconds
* if virtLight is on and another motion trigger event happens, turn on the real light.

No idea, if this works, but I would go that way.

[brononius]

The eggtimer works great!
For the moment, I'm using it as 'eggtimer', just to get familar with it.

So in the upcoming days, I'll try your idea. But indeed, it sounds logical like that, so fingers crossed...



ps can we run multiple eggtimers at the same time without any problem? Fe I would like to turn on light in front of my house for 5 minutes, in the back for 3 minutes...

[Marie.O]

The eggtimer works great!

Thanks - feedback is always appreciated.

can we run multiple eggtimers at the same time without any problem? Fe I would like to turn on light in front of my house for 5 minutes, in the back for 3 minutes...

You can have as many as you like in parallel. On Cyprus they always have at least 3-4 runnin in parallel (for each workspace motion detector)

[brononius]

setup a KNX light device (virtLight)

I was trying out your idea.

But can't figure out how to configure a virtual device.
Wen I create fe a light switch (template 47) like I've done for all my lights/outlets, I can't get it to work.
Can a virtual device be anything, or is this a specific template?

[Marie.O]

To me, a virtual device can be anything. I would setup a light device that contains non-existing Group Addresses. That way, the STATE is carried by LinuxMCE, but the KNX network isn't disturbed. At least, that's my assumption

[brononius]

hmm, think I've got another issue then.

It feels like the newly added device isn't responding correctly. When I try to switch on the virtual light manually, it doesn't come in my 99_eib.log file. Only the existing devices appear in there. When I create a new (virtual) device, I'm receiving the status **RUN_CONFIG**. A reload didn't solved this. :$

Damned, damned, damned.

[Marie.O]

Do the virtual devices change state when you turn them on from web admin?

[brononius]

Sadly not.
So I guess I've got another issue...

[Marie.O]

Did you define them to be controlled by the eibd device?

[brononius]

Yes. Was exactly the same as normal light.

But I've just did some extra apt-get update... The apt-get update frooze on the mythtv plugin. He tols me that the user was already part of public. After 10 minutes no movement, I've decided to reboot the machine. Strange thing now that linuxmce itself didn't start? I needed to start it with '/etc/init.d/linuxmce start', and at first sight the server was running again.

When I now start the dummy light, it start.
The only strange part now is that the status is OFF/0 and ON/0?
I would expect OFF/0 and ON/1 like the others.
But I'll start testing it with ON/0...