Hi, I’ve started a thread to gather all the information needed to integrate a Daikin Altherma, ESPAltherma & Home Assistant with OpenEnergyMonitor
I am a little disappointed with the Daikin Stats (SCOP and COP) from the API and display, I have tried speleolontra/daikin_residential_altherma integration from HACS…
any useful guides or snippets of information would be fab, thanks @squarepeg77 @matt-drummer @Stephen_Crown 
Hi Neil @tiger_cook !
If you haven’t seen it, there’s lots in this thread already, albeit scattered.
Firstly, the standard ESPAltherma software works well, and integrates automatically with HA. The instructions are very clear, and work fine, with no actual gotchas I can think of. The only “interesting” part is the selection of items to monitor, to use the My Heatpump app at a minimum you’d need
Handy options:
I used an M5Stack StickC-Plus, because it’s a handy package with no exposed parts and a nifty LCD screen for logging, and powered it from the X10A 5V pin, as per instructions. I used an extended cable to site the StickC in a waterproof box outside the HP casing, which effectively acted as a Faraday cage and prevented the wireless signal from being received. Your mileage will doubtless vary - @Stephen_Crown doesn’t appear to need that and has it in his HP casing. Having it outside the casing is also handy if you want to reflash it with revised parameter - saves getting the heavy casing off again.
I haven’t linked HA to EmonCMS, using the EmonCMS integration, because I preferred the EmonCMS data series, storage and facilities. A small change in the setup.h file makes it work with EmonCMS directly, providing you have an MQTT broker/server set up as part of a local EmonCMS installation. Again, @Stephen_Crown has done this.
If you go directly from ESPAltherma to EmonCMS, as I did, and you subsequently want to export your data to emoncms.org, then you need to set up a regular export of your data to your account in emoncms.org, say hourly. That is because the usual route for data from OEM emon is
Sending inputs directly to emonCMS via MQTT means emonHub is skipped, along with the item-by-item link to emoncms.org. It’s just an easy config change in cron.
Once you’ve got data into emonCMS, setting up the Feeds from the Inputs is pretty easy, and then the standard My Heatpump app (basically a pre-configured Graphs display) can be set up.
Cheers
John
I’ll add to this thread when I can (I don’t have time right now), as I use Home Assistant as a middle man (for better or worse!)
Works well for me anyway.
In the meantime, suggest using the search function on this forum for “ESPAltherma” as I’ve added that word to posts I’ve made that are related to that.
I’ve now created the post doing the end to end setup:
thanks in advance @Stephen_Crown my ESPAltherma is out for delivery, I try to flash it today, however it’s a bit rainy in Gloucestershire and I do not think I want to take the cover off the Monoblock…
Will have a little work to expose the attributes in HA 1st, and then figure out a way to display a rolling COP, 1hr, 6hr, 1Day, month etc…
Here is my personal Daikin Altherma → ESPAltherma → Home Assistant → EmonCMS setup:
I hope that it is of value to others, but do feel free to modify things, try other things out. I am not stating this is the only way of doing it.
In fact, this very site has a shop which sells billing grade metering options, which will no doubt be more accurate.
I chose to go the ESPAltherma route for a few reasons:
route for installation)With that out of the way….
Electrical power monitoring
A qualified/certified electrician may be required for this step, especially if the cable you’re looking to connect the Current Transformer (CT) inside a consumer unit
You will need a separate electrical power monitor as the data from the device is not even nearly sufficient as detailed in this thread over on the ESPAltherma GitHub discussions page. It is not accurate enough due to manay factors unfortunately.
For example, I use a Current Transformer (CT) around the cable going from the consumer unit to the Daikin Heat pump sub-consumer unit, and this is linked to the myenergi system and service which I already had in place due to owning a Zappi EV charger.
I then pull this data into Home Assistant, and send on to EmonCMS. Other electrical power monitoring systems are available, including on the OpenEnergyMonitor shop
Hardware
I ordered the following hardware, and this has been sufficient:
note: I won’t link to the shop here, as I’m not sure if it is against the rules, but the screenshot should help you find whats needed:
And the RasberryPi 3 I have, and was already using it with standard Home Assistant.
ESPAltherma
Mostly documented really well over on the repo in GitHub:
Thanks go to @Raomin for this work.
However, specific points such as wifi details and MQTT details (which is in the Home Assistant part of this post) are here:
The below is the zipped file shown above, which is what I modified to expose more sensor data:
ALTHERMA(EBLA-EDLA EWAA-EWYA D SERIES 9-16KW).zip (2.8 KB)
Then below add (as uncommenting wouldn’t work as was not included!) the following line:
Use the instructions on GitHub to complete the build using VSCode for example.
M5Stick-C installation
Before completing this step, please ensure the power is turned off, ideally at both the isolator next to the outdoor unit, and as a failsafe the circuit breaker that feeds the isolator
You will want to ensure that you have a very strong wifi connection very close if you are installing the M5Stick-C inside the Daikin outdoor unit, as the external metal casing along with a presumably small and low power wifi chip means a weak signal or a high noise environment may not allow this to work.
Others in this thread have added details of how they mounted the M5Stick-C externally in an IP rated box with outdoor rated CAT5/6 network cable. That seems like a great workaround for this issue.
The below photos at various zoom levels shows where the X10 connector is located on Daikin Altherma EDLA/EBLA 9-16 models, and shows my M5Stick-C in position (for now - I might make this more permanent to be fair):
Home Assistant
You will need the Home Assistant MQTT Add-on installed, and make a note of the user/password and IP/port:
The below is how you can tell if anything at all is coming through from ESPAltherma:
Going into that entity should look like the below
Note: only sections in red will show if not yet connected it to the Daikin outdoor unit, i.e. testing inside first, which is a good idea
Once all the sensor data is pulling through, next is amending config files to be able to consume the data:
Configuration.yaml (note you’ll need to just take the relevant section from my file and to yours as long as you double check entity names match those in your system, but uploaded the whole file so you can see full context)
Template.yaml (I think you should be ok to add this in “as is”, however, do note that the sensor names match up with the ESPAltherma .h file contents further up this post)
The below is where the EmonCMS_History integration occurs, allowing for sending sensor data collected by HA over to EmonCMS cloud service.
These show up in your EmonCMS account as inputs (which are transient and are not stored, but are free)
You will need to create feeds from inputs which then persist, and these have a cost.
The below is where the new data from MQTT Add-in is processed to create new sensors in HA:
Here are the files I am using as of today December 12 2023:
configuration.zip (1.1 KB)
template.zip (1.7 KB)
Pay very special attention to entity names, I’ve had a few fixes due to names not coming through correctly/as expected. If something is not working as expected, it’s possible an entity name mismatch
e.g.
the below does not have an underscore showing here, but does in the .h file and subsequently needs it for sensor creation:
This is the device in Template.yaml:
This is in the .h file:
Also:
The below has a “_2” on the end due to my own trial/error getting this working, so if you get this working 1st time, you will NOT have the added _2 at the end
binary_sensor.3way_valve_on_dhw_off_space_2
Screenshot for full context
This particular point was relevant in trying to get the 3 way valve data and then send to EmonCMS to register the feature for automatic identification of DHW cycles per example below:
Please ensure you restart Home Assistant to get the latest version of configuration.yaml to be active.
I have been contacted (thank you!) as it has been noted I have some minor errors on sensors in the template.yaml which they’ve fixed further down this thread, however as I don’t actively use them I hadn’t spotted these. I will fix them (including uploading a fresh template.yaml) and update this post to reflect those errors corrected when I get a chance on my laptop
EmonCMS - Cloud Service
Thanks to @glyn.hudson and @TrystanLea and probably others not mentioned for this fantastic service to show the data in an informative way with features added regularly.
note: there is also a local private EmonCMS version you could run instead with info linked here, but that’s not the scope of this guide
You will need to create an EmonCMS Cloud Service account, and setup the My HeatPump app within it.
There is a concept of Inputs and Feeds in EmonCMS
Inputs are transient in nature, take external data sources, not stored and used primarily to provide data to a Feed, using the Log to Feed processing function (and some as detailed below use a few more processes than just this)
Feeds are persistent in nature, and store the data for as long as you pay for the feed (in EmonCMS cloud version anyway), and are then consumable from EmonCMS apps such as the MyHeatpump app.
You will also need to purchase credits @ £1.20 incl. VAT per feed, per year from the OEM shop
I have ~12 active feeds, so that is ~£14.40 incl. VAT/year costs for this element.
EmonCMS Write key is here and you need this for one of the steps above in Home Assistant to add to configuration.yaml:
EmonCMS Inputs you see (hopefully) are derived from the Home Assistant configuration.yaml section where your sensors are listed for sending to EmonCMS.
(remember you need to restart Home Assistant to get the latest configuration.yaml update to become active)
The important ones are highlighted in the screenshot below (I have personally added others for my own use but they are not needed for this setup) and are the ones (albeit sensor names might be slightly different) you will need to process (spanner symbol):
Note:
For those Daikin Altherma EDLA/EBLA (and maybe others?) models with a backup heater (BUH) (not to be confused with tank/cylinder booster heater/immersion) it is not accurate to use Leaving Water before BUH R1T sensor for some reason.
Defaulting to R2T (Leaving Water after BUH R2T) sensor is the current most accurate data we have from the unit for those with a BUH
For those Daikin Altherma units without a backup heater (BUH), Leaving water before BUH R1T sensor is all that is available, and it is advised to see if someone on this forum with a MID compliant Heat Meter can provide some correlated sensor data if possible to provide confidence in its’ usage
Here is the EmonCMS Leaving Water R2T processing formula that initally gave me the most issues and has the most complex steps of all of them, but works really well:
Below is a link to the thread where @Timbones kindly helped me work the formula above out.
You should be able to add the My Heatpump app in EmonCMS, and provide the Feeds setup in the previous step:
You should then be able to launch the app and thats pretty much it:
Next step if you want to publish the system on HeatPumpMonitor.org is to log in there with your EmonCMS account and complete the steps to carry that out.
Hi @Stephen_Crown you’re a star, thanks you, i have got to the following step, I have the M5 in a container on top of the HP and have wireless connectivity I guess the other attributes will get pulled through once i add to the Config YAML and connect up, I have a 8kW unit so hoping it all reads across. From your config build…
I think i will take the cover off tomorrow no rain forecastt
Your WiFi signal is pretty low - it might peg out in the case, so watch for that.
Sorry to be a bother, I have cranked up the Power on my AP as a temp workaround as it was not connecting through the case as expected, an external enclosure will be on the list.
However, I have problems with exposing additional attributes, do I have the data pins the wrong way around (the power is good 4.85V)?
I added the include def lines with your config and tried the default, still no luck.
I have not added any YAML text yet….
its raining now and will have to wait until tomorrow to double check, I am also trawling the GitHub for any gotchas. Take care Neil
@tiger_cook The voltage looks pretty similar to mine. So think that’s ok.
Any “.h” file is good for functional testing to be honest as it should pull through a bunch of data you may/may not want, but will show it is working.
It’s only when you want to get end to end testing and working the correct “.h” file will matter.
There were a few other people on the GitHub repo referencing the 4/6/8 EDLA models, not seen anyone mention this doesn’t work. Do double check the pins either end are in the right place.
If you sort your issue and I’ve missed something in my walk through, I’ll update it to include it.
@John mentioned signal is very low (but I’m guessing noise levels are too, hence it’s working), but it will work/not work. It’s obvious when it’s offline, as the “AlthermaSensors” device state is “Unknown”:
e.g.: Here is an example when I moved the Google Wifi puck half a meter before I realised I was getting dropouts
@tiger_cook sweet!
Before going to much further, suggest getting the correct “.h” file flashed onto the M5Stick-C and ensuring all of the parameters you want to use are being brought through.
I’ll update the guide tomorrow to cover pin layout and checking of pin connections.
all sorted, now using your .h template, onto the next step within HA, thanks so much for your help @Stephen_Crown
ps extended the cable outside the Monoblock
@tiger_cook Could you elaborate on this point? What exactly have you done and how? What did you use?
My Google Wifi pick is literally the other side of the wall, and M5Stick-C signal inside the Daikin outside unit is borderline.
Thinking it would be useful to document options as others are extremely likely to have WiFi signal issues.
Thanks in advance.
no probs, used some ‘stranded’ CAT5 (more flexible and less likely to break than solid core) cable to the dupont connections via a connection blocks ultimately to a waterproof box for the M5Stack…
Having a few challenges with the COP Template, changed the power sensor from your harvi CT to my ShellyEM sensor, currently getting negative values, just going to try the stock COP template to see if it helps? out of interest, why do you not use the stock template on the GitHub?
You need to turn the negative to a positive value and create a new sensor from it, from memory this is what this section of configuration.yaml does:
sensor:
- platform: template
sensors:
daikin_altherma_ct2_storage_abs:
value_template: "{{ (states('sensor.myenergi_harvi_12642274_storage_ct2') | int) | abs }}"
unit_of_measurement: 'W'
friendly_name: 'Daikin Altherma A2W Power Usage'
The stock template has a couple of issues:
Here is my modified version for Home Assistant, although I send raw data values to EmonCMS and the calcs are done there as well separately, and I tend to use EmonCMS more anyway.
- name: "COP-myenergi-power"
unique_id: "espaltherma_myenergi_cop"
unit_of_measurement: 'COP'
state: >
{% if is_state_attr('sensor.althermasensors','Operation Mode', 'Heating') and is_state_attr('sensor.althermasensors','Freeze Protection', 'OFF') %}
{{
((state_attr('sensor.althermasensors','Flow sensor (l/min)')| float * 0.06 * 1.16 * (state_attr('sensor.althermasensors','Leaving water temp. after BUH (R2T)') | float - state_attr('sensor.althermasensors','Inlet water temp.(R4T)')|float) )
/
(states('sensor.daikin_altherma_ct2_storage_abs') | float /1000 ))
|round(2)
}}
{% else %} 0 {%endif%}
As ever, any errors, please call them out, but on the ESPAltherma stock CoP template, an Issue needs raising over on GitHub if there is a problem.
I have raised one for the R1T vs R2T sensor descrepency for example.
@tiger_cook depending on what data is output, you may want a “float” rather than “int” in the transformation power formula re: divide by 100 (your CT may be spitting out kW, whereas mine was W already)
I’d read about that, but didn’t need to change mine. Worth trying
I was fairly sure (albeit I did this bit nearly 18 months ago), the “abs” element ensured a positive figure.
To be honest, you may need to ask some questions around Home Assistant over in their forums, I’m not stating I’m an expert, I managed to get it working however!
the shelly gives a ‘+’ figure for me in Watts
so I think I can just use that sensor directly in the template, will keep going on the negative COP figure…
here are the float vs int differences
@Stephen_Crown Think I found it. 
I have different values from the 8kW unit, I guess no ‘back up heater’? and I could just use the Shelly sensor
- name: "COP-power"
unique_id: "espaltherma_cop"
unit_of_measurement: 'COP'
state: >
{% if is_state_attr('sensor.esp_altherma','Operation Mode', 'Heating') and is_state_attr('sensor.esp_altherma','Freeze Protection', 'OFF') %}
{{
((state_attr('sensor.esp_altherma','Flow sensor (l/min)')| float * 0.06 * 1.16 * (state_attr('sensor.esp_altherma','Leaving water temp. before BUH (R1T)') | float - state_attr('sensor.esp_altherma','Inlet water temp.(R4T)')|float) )
/
(states('sensor.heat_pump_power') | float /1000 ))
|round(2)
}}
{% else %} 0 {%endif%}
@tiger_cook - yes I do mention in the guide that the sensor will be depended on the model.
Given the descrepency we’ve found on the larger EDLA 9-16 model with a BUH for R1T sensor, its worth adding that you’re using that sensor to your My HeatPump app name to make it clear to others thats what you’re using.
Example of mine:
Also, until someone on here that has a MID Billing Grade Heat Meter connected to the same EDLA 4-8 model range without a BUH and can provide useful correlated data, you will need to understand the sensor accuracy is unknown (but still useful for behaviour and performance characterisation)
