Open reneklootwijk opened 3 years ago
Please format your post - I have done a start for you.
Have a look at:
Also look at 31D9
, and 31DA
.
You can capture packet logs and try things like:
cat packet.log | python client.py parse
You can post to @Raqbit here: https://gitter.im/evohome_rf/community
He & you may be able to collaborate further.
I have switched to an MIT license, here and at evohome_rf - enjoy!
Apparantly you already knew part of it. I will now try to pair my code as a new remote to the Itho CVE.
My node.js module is alsmost finished, so I use my own code to monitor and try things.
I see 31D9 and 31DA messages from toher unknown devices, with id 20: and 37:. Does this sound familiar.
BTW thanks for using the MIT license!
I see 31D9 and 31DA messages from toher unknown devices, with id 20: and 37:. Does this sound familiar.
Yes - have a look in evohome_rf/parsers.py - all that is known by me is in there!
(except for the sequence # issue)
@Raqbit may know more
By coincidence I noticed my Itho Daalderop CVE RFT uses the RAMSES-II protocol for communication with the RF remotes.
The remote has 4 keys and the 4th key activates a timer. The timer depends on the number of key presses (1-3). When a button is pressed it broadcast a message 3 times.
For mode 1 (low) the following messages are send:
63:163409 is the address of the remote, my other remote uses: 62:228945
For mode 2 (normal) the following message is send:
For mode 3 (high) the following message is send:
For mode 4 (timed high) the following messages are send for 1 key press (timer=10m):
For mode 4 (timed high) the following messages are send for 2 key presses (timer=20m):
For mode 4 (timed high) the following messages are send for 3 key presses (timer=30m):
Controlling also works by sending the following for instance: