w800RF headaches are back

[Tom-172]

I am fed up with my w800rf on my mh machine running linux.
In the past, I've had issues where it wouldn't receive any signals and
sometimes a machine restart would fix it, and sometimes stopping mh and
issuing the setserial command:

/bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a

and restarting it again.

/bin/setserial -g /dev/ttyS5      shows:

/dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11

I've tried moving it around to different serial ports and in the past,
I've had mixed results.. It even started working again on the same
serial port that it wasn't working on before.  My other devices work
fine on the serial port that the w800 is having problems on so I'm not
convinced that my serial port is the problem.

I've toyed with the idea of getting a USB to serial adapter in hopes of
avoiding these issues..

Would this be a more reliable option?  am I using the wrong setserial
options? Can someone with the w800rf and linux reply with what
"setserial -g ...." shows?  any ideas?

thanks,
tom


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Tom-172]

I forgot to mention that it works fine on a windows machine.
Using the w800rf32 win decoder software from
http://www.wgldesigns.com/w800.html I confirmed that it is seeing all
signals correctly.

Tom wrote:

> I am fed up with my w800rf on my mh machine running linux.
> In the past, I've had issues where it wouldn't receive any signals and
> sometimes a machine restart would fix it, and sometimes stopping mh
> and issuing the setserial command:
>
> /bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a
>
> and restarting it again.
>
> /bin/setserial -g /dev/ttyS5      shows:
>
> /dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11
>
> I've tried moving it around to different serial ports and in the past,
> I've had mixed results.. It even started working again on the same
> serial port that it wasn't working on before.  My other devices work
> fine on the serial port that the w800 is having problems on so I'm not
> convinced that my serial port is the problem.
>
> I've toyed with the idea of getting a USB to serial adapter in hopes
> of avoiding these issues..
>
> Would this be a more reliable option?  am I using the wrong setserial
> options? Can someone with the w800rf and linux reply with what
> "setserial -g ...." shows?  any ideas?
>
> thanks,
> tom
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Charles Sullivan]

What do you get if you run 'stty -a -F /dev/ttyS5' ?


On Fri, 20 Jun 2008 21:51:47 -0400
Tom <tom.valdes@...> wrote:

> I forgot to mention that it works fine on a windows machine.
> Using the w800rf32 win decoder software from
> http://www.wgldesigns.com/w800.html I confirmed that it is seeing all
> signals correctly.
>
> Tom wrote:
> > I am fed up with my w800rf on my mh machine running linux.
> > In the past, I've had issues where it wouldn't receive any signals and
> > sometimes a machine restart would fix it, and sometimes stopping mh
> > and issuing the setserial command:
> >
> > /bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a
> >
> > and restarting it again.
> >
> > /bin/setserial -g /dev/ttyS5      shows:
> >
> > /dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11
> >
> > I've tried moving it around to different serial ports and in the past,
> > I've had mixed results.. It even started working again on the same
> > serial port that it wasn't working on before.  My other devices work
> > fine on the serial port that the w800 is having problems on so I'm not
> > convinced that my serial port is the problem.
> >
> > I've toyed with the idea of getting a USB to serial adapter in hopes
> > of avoiding these issues..
> >
> > Would this be a more reliable option?  am I using the wrong setserial
> > options? Can someone with the w800rf and linux reply with what
> > "setserial -g ...." shows?  any ideas?
> >
> > thanks,
> > tom
> >
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

--


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Tom wrote:

