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 …
-
Show this thread
-
Replying to @marcan42
…I can _see_ the patterns just looking at the damn base64
2 replies 0 retweets 5 likes -
Replying to @11rcombs
Actually a lot of the changes are probably noise, because the base64 encodes learned *analog* pulse widths. The Broadlink packet format is known, but nobody bothered to make a generic pulse train API to at least unify IR blasters yet. That's my step 1.
1 reply 0 retweets 4 likes -
Replying to @marcan42
yeah, noticed with a tiny bit of poking that some bits were consistent across samples and some looked like noise
1 reply 0 retweets 0 likes
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.
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.