RemehaCAN component: reading Remeha CAN bus from ESPhome

I don’t necessarily have issues with my eTwist dropping off the network, but I do see that the Remeha cloud servers unreachable pretty often :roll_eyes:

Hello, I am a heating engineer and I have just installed a Tzerra Ace-Matic that I would like to automate; it is practically the only one that is incompatible with the Gwt-08. I hope you have connected your Gwt-08 (the cable is normally designed for your Elga).
I’ll have to fall back on the Gtw-iot. I’ll see if I can bypass the Home Hub and communicate directly with this gateway.

I have actually sold my GTW-08 because my installer refused to install it, and told me that if I would do it myself it could have implications for my warranty :cry:

I have an eTwist, which I assume is similar to your GTW-IoT. If so, it might be difficult to communicate with it directly. I haven’t found any open ports on the device, for instance. So for now I’m using the Remeha Home integration. Not ideal but better than nothing.

A well documented API from the vendor wasn’t on your Santa wish list?

I have e-mailed back and forth with the product manager and got very much the impression that they want to keep their devices locked up, so I didn’t want to bother Santa with something I already knew he wouldn’t be able to deliver :grimacing:

Maybe you should be talking with the sales and marketing manager, pointing out the possibilities of increased sales to a new range of tech savvy customers, keeping up with the times. Money doesn’t talk, it shouts!

I would more spin this along the lines of security. There’s more and more awareness of the risk of infrastructure shutdowns due to hacking, be it specific by ransomware or nationwide by foreign actors. Local control can protect you from that. And fear sells better than tech-savvyness unfortunately.

Ask any Venezuelan whose lights went out the other day.

Not sure if they are the target market for Remeha heat pumps though. Not very cold there in winter.

I’m sure there are quite a few computer cycles being devoted today in Venezuela to translating SCADA documentation from Engrish (yes, spelt this way deliberately) to Spanish.

I deeply, sincerely hope they don’t use HomeAssistant to run their power stations.

Very true, the US war engine didn’t use Remeha equipment to warm up the palace or the surrounds.

The fact that Remeha have to resort to a blunt and evidentary unsuccessful technique of cease and desist warnings to protect their IP and it has been reverse engineered to the level it works speaks volumes. Security by obscurity is wishful thinking. Partial security is like peeing your pants, it gives you a nice warm feeling, but your socks are still wet.

For homeowners in Europe, a reliable heater in the midst of winter is definitely a critical part of their infrastructure. You have to trust the manufacturer. In this case, is the trust misplaced? Is there a better, more viable solution that is either fully disclosed, or fully protected?

(Leaving keywords like Venezuela, war machine, Remeha, infrastructure, scada, palace, security, here for the search engines to stumble over - they will)

Apologies for the followup question, but I finally loved into my new house and got everything in Homeassistant. The challenge is now that the Integration only supplies “heating energy delivered” which is a combination of electrical + gas (i have a Hybrid system). Do you know how to get the COP of the heatpump? I am measuring the power consumed by the heatpump.

Based on the Remeha app I should be able to get the COP from the integration somewhere…



I’m fairly sure that the HA integration doesn’t provide a COP value. I’m using my own template sensor:

- unique_id: elga_heating_cop
  name: elga_heating_cop
  attributes:
    friendly_name: Elga Heating COP
  state_class: measurement
  state: >-
    {% set delivered = states("sensor.elga_heating_energy_delivered") | float(0) %}
    {% set used      = states("sensor.elga_ace_energiegebruik_per_dag") | float(0) %}
    {{ min(delivered / used, 8) | round(1) }}

Where sensor.elga_ace_energiegebruik_per_dag is a value provided by a Shelly Plug S Gen3, into which the outside unit of my Elga Ace All-in-One (so also a hybrid) is plugged.

BTW, I’m fairly sure that the COP value that the Remeha app is showing is actually the SCOP value (so basically the long-running COP average).

As an aside: a COP of 1.8 seems a bit low, mine is 4.6 and I can’t say I have a home that’s exceptionally well suited for a heat pump (“okay” insulation and only big old radiators, no under-floot heating).

So you only have an Elga Ace and not a hybrid setup? sensor.elga_heating_energy_delivered in my case is the combination of heating energy electric + heating energy gas, so that makes calculating the COP out of that pretty useless.

My house is okayish insulated, but does have underfloor heating and JAGA low temperature radiators in the upstairs rooms, so should deliver a COP way higher than the mentioned 1,8 that it is delivering now. Will do waterzijdig inregelen and additional measurements soon.

The Elga Ace All-in-One is a hybrid (both an air-source heatpump and gasboiler for heating) :slight_smile:

Are you sure that the heating_energy_delivered sensor is both electric and gas? Because it isn’t for me.

HA:

Remeha Home:

That’s really weird! Today my heating has been fully on gas and sensor.home_heating_energy_delivered_2 shows a value of 116,00 kWh. I also looked back on mixed gas/electric days and also in there the total heat delivered is the sum of gas + electrical. Based on what I am seeing however the app does show what I want (electrical heat delivered), but the integration is not showing that value so it is probably an issue with the integration

I just realised that I’m using a fork of the integration: GitHub - nobless/BDRthermea: BDRthermea integration for Home Assistant

Perhaps that explains why mine is showing the correct values while yours isn’t.

Weird: that one only gives an “ oauth_failed” message when entering credentials.

I saw that Remeha has some cloud issues yesterday, perhaps related?

Don’t know what is going wrong, but made a local copy of the integration you mentioned and that one works! I indeed now get different sensors including sensor.heatpumpairsource_1_heating_energy_consumed and sensor.heatpumpairsource_1_heating_energy_delivered which allows me to calculate the COP! Thanks for your help!

1 Like