> I forgot to mention that it works fine on a windows machine.
> Using the w800rf32 win decoder software from
> http://www.wgldesigns.com/w800.html I confirmed that it is seeing all
> signals correctly.
>
> Tom wrote:
>> I am fed up with my w800rf on my mh machine running linux.
>> In the past, I've had issues where it wouldn't receive any signals and
>> sometimes a machine restart would fix it, and sometimes stopping mh
>> and issuing the setserial command:
>>
>> /bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a
>>
>> and restarting it again.
>>
>> /bin/setserial -g /dev/ttyS5      shows:
>>
>> /dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11
>>
>> I've tried moving it around to different serial ports and in the past,
>> I've had mixed results.. It even started working again on the same
>> serial port that it wasn't working on before.  My other devices work
>> fine on the serial port that the w800 is having problems on so I'm not
>> convinced that my serial port is the problem.
>>
>> I've toyed with the idea of getting a USB to serial adapter in hopes
>> of avoiding these issues..
>>
>> Would this be a more reliable option?  am I using the wrong setserial
>> options? Can someone with the w800rf and linux reply with what
>> "setserial -g ...." shows?  any ideas?

I have a moxa 8-port card.  I've not personally experienced the problems
that you've indicated and also never use setserial on any of the moxa
ports.  Anyway, here goes:

[gliming@baltar ~]$ sudo setserial -g /dev/ttyM2
/dev/ttyM2, UART: 16550A, Port: 0xe710, IRQ: 169

And, from my ini file:

W800_module=X10_W800
W800_port=/dev/ttyM2

And, info (in case it's relevant) from dmesg:

MOXA Smartio/Industio family driver version 1.8
Found MOXA C168H/PCI series board(BusNo=0,DevNo=10)

... running fedora core 5 and compiled kernel 2.6.17

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Tom-172]

Gregg Liming wrote:

> [gliming@baltar ~]$ sudo setserial -g /dev/ttyM2
> /dev/ttyM2, UART: 16550A, Port: 0xe710, IRQ: 169
>
> And, from my ini file:
>
> W800_module=X10_W800
> W800_port=/dev/ttyM2
>
> And, info (in case it's relevant) from dmesg:
>
> MOXA Smartio/Industio family driver version 1.8
> Found MOXA C168H/PCI series board(BusNo=0,DevNo=10)
>
> ... running fedora core 5 and compiled kernel 2.6.17

It seems that the w800 on linux doesn't listen as well as on windows.

With the antenna disconnected, I don't see any issues, but with the
antenna connected, I'm seeing tons of signals received (one after the
other).
Using the windows decode program, it would see these signals coming in
at a high rate of more than 1/second, but it would also see the other
incoming signals.
Linux gets flooded with these signals and doesn't see any other signals.

Here's what I see in my mh log files

  No match found: XA1AJ
06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XA1AJ (A 1)
X10 db: try breaking XA1AJ into 4 and 2 character chunks:
  No match found: XAJ
06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XAJ (A ON)
06/21/08 08:57:03 AM X10: Unmatched incoming data=XA1AJ
Serial data: event_type=X, event_data=XA1AJ
06/21/08 08:57:03 AM X10: Incoming data=XA1AJ
X10: Previous units=A1 reset_flag=1
X10 db: try breaking XA1AJ into 4 and 2 character chunks:
  No match found: XA1AJ
06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XA1AJ (A 1)
X10 db: try breaking XA1AJ into 4 and 2 character chunks:
  No match found: XAJ
06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XAJ (A ON)
06/21/08 08:57:03 AM X10: Unmatched incoming data=XA1AJ
Serial data: event_type=X, event_data=XA1AJ
06/21/08 08:57:05 AM X10: Incoming data=XA1AJ
X10: Previous units=A1 reset_flag=1
X10 db: try breaking XA1AJ into 4 and 2 character chunks:
  No match found: XA1AJ
06/21/08 08:57:05 AM X10: Unmatched incoming data_chunk=XA1AJ (A 1)
X10 db: try breaking XA1AJ into 4 and 2 character chunks:
  No match found: XAJ
06/21/08 08:57:05 AM X10: Unmatched incoming data_chunk=XAJ (A ON)
06/21/08 08:57:05 AM X10: Unmatched incoming data=XA1AJ


If I send another signal..ie: C9 On, mh doesn't see it, however, the
windows decode program would.
Is this a limitation of mh or an incorrect setting.

I know I need to figure out where the constant A1 is coming from, (a low
battery resets to A1, right?, but would the rate be this high?) but
without knowing which signals ARE coming, it's more difficult to track down.

