x10 triggers

[dreadlocks]

I am having problems getting X10 to trigger an alarm.
I have the port setup and permissions are correct (www-data is part of the dialup group) but nothing shows up in the logs when I trigger the motion sensor.. I have a chime hooked up so I know the signal is good, using other x10 programs I send commands to turn devices but its like nothing is coming back in..

Here is me trying to issue: zmx10.pl -c on -u 1

Code: Select all

Sending 2-byte packet: 0x04, 0x66
Got nothing back from the device...
Sending 2-byte packet: 0x04, 0x66
Got nothing back from the device...
Sending 2-byte packet: 0x04, 0x66
Got nothing back from the device...
Aborting send: too many bad checksums

If i use kermit to open the serial port and watch I dont get any signlas from the firecracker when the motion sensor goes off... shouldent I see something??

[dreadlocks]

crap, figured it out.. im new to X10 and aparently the firecracker device is transmit only.. I need the 2 way receiver.. makes sence, wish I woulda known

[cordel]

Thanks for the update, I have been meaning to start playing a bit with X10 so that I could be familur with it but haven't yet had the chance.
I was aware that they produced a transmit only and transiver device but it didn't dawn on me that might be the case. We will get a X10 device list started and maybe with some help of others put together a what to get and what not to get list starting with the firecraker

Again, thanks for the update.
Regards,
Corey

[pcalleros]

I have X10 IR sensors configured with external outdoor motion cameras triggering but not creating alarms. I can see in the x10 logs the x10 signals getting to the ZM box and thats it. I currently have the IR sensors directly connected to my OmniProII. My OmniProII is creating a 60 second "ON" state which ZM is seeing but no alarm appears to ever be generated for some odd reason. Any suggestions?

IE:

O3 is one IR sensor

Sending 'gimme events' byte
Executing command '/usr/bin/zmdc.pl start zma -m 7'
Executing command '/usr/bin/zmdc.pl start zmf -m 7'
05/10/31 17:31:27 - O03 ON
Sending 'gimme events' byte
Executing command '/usr/bin/zmdc.pl stop zma -m 7'
Executing command '/usr/bin/zmdc.pl stop zmf -m 7'
05/10/31 17:31:30 - O03 OFF


My syslog shows the following:

Oct 31 21:45:21 localhost zmf_m8[17523]: INF [Debug Level = 0, Debug Log = <none>]
Oct 31 21:46:30 localhost zma_m8[26030]: INF [Got signal (Terminated), exiting]
Oct 31 21:46:30 localhost zmf_m8[17523]: INF [Got signal (Terminated), exiting]
Oct 31 21:47:20 localhost zmf_m9[17640]: INF [Debug Level = 0, Debug Log = <none>]
Oct 31 21:47:43 localhost zma_m9[26036]: INF [Got signal (Terminated), exiting]
Oct 31 21:47:43 localhost zmf_m9[17640]: INF [Got signal (Terminated), exiting]

Never get an alarm though...just the above.

[dreadlocks]

ok I got me a pair of CM11A and now I am having the same issue as pcalleros, it is not triggering an event..
If I do a zmx10.pl -c on -u 5 it turns on device 5 which is my lamp
device 1 is my motion sensor and it is seen by the monitor but dosent trigger an event.

here is the log:

Code: Select all

Sending: AOF
Sending 2-byte packet: 0x06, 0x63
Good send, sending 0x00 as OK
Packet send successful
06/01/01 04:03:57 - A05 OFF
A05 off, ok
Sending 'gimme events' byte
06/01/01 04:04:38 - A01 ON
Sending 'gimme events' byte
06/01/01 04:05:37 - A01 OFF

[dreadlocks]

ok, once again I figured it out shortly after my post..
as you can see in my log it wasent running anything, I had it set to NoDetect because the manual implies this is to be used for triggers.. however when I thought about it, continous vs triggered would apply to record.. so I set it to record and now my motion sensor is triggering the event.. sweet

[dreadlocks]

I am now tyring to use the X10 Output Alarm String to trigger the chime and turn on a light when ZM starts recording. However it is only sending the signal when it STOPS recording, not when it STARTS.. When my light never turned on I set it to !5 and now my lamp turns on when it STOPS recording.. it seems the commands are never processed when it starts recording.

zmx10.log

Code: Select all

Sending 'gimme events' byte
Executing command '/usr/bin/zmdc.pl start zma -m 1'
Executing command '/usr/bin/zmdc.pl start zmf -m 1'
06/01/01 22:11:20 - A01 ON
Sending 'gimme events' byte
Executing command '/usr/bin/zmdc.pl stop zma -m 1'
Executing command '/usr/bin/zmdc.pl stop zmf -m 1'
06/01/01 22:12:19 - A01 OFF
Sending: A05
Sending: A05
Sending 2-byte packet: 0x04, 0x61
Good send, sending 0x00 as OK
Packet send successful
Sending: AON
Argument "ON" isn't numeric in numeric gt (>) at /usr/local/share/perl/5.8.4/X10/ActiveHome.pm line 193.
Sending: AON
Sending 2-byte packet: 0x06, 0x62
Good send, sending 0x00 as OK
Packet send successful
06/01/01 22:12:21 - A05 ON

[dreadlocks]

I have been digging arround in the zmx10.pl source, I dont know perl but I am a coder so I can see whats going on by the syntax alone.

I found the issue and fixed it, but it brings up another possible issue..
first off all I changed the line that read:

Code: Select all

if ( $state == 2 && $monitor->{LastState} == 0 ) # Gone into alarm state

to

Code: Select all

if ( $state > 0 && $monitor->{LastState} == 0 ) # Gone into alarm state

which now causes the signal to be sent when I activate the recording..

However this leads to another possible issue, I cannot get the Alarm State to work, ive set the camera to Modect and NoDect (I added NoDect to the sql query as had changed in the 22-rc1) and it will not respond and trigger an alarm..
The only thing I can get to work is putting it in 'record', 'triggered','x10' and using the activation string.. this works for me but I think the idea behind having the activation vs alarm thing is if people also use an X10 security system and dont even want any recording to take place unless there security system is activated, then have alarms triggered by sensors only when they are away from home...

This leads me to my third point, I suppose since you have a setting for X10 Output Alarm String you should also have a setting for X10 Output Activation String incase you want someting like say the chime to go off to signify that ZM is now active.

In my case I just want ZM to tell the chime to go off instead of the motion sensor doing that.. when the chime is tuned directly to the motion sensor it goes off over and over agin til motion stops which is verry annoying when unloading groceries or there is alot of movment.. now I only get one chime when ZM starts recording, authough there is more of a delay now (2-3s) for the chime to go off its worth it.