[wish-info] Unit No Problem with x10watch

[Sergey Udaltsov]

Hi all

I got motion sensor and light switcher. Motion sensor generates H14,
light switcher expects H15.
Latest x10dev detects signals from the sensor ok. If I do:
$ x10watch /x10/kitchen/sensor -1 "echo on" -0 "echo off " -d
I see on and off coming properly. But when I do
$ x10watch /x10/kitchen/sensor -1 "echo on > /x10/kitchen/upperlight"
-0 "echo off > /x10/kitchen/upperlight" -d
(upperlight and sensor are symlinks to /dev/x10/h15 and h14
correspondingly) - I never get "off signal. Looking at /var/log/x10, I
see:
Apr 28 23:52:04 sputnik R H14
Apr 28 23:52:05 sputnik R H ON
Apr 28 23:52:06 sputnik T H15
Apr 28 23:52:06 sputnik T H ON
Apr 28 23:53:05 sputnik R H OFF

So, at 23:52 the signal H14 ON came - and PC generated H15 ON. But at
23:23 signal OFF came - and it seems x10watch (or whoever it is -
kernel driver?) could not identify it as coming from H14. How could I
workaround this?

TIA,

Sergey

[Scott Hiles]

When your system transmitted H15 ON, did the light actually come on? If it
didn't, then it could be that you never actually sent the H15 ON through the
powerline. As a result, the sensor may have been intelligent enough to
recognize that H14 was still the addressed house/unit and just sent the OFF
command which you saw.

If the light did come on when you transmitted H15 ON, then I don't have an
answer for you.

Without the x10watch program running, you should still see the on and off
commands in your log.

Scott

-----Original Message-----
Sergey Udaltsov
Sent: Thursday, April 28, 2005 7:47 PM
Subject: [wish-info] Unit No Problem with x10watch
Hi all
I got motion sensor and light switcher. Motion sensor generates H14,
light switcher expects H15.
$ x10watch /x10/kitchen/sensor -1 "echo on" -0 "echo off " -d
I see on and off coming properly. But when I do
$ x10watch /x10/kitchen/sensor -1 "echo on > /x10/kitchen/upperlight"
-0 "echo off > /x10/kitchen/upperlight" -d
(upperlight and sensor are symlinks to /dev/x10/h15 and h14
correspondingly) - I never get "off signal. Looking at /var/log/x10, I
Apr 28 23:52:04 sputnik R H14
Apr 28 23:52:05 sputnik R H ON
Apr 28 23:52:06 sputnik T H15
Apr 28 23:52:06 sputnik T H ON
Apr 28 23:53:05 sputnik R H OFF
So, at 23:52 the signal H14 ON came - and PC generated H15 ON. But at
23:23 signal OFF came - and it seems x10watch (or whoever it is -
kernel driver?) could not identify it as coming from H14. How could I
workaround this?
TIA,
Sergey
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id5hix
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info

[Sergey Udaltsov]

Post by Scott Hiles
When your system transmitted H15 ON, did the light actually come on? If it

Yes it does. It works correctly - I see the light turning on.

Post by Scott Hiles
didn't, then it could be that you never actually sent the H15 ON through the
powerline. As a result, the sensor may have been intelligent enough to
recognize that H14 was still the addressed house/unit and just sent the OFF
command which you saw.
If the light did come on when you transmitted H15 ON, then I don't have an
answer for you.

Pity:((

Post by Scott Hiles
Without the x10watch program running, you should still see the on and off
commands in your log.

Yeah, I realize.

BTW, I stopped and restarted x10watch between ON and OFF (on H14) -
and, sure, nothing changed. I don't really understand how happens that
sensor (actually, not sensor - RF transmitter receiving radio signal
from sensor) does not send unit number before the OFF operation...

Sergey