thanks,
tom

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Tom wrote:
> It seems that the w800 on linux doesn't listen as well as on windows.
>  
Interesting, mine works perfectly on linux.  So, perhaps its something
that differs across environments/settings.
> If I send another signal..ie: C9 On, mh doesn't see it, however, the
> windows decode program would.
> Is this a limitation of mh or an incorrect setting.
>
>  
I can't explain it.  Again, if I do the above, it works perfectly every
time.
> I know I need to figure out where the constant A1 is coming from, (a low
> battery resets to A1, right?, but would the rate be this high?)
I don't see that behavior when my ms13s have low battery; instead, they
just being to report gibberish--but, only when triggered, not at some
recurring rate.

I'm wondering if there are other linux users that are experiencing the
same problems.  Unfortunately, it's hard for me to provide useful
feedback/diagnosis when everything is fine in my setup.  I have about 20
ms13s or equivalents and most of my lighting is tied to using these; so,
I would likely immediately see problems if they were to occur.

Gregg


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[hplato]

Mine worked solid on linux up until a few weeks ago. The W800RF would  
just stop responding after 3 or 4 days. A MH restart would always fix  
the problem.

I've since moved the W800RF to a proxy MH instance to help narrow down  
the variables, as well as to provide an option to use an older version  
of MH to further diagnose the problem. So far, this setup has worked,  
however I've been tinkering and haven't had MH run for more than a few  
days.


On 21-Jun-08, at 7:12 AM, Gregg Liming wrote:

> Tom wrote:
>> It seems that the w800 on linux doesn't listen as well as on windows.
>>
> Interesting, mine works perfectly on linux.  So, perhaps its something
> that differs across environments/settings.
>> If I send another signal..ie: C9 On, mh doesn't see it, however, the
>> windows decode program would.
>> Is this a limitation of mh or an incorrect setting.
>>
>>
> I can't explain it.  Again, if I do the above, it works perfectly  
> every
> time.
>> I know I need to figure out where the constant A1 is coming from,  
>> (a low
>> battery resets to A1, right?, but would the rate be this high?)
> I don't see that behavior when my ms13s have low battery; instead,  
> they
> just being to report gibberish--but, only when triggered, not at some
> recurring rate.
>
> I'm wondering if there are other linux users that are experiencing the
> same problems.  Unfortunately, it's hard for me to provide useful
> feedback/diagnosis when everything is fine in my setup.  I have  
> about 20
> ms13s or equivalents and most of my lighting is tied to using these;  
> so,
> I would likely immediately see problems if they were to occur.
>
> Gregg
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[< Dickie Bradford >]

Hi Guys:

I also run linux, Ubuntu Server 7.10 (i think off the top of my head) but
have also ran Mandrake 10.* & 2006, serial port wise, I use a Rocketport 16
pci serial card and have had no issues so far with the w800.  I plugged it
in to the serial port, set the mh parameters and that was it, its been
working without any issues todate.  I have 6 motion detectors, about 5 key
fobs and 12+ slim line wireless switches.

I have never had to mess with the setserial command

:-)

Dickie

-----Original Message-----
From: misterhouse-users-bounces@...
[mailto:misterhouse-users-bounces@...]On Behalf Of Tom
Sent: Friday, June 20, 2008 9:47 PM
To: The main list for the MisterHouse home automation program
Subject: [mh] w800RF headaches are back


I am fed up with my w800rf on my mh machine running linux.
In the past, I've had issues where it wouldn't receive any signals and
sometimes a machine restart would fix it, and sometimes stopping mh and
issuing the setserial command:

/bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a

and restarting it again.

/bin/setserial -g /dev/ttyS5      shows:

/dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11

I've tried moving it around to different serial ports and in the past,
I've had mixed results.. It even started working again on the same
serial port that it wasn't working on before.  My other devices work
fine on the serial port that the w800 is having problems on so I'm not
convinced that my serial port is the problem.

