Hi Egbert,
HA 2026.5.3
Just upgraded to 2026.5.4 same issue.
Cleared the system state (recent packets), same result.
As part of troubleshooting i did remove completely ramses from hacs per the wiki. for that to really happen i also needed to remove the ramses dataline in /config/.storage/core.config_entries next to the deleting the ramses_cc file. It was still getting the data from there.
It resulted in an error 500 during the initial configuration, very similar as the current error. It seems somehow to crash on finding the serial port options. Restored a backup to get all working again.
any other suggestions?
I am running the latest HA too. Ramses 55.3 seems to be the latest version that supports fake evohome sensors, tried a few versions after that but had to roll back
Thanks for the restore details.
What exactly is your (serial) port connection type? USB, HA MQTT app or Mosquitto Broker?
Tip: Remove any personal settings eg. password; replace by "usr" and "pwd".
Connecting to Mosquitto Broker, initially configured via the manual input, the last item in the port menu if i remember well
The below is what i took from /config/.storage/core.config_entries. ( With changed usr/pwd 
"serial_port":{"port_name":"mqtt://usr:[email protected]:1883"}},"
ramses_esp obviously connects to the same broker, it is not on the same host as HA
somebody else seems to have very similar or same issue. See Error 500 on install
Egbert, upgrading to 0.56.8 indeed gets back the menu. so that is clear. 0.56.8 doesn't work for me. Very similar as here 0.56.8 Evohome device discovery inconsistent · Issue #677 · ramses-rf/ramses_cc · GitHub I assume 0.56.8 is a work in progress. For now i go back to 0.56.1, wich works great. ( evohome, OTB, fan). Thanks so much for the great efforts on this great integration!
Hello @Vedovatod, I have a similar heat recovery system (mine is Broferpura - RDCD25SK). After seeing your successful configuration, I purchased the Indalo-Tech dongle and I am currently integrating my heat recovery system.
Would you mind sharing your latest ramses_cc configuration for reference?
Hi All. I have been using this with an evofw3 atmega32u4 since 2022 with no issues. I upgraded to 0.56.x and lots of times I got unavailable sensors. So I performed a full wipe and install. I kept the known list and basic schema for one sensor. Since doing that, it wont detect my schema and the gateway sensor just says "problem". This was working since 2022. Any idea what has gone wrong? Any direction would be great.
I have also been a very early adopter - I understand from reading here the original developer David Bonnes passed it on and the new team (I believe) had to undergo some changes to comply with Home Assistant as well as adding new heat sources, which appears to have broken Evohome. I also accidently upgraded a couple of months ago and have lost my Ramses components. I have now reverted to the API connection, not ideal as we mainly prefer to be cloud free. I have no idea where they are on resolving this - the Github repo seems to be more active than here. Like many Im also awaiting a fix that hopefully will be coming. It may be helpful for some statement of where things are to avoid confusion.
@davidtja I just removed everything again and went back to 0.55.3 and my configuration.yaml information and within minutes everything was back up and running.
I am also on 0.55.3 and somewhat hesitant to move up until Evohome support is stable.
Sorry to report that we are not there yet for evohome. A lot of work was done on the back end, also to keep up with HA and not blocking the main process. If 0.55.3 does it for you, I suggest you stick with it until further notice.
I am 
happy to try any version and also support in anyway. It also could be something on my end.
Also an evohome user here, 0.56 releases simply refuse to work for me. 0.55 and 0.54 are ok'ish, although often a very large delay between changing temps/modes in HA and having the hardware respond.
Ive tried going back but no success. I'm hopeful the guys will get it resolved. From my perspective and given I am in the UK, I have a few months before serious use and in the meantime have the API version. Thanks
Try this 1. Installation · ramses-rf/ramses_cc Wiki · GitHub. Keep your known list before you do the wipe. Download 0.55.3, now I put the config in my configuration.yaml like before. See how you get on.
Hi, same here, I've been using this since David released it back in the day, I have a system with two controllers which means I have two instances running, one with the original usb HGI80 as and the second one using the evofw usb adaptor.
It was rock solid and had very few issues over the last few years but now my hot water automation stopped working after upgrading to 0.56 and trying to fix that I've gone to 0.57 and everything is broken.
Can you guys please look into this, we rely on the hot water automation heavily but I can't trust it to boost it.
@hamba To be fair, we should acknowledge that HomeAssistant has moved on since, and that has required changes deep inside Ramses RF.
There's a risk of breaking things, and the certainty that old versions will not load at all.
Fixing 0.56.0 by installing pre-release 0.57.0 is not advised for evohome users, as line 1 of the ReadMe states. Scroll up to learn where we stand and what other evohome users have done to restore their setups.
Egbert, maintainer
@EgbertB - no worries! I know it can be annoying when HA changes standards and you need to modify things to keep up. I'm tracking the issues in the repo and salute the brave evohome users running profiles and debug logs to be help PWhite get to the bottom of these issues - and thanks for his efforts! I'm on 0.54.3 for the moment which is stable enough (have automations that depend on ramses working more-or-less correctly.) and the upgrade path forward is broken. Happy to test again when discovery is being figured out!
Hi.
Sorry if I came across a little harse, I appreciate you guys keeping this going. I'm well aware that things move on and that it can cause problems.
Because I have two evohome controllers I run HA on separate devices from my main HA and they normally lag by a few versions.
Keep up the good work.