At 11:30 AM 1/29/00 , you wrote:

> Since moving to v1.96 I have started getting unrecognized X10 data
> messages.  Like:
>
> 01/28/00 18:10:33: unrecognized X10 data: X99
> 01/28/00 18:05:59: unrecognized X10 data: X92
> 01/28/00 18:05:59: unrecognized X10 data: X99
>
> Where is this info coming from?

hmmm.  Maybe this is coming from the new 'extended data receive' feature
that Danal Estes put into CM11.pm.  That was new with 1.96, although it
doesn't look like extended data.  I have not seen it yet.   Do you know if
you have any extended data devices?  I'm not even sure what can transmit
extended data, other than the Garage Door sensors that Danal was coding for.


        No, I don't have any extended data devices....I don't think at least.

Can you reproduce it somehow?

Bruce


        Yes I have been able to produce it pretty regularly.  Every time a motion detector detects motion.  I have both the motion and light codes set up as Appliances.  Since the motion detector is turning on the light in the same room as it is in, the light sensor sends its code soon after the motion detector senses motion.  Here is what I get in the log running with the following start up options:  -log c:\debug.log -debug X10

note: that both F4 and F5 are X10 Appliances....

CM11 data=3 hex=03
receive buffer length=3, mask=00000010, data_h=03029a92.
CM11 db: data=F4FJ
CM11 send data=BB
CM11 dim=0 header=00000100 hb=1110 cb=0011 bd=0x04,0xe3 checksum=0xe7
CM11 send: 04e3
..
CM11 data=231 hex=e7
CM11 ack
.........
CM11 data=85 hex=55
CM11 done
CM11 send data=BJ
CM11 dim=0 header=00000110 hb=1110 cb=0010 bd=0x06,0xe2 checksum=0xe8
CM11 send: 06e2
..
CM11 data=232 hex=e8
CM11 ack
.........
CM11 data=85 hex=55
CM11 done

CM11 data=90 hex=5a
mh CM11 data=Z data_d=90

CM11 data=5 hex=05
receive buffer length=5, mask=00001010, data_h=050a91929992.
CM11 db: data=F5FJ
X10 db: try breaking XF5FJ9992 into 4 and 2 character chunks:
  Found match: XF5FJ
X10 db: try breaking XF5FJ9992 into 4 and 2 character chunks:
  No match found: X99
X10 db: try breaking XF5FJ9992 into 4 and 2 character chunks:
  No match found: X92
Running serial_data_buffer string: XF5FJ
Serial data: X10 merged string=XF5FJ9992F5FJ