I've toyed with the idea of getting a USB to serial adapter in hopes of
avoiding these issues..

Would this be a more reliable option?  am I using the wrong setserial
options? Can someone with the w800rf and linux reply with what
"setserial -g ...." shows?  any ideas?

thanks,
tom


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3205 (20080621) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Tom wrote:

> Here's what I see in my mh log files
>
>   No match found: XA1AJ
> 06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XA1AJ (A 1)
> X10 db: try breaking XA1AJ into 4 and 2 character chunks:
>   No match found: XAJ
> 06/21/08 08:57:03 AM X10: Unmatched incoming data_chunk=XAJ (A ON)
> 06/21/08 08:57:03 AM X10: Unmatched incoming data=XA1AJ
> Serial data: event_type=X, event_data=XA1AJ
> 06/21/08 08:57:03 AM X10: Incoming data=XA1AJ
> X10: Previous units=A1 reset_flag=1
> X10 db: try breaking XA1AJ into 4 and 2 character chunks:

... not sure what made me look, but I just noticed the following in my
items.mht:

X10I, A1, bogus_x10_light, All_Lights, plm

I must have seen traffic reported on A1, and, in irritation, created
this "bogus" item to keep my logs clean.  Out of curiosity, I looked at
the state log for bogus_x10_light and noted that it gets set "off" a
couple of times a month where set_by=rf.  Nothing else ever sets it.
Now, it may also be that these times during a given month are when I
change out batteries and the devices are auto reset to A1.  I otherwise
can't explain it.  I definitely don't get the rate that you are seeing.
  But, maybe consider creating a similar "bogus" item to keep your logs
cleaner.

Gregg

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Charles Sullivan]

What do you get if you run 'stty -a -F /dev/ttyS5' ?


On Fri, 20 Jun 2008 21:51:47 -0400
Tom <tom.valdes@...> wrote:

> I forgot to mention that it works fine on a windows machine.
> Using the w800rf32 win decoder software from
> http://www.wgldesigns.com/w800.html I confirmed that it is seeing all
> signals correctly.
>
> Tom wrote:
> > I am fed up with my w800rf on my mh machine running linux.
> > In the past, I've had issues where it wouldn't receive any signals and
> > sometimes a machine restart would fix it, and sometimes stopping mh
> > and issuing the setserial command:
> >
> > /bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a
> >
> > and restarting it again.
> >
> > /bin/setserial -g /dev/ttyS5      shows:
> >
> > /dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11
> >
> > I've tried moving it around to different serial ports and in the past,
> > I've had mixed results.. It even started working again on the same
> > serial port that it wasn't working on before.  My other devices work
> > fine on the serial port that the w800 is having problems on so I'm not
> > convinced that my serial port is the problem.
> >
> > I've toyed with the idea of getting a USB to serial adapter in hopes
> > of avoiding these issues..
> >
> > Would this be a more reliable option?  am I using the wrong setserial
> > options? Can someone with the w800rf and linux reply with what
> > "setserial -g ...." shows?  any ideas?
> >
> > thanks,
> > tom
> >
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

--


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Tim Sailer-2]

Tom wrote:

> I am fed up with my w800rf on my mh machine running linux.
> In the past, I've had issues where it wouldn't receive any signals and
> sometimes a machine restart would fix it, and sometimes stopping mh and
> issuing the setserial command:
>
> /bin/setserial /dev/ttyS5 baud_base 115200 uart 16550a
>
> and restarting it again.
>
> /bin/setserial -g /dev/ttyS5      shows:
>
> /dev/ttyS5, UART: 16550A, Port: 0x2028, IRQ: 11
>
> I've tried moving it around to different serial ports and in the past,
> I've had mixed results.. It even started working again on the same
> serial port that it wasn't working on before.  My other devices work
> fine on the serial port that the w800 is having problems on so I'm not
> convinced that my serial port is the problem.
>
> I've toyed with the idea of getting a USB to serial adapter in hopes of
> avoiding these issues..
>
> Would this be a more reliable option?  am I using the wrong setserial
> options? Can someone with the w800rf and linux reply with what
> "setserial -g ...." shows?  any ideas?
>  

