Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[schmuttis]

Hi,

I have a fairly new eagle eye setup outside that works intermittently with a WS467 wall switch which controls several outdoor wall lights. I go outside and walk past the eagle eye. The eagle eye transmits to a wall switch but the lights never go on. I've attached the AHP log of the activity. When I check the AHP software, it shows the wall lights as being turned on. Using the AHP software I manually turn off the light switch and then turn them on. The lights go on. I was hoping someone might give me an idea of why the lights/wall switch don't go on when triggered by the eagle eye. We do have a bridge installed in the panel box so it's not a matter of being on the wrong 110 volt leg. Thanks for any and all suggestions.

221    12/6/2010 5:35:25 PM    Receive    K9
222    12/6/2010 5:35:26 PM    Receive    K9
223    12/6/2010 5:35:26 PM    Receive    K9
224    12/6/2010 5:35:29 PM    Receive    K11 (wall lights backyard)
225    12/6/2010 5:35:29 PM    Receive    K On (wall lights backyard)
226    12/6/2010 5:35:36 PM    Receive    K On (wall lights backyard)
227    12/6/2010 5:37:06 PM    Receive    K On (wall lights backyard)
228    12/6/2010 5:37:19 PM    Receive    K On (wall lights backyard)
229    12/6/2010 5:37:24 PM    Receive    K11 (wall lights backyard)
230    12/6/2010 5:37:58 PM    Receive    K On (wall lights backyard)
231    12/6/2010 5:38:05 PM    Receive    K11 (wall lights backyard)

We live in PA and it's cold but not precipitating.

[dave w]

Hi,

The eagle eye transmits to a wall switch but the lights never go on. I've attached the AHP log of the activity. When I check the AHP software, it shows the wall lights as being turned on. Using the AHP software I manually turn off the light switch and then turn them on. The lights go on. We live in PA and it's cold but not precipitating.

Sounds like your problem is with the macro you have to turn on the wall switch from the eagle trigger. When you force the macro to run with the RUN button, does the light work?

[schmuttis]

I'm not using a macro. I just have the eagle eye set to K11 and the wall switch/outside lights set to K11. I've been using AHS to try to figure out what the problem happens to be.

[schmuttis]

I meant AHP instead of AHS - sorry.

[Brian H]

Is the X10 bridge a passive one or a coupler repeater?
Are you using a transceiver like a TM751 or RR501 to receive the motion sensor or the built in receiver in the CM15A?

[schmuttis]

The bridge is a COUPLER, REPEATER, 240 VAC, CONSTANT OUTPUT AMPLITUDE SPLIT.

We had been using multiple TM751's and the wall switch worked rather well. Recently we added the CM15A. That seemed to work until it got cold outside. We've changed the location of the CM15A as well as the computer that it's attached to. The CM15A is on a long extension cord to a different outlet then what the pc (laptop is on). Previously we had the CM15A hooked into a regular PC with UPS. I switched it after reading about some of the noise problems.

I do use timers on the CM15A to turn on other lights and that seems to be working fine.

[Brian H]

Is K9 an address used in your system?

Are the TM751s on the same House Code? Since they are not polite. Sometimes more than one sends at the same time and scramble things.

Some X10 signal repeaters have been known to get into a signal fire storm when a CM15A is also in the system. That depends on the brand and model being used.

[schmuttis]

Actually I'm not sure what K9 is. When I go into "find other computers" it comes up as a red "other detected codes".

There are 5 TM751's on K house code and 1 on N house code. So it would be better to have each transceiver a different code and if we want them to turn on a different house code we'd use a macro? We've never successfully gotten our eagle eyes to work with our floodlights and chimes. Perhaps this is the reason.

This is the coupler that we have: http://www.x10.com/pro/automation/xpcr.htm. We were using this and the TM751's and all seemed to be fine. We added the CM15A and thought everything was ok then started to have problems. We associated it with the cold weather which we didn't think made sense since we saw what seemed to be the correct activity in the CM15A log.

Codes we are currently using: K, K3, K4, K5, K6, K7, K8, K10, K11, N, N1, N2, N3

What would be your suggestions?

[troll334]

If K8 is one of the XXXeye sensors, then K9 is likely his Dusk/Dawn sensor signal. You might already know...that
the motion sensor uses two codes. The primary (what you program into the sensor) is the motion signal. The Primary+1
is the light sensor used for Dusk/Dawn detection. Hence, you don't want to configure one motion sensor for K8 then
another motion sensor for K9. If you have more than one TM751 configured for a single house code, as Brian discusses,
they may be hearing the motion sensor RF signals and shoving the commands on the powerline at, or near, the same
time. This commonly leads to collisions which X10 receivers can discard as noise.
Place a TM751 as close to an outside motion sensor as possible (configured for the same house code). Unplug any other
TM751's that are on the same house code. Trip the motion sensor outside. See what happens (including AHP logging).
The fact that your log shows all 'Receives' vs. "Receive RF", says the CM15A is not hearing the motion sensor, It must be
one or more TM751s getting the RF signals and placing them on the powerline.

[schmuttis]

I set all of the transceivers to a different house code. The transceiver closest to the eagle eye and the eagle eye are both K. I'll let you know what happens tonight.

Thanks for all of your help.

[Brian H]

If K10 is another motion sensor. Its Dusk Dawn sensor will be K11.

[schmuttis]

We put all of our eagle eyes outside tonight and voila - they worked. You guys are great! We actually had the opposite problem since we just stuck them outside quickly - the chimes were going off all over the place because it was a windy night. As soon as it warms up a bit we'll find more permanent locations for them.

My only question at this point is do the eagle eyes really work up to 100 feet from a transceiver? The eagle eyes were blinking from movement but the floodlights weren't being triggered. Moving them closer the floodlights did go off. We have a frame house with wood siding and the transceivers are in the 4 corner rooms. Each transceiver is now a different code as are the chimes and floodlights. The hand held remote was able to turn the lights on and off where we thought the eagle eyes should also be able.

Once again - thank you so much for your help. We were ready to give up on the eagle eyes.

[troll334]

On a good day, the XXXeye sensors can make it 100'. Line-of-sight with no RF interference. RF is magic...
I placed an EagleEye 40' away from my CM15A (on the opposite side of my house; all inside equip) and it had trouble
making the trip. Of course, that's three interior walls, one concrete garage wall, and a bunch of metal electrical
appliances the signal had to penetrate. Once I purchase and installed a V572RF32, problem solved. I can now take
an EagleEye across the street to a neighbor's house and still trip macros, etc. Take the time to run some tests with
fresh batteries installed.