Peter Avram

Sorry for barfing this up, but this is the wonderful hack I've been thinking about making less dangerous. I'm going to go look for the post where this was raised...

In order to implement this; we'd need to do packet captures from the original hardware/remote software to capture each side of the communications and a copy of each of the...

@radinsky I will have a look. But just in case I drop off the face of the earth. when you do the packet capture attach it to this thread. That...

Sorry to be a pain @radinsky, but it turns out the app is slightly more annoying than I realised to get packet captures. The app (I have verified this) caches...

@radinsky looks good. Just on a lunch break right now so I haven't teased the rest apart yet, but packet 99 in that capture is an Auth reply from the...

I've reformatted the packet capture into a simple file (including lines for the PING sections) [s1c_simple.txt](https://github.com/mjg59/python-broadlink/files/1000175/s1c_simple.txt) I have also built a web service that uses my library to investigate the...

Its all good. I've been working backwards. The broadlink protocol uses the "data" and "data_reply" type packets to transmit requests and info. Due to the encryption the payloads *must* be...

Nice work all, I've done some more poking around and have extracted each of the packets and a "state" before and a "State" after for each event. We might need...

Hi @PeggyFree, of all the packet captures I investigated, there didn't appear to be any packets that originated from the S1C itself (without an associated request asking for the data)....

there are some pretty big issues with the protocol.md. My experience so far is to defer to the implementation (__init__.py). That documentation file has some pretty big issues. One major...