Revert back to the previous version of MH, or the trunk back around July
07. That's the version I'm using that has no serial problems. The
current production version and SVN trunk are seriously FUBAR in regards
to the serial stuff, IMO.

Tim

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[satz-2]

I believe when the wireless units run low on batteries they will reset  
to house code and unit code of A-1. I never use A-1 for that reason.

Thanks,
Greg

On Jun 21, 2008, at 8:05 AM, Gregg Liming wrote:

> .... not sure what made me look, but I just noticed the following in  
> my
> items.mht:
>
> X10I, A1, bogus_x10_light, All_Lights, plm
>
> I must have seen traffic reported on A1, and, in irritation, created
> this "bogus" item to keep my logs clean.  Out of curiosity, I looked  
> at
> the state log for bogus_x10_light and noted that it gets set "off" a
> couple of times a month where set_by=rf.  Nothing else ever sets it.
> Now, it may also be that these times during a given month are when I
> change out batteries and the devices are auto reset to A1.  I  
> otherwise
> can't explain it.  I definitely don't get the rate that you are  
> seeing.
>  But, maybe consider creating a similar "bogus" item to keep your logs
> cleaner.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Chris Barrett-2]

FWIW I put this segment of code in my main code file.

########## Default Device Handler ##########

$DefaultDevice_timer = new Timer();

if (state_now $Default_A1) {
  print_log "Error - a device is transmitting A 1";

  # Don't allow the error message to be spoken more than once a minute
  if (inactive $DefaultDevice_timer) {
    set $DefaultDevice_timer (1*60);
    announce("Error - a device is transmitting A 1");
  }
}

announce is just a wrapper for the inbuilt speak routine and Default_A1 is
defined in my items.mht as:

# If we detect a device transmitting A1 then it hasn't been properly
configured
X10I,   A1,     Default_A1,             Hidden

Chris

-----Original Message-----
From: misterhouse-users-bounces@...
[mailto:misterhouse-users-bounces@...] On Behalf Of Greg
Satz
Sent: Sunday, 22 June 2008 2:11 PM
To: The main list for the MisterHouse home automation program
Subject: Re: [mh] w800RF headaches are back

I believe when the wireless units run low on batteries they will reset  
to house code and unit code of A-1. I never use A-1 for that reason.

Thanks,
Greg

On Jun 21, 2008, at 8:05 AM, Gregg Liming wrote:

> .... not sure what made me look, but I just noticed the following in  
> my
> items.mht:
>
> X10I, A1, bogus_x10_light, All_Lights, plm
>
> I must have seen traffic reported on A1, and, in irritation, created
> this "bogus" item to keep my logs clean.  Out of curiosity, I looked  
> at
> the state log for bogus_x10_light and noted that it gets set "off" a
> couple of times a month where set_by=rf.  Nothing else ever sets it.
> Now, it may also be that these times during a given month are when I
> change out batteries and the devices are auto reset to A1.  I  
> otherwise
> can't explain it.  I definitely don't get the rate that you are  
> seeing.
>  But, maybe consider creating a similar "bogus" item to keep your logs
> cleaner.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Tom-172]

Thanks for all the responses.. It is now working, although I'm not sure why.

I think the w800rf may have a flaky connection or the phantom signal may
have just coincidently went away at the same time but I still believe
the MH implementation may have issues.

I did the following:
I removed the batteries from all of my RF devices MS13a's and DS10a's.
I attached the w800 to my windows machine and used the decoder from
their website.
Without the antenna attached, everything worked fine.. of course the
range was useless and it didn't pick up anything further than 20 feet
away. and it didn't pick up any of the A1 signals.

With the antenna attached I saw the flood of A1 messages.. my other
devices were still able to get their signals picked up.  MH would not
see any other signal because of the flood of A1 signals, so that's why I
think there is something wrong with the MH implementation.

