Monitoring and controlling an Itho Daalderop CVE RFT about ramses_protocol HOT 4 OPEN

Have a look at:

• 22F1: https://github.com/zxdavb/evohome_rf/blob/97e4b3f28d67d93050aca9e147c2c7f849c9d637/evohome_rf/parsers.py#L1299-L1323
• 22F3: https://github.com/zxdavb/evohome_rf/blob/97e4b3f28d67d93050aca9e147c2c7f849c9d637/evohome_rf/parsers.py#L1326-L1334

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!

from ramses_protocol.

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

from ramses_protocol.

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!

from ramses_protocol.

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

from ramses_protocol.