MS10A/WG800/Elk

lpott6

Active Member
Need some help.

I have several MS10As and DS10As that work fine when I sense then thru my W800RF connected to HomeSeer. Now I am trying to sense them with the W800RF connected to an M1-XSP module on my ELK M1G.

Per Electron's directions, I used the utility program to determine what code is being sent to the W800RF and have that written down. I have successfully setup DS10As and teh M1G responds to them. However, when I use the DS10A technique for the MS10A the M1G is not resonding to them.

I have searched for and read all the topics relating to the MS10A and the M1G and I cannot find any details describing how to do it.

I am assuming the MS10As are different somehow. What am I missing?

TIA
 

noshali

Active Member
Hi,

1. Was it working..meaning was it receiving signal when yo had the w800 connected ot the utility?
2. I noticed that if I changed the batteries on the ms10 or the ds10 and did not replace them right away...the code changed on me.

I was using all of my sensors and writing down th code and then all of a sudden the code change...I kinda narrowed it down to changing the batteries.

If only ELK could read the codes on its own.

regards,
 

lpott6

Active Member
electron, I will have to do it when I get home tonight. I will need to move the W800 back to a PC to use the utility and then I will post the the ASCII text output.

noshali, It was working fine on the HomeSeer PC and thru the utility, so I assume the W800 is receiving the signal. The batteries are all new.

I might try to give Martin a call, I bought them from AO, and see if he has done this.
 

lpott6

Active Member
Sorry I couldn't post earlier. Long day!

I must not have been to alert this morning, I really messed up the model #'s of my devices. The indoor motion sensor is am RMS18 and the outdoor version is an MS14A

I re-connected the W800 to a PC and captured these ASCI strings using the W800 Data Decoder:

RMS18: M1G Tesxt entry = F9FF
0:21:33 AM - FF 06 F9 00 Unrecognized/Corrupt Packet
0:21:33 AM - FF 06 F9 00 Unrecognized/Corrupt Packet
0:21:33 AM - FF 06 F9 00 Unrecognized/Corrupt Packet
0:21:33 AM - FF 06 F9 00 Unrecognized/Corrupt Packet
0:21:33 AM - FF 06 F9 00 Unrecognized/Corrupt Packet

MS14A: M1G Tesxt entry = F1F7
0:22:13 AM - F7 0E F1 08 Unrecognized/Corrupt Packet
0:22:13 AM - F7 0E F1 08 Unrecognized/Corrupt Packet
0:22:13 AM - F7 0E F1 08 Unrecognized/Corrupt Packet
0:22:13 AM - F7 0E F1 08 Unrecognized/Corrupt Packet


For reference, the 1st DS10A: M1G Tesxt entry = 07DF
open:
0:24:52 AM - DF F7 07 20 Unrecognized/Corrupt Packet
0:24:52 AM - DF F7 07 20 Unrecognized/Corrupt Packet
0:24:52 AM - DF F7 07 20 Unrecognized/Corrupt Packet
0:24:52 AM - DF F7 07 20 Unrecognized/Corrupt Packet
close: M1G Tesxt entry = 07DE
0:24:53 AM - DE F7 07 21 Unrecognized/Corrupt Packet
0:24:53 AM - DE F7 07 21 Unrecognized/Corrupt Packet
0:24:54 AM - DE F7 07 21 Unrecognized/Corrupt Packet
0:24:54 AM - DE F7 07 21 Unrecognized/Corrupt Packet

the 2nd DS10A: M1G Tesxt entry = 46DF
open:
0:23:16 AM - DF B6 46 20 Unrecognized/Corrupt Packet
0:23:16 AM - DF B6 46 20 Unrecognized/Corrupt Packet
0:23:16 AM - DF B6 46 20 Unrecognized/Corrupt Packet
0:23:16 AM - DF B6 46 20 Unrecognized/Corrupt Packet
close: M1G Tesxt entry = 46DE
0:23:18 AM - DE B6 46 21 Unrecognized/Corrupt Packet
0:23:18 AM - DE B6 46 21 Unrecognized/Corrupt Packet
0:23:18 AM - DE B6 46 21 Unrecognized/Corrupt Packet
0:23:18 AM - DE B6 46 21 Unrecognized/Corrupt Packet


I hope this provides some clues as to what I am doing wrong.
 

electron

Administrator
Staff member
The MS14A uses the regular X10 protocol, so no need to deal with ascii strings, just treat it like you would treat a regular X10 PLC device.

I am not familiar with the RMS18 model #, but it looks identical to the MS14A, so chance are it's just a regular x10 device as well.

Try creating a rule which triggers when a certain x10 code has beenr received.
 

lpott6

Active Member
electron said:
The MS14A uses the regular X10 protocol, so no need to deal with ascii strings, just treat it like you would treat a regular X10 PLC device.

I am not familiar with the RMS18 model #, but it looks identicla to the MS14A, so chance are it's just a regular x10 device as well.

Try creating a rule which triggers when a certain x10 code has beenr received.
Thanks, I'll give that a try tonight and report back how it goes.
 

lpott6

Active Member
electron said:
The MS14A uses the regular X10 protocol, so no need to deal with ascii strings, just treat it like you would treat a regular X10 PLC device.

I am not familiar with the RMS18 model #, but it looks identical to the MS14A, so chance are it's just a regular x10 device as well.

Try creating a rule which triggers when a certain x10 code has beenr received.
Sorry I haven't posted back sooner, had to go out of town and been very busy since I returned.

The RMS18 is just the indoor version of the MS14A and yes, it is std X10.

I have been scouring the forum for info on how to setup the M1 so it will use an X10 code to trigger events. I think it is done in the lighting section of RP. Using that premise, I activated "B1" in the lighting section and set it to "Serial Expander", but I do not know how to tell it which expander, my W800 is connected to XSP #2. Do I need to do the wireless setup too? I am so confused.

Maybe someone could provide a detailed description of how to do this? I would be very greatful.

Thanks
 

electron

Administrator
Staff member
You don't have to worry about what expander the signal is coming from. Simply create the lighting device, create the rule, and you are good to go.
 

lpott6

Active Member
electron said:
You don't have to worry about what expander the signal is coming from. Simply create the lighting device, create the rule, and you are good to go.
electron, Thanks once again for the info.

It finally sank in what I needed to do and I now have the RMS18's and MS14a working.
 
Top