I then proceeded to mess with the connection for the antenna.. I moved
it back and forth and also shifted the casing of the w800rf by squeezing
it.  As I did this the signal cleared up.

Again.. don't really have an answer to what happened, but it now works
and has been working for the last day.

thanks for all the help and suggestions.

Chris Barrett wrote:

> FWIW I put this segment of code in my main code file.
>
> ########## Default Device Handler ##########
>
> $DefaultDevice_timer = new Timer();
>
> if (state_now $Default_A1) {
>   print_log "Error - a device is transmitting A 1";
>
>   # Don't allow the error message to be spoken more than once a minute
>   if (inactive $DefaultDevice_timer) {
>     set $DefaultDevice_timer (1*60);
>     announce("Error - a device is transmitting A 1");
>   }
> }
>
> announce is just a wrapper for the inbuilt speak routine and Default_A1 is
> defined in my items.mht as:
>
> # If we detect a device transmitting A1 then it hasn't been properly
> configured
> X10I,   A1,     Default_A1,             Hidden
>
> Chris
>
> -----Original Message-----
> From: misterhouse-users-bounces@...
> [mailto:misterhouse-users-bounces@...] On Behalf Of Greg
> Satz
> Sent: Sunday, 22 June 2008 2:11 PM
> To: The main list for the MisterHouse home automation program
> Subject: Re: [mh] w800RF headaches are back
>
> I believe when the wireless units run low on batteries they will reset  
> to house code and unit code of A-1. I never use A-1 for that reason.
>
> Thanks,
> Greg
>
> On Jun 21, 2008, at 8:05 AM, Gregg Liming wrote:
>
>  
>> .... not sure what made me look, but I just noticed the following in  
>> my
>> items.mht:
>>
>> X10I, A1, bogus_x10_light, All_Lights, plm
>>
>> I must have seen traffic reported on A1, and, in irritation, created
>> this "bogus" item to keep my logs clean.  Out of curiosity, I looked  
>> at
>> the state log for bogus_x10_light and noted that it gets set "off" a
>> couple of times a month where set_by=rf.  Nothing else ever sets it.
>> Now, it may also be that these times during a given month are when I
>> change out batteries and the devices are auto reset to A1.  I  
>> otherwise
>> can't explain it.  I definitely don't get the rate that you are  
>> seeing.
>>  But, maybe consider creating a similar "bogus" item to keep your logs
>> cleaner.
>>    
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ________________________________________________________
> To unsubscribe from this list, go to:
> http://sourceforge.net/mail/?group_id=1365
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>
>  

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Tom-172]

>
> Chris Barrett wrote:
>> FWIW I put this segment of code in my main code file.
>>
>> ########## Default Device Handler ##########
>>
>> $DefaultDevice_timer = new Timer();
>>
>> if (state_now $Default_A1) {
>>   print_log "Error - a device is transmitting A 1";
>>
>>   # Don't allow the error message to be spoken more than once a minute
>>   if (inactive $DefaultDevice_timer) {
>>     set $DefaultDevice_timer (1*60);
>>     announce("Error - a device is transmitting A 1");
>>   }
>> }
>>
>> announce is just a wrapper for the inbuilt speak routine and
>> Default_A1 is
>> defined in my items.mht as:
>>
>> # If we detect a device transmitting A1 then it hasn't been properly
>> configured
>> X10I,   A1,     Default_A1,             Hidden
>>
>> Chris

I like this idea and I'll soon be implementing this in my setup.
I do have a suggestion to expand on this idea (unless there is already
something like this that I have not seen)

Would it be possible to have a table that lists the last seen signal
from all RF devices?  Using this table, it would simplify the process of
tracking down when a device needs it's batteries replaced.

If I receive the "Error - a device is transmitting A 1" I would then
check a webpage that shows the last seen time of all devices.  Since
devices like the DS10a send a signal
about every hour these would be relatively easy to find since the page
would show that it hasn't seen a signal in over an hour or two.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365