Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm

[hsluis]

Do you have an advise how to proceed?

[zxdavb (David Bonnes)]

Well, destroy zone 1 (which has the OTB bound to it) for a start. Then re-create it with the correct actuators (TRVs, I think, yes?).

Then, you’ll need to reset the OTB, otherwise it will do what zone 1 asks, as well as the controller - this could ‘stop’ any optimizations the controller may choose to make.

Then you’ll need to re-bind the OTB to the controller.

And why did zone 0 go from 3 TRVs to 1?

[katagia]

@katagia

The devices are found but all of their entities are unavailable. The system log shows errors:

…

How can I fix this and make the thermostats work?

@zxdavb

The errors you are receiving apply only to those packets. All other packets should be processed normally.

Do you have any entities show up OK? Most of them come via packets Tx by the controller.

You don’t generally have any value from the thermostats, other than it is nice to know if their battery is going flat.

For all other devices I can see the entities. For the thermostats, I can see the entities for battery and temperature but they are marked as unavailable. As they are were recognized I hoped it’s only a configuration issue why they can’t be read.

[brjhaverkamp (Bert)]

Hi David,

Also from my side, thanks for looking into this.
I followed your advice for the moment. I disconnected my thread dongle to free up a USB port and added the RAMSES_ESP.
I only changed the serial setting, and it looks like it picked up on all 4 devices correctly. I was able to set the temperature and sofar the devices haven’t gone missing :-).

Hope I can help figuring out what is the cause, because I want to go back to mqtt at one point.

Do you need more logging?

Bert

[rhjbruins (Rick)]

Hi All,

Love the work that has been happening here!

I have a request. as I have a MVS-15 ORCON box. And I would love for it to go into home assistant. I shouldn’t be too hard, I’ve figured out what’s the cause.

packet.log
2024-11-03T19:13:56.141016 078 I — 29:211060 --:------ 29:211060 31D9 003 000004

home-assistant.log
2024-11-03 19:13:56.141 INFO (MainThread) [ramses_rf.dispatcher] || 29:211060 | | I | fan_state | 00 || {‘hvac_id’: ‘00’, ‘exhaust_fan_speed’: 0.02, ‘fan_mode’: ‘04’, ‘passive’: False, ‘damper_only’: False, ‘filter_dirty’: False, ‘frost_cycle’: False, ‘has_fault’: False, ‘_flags’: [0, 0, 0, 0, 0, 0, 0, 0]}

The message is an 31D9. And it’s not being translated in the hvac.py in ramses_rf see below.

    @property
    def exhaust_fan_speed(self) -> float | None:  # was from: (Code._31D9, Code._31DA)
        return self._msg_value(Code._31DA, key=SZ_EXHAUST_FAN_SPEED)

    @property
    def exhaust_flow(self) -> float | None:
        return self._msg_value(Code._31DA, key=SZ_EXHAUST_FLOW)
    @property
    def exhaust_temp(self) -> float | None:
        return self._msg_value(Code._31DA, key=SZ_EXHAUST_TEMP)

I changed the code in my home-assistant docker for fan_speed, and it picks it up just fine. Any chance something can be done?

[hsluis]

Hi Bert,

Unfortunaly my device running Home Assistant is too far away to do this test myself. But did you also experienced that with the RAMSES_ESP MQTT setup the devices go missing when you change the temperature? And is that gone after connecting the device to USB?

Patrick

[brjhaverkamp (Bert)]

Hi Patrick,

Yes, when the device was available to start with, (which often it wasnt), when I set the temperature. most of the times the device bekame unavailable. But 1 or 2 times I was able to set the temperature.

On a related note I now have a serial link via USB. This is stable. But I miss how to set the mode to “Away”, or any of the other overrides. Can I configure that?

Bert

[hsluis]

Hi Bert,

Thank you, good to know. Hopefully the issue can be fixed soon.

The presets are available in the thermostat card.

[brjhaverkamp (Bert)]

Hi Patrick,
Thanks for the screenshot. I missed the option to select the profile. I found out that you can set that in the options of the card. Solved now.
And I can set away and home now as well. Hurray!

[hsluis]

Hi David,

After making the changes you advised the problems stayed the same. Since these problems were gone when Bert changed from MQTT to USB connected I tried the same. Although the distance between my Home Assistant machine and the EvoHome system is a bit too far the integration now works stable. So looking at the results of Bert and myself I think there is an issue with the MQTT communication. Is it possible to further analyse this, so it can be solved and how can I help?

[GhostlyFriend]

Hello,
As a complete noob I hope to find some assistance here for my first steps.
Today I’ve installed a Home Assistant Green.
I have HACS installed, and Ramses RF is one of the services that I see when I go to Settings / Devices & Servides.
I have plugged in the SSM-D2 stick from Indalo tech in the HA Green usb port.

I have put the following line in my configuration.yaml
ramses_cc:
serial_port: /dev/serial/by-id/usb-SparkFun_evofw3_atmega32u4-if00

I also tried different values after “/dev/serial/” that I found in differtent topics.

After restarting I open the Logbook and select the Entity Ramses RF. There are no entries.

This is about where I am at the moment. I read and applied the knowledge that I could find across the interweb.

So could anyone point me in the right direction for the next step? Tx!

[Kars (Kars de Jong)]

Unfortunately the wiki is not up-to-date, there is no need to add it to configuration.yaml (that’s deprecated), you need to add the integration through Settings → Devices & Services → + Add Integration button. Search for ramses and then click > on that line. You should then be presented with a dialog.