Suggestion for Motion detection

[murcel]

hi,

I've played around some days with a trickle star, aeron labs usb controller, a düwi light switch and an EZmotion sensor.

the initial idea was, as soon as a motion is happening the lights should go on. i am thinking of lightning in a e.g. corridor at night.
1. The sensor is tripped
2. The light should stay on a few seconds, to a minute and went down again after that time.
3. if two minutes later again the sensor is tripped, the light should go on again.

I believe that is not a big part - but i am not able of managing it. item 1-2 is working, with a response to event item. Switching the light switch on giving dcerouter an idle timeout and then switching light out again.
Unfortunately the motion detector does not "rearm". Means the second "tripped" is not fired at all.

so i read in the wiki, that one can reconfigure the ezmotion, to shorten the motion time from 20 minutes to 1 minute. So i did that. don't know if the command got to the device, but the behavior is the same than above.

So question: is my scenario in general workable with the devices above? If not, can someone suggest a device (motion) which can fulfill those requirement?

murcel

[Marie.O]

* posde is happy with regular KNX PIRs, which all have a function to turn on a specific device for a few minutes.

[Marie.O]

Apart from the above, turn on the light in the tripped event, and add a sleep 600 for a one minute period of keeping the light turned on, followed by a turn off.

[Techstyle]

I had this working with X10 also. You have all the correct hardware to do it.

I believe the way I had it set up was as Posde explained but I made sure the length of delay on the device was shorter than the amount of time the light stayed on for (Posde's delay 600).  This way the sensor would reset to untripped and trip again before the light goes out and the delay clock is reset.

If your functionality is working correctly, you should see in webadmin the sensor trip and untrip and see the light go on and off on the orbiter

[murcel]

Thanks for your input pos and techstyle.

i set it already up with a sleep timer.
That is all working well, light goes on, it sleeps for a certain amount and after that goes down again.

But the EZMotion is holding its Motion for about 20 Minutes.

Means....if - after my sleeptimeout another motion is happening within 20 Minutes - the ezmotion is not fireing again.
There is a wiki about it, to lower this ezmotion timeout to 1 minute (which would be sufficient) but that seems not to work in my case.

Anybody has experience with that?

[sambuca]

When setting configuration parameters on the EZMotion you need to press the blue button to wake the device up for it to receive the command.

br,
sambuca

[murcel]

When setting configuration parameters on the EZMotion you need to press the blue button to wake the device up for it to receive the command.

br,
sambuca

Sambuca,

just to make sure, i followed this wiki:

Select the ZWave device in the advanced web config devices section.
Select send command to device.
Select "Set Config Param" as the command to send.
48 Value (int) = Your desired timeout in minutes
239 NodeID (int) = The ZWave node ID of the HSM 100 to configure
248 Parameter ID (int) = 2
Press the blue button on the side of the HSM 100 you are trying to configure
Click "Send Message"

after that it should work right?

[sambuca]

Yes, I think so. You could also try to send the command then press the button afterwards. The command should(!) be added to a queue for sleeping devices and sent when they wake up (the blue button wakes it up).

br,
sambuca

[murcel]

When i follow the advice in the wiki http://wiki.linuxmce.org/index.php/Express_Controls_EZmotion_(HSM_100)
for setting the wakeup time to 6 minutes then in the log i see:


36      05/19/12 0:37:26.702            Nodeid: 2 Value: 360 <0x41000b70>
36      05/19/12 0:37:26.702            Adding job to sleeping queue: 0x9bcb708 <0x41000b70>
36      05/19/12 0:37:29.262            We have been idle for 30 seconds, polling device states <0x40a69b70>
40      05/19/12 0:37:29.362            Sending job 0x9bcb928 (cb 88) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x58 0x67 (###### ##Xg) <0x40a69b70>
41      05/19/12 0:37:29.366            0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0x40a69b70>
35      05/19/12 0:37:29.367            ZW_SEND delivered to Z-Wave stack <0x40a69b70>
41      05/19/12 0:37:29.387            0x1 0x5 0x0 0x13 0x58 0x0 0xb1 (####X##) <0x40a69b70>
35      05/19/12 0:37:29.388            ZW_SEND Response with callback 88 received <0x40a69b70>
35      05/19/12 0:37:29.388            ZW_SEND was successful, removing job <0x40a69b70>

then i believe that it was switched to a wakeup time of 6 Minutes.

But after some time it seems to be resettet to 3600 again.

So after following the steps in the wiki for changing certain parameters, is there s.th i have to do to make them fix? Sorry, s.th like a SAVE?

If i send the command for the motion to have a maximum length of 1 minute, then i got following response:


40      05/19/12 0:41:03.503            Sending job 0x9bcea08 (cb 111) - 0x1 0x9 0x0 0x13 0xff 0x2 0x31 0x4 0x5 0x6f 0x47 (######1##oG) <0x40a69b70>
41      05/19/12 0:41:03.507            0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0x40a69b70>
35      05/19/12 0:41:03.508            ZW_SEND delivered to Z-Wave stack <0x40a69b70>
41      05/19/12 0:41:03.528            0x1 0x5 0x0 0x13 0x6f 0x0 0x86 (####o##) <0x40a69b70>
35      05/19/12 0:41:03.529            ZW_SEND Response with callback 111 received <0x40a69b70>
35      05/19/12 0:41:03.529            ZW_SEND was successful, removing job <0x40a69b70>
10      05/19/12 0:41:24.038            Receive string: MESSAGE 85             <0x41000b70>
10      05/19/12 0:41:24.038            Received MESSAGE 85             0x9b88870 device: 137 <0x41000b70>
10      05/19/12 0:41:24.038            Received Message type 1 ID 841 from 0 to 137 (device: 137) resp 0 <0x41000b70>
36      05/19/12 0:41:33.668            We have been idle for 30 seconds, polling device states <0x40a69b70>
40      05/19/12 0:41:33.769            Sending job 0x9bcec28 (cb 112) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x70 0x4f (###### ##pO) <0x40a69b70>
41      05/19/12 0:41:33.773            0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0x40a69b70>
35      05/19/12 0:41:33.774            ZW_SEND delivered to Z-Wave stack <0x40a69b70>
41      05/19/12 0:41:33.794            0x1 0x5 0x0 0x13 0x70 0x0 0x99 (####p##) <0x40a69b70>
35      05/19/12 0:41:33.795            ZW_SEND Response with callback 112 received <0x40a69b70>
35      05/19/12 0:41:33.795            ZW_SEND was successful, removing job <0x40a69b70>

i do not know, what am i doing wrong, with this zwave.

[murcel]

* posde is happy with regular KNX PIRs, which all have a function to turn on a specific device for a few minutes.

Posde,
do you have a suggestion for a minimum knx starter kit? Which products, i believe you have :-)

[Marie.O]

Look at the KNX/EIB page in the wiki. It is all there.

[murcel]

Look at the KNX/EIB page in the wiki. It is all there.

Did that :-)
Posde, i have choosen a minimum of products, just for testing. Can you please have a look wether its complete or s.th. is missing?

SCN-P360D3.01 PIR
STV-0160.01 PSU
SCN-IP000.01 IP/KNX
AKK-0406.01

Or do i need s.th. else?

[Marie.O]

You might want to add either a binary input (BE-04000.01    or BE-08000A.01), if you have existing switches you want to re-use, or add a BE-TA55P4.01