-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New device - iVac Pro remote control #3034
Comments
Hi @gcormier First, missing the file g001 and g003, were in your readme file but not uploaded, could help to confirm my assumption regarding system address. My findings:
Data Layout:
From this you can create a configuration file to decode the signal, but parity (like CRC/CHECKSUM) is not handle by conf/flex decoder. Try this:
In result you have the system address letter follow by the dip position S1 S2, the tool address number follow by the dip position S3 S4 S5, the CMD ON/OFF, the sensor ID. |
Awesome, thanks! I've added the 2 missing files (oops!) - I'm heading out for the day but I'll give it a shot later! I've also got the hex firmware extracted, so I can run it in Ghidra and see if it's possible to figure out the checksum formula. |
Hi @gcormier Thanks to your 2 missing files, which confirmed my assumption, I can share a little update:
If you want to replay your cu8 file, just add name at the end of the above command. Notice that the checksum formula is one bit parity ( 0 or 1) of the 12 first bits. I show the bit parity value from the above command, the third bit of the message, but it's not verified. A decoder is needed for that. Edit: I also notice that the message is repeated 24 times, for a total duration of 3.052 seconds and because the gap between messages is too high, 127 ms, rtl_433 can't remove duplicated values with the flex option unique. |
Thanks so much! Since it can be decoded with a flex decoder, is there something I can do to contribute to rtl_433 to recognize this device? Or does it just remain as a known device using a flex decoder? |
You or me can create a conf file based on the flex decoder and pull a request to add it to rtl_433. If you don't know how to proceed, you have samples in conf folder, and it's mostly based on the flex options. |
Hmm just realized the low values for system address are also weirdly long. Am I misunderstanding how this signal works? Why are the two 1's that occur ~1293uS, whereas the subsequent 1's are ~900uS? |
Pretty basic device using OOK.
FCC : YCH-IVACPRO
433MHz
https://www.ivacswitch.com/wp-content/uploads/2024/06/iVAC-Remote-User-Guide-ENG-FR-SP-14789-004-warning.pdf
First 2 dip switches are "System Address"
Next 3 dip switches are a "Tool Address"
https://github.com/gcormier/rtl_433_tests/tree/ivacpro
Are these enough captures to figure out what's going on?
The text was updated successfully, but these errors were encountered: