Little update, work in progress:
The app will use default values which can be changed to match the actual values of a users system.
No ETA yet, currently in testing but I hope to publish a new version this weekend.
New test version published
You can find the test version here: Daikin Altherma | Homey
Current test version: 0.0.7
- Added continuous power usage setting (experimental)
- Added BUH1 and BUH2 usage settings
Added settings to enter the power consumption for Backup Heater 1, Backup Heater 2 and the Continuous baseline consumption.
When first installed, the app will use a 3-phase system as default, 3000W for Backup Heater 1 (BUH1), 6000W for Backup Heater 2 (BUH2) and 40W for Continuous baseline consumption. When this doesn’t match your system, you can now adjust them to your needs.
New test version published
You can find the test version here: Daikin Altherma | Homey
Current test version: 0.0.8
- Added detection for missing labels from ESPAltherma
There appeared to be a new user who either had problems selecting the correct labels in the ESPAltherma code as explained in How To: Configure ESPAltherma and the Daikin Altherma app or was experimenting with it which resulted in numerous reports in the Developer Tools.
I’ve added a detection which will post a notification in the Timeline with the missing labels (This is rate limited to once per hour)
New test version published
You can find the test version here: Daikin Altherma | Homey
Current test version: 0.0.9
- Added notifications for errors from your Daikin
Unfortunately, our Daikin Heat Pump has gone into fault mode, but it did give me the opportunity to finish the error handling code in the app.
When your Daikin reports an error, the app will now do 3 things, once per hour:
- Write a notification to the Timeline
- Write to the app’s log
- Trigger the An error occurred in the app flow card, the Error code as a token
To be able to use this functionality, these labels are be required from your ESPAltherma device:
{0x60,3,204,1,-1,"Error Code"},
{0x60,4,152,1,-1,"Error detailed code"},
{0x60,5,203,1,-1,"Error type"},
If you had previously enabled the next labels, you should comment them, they are not used:
//{0x10,4,203,1,-1,"Error type"},
//{0x10,5,204,1,-1,"Error Code"},
New test version published
You can find the test version here: Daikin Altherma | Homey
Current test version: 0.0.10
- Fixed Energy Consumption calculations when Heat Pump is in Emergency Operation Mode
While our Daikin Altherma has gone into fault mode I also noticed the power consumption calculations weren’t accurate. This is fixed now!
Hi, and it’s great that you made an app for the Daikin Altherma with ESPAltherma. It took me some effort to get the ESPAltherma working with a board and VS code 
but it works now, and I’m temporarily logging all info to Home Assistant as a workaround.
I want to have everything in my Homey Pro, but the only thing that isn’t exactly clear to me is which file from the incl/def folder I need to use for this. Do I create an extra file for this with the name in the incl/def folder with espaltherma? Does your app look at that config file?
At the moment, I am using the config file ALTHERMA(LT_CA_CB_11-16KW).h
Hi Antoine,
The app on Homey actually has no knowledge of your Daikin devicetype and what configuration you use as the app ‘just’ reads data from the MQTT Broker.
So, in order to use this app, you first have to make sure the ESPAltherma and MQTT Broker are setup successfully and functioning.
The include file you select should fit your actual device, the important thing here is you enable the minimum requered labels for the app.
How this exactly works is explained in this post: Daikin Altherma with ESPAltherma - #5 by DaneedeKruyff
If you can’t get it to work with these instructions, please let me know how far you got and where it went wrong.
Hi Danny, thanks for your quick reply. Okay, that’s clear. I’ve made some adjustments to the file, checked the rules, and added extra ones to the config file where necessary. As far as I can see, it works from MQTT Broker.
I do have a question regarding the app, though. For a heat pump with an integrated hot water tank, which type should I choose? I have this one. I was thinking of the Altherma Water heater option myself, but then not all information passes through the device, and the log file hardly gets filled either.
When I choose the heatpump option, logging does start and all values are filled.
Hi, you’re welcome. Regarding the device, while your physical device is a two in one, in Homey it’s best to create both the Heat pump and Water heater device. This will give you separate insights per device.
Hi Danny!
Thanks so much for the app, got my MQTT running and very happy to see the outputs in Homey! I am also running ALTHERMA(LT_CA_CB_11-16KW).h like @snowboardrulez
Now i had a few more values (for instance current temperature inside) which i wanted to track in insights. Not really a programmer but with a bit of gpt help got these up and running in GitHub - MichielMmm/com.altherma.mqtt: ESPAltherma support for Homey · GitHub
Two thinks noted in the app that might benefit you and others:
1 - The target water temp was not comming trough. Update DHW target temperature from MQTT · daneedk/com.altherma.mqtt@bb4c05a · GitHub
2 - i got an error every hour in the log (because i do not have the detail error code field availabel in the device file). It could not specify what it was missing, gpt suggested an update; Make extended error labels optional and fix translation · daneedk/com.altherma.mqtt@c202a6a · GitHub
Again thanks for creating this, awesome integration 
Thanks, I’ll have a look. Indoor temperature isn’t exposed for my Daikin so I didn’t include it.
I’ll have to look into how to handle differences in supported capabilities, as your particular device does not expose the error codes, but I want to keep them for devices that do support them.
So, I had a look in your repository today and that made me realise I hadn’t even committed or published the latest code.
I had indeed added the target_temperature_dhw capability earlier to the water heater device, but never actually added the code to update it from the data received from ESPAltherma, I really don’t know what I’ve been doing.
Regarding the error labels, I see the Error type label (at line 30) in the definition file you are using, but you still commented it out in app.js. Did that label not return anything or was it problematic in some way? Could you try uncommenting Error type in the ESPAltherma definition file, and uncommenting Error Type at line 24 in app.js and see if it does not throw an error or write a notification?
I’ve change the ErrorCode code so it can handle a missing Error Detailed Code.
Now for the third commit where you remove and add some capabilities, when writing the app I decided to try to add as little capabilities as possible to not overload a user with to technical or redundant information.
Quite some labels are therefore not added as capabilities in the devices, but are there to be written to the log.
Are you aware you can enable extensive logging in the apps settings and retrieve that information for analysis in for example Excel, or even more powerful let an AI agent analyse it?
Scroll all the way down in the app’s settings:
See this post for some more information.
A remark about the temperature inside, I see you added Indoor ambient temp. (R1T). Have you checked this is your actual indoor temperature? I tested this label, but found out it is not the indoor temperature as measured by the room thermostat, but the temperature in the Altherma device itself. May I suggest you check this with your actual room thermostat or install the Daikin Onecta app and compare the values between the two apps.
I’m not sure what to do with your changes in the capabilities or if you want me to do anything with your changes, how it is now I can’t really do anything with it as you’ve removed capabilities which are already in use and that would create problems for existing users.
New test version published
You can find the test version here: Daikin Altherma | Homey
Current test version: 0.1.0
- Added more languages
- Added code to actually set the target temperature of the water heater
- Fixed the code that informs about missing labels
Thanks @Michiel_M for finding these bugs!
This is awesome, thanks for looking into this so quickly Danee!
In commented out the error type because i did not enable it in the ESP, i will do in next update. Especially as you also added handling when error detailed code field is unavailable.
In added some more fields because i wanted to add them in a dashboard. But actually good to know that advanced logging feature, in was not aware! That is super useful for AI analysis indeed 
So great updates, in also wanted to try for myself of gpt could make me a bit of a programmer. But seems i can go back to the original app then, Thanks!
One question not directly related to your Homey app. You know if there is a way to check which values the ESP is receiving, other then the device capability file?
You’re welcome and thanks for your donation, much appreciated!
Play around with the logging, if there’s anything you’d like to be included I can investigate if that’s possible. (unique labels for a particular device can be troublesome, so no guarantees )
The code ChatGPT was workable, but it took a short route, removing and replacing existing capabilities without a migration patch will surely brake functionality for others.
Using AI for getting some working code is not bad, using AI to maintain an app is a whole different story, I can tell you. You can certainly learn a lot form it, but be very critical of what is provided.
About what information can be received by ESPAltherma for your particular system, I think you can better ask this at the ESPAltherma repository discussions.
