Re: Survey: Home Control Software

[nobody@xxxxxxxxxxxx (Dave Houston)]

Unless you're using something that receives RF directly, you cannot see the
RF messages. You only see powerline messages so the incorrect command has
already made it to the powerline before your software is aware of it.

Even if your software does receive direct RF messages, there are seldom
collisions between RF codes and when there are, the result is garbage -
there's no possible way to sort out what the two colliding messages were.
The RF messages do contain data which allows a receiver to check validity
but any corruption will merely cause an invalid message it will not cause
one message to be transformed into another. IOW, corrupt RF messages never
make it to the powerline from any X-10 transceiver.

Bream Rockmetteller <bream(dot)rockmetteller(at)mac(dot)com> wrote:

>Regarding the software, the reason it knows it has received a "bad"
>message is because I told it so. When I have a light act in a strange
>manner, I look at the log that Indigo keeps.
>
>If I see that an RF switch somehow transmitted "turn on E10" instead of
>"turn on the kitchen lights" which are E1, I'll  add a script in the
>"Trigger Actions" sections that says something like "If you receive a
>message to turn on E10, send a message to turn on the kitchen lights."
>That way, even if the switch or the receiver or some random noise has
>caused the message to go bad, the software will re-transmit the correct
>message.
>
>I hope this helps...


http://davehouston.net  http://davehouston.org
http://tech.groups.yahoo.com/group/roZetta/
roZetta-subscribe@xxxxxxxxxxxxxxx