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
-
I was going to write a
@home_assistant integration for my aircon. Then I found that project, and figured maybe I didn't have to. Still going to do it.1 reply 1 retweet 14 likesShow this thread -
I just... don't understand how multiple people contributing to a project end up (manually!) capturing thousands of IR codes from remotes to make this work and don't stop and think that there might be a better way.
3 replies 0 retweets 26 likesShow this thread -
Replying to @marcan42
I'm interested ... is it possible in simple words to explain how it could be done? Isn't it necessary to try the keys one by one anyway?
1 reply 0 retweets 1 like -
Replying to @brusarp
Aircon remotes don't send keycodes, they have a screen and keep track of the current settings on the remote, then transfer the entire state to the aircon. The right way to do this is to reverse engineer the packet format and figure out where mode, temp, fan speed, etc go.
2 replies 0 retweets 6 likes -
These people are literally spending hours with each remote trying every possible speed setting times every possible temperature times every possible mode (and missing out on any additional features because some have so many combinations it would take weeks to capture them all).
2 replies 0 retweets 3 likes -
For reference, here is a quick emulator I wrote for my old aircon remote: https://mrcn.st/p/jUaSBl4E It really isn't hard to work out the fields. You change the temp, see what changes; change the mode, see what changes; etc. Often you can get more modes than the remote supports.
2 replies 0 retweets 1 like -
I've been doing a little reverse engineering lcm.. what's your approach to bytes that you can't decipher and don't seem to change, treat them as magic numbers?
1 reply 0 retweets 0 likes
A priori yes (e.g. 0x40, 0xff, 0xcc in that script), they are often going to be a device/maker code (effectively a magic number). Or if you feel adventurous you can try changing them and see if it does anything discernible.
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.