jdiazbb / rfxcmd

Automatically exported from code.google.com/p/rfxcmd
1 stars 0 forks source link

undecoded arc (sending to #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hello,

I'm trying to control a 'noname' 433MHz AC socket.
I've used RFXMgr to listen to the stream that is sent
from the remote control.

Here's what I get(when I press the button on the remote control) :

11/6/2013 1:53:25 PM= 0703010816505550
Packettype        = UNDECODED RF Message
UNDECODED ARC:16505550 
------------------------------------------------
11/6/2013 1:53:25 PM= 0703010918541554
Packettype        = UNDECODED RF Message
UNDECODED ARC:18541554 
------------------------------------------------
11/6/2013 1:53:36 PM= 0703010A16505554
Packettype        = UNDECODED RF Message
UNDECODED ARC:16505554 
------------------------------------------------
11/6/2013 1:53:36 PM= 0703010B18541555
Packettype        = UNDECODED RF Message
UNDECODED ARC:18541555 

Then I tried using RFXcmd to send these bytes:
C:\rfxcmd>rfxcmd.py -d COM3 -a send -r 0703011316505554

Here's the response:
RFXCMD version 0.24
------------------------------------------------
Send                    = 07 03 01 13 16 50 55 54
Date/Time               = 2013-11-06 13:51:00
Packet Length           = 07
Packettype              = Undecoded RF Message
2013-11-06 13:51:00 07 03 01 13 16 50 55 54
RFXCMD cannot decode message, see http://code.google.com/p/rfxcmd/wiki/ReadMe f
r more information.
------------------------------------------------
Received                = 0D 01 FF 13 16 53 43 00 0C 2F 01 01 00 00
Date/Time               = 2013-11-06 13:51:01
Packet Length           = 0D
Packettype              = Interface Message
Subtype                 = Unknown type (01)
Sequence nbr            = 13
Error: unrecognizable packet

Is is possible to do this with RFXcmd?  
I guess I need to include the ARC value in the packet aswell?

thanks.
Best regards,
Niall.

Original issue reported on code.google.com by mcandrew...@gmail.com on 6 Nov 2013 at 3:04

GoogleCodeExporter commented 8 years ago
This seems to have been fixed with using the Lighting4 tab to send packets 
starting with '18…' with help from RFXCOM.

Original comment by sebastia...@gmail.com on 22 Nov 2013 at 8:16