Skip to content
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

Monitoring and controlling an Itho Daalderop CVE RFT #5

Open
reneklootwijk opened this issue Mar 7, 2021 · 4 comments
Open

Monitoring and controlling an Itho Daalderop CVE RFT #5

reneklootwijk opened this issue Mar 7, 2021 · 4 comments

Comments

@reneklootwijk
Copy link

reneklootwijk commented Mar 7, 2021

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:

067  I 132 --:------ --:------ 63:163409 22F1 003 000204

63:163409 is the address of the remote, my other remote uses: 62:228945

For mode 2 (normal) the following message is send:

060  I 133 --:------ --:------ 63:163409 22F1 003 000304

For mode 3 (high) the following message is send:

065  I 134 --:------ --:------ 63:163409 22F1 003 000404

For mode 4 (timed high) the following messages are send for 1 key press (timer=10m):

067  I 135 --:------ --:------ 63:163409 22F1 003 000204
053  I 136 --:------ --:------ 63:163409 22F3 003 00000A

For mode 4 (timed high) the following messages are send for 2 key presses (timer=20m):

067  I 137 --:------ --:------ 63:163409 22F1 003 00000A
053  I 138 --:------ --:------ 63:163409 22F3 003 000014

For mode 4 (timed high) the following messages are send for 3 key presses (timer=30m):

067  I 137 --:------ --:------ 63:163409 22F1 003 000014
053  I 138 --:------ --:------ 63:163409 22F3 003 00001E

Controlling also works by sending the following for instance:

I --- 18:000730 --:------ 63:163409 22F1 003 000404
@zxdavb
Copy link
Owner

zxdavb commented Mar 7, 2021

Please format your post - I have done a start for you.

@zxdavb
Copy link
Owner

zxdavb commented Mar 7, 2021

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!

@reneklootwijk
Copy link
Author

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!

@zxdavb
Copy link
Owner

zxdavb commented Mar 7, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants