X10 Community Forum
🖥️ActiveHome Pro => Plug-ins => iWatchOut/iWitness => Topic started by: RVerkoey on April 03, 2005, 09:54:55 AM
-
I installed the IWitness plugin and was
very impressed with it initially... I have
noticed that most of my motion sensors stop
working when the the IWitness plugin is
running. When I turn off the plugin, the
motion sensors work again. Anyone have any
suggestions? I have 4 cams on Housecodes
B1 - B4 as well as all the motion sensors
Remainder of light/appliance modules are
House Codes A1 to A16. AHPro is set
monitor Housecode B and transieves
Housecodes A and B. Using Win XP Home.
-
RVerkoey
I am not sure what you mean by “most of my
motion sensors stop working” If you look
at the activity monitor do they show when
there is motion ? If it were me I would put
all of the cameras on a house code of their
own. AHP sends off commands to the unused
cameras when one is selected. Not sure what
this might do to other devices set to the
same house code. I use house code B only
for cameras. I have not had any problems
with my motion sensors when the camera
software is running.
You may want to avoid house code A1’s use
altogether as it is the code the motion
sensors default to when the batteries start
to get week. I have had some strange things
happen, like the light that was set to A1
turn on and off for no apparent reason. It
ended up being the batteries starting to
fail in one of the motion sensors.
-
RVerkoey: Can you explain what you mean when
you say your motion sensors stop working?
There's no way that the software could make
your hardware motion sensors stop
transmitting. Do you mean that your sensors
stop triggering your macros? Are you not
seeing the motion sensors activated in AHP?
-
X10 Pro:
When the IWitness software is running,
Motion sensors that turn on lights (A5, A6
etc.) do not trigger the macro. The little
LED still blinks. They do not register in
the Activity monitor either. As soon as I
turn off the camera plug-in, the motion
sensors (A5, A6 etc) begin to turn lights on
again when motion it detected. I have AHPro
set to transcieve House Codes A, B, C.
A1 to A16 are my lights/appliances and some
motion sensors (set to the corresponding
light - A5 or A6 etc)
B1 - B10 are macros
C1 to C4 are my 4 cameras.
AHPro is set to monitor Housecode B.
I am using Win XP Home.
-
How are you turning off the camera plug-in?
When it's not turned off, do you have the
automatic camera switching on? What version
of AHP/iWitness is this?
-
X10 Pro:
I click the "x" to close the plugin while
still running AH PRo. The problems occurs
when the Auto Switching is running as well
as when it is not, just viewing the live
feed. Using Version V3.185
Also, I set up a macro to "Select Front
Cam", "Start Video Recording", "Delay 1
minute", "Stop Video Recording". This does
not work either. No response from the
IWitness plugin software when motion is
detected.
-
RVerkoey,
I noticed problems with RF range for the
motion sensors too, and I think that's what
you are seeing. I was able to fix the problem
by unplugging the USB cable from the CM15A
interface, however now I can't use the video
plugin. So, in my case at least, it's either
live video or motion sensor lights.
X10 Pro, why does my CM15A behave this way?
Is there anything I can do to have the same
RF range when the cable is connected or
disconnected? I tried resetting it, different
plugs, etc - same result: as long as the USB
cable is connected the RF range drops
significantly. I was able to test this with a
remote control - I disconnected the USB cable
and went outside, turned the porch lights on
and off (using the remote) from where the
motion sensor is located, then I unplugged
the USB cable and did the same thing, but
this time the lights did not turn on or off.
Activity Monitor also confirms that RF
signals are not being sent / received when
the USB cable is plugged in. If I move the
motion sensors closer to the CM15A, then they
work.
-
Julian: I posted on another thread where you
mentioned this that the most likely cause of
the problem with range when connected to the
PC is that the PC is putting out RF noise
that is being coupled down to the CM15A on
the USB cable. Short of replacing the PC or
the noisy components in it, the only thing
you can do is unplug the USB cable. A few
other users on these forums had the problem
and were experimenting with chokes, but I
don't know if that ended up working.
RVerkoey: Can you try flipping a light on and
off from the screen, then open the Video
Window and see if your motion sensors work?
-
X10 Pro - while your explanation of the PC
putting RF noise is plausible, I can't
understand why my setup used to work fine and
all of a sudden it stopped(after the iWitness
plugin). Nothing has change in my computer -
it's still the same one with the same
components.
I even have noise filters on my computers and
entertainment unit, to minimize RF noise.
-
I didn't realize that the problem just
started. I'll see if we changed anything that
might account for it.
-
X10 Pro - thanks for looking into it.
-
X10 Pro:
I have reinstalled AH Pro and the iWitness
Plug-in. I am still getting the same
problem. When iWitness is running, my
furthest motion sensors (approx 25 feet) in
the basement stop turning on lights. When
I turn off the iWitness plugin, everything
returns to normal. The iWitness plugin is
the culpret for sure. A motion sensor
within approx 5 feet will trigger a macro
no problem with the plugin running and I
can turn on lights/appliances within AH Pro
as well. It is just the reduced range on
the RF that needs a fixin. Looking forward
to your next patch.
-
X10 Pro:
Since plugging my RR501 (Housecode A) and
TM751 (Housecode B) back in, all of my
motion sensors are responding normally. No
more reduced range. So, now that my
cameras (Housecode C) are switching on
motion, the Snapshot and video will not
start. Cameras switch to the activity but
the "start recording" portion of the macro
does not initiate. Any suggestions !
V3.184
-
RVerkoey: Can you send me
(ahpsupport@x10.com) your AHP data file? It
should be a .AHX file in Program
Files\ActiveHome Pro\.
-
I noticed a problem as well - With a video
window on screen, events don't seem to
occur. I had the video window open and my
timed events didn't happen. With the window
closed the events happened as they should.
-
Donald: Were those events supposed to run
from the PC, or were they stored in the
interface?
-
RVerkoey:
I have motion sensors which trigger macros
that are stored in the CM15A interface. The
Macro selects the correct camera and
positions, starts the VCR Commander, and
then another macro that I call CPU Commander
(dummy module/macro). The CPU Commander
macro is stored on the PC and starts/stops
the snapshots. Everything worked but the
recording… just as in your case. What I
found is that the command after a RF command
(like the VCR Commander) was ignored. I
switched the CPU Commander macro to run
before the RF command was sent and every
thing worked. I did this on five different
macros and they all started recording. So
if you using any RF commands in your macros
try making them last to see if that will
help. I’m using WinXP, SP2, and the CM15A
Diagnostic. I have to augment the CM15A
with two TM751 transceivers for all motion
sensors, Stick-a-switches, and any other RF
device due to its poor RF reception.
-
The events are stored in the interface. I
have not had any problems with them - a
simple timed light turning on. When
IWitness is turned off event handle return
to normal - the events are not being
delayed, they just don't occur.
-
X10 Pro: why not support the untethered
from USB functioning of the CM15A with the
Video Plug-in?
The AHP/CM15A certainly don’t need the USB
once all the setups and down loads are
finished. The PC acts as a DVR via AV11A as
well as a video picture Display, while the
CM15A drives the sequencing. What needs to
be communicated can simply be accomplished
via RF echo of what is being sent to the
cameras via the power line. Firecracker RF
Transmitter and an MR29A RF Receiver or a
CM19A is all that would be required on the
PC side.
-
X10 Pro:
Any luck with my .ahx file I sent you 5 Apr
05? Just wondering is you guys found any
problems with it and the iWitness plug-in ?
-
RVerkoey: There didn't seem to be anything
wrong in the file. We're still looking at the
problem, though.
-
I have AHP & IWitness. How do I set up
motion detectors so that they turn on
cameras and record?
-
John S
Set motion detector to house and unit code of
your choice - Build a macro triggered by that
H and U code which turns on cam and records
video, snapshots, etc. Caution...the
interface must be connected to the computer
to save recording files, the computer must be
on at all times, and don't forget to set
hardware settings to allow that housecode.
Once it's working you can get more creative
with your macro and camera preferences. Hope
this helps.
-
Thanks WinS,
I tried to build a macro as suggested but do
not see the motion sensors as a hardware
choice on the macro screen. how do I get
them listed there?
Also you referred to H & U codes. I'm
assuming those are an example of house &
unit codes and not that I must use those
exact codes.
-
John,
Before you can build a macro you have to
have all of the devices you wish to use
(motion sensors, lamp modules, appliance
modules…....) already selected and placed
into a room. Once you have done that you
should see them when you try to make a
macro. If you don’t see them you probably
don’t have that room selected in the drop
down menu on the right side of the screen.
Yes. I think that WinS is referring to the
unit and house code of the devices you are
going to use.
Good luck,
Jim
-
Thanks Jim,
The sensors were selected and putin the room
and the room is selected in the drop down
menu on the right side. However I still dont
see the sensors. any other thoughts?
John
-
John,
I don’t know that you will see them in the
macro window nor do you need to. You need
to set the house and unit code of the macro
to that of the motion sensor. You then
select the items you want to control and
place them into the macro.
Jim
-
The Motion Sensor is just a place holder in
AHP for that address - you won't see a
selectable module when you create a macro -
there is nothing for you to change or
activate. Just make sure that your macro
uses the same address as the sensor - the
macro will execute when the motion sensor
is triggered. Thats all there is to it.
Just make sure that you use the appropriate
address and ON/OFF sequence. Note: some
sensors also will trigger at sunrise/sunset
(using light levels not a pre-programmed
time). This will occur at address+1 (ie: if
the sensor is programmed at for motion at
address "B6" - then the sunrise/sunset
address will be "B7"). MAKE SURE THAT YOU
DON'T HAVE SOMETHING ON THIS ADDRESS OR YOU
WILL GET UNWANTED DEVICE ACTIVATIONS.
Unless of course you want to use this
feature. It would be nice if the sensor
modules was changed to show this additional
address requirement for the affected
modules.
-
John S
Here is a basic example, although there are
many more elaborate ones:
When motion sensor (set to B1)is triggered,
camera (set in AHP as A1) is turned on and
records video for 20 seconds.
1. Set the motion sensor to house and unit
code B1.
2. Build camera module in AHP and set to A1.
3. Build a macro named "CamA1 Video".
Set macro trigger to "B1 On".
Select the camera from the drop down list
and place in the body of the macro -set to
"On".
Select from the drop down list
(Video Functions) "Video Recording", place
in the macro body and set to "Start".
Select from the lower drop down list
"Delay" place in the body and set to 20
seconds.
Select from the drop down list (Video
Functions) "Video Recording", place in the
macro and set it to "Stop".
Once you get things working you will see a
multitude of possibilities. Have fun!
-
Thanks for the advise WinS & Donald.
I followed it to the letter. However I still
am unable to get the recording to activate
from the motion detector.
Does it matter that the type of motion
detector is the Eagle Eye type?
Also, Inoticed at the bottom of the Macro
windoe it has an interface button & run from
PC button. Neither can be checked. however
there is a note next to the buttons that says
"Macro must be run from the PC.
Is that run from PC button supposed to be
checked and how can I get it to accept being
cheked. That is if you think thats even an
issue.
John S
-
John S
Have you checked the activity log to verify
that the sensor is sending a signal? If not,
move it close to the interface and try again.
If it works, what code is it sending?
-
John S
I meant to add that the two options in the
macro are fixed for cam recording - cannot be
changed, as both are required for proper
operation.
-
WinS,
I'm close but no cigar. As per your
suggestion I brought the motion sensor close
to the interface. At first it did not work
and then it did.
Thereafter it would work sometimes and
sometimes not. I have yet to get it to work
with the sensor further away from the
interface (as little as 20 ft away).
I have also got error messages from AHP
saying that an error has occured and AHP has
to shut down.
I have changed batteries in both the sensor
and the interface.
I noticed that moving the USB wire around
helped in getting a connection. So I changed
wires, but still had the problem. I think
there must be something wrong with the
interface or the connection.
X10 support has not got back to me since I
called them several times since last week as
including today. So I do appreciate the
suggestions from you and Don.
Curious to know your thoughts.
John S
-
John S
Rf range problems are quite commom. You may
have to experiment with the location of the
interface, even within the range allowed by
the USB cable. Also, the receive range of
the interface may be improved by setting the
unit horizontally (ActiveHome sticker facing
down)with the antenna at a 90 degree angle.
Some say this helps. The distance from the
sensor, how many walls the signal must pass
through, etc., all will affect the outcome.
So I recommend you get things working near
the interface and then move on to where you
would like the sensor and camera to be.
Another thing; multiple triggers of the
sensor within a short period of time could
"upset" the AHP program causing a crash.
Question: When the sensor signal is received
ok, does the macro work and the camera record?
-
The "anonymous" was mine.
-
Thanks WinS,
When the signal is received the Macro and
camera does work and it does record.
I will experiment with the distances and
position of the interface. However, I think
the interface or connection to it is the
problem because moving the cable around
seems to work sometimes.
Any way, I'm beginning to think that this
system (wireless) may not be the product for
my needs. The house is about6000 sq ft and
therefore if the wireless tends to be
problematic with distance and going thru
walls I might have to consider wired. Which
most of the house was recently wired for
cameras. I was using x10 wireless for a
quick nanny cam while researching hard wired
cameras and dvr systems.
Thanks again for your help.
JohnS
-
I've had very similar issues when running
the iWitness plug-in, not only with motion
sensors, but anything that sends or receives
RF signal. It's almost as if iWitness or
the cameras diminish RF Frequency
strength/reliability or interferes with it.
I ended up getting the RF Repeater/Extender,
which helped significantly, but only when
iWitness is not running. I'm now back to my
VCR Commander and recording to VHS. As
antiquated as that may be, it is by far more
reliable than using iWitness.