Support for HCC100 - Githubissues

zxdavb / ramses_rf

An interface for the RAMSES RF protocol, as used by Honeywell-compatible HVAC & CH/DHW systems.

MIT License

55 stars 15 forks source link

Support for HCC100 #86

Open woepies opened 9 months ago

woepies commented 9 months ago

Honeywell / Resideo introduced the HCC100 underfloor heating controller. I installed it as part of my Evohome setup, replacing my HCE80. Would it be possible to add support for the HCC100 in ramses_rf and ramses_cc? I would be happy to provide packet logs, etc.

I think my HCC100 is device 02:066404. The Home Assistant log includes this line:

2023-10-01 10:03:07.436 WARNING (MainThread) [ramses_rf.protocol.message] I --- 02:066404 --:------ 02:066404 3150 008 2100220023002400 < Corrupt payload: Payload doesn't match '^((0[0-9A-F])[0-9A-F]{2}|FC[0-9A-F]{2})+$': 2100220023002400

zxdavb commented 9 months ago

UFH is a 2nd-class citizen in ramses_rf - a situation I would love to address. Indeed, I have purchased a HCE80 for that purpose, but I am very time-poor.

Nonetheless, please do send me a packet log, and I can get to work on tweaking the parsers, which will address the above error message, at least.

What would be great would be at least 24h of packet logs (and 3d even better), with the UFH actually turning on/off.

I would also like to know your setup, and specifically if you're using OpenTherm. Which UFH zone are set to which Evohome zones would also be useful

Finally, please let me know what you mean when you want the HCC100 supported. What functionality would you like? I envisage exposing as much info as possible as HA sensors, or is there more?

You can post links here if you're willing, or PM me that stuff via community.home-assistant.io: I am zxdavb

Thanks

woepies commented 9 months ago

Outdoor temperatures are still high in the Netherlands and the CH (incl UFH) is switched off. I will send the packet log once the system is on. I was using on/off switched (BDR91) to control the boiler, but recently switched to OpenTherm because the HCC100 is supposed to support it. I still have the BDR91, so I can switch back to experiment.

In the meantime I attempted to study the HCC100 behavior myself.

The HCC100 sends a 10E0 Device Info packet when booting. The structure is the same as described on the wiki. However, the payload starts with FF, causing the parser to refuse it, 10:59:43.614 I --- 02:066404 --:------ 02:066404 10E0 038 FF0001C89D6E0600FEFF140107E7010C07E64843453130302D524144494F0000000000000000

description: "HCE100-RADIO" firmware: "20-01-2023" manufactured: "01-12-2022"

zxdavb commented 9 months ago

I have addressed the above with commit a86bd3f9733a1ea523bc819873e0cb97861fcbc9 - Add HCE100's 10E0 to protocol