First of all, thanks for this integration — it works well and is stable 👍
I’m currently using this integration with a Daikin Altherma 3 and the BRP069A62 interface. I’d like to ask if it’s possible to expose more parameters that are already available internally, to enable better monitoring and energy analysis.
Specifically, it would be very helpful to have access to:
• Compressor active status (on/off)
• Backup heater active status (at least combined, if stages are not available)
• Fault / alarm status (binary + code if possible)
• Additional temperature sensors (flow, return, outdoor, internal)
• Thermostat / zone switch states (heat demand yes/no)
• Any power or runtime-related values that could help calculate COP (e.g. compressor runtime, electrical input indicators)
We’ve seen that many of these parameters appear to be available on the Daikin internal bus and are exposed by other gateways, for example in the HMS/Intesis Daikin-to-Modbus interface documentation:
https://hmsnetworks.blob.core.windows.net/nlw/docs/default-source/products/intesis/manuals-and-guides—manuals/user-manual-in485dai001a000.pdf
The main goal is to calculate COP more accurately and to better understand system behavior (defrost, backup heater usage, faults).
I understand that the BRP interface may have limitations, but even partially exposing additional data (raw or derived) would already be very valuable.
Thanks for considering this, and happy to help test if needed.
First of all, thanks for this integration — it works well and is stable 👍
I’m currently using this integration with a Daikin Altherma 3 and the BRP069A62 interface. I’d like to ask if it’s possible to expose more parameters that are already available internally, to enable better monitoring and energy analysis.
Specifically, it would be very helpful to have access to:
• Compressor active status (on/off)
• Backup heater active status (at least combined, if stages are not available)
• Fault / alarm status (binary + code if possible)
• Additional temperature sensors (flow, return, outdoor, internal)
• Thermostat / zone switch states (heat demand yes/no)
• Any power or runtime-related values that could help calculate COP (e.g. compressor runtime, electrical input indicators)
We’ve seen that many of these parameters appear to be available on the Daikin internal bus and are exposed by other gateways, for example in the HMS/Intesis Daikin-to-Modbus interface documentation:
https://hmsnetworks.blob.core.windows.net/nlw/docs/default-source/products/intesis/manuals-and-guides—manuals/user-manual-in485dai001a000.pdf
The main goal is to calculate COP more accurately and to better understand system behavior (defrost, backup heater usage, faults).
I understand that the BRP interface may have limitations, but even partially exposing additional data (raw or derived) would already be very valuable.
Thanks for considering this, and happy to help test if needed.