EZmotion motion detection problem

[magner]

Hi,

I am currently trying to set up the motion detection for the EZmotion device.

I have followed the instructions from :

http://wiki.linuxmce.com/index.php/Express_Controls_EZmotion_(HSM_100)

I am concentrating on just the motion detection at the mo.

Here is what I have done...
Advanced>config>devices...
left side of screen srcoll down the zwave
then under security I create child device
choose template for motion detector

fill in motion detector information

port/channel number I get from multi level sensor tab under security port/channel number.
capabilities = 133,96,49,112,132,128,114,119,134
floorplan type = motion detector

I then create respond to event

event = a sensor door/window/motion
device - motion detector
time of day = day

command section

light switch on/off  to send an on command (when i press test command button it works fine)
dcerouter to execute command,
then I save.

Now I can see the LED on sensor activates when i move infront of it but it does not trigger event for light to go on/off.

in logs for my z wave it says:

No callback received: await_callback: 129 timer: 31 <0xb70c4b90>
05   12/17/10 11:13:15.276      ZWave::InternalIDToDevice() No device found for id 2/2

Can anybody please help me with this problem.

thanks in advance.

Daniel

[hari]

please enable log levels 36, 40 and 41 in /etc/pluto.conf - this will provide us with a more verbose logging.

I'd suspect that you did not do the association properly. After inclusion you need to associate the node id of the dongle to group 1 of the sensor.

best regards,
Hari

[magner]

Hi Harri,

Thanks for the swift reply.
According to the How to description, the ID is the same as the port channel number right? if so mine came out as 2.

Sorry, as not to just post all my logs, what logs would you like to see, error, whole or follow logs

this is what i found at the end of whole log.

ZW_SEND Response with callback 17 received <0xb7240b90>
36   12/17/10 19:00:19.814      ZW_SEND was successful, removing job <0xb7240b90>
40   12/17/10 19:00:19.914      Sending job 0x9a86240 (cb 18) - 0x1 0x9 0x0 0x13 0xff 0x2 0x31 0x4 0x5 0x12 0x3a (######1###:) <0xb7240b90>
41   12/17/10 19:00:19.921      0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb7240b90>
36   12/17/10 19:00:19.922      ZW_SEND delivered to Z-Wave stack <0xb7240b90>
41   12/17/10 19:00:19.943      0x1 0x5 0x0 0x13 0x12 0x0 0xfb (#######) <0xb7240b90>
36   12/17/10 19:00:19.944      ZW_SEND Response with callback 18 received <0xb7240b90>
36   12/17/10 19:00:19.944      ZW_SEND was successful, removing job <0xb7240b90>
41   12/17/10 19:00:24.245      0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x1 0x0 0xd2 (####### ###) <0xb7240b90>
36   12/17/10 19:00:24.246      FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7240b90>
36   12/17/10 19:00:24.246      COMMAND_CLASS_BASIC -  <0xb7240b90>
36   12/17/10 19:00:24.246      Got BASIC_SET from node 2, value 0 <0xb7240b90>
36   12/17/10 19:00:24.246      This is a binary sensor, so we send sensor tripped events <0xb7240b90>
36   12/17/10 19:00:24.246      Sending sensor tripped event from node 2 <0xb7240b90>

and end of follow logs

36   12/17/10 19:18:24.767      COMMAND_CLASS_BASIC -  <0xb7240b90>
36   12/17/10 19:18:24.767      Got BASIC_SET from node 2, value 0 <0xb7240b90>
36   12/17/10 19:18:24.767      This is a binary sensor, so we send sensor tripped events <0xb7240b90>
36   12/17/10 19:18:24.767      Sending sensor tripped event from node 2 <0xb7240b90>
41   12/17/10 19:18:40.025      0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x1 0xff 0x2d (####### ##-) <0xb7240b90>
36   12/17/10 19:18:40.026      FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7240b90>
36   12/17/10 19:18:40.026      COMMAND_CLASS_BASIC -  <0xb7240b90>
36   12/17/10 19:18:40.026      Got BASIC_SET from node 2, value 255 <0xb7240b90>
36   12/17/10 19:18:40.026      This is a binary sensor, so we send sensor tripped events <0xb7240b90>
36   12/17/10 19:18:40.026      Sending sensor tripped event from node 2 <0xb7240b90>

Please let me know if there is something specific I should be looking for

Thanks for your time

Daniel

[hari]

there are sensor tripped events shown in the log for node 2. does not look like  a z-wave specific problem. Check your event handler.

br Hari

[magner]

Harri,
Thank you very much for your help.

Turned out to be a battery problem (dead as doornails). Swapped them over and detector seems to be working now.

Regards
Daniel