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

hsluis · October 27, 2024, 7:03pm

Do you have an advise how to proceed?

zxdavb · October 27, 2024, 7:16pm

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 · October 28, 2024, 4:21pm

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 · November 3, 2024, 3:13pm

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 · November 3, 2024, 6:45pm

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 · November 5, 2024, 2:16pm

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 · November 6, 2024, 11:56am

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 · November 6, 2024, 12:15pm

Hi Bert,

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

The presets are available in the thermostat card.

brjhaverkamp · November 14, 2024, 8:09pm

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 · November 20, 2024, 10:43am

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 · November 20, 2024, 6:36pm

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 · November 21, 2024, 2:53pm

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.

keesma · November 22, 2024, 12:36am

I am replacing my serial RAMSES RF device with the RAMSES-ESP. The ESP seems to work well. However I am running into an issue with connecting the HA RAMSES integration to MQTT. Is it required to provide a username/password, or I can just use mqtt://[ip address]:1883?
I tried the latter but it does not seem to work.

keesma · November 22, 2024, 4:31am

It works now. It was my mistake in entering the connection string in the wrong box.

I am running into another error now:

2024-11-22 05:23:54.586 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=22E0|RQ|37:211831, tx_count=1/4>: echo_timeout=1.0
2024-11-22 05:23:54.805 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback PortTransport._read_ready() (None)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 935, in _read_ready
    self._frame_read(
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 744, in _frame_read
    super()._frame_read(dtm_str, self._regex_hack(frame, self._inbound_rule))  # type: ignore[misc]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 611, in _frame_read
    self._pkt_read(pkt)
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 421, in wrapper
    fnc(self, pkt)
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 950, in _pkt_read
    super()._pkt_read(pkt)
  File "/usr/local/lib/python3.12/site-packages/ramses_tx/transport.py", line 622, in _pkt_read
    raise exc.TransportError("Transport is closing or has closed")
ramses_tx.exceptions.TransportError: Transport is closing or has closed

This error appears almost every second.
About every 20 minutes I see that the Ramses-esp disconnects from the mqtt broker.

Any suggestions?

Update:
When I enabled the serial USB stick on home assistant again and enabled the other HGI everything seems to work again, so it seems related as expected to the MQTT connection.

Sofar I only noticed that the time synchronisation in the Ramses-esp does not seem to work.

Update 2:
I set the ntp server again, as well as the timezone and the timestamp is correct now.
However when enable the Ramses-esp I get the same error messages as before.

Update 3:
I finally solved the issue by clearing the cache and restarting home assistant.

zxdavb · November 28, 2024, 5:10pm

All,

I am looking for someone with the relevant skills to take over ramses_rf and ramses_cc as I no longer have the time to contribute at the necessary intensity.

Nor do I have honeywell/resideo evohome kit any more (although the majority of users are now HVAC).

Please PM me.

GadgetUK · November 29, 2024, 12:32pm

David,

A real shame to see this, firstly a massive thank you for all the work that you’d done on this project (your project). Hopefully someone is willing and able to take this on.

Can I ask what you’ve moved to from Evohome ?

zxdavb · December 1, 2024, 10:40am

I have switched to a heat pump.

I just don’t have time to work on it any more, either.

I is a large project (three large projects, really), and still needs some work.

Yes! Please PM me - I am happy to help someone as they take this on.

dwp · December 1, 2024, 8:31pm

yes thank you for all your work David. I’m happy to help though believe it will need several people to keep it going - while I have time, I don’t have all the skills though i do have evohome.

prescott · December 1, 2024, 11:03pm

Heatpump with traditional TRVs?

Thanks for ramses_cc! Without it I wouldnt be able to find undersized radiators and so on.

Spaco · December 4, 2024, 10:03am

David! Massive thanks for the blood, sweat and tears you have put into this. Sad to see you go, but such is life. Good luck with your future endeavours.