You could reverse engineer a proprietary protocol. Or I guess you could just manually capture the cartesian product of all possible field values, and make a giant lookup table. Times multiple proprietary target encoding formats. Times dozens of devices.https://github.com/smartHomeHub/SmartIR/blob/master/codes/climate/1023.json …
-
-
yeah, noticed with a tiny bit of poking that some bits were consistent across samples and some looked like noise
-
Once you convert it to a list of pulse widths they're all going to be a trivial format like "0 = short pulse long gap, 1 = long pulse short gap", and after you take out that layer the actual packet encoding will be trivial.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.